-
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
Backport of #44546: Add QuadJet with 3 b-tag PNet trigger to the DQM offline #44553
Conversation
A new Pull Request was created by @brunolopesbr2 for CMSSW_14_0_X. It involves the following packages:
@rvenditti, @syuvivida, @cmsbuild, @antoniovagnerini, @tjavaid, @nothingface0 can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
cms-bot internal usage |
backport of #44546 |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-85a1f2/38453/summary.html Comparison SummarySummary:
|
@cms-sw/dqm-l2 can you please review this? It would be good to have this integrated once we deliver the next HLT menu 2024 V1.1 |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @antoniovilela, @rappoccio, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This is a backport of PR #44546 to 14_0_X, as it needs to be ready alongside the HLT menu v1.1.
Added the Particle Net migrated version of the QuadJet with 3 b-tag trigger to the offline DQM. This trigger path was approved by TSG on March 13th (https://indico.cern.ch/event/1389073/).
As pointed out in the JIRA CMSHLT-3119, the validation strategy should be the same as the previous version of the path (using DeepJet), so it was copied over from the top DQM code with the necessary parameter changes. It's now important only to the Exotica PAG, so it was included in the Exotica DQM.
PR validation:
The DQM code was validated using a runTheMatrix workflow (modified to use the new trigger path). The resulting DQM file was uploaded to the DQM GUI at http://dqm-dev-test.cern.ch:8060/dqm/dev/ and it's a RelVal file. In particular, check that the new DQM plots are being created at the new HLT/EXO/DisplacedVertices/* folder and are populated with the passing events.
A further local validation with fewer events was made to validate the backport to 14_0_X, which was straight-forward.