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

Rename candidate GTs to use official names and update alcareco trigger bits #28804

Merged
merged 2 commits into from Jan 29, 2020

Conversation

christopheralanwest
Copy link
Contributor

PR description:

PR #28762 was accidentally approved and merged prior to renaming the GTs to follow the usual convention for official GTs. The string "Candidate" indicates a test GT, which could cause confusion, so this PR simply renames the global tags. The GT diffs below demonstrate that there is no change to the tag content to any of the GTs.

https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mcRun2_asymptotic_preVFP_Candidate_2020_01_21_10_53_15/110X_mcRun2_asymptotic_preVFP_v4
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mcRun2_asymptotic_Candidate_2020_01_21_10_51_32/110X_mcRun2_asymptotic_v7
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mcRun2cosmics_startup_deco_Candidate_2020_01_21_10_58_30/110X_mcRun2cosmics_startup_deco_v6
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_dataRun2_2017_2018_Candidate_2020_01_17_14_50_24/110X_dataRun2_v10
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_dataRun2_relval_Candidate_2020_01_17_14_52_17/110X_dataRun2_relval_v10
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_dataRun3_Prompt_Candidate_2020_01_19_15_27_07/106X_dataRun3_Prompt_v5
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mc2017_design_Candidate_2020_01_17_14_56_45/110X_mc2017_design_v3
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mc2017_realistic_Candidate_2020_01_17_14_54_08/110X_mc2017_realistic_v4
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mc2017cosmics_realistic_deco_Candidate_2020_01_17_14_54_57/110X_mc2017cosmics_realistic_deco_v3
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mc2017cosmics_realistic_peak_Candidate_2020_01_17_14_55_41/110X_mc2017cosmics_realistic_peak_v3
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_upgrade2018_design_Candidate_2020_01_17_14_58_40/110X_upgrade2018_design_v4
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_upgrade2018_realistic_Candidate_2020_01_17_14_59_48/110X_upgrade2018_realistic_v9
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_upgrade2018cosmics_realistic_deco_Candidate_2020_01_17_15_00_52/110X_upgrade2018cosmics_realistic_deco_v6
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_upgrade2018cosmics_realistic_peak_Candidate_2020_01_17_15_01_24/110X_upgrade2018cosmics_realistic_peak_v7
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mcRun3_2021_design_Candidate_2020_01_17_15_02_07/110X_mcRun3_2021_design_v6
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mcRun3_2021_realistic_Candidate_2020_01_17_15_02_54/110X_mcRun3_2021_realistic_v8
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mcRun3_2021cosmics_realistic_deco_Candidate_2020_01_17_15_04_04/110X_mcRun3_2021cosmics_realistic_deco_v5
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mcRun3_2023_realistic_Candidate_2020_01_17_15_05_07/110X_mcRun3_2023_realistic_v8
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_mcRun3_2024_realistic_Candidate_2020_01_17_15_06_09/110X_mcRun3_2024_realistic_v8

PR validation:

A technical test was performed: runTheMatrix.py -l limited,7.2,7.22 --ibeos

if this PR is a backport please specify the original PR:

This PR is not a backport and should not be backported.

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28804/13504

  • This PR adds an extra 12KB to repository

  • There are other open Pull requests which might conflict with changes you have proposed:

@cmsbuild
Copy link
Contributor

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

It involves the following packages:

Configuration/AlCa

@christopheralanwest, @tocheng, @cmsbuild, @franzoni, @tlampen, @pohsun can you please review it and eventually sign? Thanks.
@makortel, @Martin-Grunewald, @mmusich, @tocheng this is something you requested to watch as well.
@davidlange6, @silviodonato, @fabiocos you are the release manager for this.

cms-bot commands are listed here

@christopheralanwest
Copy link
Contributor Author

please test workflow 7.2,7.22

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 28, 2020

The tests are being triggered in jenkins.
Test Parameters:

@mmusich
Copy link
Contributor

mmusich commented Jan 28, 2020

@christopheralanwest thanks for this PR.
On a related topic, after #28762 was merged I noticed that wf 136.891 is starting to fail with message:

----- Begin Fatal Exception 28-Jan-2020 08:38:22 CET-----------------------
An exception of category 'Configuration' occurred while
   [0] Processing  Event run: 320822 lumi: 75 event: 126696592 stream: 1
   [1] Running path 'pathALCARECOSiPixelCalSingleMuon'
   [2] Calling method for module HLTHighLevel/'ALCARECOSiPixelCalSingleMuonHLTFilter'
Exception Message:
 HLTHighLevel [instance: ALCARECOSiPixelCalSingleMuonHLTFilter - path: pathALCARECOSiPixelCalSingleMuon]: No triggerList with key SiPixelCalSingleMuon in AlCaRecoTriggerBitsRcd
