GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||
GeezerVison is showing github.com — add capability to switch to legacy defaults by sawyerbfuller · Pull Request #424 · python-control/python-control Conversation
Contributor
For example,
I added a few more defaults that might change in the future, but left them as they currently are for this PR:
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
|
There was an error while loading. Please reload this page.
|
Coverage increased (+0.02%) to 84.215% when pulling 68c7ea6 on sawyerbfuller:legacy-defaults into a9d869e on python-control:master. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Changes look good. I think the docstrings for the various functions need to be updated to indicate the default values come from config variables. We should also add the new variables to the documentation in |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…ng new config parameters default_dt and remove_useless_states
|
Looks ready to merge. Will let sit for a few days in case others want to comment. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.