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 — Relax comparison of floats in tests by bnavigator · Pull Request #818 · python-control/python-control Conversation
Contributor
While trying to fix python-control/Slycot#187 in python-control/Slycot#188, I ran into precision related errors of the control test suite. Seems like the new NumPy moves around some libraries affecting the floats. There are more errors related to the frequency vector calculation of FRDs, which need to be investigated.
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 decreased (-0.01%) to 94.803% when pulling 5352222 on bnavigator:flatsys-float-tests into 2f343be on python-control:main. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Odd that we are still seeing the FRD error and that this only happens in the slycot from source version. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I'm seeing some problems in my own copy of this branch. It looks like using |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
It looks like the problem in the FRD tests had to do with using |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thank you! |
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.
Numpy 1.24 breaks compiling Slycot
There was an error while loading. Please reload this page.