Fixing types for duplicate check #1720
Merged
Conversation
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.
Fixing types for duplicate check to match how they are stored in https://github.com/UCATLAS/xAODAnaHelpers/blob/main/xAODAnaHelpers/EventInfo.h#L37-38 . Without this, the duplicate checker can change the eventNumber when casting it to an int32, which can give false positives on the duplicate check.
This should only affect analyses using
m_checkDuplicatesDataand/orm_checkDuplicatesMC. Duplicate events (real or false positives) are sent to<filename>_duplicates_tree.rootfiles, which can be used to check the impact of this fix.