I've restarted the primary and redundant h(t) pipelines at Hanford at GPS second 1165664237. This restart picks up a software update to gstlal-calibration-1.1.2-v1, which contains a couple of bug fixes:
(1) The h(t) data product should now be identical between the primary and redundant pipelines when time-dependent corrections are applied (i.e., the previously observed numerical roundoff error has been addressed);
(2) The pipeline will now run properly in offline mode, which had become a serious problem after the first bug fix referred to above.
The filters file has also been changed; see this aLOG: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=32389
Note, time-dependent corrections to h(t) (the kappa factors) are still being applied in low latency at Hanford, with the exception of changes to the coupled cavity pole frequency.
additional activity before I arrived:
Just FYI.
The problem of big violin (or any big high-Q resonances) is mostly the saturation of ADC (OMC DCPD) or DAC (mostly ESD).
To tell if whatever peak is too big or not, measure the OMC DCPD A IN1 and one of the EY ESD output as shown in the attached.
First of all, you see the time series and OMC DCPD is still very far from its ADC ceiling of +-32k, and ESD output is also very far from its ceiling of +-131k, so you don't need to worry about saturations. Note that you need to set the resolution of dataviewer 16384 and observe for at least 10 seconds before making your judgement.
If these things approach the ceiling you need to damp the worst offender, which you identify by looking at the DARM spectrum, or better, by measuring the DCPD_A_IN1 and ESDOUTF_LL_OUT spectrum (second attachment). In this case, even though we already know that it's still safe, you can see that the 4.7kHz mode is the biggest offender. In DCPD it's about 100 cts RMS or 2*sqrt(2)*100 ~300 cts pp, which is totally negligible compared with DC. In ESDOUTF_LL_OUT, it's about 10k cts RMS or ~30k pp.