TITLE: 05/27 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Corey
SHIFT SUMMARY:  locked most of the shift, issues listed below
LOG:

• handed off locked with violin damping
• Sheila called, scripts run to recover arm pointing likely removed a TRAMP time for TMSX, which is necessary for the stage INCREASE_POWER (was 0, now 30)
• Sheila restored the TRAMP time, I accepted it in SDF, H1 made it through INCREASE_POWER without issue, and then on to NLN
• (UPDATE: in DOWN, the SDF for the TRAMP was not saved, so came up as a diff, I accepted it, so it should not reappear)
• in NLN, H1 was very glitchy and SQZ lost lock a number of times, and the range ran low, between 80 Mpc and 90 Mpc for more than an hour
• Georgia called, and increased the FSS COMMON_GAIN from 23dB to 24dB, since the DC  light level was down around 1.9V on the TPD
• this brought the high frequency noise in DARM back to a normal level
• during this time, winds increased and gusted up to around 38 mph (current max is holding steady at around 35 mph)
• at shift change, H1 was locked but SQZ was unlocked
• handed H1 off to Corey, and then H1 lost lock
• after lockloss, I realigned IM2 and IM3, which had shifted alignment when the ISI tripped (IM4 did as well, but since it's driven and the change was well withing the range that IM4 is typically pointing, I did not set IM4 back to the old values, however, it might need to be checked again once Corey gets to locking the arm in IR)
• I checked tht IM4 trans QPD, ISS Second Loop QPD, and confirmed the IM alignment changes were seen on these QPDs
  • previous time when H1 was unlocked, to unlocked after the EQ, to now restored
    • IM4 TRANS pitch: was ~1.6, then ~3.6, now ~0.17 -> change due to EQ(IMs) = 0.2
    • IM4 TRANS yaw: was ~1.4, then ~1.5, now ~1.4
    • ISS2 QPD pitch: was ~0, then ~0.56, now ~0 -> change due to EQ(IMs) = 0.6
    • ISS2 QPD yaw: was ~-0.05, then ~0.0, now ~-0.07
• Corey's doing an initial alignment

IM Shift & Restoring Pre-EQ

After antoher SQZ unlocking followed by a close H1 Lockloss, took this opportunity to take the IMs to their pre-Peru-EQ values (Cheryl did this...most notable change was Pitch for IM2 & IM3)---this is mainly because the last lock was not great & we're hoping that fixing the IM shifts will help H1.

ALS PDH Errors

On a seperate note, after H1 lost lock, noticed that we do not have any light for ALS x & y (green).  On the ALS Overview both X & Y have "ERROR 4 PDH" errors. 

This is is what I'm going to look into next.  Once through ALS issue, will run a new INITIAL ALIGNMENT to the new IM pointing & see how H1 likes that.

TITLE: 05/26 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 104Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    Wind: 26mph Gusts, 18mph 5min avg
    Primary useism: 0.17 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY:

H1 was out of OBSERVING when I walked in.  Cheryl let me know this was due to the SQZ being unlocked; she was giving it time to INIT to a LOCKED state, and we saw it get back there.  We waited a few minutes to go back to OBSERVING in case it was going to drop back out again.

(while waiting I closed/reopened the medm for video2 because the OPS_OVERVIEW was froze giving impression we had still been in OBSERVING.)

23:09 H1 back to OBSERVING (it dropped out due to the SQZ at 22:47).

H1 has been locked for almost 7hrs post-Peru-EQ with Ed & Cheryl recovering here and Sheila/Georgia helping over the phone.  Cheryl is investigating the IMs to see if the shift they had from EQ is better/worse/no change.

Winds have picked up to just under 20mph over the last 2hrs.

• H1 into Observe at 17:27:50 UTC
• H1 out of Observe at 19:27:36 UTC, SQZ lost lock
  • SQZ relocked (no OPS assistance)
• H1 back to Observe at 19:31:45 UTC

I plotted the violin modes that have the highest RMS - some are slowly coming down, others, holding steady, none are ringing up at this time.

TITLE: 05/26 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 11mph Gusts, 9mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.14 μm/s
QUICK SUMMARY:

• late entry due to working on violins
• Sheila called and put a ramp time on moving TMSX, before I attempted INCREASE_POWER
• from ENGAGE_DC_VIOLINS, where Ed handed off to me, INCREASE_POWER was successful, and then NLN
• once violin is ringing up, so I'll damp that and go to Observe

TITLE: 05/26 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:
LOG:

9:35 Begin resetting Watchdogs -

• OFI WD is tripped. I can't find how to un-trip this. It isn't accessible from the Ops Overview screen.
• Found it! SITEMAP>SUS_AS.

9:57 BLRMS below 1um/s - AS spot is low and right

• Bringing SEI_CONFIG back to WINDY

10:07 Everything un-tripped. Everything re-aligned - AS Spot still low and right

• no flashing on ALSY camera
• reset BS and all Y optics back to witness sensor values prior to EQ
• Oplev spots look good

11:40 Just got off the phone with Sheila (she called in to check on the quads). I didn't push the big green RECOVER EQ button!!!!!! -_-

• Things look a LOT better now.

11:45 Begin Initial Alignment

12:10 Raine from LLO called to let me know that ALSY tripped and requires a trip to the end station - phone buddy system in effect

12:33 Raine reported back at the corner station.

12:52 begin re-locking H1

14:00 Lock failed at INCREASE POWER

14:23 Lock failed at INCREASE POWER (again)

• Going to wait at ENGAGE_DC_VIOLINS
• ETMY MODES 1 & 6 are rung up pretty good - gonna take a while

15:00 Handing off to Cheryl

07:51:52UTC Lockloss - StripTool showed no wavering or oscillations prior. Dropped from stable ~109Mpc to 0 instantly.

This is a huge quake. I no sooner saw the spot on USGS and started to examine the state of the ISIs when the lock fell off with out any Verbal Alarm warning of an incoming. The S&P waves rolled in faster than I could even react.  As I type this (08:00 UTC), the incoming EQ Verbal came in with 910 seconds to R3.5 wave arrival . BLRMS are already off scale. By this time, most of the ISIs had tripped upon P & S wave arrival and then the rest, with some of the smaller suspensions, tripped (r3.5 countdown not even completed yet). Also, prior to the second wave of trips I pressed the big red VERY LARGE EQ button. I entered "yes" in the confirmation window and wasn't sure that any changes had actually been effected as tripping continued. I understand that it takes time for the damping but when I pressed it again and entered "y" i got feedback from the script confirming damping and isolations effected. I temporarily changed the  BLRMS upper Y-axis limits (both graphs) so I could see the max velocities (default limits were: .03-.1Hz = 30um/s & .1-.3Hz = 3um/s). EX hit 50u; EY hit 40+u; CSZ hit 30u+. CDS Overview also showing IM,  TMSX, and associated IOP DAC KILLS. No aftershocks reported at this time. Curious ISC_LOCK items appearing on Verbal Alarms screen. I don't recall them being announced audibly. Guardian will remain in DOWN/READY and trips will remain safely tripped until sufficient "ringdown".  time out 8:56UTC.

TITLE: 05/26 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 110Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    Wind: 10mph Gusts, 7mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.16 μm/s
QUICK SUMMARY:

TITLE: 05/26 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 113Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY:

H1 currently has 3+hrs of observing/lock under its belt.  Be mindful of the IMC MCL threshold diffs I had (noted in earlier alog).

Microseism has been trending down and has returned to the 50th percentile.  Ed reported some heavy rain on parts of his drive in.
LOG:

• 21:00 - 23:20 Corey tour
• 23:30 Checked on TCSy Chiller (alogged)
• 0:05-0:19 Amber tour
• 1:04 51+hr lock ENDS!
• 1:04-3:50 Lockloss recovery

At 1:04utc (5:04pm), H1 had a lockloss after 51+hrs of lock.

1. 1:04-1:43:  Spent first 40min to try and relock (arms looked fine, PRM looked good), but lost lock after DRMI).  Since this took so long to get to that point, opted for an INITIAL ALIGNMENT.
2. 1:44-2:17:  Alignment took roughly 35min (with Xarm Green taking a lot of time to converge to eventually allow OFFLOADING).
3. 2:18 - 3:50utc:  Back to locking.  Spent about 90min of locking with a few failed attempts before/after DRMI.  For most recent attempt, hung out at OFFLOAD_DRMI_ASC for about 5min...and this was with some minor touch up with PRM & SRM mirrors...mainly waited until all the StripTool signals were flat and optimized.  Then just took H1 to NLN (from here took about 25min).
   • Had a couple of DIFFs for LSC/IMC/MCL trigger thresholds (attached).  Since these were just threshold values, I ACCEPTED them.
   • The diffs above occurred after the lockloss at 1:43utc

