Due to issues with running the report script locally (being worked on), Sudarshan will post the results of this past Tuesday's End Y Pcal calibration.  Attached are pics of the logsheet so he has the pertinent information.

TITLE: 08/16 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 51Mpc
INCOMING OPERATOR: JeffB
SHIFT SUMMARY:  Quiet shift, with a few hours of calibration measurements in the middle. JeffK was operator for the first hour, then I took over for the rest of the shift.
LOG:

(JeffK) Aug 16 2017 15:15:44 UTC New remote user, ROOT
(JeffK) Aug 16 2017 15:18:13 UTC New remote user, ROOT
(JeffK) Aug 16 2017 15:51:12 UTC GRB Alert
Aug 16 2017 16:00:00 UTC Take over from JeffK
Aug 16 2017 16:10:06 UTC Parking lot crew through gate
Aug 16 2017 17:12:53 UTC Karen opening receiving roll-up door to remove cardboard
Aug 16 2017 17:31:09 UTC Out of Observe for JeffK calibration measurements
Aug 16 2017 18:12:26 UTC JohnW working on chiller fault at EndYAug 16 2017 19:09:33 UTC Bubba and JohnW to EndY chiller yard
Aug 16 2017 19:28:50 UTC Bubba and JohnW to EndY air handler mechanical room
Aug 16 2017 19:46:25 UTC Bubba and JohnW leaving EndY
Aug 16 2017 20:20:04 UTC TJ to optics lab to check on parts
Aug 16 2017 20:45:22 UTC TJ out of optics lab
Aug 16 2017 21:00:45 UTC JohnW to MidY
Aug 16 2017 21:11:28 UTC Measurements finished
Aug 16 2017 21:11:59 UTC Back to Observing
Aug 16 2017 21:19:52 UTC JohnW back
Aug 16 2017 22:50:08 UTC Hand over early to JeffB

J. Kissel

Managed to get all other QUADs worth of UIM characterization -- to confirm what's seen on ETMY (see LHO aLOG 31603) is either normal, or abnormal. Will process and post detailed results in due time. Preliminary results indicate that all QUADs show the 167 Hz feature, but only some QUADs show the ~110 Hz feature or 300 Hz forest. Interesting! We'll see how he UIM blade dampers impact this stuff.

Data lives here:
2017-08-16_H1SUSETMX_L1_iEXC2DARM_HFDynamicsTest_100-250Hz.xml
2017-08-16_H1SUSETMX_L1_iEXC2DARM_HFDynamicsTest_250-350Hz.xml
2017-08-16_H1SUSETMX_L1_iEXC2DARM_HFDynamicsTest_300-500Hz.xml
2017-08-16_H1SUSETMX_L1_iEXC2DARM_HFDynamicsTest_90-400Hz_SweptSine.xml
2017-08-16_H1SUSETMX_L1_PCAL2DARM_HFDynamicsTest_100-250Hz.xml
2017-08-16_H1SUSETMX_L1_PCAL2DARM_HFDynamicsTest_250-350Hz.xml
2017-08-16_H1SUSETMX_L1_PCAL2DARM_HFDynamicsTest_300-500Hz.xml
2017-08-16_H1SUSETMX_L1_PCAL2DARM_HFDynamicsTest_90-400Hz_SweptSine.xml

2017-08-16_H1SUSITMX_L1_iEXC2DARM_HFDynamicsTest_100-250Hz.xml
2017-08-16_H1SUSITMX_L1_iEXC2DARM_HFDynamicsTest_250-350Hz.xml
2017-08-16_H1SUSITMX_L1_iEXC2DARM_HFDynamicsTest_300-500Hz.xml
2017-08-16_H1SUSITMX_L1_iEXC2DARM_HFDynamicsTest_90-400Hz_SweptSine.xml
2017-08-16_H1SUSITMX_L1_PCAL2DARM_HFDynamicsTest_100-250Hz.xml
2017-08-16_H1SUSITMX_L1_PCAL2DARM_HFDynamicsTest_250-350Hz.xml
2017-08-16_H1SUSITMX_L1_PCAL2DARM_HFDynamicsTest_300-500Hz.xml
2017-08-16_H1SUSITMX_L1_PCAL2DARM_HFDynamicsTest_90-400Hz_SweptSine.xml

