Closed hristovaivana closed 2 years ago
I was able to successfully run readoutapp_gen
with these changes and generate a configuration.
When I tried to run it, I saw messages in the logfile along the lines of PdspChannelMapService: Bad fiber number, falling back to 1. Ununderstood fiber number: 23
. I'm not sure if I'm doing something wrong (probably). This generally look good.
Hi Kurt, many thanks! Yes, these errors are a good point. This could be caused by the content in the input file tp_frames.bin
or the decoding of those binary data. That would be good to fix to remove those errors, I'll be having a look at that and the fixes will eventually affect the fdreadoutlibs
or detdataformats
packages (assuming the input file is ok). That's why this standalone test is useful for us to find and fix such problems.
Oh, I know the reason now for these errors. This could/likely be because the candidate release has switched to the WIB2 format for the FW TPs, and tp_frames.bin
contains WIB1 data. I need to prepare a new tp_frames.bin
file from a WIB2 data capture or simulated patterns file.
I created and tested with a WIB2 tp_frames.bin
file, located here https://cernbox.cern.ch/index.php/s/FqMXxSpM3WjgeCN.
The errors Kurt noticed above no longer appear in the logs.
Following Pierre's fix for the new boot configuration, this PR is to 1) fix error he reported when running
nanorc
with the configuration fromand a
tp_frames.bin
file from https://cernbox.cern.ch/index.php/s/zaOYX1tPT4cG3Fx2) add options to set, a) the offline channel map name, and b) a constant for the stitching algorithm, from the command line.
This standalone readout configuration generation was tested and works with the following setup