J. Kissel
WP 6368 (Now Closed)

The PCALX roaming calibration line has been off since Dec 09 2016 06:41:24 UTC (1165300901, Dec 08 2016 22:41:24 PST) when Rick, Evan, and Travis had last turned it OFF for transient hardware injections (see LHO aLOG 32376). Since Sudarshan now has a satisfactory amount of data at 30 [W], and has processed the data (see LHO aLOG 32512), we will keep this line OFF as planned, until further notice.

WeeklyXtal - PSL_AMP_D3 and D4PWR are tracking humidity trends pretty coherently. D1&2 powers have trended upward slightly.

WeeklyLaser -  Over the last 3 or 4 days the LRA position has walked it's way down from the Nominal 4500 to 4496. OSC_BOXHUM has dropped even lower.

WeeklyEnv - Humidities down, temperatures stable.

WeeklyChiller - OSC_PRESS1&2 are trending slightly downward. Headflows are also, very marginally, drifting downward.

WP 6396

Installed new LPC (+) voltage power supply for ion pump #12 at EX. Next Gerardo will install CDS wiring for MEDM read back.

FAMIS#7416

Laser Status:
SysStat is good
Front End Power is 34.36W (should be around 30 W)
Front End Watch is GREEN
HPO Watch is GREEN
PMC:
It has been locked 0.0 days, 0.0 hr 6.0 minutes (should be days/weeks)
Reflected power is 14.17Watts and PowerSum = 75.1Watts.

FSS:
It has been locked for 0.0 days 0.0 hr and 6.0 min (should be days/weeks)
TPD[V] = 2.18V (min 0.9V)

ISS:
The diffracted power is around 3.314% (should be 5-9%)
Last saturation event was 0.0 days 0.0 hours and 6.0 minutes ago (should be days/weeks)

Possible Issues:
PMC reflected power is high

wiki: https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20161208

Below I summarise the main highlights of this shift:

duty cycle 65.2%, the range is 70 - 75Mpc.
on Thursday 8th lockloss due to multiple earthquakes keeping occuring to morning on Friday
Software saturation - H1:LSC-X_ARM_CTRL [1] at ~11:00UTC on Thursday 8th
18kHz PI modes strong peak at 11:07UTC and 12:10UTC on Thursday 8th, at ~8:00UTC, ~ 9:00UTC, ~ 10:30UTC and at ~12:30 on Friday 9th.
the planned stochastic injection at 00:10UTC Thursday 8th
quiet on Saturday 10th and Sunday 11th

The PSL Enclosure phone has been switched off.

A reminder that it needs to be re-enabled when work is being done in the Laser Area Enclosure.
The power supply for it is in Rm 163.

TITLE: 12/13 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 73.1393Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:

Operator-less for the first 90min, but rest of the shift saw me here watching a nice performing H1 on a quiet Earth. 
LOG:

