• H1 is locked at NLN for 4hr16min and Observing for ≈1.5hrs. We are currently coincidental with Livingston. 
• GWIstat issue is being addressed by clibration team as per correspondence with Keita and Jeff K

00:33 Runnnig a2l. DTT ploit shows high incoherence in YAW. Python problems? Not running from the MEDM screen

00:52 Jeff K running calibration measurements

02:44 Checking a2l, post calibration. PIT is showing a pretty good deal of mis-alignment. Going to run the script one more time before setting the intention bit.

03:02 H1 in Observing

He was informing me that they were going to go to Observing. I told him we had been there for a few hours already but he brought to my attention the fact that GWI stat is reporting us as NOT ok. Anyone?

J. Kissel

I've taken the calibration measurement suite that shall be representative of post-winter break. Analysis to come, data files listed below. 

Sensing Function Measurements:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/SensingFunctionTFs/
   Swept Sine:
       2017-01-03_H1DARM_OLGTF_4to1200Hz_25min.xml
       2017-01-03_H1_PCAL2DARMTF_4to1200Hz_8min.xml
   Broadband:
       2017-01-03_H1_PCAL2DARMTF_BB_5to1000Hz.xml

Actuation Function Measurements:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/FullIFOActuatorTFs/2017-01-03/
   UIM:
       2017-01-03_H1SUSETMY_L1_iEXC2DARM_25min.xml
       2017-01-03_H1SUSETMY_L1_PCAL2DARM_8min.xml
   PUM:
       2017-01-03_H1SUSETMY_L2_iEXC2DARM_17min.xml
       2017-01-03_H1SUSETMY_L2_PCAL2DARM_8min.xml
   TST: 
       2017-01-03_H1SUSETMY_L3_iEXC2DARM_8min.xml
       2017-01-03_H1SUSETMY_L3_PCAL2DARM_8min.xml

