[Patrick, JeffK, Jenne]

It looks like either SR3's OSEMs jumped, or its oplev jumped, after this big earthquake yesterday.  This was causing problems with SRC_ALIGN during initial alignment, since SR3 wasn't really pointed the right way.  This may have contributed to the problems with locking at LowNoiseASC over the last day or so, if other optics were being forced to follow, so the SRC was a little wonky.

Normally when one is having trouble with SRC_ALIGN, you can make sure that the SRC optics are all at their witness positions from the last lock.  This didn't work this time.  SR3 has a "cage servo" to keep the pitch OSEM witness reading constant.  Since there was some kind of jump, the witness sensor probably changed, and then the servo moved the optic to keep the witness constant.  You can see in the pitch oplev that it looks like SR3 moved about 3/4 of a microradian.  In yaw, which does not have a cage servo, the oplev stayed the same, but the OSEMs saw a jump.  Patrick moved SR3 closer to its pitch oplev value from before the earthquake, and we were able to lock SRY and move on with alignment and locking. 

Since the work last week (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=31425) did not help the problems with the OAF machine we attempted more mods today.
0900
Replaced the IO chassis with the original unit.  
Installed a new Onestop card in the chassis
Swapped the first two ADC cards, ribbon cable and interface board.
Replace the 18 bit DAC with a new one.  (The old had the wrong Ram Chips)
Replaced the SFP fiber transceivers for timing with new ones.

None of this fixed the problem so.
1250:We just swapped the onestop fiber with another one that had already been pulled.

I've set damping gains to zero for all PI modes except 3, 26, 27, 28 after there was no sign of them ringing up over long 30 W locks this weekend. Changes have been put into PI guardian and SDF. Thanks so much to the operators who did the work! 

Note that the PI StripTools will continue to monitor as usual, so if any known mode begins to ring up, you can simply put in a gain (try +/- 3000), then try to damp as usual. Just make a note of it in the log. 

WeeklyXtal - Historically, the amp ddiode power tends to trend downward. It seems to be oscillating in these trends and not really decreasing. I was reminded that these also track with humidity.

WeeklyLaser - Osc Box humidity is a little elevated in the past 5-7 days due to an incursion to adjust PMC power and mode matching.

WeeklyEnv - So, the RH inside the H1 enclosure reflect an incursion last Tuesday.

Weekly Chiller - Looks normal

SEI: No issues. If there is trouble relocking due to environmental noise please notify Jim W. He would like to use the time for testing.
SUS: Investigating ITMY long damping time. Fix bug in quad suspension monitor models.
CDS: OAF troubleshooting. Summary of events: ADC added -> started glitching. ADC removed -> glitching continued. Reseated cards -> glitching continued. Fiber patch? -> glitching continued. Moved cards to new IO chassis -> glitching continued. New timing slave? -> glitching continued. To try: Changed SFP for timing. Swap two of the ADCs.
PSL: Turn off DBB. Touch up optical lever centering for BS and ETMY.
VAC:
Drift up in pressure registered by PT170, PT180, PT140. Prepare valves connecting either PT170 or PT180 for bakeout. May need to move Genie lift.
Kyle to continue testing pump at end X (WP 6310).
A note that the red indicator on the vacuum overview for IP12 is fine, it is valved out.
CP3 can now be filled from the control room.
FAC: Still looking for H2O leak. 
PEM: Robert and Anamaria here at the end of the month to run PEM injections.

At LHO, DCS (LDAS) successfully switched to using the H1 ER10 locations to archive data starting from: 1163173888 == Nov 14 2016 07:51:11 PST == Nov 14 2016 15:51:11 UTC. This change should be transparent to users requesting data.

TITLE: 11/14 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Patrick
SHIFT SUMMARY:  Unable to make it past LOWNOISE_ASC.  From watching the ISC_LOCK log in real time, it seems that we would lose lock as the PRC1 FM10 switches were being turned on.  From looking at the Guardian code for this state, this is the last thing this state does, so it could just be a coincidence.  Wind is picking up to ~40mph, so locking may get more difficult.
LOG:

PSL dust alarm has been going off all night

8:31 EX HEPI and ISI WDs tripped at lockloss

11:09 EX HEPI and ISI WDs tripped at lockloss

11:35 restart OAF

11:51 restart OAF

12:00 restart OAF

13:09 PI mode 27 ringing up, changed phase from 35 to 70 and gain from 5000 to 4000

13:11 EX HEPI and ISI WDs tripped at lockloss

14:34 restart OAF twice

Nutsinee left me with a well aligned IFO in the early stages of locking.  Since the beginning of the shift, it has reliably gotten to LOWNOISE_ASC, but rarely further.  I'm not sure what to do about this as I can find no mention of commissioning changes to this state.  So far, I have had to restart OAF twice.

