-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
PUID UL18 backport #32872
PUID UL18 backport #32872
Conversation
A new Pull Request was created by @singh-ramanpreet (Ramanpreet Singh) for CMSSW_10_6_X. It involves the following packages: RecoJets/JetProducers @perrotta, @jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
what is the meaning of the "future" here? There was some discussion about another re-miniAOD, but that was planned to be done in 11_X or later release. It seems like the current proposal for the backport should be using |
test parameters:
|
I thought all the UL campaign will be using
Okay, then is there a need for backport? @alefisico @camclean |
We will need this backport for any future miniAOD campaign. I think here is more important for the next nanoAOD campaign. (That PR will be done asap) |
for 11_2 we need a backport for 10_6 : |
it should be available in the next 10_6_X IB (IIUC, starting from CMSSW_10_6_X_2021-02-11-2300) |
backport of #32418 |
still little idea, - run2_miniAOD_UL.toModify(pileupJetId, algos = _chsalgos_106X_UL17)
+ run2_miniAOD_devel.toModify(pileupJetId, algos = _chsalgos_106X_UL18)
+ (run2_miniAOD_devel & run2_jme_2017).toModify(pileupJetId, algos = _chsalgos_106X_UL17) or addition, run2_miniAOD_UL.toModify(pileupJetId, algos = _chsalgos_106X_UL17)
+ run2_miniAOD_devel.toModify(pileupJetId, algos = _chsalgos_106X_UL18) or just - run2_miniAOD_UL.toModify(pileupJetId, algos = _chsalgos_106X_UL17)
+ run2_miniAOD_devel.toModify(pileupJetId, algos = _chsalgos_106X_UL18) |
run2_miniAOD_UL.toModify(pileupJetId, algos = _chsalgos_106X_UL18) | ||
(run2_miniAOD_UL & run2_jme_2017).toModify(pileupJetId, algos = _chsalgos_106X_UL17) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
run2_miniAOD_UL.toModify(pileupJetId, algos = _chsalgos_106X_UL18) | |
(run2_miniAOD_UL & run2_jme_2017).toModify(pileupJetId, algos = _chsalgos_106X_UL17) | |
run2_miniAOD_UL.toModify(pileupJetId, algos = _chsalgos_106X_UL17) | |
(run2_miniAOD_devel & run2_jme_2018).toModify(pileupJetId, algos = _chsalgos_106X_UL18) |
is what I understood is needed
- the first line reverts back to the current default of the PR
- the second enables the 2018 PU ID for the 2018 "devel" re-miniAOD
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is no run2_jme_2018_cff
, did you mean run2_miniAOD_devel.toModify(pileupJetId, algos = _chsalgos_106X_UL18)
for second line?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my expectation is that my proposed change above when used with --era Run2_2018,run2_miniAOD_devel --procModifiers run2_miniAOD_UL
will give an updated UL re-mini with the 2018 PU ID for the 2018 era/setup. (to compare with the production default --era Run2_2018 --procModifiers run2_miniAOD_UL
which is locked to use PU ID 2017 by the no-change policy due to the 2018 campaign being already in progress)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is no
run2_jme_2018_cff
, did you meanrun2_miniAOD_devel.toModify(pileupJetId, algos = _chsalgos_106X_UL18)
for second line?
Ehm, it may be better that run2_jme_2018
actually existed.
Otherwise, the last line would have (run2_miniAOD_devel & (~run2_jme_2016) & (~run2_jme_2017)).
fixed, only addition is now please review/test. |
@@ -34,6 +35,7 @@ | |||
# residualsTxt = cms.FileInPath("RecoJets/JetProducers/data/download.url") # must be an existing file | |||
) | |||
run2_miniAOD_UL.toModify(pileupJetId, algos = _chsalgos_106X_UL17) | |||
run2_miniAOD_devel.toModify(pileupJetId, algos = _chsalgos_106X_UL18) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
from #32872 (comment)
Ehm, it may be better that run2_jme_2018 actually existed.
Otherwise, the last line would have (run2_miniAOD_devel & (~run2_jme_2016) & (~run2_jme_2017)).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay, somehow I missed this comment. I will push another quick fix.
now it should be in line with comments. please review/test. |
@cmsbuild please test |
-1 Failed Tests: UnitTests RelVals RelVals-INPUT Unit TestsI found errors in the following unit tests: ---> test runtestPhysicsToolsNanoAOD had ERRORS RelVals
Expand to see more relval errors ...RelVals-INPUT
Expand to see more relval errors ...
|
|
Co-authored-by: Slava Krutelyov <[email protected]>
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-8c8b6b/12849/summary.html Comparison SummarySummary:
|
+1
The external files should already be in the IB according to cms-sw/cmsdist@IB/CMSSW_10_6_X_2021-02-07-0000/slc7_amd64_gcc700...IB/CMSSW_10_6_X_2021-02-11-2300/slc7_amd64_gcc700 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_3_X is complete. This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
PR validation:
V05-13-00
). Currently in latest IBCMSSW_10_6_X_2021-02-10-1100
it is still (V5-12-00
) or for testing purposes, use the PR UL18 PU ID training weights AK4CHS cms-data/RecoJets-JetProducers#12Re-miniAOD info
Default for UL campaign will be
UL18
and, forUL17
&UL16
* it will be usingrun2_jme_2017
&run2_jme_2016
* respectively.*(in future)
Code changes
I have kept code changes to minimal since it's a backport, but I can do same level of cleaning as it was done in main PR.
FYI: @alefisico @camclean @marinakolosova