Phase 2 GTT fix off-by-one error and collection mismatch in L1TrackObjectNtupleMaker #1234
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.
Edit note: this is not time-critical, and can be deferred as needed according to AR timeline (but this is adjacent to everything outside the GTT ntuples)
Phase 2 GTT fix off-by-one error and collection mismatch in L1TrackObjectNtupleMaker
PR description:
This PR addresses a bug in the L1TrackObjectNtupleMaker for GTT ntuple production (being deprecated in favor of L1Nano, but submitted for posterity), which cross-linked the wrong track indices for the various GTT selected collections.
PR validation:
scram b code-checks
scram b code-format
scram b
cmsRun L1TrackObjectNtupleMaker_cfg.py
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
This will require a forward-port to master as well