In article <320F2517.firstname.lastname@example.org>, Ken Davis <email@example.com> writes: > Matt Feinstein wrote: >> >> Hi all-- >> >> How come Simulink lets you vectorize the inputs and outputs for a >> linear state-space block or an integrator block but can't do the same >> for a linear transfer function block? This doesn't seem logical. Am >> I missing something here? >> >> Matt Feinstein >> firstname.lastname@example.org > > For the same reason that their "filter" function can't filter multiple > time-series simultaneously. I've never understood why this is so. It > would be a relatively simple modification to the code to add an extra > loop, it would require no change to the calling sequence, and it would > add immensly to the functionality. Maybe in the next version...
The largest side effect to vectorizing the transfer function or filter blocks is that SIMULINK would require an additional set of discrete or continuous states for each additional input element. BTW, it's actually a bit tricker to do than you realize.
I'll answer some obvious questions:
Are we doing this for SIMULINK 2? No.
Did we consider doing this for SIMULINK 2? Yes.
How come you didn't implement this for SIMULINK 2? We really haven't received a lot of requests for this functionality. I am certain that these blocks will be vectorized in the future, perhaps 2.1.
When will SIMULINK 2 be available? Don't know.
__ Rick Spada _______________________ email@example.com __ The MathWorks, Inc. firstname.lastname@example.org 24 Prime Park Way http://www.mathworks.com Natick, MA 01760-1500 ftp.mathworks.com __ Tel: 508-647-7000 ___ Fax: 508-647-7001 _________________