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
Move 2015/2016 Data ReReco ZeroBias RelVals to use @rerecoZeroBias DQM sequence #27727
Move 2015/2016 Data ReReco ZeroBias RelVals to use @rerecoZeroBias DQM sequence #27727
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27727/11350
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages: Configuration/PyReleaseValidation @cmsbuild, @andrius-k, @kmaeshima, @zhenhu, @schneiml, @prebello, @kpedro88, @pgunnell, @jfernan2, @fioriNTU can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test workflow 134.710,134.812,134.912,136.732,136.745,136.756,136.767,136.778 |
The tests are being triggered in jenkins. |
ok no problem thank you @fioriNTU |
@prebello no need for the moment. I will update the PR in a few minutes, once my local tests complete, and the tests will need to be relaunched in any case. |
Comparison job queued. |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
@jfernan2
things look in good order to me, a screenshot as an example: |
+1 |
+1 |
+1 |
merge |
+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 be automatically merged. |
PR description:
This PR completes the effort started in PR #27415 to move the Data ReReco ZeroBias RelVal workflows to use the
@rerecoZeroBias
DQM sequence.As a reminder this is done in order to test the sequence that is actually run at Tier-0 during physics certification and spot beforehand possible issues affecting production.
In #27415 it was not directly possible to activate the changes in the 2015 / 2016 workflows (already prepared), because they would have failed with the error reported in #27415 (comment):
It turns out that this error is due to the fact that with the current definition of the
rerecoZeroBias
sequence, the sequencedqmHarvestingExtraHLT
which runs theDQMOffline_Certification
cmssw/Configuration/StandardSequences/python/Harvesting_cff.py
Line 16 in e43377b
which is defined as
cmssw/DQMOffline/Configuration/python/DQMOffline_Certification_cff.py
Line 9 in 50022b6
which in turn contains
sipixelCertification
cmssw/DQMOffline/Configuration/python/DQMOffline_CRT_cff.py
Line 17 in 02d4198
is put into the
cms.schedule
execution before the actual execution of the Pixel harvesting step, resulting into looking for an histogram which is not yet created.N.B.: Resolving the
@rerecoZeroBias
harvesting sequence into its actual sub-sequences solves the issue, but I am not sure it's the most elegant way of doing it. Suggestion are welcome.PR validation:
Run the standard battery of tests for the workflows which have been changed:
which passed without issues.
if this PR is a backport please specify the original PR:
This is not a backport, though a backport might be needed for the actual 2016 Ultra-Legacy reprocessing.
cc:
@jandrea @arossi83