TITLE: 04/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: after EQs rang down, locked H1, didn't need an initial alignment, had to accept a couple things on violin damping

Overall Summary | DQ Shift Page

• 92.5% duty cycle for the 4 days.
• 50 Hz glitch line remains (since April 8th 2017).
• Starting on the 19th, we began to see clumps of glitches around 20 - 50 Hz (mostly ~30 Hz) . These glitches seem to be most frequent when ETMY optic pitch motion (most prominently 10 - 30 Hz) is at its highest. This can be seen on the SUS | OPLEV BLRMS page within the summary pages. I did not see any other noise correlations.
• Related to the above point, Hveto's most significant channel was consistently H1:SUS-ETMY_L3_OPLEV_PIT_OUT_DQ as it vetoed many of the 20 - 50 Hz glitches mentioned above. The corresonding YAW channel was number 2 in significance.
• We rode through a fair amount of EQs without too much issue.

TITLE: 04/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    Wind: 12mph Gusts, 8mph 5min avg
    Primary useism: 0.30 μm/s
    Secondary useism: 0.19 μm/s
QUICK SUMMARY: EQ shaking coming down, some aftershocks

Sheila, Nutsinee

WP6597

We commented out a line in the guardian that turn the damping gain on for this mode (H1:SUS-ETMY_L2_DAMP_MODE10_GAIN) to see if the line become more or less of a problem when it's not actively damped. We also unmonitored the gain channel.

Ops: If the line rings up during your shift, add the gain of 0.02 back and attempt to damp the line as usual. Adding the gain back won't kick you out of Observe but changing the phase will.

TITLE: 04/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: All when well until the earthquake. I'd guess that it should be an hour or two before we can get locked again.
LOG:

• 19:34 Hanford monthly phone test and siren activation
• 22:03 Lockloss from 7.1M earthquake in Chile

7.1 Valparaiso, Chile

Was it reported by Terramon, USGS, SEISMON? Yes, Yes, Yes

Magnitude (according to Terramon, USGS, SEISMON): 7.1 for all

Location: 38km W of Valparaiso

Starting time of event (ie. when BLRMS started to increase on DMT on the wall): ~21:55 UTC

Lock status? L1 & H1 lost lock

EQ reported by Terramon BEFORE it actually arrived? Yes

Note: SEISMON reported it before Terramon and USGS, heard the Verbal alert and gave us a good 20min to watch the waves come in.

SEISMON gave us a good 45min warning and we could watch the incoming waves as they came. Kind of cool, except for the fact that it killed the lock. I switched into the SEI configuration of LARGE_EQ_NOBRSXY immediately after the lockloss.

model restarts logged for Wed 19/Apr/2017 - Sun 23/Apr/2017 No restarts reported

Our range has been dropping a bit for the last 2.5 hours or so, we are now around 57Mpc. It looks to correlate with the 3-10hz seismic blrms that are also elevated higher than a usual weekday, but I am not sure that this is the cause.

Locked for 13hrs

Starting CP3 fill. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 490 seconds. TC B did not register fill. LLCV set back to 22.0% open.
Starting CP4 fill. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill completed in 2185 seconds. TC B did not register fill. LLCV set back to 40.0% open.

Looking at the HofT frame files around the time of the problem late last night Hanford time:

Each HofT directory (named by the 6 most significant digits in the GPS time) should have 2500 frame files in them, 117705 has 2498 files (missing two).

The two frame files which are missing are:

Note that the first missing channel is the first one in the directory, maybe a directory rotation error?

I'm not sure if the bad data started at 117705000 or 1177050356 or another time.

Went over work for tomorrow.

New items:

Vac - Pressure test at mid stations, maybe tomorrow.  Will inform operator, who will note it in the log.

    Kyle mounting on CP1 aux ion pump.

CDS - Patrick will me migrating some new systems

    New NDS2 client software, not going to the Guardian.

   HAM3 cabling work.

Fac - Engine hoist into beir garten, craning to beir garten as well. This will require a soft close of GVs.

HWS - Nutsinee work needs green light and ITMs misaligned.

CAL - Work to be done to fix the h(t) loss of online data.

