The problem reported by Cheryl from the owl shift (alog 54008) is the same thing as we experienced before (alog 53965), 3MHz beat note degrades as SQZ ASC tilts ZMs, eventually ASC runs away, SQZ guardian resets ASC, beat note goes back to normal, and it repeats it many, many times (1st attachment). We had the same problem in the afternoon.

We first tried to relieve the ASC output by moving ZM2 YAW manually, but the runaway behavior only got faster.

Then we checked the dark offset of ASC-AS_A_RF42 and AS_B for all I and Q channels after closing the beam diverter and some of them were 20 to 30, which is significant as the sum channel is only 150-160 counts when the beam diverter is open. Usually an offset of 20 to 30 counts is not huge, but in this case the signal is very small, therefore we want to monitor this periodically.

After adjusting this, the running away behavior was gone. 2nd and 3rd attachment shows the sdf diff (except for ZM1 P offset because it was unmonitored, we changed the setting to monitor it).

Daniel also found that the NLG was somewhat lower than before.  H1:SQZ-SHG_LAUNCH_DC_POWERMON keeps creeping up (6.9 today VS 5.2 on Dec/17) though OPO TRANS is still 1.0, and CLF REFL 6MHz monitor was ~ -30.5 instead of -29.5-ish. Daniel changed the OPO temperature (H1:SQZ-OPO_TEC_SETTEMP) from 33.246 to 33.214 degree Celsius to gain 1dB or so for H1:SQZ-CLF_REFL_RF6_DEMOD_RFMON. That doesn't mean that degradation is OK, we have to keep monitoring.

I have been using the BSC10 -X door central viewport to make movies of the flashing of scattered light from ETMY. Replacing the bellows requires large forces, so, after consulting with Ed and Jason, I have left the bellows disconnected from the viewport, but with the open end covered in aluminum foil, and I have placed a standard viewport cover over the viewport in the BSC door. The VEA is thus laser safe. The beam that travels through this bellows is from the TMS, but we have been leaving the beam diverter closed at all times, so there is no beam currently, and this shouldnt affect operations. I will put the bellows back on when we arent trying to keep locked and I can apply large forces (e.g. a Tuesday or earthquake).

TITLE: 12/20 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
INCOMING OPERATOR: Camilla
SHIFT SUMMARY: an active night for H1, in and out of Observe, currently in Observe
LOG:

• 08:53 - H1 in Observe
• 11:57 - H1 in commissioning - lockloss, alog 54006
• 13:52 - H1 in Observe
• 14:16 - H1 in commissioning - ITMX mode8 rung up
• 14:43 - H1 in Observe - range at 110Mpc, and violins damping, though beginning of this stretch stil has excess violin mode noise
• 15:04 - H1 in commissioning - beam diverter /  SQZ, H1 out of Observe
  • this corrected itself for about 3 minutes, then 9 more cycles in about 20 minutes
• 15:37 - H1 in Observe
• 15:38 - H1 in commissioning - beam diverter /  SQZ, H1 out of Observe
  • manually cycled the beam diverter, SQZ locked
• 15:53 - H1 in Observe
• 15:55 - H1 in commissioning - beam diverter /  SQZ, H1 out of Observe
  • took every SQZ guardian to Down, then Init, then relock
• 16:00 - H1 in Observe

Violin Current State:

• ITMX: modes 7 and 8 have modified damping gains
  • mode 7 nominal is +10, was at +20 for over 2 hours, set back to nominal of +10
  • mode 8 nominal is +10, currently at -4, lscparams gain new set to -4
  • violin guardian will need to be reloaded to encorporate new mode 8 gain sign
  • modes 7 and 8 should be watched at next relocking
• ETMYL modes 1 and 6 have modified damping gains
  • mode 1 nominal is 0.1, currently at 0.5
  • mode 6 nominal is 0, currently at -2
  • these are working, but not ready for prime time

TITLE: 12/20 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 114Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    SEI_CONF state: USEISM
    Wind: 17mph Gusts, 15mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.69 μm/s
QUICK SUMMARY: Locked 2h25, high microseism, some wind. Watching ITMX Mode 8 as it is rung up.

Lockloss quad-fecta:  Glitch, EQ ground motion, useism, and wind.

CURRENT ENVIRONMENT:
    SEI_CONF state: USEISM
    Wind: 18mph Gusts, 15mph 5min avg
    Primary useism: 0.19 μm/s
    Secondary useism: 0.75 μm/s

