-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Validation code update for MTD tracks and hits #33252
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33252/21720
|
A new Pull Request was created by @gsorrentino18 (Giulia Sorrentino) for master. It involves the following packages: Validation/Configuration @andrius-k, @kmaeshima, @ErnestaP, @ahmad3213, @cmsbuild, @jfernan2, @mdhildreth, @civanch, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d4883c/13713/summary.html Comparison SummarySummary:
|
+1 |
meHitLongPos_->Fill(recHit.position()); | ||
meHitLongPosErr_->Fill(recHit.positionError()); | ||
|
||
meOccupancy_->Fill(global_point.z(), global_point.phi()); | ||
|
||
if (LocalPosDebug_) { | ||
meLocalOccupancy_->Fill(local_point.x() + recHit.position(), local_point.y()); |
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.
@gsorrentino18 is the addition of the reconstructed longitudinal position giving the expected behaviour?
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.
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 is observed likely accounts for uncertainty in the reconstructed position that is used on top of the nominal center of the crystal according to the geometry, this is seen also in the one-dimensional plot of the longitudinal position in local coordinates
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 any case the 16x3 layout is confirmed to be in the correct orientation, unlike the ETL pixels layout (@parbol FYI)
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33252/21784
|
Pull request #33252 was updated. @andrius-k, @kmaeshima, @ErnestaP, @ahmad3213, @cmsbuild, @jfernan2, @mdhildreth, @civanch, @rvenditti can you please check and sign again. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d4883c/13800/summary.html Comparison SummarySummary:
|
@cms-sw/dqm-l2 @cms-sw/simulation-l2 |
+1 |
+1 |
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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR expands the validation code for tracks, including monitoring for the following quantities:
-Time and time error of tracks at the different steps of the MTD track reconstruction
-MVA and pathlenght of MTD tracks
-pT resolution wrt General tracks
The validation code for ETL and BTL Reco Hits has also been expanded, adding time and energy resolution MEs and implementing an optional set of histograms for the monitoring of the hits local position, that can be used for dedicated studies.
PR validation:
The new code has been tested in the release CMSSW_11_3_X_2021-03-19-1100