Fix for Loopers identified as primaries#15603
Merged
Merged
Conversation
sawenzel
approved these changes
Jul 16, 2026
sawenzel
left a comment
Collaborator
There was a problem hiding this comment.
Looks correct to me. Maybe as a follow-up we could use a more dedicated encoding (e.g. the gen field) so we don't confuse the loopers' status 2 with genuinely decayed particles?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As reported in https://its.cern.ch/jira/browse/O2-7039, the loopers are identified as physical primaries as they check all the boxes in the isPhysicalPrimary function definition.
By setting the HepMC status to a number != 1 the particle is automatically reported as non-primary, while the transport is insured with the kToBeDone flag, which doesn't depend anymore on the HepMC status. Potentially we could set an entirely different code than 2 to always be able to identify loopers, however I'm not sure how the generators handle that code (as it is set usually from the status code of the generated particle as of now in O2)