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
MTD validation: optional histograms of BTL and ETL uncalibrated RecHits #33662
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33662/22555
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
…or the BTL and ETL time resolutions and a ROOT macro to analyze them.
66de3d1
to
a92841d
Compare
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33662/22556
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33662/22558 |
A new Pull Request was created by @casarsa (Massimo Casarsa) for master. It involves the following packages: Validation/MtdValidation @andrius-k, @kmaeshima, @ErnestaP, @ahmad3213, @cmsbuild, @jfernan2, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
@casarsa I assume you already tested the update with the flags activated |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-32fda8/14952/summary.html Comparison SummarySummary:
|
+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) |
Yes. Activating the flags has no significant impact on the RAM usage and execution time, while it increases the DQM root file by 345.4 kB. |
@casarsa and of course you verified that the output is what expected an usable with the macro, am I correct? |
It goes without saying. |
+1 |
This PR introduces some optional histograms of the BTL and ETL uncalibrated RecHits to check the hit time resolution as a function of the hit amplitude and the hit pseudorapidity. The booking and filling of the new histograms is optional and can be switched on with a configuration flag: the default is OFF.
A ROOT macro is also provided to analyse the uncalibrated RecHits histograms.
PR validation:
The new code has been tested with both the new feature OFF and ON using the WF 34634.0 with CMSSW_12_0_X_2021-05-06-2300.
MemoryReport> Peak virtual size 6392.12 Mbytes
Key events increasing vsize:
[0] run: 0 lumi: 0 event: 0 vsize = 0 deltaVsize = 0 rss = 0 delta = 0
[1] run: 1 lumi: 1 event: 1 vsize = 6392.07 deltaVsize = 0 rss = 3387.42 delta = 0
[2] run: 1 lumi: 1 event: 2 vsize = 6392.11 deltaVsize = 0.046875 rss = 3442.12 delta = 54.6953
[8] run: 1 lumi: 1 event: 8 vsize = 6392.12 deltaVsize = 0.0078125 rss = 3302.1 delta = -140.02
[0] run: 0 lumi: 0 event: 0 vsize = 0 deltaVsize = 0 rss = 0 delta = 0
[10] run: 1 lumi: 1 event: 10 vsize = 6392.12 deltaVsize = 0 rss = 3322.02 delta = 19.918
[9] run: 1 lumi: 1 event: 9 vsize = 6392.12 deltaVsize = 0 rss = 3323.58 delta = 21.4805
[8] run: 1 lumi: 1 event: 8 vsize = 6392.12 deltaVsize = 0.0078125 rss = 3302.1 delta = -140.02
TimeReport> Time report complete in 227.177 seconds
Time Summary:
Event Throughput: 0.088003 ev/s
CPU Summary:
Processing Summary:
Size of the MTD histograms in the DQM root file:
1129.74 KiB MTD/ETL
239.63 KiB MTD/BTL
MemoryReport> Peak virtual size 6366.38 Mbytes
Key events increasing vsize:
[0] run: 0 lumi: 0 event: 0 vsize = 0 deltaVsize = 0 rss = 0 delta = 0
[1] run: 1 lumi: 1 event: 1 vsize = 6366.33 deltaVsize = 0 rss = 3401.11 delta = 0
[2] run: 1 lumi: 1 event: 2 vsize = 6366.38 deltaVsize = 0.046875 rss = 3462.15 delta = 61.0352
[8] run: 1 lumi: 1 event: 8 vsize = 6366.38 deltaVsize = 0.0078125 rss = 3507.35 delta = 45.1992
[0] run: 0 lumi: 0 event: 0 vsize = 0 deltaVsize = 0 rss = 0 delta = 0
[10] run: 1 lumi: 1 event: 10 vsize = 6366.38 deltaVsize = 0 rss = 3527.03 delta = 19.6797
[9] run: 1 lumi: 1 event: 9 vsize = 6366.38 deltaVsize = 0 rss = 3525.76 delta = 18.4102
[8] run: 1 lumi: 1 event: 8 vsize = 6366.38 deltaVsize = 0.0078125 rss = 3507.35 delta = 45.1992
TimeReport> Time report complete in 234.941 seconds
Time Summary:
Event Throughput: 0.0859958 ev/s
CPU Summary:
Processing Summary:
Size of the MTD histograms in the DQM root file:
1129.74 KiB MTD/ETL
239.63 KiB MTD/BTL
MemoryReport> Peak virtual size 6366.63 Mbytes
Key events increasing vsize:
[1] run: 1 lumi: 1 event: 1 vsize = 5854.57 deltaVsize = 0 rss = 3397.2 delta = 0
[2] run: 1 lumi: 1 event: 2 vsize = 5854.62 deltaVsize = 0.046875 rss = 3455.33 delta = 58.125
[4] run: 1 lumi: 1 event: 4 vsize = 6366.62 deltaVsize = 512 rss = 3481.23 delta = 25.9062
[8] run: 1 lumi: 1 event: 8 vsize = 6366.63 deltaVsize = 0.0078125 rss = 3500.05 delta = 18.8164
[0] run: 0 lumi: 0 event: 0 vsize = 0 deltaVsize = 0 rss = 0 delta = 0
[10] run: 1 lumi: 1 event: 10 vsize = 6366.63 deltaVsize = 0 rss = 3517.79 delta = 17.7422
[9] run: 1 lumi: 1 event: 9 vsize = 6366.63 deltaVsize = 0 rss = 3523.39 delta = 23.3438
[8] run: 1 lumi: 1 event: 8 vsize = 6366.63 deltaVsize = 0.0078125 rss = 3500.05 delta = 18.8164
TimeReport> Time report complete in 238.522 seconds
Time Summary:
Event Throughput: 0.0857586 ev/s
CPU Summary:
Processing Summary:
Size of the MTD histograms in the DQM root file:
1205.19 KiB MTD/ETL
509.57 KiB MTD/BTL
@fabiocos @parbol @gsorrentino18