-
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
[14_1_X] Added more ZDC functionality to DQM #46407
base: CMSSW_14_1_X
Are you sure you want to change the base?
Conversation
Code-reformated + title change
A new Pull Request was created by @cfmcginn for CMSSW_14_1_X. It involves the following packages:
@antoniovagnerini, @cmsbuild, @nothingface0, @rvenditti, @syuvivida, @tjavaid can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
cms-bot internal usage |
please test |
+1 Size: This PR adds an extra 24KB to repository Comparison SummarySummary:
|
Just to add another tag for relevant reviewers: @denizsun, @salimcerci, @JoshPBR2, @abdoulline. This is a modification of of the original PR, which we intend to update with the changes once @JoshPBR2 is available to do so. The current version of the release is 14_1_3, built yesterday. If possible, we would love for this to be included the next release, i.e. 14_1_4. As @cfmcginn mentions, it would be good to understand what is most appropriate to do for the source client file. The reason why we have questions is that I am not entirely sure what is used to create the plots online vs. local tests. Please let us know what you think! |
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.
This PR is different from the master one: #45948, thus it's not a backport. You need to close that one and open another one that contains the same changes as this one in the master (CMSSW_14_2_X) cycle.
// std::shared_ptr<hcaldqm::Cache> globalBeginLuminosityBlock(edm::LuminosityBlock const &, | ||
// edm::EventSetup const &) const override; | ||
//void globalEndLuminosityBlock(edm::LuminosityBlock const &, edm::EventSetup const &) override; |
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.
needed?
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.
No, removed in most recent commit
edm::EDGetToken sumToken_; | ||
edm::ESGetToken<HcalTopology, HcalRecNumberingRecord> htopoToken_; | ||
edm::ESGetToken<HcalLongRecoParams, HcalLongRecoParamsRcd> paramsToken_; | ||
//edm::EDGetTokenT<l1t::EtSumBxCollection> sumZDCToken_; |
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.
//edm::EDGetTokenT<l1t::EtSumBxCollection> sumZDCToken_; |
needed?
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.
No, removed in most recent commit
_tagQIE10 = ps.getUntrackedParameter<edm::InputTag>("tagQIE10", edm::InputTag("hcalDigis", "ZDC")); | ||
_tokQIE10 = consumes<QIE10DigiCollection>(_tagQIE10); | ||
|
||
//const edm::EDGetTokenT<l1t::EtSumBxCollection> sumZDCToken_; |
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.
//const edm::EDGetTokenT<l1t::EtSumBxCollection> sumZDCToken_; |
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.
Adopted
//const edm::EDGetTokenT<l1t::EtSumBxCollection> sumZDCToken_; | ||
|
||
sumTag = ps.getUntrackedParameter<edm::InputTag>("etSumTag", edm::InputTag("etSumZdcProducer", "")); | ||
//sumTag = ps.getParameter<edm::InputTag>("etSumTag"); |
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.
//sumTag = ps.getParameter<edm::InputTag>("etSumTag"); |
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.
Adopted
sumTag = ps.getUntrackedParameter<edm::InputTag>("etSumTag", edm::InputTag("etSumZdcProducer", "")); | ||
//sumTag = ps.getParameter<edm::InputTag>("etSumTag"); | ||
sumToken_ = consumes<l1t::EtSumBxCollection>(sumTag); | ||
//sumZDCToken_ = consumes<l1t::EtSumBxCollection>(ps.getUntrackedParameter<edm::InputTag>("sumZDCToken")); |
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.
//sumZDCToken_ = consumes<l1t::EtSumBxCollection>(ps.getUntrackedParameter<edm::InputTag>("sumZDCToken")); |
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.
Adopted
process.load("Configuration.StandardSequences.FrontierConditions_GlobalTag_cff") | ||
process.GlobalTag.globaltag = autoCond['run3_data_prompt'] | ||
process.load("Configuration.StandardSequences.FrontierConditions_GlobalTag_cff") | ||
process.GlobalTag.globaltag = '141X_dataRun3_Prompt_Candidate_2024_10_08_09_42_50' |
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.
don't change the default here.
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.
Sounds good, the above is a candidate GT, but the default version will change once the new GT (containing the changes from the candidate) is in place.
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.
This is reverted in most recent commit
@@ -57,10 +58,12 @@ | |||
process.dqmSaverPB.runNumber = options.runNumber | |||
process = customise(process) | |||
process.DQMStore.verbose = 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.
don't comment the lines in between.
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.
Done, no longer commented in most recent commit
process.hcalDigis.InputLabel = rawTag | ||
process.emulTPDigisNoTDCCut = process.emulTPDigis.clone( | ||
parameters = cms.untracked.PSet( | ||
ADCThresholdHF = cms.uint32(255), | ||
TDCMaskHF = cms.uint64(0xFFFFFFFFFFFFFFFF) | ||
) | ||
) | ||
process.HcalTPGCoderULUT.LUTGenerationMode = False | ||
process.HcalTPGCoderULUT.LUTGenerationMode = True |
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.
what's the purpose of this change?
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.
This is actually what we would like feedback on from @denizsun and @salimcerci, this is necessary for the code to run with the candidate GT (which does not yet include an updated L1TriggerObject) , but probably not necessary for actual data-taking. In this case, should we include this or leave it out?
process.maxEvents = cms.untracked.PSet( | ||
input = cms.untracked.int32(-1) | ||
) |
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.
process.maxEvents = cms.untracked.PSet( | |
input = cms.untracked.int32(-1) | |
) |
in live mode the number of events processed is regulated elsewhere:
cmssw/DQM/Integration/python/config/inputsource_cfi.py
Lines 111 to 125 in f97584b
source = cms.Source("DQMStreamerReader", | |
runNumber = cms.untracked.uint32(options.runNumber), | |
runInputDir = cms.untracked.string(options.runInputDir), | |
SelectEvents = cms.untracked.vstring('*'), | |
streamLabel = cms.untracked.string(streamLabel), | |
scanOnce = cms.untracked.bool(options.scanOnce), | |
datafnPosition = cms.untracked.uint32(options.datafnPosition), | |
minEventsPerLumi = cms.untracked.int32(1), | |
delayMillis = cms.untracked.uint32(500), | |
nextLumiTimeoutMillis = cms.untracked.int32(nextLumiTimeoutMillis), | |
skipFirstLumis = cms.untracked.bool(options.skipFirstLumis), | |
deleteDatFiles = cms.untracked.bool(False), | |
endOfRunKills = cms.untracked.bool(endOfRunKills), | |
inputFileTransitionsEachEvent = cms.untracked.bool(False) | |
) |
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.
Removed in most recent commit
Hi @mmusich, thanks for your comment! The plan is to update the PR to master (CMSSW_14_2_X) cycle to have the same changes as the one here, i.e. this would be a true backport. Unfortunately, we've been unable to get ahold of Josh (I believe he might be traveling to CERN), and he is needed in order to make this change. We wanted to give ample time for review of these changes, so we decided to open the PR to 14_1_X as soon as possible. Let me know what you think of this strategy. |
well, abandoning the unattended PR and opening a new one from scratch will get you merged faster. This one cannot be integrated until the master one is merged. |
Okay I see, in that case we will see if Josh gets back to us today, and if not, we will close the master PR and open a new one. |
@hjbossi any updates on the comments by Marco? At this stage, I would also recommend closing the master #45948 and making a new one that matches the backport. |
I intend to open the new PR to main today; I don't know that I have power to close the old, but that should follow |
PR to main can be found here: |
Pull request #46407 was updated. @antoniovagnerini, @cmsbuild, @nothingface0, @rvenditti, @syuvivida, @tjavaid can you please check and sign again. |
Code reformatted, emulator updates, and histogram title change
PR description:
This is a backport to CMSSW_14_1_X of existing PR here: #45948
The PR adds to the DQM for ZDC specific histograms, via ZDCQIE10Task
The backport is updated relative to the main PR, mostly fixing build issue, retitling some histograms, and updating python such that emulated ZDC sums fill. It is also rebased to 14_1_X for the backport.
PR validation:
PR is tested in CMSSW_14_1_X_2024-10-15-2300, after running a merge-topic to incorporate the PR into a fresh area
scram b ran successfully, validating the build
Following test command produces the expected output:
under the upload directory. Inspected histograms inside the DQM file appear reasonable for ZDC sums.
In addition, the following set of commands are run
scram b runtests
scram build code-checks
scram build code-format
code-checks revealed no issues, code-format suggestions were adopted. runtests had multiple failures, detailed below - however, every failure existed already with runtests in a fresh area of CMSSW_14_1_X_2024-10-15-2300 with the same packages checked out (before merge-topic), so it is unclear it is the result of the PR
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:
As mentioned above, PR is a backport (with modification) of #45948, intended for CMSSW_14_1_X
One note - close inspection of the changes to the python file would be welcome - the changes were made as part of testing the full package but unclear to me all should be incorporated into the branch as is. Guidance appreciated.
@hjbossi @mandrenguyen