Reports until 01:23, Wednesday 07 August 2019
H1 DetChar (DetChar, ISC)
corey.gray@LIGO.ORG - posted 01:23, Wednesday 07 August 2019 - last comment - 13:48, Wednesday 07 August 2019(51093)
Another Period of Odd Noise Observed On H1 But At Different Frequency (this time roughly 8-30Hz)

As mentioned earlier in my shift transition alog, noticed increased noise on H1 through various computers on the wall in the Control Room.  For the most part I do not recall any odd activity for the DARM bands in question (10-20 & 20-34Hz), so when they are noisy, it's pretty obvious & so then an investigation begins. 

Overall there was a noticeably noisy period, then it died down (but lingered), and then went quiet...but still getting glitches.  Unfortunately I only snapped screenshots of the BLRMS striptool.  (I was too slow to grab screenshots of the DARM spectra as well as the MICH/PRCL/SRCL spectra.

Since this is a much different feature from the high-freq noise I observed last night, I did not run Keita's measurement.

Here is an updated summary:

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 06:15, Wednesday 07 August 2019 (51096)

Just to give an update, we have not had the really noisy stretch like we did at the beginning of this current lock, BUT this 8-30Hz noise has not gone away either.  Attached is a look at the last 7+hrs & you can see the noise has been fairly regular for the entire lock.

Scanning through Summary Pages tonight's lock as seen with DMT OMEGA looks somewhat similar over the last few days (i.e. since 8/2), and 2nd attachment is looking at 8/5 where we have a long lock which also has this low-freq noise.

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 13:43, Wednesday 07 August 2019 (51103)DetChar, OpsInfo
Corey -- There's a brief comment in LHO aLOG 51034, and it's come up verbally in commissioning meetings, but not clearly stated in any aLOGs -- sorry for not catching you up! #OwlsAreTough

Here's the story: 

This excess glitchiness below ~15 Hz is a result of the new alignment position of the beam going in to the OMC. We think this alignment position is making the OMC (and thus DC readout, DARM, and DETLAL EXTERNAL) more sensitive to scattered light in and around the OMC. We made this alignment change at the tail end of Aug 1 2019, as a result of the new global alignment position after losing our reference on July 30 -- which is why it's been seen since Aug 2. We're not super happy with it, but it did recover some optical gain that we lost else where. The tentative plan is to reduce the gain of the OMC ASC loops to see if this glitchiness goes away, if that doesn't work, we may consider a new alignment in to the OMC.

We'll try to find a way to keep owl shifters better posted!
corey.gray@LIGO.ORG - 13:48, Wednesday 07 August 2019 (51104)

No worries!  I figured this was proably related to recent alignment work (due to the camera bump).  I didn't know a whole lot about this recovery because of being away on vacation and then did not have time to catch up on alogs last night due rough 1st half of the graveyard trying to relock H1.    THANKS for explaning this though!  (OK, time to sleep for tonight's shift.)