Activity Log: All Times in UTC (PT)

08:00 (00:00) Take over from Patrick
08:50 (00:50) GRB alert 
09:15 (01:15) Air handler alarms for CS zone 1B and zone 4 – Duct temperatures 97.3F and 99.41F
12:10 (04:10) GRB alert
16:00 (08:00) Turn over to Travis

End of Shift Summary:

Title: 11/21/2015, Evening Shift 08:00 – 16:00 (00:00 – 08:00) All times in UTC (PT)

Support: None needed
 
Incoming Operator: Travis

Shift Detail Summary: 08:50 (00:50) GRB alert – LHO in Observing; LLO down due to environmental issues. Ignored alarm.  12:10 (00:10) GRB (E202631) – LHO in Observing; LLO down due to FE problem. Ignored the alert.

Generally a good shift. IFO in Observing mode for ~ 12 hours. Range has been around 78Mpc. Other than cold and fog, weather is good and seismic has been stable for the entire shift. Only one ETM-Y saturations and no problems with RF45. No additional temperature related alarms in the corner or end stations. 

   12:10 (04:10) Received GBR alert (E202631). LHO in Observing mode. Spoke with LLO; their FE is down and they are working on recovery. Ignored the alert. 

   A good first half of this Owl shift. IFO in Observing mode for past 9 hours. Range is around 78Mpc. Wind is clam (0 - 3mph) and seismic activity is low and steady. Warmer than last night, the corner station is reporting a balmy 26F, with heavy fog. There has been one EMT-Y glitch.  

  Had temperature alarms on FMC-CS_LVEA_REHEAT_1B_DEGF and FMC-CS_LVEA_REHEAT_4_DEGF. CS zone 1B has output temp of 98.41F and zone 4 is at 99.56F. Have attached a 48 hour trends of the chiller yards and a screen shot of the corner station air handlers. Will continue to monitor.   

   08:50 (00:50) received GRB alert (E202583). LHO in Observing. Spoke to LLO, they are down due to environmental conditions. Ignored alert. 

Title:  11/22/2015, Evening Shift 08:00 – 16:00 (00:00 – 08:00) All times in UTC (PT)
	
State of H1: 08:00 (16:00), The IFO locked at NOMINAL_LOW_NOISE, 22.3w, 79Mpc.  

Outgoing Operator: Patrick

Quick Summary:  IFO has been in Observing mode for the past 5 hours, except as noted in Patrick log entries. Environmental conditions – wind is a light to gentle breeze (4-12mph). Seismic activity is quiet after a couple of small earthquakes ~ 2 hours ago. Microseism is centered around 0.3 um/s.  

TITLE: 11/21 [EVE Shift]: 00:00-08:00 UTC (16:00-00:00 PDT), all times posted in UTC
STATE Of H1: Observing @ ~ 77 MPc.
SHIFT SUMMARY: Had trouble relocking after the earthquake at the beginning of shift. Have remained at NLN since. Went out of observing while Chris ran his swept-sine measurement. Winds have remained low. Survived two short peaks to ~ .2 um/s in the earthquake band.
INCOMING OPERATOR: Jeff B.

Chris is done.

To allow Chris to run a swept-sine measurement.

LLO had called and said they would be down for awhile.

I'm going to finish doing a swept-sine through the INJ_HARDWARE filterbank from 5-500Hz. Previously I had only finished 500-2000Hz.

The IFO intent mode has been turned off.

This is WP#5595.

The ISI blends are on Quite_90.
The range is ~ 78 MPc.

Relocking sequence:

I had to move ETMX and ETMY in Pitch.
I had to move TMSY in Pitch.
I lost lock on SWITCH_TO_QPDS.

I had to move ETMX in Pitch and Yaw.
The ALS_DIFF node gave notifications on FIND_IR that 'X arm alignment is bad, not searching' and 'Y arm alignment is bad, not searching'. It eventually went to CHECK_IR without intervention.
The ISC_LOCK node gave an 'IR not really found' notification on CHECK_IR.
I adjusted H1:ALS-C_DIFF_PLL_CTRL_OFFSET to bring the IR in the Y arm to around 1.
I lost lock on SWITCH_TO_QPDS.

The ISC_LOCK node gave an 'IR not really found' notification on CHECK_IR.
I adjusted H1:ALS-C_DIFF_PLL_CTRL_OFFSET to increase the IR in the Y arm but still got 'IR not really found' notifications. I decided to try to move to DRMI_LOCKED anyway.
I lost lock on RF_DARM.

I lost lock on FIND_IR.

I started an initial alignment.
The MC lost lock and relocked on LOCKING_XARM_IR.
The X arm seemed to lock and then lose lock on IR.
The MC lost lock and relocked.
I set the X arm LSC gain to .15. The MC lost lock and relocked.
I set the X arm LSC gain to .15 again. It did not seem to help. I set it back to .05.
The X arm does not want to lock on IR.

