Remove Run2 procModifier from Run3 ReMINI relval workflows and fix BTV MINIAOD DQM#48686
Conversation
|
cms-bot internal usage |
|
enable nano |
|
please test |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-48686/45705
|
|
A new Pull Request was created by @hqucms for master. It involves the following packages:
@AdrianoDee, @Moanwar, @antoniovagnerini, @ctarricone, @DickyChant, @miquork, @rseidita, @srimanob, @subirsarkar can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
+1 Size: This PR adds an extra 68KB to repository Comparison SummarySummary:
NANO Comparison SummarySummary:
Nano size comparison Summary:
|
|
+pdmv |
|
+dqm |
|
+Upgrade |
|
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @antoniovilela, @rappoccio, @mandrenguyen, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
PR description:
This PR removes the
run2_miniAOD_UL_preSummer20procModifier, which leaked into the Run3 ReMINI relval workflows (2500.2601,2500.2701) when cloning the relval steps from Run2_UL configs.When fixing this, it revealed an outdated configuration in the BTV MINIAOD DQM, which by default includes the
bTagSVDQMmodule that relies onpfSecondaryVertexTagInfos. However, with the removal of CSVv2 from MINIAOD, thepfSecondaryVertexTagInfoscollection is no longer produced in the MINIAOD step, so thebTagSVDQMmodule would crash.This problem has not been revealed so far because in
bTagMiniDQM_cff.py, theminiAOD_skip_trackExtras(part ofrun2_miniAOD_UL_preSummer20) modifier was used to exclude thebTagSVDQMmodule. However, since the default MINIAOD no longer haspfSecondaryVertexTagInfos, thebTagSVDQMmodule should also be removed in the default configuration too.PR validation:
Tested with
runTheMatrix.py -w nano --ibeos -l 2500.2601,2500.2701.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:
To be backported to 150X.