Add run2_HE2017 to 2017 special tracking eras #15495
Merged
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.
This PR adds the
run2_HE_2017
sub-era toRun2_2017_trackingPhase1PU70
andRun2_2017_trackingRun2
eras following its existence inRun2_2017
era (which I noticed in #15469 (comment)).Tested in CMSSW_8_1_X_2016-08-16-2300. There should be no effect in standard phase0/1/2 workflows. I guess in principle the special workflows
10024.[23]
(employingRun2_2017_trackingRun2
era) could be affected via jetCore iteration, but with 10 events in runTheMatrix I saw no differences.@rovere @VinInn