Basic Statistics: The number of segments found in the HW timeline is 739 The number of triggers found in the log file is 724 The number of triggers with matching segments is 721 out of 724 triggers The number of segments with matching triggers is 721 out of 739 segments Here comes the list of triggers with no matching segment: 944668815.0 - Omega Scan shows successful at L1, not H1 954576066.0 - Omega shows successful at both sites 968169966.0 - Seems successful Here comes the list of segments with no trigger: [[931788884 931792427] - ??? [935561686 935561894] - Comp; no data [942911884 942912093] - Comp; no data [944667720 944667928] - ??? [946137485 946137694] - Comp; no data [946223886 946224094] - Successful injection, exp SNR < 1 [946396685 946396894] - Comp; no data [951321484 951321693] - Comp; no data [951580725 951580934] - Comp; no data [963244990 963245198] - Comp; no data [966378190 966378373] - Blind [967021102 967021285] - Blind [967475246 967475454] - ??? (Big dog testing?) [967483053 967483262] - ??? (Big dog testing?) [968654445 968654628] - Blind [971351885 971352094] - Comp; no data [971528286 971593333] - End of run testing [971621885 971622015]] - Injection at last second of S6 "Comp; no data" indicates a compromised injection where there is no data available at the merger time. This is expected - such injections show up in the Timeline, but are not recoverable in the data, so are not in the "simple" log files.