Note that this includes the new/better L2/L3 crossover design re-installed earlier today (see LHO aLOG 32933), both in ETMY itself and in the CAL-CS replica that forms DELTAL_EXTERNAL_DQ. The mean data points for ratio of PCAL to DELTL_EXTERNAL (which should be unity if we've calibrated the data correctly), show a ~10%, frequency-dependent deviation, worst at ~200 Hz. We'll have to wait until time-dependent parameters are corrected for before deciding if anything is really "wrong" or incorrect.

We know that we will have to adjust the actuation strength and sensing gain by a scalar ~1% because of mistakenly over counting the gain of the analog anti-imaging and anti-aliasing filters (see LHO aLOG 32907), but this won't be the majority of the discrepancy.

Two alarms so far 5 minutes apart. Trends don't really show anything obvious.

Thu 22nd Dec - Sat 24th Dec No restarts reported

Sun 25 Dec Many unexpeced restarts of h1tw0 (05:35 - 13:10). System turned off to prevent further restarts.

Mon 26th Dec - Fri 30th Dec No restarts reported

Sat 31st Dec

2016_12_31 15:57 h1iopsusauxh34
2016_12_31 15:57 h1susauxh34
 

h1susauxh34 computer died, was power cycled.

Sun 1st Jan - Mon 2nd Jan No restarts reported

J. Kissel

I've grabbed traditional "charge" (effective bias voltage due to charge) measurements from H1 SUS ETMX and ETMY this afternoon while under an earthquake. Measurments show that the effective bias voltage is still holding around / under +/-10 [V] in all quadrants. Nice!

Still on the to-do list: compare this against longitudinal actuation strength measurements via calibration lines, a. la. LHO aLOG 24547. Perhaps our new years resolution can be to start this regular comparison up again.

awgtpman issues

Jenne, Dave, Jim:

we experienced some TP issues this morning. Command line "diag -l" was slow to start and did not support testpoints. First we restarted the models on h1susauxh34 since this showed errors over the break and had CRC errors, this did not fix the TPs. Next we restarted the awgtpman process on h1asc and this did fix the problems. Remember that h1asc has a special awgtpman process to permit more testponts to be opened. The reason for today's problem is unknown.

Guardian reboot

Dave, Jim:

To ensure the python leap-second updates were installed on all nodes, we rebooted h1guardian0 (it had been running for 33 days). All nodes came back with no problems. We recovered about 4GB of memory.

python gpstime leapseconds

Jim

gpstime package updated, see alog 32919 for details.

Jeff K, Jonathan, Jim, Dave:

For due diligence we performed some sanity tests on the DAQ to confirm the leap-seconds did not cause any problems.

Event at Known Time:

Jeff K dropped a ball onto the control room floor at a recorded time. We looked at a seismometer signal (e.g. H1:ISI-GND_STS_HAM2_X_DQ) using both NDS1 (dataviewer and command-line) and NDS2. The signal showed up in the latter part of the recorded second as expected.

Decode IRIG-B analog signal:

The digitized IRIG-B signal H1:CAL-PCALX_IRIGB_OUT_DQ was read by hand for an arbitary GPS time. The time chosen is GPS = 1167523720 which corresponds to a UTC time of Jan 04 2017 00:08:22.

The decoded IRIGB time is 00:08:40 which is UTC + 18. Tthere have indeed been 18 leap seconds applied to UTC since the GPS epoch of Jan 1980, this is correct.

For anyone interested in decoding irig-b by hand, the attached image shows the seconds, minutes, hours part of the analog signal along with the decoding table.

TITLE: 01/03 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC

• Apollo working on HVAC Controls (with Bubba)
• 16:19 Charging LVEA forklift batteries (Joe D)
• 16:25 Addressing ISIs & getting back to NOMINAL (JeffK)
• 16:38 Opening PSL Shutter (Corey)
• 17:24 Checking on PSL & TCS
• 17:30 Norco truck heading to CP6 (MX's -4379)
• 17:39 2nd Norco truck also heading to MX (CP5, -4377)
• 18:10 Fixing Leap Second issue which affects python operations (Jim)
• 18:15 Picking Up STS at EY (Jim)
• 18:33 MY cable inventory 
• 18:59 Paradise water
• 19:15-20:56 Alignment
• 19:18 Gerardo removing snow of solar panels down both arms (Actually he found out John/Kyle took care of it)
• 20:13 TCSy Chiller Flow Is Low Verbal Alarm (Jason notified)
• 22:05  7.2 EQ in Fiji hits us---->Observatory Mode:  EARTHQUAKE
  • Charge Measurement (Kissel) 
  • PUM work (Kissel)
• 22:45 LVEA Swept (Jim)
• 23:50 EY Temp High alarm 
• Toward end of shift, went for relocking & handing Ed a locked DRMI

Restoring From Holiday Log Notes:

• LVEA Temperature checked & OK (Kissel)
• PSL Shutter opened (Corey)
• ISIs restored individually (Kissel)
• BRSx has damping OFF (Kissel)
• SEI_CONFIG taken to WINDY (Kissel)
• TCS Ring Heater powers have no change over last 20days (Corey)
• PSL Chillers OK (Corey & Jason)
• PSL being checked (Jason)
• Initial Alignment Notes
  • 19:15- 20:56 alignment
  • TMSx moves were needed to lock up ALSx
  • Beatnote was at -30!  But Keita asked if we opened the ALS Pipe (I had only opened the PSL pipe!  Went out to open the ALS pipe.)
  • BS was way off for the Michelson, but took to DOWN & tweaked BS in positive pitch until it looked good.  Then took to MICH_DARK_LOCKED & proceeded normally.
• Dark Offset script run (Jenne)
• PSL Rotation Stage calibrated via script (Jenne)
• Had ALS troubles due to some settings (ESD ETMx) which remained from Jeff's charge measurement attempt earlier.

John, Kyle, Alfredo, Gerardo 

X2-8 battery charge a little low but still had lots of life left.

J. Kissel

Before the holiday break, I'd discovered that we had somehow lost the settings improved the design of the L2/L3 (or PUM/TST) crossover -- see LHO aLOG 32540 for the bad news discovery, and LHO aLOG 28746 for the original design.

I've now fixed the problem, and we have the new improved crossover again.

This required several steps:
(1) Turned on / switched over to the appropriate filters in the L2 and L3 DRIVEALIGN_L2L filter banks:
                  Good               Bad
     L2 L2L    (FM6, FM7)       (FM2, FM7 ,FM8)
     L3 L2L    (FM4, FM5)       (FM3, FM4)

(2) Turned on / swtiched over to the appropriate filters in the corresponding replicas of those filter banks in the CAL-CS model, such that the calibration will be unaffected.

(3) Changed the LOWNOISE_ESD_ETMY state of the ISC_LOCK guardian, such that it now forces the new configuration instead of the old. Committed to the userapps repository.

(4) Accepted the changes in the H1SUSETMY and H1CALCS SDF systems.

Hopefully we won't lose these settings again!

While waiting for the ground to stop shaking, I ran throught Betsy's annotated LVEA sweep. I didn't find anything out of place, I did run through the science mode process for the PSL (unclear if that was necessary, I got the impression from the checksheet on the PSL that it was). Everything else seemed okay.  I don't believe the ends have been done, but access is dicey today.

This morning, Jason, Mark and I swapped the assumed-to-be failing TCSY flow sensor which has been showing epochs of glitching and low readout (while other indicators show normal flow, alogs 32712 and 32230).  The process to do this was such:

1) Key laser off at control box in rack, LVEA

2) Turn RF off at mezzanine rack, Mech room

3) Turn chiller off on mezzanine, Mech room

4) Turn power off on back of controller box in rack, LVEA (we also pulled the power cable to the sensor off the front of the controller, but it was probably overkill)

5) Close in-line valves under BSC chamber near yellow sensor to-be-swapped, LVEA

6) Quick-disconnect water tubes at manifold near table, LVEA

7) Pulled yelow top off of yellow sensor housing under BSC at the piping, LVEA

8) Pulled the blue and black wires to the Power recepticles inside the housing (see pic attached).  Pulled full grey cable out of housing.

9) While carefully supporting blue piping*, unscrewed large white nut holding housing/sensor to piping (was tough, in fact so tough that we later removed all of the teflon tape which was unneeded in his join)

10) Pull* straight up on the housing (hard) and it comes out of the piping.

11) Reverse all above steps to insert new housing/sensor, wires and turn everything back on.  Watch for rolled o-rings on the housing and proper alignment of the noth feature when installing the new sensor.  Verify mechanical flow sensors in piping line show ~3-4 G/m readout when flow/chiller is restored to functionality.

12) Setup new flow sensor head with Settings:  Go to the other in-use sensor, pull off the top and scroll through the menu items (red and white buttons on the unit (shown in pic).  Set the new head to these values.

13) Verify the new settings on the head are showing a ~3 G/m readout on the medm screen.  If not, possibly there is setting on the sensor that needs revisited.

14) Monitor TCS to see that laser comes back up and stabilizes.

* Blue piping can crack so be careful to always support it and avoid torque torque

Note - with the sensor removed, we could see alot of green merk in the blue piping where the paddle wheel sits.  Still suffering green sludge in this system...