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 update #27607
MTD validation update #27607
Conversation
…tograms of BTL energy and time resolution, and BTL occupancy vs hit energy
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27607/11047
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27607/11048
|
A new Pull Request was created by @casarsa (Massimo Casarsa) for master. It involves the following packages: SimGeneral/MixingModule @andrius-k, @kmaeshima, @schneiml, @civanch, @mdhildreth, @cmsbuild, @jfernan2, @fioriNTU can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@casarsa I do see plots (6) in BTL but not in ETL like you said in the description. This is happening in the 3 Phase2 workflows. Is this expected? |
@jfernan2 For the time being those checks have been implemented only for BTL. |
@casarsa OK, I was confused by your statement: |
+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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
@@ -4,4 +4,5 @@ | |||
<use name="Geometry/Records"/> | |||
<use name="Geometry/MTDGeometryBuilder"/> | |||
<use name="DQMServices/Core"/> | |||
<use name="hepmc"/> |
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.
@casarsa why this dependence?
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.
That surprised me too. It seems it's required by SimDataFormats/CrossingFrame/interface/CrossingFrame.h, that includes HepMCProduct.h.
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.
By quick look it looks like the include of HepMCProduct.h
could easily be removed from SimDataFormats/CrossingFrame/interface/CrossingFrame.h
.
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.
Regardless of the possible cleanup of SimDataFormats/CrossingFrame/interface/CrossingFrame.h
, the proper dependence to be added here is SimDataFormats/CrossingFrame
. That should make the explicit dependence in hepmc
uneecessary (as SimDataFormats/CrossingFrame
depends on that).
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.
@makortel let's open a separate issue for that
MixCollection<PSimHit> btlSimHits(btlSimHitsHandle.product()); | ||
|
||
// --- Loop over the BLT SIM hits | ||
std::unordered_map<uint32_t, MTDHit> m_btlSimHits; |
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.
@casarsa this energy accumulation is equivalent to that used in the digi - rechit construction, am I correct?
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.
Yes, you are. In both cases I'm starting from the SimHits and am accumulating the energy released in the same BTL crystal.
+1 |
PR description:
This is an update of the MTD validation package:
PR validation:
The updated code has been compiled in the release CMSSW_11_0_X_2019-07-24-2300 and tested with the 2026D41 WFs 20434 and 20634 with PU200.
The total size of the MTD monitoring plots is:
476.28 KiB MTD/ETL
237.66 KiB MTD/BTL
WF 20434 report (step 3):
MemoryReport> Peak virtual size 4673.77 Mbytes
Key events increasing vsize:
[5] run: 1 lumi: 1 event: 5 vsize = 4641.77 deltaVsize = 0.0351562 rss = 3226.27 delta = 29.5234
[2] run: 1 lumi: 1 event: 2 vsize = 4641.74 deltaVsize = 0.304688 rss = 3196.74 delta = 1.77734
[7] run: 1 lumi: 1 event: 7 vsize = 4673.77 deltaVsize = 32 rss = 3273.65 delta = 76.9062
[0] run: 0 lumi: 0 event: 0 vsize = 0 deltaVsize = 0 rss = 0 delta = 0
[0] run: 0 lumi: 0 event: 0 vsize = 0 deltaVsize = 0 rss = 0 delta = 0
[9] run: 1 lumi: 1 event: 9 vsize = 4673.77 deltaVsize = 0 rss = 3287.06 delta = 13.4141
[8] run: 1 lumi: 1 event: 8 vsize = 4673.77 deltaVsize = 0 rss = 3287.99 delta = 14.3438
[7] run: 1 lumi: 1 event: 7 vsize = 4673.77 deltaVsize = 32 rss = 3273.65 delta = 47.3828
TimeReport> Time report complete in 506.789 seconds
Time Summary:
Event Throughput: 0.259417 ev/s
CPU Summary:
Processing Summary:
WF 20634 report (step 3):
MemoryReport> Peak virtual size 9869.82 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 = 8169.59 deltaVsize = 0 rss = 6721.41 delta = 0
[2] run: 1 lumi: 1 event: 2 vsize = 9833.69 deltaVsize = 1664.11 rss = 6793.38 delta = 71.9688
[7] run: 1 lumi: 1 event: 7 vsize = 9865.82 deltaVsize = 32 rss = 6828.83 delta = 35.4531
[10] run: 1 lumi: 1 event: 10 vsize = 9869.82 deltaVsize = 4 rss = 6832.15 delta = 3.31641
[8] run: 1 lumi: 1 event: 8 vsize = 9865.82 deltaVsize = 0 rss = 6842.48 delta = 13.6445
[7] run: 1 lumi: 1 event: 7 vsize = 9865.82 deltaVsize = 32 rss = 6828.83 delta = -288.48
[10] run: 1 lumi: 1 event: 10 vsize = 9869.82 deltaVsize = 4 rss = 6832.15 delta = 3.31641
TimeReport> Time report complete in 2705.11 seconds
Time Summary:
Event Throughput: 0.00401843 ev/s
CPU Summary:
Processing Summary: