LIVE calc. crudely accounts for correlations. Need offline calc. DEAD TIME: [ 0]: 20.53% [++]: 59.37% [--]: 59.26% [+-]: 59.11% [-+]: 59.19% TRIGGER RATES: PRES/REAL T1[ 0] : 2.6/8286.7 Hz T2[ 0] : 1.0/417.7 Hz T3[ 0] : 3.3/267.9 Hz T4[ 0] : 0.0/12.7 Hz T5[ 0] :14.5/14.5 Hz T6[ 0] : 5.3/1868.7 Hz T7[ 0] :12.7/829130.1 Hz T8[ 0] :10.2/1024.0 Hz
Adding up the rates give ~40 Hz (not counting T7, which shows up here but bypasses the Trigger supervisor). Is this understood?
Also the deadtimes are wildly different for different helicity states.
This is the case for a full statistics 'normal' run Run 5332 (14 uA):
LIVE calc. crudely accounts for correlations. Need offline calc. DEAD TIME: [ 0]: 18.16% [++]: 27.11% [--]: 11.80% [+-]: 26.38% [-+]: 12.65%Is the formula for the end of run script just completely broken, or is there a more serious problem?