-
Notifications
You must be signed in to change notification settings - Fork 47
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
Fix pypesto.profile.parameter_profile incorrectly assuming symmetric bounds #1166
Conversation
…bounds Use the correct bounds for checking whether we are done computing the profile. Add test. Closes #1165
Codecov Report
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. @@ Coverage Diff @@
## develop #1166 +/- ##
============================================
- Coverage 88.16% 53.37% -34.80%
============================================
Files 79 148 +69
Lines 5257 11653 +6396
============================================
+ Hits 4635 6220 +1585
- Misses 622 5433 +4811
|
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.
Thanks for noticing 👍🏼
) or (current_profile.ratio_path[-1] < options.ratio_min) | ||
raise AssertionError("par_direction must be -1 or 1") | ||
if not options.whole_path: | ||
stop_profile |= current_profile.ratio_path[-1] < options.ratio_min |
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.
not entirely sure why not an = but should be fine.
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.
Because it's stop_due_to_bounds or stop_due_to_ratio
, just =
would ignore the stop_due_to_bounds
part.
Use the correct bounds for checking whether we are done computing the profile.
Add test.
Closes #1165