New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
era-aware T0 data processing setup #13417
era-aware T0 data processing setup #13417
Conversation
…: customizations with Run2 should still be cleaned up
…thods shared with cmsDriver/data processing to the end of the file with a message that they are to be removed in 81X
@cmsbuild please test |
@cmsbuild please test |
The tests are being triggered in jenkins. |
@cmsbuild please test |
The tests are being triggered in jenkins. |
era-aware T0 data processing setup
hello @hengne , |
Added era-based T0 scenarios
The naming convention is to have a suffix matching the era name.
Tested in 800, in particular, by inspection and comparison of the T0 config files generated with Configuration/DataProcessing/test/RunPromptReco.py.
The reco parts in matching old and new scenarios are functionally identical.
There are some relevant discrepancies in L1-related pieces; they are apparently due to missing modifiers in eras
Old scenarios are still in place and will give the same results, but the plan is to remove them at some point in 81X cycle.
@hengne
It should be now also possible to move to eras in the relval matrix for data processing, however for some eras additional customizations are still needed (customisePostEra_Run2_25ns and customisePostEra_Run2_2016 are needed for the 25ns setups)