Tonight I started looking at ITMX modes that are close in frequency.  Mode 7 is at 502.784, and mode 8 is at 502.909.  I checked the damping filters, and mode 8 damping filter was biased toward the mode 7 peak, so I shifted that bias to be away from the mode 7 peak, saved and loaded the filter file.  On can see where I loaded the new filter because the drive on mode 8 starts to grow, and the LOG10 signal increases.  I turned the gain to zero, and waited, and then tried a smaller positive gain, and watching dtt, I could see that again mode 8 was ringing up, so I tried a negative gain, and at the time of the snapshot mode 8 gain was -20, and the mode was damping/damped quite nicely.  Mode 7 gain remains at it's nominal of +10.   Now that mode 8 is damped, I'm turning down the gain, and will alog that number at the end of my shift.  Mode 7 and mode 8 damping filter bode plots, and the time series showing the -20 gain on mode 8 are attached below.

TITLE: 12/20 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 110Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_CONF state: USEISM
    Wind: 13mph Gusts, 11mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.77 μm/s
QUICK SUMMARY:  TJ was locking when I arrived, I did nothing, H1 in Observe

<b>TITLE:</b> 12/20 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
<b>STATE of H1:</b> Lock Acquisition
<b>INCOMING OPERATOR:</b> Cheryl
<b>SHIFT SUMMARY:</b> A 31 hour lock was ended by a nearby earthquake. I lost lock a few times while the DRMI ASC was trying to engage, so I decided to run an initial alignment. Made it through DRMI 2 times since then.
<b>LOG:</b>

• 0642 Lock loss

A surprise nearby earthquake showed up faster than I could react. Still nothing on seismon or USGS.

Locked for 29 hours. No issues to report.

Several changes to the lock clock:

• it is now zeroed when going back into NLN (previously it was zeroed at the time of lock loss) so that the lock duration can be viewed after lock is lost.
• to indicate whether it is an incrementing clock or frozen, it is GREEN when running and WHITE when frozen (using EPICS alarm colours)
• Jeff asked that it be labeled NLN rather than Lock to be more accurate.

• 16:24 Tyler to MY
• 17:13 Coffey chiller onsite to look at broken PSL chiller, they will be working in the Mechanical room, with Jeff B accompanying.
• 18:11 Tyler and Chandra to MX then MY
• 18:13 Chiller work compleate. Day operator to check it is on daily. See Jeff's alog 53991
• 18:31 Kyle to MX
• 19:26 Tyler to MY
• 21:05 Tyler and Scott to MX then MY
• 21:53 Craning is happening at MY to move new equipment
  • This caused a vacuum sensor to alarm (MY PT-246). Chandra's alog 53993
• 22:20 SEI_CONF from WINDY to USEISM as secondary useism ~ 0.55 μm/s and could be seen on FOMs.
  • This causes some visible glitches (images FOM 1 and FOM 2).
• 22:31 Tyler and Scott to MX

TITLE: 12/19 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 114Mpc
OUTGOING OPERATOR: Camilla
CURRENT ENVIRONMENT:
    SEI_CONF state: USEISM
    Wind: 3mph Gusts, 2mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.57 μm/s
QUICK SUMMARY: 24.5 hour lock, sesism is trending up.

Jenne, Camilla

Operator: When next out of observe. Please reload ISC_LOCK Guardian.

{Tyler, Scott}

From 1:45 pm to 2:15 pm (local), Tyler and Scott operated the overhead crane at mid-Y to set two newly rebuilt BT roughing pumping. The EH2600 blower sits on the cement slab and the EDP200 pump sits next to slab. These pumps are located next to CP4 (toward end station) and will eventually bolt to the 10" GV on side of BT.

During this exercise, PT-246 cold cathode pressure gauge tripped. It will alarm until it comes back online (sometimes takes hours).

I have semi automated the analysis of the high frequency roaming lines. The timestamp for these roaming lines can be found here: LHO alog 53624

The scripts used to obtain the data and convert it into appropriate format for processing lives here:  svn/aligocalibration/trunk/Runs/O3/H1/Scripts/HighFrequency/

The results are saved at the following location: svn/aligocalibration/trunk/Runs/O3/H1/Measurements/HighFrequency/

The instructions on how to run the code can be found in README file here: svn/aligocalibration/trunk/Runs/O3/H1/Scripts/HighFrequency/README