I took the Earthquake downtime to align the PMC using the picomotors. The IMC was set to 30 W with the second loop ISS engaged and DC coupled. A 90 Hz line with amplitude 0.2 V was injected into PMC_TF_IN_EXC. The picomotors were moved to minimize the 90 Hz line in the IMC WFS signals. The attached plot shows that the rms seen by the IMC WFS was reduced by about 7. However, the overall coherence between PMC_HV_MON and the IMC WFS did not change significantly; see plot 1. The diffracted power increased from 3.8% to 5.05%; see plot 2. At the same time the sum of reflected and transmitted power of the PMC decreased from 76.5 W to 74.6 W, a 2.5% change; see plot 3.

Currently, the picomotor controller uses channel 1 and 2 for mirrors 1 and 2, respectively. It probably would be easier to hook up the pitch degrees-of-freedom to channel 1 and the yaw ones to channel 2. This way it would be possible to move both mirrors simultaneously in pitch or yaw.

Both ITM HWS appear to have stopped writing data to the frame about 8 hours ago. Just about time after the 7.8M earthquake has settled. It's not obvious from the control room that the script has stopped running since the value that we're currently watching just stayed flat instead of being bad (this is likely due to the new python script). We have to find a new way to warn us when the HWS misbehave.

Both ITMX and ITMY HWS have the same error:

ERROR: Image acquisition failed: 1 timeouts and 1 overruns occurred. - State 3Br

I haven't restarted the HWS computer in case Richard wants to investigate this.
 

Terramon predicted R-wave peak to be 2.3 um/s. IFO is going to be down for another while longer.

Restarted nuc5 again to bring back the seismic display that disappeared. This time the arrange.sh script did not work and I had to place the positions by hand. Why is the top monitor now to the right of the bottom monitor?

TITLE: 11/14 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Nutsinee
SHIFT SUMMARY: Have spent the majority of the shift alternating between trying to get the SRC to lock in initial alignment and trying to get DRMI to stay locked. I was able to get PRMI to lock stably, and DRMI would keep locking briefly, but only stayed locked once. When it did stay locked I tried moving around the SRM but it didn't seem to have much effect, and I don't think the signals got high enough for guardian to say the LOCK_DRMI_1F state was complete. I then noticed that guardian was complaining about a lost connection to a channel (I think it had trigger in the name), so I tried INIT to see if that would reconnect it. Unfortunately that broke the DRMI lock. I don't think the earthquakes have helped much either. Looking back in the alog, I saw Sheila's post about changing the SRCL FF. After trending back I changed the H1:LSC-SRCLFF1_SW1S and H1:LSC-SRCLFF1_SWSTAT back to what I think they were before she made the change. I don't think this has made any difference.

I restarted nuc5 and video4. Later in the shift the seismic trace on the lower screen disappeared. Yesterday it was the seismic plot on the upper screen that disappeared.

I had to restart OAF once.

The earthquakes have rung down.
LOG:

16:59 UTC Restarted nuc5 (twice) and video4. Apparently the televisions turn off and stay off when nuc5 is restarted?
17:19 UTC IMC is not locking
18:19 UTC Toggled the PSL noise eater switch. Used LLO operator for buddy system since no one else was here.
18:28 UTC Changed the ISI configuration from EARTH_QUAKE_V2 to WINDY
18:51 UTC Cleared history on all IMC WFS DOF. IMC locked immediately. Getting notifications of IMC WFS not centered.
18:59 UTC The ALS X arm is locked on green but the transmission is only around .9. I could try moving TMS but I think I should do an initial alignment.
SRC is not locking in initial alignment. Each time I take it to down to try again the SRM and HAM5 ISI trip.
20:22 UTC Giving up on SRC alignment for now. Going to skip and try to lock DRMI.
20:57 UTC I can get the PRC to lock stably. DRMI will lock briefly but not hold.
21:14 UTC Trended back SRM alignment sliders. They seemed to change substantially 5 hours or so ago. Moving them to match and retrying SRC initial alignment.
22:16 UTC OAF glitch. Restarted with script.
23:10 UTC Trying initial alignment again.
23:24 UTC SRC still won't lock
23:49 UTC Trying to see if undoing the changes I believe Sheila made to the SRCL FF will help:
patrick.thomas@operator0:~$ caput H1:LSC-SRCLFF1_SW1S 17668
Old : H1:LSC-SRCLFF1_SW1S            16708
New : H1:LSC-SRCLFF1_SW1S            17668
patrick.thomas@operator0:~$ caput H1:LSC-SRCLFF1_SWSTAT 300652
Old : H1:LSC-SRCLFF1_SWSTAT          300652
New : H1:LSC-SRCLFF1_SWSTAT          300652
This does not appear to help.

Currently at the Align SRM stage of initial alignment. I have attempted to lock the SRC multiple times without success. Still investigating but running out of ideas.

It appears to be coincident with noise in the FSS (see attached plot). It may be that the IMC feeds back to the FSS though?