-
Notifications
You must be signed in to change notification settings - Fork 438
improve forced_response and its documentation #588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Strange that the markov test fails here too. https://github.com/python-control/python-control/pull/588/checks?check_run_id=2188093854#step:5:212 A rerun succeeded. Wonder what triggered the length mismatch of Y and U. |
a09e98c
to
66b381f
Compare
Even without the modifications of this PR, Fixed with a6ea296 TODO: cover the new lines. They were only triggered by the testMarkovResults test depending on the random seed. |
a6ea296
to
77c3b40
Compare
xfail testmarkovResults until #588 is merged
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Seems reasonable to allow a nonzero start time!
return_x
as revealed by control.forced_response argument T #586.Remove redundant kwarg defaults. They are in the call signuature.Numpydoc compliant default indication