[Sheila, Jenne, Kiwamu, Patrick]
We lost lock about 8 hours ago, and haven't been able to lock since. Sheila suggested we look at the Yarm ALS PDH control signal, since that has caused trouble in the past. Indeed, we saw glitches.
We were looking at H1:ALS-Y_REFL_CTRL_OUT_DQ, and saw very obvious glitches at about a 1Hz rep rate. At the same time, we see dips in the ALS transmitted power (H1:ALS-Y_TR_A_LF_OUT) down to 0.5 or lower from a nominal locked value of 1.0. We also see much smaller glitches in the Xarm, often at the same time as the Yarm glitches, but not always. The Xarm power dips are also much smaller than those for the Yarm. The first attachment shows the REFL CTRL signals. We don't save the transmitted powers, so I don't have a good plot of those.
We have certainly seen these glitches before, and there are rumors that it seems to happen more often when it's raining. Not totally clear how that's related - is the extra humidity doing something to us?? Anyhow, in the past the solution has always been to wait it out, and it'll go away. Colloquially the problem is usually gone by the time anyone drives down to the end station.
We went down to the end station and tried several things while looking at the PLL beatnote, but none of them changed the glitches. At a few times, Sheila noted that there were peaks around the beatnote, 8MHz above and below. We're not totally sure what those are.
Suspecting that the PSL was somehow involved since we often see glitches simultaneously in the X and Y arms, we closed the light pipe shutter for the PSL ALS beam that goes to ISCT1. We were hoping that if there were some kind of feedback from the Yarm to the PSL that was then getting sent to the Xarm through the PLL, this would prevent that. However, no change. The light pipe's shutter was re-opened.
We then went back to the Yend to lock the green arm, but bypassing the PLL, thus eliminating the PSL light from the system. We didn't see any tell-tale dips in the transmitted power while we did this, but when we put the system back to normal, the problem seemed to have already resolved itself. So, it's not a 100% conclusive test.
We're going back to trying to lock for now.