Skip to content

allow float precision in result assertions #615

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

Merged
merged 3 commits into from
Apr 29, 2021

Conversation

bnavigator
Copy link
Contributor

@bnavigator bnavigator commented Apr 24, 2021

Fix the current CI with Conda Python 3.9 libraries fail.

@coveralls
Copy link

coveralls commented Apr 24, 2021

Coverage Status

Coverage remained the same at 89.476% when pulling 8a56d67 on bnavigator:py39-float-tests into e81f648 on python-control:master.

@bnavigator bnavigator changed the title allow float precision in test_damp allow float precision in result assertions Apr 24, 2021
@bnavigator
Copy link
Contributor Author

StateSpace matrices are always of dtype float (or complex, if #484 ever gets adopted), so comparing them to integer reference values can have a float precision error.

Not necessarily true for TransferFunction right now, but keep the same logic.

@bnavigator
Copy link
Contributor Author

Merging now, so that other PRs can be checked properly again.

@bnavigator bnavigator merged commit a6a5bee into python-control:master Apr 29, 2021
@murrayrm murrayrm added this to the 0.9.1 milestone Dec 30, 2021
@bnavigator bnavigator deleted the py39-float-tests branch February 18, 2024 20:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants