You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Activity
bnavigator commentedon Mar 24, 2021
Automatic timevector calculation only works if the sys has
dtspecified.Should be stated more explicitly in the documentation anda better error message should be provided.Plus, there is a bug in
drss. It should return a system withdt=True, but the returned system hasdt=0.Agreed, this is
a bugan error in the documentation. Since 0.9.0 the default value ofconfig.defaults['forced_response.return_x']isFalse.