-
Notifications
You must be signed in to change notification settings - Fork 31
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
Always check for finite x0 #1955
Conversation
Initial states should always be checked for finite values, not only with `Model.setAlwaysCheckFinite(True)`. As this only happens once per simulation, the overhead is negligible. Closes #1952
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #1955 +/- ##
===========================================
+ Coverage 75.96% 76.01% +0.04%
===========================================
Files 76 76
Lines 12981 13015 +34
===========================================
+ Hits 9861 9893 +32
- Misses 3120 3122 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
|
this is an abysmal pain to look at, can we separate clang formats from actual changes? |
oops. didn't notice there was so much. I'll just clang-format everything later, then that issue should be solved for the near future. |
This reverts commit a09c4d1.
Kudos, SonarCloud Quality Gate passed! |
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.
👍
Initial states should always be checked for finite values, not only with
Model.setAlwaysCheckFinite(True)
. As this only happens once per simulation, the overhead is negligible.Closes #1952