identification of FEDid causing sync loss in FlowchartCase1
Created by: andreh12
FlowchartCase1 seems to search for FEDs in TTS out of sync state for this case which is however unrelated (out of sync FEDs are relevant for flow chart case 3).
Sync loss is the condition when an unexpected event number was received (e.g. event 3 after event 1).
@mommsen confirmed that currently the only way to determine the FEDid which caused a sync loss condition on the RU from flashlist information is to check the RU error message.
Here is a test case: /DAQExpert//?start=2016-10-26T05:55:59+02:00&end=2016-10-26T05:58:32+02:00
The corresponding error message from the log4j log is:
SyncLoss: Caught exception: exception::MismatchDetected 'Mismatch detected: expected evb id runNumber=284006 lumiSection=390 resyncCount=233 eventNumber=4910173 bxId=3388, but found evb id runNumber=284006 *resyncCount=234 eventNumber=1 bxId=94 in data block from FED 583 (CTPPS_TOT)
In the corresponding json data (see e.g. /DAQExpert//snapshot?time=%222016-10-26T03%3A56%3A58.178Z%22
) it looks like the message is truncated to 80 characters:
"errorMsg": "Caught exception: exception::MismatchDetected 'Mismatch detected: expected evb i",
also in the flashlist dump (/daqexpertflashlists/flashlists/RU/2016/10/26/3/1477454220204.smile
) this is already truncated:
"errorMsg" : "Caught exception: exception::MismatchDetected 'Mismatch detected: expected evb i",