-
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
Move CSC trigger and GEM-CSC trigger lookup tables into eventsetup objects (CCLUT-17) #34779
Move CSC trigger and GEM-CSC trigger lookup tables into eventsetup objects (CCLUT-17) #34779
Conversation
FYI @rathjd |
I see the exact same 2 validation plots as in #34582. So the LUTs are looked and used alright. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-34779/24446
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
Originally I had the luts pass by reference in |
pset_.getParameter<std::vector<std::string>>("esDiffToSlopeME1bFiles"); | ||
|
||
// read the text files and extract the data | ||
const auto& GEM_pad_CSC_hs_ME1a_even_ = load(padToHsME1aFiles_[0]); |
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.
Change the type from const auto&
to just auto
. This will allow the std::move
to work.
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.
Very good!
Hi @dildick while we are still at the code checks part, can you please squash some of the commits (bugfix, change name, several code checks)? Thanks! |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-34779/24450
|
A new Pull Request was created by @dildick (Sven Dildick) for master. It involves the following packages:
@malbouis, @andrius-k, @yuanchao, @kmaeshima, @ErnestaP, @ahmad3213, @rvenditti, @cmsbuild, @rekovic, @jfernan2, @tlampen, @ggovi, @pohsun, @francescobrivio, @cecilecaillol, @tvami can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@tvami Done. It can all go into a single commit. |
@dildick great thanks! Another thing that when a new record is introduced, we usually like if there is a presentation about it at the AlCaDB meeting. Would you be available to present at the next meeting (Monday, 16:00)? |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-34779/24453
|
please test |
@qliphy Are the tests stuck? |
@cmsbuild , ping |
@cmsbuild , please test |
ping @tvami. Is the bot stuck again on the same test? |
@smuzaffar : tests look stuck ("Not yet started" since several hours) in several PR. Is there anyfhing that can be done to start them? |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-297c50/18195/summary.html Comparison SummarySummary:
|
+1 |
@qliphy Can this PR be signed off? Thanks! |
+1 |
PR description:
Move CSC trigger and GEM-CSC trigger lookup tables into eventsetup objects. This should prevent cmsRun from spending too much time loading lookup tables for the pattern finding logic. This PR requires cms-data/L1Trigger-CSCTriggerPrimitives#11
In response to #34633
@Dr15Jones @makortel Supersedes #34693.
CSCL1TPLookupTableEP
which is an ESProducer.CSCL1TPLookupTableEP
produces 3 types of ES data: (a)CSCL1TPLookupTableCCLUT
, (b)CSCL1TPLookupTableME11ILT
, and (c)CSCL1TPLookupTableME21ILT
. (a) is for upgrade (1). (b) and (c) are for upgrade (2).CSCL1TPLookupTableCCLUT
.CSCL1TPLookupTableCCLUT
followsCSCTriggerPrimitivesProducer
->CSCTriggerPrimitivesBuilder
->CSCMotherBoard
->CSCCathodeLCTProcessor
->ComparatorCodeLUT
.Proposal was presented at https://indico.cern.ch/event/1065089/contributions/4478403/attachments/2292436/3897925/GEM_CSC_Trigger_AlcaDB_20210808.pdf
PR validation:
Tested the code so far on
/RelValSingleMuPt10/CMSSW_11_3_0-113X_mcRun4_realistic_v7_2026D76noPU-v1/GEN-SIM-DIGI-RAW
. Efficiency plots for ME1/1 and ME2/1 are the same as in #34582.if this PR is a backport please specify the original PR and why you need to backport that PR:
N.A.
Before submitting your pull requests, make sure you followed this checklist:
@tahuang1991