Fixed of FDD digit2raw and digit writer/reader#5617
Conversation
mbroz84
commented
Mar 4, 2021
- Fix of warnings seen when reading raw data made from MC digits
- DigitWriterSpec moved from Steer to FDDWorkflow, other obsolete DigitWriter deleted
- DigitReader reading Trigger Inputs branch
shahor02
left a comment
There was a problem hiding this comment.
Hi @mbroz84
thanks for fixes, but there are still some problems:
-
when reading / writing digits related to raw data, the MC (and triggerInputs) must be disabled.
I've fixed this and opened a PR in your repo, please merge it and forcepush). -
testing on 200 pbpb events generated as
o2-sim-digitizer-workflow
o2-fdd-digit2raw --configKeyValues "HBFUtils.nHBFPerTF=128;HBFUtils.orbitFirst=0" -o raw/FDD
o2-raw-file-reader-workflow --input-conf raw/FDD/FDDraw.cfg | o2-fdd-flp-dpl-workflow
I see differences between the digits from simulation and decoding, e.g. (decoded is red one: there is apparently an overflow leading to a truncation in the amplitude, while nChanA looks like not filled but differing due to different initialization in simulation and decoding (-1 / 127).

- converting the same digits to raw with 16 orbits per TF (and obtaining the same data in 3 TFs), and running
o2-raw-file-reader-workflow --input-conf raw16/FDD/FDDraw.cfg --configKeyValues "HBFUtils.nHBFPerTF=16;HBFUtils.orbitFirst=0" | o2-fdd-flp-dpl-workflow
I see difference (this one is red) wrt the raw data from the previous exercise:

Apart from that, I see only 1 entry in the output digits tree, while there should have been 3 (==nTF)
I've uploaded the data you need to reproduce this here:
tar cvzf fdd.tar.gz fdddigits.root o2sim_g*.root raw16/FDD raw/FDD
fdddigits.root
o2sim_geometry.root
o2sim_grp.root
raw16/FDD/
raw16/FDD/fdd.raw
raw16/FDD/FDDraw.cfg
raw/FDD/
raw/FDD/fdd.raw
raw/FDD/FDDraw.cfg
Could you please fix this and make sure that the output of both single- and multi-TF reconstruction agrees with simulation.
|
ps: it may happen that having just 1 entry in the output digits tree in case of multiple TF decoding is due to the problem in RootTreeWriter, I see it also in some other detectors. I will check this, meanwhile, please check the p.2. |
|
@mbroz84 your digitWriter was not storing more than 1 TF because it was initialized with request to close the tree after 1st event. I've fixed this in the PR open in your repository. So, only the problem if different content of simulated and decoded digits remain. |
disable MC in DigitWriter/Reader when used with raw data
|
The inconsistencies in digits after Digit2Raw + Raw2Digit should be fixed now. |
|
Hi @mbroz84 thanks, but the CI produces this error: |
|
Hi [~mbroz] I've run with your PR over the data from my previous message, the errors are gone but in both (re-)generated and decoded digits the I prefer to merge this to avoid errors in the full system test, the fix can be added in other PR |