This PR re-introduces CRTData in Stage0. #857
Conversation
SFBayLaser
left a comment
SFBayLaser
left a comment
There was a problem hiding this comment.
This change looks to be straightfoward.
What does this mean for output data file size? Imagine a small increase?
|
trigger build larsoft@v10_06_00_02 LArSoft/lar*@LARSOFT_SUITE_v10_06_00_02 SBNSoftware/sbnalg@v10_06_00_05 SBNSoftware/sbnobj@v10_01_01_01 SBNSoftware/sbnanaobj@v10_00_05_02 SBNSoftware/sbndaq_artdaq_core@v1_10_06 SBNSoftware/sbncode@v10_06_00_06 SBNSoftware/icarusutil@v10_06_00_04 SBNSoftware/icaruscode@v10_06_00_06 |
|
✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard |
|
❌ CI build for ICARUS Failed at phase build ICARUS on slf7 for c14:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build ICARUS phase logs parent CI build details are available through the CI dashboard |
|
✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard |
|
❌ CI build for ICARUS Failed at phase ci_tests ICARUS on slf7 for e26:prof - ignored warnings for build -- details available through the CI dashboard 🚨 For more details about the failed phase, check the ci_tests ICARUS phase logs parent CI build details are available through the CI dashboard |
By mistake CRTData were dropped from Stage0. They are needed to fill Calib Ntuples.
Here is a detail of the data size imprint:
Current [no CRTData from Stage0]:
stage0: 37364 KB
stage1: 55246 KB
ntuples: 2059 KB
Proposal [CRTData preserved in Stage0]
stage0: 38871 KB
stage1: 56812 KB
ntuples: 2456 KB