I put the ALS_XARM and ALS_YARM nodes to LOCKED_SLOW_W_ETM_WFS. I put the ALIGN_IFO node to SET_SUS_FOR_ALS.
I increased H1:ALS-C_COMM_A_DEMOD_RFMON from around 4.1 to around 4.6 by moving PR3.
I put the ALS_XARM and ALS_YARM nodes to UNLOCKED. I accidentally put the ALIGN_IFO node to INPUT_ALIGN_OFFLOADED. I quickly put it to INPUT_ALIGN.
The X arm still does not want to lock on IR.

I finally got the X arm to lock on IR by adjusting PR2 in Yaw from 4303.4 to 4302.4.

I adjusted H1:ALS-C_DIFF_PLL_CTRL_OFFSET and H1:ALS-C_COMM_VCO_CONTROLS_SETFREQUENCY in CHECK_IR. It may have improved TRX.
I stopped at ENGAGE_ASC_PART3 to wait for the ASC loops to converge. I reduced the ISS diffracted power.
I engaged the ISS second loop by hand.
I reached NOMINAL_LOW_NOISE.

TITLE: 11/21 [EVE Shift]: 00:00-08:00 UTC (16:00-00:00 PDT), all times posted in UTC
STATE Of H1: Just lost lock coincident with an earthquake.
OUTGOING OPERATOR: Travis
QUICK SUMMARY:
From the the cameras:
The lights are off in the LVEA.
The lights are off in the PSL enclosure.
The lights are off at mid X.
I can not tell if the lights are on or off at mid Y.
The lights are off at end X.
The lights are off at end Y.

The 0.03 - 0.1 Hz (earthquake) seismic band has just jumped to ~ 0.5 um/s.
The 0.1 - 0.3 Hz (microseism) seismic band is between ~ 0.1 and 0.4 um/s.

The winds are between ~ 0 and 10 mph.

The ISI blends are on Quite_90.

From pinging:
The CDS WAP is off at the LVEA.
The CDS WAP is on at mid X.
The CDS WAP is on at mid Y.
The CDS WAP is off at end X.
The CDS WAP is off at end Y.

Title: 11/21 Day Shift 16:00-24:00 UTC (8:00-16:00 PST).  All times in UTC.

State of H1: Locking

Shift Summary:  Locked almost my entire shift. Lockloss at 23:55 UTC likely due to 2 EQs with similar arrival times. 

Incoming operator: Patrick

Activity log: None

Locked in Observing for the past ~18 hours.  There have been 12 ETMy saturations since the start of my shift, but none seems to correlate with any RF45 glitching as none has been seen.

The psinject process running on h1hwinj1 have stopped several times recently. The monit program on this machine then restarts the process and reports this to sysadmins. The latest stop-start was at 09:34 PST this morning, and I confirmed that the CW excitation was absent for 34 seconds at this time.

Here is a list of all the restarts for the month of November as reported by monit. Some may have been due to maintenance, and H1 may not have been in observation mode for every event.

Sat, 21 Nov 2015 09:34:39

Sat, 21 Nov 2015 00:45:22

Fri, 20 Nov 2015 16:10:05

Wed, 18 Nov 2015 13:58:44

Wed, 18 Nov 2015 05:00:26

Tue, 17 Nov 2015 03:05:18

Tue, 17 Nov 2015 00:01:10

Sat, 14 Nov 2015 07:05:26

Fri, 13 Nov 2015 00:00:34

Sun, 01 Nov 2015 00:00:22

we are investigating the reason why psinject is stopping (FRS4019) https://services.ligo-la.caltech.edu/FRS/show_bug.cgi?id=4019

I talked with Jeff and Travis and we decided to increment heat as we are running out of range in the FMCS controls. Outdoor temps have fallen to ~18F overnight.

In the LVEA - incremented HC1B from 9 to 10 ma (control signal) at 8:16 PST

EX - incremented HC3 from 10-11 ma at 8:18

EY - incremented HC3 from 10-11 ma at 8:19.

Edit - incremented EX HC3 from 11- 12ma at 8:33 for some additional heat as response was not sufficient.

While trying to understand and deal with the Beckhoff SDF diffs in OBSERVE mode, I stumbled on a weird channel that toggled states around 4pm local last Wed Nov 11 (01 UTC WED 11th).  (Note, this occured well before the windy troublesome locking period when we saw a power glitch on Tuesd Wed 17th.)  If the VCO Frequency Servo is set to "Int" (see the center of the medm pic attached below), do we care what this EXTFREQUENCYOFFSET channel is doing?  And where is the medm for this EXTFREQUENCYOFFSET channel anyways? - Even with commissioners, we couldn't immediately find it...  And, and, what's with the glitch in the middle of the 20 day trend on Wed 11th?