Activity Log: All Times in UTC (PT)

23:00 (16:00) Take over from TJ
23:15 (16:15) Complete initial alignment. 
23:16 (16:16) Trying to relock
23:37 (16:37) Sheila left the site
00:00 (17:00) Put IFO in down state until wind and seismic calms down.  
02:05 (19:05) Robert S. left the site
02:15 (19:15) Wind below mostly 30 mph - trying to relock
02:35 (19:35) Wind back up, gusts near 40 mph– Cannot get past LOCKING_ALS, will wait for things to settle a bit more
04:18 (21:18) Wind up and down; Seismic still high. Tried relocking with same negative results 
04:43 (21:43) After 12 lockloss at LOCKING_ALS in 12 locking attempts and now seeing wind gusts up to 50+ mph, put the IFO in a DOWN state waiting for Mother Nature to relax  
06:28 (23:28) Wind dropping but still gusty, seismic activity still high. Going to give locking another try
07:00 (00:00) Turn over to Travis


End of Shift Summary:
Title: 10/10/2015, Evening Shift 23:00 – 07:00 (16:00 – 00:00) All times in UTC (PT)

Support: Sheila, Elli

Incoming Operator: Travis

Shift Summary: 
- After many tries cannot get past ALS locking state. Wind still over 35 mph with gusts to mid-50s. Will wait until settle down before trying to relock.

- Turned on Jim W. 45 mHz ST1 blends on ITMY while trying to lock (04:18 to 04:43). Saw no difference in the behavior of Y and X during ALS locking. Saw no apparent difference in behavior of the ALS locking with the 45 mHz or Quite_90 ST1 Blends.  
- Wind strong and gusty all shift. Seismic activity also high all shift. The wind is still in the upper 20s and gusty, although it is trending lower. In the past 30 have been able to get to LOCK_DRMI_1F before lockloss. Conditions are improving.  

   Wind had settled a bit (in the teens and 20 mph range) but seismic activity still high. I tried to relock using the 45 mHz Blends, supplied by Jim W, on ITMY. There was no observed difference in the locking/lockloss behavior with the 45 mHz or Quite_90 Blends. I restored the Quite_90 Blends on ITMY.

   Note: While trying to relock this time the wind came back up into the 20s and 30s with several gusts in the 40s, and a couple of gusts over 50 mph. I don't know how good a test of the 45 mHz Blends this was.       

   IFO has been unlocked all shift. Wind is still high (gusts in the 50s mph) but calming down. Mostly wind is in mid 20s to low 30s. Seismic activity is still high but also settling down. Tried relocking about 30 minutes ago, with no luck. Still cannot move beyond LOCKING_ALS. As conditions improve will continue to try relocking. 

Title:  10/10/2015, Evening Shift 23:00 – 07:00 (16:00 – 00:00) All times in UTC (PT)

State of H1: At 23:00 (16:00) Unlocked due to high wind and seismic activity. Running initial alignment. 

Outgoing Operator: TJ

Quick Summary: Wind is high 35mpg with gusts to over 40mph; seismic activity is also high. At shift change, TJ was finishing an initial alignment. Now trying to relock.      

Title: 10/10 Day Shift 15:00-23:00 UTC (8:00-16:00 PST).  All times in UTC.

State of H1: Unlocked, high winds and high microseism

Shift Summary: Locked until 21:24, haven't been able to relock since due to environment issue.

Incoming operator: Jeff B.

Activity log:

• 15:32 ETMY sat.
• 15:58 Out of Observing, Robert starting PEM inj
• 16:30 Robert to LVEA
• 17:10 Robert out of LVEA and going to area inside vertex to tamp
• 17:50 Robert, Chris back
• 18:10 Robert into LVEA
• 18:14 Robert out, LVEA swept
• 18:17 Observing
• 19:29 ETMY sat. (x2)
• 19:45 Hanford Fire Dept. Driving to MY to check on a panel that was giving them an alarm
• 20:01 Fire Dept. back, all is well
• 20:58 Sheila starting A2L script while LLO is down
• 21:24 Lockloss
• 22:28 Starting Initial Alignment, maybe it will help in these high winds
• 22:29 Ken and his Parents going into the CER
• 22:38 Ken and company out

