Skip to content
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

Merged
merged 5 commits into from
Jul 2, 2019
Merged

Conversation

hbecerri
Copy link
Contributor

@hbecerri hbecerri commented Jun 24, 2019

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

@cmsbuild cmsbuild changed the base branch from CMSSW_11_0_X to master June 24, 2019 12:50
@cmsbuild
Copy link
Contributor

@hbecerri, CMSSW_11_0_X branch is closed for direct updates. cms-bot is going to move this PR to master branch.
In future, please use cmssw master branch to submit your changes.

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27330/10564

  • This PR adds an extra 68KB to repository

@cmsbuild
Copy link
Contributor

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.
@hdelanno, @makortel, @mtosi, @fioriNTU, @jandrea, @idebruyn, @threus this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

@hbecerri hbecerri changed the title Dqm tk quick collection New plots for Tracking Workspace Jun 24, 2019
histname = "Ratio_byFolding2_" + histTag;
tkmes.Ratio_byFolding2 = ibooker.book1D(histname, histname, TrackPtBin, TrackPtMin, TrackPtMax);
tkmes.Ratio_byFolding2->setAxisTitle("Track p_{T} (GeV/c)", 1);

Copy link
Contributor

@jfernan2 jfernan2 Jun 25, 2019

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

Copy link
Contributor Author

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.

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27330/10591

  • This PR adds an extra 68KB to repository

@cmsbuild
Copy link
Contributor

Pull request #27330 was updated. @andrius-k, @kmaeshima, @schneiml, @cmsbuild, @jfernan2, @fioriNTU can you please check and sign again.

@jfernan2
Copy link
Contributor

@hbecerri have you done any kind of validation? Does this PR need a backport? Please add this information in the PR description
https://twiki.cern.ch/twiki/bin/view/CMS/DQMGithubGuide

@hbecerri
Copy link
Contributor Author

@hbecerri have you done any kind of validation? Does this PR need a backport? Please add this information in the PR description
https://twiki.cern.ch/twiki/bin/view/CMS/DQMGithubGuide

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.

@jfernan2
Copy link
Contributor

@hbecerri I was referring to backports to CMSSW prior to 11XY
https://twiki.cern.ch/twiki/bin/view/CMS/ReleaseSchedule

hbecerri added a commit to hbecerri/cmssw that referenced this pull request Jun 26, 2019
@cmsbuild
Copy link
Contributor

cmsbuild commented Jul 1, 2019

@cmsbuild
Copy link
Contributor

cmsbuild commented Jul 1, 2019

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Jul 1, 2019

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-55d7a2/1279/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 4 differences found in the comparisons
  • DQMHistoTests: Total files compared: 33
  • DQMHistoTests: Total histograms compared: 3290686
  • DQMHistoTests: Total failures: 2
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3290350
  • DQMHistoTests: Total skipped: 334
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 3206.965 KiB( 32 files compared)
  • DQMHistoSizes: changed ( 10024.0,... ): 132.521 KiB Tracking/TrackParameters
  • DQMHistoSizes: changed ( 1330.0,... ): 132.131 KiB Tracking/TrackParameters
  • DQMHistoSizes: changed ( 140.53 ): 38.552 KiB Tracking/TrackParameters
  • DQMHistoSizes: changed ( 20034.0,... ): 133.693 KiB Tracking/TrackParameters
  • DQMHistoSizes: changed ( 158.0,... ): 166.837 KiB Tracking/TrackParameters
  • DQMHistoSizes: changed ( 7.3 ): 60.995 KiB Tracking/TrackParameters
  • DQMHistoSizes: changed ( 8.0,... ): 60.878 KiB Tracking/TrackParameters
  • Checked 137 log files, 14 edm output root files, 33 DQM output files

@jfernan2
Copy link
Contributor

jfernan2 commented Jul 1, 2019

@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:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_11_0_X_2019-06-30-2300+55d7a2/32500/dqm-histo-comparison-summary.html

@hbecerri
Copy link
Contributor Author

hbecerri commented Jul 2, 2019

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.

@jfernan2
Copy link
Contributor

jfernan2 commented Jul 2, 2019

@hbecerri OK, basically I wanted you to confirm that you get the correct number of plots on Tracking / TrackParameters:

  • Cosmics wf: 54 new plots on GeneralProperties
  • Data/MC: 116 new plots on generalTracks, highPurityTracks
  • HI Run1: 29 new plots on GeneralProperties
  • Hi: 158 new plots on generalTracks, hiConformalPixelTracks, highPurityTracks

@hbecerri
Copy link
Contributor Author

hbecerri commented Jul 2, 2019

@hbecerri OK, basically I wanted you to confirm that you get the correct number of plots on Tracking / TrackParameters:

  • Cosmics wf: 54 new plots on GeneralProperties
  • Data/MC: 116 new plots on generalTracks, highPurityTracks
  • HI Run1: 29 new plots on GeneralProperties
  • Hi: 158 new plots on generalTracks, hiConformalPixelTracks, highPurityTracks

Hi @jfernan2, it is the correct number of plots

@jfernan2
Copy link
Contributor

jfernan2 commented Jul 2, 2019

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Jul 2, 2019

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)

@fabiocos
Copy link
Contributor

fabiocos commented Jul 2, 2019

+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") {
Copy link
Contributor

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 ?

Copy link
Contributor Author

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.

@mtosi
Copy link
Contributor

mtosi commented Jul 16, 2019 via email

cmsbuild added a commit that referenced this pull request Aug 6, 2019
New plots for Tracking Workspace (Backport to CMSSW_10_6_X of #27330)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants