After reading Keita's alog 32025, I used the template to passively look at coherance over this lock, and pitch is at 0.9 and has been and this was not in the previous lock, interestingly enough, though yaw was worse at the end of the last lock.
Going out of Observe now to reduce the coherance made sense in light of the long lock we just had.
paasive a2l checks:
Here's what's odd - pitch and yaw coherances are better an hour after running a2l, but the entire region 10Hz to 40Hz is elevated, and the range has gone down.
Plot start time is 20:32:06UTC.
New plot - start time 20:43:21 - coherence is higher but 10-40Hz is not elevated.
Smaller coherence with larger DARM noise at 20Hz means that the excess noise is not due to a2l coupling. When something other than a2l coupling dominates the noise at 20Hz, running or not running a2l is irrelevant, so please don't run it.
Again I'll say this, it's a perfect project for a fellow to write a script to plot the coherence and DARM BRMS for 15-25Hz or so VS time. With such a script it would be easy for operators to determine (and show to others) if running a2l would be beneficial or not.
Anyway, going out of OBSERVE to run a2l script is OK when all of below are satisfied.
Do it sparingly, single IFO data is still valuable for CW.
(Added later at 13:30 local time: If the coherence is super bad like Cheryl's "before" plot for PIT, there's not much point in waiting hours to run a2l, but make sure that the alignment itself is not suspect.)