-
Notifications
You must be signed in to change notification settings - Fork 166
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
refactor: Remove forceIntersectBoundaries
from Navigator
#3238
refactor: Remove forceIntersectBoundaries
from Navigator
#3238
Conversation
📊: Physics performance monitoring for 1a4642bphysmon summary
|
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.
If its green, it seems to work. Only the comments in the affected section may need to be rethought...
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.
A wait but there are some physmon differences...
I suspect that these are coming from the simulation and the low stats in ttbar. I can try to validate this with higher stats or look at a case where it changes |
…ator-forceIntersectBoundaries
Invalidated by push of 9416724
If the CI passes, and we understand the differences in the output, then it is fine. |
@noemina I investigated the propagation errors a bit and I think I have a solution with the 3 PRs in combination |
Quality Gate passedIssues Measures |
closing in favor of #3437 |
This is an attempt to drop a
Navigator
hotfix from the past assuming that it has been fixed by one of theNavigator
refactors.blocked by