• 9:54, 10:47, 14:26 PSL Anteroom DUST MINOR & MAJOR Alarms for 0.3um
• ~12:30 Range begins drop from 70Mpc down to 62Mpc (not obviously correlated with seismic.
• 13:42:  Notice L1 down & also around this time notice a jump in 0.03-0.1Hz seismic (No EQ alerts though).  This was an EQ alogged earlier.
• Handded off a locked H1 to Bartlett for Maintenance Day

Ops Shift Transition:12/13/2016, Day Shift 16:00 – 00:00 (08:00 - 16:00) -  UTC (PT)

Andy, Tom Dent, Josh

Nutsinee (alog 32159) and Patrick (alog 32163) both reported a string of glitches during their shifts on Dec 4th. These showed up again in connection with an investigation into some PyCBC loudest events. At Tom's suggestion, we listened to the PSL microphone, which is one of many PEM channels seeing a huge disturbance at these times.

I've attached the wav file of the PSL center mic. It seems like the PSL intercom (or some other phone) rings twice and afterwards forwards the call somewhere else. You can hear a faint third ring, and Josh has another file where talking can be heard after the faint ring. When this happened at LLO during an ER, (L1 alog 8451 the intercom would answer and then make a busy signal.

It's not clear why we haven't seen this more often, or when the intercom could have gotten connected. This is in the middle of a long stretch of science mode.

Edit: To be clear, the loud rings make something very strong in DARM. We're investigating to what extent the quieter stuff shows up.

Have had a decent night tonight.  However at around 12:30utc noticed H1 range taking a noticeable dip from 70Mpc down to 62Mpc.  All of this happened within an hour time frame (appears to be coming back up near 70Mpc.  There is nothing obvious in the BLRMS seismic traces (well, for high freq the Corner Station seismometer there is a bump which sort of lines up...but the corner station has many of these bumps and the other ones don't drop the range.)  Anyway, it was a curiousity.  

There was a small EQ around this time, but it was after the fact and fairly quick.

Overall the H1 range tends to show very slow oscillations in range values and one would think it was useism, but they also don't match up. I'm just curious about why our range fluctuates on a slow time scale like this & how it's curious it doesn't match seismic (L1's range appears to follow seismic more obviously...atleast from my glances at their range and seismic screenshots.)

Noticed L1 dropping out of lock at around 13:42 & around this time noticed elevated noise on our EQ BLRMS signal (also notice it on LLO EQ band screenshots).  Nothing observed on Terramon or USGS website (and other websites).  I did notice a 4.4 in Baja California here:  http://www.emsc-csem.org/Earthquake/earthquake.php?id=552372

• Not reported on Terramon or USGS site.  Observed on our 0.03-0.1Hz BLRMS at 0.2um/s (saw possible posting on emsc-csem.org)     
• Magnitude:  4.4
• Location:  Gulf of California
• Starting time of event:  Observed on BLRMS at 13:41utc (emsc-csem.org reports eq at 13:27utc)
• Lock status?  H1 remained locked (L1 broke lock)
• Not reported on Terramon as of 14:02utc

Since the start of O2, we have had some pesky dropouts of OBSERVING due to SDF channel changes for some ALS channels from a Beckhoff computer at each of our End Stations (sysecatx1plc2 & sysecaty1plc2).  Below, I wanted to list each of the occassions, the amount of time we were out of Science mode, channels involved, and their current state.

• 12/3:  8min Out of OBSERVING (Corey Alog)
  • Due to the following & UNMONITORED the following:
    • H1:ALS-X_FIBR_SERVO_IN1GAIN
    • H1:ALS-X_FIBR_LOCK_TEMPERATURECONTROLS_ERRORSIGNAL
    • H1:ALS-X_FIBR_LOCK_TEMPERATURECONTROLS_POLARITY
• 12/3:  1min Out of OBSERVING (Ed Alog)
  • Due to following & UNMONITORED:  H1:ALS-X_FIBR_LOCK_TEMPERATURECONTROLS_ON
• 12/10:  5min Out of OBSERVING (Cheryl Alog)
  • Due to H1:ALS-Y_FIBR_LOCK_TEMPERATURECONTROLS_ON
• 12/11:  8min Out of OBSERVING.  (Cheryl Alog)
  • Due to the following & UNMONITORED:  H1:ALS-Y_FIBR_LOCK_TEMPERATURECONTROLS_ON

Should UNMONITOR (3) ALS-Y Channels

Above we can see all of the channels we noticed/caught/UNMONITORED.  I would suggest we take the preemptive action of UNMONITORING (if not already done so) the following channels for sysecaty1plc2 next time we are out of OBSERVING:

• H1:ALS-Y_FIBR_SERVO_IN1GAIN
• H1:ALS-Y_FIBR_LOCK_TEMPERATURECONTROLS_ERRORSIGNAL
• H1:ALS-Y_FIBR_LOCK_TEMPERATURECONTROLS_POLARITY

Have remained locked at NLN since 21:44 UTC.
Stood down for a GRB at 23:20 UTC. It appeared that the injections were not automatically blocked for the GRB, so I set the INJ_TRANS guardian node to INJECT_KILL manually. Requested INJECT_SUCCESS at 00:35 UTC.
Damped PI modes 26 and 28.
Ran a2l near beginning of lock.

J. Kissel for S. Karki
WP #6368

I've moved the PCALX roaming line, its long duration sweep, from 4001.3 Hz to 4301.3 Hz. See schedule status below.

Since it looks like we'll have the duty cycle to just finish the schedule within a week, I'm just going to continue to re-gathering the highest frequency data. As such, Sudarshan has something consistent and straightforward with which to work instead of data with a bunch details or qualifications. 


Frequency    Planned Amplitude        Planned Duration      Actual Amplitude    Start Time                 Stop Time                    Achieved Duration
(Hz)         (ct)                     (hh:mm)                   (ct)               (UTC)                    (UTC)                         (hh:mm)
---------------------------------------------------------------------------------------------------------------------------------------------------------
1001.3       35k                      02:00                   39322.0           Nov 28 2016 17:20:44 UTC  Nov 30 2016 17:16:00 UTC         days    @ 30 W  
1501.3       35k                      02:00                   39322.0           Nov 30 2016 17:27:00 UTC  Nov 30 2016 19:36:00 UTC         02:09   @ 30 W         
2001.3       35k                      02:00                   39322.0           Nov 30 2016 19:36:00 UTC  Nov 30 2016 22:07:00 UTC         02:31   @ 30 W
2501.3       35k                      05:00                   39322.0           Nov 30 2016 22:08:00 UTC  Dec 02 2016 20:16:00 UTC         days    @ 30 W
3001.3       35k                      05:00                   39322.0           Dec 02 2016 20:17:00 UTC  Dec 05 2016 16:58:57 UTC         days    @ 30 W
3501.3       35k                      05:00                   39322.0           Dec 05 2016 16:58:57 UTC  Dec 06 2016 21:09:56 UTC         ~15:00  @ 30 W
4001.3       40k                      10:00                   39322.0           Dec 06 2016 21:09:56 UTC  Dec 07 2016 18:50:09 UTC         ~20:00  @ 30 W
4301.3       40k                      10:00                   39322.0           Dec 07 2016 18:50:09 UTC
4501.3       40k                      10:00                   39322.0           
4801.3       40k                      10:00                   39222.0           
5001.3       40k                      10:00                   39222.0         

Frequency    Planned Amplitude        Planned Duration      Actual Amplitude    Start Time                 Stop Time                    Achieved Duration
(Hz)         (ct)                     (hh:mm)                   (ct)               (UTC)                    (UTC)                         (hh:mm)
---------------------------------------------------------------------------------------------------------------------------------------------------------
1001.3       35k                      02:00                   39322.0           Nov 11 2016 21:37:50 UTC    Nov 12 2016 03:28:21 UTC      ~several hours @ 25 W
1501.3       35k                      02:00                   39322.0           Oct 24 2016 15:26:57 UTC    Oct 31 2016 15:44:29 UTC      ~week @ 25 W
2001.3       35k                      02:00                   39322.0           Oct 17 2016 21:22:03 UTC    Oct 24 2016 15:26:57 UTC      several days (at both 50W and 25 W)
2501.3       35k                      05:00                   39322.0           Oct 12 2016 03:20:41 UTC    Oct 17 2016 21:22:03 UTC      days     @ 50 W
3001.3       35k                      05:00                   39322.0           Oct 06 2016 18:39:26 UTC    Oct 12 2016 03:20:41 UTC      days     @ 50 W
3501.3       35k                      05:00                   39322.0           Jul 06 2016 18:56:13 UTC    Oct 06 2016 18:39:26 UTC      months   @ 50 W
4001.3       40k                      10:00                   39322.0           Nov 12 2016 03:28:21 UTC    Nov 16 2016 22:17:29 UTC      days     @ 30 W (see LHO aLOG 31546 for caveats)
4301.3       40k                      10:00                   39322.0           Nov 16 2016 22:17:29 UTC    Nov 18 2016 17:08:49 UTC      days     @ 30 W          
4501.3       40k                      10:00                   39322.0           Nov 18 2016 17:08:49 UTC    Nov 20 2016 16:54:32 UTC      days     @ 30 W (see LHO aLOG 31610 for caveats)   
4801.3       40k                      10:00                   39222.0           Nov 20 2016 16:54:32 UTC    Nov 22 2016 23:56:06 UTC      days     @ 30 W
5001.3       40k                      10:00                   39222.0           Nov 22 2016 23:56:06 UTC    Nov 28 2016 17:20:44 UTC      days     @ 30 W (line was OFF and ON for Hardware INJ)