Description

murrayrm

opened on Jun 7, 2023

Issue body actions

As described in #905:

Any reason why initial_response, step_response, and forced_response can’t/shouldn’t be modified to be compatible with NonlinearIOSystems? It was a bit confusing to students in my class last quarter why they had to switch to a different simulation function if they included a nonlinear system in their InterconnectedSystem.

It should be possible to make all of the systems work for a NonlinearIOSystem.

For the impulse response, we could take the linearization of the system at the initial condition and then use that to reset the initial condition, though I'd want to think that through make sure that is the right thing to do mathematically.

Activity

1. murrayrm

   added this to the 0.10.0 milestone on Jun 7, 2023
2. murrayrm commented on Jun 8, 2023

   

   murrayrm

   on Jun 8, 2023

   MemberAuthor

   More actions

   From #905:

   As we move into 0.10 (see #904), I think we can do the following:

   • Allow initial_response and step_response to work for either linear or nonlinear systems.
   • Allow forced_response to take a nonzero X0 as an optional argument, but perhaps document it as mainly being there for the "pure" forced response, which at least one textbook defines as corresponding to X0=0 (FBS, page 6-3).
   • Use input_output_response as the general function for simulating a linear or nonlinear system for a specified input and initial condition (suggestions welcome for a better name).
   • Allow impulse_response only for linear systems (mainly because I think it is mainly useful for educational purposes when teaching linear control theory, convolution, etc).
3. murrayrm

   linked a pull request that will close this issueI/O system class restructuring #916on Jun 19, 2023
4. murrayrm

   closed this as completedin #916on Jul 2, 2023

Issue actions