• TITLE: 12/21 Eve Shift: 00:00-08:00UTC (16:00-00:00 PDT), all times posted in UTC"

• STATE Of H1: Observing, locked for 16 hrs

• OUTGOING OPERATOR: Jim W

• QUICK SUMMARY: RF45 is back!!! the past 2 hours os so the IFO has been plagued by the RF45 noise. There are people in the control room investigating but in the mean time I guess the plan is to stay in Observing and just make sure that the data is flagged.

• Wind <20mph, useism 0.8um/s, PSL 21.9W, CW inj running.

TITLE:    Dec 21 Day Shift 08:00-16:00UTC

STATE Of H1: Observing, RF45 is acting up

SUPPORT: Typical control room crowd

SHIFT SUMMARY: I took over for Cheryl at 21:30, thing were quiet until RF45 started acting up at 23:30, still in observe, but data is obviously bad

ACTIVITY LOG:

21:20 JeffK Running pcal to darm tf, llo calls to say they are at dc readout, done 22:30

22:00 Bubba to Mid-Y, back 24:00

45 MHz stabilization started gitching circa 23:15:00 Z.

This was accompanied by a drop of a few percent in AS90.

Nothing is visible in the spare amplitude demod on the ISC rack (23567). Noise appears stationary with an rms of a few millivolts, meaning the RAN of this glitch at the ISC rack (not including the EOM driver chain) is less than a few parts in 10⁵.

J. Kissel

Another collection of our bi-monthly(-ish) assessment of the calibration and DARMOLGTF. Details will be processed later including analysis of time-dependence. The front-end, CAL-CS, DELTAL_EXTERNAL calibration (and therefore the low-latency GDS pipeline output) is still within the desired precision. I attach screenshots of the measurements for posterity. Note, this time, I've updated the reference to be the most recent sweep, taken Dec 01 2015, (see LHO aLOG 23883, also yet to be processed.)

DARM OLGTF Template:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/DARMOLGTFs/2015-12-21_H1_DARM_OLGTF_7to1200Hz.xml

Corresponding Exports: 
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/DARMOLGTFs/
2015-12-21_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKEXC_coh.txt
2015-12-21_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKEXC_tf.txt
2015-12-21_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKIN1_coh.txt
2015-12-21_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKIN1_tf.txt

PCAL2DARM TFs:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/PCAL/2015-12-21_PCALY2DARMTF_7to1200Hz.xml

Coresponding Exports:
2015-12-21_PCALY2DARMTF_7to1200Hz_A_PCALRX_B_DARMIN1_coh.txt
2015-12-21_PCALY2DARMTF_7to1200Hz_A_PCALRX_B_DARMIN1_tf.txt

Title: Ops Day Shift, 16:00-23:59UTC, 08:00-16:00PT

State of H1: in Oberve for almost 12 hours, range is 74.3Mpc

Details: some site activites, useism is around 0.7um.s, winds 5-15mph

work today:

- follow up on glitch and range drop around 14:00UTC

- CDS - Richard tomorrow/today, audio signal

- Bubba at MY and MX

work tomorrow Maintenance:

- Hugh rezero TS2's at end stations

- Richard, audio signal

- Bubba, forklift work, clean room curtains at EY, switch fans at EY, pick up welder at EX

- Jason, BS and SR3 oplevs

- Sudarshan/Darkhan, possible pcal calibration at Y end

- Jeff, forklift PSL chiller

Attached are 7 day pitch, yaw, and sum trends of all active H1 optical levers.

State if H1: in Observe

Plot 1 shows the RF AM stabilization out-of-loop sensor and the control signal. Over the past 30 days there were 5 clearly visible glitches in the control signal. These are reflected in the out-of-loop sensor. However, there are two non-stationary episodes in the sensor signal which have only a negligible counterpart in the control signal.

Plot 2 shows the same traces over the past 120 days. Overall, the glitches seem to have reduced in size and frequency for no apparent reason.

Activity Log: All Times in UTC (PT)

08:00 (00:00) Take over from Ed
11:15 (03:15) High heat alarm for CS Zone 4 duct temperature, (101.16F). Will monitor.
13:08 (05:08) Four ETM-Y saturations (18:08:33, 37, 40, 44), with a marked drop in range to ~ 63Mpc
16:00 (08:00) Turn over to Cheryl    


