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

Activity Log:Time - UTC (PT)

3pm local

Patrick, Kyle, Dave, Chandra

Successfully filled CP3 and CP4 using automation code and executing code via cron job. We lifted leads of both TCs on CP3 to mimic faults to verfiy code aborts. We tried to increase exhaust pressure to >2 psig threshhold by closing bypass exhaust valve but due to cold exhaust pipes it never rose above 1 psig. We even cracked the bypass LLCV half turn on CP4 along with doubling LLCV % open. We'll revisit that error test.

CP3 took about 30 seconds to overfill at 50% open.

CP4 took several minutes to overfill at 70% open and 1/2 turn open on bypass LLCV. Raised nominal from 35% to 36%.

Next week we'll test alert messaging.

Reposting the log from LLO comparing the two sites' PSL vibration coupling. 

https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=30465

   IFO has been locked in Observing for the past 3.5 hours. Suppressed PI Mode-28 and dropped out of Observing from 19:06 to 19:18 to run the A2L script while LLO was out of lock.
   Conditions are OK. The wind is up to a Moderate to Fresh Breeze (13 - 24 mph), It is cold (windchill around 9F)and clear. Microseism up at the end stations but still below 0.9, CS is fine.
        

For fun I've written a script to calculate the site windchill now the wind has kicked up. It uses the NOAA formula. The script is called windchill

david.barker@zotws2: windchill
EX temp 20.1(degF) wind 09.0(mph) windchill 09.6(degF)
MX temp 19.4(degF) wind 09.0(mph) windchill 08.8(degF)
CS temp 21.2(degF) wind 08.0(mph) windchill 11.7(degF)
MY temp 19.3(degF) wind 08.0(mph) windchill 09.4(degF)
EY temp 17.8(degF) wind 08.0(mph) windchill 07.6(degF)
 
wind chill average over site 9.4 degF
 
 

   At 19:06 (11:06) took advantage of LLO being down to dropped out of Observing to run the A2L script. Back in Observing at 19:18. 

   After relocking this morning had an SDF diff for IMC-REFL_SERVO_IN1GAIN. 

TITLE: 12/16 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 75.8911Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:  Smooth sailing for the first 6 hours of shift.  Then a mysterious lockloss, followed by a quick IA, and back to Observing.
LOG:

See previous aLogs for the play-by-play.

15:59 Lockloss.  Cause unknown.  I'll let Jeff investigate and relock.
 

After a quick and painless IA, we are back to Observing.  I had to accept a few more SDF diffs for ECAT systems. Seems oddly similar to Corey's mysterious lockloss followed by ECAT diffs in aLog 32591.  Seen screenshots of accepted SDF diffs.

Cause is yet unknown.  Nothing seemed to ring up on any of the normal FOMs.  Just got a sudden Verbal Alarms notification that the HAM6 ISI WD had tripped.

Locked for ~22.5 hours.  No issues.

TITLE: 12/16 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 69.5545Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
    Wind: 10mph Gusts, 8mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.27 μm/s
QUICK SUMMARY:  Locked in Observing for 19+ hours.  No issues as of yet.
 

TITLE: 12/16 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 73.1215Mpc
INCOMING OPERATOR: Travis
SHIFT SUMMARY: No changes to note since mid shift summary. 
LOG:
01:10 UTC Brief notification that HWSX code stopped running.
01:40 UTC Out of observing to run a2l.
01:48 UTC a2l done. No errors reported. Back to observing.
02:04 UTC EY started constantly saturating.
02:44 UTC Out of observing. Changed gain for H1:SUS-ETMY_L2_DAMP_MODE10 from 100 to 0.02. Turned off FM1 and turned on FM9 and FM10 (Settings at Dec 15 2016 08:46:51 UTC from conlog test machine). 4.7kHz mode has come down and saturations have stopped.
02:59 UTC Accepted SDF differences. Back to observing.
03:17 - 03:27 UTC Stepped out of control room.
03:48 UTC Changed phase to damp PI mode 26.

Out of observing twice. Once to run a2l and once to damp 4.7kHz violin mode. PI mode 26 started increasing again. This time changing the phase damped it.

Josh, Andy, David

After stumbling on the ringing phones in the LVEA in O2 (entry 32503) we sent this request, to find other times in h(t) that look like phone ringing glitches, to GravitySpy citizen scientists. Though it's dirty laundry airing this is a way to engage a network of many interested folks to find issues.  

