Change production config to point at replay data

This allows for the detchar checks (most notably the omegascans) to work on the early warning test, which is using replay data. This needs to be reversed once live data comes back, as noted in this issue #349 (closed).

added Configuration Data Quality labels

mentioned in issue #349 (closed)

The qscans appear for L1 but not for H1/V1. Do we understand of this distinction among the instruments?

Here's two: https://gracedb.ligo.org/superevents/MS200615ce/view/ https://gracedb.ligo.org/superevents/MS200614ct/view/

approved this merge request

OK, thanks. Is the presence of the L1 qscan expected for one of these events? If datafind is failing, what is exactly plotted in that L1 scan?

OK, that explains it. I was alarmed when seeing the L1 qscan on a known detection without any obvious signal present! Thanks again for the quick response and action.

Please remember that comments on MRs are public.

approved this merge request

resolved all threads

merged