-
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
add GPU RelVals using 2023 HLT menu #41354
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41354/35194
|
A new Pull Request was created by @missirol (Marino Missiroli) for master. It involves the following packages:
@bbilin, @cmsbuild, @AdrianoDee, @srimanob, @kskovpen, @sunilUIET can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
test parameters:
|
@fwyzard, could you please review this PR? (I don't know these wfs well) |
# Patatrack ECAL-only: RunJetMET2022D on GPU (optional) | ||
# Patatrack HCAL-only: RunJetMET2022D on GPU (optional) | ||
|
||
workflows[140.065502] = ['Run3-2023_JetMET2022D_RecoPixelOnlyGPU',['RunJetMET2022D','HLTDR3_2023','RECODR3_reHLT_Patatrack_PixelOnlyGPU','HARVESTRUN3_pixelTrackingOnly']] |
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 would use triplets by default for 2023, so 140.065506
?
@@ -494,6 +494,11 @@ | |||
workflows[140.068] = ['',['RunTau2022D','HLTDR3_2023','RECONANORUN3_reHLT','HARVESTRUN3']] | |||
workflows[140.069] = ['',['RunMuonEG2022D','HLTDR3_2023','RECONANORUN3_reHLT','HARVESTRUN3']] | |||
|
|||
### run3-2023 (2022 data) - Pixel-only, ECAL-only and HCAL-only | |||
workflows[140.065501] = ['Run3-2023_JetMET2022D_RecoPixelOnlyCPU',['RunJetMET2022D','HLTDR3_2023','RECODR3_reHLT_Patatrack_PixelOnlyCPU','HARVESTRUN3_pixelTrackingOnly']] |
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 would use triplets by default for 2023, so 140.065505
?
please test |
From looking at the diff, the changes seem OK. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-1a45e3/32011/summary.html Comparison SummarySummary:
GPU Comparison SummarySummary:
|
From the test results we can see that the gpu workflow did run on a gpu. |
f8f5e37
to
4458799
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41354/35214
|
Pull request #41354 was updated. @bbilin, @cmsbuild, @AdrianoDee, @srimanob, @kskovpen, @sunilUIET can you please check and sign again. |
please test The latest push contains a minor update to |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-1a45e3/32026/summary.html Comparison SummarySummary:
GPU Comparison SummarySummary:
|
I've run the data workflows from latest version of this PR, and compared the
Looks good to me. |
+pdmv |
@AdrianoDee @srimanob , could you please review this PR and its backport (#41371) ? |
+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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
After merging this PR, six of the new workflows [*] failed in the IB The IB error is the same for all 6 wfs ("DAS-Err"). Clicking on the "1" next to DAS-Err, one sees a DAS query [2] that returns 0 results. Those workflows passed during the PR tests (e.g. here). I'm no expert, but it looks like
I think the issue is that the GEN-SIM sample [3] does not exist [4]. @cms-sw/pdmv-l2, could/should [3] be produced? (if it wasn't already) @cms-sw/orp-l2, should I disable [1] in [1] [2] [3] [4] Looking [3] up on the DAS webpage returns a 'dummy' entry with
I see the same 'dummy' entry if I put a random string ( |
#41386 removes the 6 problematic wfs from the list of GPU RelVals. |
PR description:
This PR is an attempt to add GPU RelVals making use of the 2023 HLT menu. The goal is to have wfs that run the latest HLT pp menu for 2023 on machines with a GPU.
Workflows are added for both MC and data (using data from 2022), trying to follow the structure of the existing GPU RelVals.
The next step would be to change the default GPU wfs in PR tests (here) to use 2023 ones.
PR validation:
Some of the added workflows pass locally.
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:
If approved, it should be backported to
CMSSW_13_0_X
.