MIMO impulse and step response #514
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements MIMO impulse and step responses, mirroring the style and functionality of frequency response functions for MIMO systems. It resolves issue #512 and is consistent with the discussion issue #453. Specifically:
step_response
orimpulse_response
will generate an array of responses (indexed by output, input, and time).squeeze=True
keyword.squeeze=False
keyword.Note that the response for
initial_response
andforced_response
is not indexed by the input (since there is no input in one case and a specifically applied input in the other). The processing of thesqueeze
keyword is the same: by default SISO systems will be returned without the output axis, usesqueeze=True
to remove single dimensional axes from MIMO systems, usesqueeze=False
to force SISO systems to be treated like MIMO systems.Other (small changes):
transpose
keyword was working: it changed [output, input, time] to [time, input, output] instead of [time, output, input]. This was caught when adding unit tests.