-
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.0.X] Miscellaneous fixes for TRK POG Data/MC validation tool #45174
[14.0.X] Miscellaneous fixes for TRK POG Data/MC validation tool #45174
Conversation
type bug-fix |
A new Pull Request was created by @mmusich for CMSSW_14_0_X. It involves the following packages:
@antoniovagnerini, @tjavaid, @rvenditti, @syuvivida, @cmsbuild, @nothingface0 can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
cms-bot internal usage |
@cmsbuild please test |
…s histogram merging issues
53411d0
to
0f4aa34
Compare
Pull request #45174 was updated. @antoniovagnerini, @cmsbuild, @rvenditti, @tjavaid, @syuvivida, @nothingface0 can you please check and sign again. |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-02b761/39795/summary.html Comparison SummarySummary:
|
+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) |
@cms-sw/orp-l2 can this be merged? |
+1 |
backport of #45173
PR description:
Few miscellaneous fixes for the TRK POG data/MC validation tool:
trackPhiH
ME to avoid using dynamic range which causes histogram merging issuesThese were spotted by operating the data/MC validation tool on 2024 data.
PR validation:
cmssw
compilesIf 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 #45173 for 2024 data-taking purposes.
Cc: @dbruschi