GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — allow arrays of step, impulse responses for LTI systems · Issue #512 · python-control/python-control

allow arrays of step, impulse responses for LTI systems #512

New issue
Copy link
New issue
Copy link
Closed
#514
Closed
allow arrays of step, impulse responses for LTI systems#512
#514
Copy link
Assignees
murrayrm
Milestone
0.9.0

Description

@murrayrm
murrayrm
opened on Jan 17, 2021
Issue body actions

The current implementation of step and impulse responses for MIMO systems requires the specification of an input channel, so that you always get a SIMO (or SISO) time response. As pointed out in #453, this is not symmetric with the frequency responses, where you can index the input and output channels. There is no reason this couldn't be done consistently for step and impulse responses by just iterating over the set of all input channels. This would help make time and frequency responses more consistent.

Note that one inconsistency will remain: when you compute a forced response, you have to specify the particular input. So in that case you can't index the input channel, only the output channel.

Activity

  1. sawyerbfuller commented on Jan 18, 2021

    @sawyerbfuller
    sawyerbfuller
    on Jan 18, 2021 via email
    Contributor
    More actions
    Agree about consistency argument. If input=None , could just return eg step response to each input on a separate “row”. Could do the same with forced response too, though specified input u data is more likely in that function to be only of interest for the specified input # (eg aileron vs throttle will have much different magnitudes).
  2. murrayrm
    self-assigned this
    on Jan 18, 2021
  3. murrayrm commented on Jan 18, 2021

    @murrayrm
    murrayrm
    on Jan 18, 2021
    MemberAuthor
    More actions

    I have coded up this change, including input=None handling (separate row for each input). Just waiting on merge of #511 before sending a PR.

    This change breaks some of the unit test code that was implicitly assuming that input=None would select the first input. But changes are minor and everything is pretty much backward compatible. I suggest we implement this change into 0.9.0, though, since it may require modification of user code.

    Reacted by Sawyer Fuller
  4. murrayrm
    added this to the 0.9.0 milestone on Jan 18, 2021
  5. murrayrm
    linked a pull request that will close this issueMIMO impulse and step response #514on Jan 19, 2021
  6. murrayrm
    closed this as completedin #514on Jan 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @murrayrm
    murrayrm

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    • 0.9.0

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.