-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Introduce relval worflow for beam-halo in 2018 and post-LS2 detector configuration #26510
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-26510/9373
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages: Configuration/PyReleaseValidation @pgunnell, @zhenhu, @prebello, @cmsbuild, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test workflow 8.20 |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready There are some workflows for which there are errors in the baseline: @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
Comparison job queued. |
Comparison is ready 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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
@kpedro88 I have seen now that it has still string 19 instead of 21. It should be changed to match the new policy for Run3 relvals. |
@prebello in CMSSW we develop against master. The change from 19 to 21 has not entered master yet. If it enters before this PR, then this PR will be rebased accordingly. If this PR enters first, the other PR will be rebased to propagate the change. |
+1 |
PR description:
As there is renewed interest within the Tracker DPG about using Beam Halo tracks for tracker alignment purposes during Run 3, and we currently have only a configuration from run1 in the matrix, we would like to propose an updated version using the 2018 detector (which at least features the phase-1 pixel detector) and the post-LS2 (2019 at the moment).
I profit of this PR to add also a workflow for post-LS2 cosmics production.
Notice, though, that at the moment the GT used for the post-LS2 workflows are still the collisions one, since the post-LS2 cosmics GT is missing (see request at: https://hypernews.cern.ch/HyperNews/CMS/get/calibrations/4124.html )
As the cosmics digitization for Run3 is not working at the moment due to missing castor SimHits I also fix that by adding a modifier for the comics workflow (apparently left-over in commit 0b1663f)
PR validation:
within
CMSSW_10_6_X_2019-04-23-1100
the command:run to completion, producing 10 events in
RECO
data-tier.if this PR is a backport please specify the original PR:
This is not a backport
@mtosi @adewit @connorpa