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
integrate 0T workflows for Cosmics and Collisions #30527
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30527/16740
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages: Configuration/AlCa @pgunnell, @chayanit, @wajidalikhan, @christopheralanwest, @tocheng, @cmsbuild, @kpedro88, @tlampen, @pohsun can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
test parameters |
@cmsbuild, please test |
The tests are being triggered in jenkins.
|
## | ||
## Append for 0T conditions | ||
## | ||
import six | ||
from Configuration.StandardSequences.CondDBESSource_cff import GlobalTag as essource | ||
connectionString = essource.connect.value() | ||
ConditionsFor0T = ','.join( ['RunInfo_0T_v1_mc', "RunInfoRcd", connectionString, "", "2020-07-01 12:00:00.000"] ) | ||
GlobalTags0T = {} | ||
for key,val in six.iteritems(autoCond): | ||
if "phase" in key: | ||
GlobalTags0T[key+"_0T"] = (autoCond[key], ConditionsFor0T) | ||
|
||
autoCond.update(GlobalTags0T) | ||
|
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.
Is there a reason that you have included this snippet here rather than in a separate file with a name such as autoCondSpecial.py
or autoCondModifiers.py
, analogous to the treatment of autoCondHLT
and autoCondPhase2
below? Once the additional modifiers to convert the Run-2 HEfail and cosmic GTs to symbolic GTs, they would also be contained in the same file.
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.
no particular reason, can be moved elsewhere if desired. I didn't know about additional use cases and didn't want to clutter the folder with one more 10 lines file.
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.
@christopheralanwest I followed your suggestion and went ahead to created Configuration/AlCa/python/autoCondModifiers.py
. Is that what you had in mind?
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.
Thanks, that's exactly what I had in mind.
+1 |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
Pull request #30527 was updated. @pgunnell, @chayanit, @wajidalikhan, @christopheralanwest, @tocheng, @cmsbuild, @kpedro88, @tlampen, @pohsun can you please check and sign again. |
@cmsbuild please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
+1 |
+upgrade |
+1 |
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. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
PR #30435 highlighted the lack of appropriate testing workflows to check the reconstruction of 0T data (see in particular #30435 (comment) ). As we (Pixel / Tracker) support 0T conditions for both CRUZET (and eventually 0T collisions data, as it might be foreseeable in the scenario of Run-3 startup [*] in which there is a pilot run in 2021) it is important to not introduce bugs in the 0T data reconstruction, which if untested for long time might hit production workflows.
I introduce in this PR, simulation workflows for comics (
wf 7.24
) and collisions (w/o PU ,wf 11634.24
and w/ PU - std mixing,wf 11834.24
) in the 2021 scenario.To achieve this, a new class
UpgradeWorkflow_0T
is introduced inConfiguration/PyReleaseValidation/python/upgradeWorkflowComponents.py
and also several new symbolic global tags (derived from the existingauto:phase*
keys) supporting the 0T case (via appending of the 0T version of theRunInfo
payload).I provide below a comparison of the parmateres for the 0T and 3.8T
RunInfo
payloads:RunInfo_0T_v1_mc
RunInfo_v1_mc
PR validation:
This branch has been tested by running:
if this PR is a backport please specify the original PR and why you need to backport that PR:
[*] link