-
Notifications
You must be signed in to change notification settings - Fork 173
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!: Fix vertex finding for seeds with z=0
#2917
Conversation
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.
Looks reasonable to me
Invalidated by push of 9d85a36
📊: Physics performance monitoring for bf674c6physmon 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.
Very good idea; I don't know why we did this but I am guessing that it is a relict from athena.
- Do you know why the physmon changes for the IVF? I don't see why it should
- Is this breaking because of the (very sensible) renaming?
I am also a bit puzzled about the performance changes in the IVF. I can try to track it down Yeah I think flagging as breaking makes a lot of sense here |
z=0
z=0
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2917 +/- ##
=======================================
Coverage 48.78% 48.78%
=======================================
Files 493 493
Lines 28911 28905 -6
Branches 13749 13747 -2
=======================================
- Hits 14104 14102 -2
+ Misses 4913 4911 -2
+ Partials 9894 9892 -2 ☔ View full report in Codecov by Sentry. |
the physmon regression is actually coming from an existing problem. if a single propagation during vertex fitting fails the whole event will have 0 vertices. the propagation to the perigee is not stable as the distance estimate can be quite a bit off and our overstepping tolerance will ruin the propagation. this happens more frequently than before because more vertices are reconstructed I added a fix here #2930 |
The AMVF config `addSingleTrackVertices` was not correctly applied in the finding process and endet up always being `true`. This PR fixes the behavior. discovered in #2917
The AMVF config `addSingleTrackVertices` was not correctly applied in the finding process and endet up always being `true`. This PR fixes the behavior. discovered in acts-project#2917
blocked by the vertexing refactor atm |
cddd364
to
afc6698
Compare
I decoupled this one now from #2930 and pulled the vertex refactor changes in. Ready to go from my side |
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.
Seems reasonable, I only have nitpicks.
Output change is likely due to extra vertices being found?
Core/include/Acts/Vertexing/AdaptiveGridDensityVertexFinder.ipp
Outdated
Show resolved
Hide resolved
Co-authored-by: Paul Gessinger <hello@paulgessinger.com>
)" This reverts commit 123746c.
)" This reverts commit 123746c.
This PR changes Athena outputs |
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.
The code shuffle here might have unexpected effects. I will revert and see if that is it.
Otherwise I can only suspect that the number of vertices is changing. If so I would think it is a bug fix but we have to check the plots.
)" This reverts commit 123746c.
…roject#2917)"" This reverts commit dbdc5a3.
#3002 will hopefully resolve this |
…ts-project#2917 (acts-project#3002) In acts-project#2917 I changed the way how "no more seeds" is communicated in our vertexing code but forgot to wire this for the `TrackDensityVertexFinder` correctly.
This fixes another case where the overstepping tolerance bites us from behind. Perigee surfaces are prone to the issue of bad path length estimation so we need a special treatment. discovered in #2917
…ject#2930) This fixes another case where the overstepping tolerance bites us from behind. Perigee surfaces are prone to the issue of bad path length estimation so we need a special treatment. discovered in acts-project#2917
The AMVF config `addSingleTrackVertices` was not correctly applied in the finding process and endet up always being `true`. This PR fixes the behavior. discovered in acts-project#2917
While working on the 4D vertexing performance I realized that our vertex finders will abort if a seed with `z=0` is found. This can happen using a grid based seeder as it can round to exactly 0. As far as I could see the vertex constraint was only used to signal the finish line for the vertex finding. I exchanged that with an optional and also removed the vector which had no use as far as I could tell
…ts-project#2917 (acts-project#3002) In acts-project#2917 I changed the way how "no more seeds" is communicated in our vertexing code but forgot to wire this for the `TrackDensityVertexFinder` correctly.
…ject#2930) This fixes another case where the overstepping tolerance bites us from behind. Perigee surfaces are prone to the issue of bad path length estimation so we need a special treatment. discovered in acts-project#2917
The AMVF config `addSingleTrackVertices` was not correctly applied in the finding process and endet up always being `true`. This PR fixes the behavior. discovered in acts-project#2917
While working on the 4D vertexing performance I realized that our vertex finders will abort if a seed with `z=0` is found. This can happen using a grid based seeder as it can round to exactly 0. As far as I could see the vertex constraint was only used to signal the finish line for the vertex finding. I exchanged that with an optional and also removed the vector which had no use as far as I could tell
…ts-project#2917 (acts-project#3002) In acts-project#2917 I changed the way how "no more seeds" is communicated in our vertexing code but forgot to wire this for the `TrackDensityVertexFinder` correctly.
…ject#2930) This fixes another case where the overstepping tolerance bites us from behind. Perigee surfaces are prone to the issue of bad path length estimation so we need a special treatment. discovered in acts-project#2917
While working on the 4D vertexing performance I realized that our vertex finders will abort if a seed with
z=0
is found. This can happen using a grid based seeder as it can round to exactly 0.As far as I could see the vertex constraint was only used to signal the finish line for the vertex finding. I exchanged that with an optional and also removed the vector which had no use as far as I could tell