• Robert has been in the LVEA (judging by the Camera shots, he's checking light scattering in the input arm).
• Have currently been locked 3.5+hrs.  The range is hovering has been hovering between 60-70Mpc even with Robert work & injections.  
• Had a PI Mode18 rung up recently and damped it out via phase change.
• Winds toyed with approaching 20mph but have subsided.  Calif EQ quietly rolled by (no SEI action taken)

Whoops---just dropped out of lock. at 18:40 (11:40am).

TITLE: 10/30 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    Wind: 9mph Gusts, 6mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.26 μm/s
QUICK SUMMARY:

• Arrived a bit late due to needing to swap a flat tire.
• Cheryl just took H1 up to NLN. 
• I transitioned Observatory Mode to Commissioning.
• Robert's shaker at EY continues to shake (and give us a 65Hz line & harmonics seen on DARM); this has been since yesterday at about noon.
• Robert is staging to get continue his various measurements/investigations/injections.
• Storm continues its downward trend as seen on useism.
• ISI Config was on USEISM_MOD_WIND.  Cheryl took it here during the big EQ & we had higher useism touching the 90percentile.  I am going to take the system to the nominal WINDY state.
• HAM2 HEPI excitation indication still noted on overviews (Guardian/CDS).  Thought of killing it, but Robert mentioned they might run it again, so I held off.
• IM3 continues with "out of nominal range" on DIAG_MAIN (Cheryl will investigate).
• H1IOPASC0 is noting a TIMING ERROR on the CDS Overview (indicated by RED "TIM" box and RED CPU Max box (i.e. H1:FEC-18_CPU_METER_MAX).  Hitting Diag Reset cleared both Timing Errors on the H1IOPASC0 window.
• Conlog continues to have INVALID boxes on CDS Overview.
   

State of H1: relocking

Shift Details / Activites:

• lock loss due to earthquakes in Italy
• used the LARGE EQ state for SEI that JimW reccommended - no platforms tripped
• after EQs rand down, Initial Alignment
• first lock that made it to DC READOUT, paused for roll mode damping, my bad click broke lock
• second lock that made it to DC READOUT, paused for damping, then went to Nominal Low Noise
• set TCSY to 0.4W, and left TCSX at 0.2W
• noticed range dropping fast, thought it might be TCS, turned TCSY off (0W) at 13:47UTC
• went to make some lunch, and did not see the notification of a PI mode ringing up when I came back, can we make it repeat, like the GRBs?
• PI mode 27 broke the lock

Notifications:

• GRB came in while 9:51:19, while H1 was in DRMI

State of H1: relocked and in Nominal Low Noise, Range is 68MPc

Activities:

• recovery from EQs
• no SEI platforms tripped
• H1 needed an Initial Alignment - can be attributed to a lock of about 10 hours before EQs arrived
• some early ASC issues
• paused at DC Readout - damping bounce and roll
• on the way to NLN, had to damp PI mode 18

• relocked and in DC readout
• sitting here to address roll modes
• bounce modes aren't great, but look like they're coming down
• will also look at violins, since JimW had them ring up during his shift

• done with Initial Alignment
• set ISC_LOCK to Down and run Init
• ISC_LOCK says it's done running DOWN, and goes ro Ready
• but ALIGN_IFO is still in SRC_OFFLOADED
• wouldn't it make sense for the ISC_LOCK down script to handle setting all of the nodes to the proper state?
• or maybe ISC_LOCK INIT could do this?
• or maybe they do and I did the wrong guardian sequence?
• screenshot of where H1 landed

State of H1: SEI in LARGE_EQ_NOBRSXY, ground motion increased to 10um/s

Help: JimW changed SEI settings to EARTH_QUAKE_V2, and explained the use of LARGE_EQ if ground motion got worse

Details:

• 6:40UTC-7:40UTC, M6.6, M4.4, and M4.4 earthquakes in Italy
• H1 has been down more than an hour
• 7:25UTC, ground motion increased to 10um/s, so I switched SEI to LARGE_EQ
• no SEI platforms have tripped
• IMC can only lock for a few minutes

TITLE: 10/29 Day Shift: 23:00-7:00 UTC , all times posted in UTC
STATE of H1: Relocking Earthquake
SHIFT SUMMARY:
Robert and Jenne both left part way through the shift. PI mode 2 rang up (which was easily handled by adjusting damping phase) and  2 violin modes on ETMY rang up (508.585 & 508.661), but it took me 20+ minutes to realize, because there is no alarm system and the monitor screens are kind of unclear. Seems like we could take some pages from the PI book to help with that. I also changed the TCSY power from 0 to .2w per Kiwamus request.

TITLE: 10/29 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Jim
SHIFT SUMMARY:
H1 was locked entire shift.  Robert was at the end stations (mostly EY) performing measurements.  Jenne worked on a filter for SRCL FeedForward.

Noticed the HAM2 HEPI has an excitation noted in the CDS Overview---Jim says this might be from Robert.

DIAG_MAIN is noting IM3 P&Y are out of nominal range (can talk to Cheryl about this).

LOG:

• 15:15  Robert to End Stations for injections
• 15:15 NO BRS for EX & EY
• 17:30 Robert back, but heading back out to EY.  Turned EX BRS back on.
• 20:30-12:45 Saw a random couple walking around the site (up to OSB & then around the LSB).  (two guys here walking around 22:15UTC)
• 21:32 LOCKLOSS due to us.  Back to NLN in ~30min.  Took TCS to settings Cheryl had for her last lock & also returned BRS to X&Y (since Jenne wanted to hand back to Robert & he was thinking of transitioning to LVEA work).
• 22:12 PI Mode 28 rung up.  Took phase from 90 down to 60 degrees did the trick.
• 22:20 Robert heading out to LVEA to look through input (HAM2) viewports.

Last time I was on shift, we were filling the TCSy Chiller fairly frequently.  Went out to chec on both chillers.  

• X was fine.
• Y was a little low ("6.5 level").  So I took it up to "8.7" by adding 225mL.  Before topping off I could see an "air bubble" which popped.  At any rate--perhaps I could have added more water due to bubble effect, but opted to leave it as is.

TITLE: 10/29 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 58.0319Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    Wind: 11mph Gusts, 7mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.46 μm/s
QUICK SUMMARY:

Currently have a lock approaching 2Hrs (started at around 73Mpc, but was slowly trending down, and in the last few minutes took a step down to 55Mpc) . 

Robert is here and has headed out to the end stations for injection work (the BRS was switched to the VERY_WINDY_NOBRSXY state).   Switching Observatory Mode to:  UNKNOWN (since I don't see an "injection" option).

Cheryl gave me a suggestion of keeping TCSx at 0.4 & moving TCSy from 0.0 to 0.2 for the next change.

Might have broken the lock 2.5 hours ago, and could be a problem today.

I think that the nominal setting of the CAL-PINJX_TRANSIENT filter bank gain is supposed to be zero. When a transient injection is imminent, then the gain is ramped to 1.0, the injection happens, and then the gain is ramped to zero. However, the SDF safe set point is 1.0. Therefore, I am setting the gain to 0 and accepting the change in the SDF safe file.

Kiwamu saked the ops to run some TCS laser noise measurements.

SETUP:

• After IFO is locked at NLN for at least 30 minutes
• Open TCS_MASTER screen
• Open the CO2 X & Y screens
• Open the POWER CONTROLS screens for X & Y
• increase the power by 0.1W
• Wait 90 minutes, and increase the power by another 0.1W
• Repeat until at about 2W
• aLOG the times and power levels

Started the run: 

    TSC X - Initial Power = 0.2W                     TSC Y - Initial Power = 0.0W

At 05:08 Lost lock due to a Mag5.8 EQ in Alaska.

The results of cdsutils.avg() in guardian is sometimes giving us very weird values. 

We use this function to measure the offset value of the trans QPDs in Prep_TR_CARM.  At one point, the result of the average gave the same (wrong) value for both the X and Y QPDs, to within 9 decimal places (right side of screenshot, about halfway down).  Obviously this isn't right, but the fact that the values are identical will hopefully help track down what happened.

The next lock, it correctly got a value for the TransX (left side of screenshot, about halfway down), but didn't write a value for the TransY QPD, which indicates that it was trying to write the exact same value that was already there (epics writes aren't logged if they don't change the value). 

So, why did 3 different cdsutils averages all return a value of 751.242126465?

This isn't the first time that this has happened.  Stefan recalls at least one time from over the weekend, and I know Cheryl and I found this sometime last week. 

Ed, Sheila

Are ezca connection errors becoming more frequent?  Ed has had two in the last hour or so, one of which contributed to a lockloss (ISC_DRMI).

The first one was from ISC_LOCK, the screenshot is attached.