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 of some L1T producers for L1TNtuples (legacy modules), of the L1TExtCondProducer, and of the L1MenuViewer #36839

Merged
merged 8 commits into from Feb 2, 2022

Conversation

elfontan
Copy link
Contributor

@elfontan elfontan commented Jan 30, 2022

PR description:

This PR includes some updates related to the L1 trigger emulation:

  • Updates of some producers used to produce L1TNtuples that were causing warnings because they were legacy modules:
    L1UpgradeTfMuonTreeProducer, L1UpgradeTreeProducer, L1HOTreeProducer, L1EventTreeProducer.
  • Update of the L1TExtCondProducer, where a problem related to the usage of the hltGetConfiguration command for MC (uGT only, not FullMC) occured. The issue is related to the configuration file SimL1EmulatorRepack_uGT_cff, where simGtExtFakeStage2Digis.tcdsRecordLabel is modified both for data and MC. However, the label InputTag("unpackTcds","tcdsRecord") for MC implies some checks in the L1ExtCondProducer that are failing. After some investigation, it seems that this tcdsRecordLabel and related input tag should be used as InputTag("unpackTcds","tcdsRecord") only for data. The implemented fix allows to consider all different scenarios in a proper way: FullMC (InputTag empty --> no checks), Full (InputTag ("unpackTcds","tcdsRecord") and real data), uGT data (InputTag ("unpackTcds","tcdsRecord") and real data), uGT MC (InputTag ("unpackTcds","tcdsRecord") BUT not real data --> checks skipped).
  • Fix of the L1MenuViewer to avoid an exception MustUseESGetToken.
  • Update of the script use to produce test vectors including example files produced with CMSSW_12X and a small fix needed for the migration to Python3.

PR validation:

Basic tests performed successfully starting from CMSSW_12_3_X_2022-01-26-1100.
From CMSSW_12_3_X_2022-01-26-1100/src:

scram b distclean
git cms-checkdeps -a -A
scram b -j 8
scram b runtests
scram build code-checks
scram build code-format
runTheMatrix.py -l limited -i all --ibeos

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36839/28027

  • This PR adds an extra 28KB to repository

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @elfontan (Elisa Fontanesi) for master.

It involves the following packages:

  • L1Trigger/L1TGlobal (l1)
  • L1Trigger/L1TNtuples (l1)
  • L1TriggerConfig/Utilities (l1)

@epalencia, @cmsbuild, @cecilecaillol, @rekovic can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @missirol, @dinyar, @kreczko, @thomreis this is something you requested to watch as well.
@perrotta, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@@ -137,7 +137,7 @@ void L1TExtCondProducer::produce(Event& iEvent, const EventSetup& iSetup) {
}

bool TriggerRulePrefireVetoBit(false);
if (makeTriggerRulePrefireVetoBit_) {
if (iEvent.isRealData() && makeTriggerRulePrefireVetoBit_) {
// code taken from Nick Smith's EventFilter/L1TRawToDigi/plugins/TriggerRulePrefireVetoFilter.cc

Copy link
Contributor

Choose a reason for hiding this comment

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

@elfontan , thanks for following up on these fixes. Imho, the following change should also be included in L1TExtCondProducer.cc to avoid the seg-fault discussed in #36786 (comment) , throwing an exception instead:

    // should be 16 according to TCDSRecord.h, we only care about the last 4
    if (eventHistory.size() < 4) {
-      edm::LogError("L1TExtCondProducer") << "Unexpectedly small L1A history from TCDSRecord";
+      throw cms::Exception("L1TExtCondProducer") << "Unexpectedly small L1A history from TCDSRecord: (size = " << eventHistory.size() << " < 4)";
    }

The reason is that LogError does not stop the routine, but after that the code assumes that the vector has at least size==4 , and this is what caused the seg-fault.

@elfontan
Copy link
Contributor Author

Hi @missirol,
thank you for looking into this!
Sure, I can change that line, too. Should I then coherently change all the edm::LogError to throw cms::Exception, in your opinion? Do you see any problem with this?

Cheers,
--Elisa

@missirol
Copy link
Contributor

missirol commented Jan 31, 2022

Should I then coherently change all the edm::LogError to throw cms::Exception, in your opinion?

Well, this would be a question for experts of this plugin. From reading the code, I would say it's not necessary to change the other LogError calls: they signal that there is something wrong/unexpected going on, but the plugin won't crash as a result (unlike for the first LogError call, which should change to an Exception); for these other LogError calls, the worst that can happen is that TriggerRulePrefireVetoBit remains false.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36839/28034

  • This PR adds an extra 28KB to repository

@cmsbuild
Copy link
Contributor

Pull request #36839 was updated. @epalencia, @cmsbuild, @cecilecaillol, @rekovic can you please check and sign again.

@cecilecaillol
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-63ed00/22098/summary.html
COMMIT: 0f7b567
CMSSW: CMSSW_12_3_X_2022-01-30-2300/slc7_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/36839/22098/install.sh to create a dev area with all the needed externals and cmssw changes.

CMS StaticAnalyzer warnings: There are 1 inherits from legacy modules warnings. See https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-63ed00/22098/llvm-analysis/legacy-mod-sa.txt for details.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 1 differences found in the comparisons
  • DQMHistoTests: Total files compared: 43
  • DQMHistoTests: Total histograms compared: 3449612
  • DQMHistoTests: Total failures: 0
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3449590
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 42 files compared)
  • Checked 181 log files, 42 edm output root files, 43 DQM output files
  • TriggerResults: no differences found

@cecilecaillol
Copy link
Contributor

+l1

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 1, 2022

Pull request #36839 was updated. @epalencia, @cmsbuild, @cecilecaillol, @rekovic can you please check and sign again.

@perrotta
Copy link
Contributor

perrotta commented Feb 1, 2022

@elfontan if you want to make const l1GtMenuToken_ you must initialize it in the class initializer list

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 1, 2022

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36839/28100

  • This PR adds an extra 32KB to repository

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 1, 2022

Pull request #36839 was updated. @epalencia, @cmsbuild, @cecilecaillol, @rekovic can you please check and sign again.

@cecilecaillol
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 2, 2022

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-63ed00/22140/summary.html
COMMIT: 9699119
CMSSW: CMSSW_12_3_X_2022-02-01-2300/slc7_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/36839/22140/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: 7 differences found in the comparisons
  • DQMHistoTests: Total files compared: 43
  • DQMHistoTests: Total histograms compared: 3449612
  • DQMHistoTests: Total failures: 12
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3449578
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 42 files compared)
  • Checked 181 log files, 42 edm output root files, 43 DQM output files
  • TriggerResults: no differences found

@cecilecaillol
Copy link
Contributor

+l1

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 2, 2022

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 (and backports should be raised in the release meeting by the corresponding L2)

@perrotta
Copy link
Contributor

perrotta commented Feb 2, 2022

+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

5 participants