[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: compatability- lsim() suggestions?

From: Paul Kienzle
Subject: Re: compatability- lsim() suggestions?
Date: Sat, 08 Mar 2003 22:38:58 -0500
User-agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.3a) Gecko/20021212

Raymond Rogers wrote:

A S Hodel wrote:

Then a year later MATLAB came out with the tf, ss, zpk functions, etc., using MATLAB's new object-oriented programming capabilities and a whole new way for Octave and MATLAB to be incompatible was born. Pretty clever, eh? Now that raises some pretty involved (pronounced "labor intensive") issues in how to make Octave and MATLAB "compatible." Given that only one part of that team (and only part of that part) is interested in pure MATLAB compatibility, some thought needs to be put here - including
thoughts toward backward compatibility.

"Exciting - isn't it?"  Draal, Babylon 5.

Thanks for the information. Knowing that I will just convert the offending code over to the new form. This should avoid compatability problems ( of this sort) and be transparent. ss2sys is a function in Matlab isn't it? I can't seem to find it in my version; version 4.0

The function is called ss in matlab and ss2sys in octave.
The interface is a bit different.
You could:

 (a) write code which does a runtime check and calls
  either ss or ss2sys,

 (b) write an install script that converts from ss2sys to
  sys when installing in matlab  (or vice versa),

 (c) write ss for octave and add it to octave or
   octave-forge, or

 (d) write ss2sys for matlab and install it if needed.

Paul Kienzle

Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:
How to fund new projects:
Subscription information:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]