2017-08-16_H1SUSITMY_L1_iEXC2DARM_HFDynamicsTest_100-250Hz.xml
2017-08-16_H1SUSITMY_L1_iEXC2DARM_HFDynamicsTest_250-350Hz.xml
2017-08-16_H1SUSITMY_L1_iEXC2DARM_HFDynamicsTest_300-500Hz.xml
2017-08-16_H1SUSITMY_L1_iEXC2DARM_HFDynamicsTest_90-400Hz_SweptSine.xml
2017-08-16_H1SUSITMY_L1_PCAL2DARM_HFDynamicsTest_100-250Hz.xml
2017-08-16_H1SUSITMY_L1_PCAL2DARM_HFDynamicsTest_250-350Hz.xml
2017-08-16_H1SUSITMY_L1_PCAL2DARM_HFDynamicsTest_300-500Hz.xml
2017-08-16_H1SUSITMY_L1_PCAL2DARM_HFDynamicsTest_90-400Hz_SweptSine.xml

J. Kissel

Was able to grab an entire suite of calibration measurements this afternoon. Data files listed below, will process in due time. Preliminary results are as expected -- attached is a screen shot of "perfect" reference calibration against current CAL-DELTAL_EXTERNAL, which we know is *not* corrected for time dependent correction factors -- namely kappa_TST which is up at ~10% at the moment, likely causing the shown discrepancy.

Actuation:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/FullIFOActuatorTFs/2017-08-16
2017-08-16_H1SUSETMY_L1_iEXC2DARM_25min.xml
2017-08-16_H1SUSETMY_L1_PCAL2DARM_8min.xml
2017-08-16_H1SUSETMY_L2_iEXC2DARM_17min.xml
2017-08-16_H1SUSETMY_L2_PCAL2DARM_8min.xml
2017-08-16_H1SUSETMY_L3_iEXC2DARM_8min.xml
2017-08-16_H1SUSETMY_L3_PCAL2DARM_8min.xml

Sensing:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/SensingFunctionTFs
2017-08-16_H1DARM_OLGTF_4to1200Hz_25min.xml
2017-08-16_H1_OMCDCPDSUM_to_DARMIN1.xml
2017-08-16_H1_PCAL2DARMTF_4to1200Hz_8min.xml
2017-08-16_H1_PCAL2DARMTF_BB_5to1000Hz_0p25BW_250avgs_5min.xml

CHWP1 tripped off this morning for some reason so I have started CHWP2. This has allowed the second chiller to start. Chilled water temps rose to 52F and are now back to 37F.

There may be a small blip in the VEA space temperature, although it appears it may only move by 1 or 2 tenths of a degree F.

Over the weekend, I the seismon code had died. I don't know why it died over the weekend, but it looks like I may have restarted some wrong versions of epics code. Corey had found it dead again after my last shift, probably a result of the epics code crashing in a way that's not totally obvious on the medm display. I restarted the right versions of the code this morning, but it's hard tell if it's actually, really running, so it needs monitoring. If the code is found not running again, I'd like to know, so I can try to diagnose the code. Some symptoms are the gps clock on the medm is dead (this will turn on a red  light on my new medm & there is a diag_main test) or not catching new earthquakes. Also, the new version of the code seems to have more or less killed the old display, so there is no need to report on the old, single event seismon not updating.

Added 100 mL H2O to Xtal chiller.  Diode chiller level is OK.  Filters appear clean.  FAMIS 6536.

model restarts logged for Tue 15/Aug/2017
2017_08_15 10:57 h1nds0
2017_08_15 14:35 h1sysecaty1plc1sdf
2017_08_15 14:35 h1sysecaty1plc2sdf
2017_08_15 14:35 h1sysecaty1plc3sdf

Tuesday maintenance restart of h1nds0 to speed up guardian. Unexpected crash of Beckhoff EY SDF models (caused by h1ecaty1 crash).

model restarts logged for Mon 14/Aug/2017 - Sun 13/Aug/2017 No restarts reported

model restarts logged for Sat 12/Aug/2017
2017_08_12 18:32 h1iopsusauxex
2017_08_12 18:32 h1susauxex
2017_08_12 18:34 h1alsex
2017_08_12 18:34 h1calex
2017_08_12 18:34 h1iopiscex
2017_08_12 18:34 h1iscex
2017_08_12 18:34 h1pemex
2017_08_12 18:36 h1hpietmx
2017_08_12 18:36 h1iopseiex
2017_08_12 18:36 h1isietmx
2017_08_12 18:38 h1iopsusex
2017_08_12 18:38 h1susetmx
2017_08_12 18:38 h1susetmxpi
2017_08_12 18:38 h1sustmsx

Timing system at EX was powered down, requiring all models to be restarted.

