Scouting DQM: add best-track and shower-shape monitoring for scouting electrons [16.0.X]#50457
Conversation
|
A new Pull Request was created by @sakura-ngt for CMSSW_16_0_X. It involves the following packages:
@Martin-Grunewald, @cmsbuild, @ctarricone, @gabrielmscampos, @mmusich, @nothingface0, @rseidita can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
cms-bot internal usage |
1455ffd to
937f5aa
Compare
|
Pull request #50457 was updated. @Martin-Grunewald, @cmsbuild, @ctarricone, @gabrielmscampos, @mmusich, @nothingface0, @rseidita can you please check and sign again. |
|
@cmsbuild, please test |
|
type ngt |
|
+1 Size: This PR adds an extra 44KB to repository Comparison SummarySummary:
|
|
+hlt |
|
+dqm
|
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_16_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_16_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @ftenchini, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
|
REMINDER @sextonkennedy, @mandrenguyen, @ftenchini: This PR was tested with #50494, please check if they should be merged together |
|
+1 |
backport of #50444
PR description:
This PR extends
ScoutingCollectionMonitorwith additional electron and photon monitoring. It adds calorimeter variables (nClusters,nCrystals,rechitZeroSuppression), electron track multiplicity, and best-track observables viaedm::ValueMapsfromrun3ScoutingElectronBestTrack.New histograms are booked and filled using
edm::Refaccess, skipping electrons without valid tracks. The requiredValueMapinputs are added to the configuration.The
run3ScoutingElectronBestTrackproducer is included in both online and offline DQM sequences.PR validation:
These commands run fine:
as well as:
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:
Verbatim backport of #50444 to the 2026 data-taking release.