-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Include scouting EGM in Online DQM stream #48850
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
Conversation
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-48850/45990 |
|
test parameters:
|
|
please test |
|
+1 Size: This PR adds an extra 40KB to repository Comparison SummarySummary:
|
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.
if ScoutingEGammaCollectionMonitoringOnline and ScoutingElectronTagProbeAnalysisOnline are clones of the offline ones, can't they just be cloned and then the relevant parameters be changed in-situ?
| l1tAlgBlkInputTag = cms.InputTag("gtStage2Digis"), | ||
| l1tExtBlkInputTag = cms.InputTag("gtStage2Digis"), | ||
| ReadPrescalesFromFile = cms.bool(False), | ||
| triggerSelection = cms.vstring(["DST_PFScouting_ZeroBias_v", "DST_PFScouting_DoubleEG_v", "DST_PFScouting_SinglePhotonEB_v"]), |
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 the muon equivalent we had issues with these hardcoded bits when running scouting paths in a VdM scan, see e.g.: PR #48529 for a rationale.
I think these should be avoided here as well.
| scoutingMonitoringTagProbe = cms.Sequence(ScoutingElectronTagProbeAnalysis) # * ScoutingElectronEfficiencySummary) | ||
| ScoutingElectronTagProbeAnalysisOnline = DQMEDAnalyzer('ScoutingElectronTagProbeAnalyzer', | ||
| OutputInternalPath = cms.string('/HLT/ScoutingOffline/EGamma/TnP/Tag_ScoutingElectron'), | ||
| BaseTriggerSelection = cms.vstring(["DST_PFScouting_ZeroBias_v", "DST_PFScouting_SingleMuon_v", "DST_PFScouting_DoubleMuon_v", "DST_PFScouting_JetHT_v"]), |
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 the muon equivalent we had issues with these hardcoded bits when running scouting paths in a VdM scan, see e.g.: PR #48529 for a rationale.
I think these should be avoided here as well.
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.
I am still investigating this #48529 issue. So I think the goal is to make the code runable for following command (but I notice the data permission is not public)
cmsRun scouting_dqm_sourceclient-live_cfg.py runInputDir=/eos/user/d/dpapagia/data runNumber=394413 scanOnce=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.
so I think the goal is to make the code runable for following command
correct. @nothingface0 would you mind giving @tihsu99 read rights over that folder?
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.
I did a test using the branch proposed here and I don't observe issues.
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.
I just shared the directory with Ting-Hsiang. Having all those files under my personal space is probably suboptimal, I'll think about moving it somewhere where they can be shared centrally, perhaps.
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.
Thank you for sharing.
I also run with it and as @mmusich observed, I also didn't see any issues.
|
|
||
| scoutingMonitoringEGM = cms.Sequence(ScoutingEGammaCollectionMonitoring) | ||
| ScoutingEGammaCollectionMonitoringOnline = DQMEDAnalyzer('ScoutingEGammaCollectionMonitoring', | ||
| OutputInternalPath = cms.string('/HLT/ScoutingOffline/EGamma/Collection'), |
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.
in the online DQM we're using a different path:
/HLT/ScoutingOnline/...please update.
|
|
||
| scoutingMonitoringTagProbe = cms.Sequence(ScoutingElectronTagProbeAnalysis) # * ScoutingElectronEfficiencySummary) | ||
| ScoutingElectronTagProbeAnalysisOnline = DQMEDAnalyzer('ScoutingElectronTagProbeAnalyzer', | ||
| OutputInternalPath = cms.string('/HLT/ScoutingOffline/EGamma/TnP/Tag_ScoutingElectron'), |
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.
in the online DQM we're using a different path:
/HLT/ScoutingOnline/...please update.
|
|
||
|
|
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 (size_t i = 1; i < patEls->size(); ++i) { | ||
| if (patEls->ptrAt(i - 1)->pt() < patEls->ptrAt(i)->pt()) { | ||
| edm::LogWarning("ScoutingEGammaCollectionMonitoring") | ||
| << "pat::Electron collection not sorted by PT in descending order" | ||
| << " will result in random histo filling. \n" | ||
| << "pat::Electron[" << i << "].pt() = " << patEls->ptrAt(i)->pt() << "\n" | ||
| << "pat::Electron[" << i + 1 << "].pt() = " << patEls->ptrAt(i + 1)->pt(); | ||
| } | ||
| } |
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.
I notice this only now. Does it make sense to sort the input upfront then?
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, this is redundant, just for developping purpose. Will remove it.
|
-hlt
|
|
A new Pull Request was created by @tihsu99 for master. It involves the following packages:
@antoniovagnerini, @ctarricone, @rseidita can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-48850/46016 |
|
Pull request #48850 was updated. @Martin-Grunewald, @antoniovagnerini, @cmsbuild, @ctarricone, @mmusich, @rseidita can you please check and sign again. |
|
test parameters:
|
|
@cmsbuild, please test |
|
+1 Size: This PR adds an extra 28KB to repository Comparison SummarySummary:
|
|
+hlt
@tihsu99 do you plan a 15_0_X backport? @cms-sw/dqm-l2 it would be nice to get the backport of this included in the next online release. |
Yes, I plan a 15_0_X backport. I will make another backport PR after this PR is approved, |
|
+dqm @tihsu99 please open the backport asap so we can get deploy it cleanly in the online release |
|
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. @ftenchini, @sextonkennedy, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
I second this, if you can make a backport by later today it will have a chance to enter the next data-taking release. |
|
+1 |
PR description:
A patch is added to include scouting egamma DQM monitoring in the online stream. The update is highly related to previous PR cmssw#48398 (New HLT Scouting DQM Online Client) i.e. here we introduce scouting egamma part into HLT Scouting DQM online client for the DQMOnlineScoutingstream. This progress has been mentioned in the scouting meeting at 28 Aug 2025.
Description of the current change
useOfflineObjectin the config files under the originalHLTriggerOffline/Scouting. In online stream, we could choose not to use any offline object by such options.HLTriggerOffline/Scouting/python/HLTScoutingEGammaPostProcessing_cff.py, which corresponds to the DQM Harvester, uses offline objects to achieve more accurate Tag-and-Probe measurements. Therefore, this postprocessor is not included in the online DQM sequence. (Similarly, in previous PR, for scouting muons, the harvester defined inHLTriggerOffline/Scouting/python/ScoutingMuonMonitoring_Client_cff.pyis not used in Online DQM.) This is mentioned here for completeness.PR validation:
This PR has been prepared from
CMSSW_15_1_X_2025-08-27-2300Check the code dependency and its output
And
Backport plan:
This is not backport but it will be backported to 15.0.X for 2025 data taking operations.
(c.c. TSG-scouting conveners @silviodonato @patinkaew )