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.

[JeffK, Jenne]

More thought required, but here is a plot overlaying the power recycling gain as measured by PD DC powers, and the optical gain as measured by the calibration lines.  Both of them are normalized, so that we are looking at percent changes rather than absolute values.  The calibration line data is taken from Sudarshan's aLog 22908.

I noticed that the End station temperature had just started to climb rapidly so I checked out the chilled water system and found CWP1 tripped off. Since this pump tripped earlier in the week with no obvious reason I elected to start the alternate pump CWP2. The VEA temperature is returning.

Marie at LLO has finalized the calibration / conversion from the A2L gain to actual beam spot position, and posted the LLO results at aLog 22426.  I have downloaded the updated code, and redone the plots of LHO results, and it's still clear that our beam positions change very little lock-to-lock.

Again, the color of the spot indicates the length of time since the power-up:  blue is a cold IFO, and more pink is a warmer IFO.

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

STATE Of H1: Observing

SUPPORT: N/A

LOCK DURATION: Entire shift

INCOMING OPERATOR: Cheryl

END-OF-SHIFT SUMMARY: IFO locked the entire shift.(currently 74.1Mpc) The winds picked up to over 20mph twice but for short periods. GraceDB Ext Not system continues its vener ending pass/fail cycle. Sei and µSei remain the same. Handing off to Cheryl.  

ACTIVITY LOG:

16:30 Chris called to inform me that he would be heading out to do  the aluminium stripping on the X arm

17:07 Joe out to join Chris on the Xarm

17:10 Karen into CS mechanical room to swiffer

17:15 Increase in EQ band x-axis to .1µm/s due to a pair of earthquakes around New Guinea and Timor

17:30 Winds increasing to ≤20mph

18:17 Joe back temporarily to get necessaries then heading back out. Chris is back and out to an appointment

19:57 Joe back from x-arm, for now.

21:00 X-arm crew back out to work

21:34  Noticed a slight downward trend in range starting about 2 hours ago. µSeism is around .3 mocrons

21:38  Kyle asked about driving forklift from shipping and recieveing area of OSB to woodshop for loading a generator to bring to X-2-8. I recommended that he doesn’t do that at this time as we are in coincidental observing mode with Livingston. I will contact him if we should break lock.

21:44  Got the OK from Landry to move the green forklift from LSB for the abovementioned task.

21:48 John W informed me that they were fixing the FMCS computer and that I was going to get some errors and alarms. ie;   CS temperature is low (Nov 5 21:48:23 UTC)

22:59 Range is back up to 80Mpc

23:08  Joe reported back from X-arm. Chris will follow shortly.

23:30  Dave Barker will be going into the MSR to change tapes.

MID-SHIFT SUMMARY:  Nothing big to report except for some ETMY glitches (usual). the wind picked up for a bit, around 20mph, but it’s starting to die down. Also, one GraceDB External Notification script failure and recovery as I’m writing this. (that I’ve noticed).

I have posted the latest LHO calibration uncertainty plots.

I have reduced our kappas' uncertainty to 1% in mag and 0.5 degrees in phase.  We are now limited by our measurements.

I believe that our "statistical uncertainty only" plots are underestimating error.

This is because the systematic error that remains in our measurements is ignored when we consider only the uncertainty bars.  
One way to combat this underestimation is to not fit our systematic to the final weighted mean of all our measurements, but instead fit to each of our measurements and take the std of our remaining systematic errors as our total systematic error.  This ought to fix the fact that I was ignoring remaining systematic errors in our "statistical uncertainty only" plots.

Plots 1-4 show nominal O1 model mag and phase uncertainty (the statistical uncertainty and systematic error summed in quadrature).  
Plots 5-8 show the systematic corrections model mag and phase uncertainty (statistical uncertainty only).  I believe these are currently underestimated.
Plot 9 is the comparison of the nominal O1 calibration response function to the systematic corrections model I make.  (The red line is the systematic correction model, the dashed lines are the associated uncertainty)

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

In light of the violin mode stuff over the weekend, I wanted to make sure we aren't going to be caught unawares by other harmonics ringing up.

We have paid considerable attention to damping the fundamentals and second harmonics of the violin modes, but in general we leave the higher harmonics undamped. (We have had some isolated cases in which we have had to temporarily apply damping to high harmonics; see, e.g., LHO#18599).

I checked the heights of the third harmonics during the first long lock (25 hours long) that we had after the power outage. I chunked the DCPD sum timeseries into 1000 s segments and then took ASDs of each. To identify the violin modes, I simply looked for peaks in the DCPD spectrum that were higher than some threshold above the noise (in this case, the noise floor is about 1×10⁻⁷ mA/Hz^1/2, and the threshold I chose was 5×10⁻⁶ mA/Hz^1/2). This resulted in 25 peaks being identified. For each ASD, I integrated under each peak to get an rms mode amplitude. Since the violin modes are anharmonic, I believe that these peaks (which range in frequency from 1456.18 Hz to 1484.67 Hz) are truly third harmonics, rather than upconverted first harmonics (which range from 498 to 509 Hz, and hence we would expect upconversion to appear from 1496 to 1527 Hz).

All 25 peaks appear to be ringing down, with time constants on the order of 2×10⁵ s (≈50 hours). I fitted each ringdown to an exponential, which resulted in Qs ranging from 0.55×10⁹ to 1.28×10⁹. [For similar results on lower-order mode Qs, see, e.g., Keiko's measurements on L1 IY.]