After the lockloss at 21:24 UTC we haven't been able to lock since.

A few possible environmental factors for these locking woes:

• High winds - Gust up to 55 mph at EX
• High microseism - This has been up for the past 24 hours and hasn't gone down yet.

Out of Observing so Sheila can run her A2L script while LLO is down (WP#5552)

Observing at ~75Mpc. LLO was up for an hour or so but they are back down. The Hanford Fire Dept had to drive to MY to check a panel that was giving them an alert. Gardening crew is still on site and so is a tour group.

1. The re-calibrated C01 hoft data now exist at CIT.

The results of some quick tests are given below.

The calibration group should decide if it wants to do further testing before we announce that this data is ready for analysis.

Updated missing data and DQ flags are also yet to be inserted into the segment database.

2. The filter files and command line arguments used with gstlal_compute_strain are documented here:

https://wiki.ligo.org/Calibration/GDSCalibrationConfigurations

3. The frame-types, channels names, and DQ flag names are documented in the DCC here:

https://dcc.ligo.org/LIGO-T1500502

Specifically, the frame-types are H1_HOFT_C01 and L1_HOFT_C01 and exist for:

H1: 1125969920 == Sep 11 2015 01:25:03 UTC to 1128398848 == Oct 09 2015 04:07:11 UTC

L1: 1126031360 == Sep 11 2015 18:29:03 UTC to 1128398848 == Oct 09 2015 04:07:11 UTC

4. I have update the times C01 exists on the GDS calibration configuration pages, on the O1 Run page, and in the DCC document:

https://wiki.ligo.org/Calibration/GDSCalibrationConfigurations
https://wiki.ligo.org/LSC/JRPComm/ObsRun1#Calibrated_Data_Generation_Plans_and_Status
https://dcc.ligo.org/LIGO-T1500502

(And the wiki pages, https://wiki.ligo.org/Calibration/T1500502_Prototype_Info points to the DCC document.)

5. Missing data flags and updated DQ flags are yet to be inserted into the segment database, pending generating these and an OK to proceed.

Here are some important details:

There is no missing H1_HOFT_C01.

There are gaps in L1_HOFT_C01 due to times when there were bad dataValid flags in the raw 64 s L1_R data. These gaps have been reduced down to the times of those raw frames -/+ 16 wings needed for filtering.

The times of the gaps in L1 C01 hoft intersected with L1_DMT-ANALYSIS_READY:1 are:

$ ./compareSegLists.tcl -f1 segs_MISSING_L1_HOFT_C01.txt -f2 segs_L1_DMT-ANALYSIS_READY_1.txt -i -s -T
1127128496 1127128592 96
1127353008 1127353104 96
1127387760 1127387856 96
1127435760 1127435856 96
1127687856 1127687952 96
1128122032 1128122075 43
1128122086 1128122128 42
1128320816 1128320912 96
Total duration = 661 seconds.

The UTC time of raw L1_R data with bad dataValid flags that intersect L1_DMT-ANALYSIS_READY:1 are:

$ ./compareSegLists.tcl -f1 segs_MISSING_L1_HOFT_C01.txt -f2 segs_L1_DMT-ANALYSIS_READY_1.txt -i | awk '{sum = $1 + 16; print sum}' | xargs -l tconvert
Sep 24 2015 11:14:55 UTC
Sep 27 2015 01:36:47 UTC
Sep 27 2015 11:15:59 UTC
Sep 28 2015 00:35:59 UTC
Sep 30 2015 22:37:35 UTC
Oct 05 2015 23:13:51 UTC
Oct 05 2015 23:14:45 UTC
Oct 08 2015 06:26:55 UTC

Most of the above seem associated loss or gain of lock. For example, see the drop out in L1 lock segments near Sep 24 2015 11:14:55 UTC here:

https://ldas-jobs.ligo-la.caltech.edu/~detchar/summary/day/20150924/

Gaps have been filled in when C00 was missing during maintenance days after DMT calibration restarts, but none of these intersect with L1_DMT-ANALYSIS_READY:1

Bottom line: The analysis using the C01 hoft will lose 661 s of L1 ANALYSIS_READY time due to bad dataValid flags.

6. The data is available via NDS2 and using gw_data_find.

Quick test show no issues, e.g., in these example comparison plots between GDS online and DCS offline C01 spectra from Oct 9 (i.e., after Oct. 6 filter updates):

https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=99928
https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=99929

And for example, calibration factors (which are not applied) now agree too, e.g., for L1:

https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=99835
https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=99836
https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=99839

The calibration group should decide if it wants to do further testing.
 

Back to Observing at ~73Mpc after Robert's work, LLO is still down.

While LLO is down, Robert will do some injections

• Title: 10/10 DAY Shift: 15:00-23:00UTC (8:00-16:00PDT), all times posted in UTC
  

• State of H1: Observation Mode at 74Mpc
  

• Outgoing Operator: Travis
  

• Quick Summary: No issues, it was locked his whole shift with a handful of saturations as usual. Microseisms are VERY high, wind is between 5-20mph, and LLO is currently down.

Title: 10/10 Owl Shift 7:00-15:00 UTC (0:00-8:00 PST).  All times in UTC.

State of H1: Observing

Shift Summary: Locked for the entire shift in Observing.  Wind and seismic calm.  A typical number of ETMy saturations.

Incoming operator: TJ

Activity log:

14:45 Landscapers on site

Locked in Observing Mode for the past 12 hours.

Activity Log: All Times in UTC (PT)

23:00 (16:00) Take over from Ed
23:00 (16:99) Intent Bit set at Observing
23:40 (16:40) Finished GRB hold
23:58 (16:58) Kyle & Gerardo – Back from Mid-Y
06:15 (23:15) Nutsinee – Left the site
07:00 (00:00) Turn over to Travis


End of Shift Summary:

Title: 10/09/2015, Evening Shift 23:00 – 07:00 (16:00 – 00:00) All times in UTC (PT)

Support: Marissa

Incoming Operator: Travis

Shift Summary: 
- 23:00 (16:00) IFO locked. Intent Bit set to Commissioning. Wind is moderate, some seismic activity.     
- 23:00 (16:00) Received GRB alert at 22:40 – Held site in stand down mode until 23:40 (16:40).

    A smooth and quiet shift. Some wind (gust up to mid 30mph) and moderate seismic activity in first part of shift. Wind and seismic activity settling down toward end of shift. Had nine (9) saturation alarms during shift.     	

   IFO has been locked at NOMINAL_LOW_NOISE, 22.4w, 76Mpc, in Observing mode for first four hours of the shift. The wind is moderate (between 5 & 20mph), microseism is steady at <0.5micron/s. Higher frequency seismic activity has been declining all shift.    
   In a GRB hold from 22:40 (15:40) to 23:40 (16:40.)
   There have been six (6) ETM-Y saturation events thus far this shift. All other IFO vital signs are normal.   

Kyle, Gerardo 

1140 hrs. local -> Spun up LD, Turbo and QDP80  

1330 hrs. local -> 7.1 x 10-8 torr*L/sec with cal-leak open -> closed cal-leak -> < 10-11 torr*L/sec with cal-leak closed -> Calibration is OK

1335 hrs. local -> Valved-in Turbo to Y-mid volume -> Y-mid background initially found to be 1.8 x 10-8 torr*L/sec -> Fell steadily to 8 x 10-9 torr*L/sec over the next 60 minutes of pumping

Begin Testing

1435 hrs. local -> Began leak testing aLIGO GNB spool welds -> "Bagged" flange-to-spool welds in 180 degree sections -> Applied 5 LPM helium flow at bottom of bag and pumped at top of bag via O2 sensor/pump -> Started 100 second timer when 0% < O2 < 7% -> No response for either flange (4 bagged sections) -> Tested butt welds of cylinder spool roll -> Bagged butt weld in three sections (from flange to stiffener, between stiffeners and from stiffener to other flange) -> Background remained steady at 8 x 10-9 torr*L/sec during entire test period until a few seconds before the conclusion of the last weld test at which point it began to climb -> Stopped helium flow -> signal continued to climb -> removed bags from two most recent welds tested -> signal continued to rise -> Signal peaked at 1.2 x 10-7 torr*L/sec (tens of minutes after stoppage of helium flow) -> Isolated LD from Turbo exhaust -> signal immediately fell to < 10-11 torr*L/sec -> Recombined LD to Turbo exhaust -> Opened up building exterior doors to air out room.  

1645 hrs. local -> Valved-out turbo from Y-mid volume and shut down LD and pumps with Y-mid background at 4.6 x 10-8 torr*L/sec. 

Conclusion:  In retrospect, we should have reduced the helium flow rate once a minimum O2% was achieved.  As is, we put more helium into the room that was necessary (calculate a total of 85 liters over 90 minutes).  As such, we cannot conclude that the last weld tested was the source of the signal response.  We did demonstrate, however, that there is a leak(s) at the Y-mid (as opposed to other explanations) when we isolated the LD from the Turbo exhaust and the signal immediately fell off.

I propose that for the next session we pump the Y-mid with the turbo for a few hours to get the background back into the 10-9 range then revisit the last two butt welds tested.   

C. Cahillane

I have finally decided to check if linearly adding A_pu for uncertainty is okay.  It turns out it's conservative, and we get lower uncertainty bars if we propagate correctly.
The equation for A_pu is:
A_pu = A_pum + A_uim 

We had been propagating uncertainty linearly like this:
σ_|A_pu| = |A_pum| * σ_|A_pum| + |A_uim| * σ_|A_uim|
σ_φ_A_pu = σ_φ_A_pum + σ_φ_A_uim

This is bad.
The correct way to propagate it is quadratically.  I do not yet have a nice write-up of my equations, but they will be included in DCC T1400586 hopefully soon.  There is no mysterious method of uncertainty propagation used, just simple first order Taylor expansion.
The plot below is my comparison of the correct vs. linear uncertainty propagation.
Plot 1 is the comparison including systematic errors in uncertainty.  Plot 2 is statistical uncertainty only.

Summary:

We had single-IFO time so I tested the new inverse actuation filter for PCALX. WP5530

Sudarshan and I believe we tracked down the factor of 2 and sign error from the initial PCALX test, see aLog 22160. We wanted to do this test to confirm that.

CBC injections:

The waveform file is: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/Inspiral/H1/coherenttest1from15hz_1126257408.out

The XML parameter file is: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/Inspiral/h1l1coherenttest1from15hz_1126257408.xml.gz

I did three CBC injections. The start times of the injections were: 1128303091.000000000, 1128303224.000000000, and 1128303391.000000000.

The command line to do the injections is:
ezcawrite H1:CAL-INJ_TINJ_TYPE 1
awgstream H1:CAL-PCALX_SWEPT_SINE_EXC 16384 coherenttest1from15hz_1126257408.out 1.0 -d -d >> 20151006_log_pcal.out
awgstream H1:CAL-PCALX_SWEPT_SINE_EXC 16384 coherenttest1from15hz_1126257408.out 1.0 -d -d >> 20151006_log_pcal.out
awgstream H1:CAL-PCALX_SWEPT_SINE_EXC 16384 coherenttest1from15hz_1126257408.out 1.0 -d -d >> 20151006_log_pcal.out

I have attached the log. I had to change the file extension to be posted to the aLog.

DetChar injection:

I injected Jordan's waveform file: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/detchar/detchar_03Oct2015_PCAL.txt

The start time of the injection is: 1128303531.000000000

The command line to do the injections is:
awgstream H1:CAL-PCALX_SWEPT_SINE_EXC 16384 detchar_03Oct2015_PCAL.txt 1.0 -d -d >> 20151006_log_pcal_detchar.out

I have attached the log. I had to change the file extension to be posted to the aLog.