ITMY OpLev laser swap. ETMY OpLev is also glitching.

Tour of Indian visitors tomorrow.

Thrusday/Friday the PAC will be here using many of the conference rooms.

Michael Laxen here from LLO. Nicole Washington here for inventory.

Laser Status:
SysStat is good
Front End Power is 34.07W (should be around 30 W)
HPO Output Power is 168.5W
Front End Watch is GREEN
HPO Watch is GREEN

PMC:
It has been locked 2 days, 7 hr 33 minutes (should be days/weeks)
Reflected power = 16.55Watts
Transmitted power = 64.53Watts
PowerSum = 81.08Watts.

FSS:
It has been locked for 0 days 10 hr and 24 min (should be days/weeks)
TPD[V] = 3.623V (min 0.9V)

ISS:
The diffracted power is around 2.8% (should be 3-5%)
Last saturation event was 0 days 10 hours and 29 minutes ago (should be days/weeks)

Possible Issues:
none

• Osc Pwr and Current reflect the recent maintenance increase of diode powers.
  • subsequently, the PMC and HPL DC outputs follow
• Chiller plots also show a slight increase in pressures and flows

TITLE: 04/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 63Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    Wind: 19mph Gusts, 15mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.25 μm/s
QUICK SUMMARY: Environment is calm, and it seems that the h(t) data has been fixed

TITLE: 04/24 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

"No good h(t)" from beginning of current lock (6:42-11:24utc); everything looks good now.  Knocked down 4.2kHz line while L1 was down.  H1 has been locked for 8+hrs.
LOG:

• 10:12-11:12 GRB Stand Down
• 11:32-11:41:  Out of OBSERVING
  • A2L run (before & after measurement looks like it got worse. Will leave as is.)
  • 4.25kHz Violin Harmonic peak at 6e-17 as seen on running DARM spectra (WITH FM9 [+30deg phase] engaged).  Turned OFF FM9 & after 2min turned ON FM8 (-30deg).  So went from +30deg to -30deg.  Peak disappeared into noise floor.  ACCEPTED SDF Diff.

• h(t) issue appearing to be resolved.
• 10:12 GRB notification
• H1 range hovering at a steady 65Mpc.
• With GRB stand-down complete & L1 down---will run an A2L & damp 4.2kHz violin harmonic.

SYMPTOMS

This evening during the Operator Handoff, Jeff noticed that the GWI.stat state for H1 (see attached) was in a YELLOW "No good h(t)" state (this was after he had taken it to OBSERVING minutes earlier).

• On the 4/24/17 Daily Summary Page, the DMT SenseMon plot (see attached) shows a red GDS BNS Range of 30Mpc for this new current lock (the gray "Front End range" is at a more normal 65Mpc).
• On the CAL:  h(t) generation Calibration state plot (see attached), we are in the RED state for:  h(t) OK,  Kst smooth, Kpu smooth, Ka smooth, & Ka median
• DMT SPI Page:  No obvious issues listed
• Current Network Status for Nagois Core Page:  We have the following CRITICAL alarm for H1 Intent Bit:
  • Critical: at 1177056402 we found a total of 600.0 seconds where h(t) ok was off but intent was on. This happened for a total of 1 blocks. The worst offender had length 600.0 seconds (maximum allowed 270.0 ) starting at 1177055800.0 (buffer begin) and ending at 1177056400.0 (buffer end)

Summary:  Only symptom viewable in the Control Room is the GWI.stat.  Range looks fine on the BNS FOM on nuc0.

Do Not Think This Is EY CRC Error....

Travis noticed my note about the h(t) issue in my alog and just sent me a text about the issue he had during his graveyard shift & how he fixed it last week (alog35702:  EY CRC Error 9:51 UTC).  

I do not think this is the issue because we:

1. Did NOT receive an "EY CRC error"  Verbal Alarm
2. And all CRC values on the CDS Overview are 0.

My Action

Since, there are no alarms/notifications here, will send an email out to the DetChar Group (due to Summary Page), Peter Shawan (due to GWI.stat), & Greg Mendel/Dan Moreu/Dave Barker (due to nagois CRITICAL alarms).  Will then wait for any instructions for further action.