In TOF unpacker algo, add count of hit messages rejected due to bad epoch + final printout

requested review from @v.singhal

assigned to @p.-a.loizeau

@v.singhal This is an attempt to add the printout for the errors you saw in some of the Au runs.

Could you please let me know which run number I should use to test it or maybe test the branch yourself if you have the time?

Dear @n.herrmann, @i.deppner,

you have been identified as code owner of at least one file which was changed with this merge request.

Please check the changes and approve them or request changes.

added CodeOwners label

Dear @p.-a.loizeau,

Getting below error message

[ERROR] CbmTofUnpackAlgo::ProcessEpoch => Error global epoch, DPB 0xabc4 last 0x48907a, current 0x48907c, diff 2, raw 0x0000ff0048907c01, NoErr 29
[ERROR] CbmTofUnpackAlgo::ProcessEpoch => Ignoring data until next valid epoch

List of such runs is (which I unpacked) | 2183 | | 2184 | | 2188 | | 2189 | | 2191 | | 2193 | | 2211 | | 2214 | | 2216 | | 2217 | | 2227 | | 2228 | | 2229 | | 2230 | | 2231 | | 2232 | | 2233 | | 2235 | | 2238 | | 2239 | | 2242 | | 2243 | | 2244 | | 2245 | | 2246 | | 2247 | | 2252 | | 2258 | | 2259 | | 2260 | | 2261 | | 2262 | | 2264 | | 2265 | | 2266 | | 2272 | | 2274 | | 2277 | | 2281 | | 2282 | | 2289 | | 2290 | | 2297 | | 2301 | | 2302 | | 2303 | | 2304 | | 2305 | | 2508 | | 2516 | | 2516 | | 2522 | | 2532 | | 2559 | | 2560 | | 2561 | | 2568 | | 2569 | | 2570 | | 2582 | | 2582 |

Such EPOCH loss error messages are from uranium (March) and gold (June) runs only. Manually I tried to list particular time slice number of each run in which such error messages occured, but till now could not complete (It is a cumbersome task, I'll share with you the google sheet for the same). Do not know will we gain any thing from timeslice number info.

Other than this, in uranium runs (March), also seen below warning message :-

[WARN] CbmTofUnpackAlgo::unpack => Could not find the gDPB index for FLIM id 0xabc4 in timeslice 0 in microslice 0 component 19
If valid this index has to be added in the TOF parameter file in the DbpIdArray field
[WARN] CbmTofUnpackAlgo::unpack => Could not find the gDPB index for FLIM id 0xabc5 in timeslice 0 in microslice 0 component 20
If valid this index has to be added in the TOF parameter file in the DbpIdArray field
[WARN] CbmTofUnpackAlgo::unpack => Could not find the gDPB index for FLIM id 0xabc6 in timeslice 0 in microslice 0 component 21
If valid this index has to be added in the TOF parameter file in the DbpIdArray field
[WARN] CbmTofUnpackAlgo::unpack => Could not find the gDPB index for FLIM id 0xabc7 in timeslice 0 in microslice 0 component 22 
If valid this index has to be added in the TOF parameter file in the DbpIdArray field

Other than these in run 2242, unpacking crashed with below message

[FATAL] CbmTofUnpackAlgo::ProcessEpoch => Stopping there, system is not synchronized and send corrupt data

Thanks for putting this information in the output. Regards Vikas

Dear Pierre,

Changes looks okay, but I did not run the branch.

two more general point,

(1) at the end of unpacking few summary information is displayed below an example:

[INFO] SourceTsArchive::Close() Let's hear some famous last words:
[INFO] CbmRecoUnpack::Finish() I do let the unpackers talk first :
[INFO] CbmMuchUnpackAlgo::Finish.-------------------------
 Unpack process :
 4344 Timeslices with
 0 Raw Messages,
 862900755 Digis

Here 4344 are number of microslices, in all processed timeslices, in which MuCh hit messages were present, so "4344 Timeslices" should be "4344 Microslices". (May be corrected).

(2) Can in the beginning of unpacking output messages all the input file names be displayed in the order in which unpacker pick and process? (In general we use wild character in input file name) and sometime confuse in which sequence, input files will be processed. Probably in offline monitoring, such order is displayed.

Thanks and regards

Vikas.

marked this merge request as ready

added Reconstruction mCBM labels

approved this merge request

added 7 commits

• 5d2bee93...d5af4b0a - 6 commits from branch computing:master
• 959c14d1 - In TOF unpacker algo, add count of hit message rejected due to bad epoch + final printout

Compare with previous version

@p.-a.loizeau,

since @v.singhal approved the MR in my opinion it can be merged.

resolved all threads

merged