model restarts logged for Fri 11/Aug/2017 No restarts reported

Attached are the plot lines for the VPW desiccant cabinets.  Nothing out of the ordinary shown.

TITLE: 08/16 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 54Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    Wind: 6mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.10 μm/s 
QUICK SUMMARY:

Smooth transition, running in nominal low noise, and in observation. Lock Clock says we've been running for 16:11 hh:mm. Waiting for gravitational waves!

TITLE: 08/16 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1:  Observing at 54Mpc
INCOMING OPERATOR: Mix of LHO Staff coverage for today's DAY shift starting with Jeff K.
SHIFT SUMMARY:

Nice & quiet shift with H1 locked for 16hrs (going on 9.5hrs of Triple C.).
LOG:

• 12:36-13:36 GRB Stand Down (Fermi satellite & consulted LLO operator).  (Now does Virgo receive these notifications?)

Smooth sailing currently with a 5+hrs of Triple C.

TITLE: 08/16 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 54Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 8mph Gusts, 6mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.07 μm/s 
Quiet seismically and wind-wise.
QUICK SUMMARY:

H1 locked for over 8hrs at 54Mpc.Went through Check Sheet.  Did my OSB walkthrough.

   IFO locked and Observing along with LLO and Virgo. There was a moderate EQ (Mag 4.8) in the Mid-Atlantic which registered sharply on the 0.03 - 0.1Hz seismic plot about an hour ago. It did not disturb the IFO. Environmental conditions are good. All is normal at this time.  

We have had issues with RxPD clipping at Y-End Pcal since earlier this year. In light of this clipping we switched to using TxPD instead of RxPD since June 19, 2017.  This clipping introduced a systematic error in the calibrated data before June 19. The mathematical recipe that describes this systematic error is in LHO alog #34153. The comment on the same alog also contains the correction factor that needs to be applied to account for clipping until Jan 22.

The files below contains the correction factor from Jan 22, 2017 02:19:02 UTC to Jun 19, 2017 17:35:22 UTC.  

Correction factor at three calibration line frequencies for all time with 10s interval (the data is obtained from 10s FFT).

 ${CalSVN}/aligocalibration/trunk/Runs/O2/H1/Results/PCAL/O2_RxPD_TxPD_factor_Jan22_Jun20.txt

Correction factor at three calibration line frequencies for science-quality data with 2 minute running average

${CalSVN}/aligocalibration/trunk/Runs/O2/H1/Results/PCAL/O2_RxPD_TxPD_factor_Jan22_Jun20_scienceintent_2minrunningavg.txt (Data)

${CalSVN}/aligocalibration/trunk/Runs/O2/H1/Results/PCAL/O2_RxPD_TxPD_factor_Jan22_Jun20_scienceintent_2minrunningavg.png (Plot)

The script used to produce these correction factors is here:

${CalSVN}/aligocalibration/trunk/Runs/O2/H1/Scripts/PCAL/TxPDRxPD_factor_Jan22_Jun20_2017.m

Thomas, TJ, Peter King, Aidan (remotely)

The goal of this measurement is to get the end HWS to sample the ETMs while locked on IR at low power (2 Watts) as a reference and then transition to higher power (29 Watts).

Preparation:

- This morning Peter and I went down to the end stations to install the Hartmann plate on EX and double check that EY's plate was still on.  Both are currently installed.

- The virtual disk that houses the HWS data frames was full so I ran a script that deletes old data, we are currently at 87% full.

-  I automated the misalignment procedure with this script: /ligo/home/thomas.vo/LIGO/AOS/TCS/20170815_ETM_Abs_Meas/Setup_HWS_Ends_Test.py. In order to image just the ETM, we need to input a bias offset to ALS-PZT2 YAW in order to offset the reflection off the ITM, the offsets were determined in aLOG-35979.  For the X-ARM, the bias offsets were correct, but for the Y-ARM the offsets would kick the ETMY reflection off the HWS so we decided to do this move by hand however it was difficult to precisely discern how far off the ITM spot was.

We locked both arms in green and took the lock guardian all the way up to DC_Readout, then I manually opened the shutter on the green beams and ran a misalignment script (see below) and started the HWS code.  However, the code on ETMX crashed in the middle of the test and didn't throw up any warnings but we were able to get ETMY measurements. The data is in /data/H1/ETMY_HWS/1186800000.

- Start time (@ 2 Watts):  15:35:00 PST

- End time (@ 29 Watts): 15:55:00 PST

- Shuttered: 16:10:00 PST