----- End Fatal Exception -------------------------------------------------

(see e.g. log here).
This means that the autoCond key run2_data_promptlike which is employed in that wf needs to be updated. As you are touching autoCond here, would it be possible to include a fix for that?
Now as far as I can see the current Global Tag for that key uses the tag AlCaRecoHLTpaths_2017_v5 which is different from the one used by the run3_data_promptlike key (i.e. AlCaRecoHLTpaths8e29_5e33_v7_prompt) which is also contained in the current Prompt Reco GT. I am wondering if this difference is intentional. If it is I can provide a new tag AlCaRecoHLTpaths_2017_v6 with the new trigger keys, otherwise I would think it is advisable to align the two Global Tags to use the same tag.
Please let me know.
cc:
@silviodonato

@silviodonato
Copy link
Contributor

please test workflow 136.891

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 28, 2020

The tests are being triggered in jenkins.
Test Parameters:

@silviodonato
Copy link
Contributor

please have a look at #28762 (comment)

@cmsbuild
Copy link
Contributor

-1

Tested at: 3d9e2b6

CMSSW: CMSSW_11_1_X_2020-01-27-2300
SCRAM_ARCH: slc7_amd64_gcc820
You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-1fc432/4376/summary.html

I found follow errors while testing this PR

Failed tests: RelVals

  • RelVals:

When I ran the RelVals I found an error in the following workflows:
136.891 step3

runTheMatrix-results/136.891_RunSingleMu2018D+RunSingleMu2018D+HLTDR2_2018+RECODR2_2018reHLT_skimSingleMu_Prompt_Lumi+HARVEST2018_L1TMuDQM_Prompt/step3_RunSingleMu2018D+RunSingleMu2018D+HLTDR2_2018+RECODR2_2018reHLT_skimSingleMu_Prompt_Lumi+HARVEST2018_L1TMuDQM_Prompt.log

@cmsbuild
Copy link
Contributor

Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped)

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28804/13519

  • This PR adds an extra 12KB to repository

  • There are other open Pull requests which might conflict with changes you have proposed:

@christopheralanwest
Copy link
Contributor Author

please test workflow 136.891

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 28, 2020

The tests are being triggered in jenkins.
Test Parameters:

@cmsbuild
Copy link
Contributor

Pull request #28804 was updated. @christopheralanwest, @tocheng, @cmsbuild, @franzoni, @tlampen, @pohsun can you please check and sign again.

@cmsbuild
Copy link
Contributor

+1
Tested at: bcd63b5
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-1fc432/4390/summary.html
CMSSW: CMSSW_11_1_X_2020-01-28-1100
SCRAM_ARCH: slc7_amd64_gcc820

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-1fc432/4390/summary.html

@slava77 comparisons for the following workflows were not done due to missing matrix map:

  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/results/JR-comparison/PR-1fc432/136.891_RunSingleMu2018D+RunSingleMu2018D+HLTDR2_2018+RECODR2_2018reHLT_skimSingleMu_Prompt_Lumi+HARVEST2018_L1TMuDQM_Prompt

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 34
  • DQMHistoTests: Total histograms compared: 2697090
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2696743
  • DQMHistoTests: Total skipped: 346
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 33 files compared)
  • Checked 147 log files, 16 edm output root files, 34 DQM output files

@christopheralanwest christopheralanwest changed the title Rename candidate GTs to use official names Rename candidate GTs to use official names and update alcareco trigger bits Jan 28, 2020
@christopheralanwest
Copy link
Contributor Author

+1

@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. @davidlange6, @silviodonato, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

@silviodonato
Copy link
Contributor

+1
thanks for the fix

@cmsbuild cmsbuild merged commit cf33acd into cms-sw:master Jan 29, 2020
@mmusich
Copy link
Contributor

mmusich commented Jan 29, 2020

@christopheralanwest @silviodonato
as far as I can this PR destroys more workflow than the previous situation: https://cms-sw.github.io/relvalLogDetail.html#slc7_amd64_gcc820;CMSSW_11_1_X_2020-01-29-1100
I think I understand why the prompt-like workflows had employed a different trigger bit selection. Certain alcas are run on demand and do not subsist on all the IOVs in Prompt Reco, while they are run over across the board in the IB tests.
I'll provide shortly a new tag AlCaRecoHLTpaths_2017_v6 to be used instead.

@mmusich
Copy link
Contributor

mmusich commented Jan 29, 2020

the new tag is available: https://cms-conddb.cern.ch/cmsDbBrowser/list/Prod/tags/AlCaRecoHLTpaths_2017_v6
Here is the diff w.r.t the previous tag:
image

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

4 participants