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 — Rebased #431: Default dt is 0 by bnavigator · Pull Request #490 · python-control/python-control Conversation…" from python-control#438 This reverts commit 2b98769. …re that combines systems with different timebases …s default system timebase …tems, refactored __init__ on both to use it
This was
linked to
issues
Closed
|
There was an error while loading. Please reload this page.
|
Coverage increased (+0.3%) to 87.52% when pulling 75f3aef on bnavigator:rebase-pr431 into 6ed3f74 on python-control:master. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
d83ade4 to
8b82850
Compare
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I look through the changes and these look good to me.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| TransferFunction.__add__(tsys.siso_tf1c, tsys.siso_tf1d) | ||
| with pytest.raises(ValueError): | ||
| TransferFunction.__add__(tsys.siso_tf1d, tsys.siso_tf2d) | ||
| with pytest.raises(ValueError): |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I assume these are removed because these tests are already performed above in eg ‘test_timenase_conversion’?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
They don't raise an error anymore. You had an equivalent change in #431. dt=0.1 and dt=True are compatible now.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I see, makes sense!
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| try: | ||
| dt = args[0].dt | ||
| except NameError: # pragma: no coverage | ||
| except AttributeError: |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
🤙
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Added one more simple test in order to not uncover a line. The double dt resolver is documented behavior and thus should be checked. |
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.
use dt=0 instead of dt=None (unspecified timebase) as default option for lti systems? Problem with DT State-Space Response Bugs in InterconnectedSystem: different dt's [fixed] and non-proper TFs [open]
There was an error while loading. Please reload this page.