During the down hour, I made shaker injections at HAM1 and IOT2, and made the following site activity injections:

When both sites went out of Observing I was going to take the opportunity to do some violin mode damping. However, we were ready to go on Observing before I get to damp anything (I didn't even finish making the filter). The modified filter bank is ETMY L2 DAMP MODE4 FM7 and FM8 (BP and -60deg). This frequency however was already damped by MODE10 filter bank but hasn't been included in the violin mode table. I will edit the table accordingly.

TITLE: "11/06 [EVE Shift]: 23:00-07:00UTC (16:00-00:00 PST), all times posted in UTC"

STATE Of H1: Observing at ~ 80Mpc

OUTGOING OPERATOR: Ed

QUICK SUMMARY: LLO was down for some commissioning. Robert took the opportunity to do some injection on HAM1. Wind ~5mph. EQ band seismic activity slowly increase and now cruising between e-2 and e-1 um/s. Microseism is crossing over the 50th percentile line. 

While looking at our PRC gains as a function of time, I noticed that yesterday we had a very abnormal lock.  The lock between approx 01:30-10:00 UTC on 5 Nov 2015 sees a slow drift where we slowly lose power buildup over time, and lose lock when we have lost about 10% of the power buildup.  The IM4 Trans PD doesn't see the power drift, so it's not anything to do with the IMC or anything upstream of that.

All 3 power recycling optics see some drift (as seen by their M3 witness sensors), as do the ETMs (as seen by their oplevs).  This is the same lock that SR3 had its problem where I hand-offloaded pitch from M2 to M1 (aLog 23128), but it doesn't look like that drift lines up with the power drift very well.  Anyhow, I'm not sure what started drifting and why, but it looks like all of these optics' ASC controls are pushing them around to try to fix the drift, perhaps? 

Our locks since this one have been fine, and look totally normal, so I'm not sure that there's a persistent problem that we need to fix, but this seemed worth noting.

The first plot shows the power drift in POP and a Transmission PD, as well as the optic alignments of most of the optics, and the second plot has another few alignment traces, as well as the SR3 cage servo output.

TITLE:    Nov 6 DAY Shift 16:00-00:00UTC (08:00-04:00 PDT), all times posted in UTC

STATE Of H1: Observing

SUPPORT: N/A

LOCK DURATION: ≈5 hrs

INCOMING OPERATOR: Nutsinee

END-OF-SHIFT SUMMARY: There was a mysterious lockloss ≈7 hrs ago and I had some trouble re-locking (see activity log). After that, smooth sailing. Handing off to Nutsinee.

ACTIVITY LOG:

17:02  Robert into LVEA to install shaker

16:57  LockLoss

17:30  went 20 minutes trying to get PRMI locked. Ditched and went to initial alignment

17:56 Chris called to tell me he was leaving in a few to go doen X-Arm to do beam tube work. Joe will accompany.

18:15  First attempt at relocking failed. Problems with Y-arm and diff vco. Re-visited Y arm alignment. H1:SUS-ETMY_M0_LOCK_Y_OUT16 took a rather long time to decide where it wanted to settle down.

19:00  OMC locked on wrong mode: After playing with OMC guardian and LOCK_00, then tripping the OMC watchdog and having to request align a few times, I got OMC back locked on the proper mode. 19:18 NOTE TO SELF: make sure that after manually locking OMC to advance the OMC Guardian node to “READY_FOR_HANDOFF” before manually pushing DC_READOUT. D’OH!

19:58  Re-locked at NLN

20:01  set intent bit to Undisturbed

00:00 Set intent bit to Commissioning for Robert to do some injections. This is being done in cooperation with Livingston.

NOTE:  We tested 2-way radio (walkie/talkies) between 1420 - 1430 hrs. local

This week we were able to install and caulk metal strips on the upper portion of 120 meters of enclosure.

Total of 36.55 hours of OTL dues to faults during month of October 2015.

3928  is marked as new. ITMY did not misalign as requested by the script. PR2 and IM4 alignment REFL WFS not running. This is still being investigated.

3926 is marked as closed procedural. This fault was due to a human error. The actuation amplitude was too strong in the template and will be reduced to avoid this in the future.

3925 is marked as new.  The interferometer broke lock when aborting a measurement of the CHARD P open loop (swept sine excitation) using DTT. This is still being investigated.

3922 is marked as work in progress. To avoid Guardian nodes from hanging, it is now standard operating procedure to reboot the Guardian machine following a DAQ process restart, which is scheduled weekly at the end of the Tuesday maintenance period. However, there is a concern that there is a potential that this could re-occur should we need to restart these vulnerable Guardian nodes while the IFO is locked, resulting in a lock loss and more significant down-time. This is still being investigated.

3916  is marked as work in progress. Suspensions WD can trip during an alignment and be set to bad positions. Audible alarms should be set to avoid missing a suspension or SEI that tripped. These are not yet set up.

3895  is marked as closed unavoidable. Effect of glitch was limited i.e  PSL tripped but Front Ends did not. Recovery from power glitch was very smoothly done by LLO staff

3863 is marked as closed unresolved.  Alarms handlers have been set for operators to be informed should this issue arise again. We may wish to consider options for implementing something in Guardian.

3860 is marked as closed duplicate  of  Fault Report 3141 - MASTER: Beckhoff communication issue. We will monitor for a reoccurence

3846  is marked as closed unresolved. For some reason performing this transition only worked at a smaller CARM offset . It's not clear what necessitated this change. We will monitor for a repeat occurence.

3830  is marked as closed resolved. The settings were not saved correctly under the safe snap file which was restored during the model restarts -cf https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=21832-. The safe snap file has been corrected  to prevent a repeat occurence.

3828 is marked as closed unresolved.  Don't know what the root cause is yet. A note on a work around procedure has been added to the Operator Wiki.  We will monitor for a repeat occurrence

3825 is marked as closed procedural. This was an OOPS. Detector engineers miscommunicated interaction  between PSL work and affect on ALS.  Awareness has been shared which should prevent a reoccurrence

3823 is marked as closed resolved. This resulted in two action items one to look into widening  control limits on the front end watchdog which is programmed so that it trips at 15% loss of power from when it was activated and the other to close training gap on single operator on PSl restart procedure.

3808  is marked as closed resolved. Required spare PZT controller to be installed.   Root cause of the failure of the controller is still under investigation and being monitored for a  repeat occurrence.

3796  is marked as pending. This is not likely to be addressed until a future RCG update, and so it was recommended that we turn off monitoring of DACKILL channels in IOP models until the fix is available.

3793 is marked as closed resolved. The BS OpLev Guardian settings were widened which should prevent a reoccurrence

3747 is marked as closed resolved. The ISC_Lock Guardian has been modified which should prevent a reoccurrence

3744 is marked as closed resolved.  We will monitor for a reoccurence

RF45 has been quiet since I and Evan made an investigation last time (alog 23125).

One thing we didn't do in the PSL room was to wiggle/tap the EOM inductor box and its connectors. Next time it acts up, we should try that. FYI, inductor box is the top part of EOM assembly that accepts the cable from EOM driver, and is connected to the lower part where the crystal sits by now infamous DB15.

MID-SHIFT SUMMARY: After losing lock, for reasons not apparent to me, there was some difficulty getting re-locked that included initial alignment (PRMI wouldn't lock), diff VCO woes, OMC locking on wrong mode and Jenne helping with wait times for ASC loops. Finally back to NLN at 20:00UTC. Wind is ≤5mph. EQ Sei is ≈t .28µ and µSei is ≈.12µ.

Following on from Hugh's alog entry (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=22883) about the reference
cavity temperature and HEPI hitting its software limit ... Attached are two plots of the reference cavity temperature:
an in the loop measurement (H1:PSL-FSS_DINCO_REFCAV_TEMP) and out of loop measurement (H1:PSL-FSS_DINCO_REFCAV_TEMP_OOL).

The coefficient of thermal expansion for Corning 7940 is 0.52E-6 / degC.  For the ~0.01 degC change this corresponds
to a length change in the reference cavity of 5.2 nm, or a dL/L of 2.6E-8.  Assuming the equivalent dL/L for HEPI is
6.3E-8 (250E-6/4000) then the temperature change doesn't fully explain why HEPI hit its limit.

However temperature regulation of the reference cavity wouldn't hurt, particularly if done at a point higher than room
temperature.  The hardware is already there, modulo a small change to bring the heater front end model to reflect the
installed cabling - a post observing run task.

TITLE: Nov 6 DAY Shift 16:00-00:00UTC (08:00-04:00 PDT), all times posted in UTC

STATE Of H1: Observing

OUTGOING OPERATOR: Patrick

QUICK SUMMARY: IFO is in Observing @ ≈80Mpc. Eq sei bands are all in the .2micron range. µSei is around .2µ. Wind is 0mph. All light appear to be off in E, M, CS & PSL. CW injections are running. Cal lines are running. Livingston is up and running. Quite 90 blends being used.

TITLE: 11/06 [OWL Shift]: 08:00-16:00 UTC (00:00-08:00 PDT), all times posted in UTC
STATE Of H1: Locked. Observing @ ~ 80 MPc.
SHIFT SUMMARY: Locked and observing entire shift. Possible EPICS freeze. SUS ETMY saturations.
INCOMING OPERATOR: Ed
ACTIVITY LOG:

10:07 - 10:16 UTC Stepped out of control room

SUS E_T_M_Y saturating (Nov 6 09:02:02 UTC)
SUS E_T_M_Y saturating (Nov 6 09:02:04 UTC)
Current time: Nov 6 10:00:00 UTC
SUS E_T_M_Y saturating (Nov 6 10:41:05 UTC)
Current time: Nov 6 11:00:00 UTC
SUS E_T_M_Y saturating (Nov 6 11:26:53 UTC)
Current time: Nov 6 12:00:00 UTC
Current time: Nov 6 13:00:00 UTC
Current time: Nov 6 14:00:00 UTC
SUS E_T_M_Y saturating (Nov 6 14:22:30 UTC)
SUS E_T_M_Y saturating (Nov 6 14:22:32 UTC)
SUS E_T_M_Y saturating (Nov 6 14:22:35 UTC)
Current time: Nov 6 15:00:00 UTC
SUS E_T_M_Y saturating (Nov 6 15:46:04 UTC)
SUS E_T_M_Y saturating (Nov 6 15:46:07 UTC)

~ 13:55 UTC Noticed brief flatline in striptools. Doesn't appear to have affected anything.

Have remained locked and in observing. Rode through what appears to be two small earthquakes.

TITLE: 11/06 [OWL Shift]: 08:00-16:00 UTC (00:00-08:00 PDT), all times posted in UTC
STATE Of H1: Observing @ ~ 81 MPc.
OUTGOING OPERATOR: Cheryl
QUICK SUMMARY: From the cameras the lights are off in the LVEA, PSL enclosure, end X, end Y and mid X. I can not tell if they are off at mid Y.
Seismic in 0.03 - 0.1 Hz band is between .007 and .03 um/s. Seismic in 0.1 - 0.3 Hz band is between 0.08 and 0.3 um/s. Winds are less than ~ 5 mph.
ISI blend filters are on Quite_90.

Title: Ops Eve Shift Summary, 00:00UTC to 08:00UTC1(6:00PT to 23:59PT), all times UTC

State of H1: locked in Observe 12+ ours, Range is 81Mpc

Incoming Operator: Patrick

Shift Summary: quiet evening with good range

Shift Activities:

- 00:07:01UTC ETMY saturation

- 00:09:00UTC, Kyle called and reported that he and Gerardo were back from x28 port 

- 01:08:23UTC ETMY saturation

- 01:08:26UTC ETMY saturation

- around 01:21UTC, earthquake arrived

Time: Fri Nov 06 01:09:55 UTC 2015

Location: 87km SSW of Nikolski, Alaska; LAT: 52.3, LON: -169.5

Magnitude: 5.5

- 03:57:03UTC ETMY saturation

- 04:19:40UTC ETMY saturation

- 04:40:56UTC ETMY saturation

Cheryl emailed me to say that the durations shown by GWIstat were incorrect.  I looked and it turns out that GWIstat (and also gwsnap) got restarted by Condor a few times today, for reasons which are not yet clear.  Each time it restarts, the duration counters for LHO and LLO get reset to zero, since the program doesn't currently have a way to look back in time to set the duration properly.  But I have added a little code to add a greater-than sign on the duration when the program restarts, until the status changes, so at least there will be a visual indicator that the duration shown is just a lower bound.

Lost lock about 2 hours ago, not sure why. Trying to relock now, but DRMI is not cooperating. Otherwise, things are quiet. Winds down, useism is down. RF45 has not been awful.

J. Kissel, K. Izumi, N. Kijbunchoo

We've gathered new DARMOGLTF measurements to continue our long-term investigating on the slow evolution of the calbriation parameters. Based on what I see in DTT alone, the uncorrected loop gain and pcal to CAL-CS transfer function remains within 5% and 5 [deg] of the reference model. Very good! I attach screen shots of the raw measurements and a conlog of the relevant settings, but more detailed analysis to come.

The new DTT results live here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/DARMOLGTFs/2015-10-28_H1_DARM_OLGTF_7to1200Hz.xml
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/PCAL/2015-10-28_PCALY2DARMTF_7to1200Hz.xml

and have been exported to the following:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/DARMOLGTFs
 1 / (1 + G) = 2015-10-28_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKEXC_coh.txt 
               2015-10-28_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKEXC_tf.txt
         -G  = 2015-10-28_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKIN1_coh.txt
               2015-10-28_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKIN1_tf.txt

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/PCAL/
C / (1 + G)  = 2015-10-28_PCALY2DARMTF_7to1200Hz_A_PCALRX_B_DARMIN1_coh.txt
               2015-10-28_PCALY2DARMTF_7to1200Hz_A_PCALRX_B_DARMIN1_tf.txt