3:50utc:  Back To OBSERVING  (Have had a couple of large/long glitches in the first 15min so far.)

4:10:  Time to make lunch.

Trying to relock H1 after 2+day lock.  Ran an alignment, but have had a few failed attempts thus far.  Contemplating another alignment after a few more locking attempts now.  

Tried relocking immediately afterward, but DRMI took a while & after it did lock, broke lock at SHUTTER_ALS.  (POP18 only got up to about 55 with PRM/SRM touch ups at OFFLOAD_DRMI_ASC).

Ran an alignment.

Now back to locking.  DRMI took about 7min to lock.  (POP18 only got up to about 59 with PRM/SRM touch ups at OFFLOAD_DRMI_ASC).

SUMMARY so far:

1:04 H1 lockloss after 51hrs 44min!

• 1:04-1:44Just tried relocking.  DRMI took a long time & lockloss at SHUTTER_ALS.  Note:  POP18 only up to about 65.  :-/
• 1:44-2:17 ALIGNMENT
  • Xarm took a while to converge
• 2:18 Locking Again.  A few locklosses before & after DRMI so far.

TITLE: 05/25 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 111Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 8mph Gusts, 5mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.23 μm/s

Microseism has been taking slight dip down and now is touching the 50th percentile.  Higher winds from Cheryl's shift seem to be dying down
QUICK SUMMARY:

H1 has been running for almost of 51hrs (as of 0:15utc); with Observing currently at 25+hrs.

I had a a tour group here from roughly 2pm-4:15pm & Cheryl covered me as I escorted the group back to the LSB parking lot.  Amber is now in here with another group (there will also be a public lecture in the LSB at 6pm).

M. Wade, A. Viets

I have finished creating DCS calibration filters files for the C01 h(t) frame production.  The first epoch for C01 h(t) frames will use filters file

aligocalibration/trunk/Runs/O3/GDSFilters/H1DCS_C01_1239472998.npz

I have attached plots from sanity checks run using this filters file on data from GPS times 1239720596-1239723372.  The first attached plot is an ASD comparison of data calibrated with this filters file (expected C01 data), the corresponding C00 data, and the corresponding CAL-CS data.  The second plot is the ASD ratio of these three strain products.  The third plot is the response function as derived from the expected C01 data and the CAL-CS data compared to the pyDARM model response, and the fourth plot is a zoom-in on the ratio of this response function comparison.  All of these tests indicate that this filters file is ready for use on C01 data, giving the expected level of agreement in each comparison.

M. Wade, A. Viets

I have finished creating DCS calibration filters files for the C01 h(t) frame production.  The first epoch for C01 h(t) frames will use filters file

aligocalibration/trunk/Runs/O3/GDSFilters/H1DCS_C01_1237831461.npz

I have attached plots from sanity checks run using this filters file on data from GPS times 1239036564-1239039340.  The first attached plot is an ASD comparison of data calibrated with this filters file (expected C01 data), the corresponding C00 data, and the corresponding CAL-CS data.  The second plot is the ASD ratio of these three strain products.  The third plot is the response function as derived from the expected C01 data and the CAL-CS data compared to the pyDARM model response, and the fourth plot is a zoom-in on the ratio of this response function comparison.  All of these tests indicate that this filters file is ready for use on C01 data, giving the expected level of agreement in each comparison.