TLRs for run2 data processing configurations (start from CSC) #4396
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.
RecoTLR.py functions to modify the prompt and express processing for run2 detector.
These come with new DataProcessing scenarios (based on config builder pp and cosmics scenarios).
Aiming for July global runs.
Can be tested by calling the regular T0 cmsDriver versions of these (see e.g. 1000.0 or 1001.0)
Configuration/DataProcessing/RecoTLR.customisePromptRun1
andConfiguration/DataProcessing/RecoTLR.customiseExpressRun2
for pp orConfiguration/DataProcessing/RecoTLR.customiseCosmicDataRun2
for cosmics.Tested on ~50K events from a local CSC runs.
Taking 221766 as an example, fairly high level reco returns decent results