TITLE: 08/15 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 53Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:

RED "RMS WD" on the Ops Overview, sounds like it is more of a bug on the Ops Overview.

L1 & V1 went down at around 14:00 & now H1 is set for Maintenance.
LOG:

• 12:39-13:39 Stand-Down Time for GRB Received (from Fermi satellite).  LLO TeamSpeaked us and we confirmed both sites received this real GRB Alarm.
• 13:55 Scaffolding Work at Mid-Y until ~15:00utc (8am) (Chris S.) 
• 13:57 Sealing work for OSB Large/Main Parking Lot begins.
• 14:59 Staging for maintenance electronics work (Ken/Richard M)
• 14:59 Portapotty cleaners on-site. 
• 15:00 LVEA Cleaning (Karen)
• 15:08 Charge measurements begun (Jeff)

H1 locked for 44.5hrs w/ steady 52Mpc range.  Nice triple coincidence for the last 2hrs.

Noticed a RED "RMS WD" on the Ops Overview (see attached with RED box & also part of the ETMy SUS screen).  

Did NOT receive any RMS WD alarms, and I don't see a RED fault box for any OSEM for ETMy's L2 out mons (my previous experience is that one of the OSEMs would be RED and we would need to enter a "1" & then a "0" to clear this up....lately there's been a script to take care of this.)

Looking at some related channels, I do see (trend attached) a bit of nosiness for these channels at the beginning of my shift (assuming this is due to the noise from the Samoa EQ when many things were oscillating.  Perhaps this caused this unique "trip"?).  

Since we are going on a 43hr lock, have been in triple coincidence, I will not address this until/if we break lock during the shift.  

TITLE: 08/15 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 4mph 5min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.11 μm/s 
QUICK SUMMARY:

Walked in to see H1 rolling through a Samoan earthquake (as seen on tidal signals, ASC control signals, and the seismometer signals.  But after doing OSB walkthrough for doors/lights everything is quiet and optimal.  H1 has been locked almost 41hrs and the range has been at a steady 52Mpc.

   Continued triple coincident Observing for first half of the shift. The A2L YAW is elevated. Will run the repair script at the first opportunity. All else is green and clear at this time. 

TITLE: 08/14 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 53Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:  Covering the last 1.5 hours of Cheryl's day shift, so not a lot to report.  Lock is 32+ hours old.  No issues.
LOG:  

22:22 JeffK to Optics Lab to help TJ with VOPO assembly

Activities: all times in UTC

• 16:55 - Karen to VPW - done
• 17:00 - ChrisS to MY - done
• 18:08 - Bubba to MY
• 18:56 - Bubba back from MY
• 21:05 - TJ to OSB optics lab

Currently:

• 21:05 - TJ to OSB optics lab
• electrical work about the CR ceiling planned for this afternoon

Added to Maintenance:

• P-cal X - tweak alignment and calibration measurements - Travis

J. Kissel, S. Karki

I discovered this morning that H1 PCAL X was no longer churning out any of Sudarshan's thesis generating lines. Though I knew we'd intentionally turned off the 333.9 Hz and 1083.3 Hz lines this past Friday evening (see LHO aLOG 38148), we had intended to continue to run the >2 kHz long-duration sweep lines. They had stopped running at 2017-08-13 01:33 UTC --> 2017-08-12 (Saturday) at 6:33 pm local.

What happened?
When the EX SUS rack lost one leg of its power (see LHO aLOG 38162), the EX:ISC power supply was unnecessarily cycled as well, which killed the timing signal to the ISC I/O chassis, the master of the EX Dolphin network. With the master dead, all EX front-ends went belly up -- including PCALX. Upon restart of the front-ends (see LHO aLOG 38163), the guardian code managing this high frequency line,
   /opt/rtcds/userapps/release/cal/h1/guardian/HIGH_FREQ_LINES.py
did not register that we'd lost lock, the safe.snap had some old setting, and we don't monitor these the frequency or gain of the H1:CAL-PCALX_PCALOSC1 oscillator because it is regularly changed during observation -- so no one noticed that the line was off.

I've edited the guardian code to start at the next data point, at 4001.3 Hz, loaded it, ran the INIT state, which turned on the line at 2017-08-14 20:31:30 UTC (if you want to be picky, it was ramping up from 20:31:30 UTC, and fully ON and stable by 20:31:30 UTC).

Again, because the frequency and gain of this oscillator is not monitored, this guardian reload and settings change did NOT take us out of observation mode.

Got a long enough patch of wind over the weekend, long enough around 20mph and from the south or SW direction, see first attachment.  The previous post about this had the wind from the NNW.  Go to this alog to walk back through all the positions.

Looking at the second attachment, the Z DOF here looks pretty different than first look at Roam8, otherwise the X & Y DOFs look similar: during the quiet period (1000hrs 10 Aug) the floor or the HAM5 STS2 is noisier than the ITMY unit or that location at frequencies below 20 to 40mHz.  During the high wind, 1640hrs 13 Aug, the Roam8 measurement is noisier by a factor of a few below 20 to 70mHz.  At the lowest frequencies, below 10 or less, one might argue the HAM5 machine got less noisier during the windy time but these calibrated machines are giving an actual motion, not relative, again arguing that the HAM5 machine is not a good as ITMY.

Bottom line--for Roam8: not as good as ITMY.

Maintenance for 15 Aug 2017:

• Prep for squeezer table placement - Richard/Fil/Liz
• cleanroom test run in LVEA - Bubba
• My CP3 insulation - contractor
• entry to PSL Ante-Room - Cheryl
• re-sealing OSB parking lot - Bubba
• replace VFD at EY - Bubba
• pump diode current adjustments - Jason
• adjust beam into PMC - Jason
• power cycle dust monitor in PSL (Ante-Room or in laser room TBD) - JeffB/Richard/Cheryl
• pull cables to HAM6 - Richard
• 3IFO Inventory in LVEA - Hugh

TITLE: 08/14 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 51Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY: locked 24+ hours

TITLE: 08/14 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1:
INCOMING OPERATOR: Travis
SHIFT SUMMARY:

"Seismon system not updating" DIAG_MAIN alarm, we aren't getting updates of 4.0+ EQs (last one was at 3:05utc, but we've had others since).
H1 has been locked for over 24hrs with a steady 52Mpc.
LOG:

• 8:22 - 8:33  Vehicle at LSB, person walked toward LSB entrance & then drove off.

Laser Status:
SysStat is good
Front End Power is 33.88W (should be around 30 W)
HPO Output Power is 154.7W
Front End Watch is GREEN
HPO Watch is GREEN

PMC:
It has been locked 5 days, 18 hr 52 minutes (should be days/weeks)
Reflected power = 17.86Watts
Transmitted power = 57.96Watts
PowerSum = 75.82Watts.

FSS:
It has been locked for 1 days 0 hr and 15 min (should be days/weeks)
TPD[V] = 1.072V (min 0.9V)

ISS:
The diffracted power is around 2.3% (should be 3-5%)
Last saturation event was 1 days 0 hours and 54 minutes ago (should be days/weeks)

Possible Issues:
PMC reflected power is high

TITLE: 08/14 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 51Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
    Wind: 10mph Gusts, 8mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s

Small step up with useism (factor of 2 over last 24hrs).  Winds up & down over last 24hrs (currently quiet).
QUICK SUMMARY:

While going through checksheet, noticed a dead video4 computer (rebooting).  Other than that, no notable changes.

TITLE: 08/14 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Not much happened, locked entire shift
LOG:
Around 4:00 UTC, I saw that our seismon code was dead. Not sure what happened, but there was a prolonged period without any 4.0+ earthquakes. Maybe some of the cleanup processes broke it (i.e. all event folders were wiped, seismon couldn't decide where to new ones) ?

TITLE: 08/13 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY:  Locked the entire shift, 8.5 hours total now.  No issues to report.
LOG:  Restarted Video5.

PaulM, TJ, SudarshanK(remotely)

The low frequency Pcal lines running at 333.9 Hz and 1083.3 Hz were switched off during the PEM injection commissioning break and the guardian node (HIGH_FREQ_LINES) that schedules the single line injection beginning from 4501.3 Hz and ending at 1501.3 Hz with 500 Hz interval was initiated.

   Could not reach Pcal folks to confirm SDF differences. Accepted the differences (see file below) to get back to Observing.