Skip to content

control.forced_response argument T #586

Closed

Description

@forgi86

In version 0.9:

  • For a discrete-time system , the time vector should be optional in the forced response (as stated in the documentation).
    However, this code does not work for me:

sys = control.drss(states=1, outputs=1, inputs=1)
u = np.random.randn(1000)
control.forced_response(sys, U=u)

  • Also, the default value of return_x is stated to be True in the docstring, but it is None (False?) in the code.

Activity

  1. bnavigator commented on Mar 24, 2021

    @bnavigator
    Contributor
    • For a discrete-time system , the time vector should be optional in the forced response (as stated in the documentation).

    Automatic timevector calculation only works if the sys has dt specified. Should be stated more explicitly in the documentation and a better error message should be provided.

    Plus, there is a bug in drss. It should return a system with dt=True, but the returned system has dt=0.

    • Also, the default value of return_x is stated to be True in the docstring, but it is None (False?) in the code.

    Agreed, this is a bug an error in the documentation. Since 0.9.0 the default value of config.defaults['forced_response.return_x'] is False.

  2. self-assigned this
    on Mar 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions