Skip to content
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

Update PU for Run3 wfs #39041

Merged
merged 6 commits into from Aug 25, 2022
Merged

Update PU for Run3 wfs #39041

merged 6 commits into from Aug 25, 2022

Conversation

kskovpen
Copy link
Contributor

@kskovpen kskovpen commented Aug 11, 2022

PR description:

Update MinBias datasets for 2021, 2023, 2024, and 2021FS Run3 PU wfs, following the discussion in #38760.

PR validation:

Tested on 11834.0,12634.0,13034.0,13434.0,12234.0

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:

Not a backport.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39041/31527

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @kskovpen for master.

It involves the following packages:

  • Configuration/PyReleaseValidation (pdmv, upgrade)

@jordan-martins, @bbilin, @cmsbuild, @AdrianoDee, @srimanob, @kskovpen can you please review it and eventually sign? Thanks.
@makortel, @kpedro88, @fabiocos, @Martin-Grunewald, @missirol, @trtomei, @beaucero, @slomeo this is something you requested to watch as well.
@perrotta, @dpiparo, @qliphy, @rappoccio you are the release manager for this.

cms-bot commands are listed here

@kskovpen
Copy link
Contributor Author

test parameters:

  • workflow = 11834.0,12634.0,13034.0

@kskovpen
Copy link
Contributor Author

please test

@cmsbuild
Copy link
Contributor

-1

Failed Tests: RelVals-INPUT
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ca1e69/26774/summary.html
COMMIT: 860d91e
CMSSW: CMSSW_12_5_X_2022-08-11-1100/el8_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/39041/26774/install.sh to create a dev area with all the needed externals and cmssw changes.

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:

You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ca1e69/26774/git-recent-commits.json
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ca1e69/26774/git-merge-result

  • DAS Queries: The DAS query tests failed, see the summary page for details.

RelVals-INPUT

  • 11601.0DAS Error
  • 11602.0DAS Error
  • 11603.0DAS Error
Expand to see more relval errors ...
  • 11604.0
  • 11605.0
  • 11606.0
  • 11630.0
  • 11725.0
  • 11925.0

Comparison Summary

Summary:

  • You potentially added 235 lines to the logs
  • ROOTFileChecks: Some differences in event products or their sizes found
  • Reco comparison results: 9336 differences found in the comparisons
  • DQMHistoTests: Total files compared: 53
  • DQMHistoTests: Total histograms compared: 4016058
  • DQMHistoTests: Total failures: 23138
  • DQMHistoTests: Total nulls: 4
  • DQMHistoTests: Total successes: 3992894
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 3.4220000000000006 KiB( 52 files compared)
  • DQMHistoSizes: changed ( 11834.0 ): 3.900 KiB SiStrip/MechanicalView
  • DQMHistoSizes: changed ( 12634.0 ): 0.811 KiB SiStrip/MechanicalView
  • DQMHistoSizes: changed ( 13034.0 ): -1.289 KiB SiStrip/MechanicalView
  • Checked 220 log files, 59 edm output root files, 53 DQM output files
  • TriggerResults: found differences in 4 / 52 workflows

@srimanob
Copy link
Contributor

@kskovpen
How do you plan for FastSim? Thanks.

@@ -3710,11 +3710,11 @@ def gen2021HiMix(fragment,howMuch):
defaultDataSets['2017Design']='CMSSW_12_0_0_pre4-113X_mc2017_design_v5-v'
defaultDataSets['2018']='CMSSW_12_0_0_pre4-113X_upgrade2018_realistic_v5-v'
defaultDataSets['2018Design']='CMSSW_12_0_0_pre4-113X_upgrade2018_design_v5-v'
defaultDataSets['2021']='CMSSW_12_0_0_pre4-120X_mcRun3_2021_realistic_v2-v'
defaultDataSets['2021']='CMSSW_12_5_0_pre4-124X_mcRun3_2022_realistic_v10-v'
Copy link
Contributor

@mmusich mmusich Aug 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @kskovpen let me understand.
Are these samples done using the vtx smearing as of #38760 ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They use Run3RoundOptics25ns13TeVLowSigmaZ

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am confused then.
What's the point of updating them?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we use Realistic25ns13p6TeVEarly2022Collision?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, Run3RoundOptics25ns13TeVLowSigmaZ is the current vtx smearing while Realistic25ns13p6TeVEarly2022Collision will be the new one.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, Marco

@kskovpen
Copy link
Contributor Author

@kskovpen
How do you plan for FastSim? Thanks.

It's coming.

@srimanob
Copy link
Contributor

srimanob commented Aug 12, 2022

@kskovpen
How do you plan for FastSim? Thanks.

It's coming.

Thanks. To confirm the cmsDriver with CMSSW_12_5_0_pre4, it should come from
runTheMatrix.py --what upgrade -l 13240.303 --command="--beamspot Realistic25ns13p6TeVEarly2022Collision" --wm init

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39041/31543

@kskovpen
Copy link
Contributor Author

The inputs for the failing wfs are now being reproduced in the newly submitted wfs. Thanks to @srimanob for additional suggestions. Let's retrigger the tests tomorrow to see if anything of these new inputs can fix the failures.

@kskovpen
Copy link
Contributor Author

please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ca1e69/27065/summary.html
COMMIT: bcf184a
CMSSW: CMSSW_12_5_X_2022-08-24-1100/el8_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/39041/27065/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 3149 differences found in the comparisons
  • DQMHistoTests: Total files compared: 51
  • DQMHistoTests: Total histograms compared: 3693084
  • DQMHistoTests: Total failures: 36621
  • DQMHistoTests: Total nulls: 1
  • DQMHistoTests: Total successes: 3656440
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 1.983 KiB( 50 files compared)
  • DQMHistoSizes: changed ( 11834.0 ): 1.979 KiB SiStrip/MechanicalView
  • DQMHistoSizes: changed ( 312.0 ): 0.004 KiB MessageLogger/Warnings
  • Checked 212 log files, 49 edm output root files, 51 DQM output files
  • TriggerResults: found differences in 2 / 50 workflows

@srimanob
Copy link
Contributor

srimanob commented Aug 25, 2022

+Upgrade

All updated workflows run. The histogram differences come from Run-3 PU workflows (11834.0, 13434.0) where the GS (old BS simulation) is mixed with (new BS) PU in this PR. This is expected. I don't think we need to trigger the test with #38760 but as prefer. FYI @mmusich

This PR should be merged together with #38760.

@srimanob
Copy link
Contributor

Hi @kskovpen
Thanks for all efforts of submission. Would you mind to re-submit 11725.0 with 1 core? The output can be v2, we can overwrite the version later in the code. This can come in the follow up PR. Thanks.

@kskovpen
Copy link
Contributor Author

11725.0

Thanks a lot @srimanob. This workflow has been resubmitted.

@kskovpen
Copy link
Contributor Author

+pdmv

Maybe a question to @smuzaffar. Do you know whether the accessed datasets in IBs are additionally copied somewhere safe? Asking this because normally there is a limited lifetime defined for the relval output datasets stored on EOS.

@cmsbuild
Copy link
Contributor

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)

@smuzaffar
Copy link
Contributor

+pdmv

Maybe a question to @smuzaffar. Do you know whether the accessed datasets in IBs are additionally copied somewhere safe? Asking this because normally there is a limited lifetime defined for the relval output datasets stored on EOS.

@kskovpen , yes the dataset files opened during PR/IB tests are backed up under /eos/cms/store/user/cmsbuild/store. Note that during PR/IB tests we only process a small number of events, so we do not backup the full dataset but only keep the root files which were actually opened during PR/IB tests.

@kskovpen
Copy link
Contributor Author

Thanks @smuzaffar

@perrotta
Copy link
Contributor

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants