Update TICL & HGCal simulation truth validation to use new simulation truth collections, and simplify validation to use only SimCluster dataformat#51047
Conversation
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-51047/49491
|
|
A new Pull Request was created by @tcuisset for master. It involves the following packages:
@Martin-Grunewald, @Moanwar, @civanch, @cmsbuild, @ctarricone, @gabrielmscampos, @jfernan2, @kpedro88, @mandrenguyen, @mdhildreth, @mmusich, @rseidita, @srimanob can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
@cmsbuild please test |
|
@cmsbuild, please abort |
|
test parameters:
|
|
@cmsbuild, please test |
|
-1 Failed Tests: RelVals Failed RelVals |
|
Pull request #51047 was updated. @Martin-Grunewald, @Moanwar, @battibass, @civanch, @cmsbuild, @ctarricone, @ftorrresd, @gabrielmscampos, @jfernan2, @kpedro88, @mandrenguyen, @mdhildreth, @mmusich, @rseidita, @srimanob can you please check and sign again. |
|
please test |
|
-1 Failed Tests: Build Failed BuildI found compilation warning when building: See details on the summary page. |
|
I had accidentally introduced a spurious semicolon in the last commit, now the build should be fixed |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-51047/50137
|
|
Pull request #51047 was updated. @Martin-Grunewald, @Moanwar, @battibass, @civanch, @cmsbuild, @ctarricone, @ftorrresd, @gabrielmscampos, @jfernan2, @kpedro88, @mandrenguyen, @mdhildreth, @mmusich, @rseidita, @srimanob can you please check and sign again. |
|
please test |
|
-1 Failed Tests: RelVals Failed RelValsExpand to see more relval errors ... |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-51047/50144
|
|
Pull request #51047 was updated. @Martin-Grunewald, @Moanwar, @battibass, @civanch, @cmsbuild, @ctarricone, @ftorrresd, @gabrielmscampos, @jfernan2, @kpedro88, @mandrenguyen, @mdhildreth, @mmusich, @rseidita, @srimanob can you please check and sign again. |
|
please test |
|
+1 Size: This PR adds an extra 24KB to repository Comparison SummarySummary:
Max Memory Comparisons exceeding threshold@cms-sw/core-l2 , I found 1 workflow step(s) with memory usage exceeding the error threshold: Expand to see workflows ...
|
|
Hi @tcuisset, Thanks a lot for fixing and updating the PR! Could you please have a look at the memory increase? It seems to be ~70 MB above the threshold. Is that expected? |
…om eventContent to reduce the memory usage when running on pileup
Hi @Moanwar , I've reduced the number of associators that run by default in the config, so it should reduce the memory usage when running with pileup now. |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-51047/50208
|
Thanks a lot @tcuisset , sounds good , lets test again |
|
@cmsbuild please test |
|
Pull request #51047 was updated. @Martin-Grunewald, @Moanwar, @battibass, @civanch, @ctarricone, @ftorrresd, @gabrielmscampos, @jfernan2, @kpedro88, @mandrenguyen, @mdhildreth, @mmusich, @rseidita, @srimanob can you please check and sign again. |
|
+1 Size: This PR adds an extra 36KB to repository Comparison SummarySummary:
|
Thanks @tcuisset, it seems to be working. |
Mostly the diagram is still accurate. For the left part (SimCluster part), there is no change. For the right part, the SimTracksters for "merged" and "legacy" are disabled by default (but the "CaloParticle" and "Boundary-track" are still enabled). But you just need to uncomment a few lines of python config to enable them back. The related associators are also disabled (they were not shown on the diagram). |
|
+1 |
|
+simulation |
|
+dqm |
PR description:
This is a follow-up on #50578, which had updated CaloTruthAccumulator to produce multiple SimCluster collections, with the intent to use only one dataformat for calorimeter truth information (instead of CaloParticle / SimCluster dataformat dichotomy).
This PR updates the TICL/HGCal validation to use the new SimCluster collections produced in CaloTruthAccumulator.
Use of CaloParticle dataformat is replaced nearly everywhere with the use of caloparticles in SimCluster dataformat (with just some remaining usage related to simTime).
Summary of the setup after this PR:

Documentation
Slides at TICL meeting
Slide 7 of HGCAL presentation at NGT MC truth workshop
Details:
PR validation:
Tested with various Phase 2 workflows:
There should not be any validation differences in reco objects. Very minor differences in validation could be caused by the switch from "legacy" to "boundary" SimCluster (which could change slightly validation results for status=1 photons that do not convert before reaching the calorimeter)
FYI @felicepantaleo @waredjeb