Incorrect reporting of data size from Fragments in Containers when upgraded
Because of a minor error in ContainerFragment.hh, the reported data sizes for contained Fragments that have headers with different size from the current version are off by the difference in size between the previous version and the current. This was caused by an incorrect assumption when allocating the output Fragment in ContainerFragment::at.
#3 Updated by Pengfei Ding 12 months ago
Ran rawEventDump under artdaq v3_06_01 w/wo the bugfix on files generated by ToySimulator under artdaq v3_05_00 and v3_06_01.
Confirmed the following:
For fragment generated under v3_05_00, with the bug fix, rawEventDump reports:
1) fragment type 3, timestamp 9623, has metadata true, and sizeBytes 240 (hdr=24, data=208, meta (calculated)=8)
without the bugfix, it reports:
1) fragment type 3, timestamp 9623, has metadata true, and sizeBytes 240 (hdr=24, data=216, meta (calculated)=0)
For fragment generated with artdaq v3_06_01, rawEvetnDump reports the following w/wo the bugfix:
1) fragment type 3, timestamp 0, has metadata true, and sizeBytes 248 (hdr=32, data=208, meta (calculated)=8)