-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
CICADA-uGT emulator additions #44222
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44222/39227
|
I'm marking this pull request ready after adding the unpacker commit. However, I should stress that the unpacker has not been tested in realistic conditions with actual CICADA input data present, and therefore has not been tested to be working. It does compile, and it does seem to properly fail-safe to a 0.0 score in the case of nothing to unpack/nothing unpacked. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44222/39361
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44222/39362
|
A new Pull Request was created by @aloeliger for master. It involves the following packages:
@aloeliger, @epalencia, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
assign hlt
|
New categories assigned: hlt @Martin-Grunewald,@mmusich you have been requested to review this Pull request/Issue and eventually sign? Thanks |
EventFilter/L1TRawToDigi/plugins/implementations_stage2/CaloSummaryUnpacker.cc
Outdated
Show resolved
Hide resolved
It is not clear to me how/where the unpacker is called. Within existing (unpacking) code or a new module, which needs to be added to some python unpacking sequence? What about the packer? |
@Martin-Grunewald It's defined as part of the GT unpacking setup here:
I need to wait until I have test crate records before I can test this non-trivially however. (Seems like it wont unpack empty/unused records?). |
EventFilter/L1TRawToDigi/plugins/implementations_stage2/GTCollections.h
Outdated
Show resolved
Hide resolved
c0b5b26
to
d7cb22a
Compare
-1 Failed Tests: RelVals
RelVals
|
That's a phase 2 issue, which should be impossible for this to affect |
+l1 |
Wrong PR. But whatever. |
please test Hoping this is temporary |
Known issue: #41451 . |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-547e2e/40106/summary.html
Comparison SummarySummary:
|
+1 |
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. @sextonkennedy, @rappoccio, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
@aloeliger @cms-sw/l1-l2 |
+1 |
@antoniovilela That is correct. bcb0dab should rerevert #45037 (I.e. it is included again) |
Thanks. |
@@ -51,6 +51,8 @@ void L1TGlobalProducer::fillDescriptions(edm::ConfigurationDescriptions& descrip | |||
->setComment("InputTag for Calo Trigger EtSum (required parameter: default value is invalid)"); | |||
desc.add<edm::InputTag>("EtSumZdcInputTag", edm::InputTag("")) | |||
->setComment("InputTag for ZDC EtSums Plus and Minus (required parameter: default value is invalid)"); | |||
desc.add<edm::InputTag>("CICADAInputTag", edm::InputTag("")) | |||
->setComment("InputTag for CICADA Anomaly Detection (required parameter: default value is invalid)"); |
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.
So now that this PR and its backport are in 14_1 / 14_0, what value for this new parameter should be used at HLT level running the L1TGlobalProducer? hltGtStage2ObjectMap = cms.EDProducer( "L1TGlobalProducer",...
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.
@Martin-Grunewald Do you want emulator or DAQ values?
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.
For emulator it should be this guy:
For unpacked, here:
https://github.com/cms-sw/cmssw/blob/master/EventFilter/L1TRawToDigi/python/caloLayer1Digis_cfi.py
we don't show up in the production uGT record though, so I wouldn't expect that to be valid yet.
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.
So in HLT where we run hltGtStage2Digis = cms.EDProducer( "L1TRawToDigi",...
it would be hltGtStage2ObjectMap.CICADAInputTag = cms.InputTag("hltGtStage2Digis","CICADAScore"),
, correct?
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.
Can this discussion be documented in a CMSHLT Jira ticket please @aloeliger ?
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.
PR description:
This PR adds the uGT half of the CICADA -> uGT emulator chain. It adds all the pieces needed to parse and compare the new CICADA condition added in uTM v 0.12.0. This is being opened in draft because no unpacker/packer combo is available yet, but will be added after I have had the chance to speak to experts about reading the CICADA record.
Depends on utm version 0.12.0
@elfontan You should likely take a look at my work on this, this is more working with uGT than I am used to.
@cms-sw/hlt-l2 Just in case you aren't automatically pinged on this, FYI. There is no unpacker/packer, but I will keep this in draft while I develop them. I will be speak to experts about it ASAP.
EDIT 06/03/24: Draft unpacker (not non-trivially tested) added.
PR validation:
All code compiles and has had code formatting applied.
In addition, I have tested the emulator on a new proto-type menu including a CICADA seed:
https://cernbox.cern.ch/files/link/public/LeBbgndwFDjWoI5?tiles-size=1&items-per-page=100&view-mode=resource-table
The emulator runs all the way through. The following are debug statements (now removed) from various components of the global board, CICADA conditions, and trigger menu parser showing that the emulator receives the score, compares to the menu, and in this case, decides it is below threshold and doesn't pass the menu cut:
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:
This PR is not a backport however, is likely to be needed for data-taking so a backport is probable to CMSSW_14_0.