-
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
Reorganize FastSim Run3 workflow #38660
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38660/30947
|
A new Pull Request was created by @srimanob (Phat Srimanobhas) for master. It involves the following packages:
@jordan-martins, @bbilin, @cmsbuild, @AdrianoDee, @srimanob, @kskovpen can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
test parameters:
|
@cmsbuild please test |
@srimanob have you |
Hi @kpedro88 It shows that previous |
FYI @sbein |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-53c47c/26090/summary.html Comparison Summary@slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38660/30951
|
+1 |
+Upgrade Presented in the SIM meeting, https://indico.cern.ch/event/1182398/ |
@cms-sw/pdmv-l2 |
Thanks a lot for all the updates @srimanob . I wonder if jenkins tests would catch all the existing wfs that could be potentially touched by these changes (I haven't seen any problems). Otherwise, it is fine with us. |
Hi @kskovpen Yes, this PR covers FastSim NoPU, FastSim PU, and MinBias PU creation (13234.0,13434.0,13240.303). And they will be part of IB test. The PR test after merging this PR will cover FastSim NoPU and FastSim PU. |
+pdmv |
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. @perrotta, @dpiparo, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
@perrotta @qliphy The plan is to merge this PR first. Let's IB done, and see nothing wrong. Then I will rebase #38736 to support MiniAOD and NanoAOD DQM, and some structure change for FastSim. |
'GT' : 'auto:phase1_2022_realistic', | ||
'HLTmenu': '@relval2022', | ||
'Era' : 'Run3_FastSim', | ||
'BeamSpot': 'Run3RoundOptics25ns13TeVLowSigmaZ', |
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 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.
I am fine with both options. maybe @perrotta has preference?
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.
Hi @qliphy
As those PR is still in progress. I prefer to merge this first. The next PR will come in 2-3 days. Thanks.
Anything that stops to merge this PR? |
+1
|
PR description:
This PR is to reorganize the Run3 FastSim workflow.
Before:
To be done:
Comments are welcomed.
PR validation:
Running with configs out from the following runTheMatrix:
runTheMatrix.py --what upgrade -l 13234.0,13434.0,13240.303 --wm init
Comparison of workflow list can be done with
diff /afs/cern.ch/user/s/srimanob/public/ForFastSim/runTheMatrix_original.log /afs/cern.ch/user/s/srimanob/public/ForFastSim/runTheMatrix_withPR_v2.log
It shows that previous
.301, .302, .303
are removed, and new workflows are added, started from13200.
.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:
No need of backport.