The reply from user @EcceruElme pointed to two similar glitches in O1/ER10/O2.
One is in Livingston at 1132398529.14 (Nov 24th 11:08 UTC - link) and looks like an ER10 instance of engaging violin mode damping while in observation ready but before SDF checks were being enforced, so ok.
One is in Hanford at 1128269436.32 which is 2015-10-07 at 16:00 during a long nice science mode lock (summary page for that day). This sounds a little like a fax machine then some bangs and a human voice through a loudspeaker and some more bangs. In the hour around that time there are also some other loud bangs. We have no idea what it could be but it happened in otherwise unbroken excellent O1 data so perhaps folks on site know what it is and if it can be (or has been) turned off.

Attachments:

- Audio file of Input Optics Microphone with no filtering.
- Spectrogram of Input Optics Mic (it was also loud in BS Mic, others in LVEA but quiet in PSL room Mics) and Strain
- OmegaScan of Strain (from GravitySpy) 

Chandra lifted the lead for TE252A. Kyle put the CP4 LLCV into PID and disabled. The script to fill CP4 was run:
vacuum@vacuum1:/ligo/home/patrick.thomas/svn/scripts$ python cp4_fill.py 70 -60 3600
Starting CP4 fill. TC A error. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill completed in 30 seconds. LLCV set back to 35.0% open.
Chandra put back the lead for TE252A.

Chandra lifted the lead for TE202B. Kyle put the CP3 LLCV into PID and disabled. The script to fill CP3 was run:
vacuum@vacuum1:/ligo/home/patrick.thomas/svn/scripts$ python cp3_fill.py 50 -30 3600
Starting CP3 fill. TC B error. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 110 seconds. LLCV set back to 19.0% open.
Chandra put back the lead for TE202B.

Both scripts are in svn under /trunk/scripts in the projects repository. Revision 4023.

Looking at a few tasks on the calibration to-do list, I ended up down the rabbit hole. Sadly, it's getting late and will have to return to this tomorrow.

Investigations:

1) Working on fixing the PCAL --> CAL-CS_DELTAL_EXTERNAL calibration (see LHO alog 31994). Kiwamu's original script computed a transfer function accounting for time delays caused by the DAQ and the CAL-CS whitening filter. However, this is already taken into account in the clock cycles delay in the CAL-CS model when adding the sensing and actuation paths. Since CAL-CS corrects for the phase delay caused by AA/AI filtering--analog and digital--using the delayed actuation path, then what one really wants is to correct CAL-CS for the magnitude changes of the AA/AI filtering and any CAL-CS whitening on this channel while also correcting the PCAL_RX_PD channel for the effect of AA and that we also have not applied a filter with two poles at 1 Hz (for the free-mass response):

DELTAL_EXT   W * [Derr/C_foton + A*Dctrl*delay]
---------- = ----------------------------------
PCAL_RX_PD         m * f^2 * AA_a * AA_d

 m     DELTAL_EXT [C_real/C_foton] / [W * abs(AA_a * AA_d * uncompensatedOMCpoles)]
--- = ------------------------------------------------------------------------------
 m                PCAL_RX_PD / [f^2 * AA_a * AA_d]

Note that the correction factors applied in the numerator of the final equation are really only to be applied to the sensing side. However, the corrections are only at high frequency (low-frequency corrections are simply unity), so the numerator term is dominated by the sensing function.

Thus the calibration to be applied is thus:

   [C_real/C_foton] * [f^2 * AA_a * AA_d]
----------------------------------------------
[W * abs(AA_a * AA_d * uncompensatedOMCpoles)]

Unfortunately, this results in a large deviation in phase at higher frequencies (~60 degrees at 1 kHz, see attached figure) while recent measurements using an incorrect calibration filter do not suffer from this large phase deviation. The phase deviation is due to application of the analog and digital AA on the Pcal. Why?

2) I constructed an O2 version of the front-end calibration time delay diagrams based on the model (see attached), but when I look at the GDS correction factors to be applied to the CAL-CS channels, I do not find matching delays. In addition, the values obtained to not mesh with the recent work done at LLO (see LLO alog 29899). This will have to be investigated further tomorrow also.