| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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).

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.
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
|
@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. |
Sorry, something went wrong.
disable MC in DigitWriter/Reader when used with raw data
|
The inconsistencies in digits after Digit2Raw + Raw2Digit should be fixed now. |
Sorry, something went wrong.
|
Hi @mbroz84 thanks, but the CI produces this error: /mnt/mesos/sandbox/sandbox/o2/sw/SOURCES/O2/5617/0/Detectors/FIT/FDD/reconstruction/src/ReadRaw.cxx:84:23: error: narrowing conversion of '(& lut)->o2::fdd::LookUpTable::getChannel(link, ((int)((long unsigned int)eventData[(2 * i)].o2::fdd::EventData::<anonymous>.o2::fdd::EventData::<unnamed union>::<anonymous>.o2::fdd::EventData::<unnamed union>::<unnamed struct>::channelID)))' from 'int' to 'uint8_t {aka unsigned char}' inside { } [-Werror=narrowing]
chData = {int(lut.getChannel(link, int(eventData[2 * i].channelID))),
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/mnt/mesos/sandbox/sandbox/o2/sw/SOURCES/O2/5617/0/Detectors/FIT/FDD/reconstruction/src/ReadRaw.cxx:99:23: error: narrowing conversion of '(& lut)->o2::fdd::LookUpTable::getChannel(link, ((int)((long unsigned int)eventData[((2 * i) + 1)].o2::fdd::EventData::<anonymous>.o2::fdd::EventData::<unnamed union>::<anonymous>.o2::fdd::EventData::<unnamed union>::<unnamed struct>::channelID)))' from 'int' to 'uint8_t {aka unsigned char}' inside { } [-Werror=narrowing]
chData = {int(lut.getChannel(link, (eventData[2 * i + 1].channelID))),
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
Sorry, something went wrong.
|
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 nChanA/C, nTimeA/C and amplA/ are empty. Could you check please? I prefer to merge this to avoid errors in the full system test, the fix can be added in other PR |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.