-
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
New plots for Tracking Workspace #27330
Conversation
@hbecerri, CMSSW_11_0_X branch is closed for direct updates. cms-bot is going to move this PR to master branch. |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27330/10564
|
A new Pull Request was created by @hbecerri for master. It involves the following packages: DQM/TrackingMonitor @andrius-k, @kmaeshima, @schneiml, @cmsbuild, @jfernan2, @fioriNTU can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
histname = "Ratio_byFolding2_" + histTag; | ||
tkmes.Ratio_byFolding2 = ibooker.book1D(histname, histname, TrackPtBin, TrackPtMin, TrackPtMax); | ||
tkmes.Ratio_byFolding2->setAxisTitle("Track p_{T} (GeV/c)", 1); | ||
|
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.
@hbecerri please set a meaningful name in the title of the plots (second histname in book1D), otherwise it will be difficult to know what ZoneX stands for. Thanks
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.
Hello @jfernan2, I did the modifications. I tried to be more specific.
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27330/10591
|
Pull request #27330 was updated. @andrius-k, @kmaeshima, @schneiml, @cmsbuild, @jfernan2, @fioriNTU can you please check and sign again. |
@hbecerri have you done any kind of validation? Does this PR need a backport? Please add this information in the PR description |
Hello @jfernan2, I updated the PR description. I used the runTheMatrix tool to validate my changes. Also, trying to create a PR CMSSW_11_0_X cmsbuild automatically changes the base branch to masters. |
@hbecerri I was referring to backports to CMSSW prior to 11XY |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@hbecerri thanks for the fix. Can you make a final check to see that everything is in place now concerning Tracking? I see now different folders depending on the workflow: |
Hello @jfernan2, I see the different folders depending on the workflow but I am not sure that it is related with my changes. Probably it is something expected? What I can see is that the new plots are always in the right place. |
@hbecerri OK, basically I wanted you to confirm that you get the correct number of plots on Tracking / TrackParameters:
|
Hi @jfernan2, it is the correct number of plots |
+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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
@@ -850,6 +853,21 @@ void TrackAnalyzer::bookHistosForBeamSpot(DQMStore::IBooker& ibooker) { | |||
DistanceOfClosestApproachToBS->setAxisTitle("Track d_{xy} wrt beam spot (cm)", 1); | |||
DistanceOfClosestApproachToBS->setAxisTitle("Number of Tracks", 2); | |||
|
|||
if (Folder == "Tr") { |
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.
@hbecerri may I ask you to remind me what you mean by this check ?
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.
Hello @mtosi, as is mentioned before in this PR, the modules I modified are being used by other subsystems (MUO, HLT/EGM and HLT/EXO) so the new plots were also in different workspaces other than Tracking. So the check is to create the new plots only for Tracking.
thanks
mia
… On 16 Jul 2019, at 15:32, hbecerri ***@***.***> wrote:
@hbecerri commented on this pull request.
In DQM/TrackingMonitor/src/TrackAnalyzer.cc:
> @@ -850,6 +853,21 @@ void TrackAnalyzer::bookHistosForBeamSpot(DQMStore::IBooker& ibooker) {
DistanceOfClosestApproachToBS->setAxisTitle("Track d_{xy} wrt beam spot (cm)", 1);
DistanceOfClosestApproachToBS->setAxisTitle("Number of Tracks", 2);
+ if (Folder == "Tr") {
Hello @mtosi, as is mentioned before in this PR, the modules I modified are being used by other subsystems (MUO, HLT/EGM and HLT/EXO) so the new plots were also in different workspaces other than Tracking. So the check is to create the new plots only for Tracking.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
New plots for Tracking Workspace (Backport to CMSSW_10_6_X of #27330)
PR description:
Add new plots in the Tracking Workspace
dz with respect to BS
dxy with respect to the BS vs eta and phi,
q over p
track quality (isLoose, isTight, isHighQuality),
"inclusively" but also vs pT and eta
number of tracks per vertex, for the hard vertex and
for the other (PU) vertices
tracking efficiency plots from the folding method, for the
"eta vs phi map"
tracking efficiency vs pT of the tracks
Validated with runTheMatrix.py -l 10024