-
Notifications
You must be signed in to change notification settings - Fork 178
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: ParticleID collision in Geant4 #2039
fix: ParticleID collision in Geant4 #2039
Conversation
tagging @Corentin-Allaire as this might impact the ambi performance eval? |
Codecov Report
@@ Coverage Diff @@
## main #2039 +/- ##
=======================================
Coverage 49.83% 49.83%
=======================================
Files 420 420
Lines 23962 23962
Branches 10859 10859
=======================================
Hits 11942 11942
Misses 4390 4390
Partials 7630 7630 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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 good from my side
I wonder if we can optimize the barcode or the utilization of the barcode in the G4 translation so we avoid overflows for ttbar
It definitely could affect it, if we have multiple track with the same id then one of them will be treated as a duplicate |
📊 Physics performance monitoring for 411a5e6Full report VertexingSeedingCKFAmbiguity resolutionTruth tracking (Kalman Filter)Truth tracking (GSF) |
Actually there are quite a lot of collisions in one event:
|
That number seems a bit too high, for how many event is that ? |
I dont actually know but it might be plausible considering all the secondary particles? I once use G4 with 100 muon event and got like 10k secondaries |
Its for one event, but without post selection. And probably you need to divide this number by two, because right now it counts initial and final particles. |
I just run the job with the default selector and I see 0 overlap so this probably doesn't change much in the end ? |
Sure, if we can change the barcode behaviour to be safe against this, let's do it! |
Can you specify what this means? Which particles are disregarded? |
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 turning this around so quickly 👍
looks good - just two questions
Examples/Algorithms/Geant4/include/ActsExamples/Geant4/EventStoreRegistry.hpp
Show resolved
Hide resolved
Finally, I have some plots @asalzburger |
@benjaminhuth - can you fix the format, please ? |
Yeah and I need to do some clean-up still |
@asalzburger The CI should run through now, could you reapprove? |
This attempts to fix particle collisions in Geant4. These occur I think when the bits in the `ActsFatras::Barcode` are not enough to capture all results. This way it could happen that multiple particles where associated with a single ID:  I think the correct fix for this to check for collision and ignoring particles that collide. Furthermore, the barcode generation is improved, so that collisions should happen less frequently. Since this happens quite frequently with default settings for Geant4+Pythia8(ttbar), I think all so far generated events using this configuration are suffering from this problem
This attempts to fix particle collisions in Geant4. These occur I think when the bits in the
ActsFatras::Barcode
are not enough to capture all results. This way it could happen that multiple particles where associated with a single ID:I think the correct fix for this to check for collision and ignoring particles that collide. Furthermore, the barcode generation is improved, so that collisions should happen less frequently.
Since this happens quite frequently with default settings for Geant4+Pythia8(ttbar), I think all so far generated events using this configuration are suffering from this problem