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

add MTD related hits plots #27682

Merged
merged 6 commits into from
Sep 19, 2019
Merged

add MTD related hits plots #27682

merged 6 commits into from
Sep 19, 2019

Conversation

mtosi
Copy link
Contributor

@mtosi mtosi commented Aug 2, 2019

PR description:

add 3 new histograms to the MTV for having the MTD hits profile vs eta

@makortel do you think we should add a flag for the phase2 (so that we add those plots only for the relevant workflows) ?

@cmsbuild
Copy link
Contributor

cmsbuild commented Aug 2, 2019

The code-checks are being triggered in jenkins.

@mtosi
Copy link
Contributor Author

mtosi commented Aug 2, 2019

@lgray @pmeridian

@cmsbuild
Copy link
Contributor

cmsbuild commented Aug 2, 2019

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27682/11270

  • This PR adds an extra 32KB to repository

  • There are other open Pull requests which might conflict with changes you have proposed:

Code check has found code style and quality issues which could be resolved by applying following patch(s)

@makortel
Copy link
Contributor

makortel commented Aug 2, 2019

do you think we should add a flag for the phase2 (so that we add those plots only for the relevant workflows) ?

Hmm, I'm not sure. It's a bit of a hassle, but would save some memory for non-phase2 workflows. If more MTD plots are foreseen, the flag would start to be more useful.

@mtosi
Copy link
Contributor Author

mtosi commented Aug 2, 2019

well, in view of a more 4D tracking (and vertexing), I would expect more plots which are relevant only with the MTD detectors

but, this will not happen in the short term, I’m afraid

if you agree, I’ll add a flag
or are there more brilliant ways ?

@makortel
Copy link
Contributor

makortel commented Aug 2, 2019

if you agree, I’ll add a flag
or are there more brilliant ways ?

Sounds good, a configuration flag customized with an era is the best way.

@mtosi
Copy link
Contributor Author

mtosi commented Aug 2, 2019 via email

@fabiocos
Copy link
Contributor

@mtosi what are the plans for this PR? It looks dormant...

@mtosi
Copy link
Contributor Author

mtosi commented Sep 10, 2019

@fabiocos , thanks for the message
apologies for the delay, but I'm just back from Holidays ...

@jfernan2
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 17, 2019

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/2546/console Started: 2019/09/17 16:23

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

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

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 34
  • DQMHistoTests: Total histograms compared: 2957336
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2956994
  • DQMHistoTests: Total skipped: 341
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 607.748 KiB( 33 files compared)
  • DQMHistoSizes: changed ( 20434.0,... ): 96.938 KiB Tracking/Track
  • DQMHistoSizes: changed ( 20434.0,... ): 18.996 KiB Tracking/TrackBuilding
  • DQMHistoSizes: changed ( 20434.0,... ): 9.686 KiB Tracking/TrackFromPVAllTP
  • DQMHistoSizes: changed ( 20434.0,... ): 9.627 KiB Tracking/TrackFromPV
  • DQMHistoSizes: changed ( 20434.0,... ): 9.551 KiB Tracking/TrackConversion
  • DQMHistoSizes: changed ( 20434.0,... ): 4.790 KiB Tracking/TrackAllTPEffic
  • DQMHistoSizes: changed ( 20434.0,... ): 2.350 KiB Tracking/TrackGsf
  • Checked 145 log files, 15 edm output root files, 34 DQM output files

@jfernan2
Copy link
Contributor

@mtosi are you aware that you add 3 plots X 63 folders = 189 histograms? And that in some cases they are empty? It was not clear to me from your PR description
https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_11_0_X_2019-09-16-2300+b2133b/33509/dqm-histo-comparison-summary.html

@mtosi
Copy link
Contributor Author

mtosi commented Sep 18, 2019

ciao
thanks for the comment, indeed it is expected and meant to validate / monitor the hits from the MTD detector. they are not used in the current pattern recognition, but the MTD and TRK POG are planning to make use of them as well

@jfernan2
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

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)

// const auto mtdHits = track.hitPattern().numberOfValidTimingHits();
const auto btlHits = track.hitPattern().numberOfValidTimingBTLHits();
const auto etlHits = track.hitPattern().numberOfValidTimingETLHits();
histograms.nMTDhits_vs_eta[count].fill(eta, btlHits + etlHits);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mtosi sorry, the 3 histograms are identical in definition, just filled with either btl, etl or both. At the least the last histogram is redundant (or the first two). Could you please clarify the rationale behind this choice, that ahs an impact in memory?

@mtosi
Copy link
Contributor Author

mtosi commented Sep 18, 2019

as always, we make plots for subsystem and for the whole
(as we do for the 4 strip subsystem, and and the whole strip detector)

@fabiocos
Copy link
Contributor

@mtosi @jfernan2 in case we start to be compressed in memory a choice to be reconsidered...

@mtosi
Copy link
Contributor Author

mtosi commented Sep 19, 2019 via email

@fioriNTU
Copy link
Contributor

@mtosi @fabiocos one possible workaround would be to fill etl and btl plots in step1 and then sum up them in Harvesting. This would save 1/3 of the memory added. However the increase in memory of about 600 KB seems completely acceptable, so we can safely integrate it for the time being.

@fabiocos
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit dfa1c73 into cms-sw:master Sep 19, 2019
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.

None yet

6 participants