End of Shift Summary:

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

Support:  None
 
Incoming Operator: Cheryl

Shift Detail Summary: Locked in Observing mode for past 8 hours. Power at 21.8w, range 79Mpc. Wind is light to gentle breeze (4-12mph). Seismic is improving with a downward trend for the past 6 hours. Microseism is also decreasing, but at a much slower rate than seismic. 

Other than 4 ETM-Y saturations (within 11 seconds), which took the range down to a low of 63Mpc, there were no problems or issues during the shift.  

    All quiet on the western front. IFO is in Observing mode, with 21.8W, and 81.5Mpc of range. The wind, seismic, and microseism have remained constant over the first 4 hours of the shift. For the most part generally good data collecting conditions prevail. 

           Transition Summary:
Title:  12/21/2015, Owl Shift 08:00 – 16:00 (00:00 – 08:00) All times in UTC (PT)
	
State of H1: 08:00 (00:00), The IFO has just relocked. Power at 21.9W, range 78Mpc. Wind is variable up to a moderate breeze (18mph), seismic and microseism remain high.        

Outgoing Operator: Ed

TITLE:    Dec 21 EVE Shift 00:00-08:00UTC (16:00-00:00 PDT), all times posted in UTC

STATE Of H1: Observing @ 80Mpc

SUPPORT: N/A

INCOMING OPERATOR: Jeff B

SHIFT SUMMARY: Lots of trouble with µSei and a bit of wind that blew up. The details are in the activity log. ISI Blends set to 45Mhz around the board except for ETMX off axis

ACTIVITY LOG:

01:15 Trouble with input align. PR2 pointing was bad. Yaw was off by 6µrads

01:18 Dark mitch still won’t grab. µSei is now peaking around 1.5µm/s. Wind is still NOT an issue. The beam splitter appears to be really feeling the ground motion.

02:50 Touched base with Jenne just to apprise her of the IFO situation

03:00  took ISC_LOCK to down. There doesn’t seem to be any locking (ie Dark Mich, PRMI or DRMI) going on in my near future. uSeism is still trending above 1um/s and the BS is jumping all over itself. th wind has also blown up to >= 20mph at EY.

05:58 PRMI locked! (first small victory)

06:01 DRMI Split mode. no time to tweak.

06:08 DRMI Split mode. no time to tweak.

06:14 DRMI Split mode. no time to tweak.

06:24 Lockloss. IMC broke lock.

06:57 DRMI LOCKED!!!!

07:05  John called to tell me that he was turning on some heat in the LVEA. (H1CA)

07:13  Lost lock at COIL_DRIVERS. grrrrr

08:02 NLN!

08:04 intent it set to Observing

I noticed that the LVEA temperature control was running out of range so I have added an additional stage of heat.

HC1A control has been set to 15ma (was 4 ma) It appears that the first stage heater is not working so this should turn on the second stage.

The duct temperature is behaving normally - first plot. Second plot shows the face bypass dampers railing at 7ma.

Max, Chris

Summary:

We tested scheduling the burst injections. The purpose of this test was to test the burst pipeline hardware injection recovery as outlined in the O1 plan.

The initial aLog is here: aLog entry

Waveform:

The waveform parameters are here: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/config/Burst/Waveform/WNB_burst_1134573920_1.info

The waveform file for H1 and L1 are: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/config/Burst/Waveform/WNB_burst_1134573920_1_H1.txt https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/config/Burst/Waveform/WNB_burst_1134573920_1_L1.txt

First Test:

The first test was scheduled for 1134577813. The schedule file was given:
1134577813 2 1.0 WNB_burst_1134573920_1_

This injection failed.

It failed because the waveform files ended in .dat instead of .txt. tinj was updated but the documentation for performing hardware injections document was not!

Max and I checked the PINJX_TRANSIENT EXCMON channel to confirm that a signal did not go into the inteferometers.

Second Test:

The second test was scheduled for 1134581196. We renamed the waveform ASCII files and the schedule file was given:
1134581196 2 1.0 WNB_burst_1134573920_1_

This injection was successful.

cWB already picked up the injection. See gracedb link: gracedb entry

Action Items

  * The documentation for burst injections needs to be updated with the correct filename.