Summary: H1 Remained Locked, L1 Broke lock, Virgo was already down before EQ
H1 rode through this decent-sized EQ from the South Pacific. The green ITMY Z EQ BLRMS signal approached 1000nm, but never got there (instructions say to take it to LARGE_EQ, which I assume is LARGE_EQ_NOBRSXY [I'm assuming even when locked?], but we never reached the threshold).
Play By Play Of Signals/Tools/Monitors As EQ Approaches/Passes:
TITLE: 06/25 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
Wind: 4mph Gusts, 3mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.07 μm/s
useism continues it's downward step down from yesterday. Winds are gentle/neglible.
QUICK SUMMARY:
Two fast locklosses over the last 12hrs for H1; Jim mentioned recent one was extremely easy/fast to recover from. Currently approaching 4hr lock.
Noticed some recent DARM blrms oscillations on the video0 StripTool, (see attached)....these have generally been flat when I've scanned them for my recent shifts of last couple weeks:
(Only mentioning these, because haven't noticed much activities on these lately.)
TITLE: 06/25 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: One unexplained lockloss, but it locked right back up
LOG:
10:54 Lockloss
11:22 Back to Observing
TITLE: 06/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY: One lock loss, but ti came back up with no issues.
LOG:
No obvious reasons why we broke lock. 60hrs and 2min
Back to Observing at 05:47 UTC
58 hours locked with calm environment. DIAG_MAIN started reporting the PCAL Y RX PD greater than 1% off message again. Trended and saw the same as yesterday (see 37103)
TITLE: 06/24 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
Wind: 9mph Gusts, 7mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY: 54 hour lock, calm environment.
TITLE: 06/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
Nice quiet shift with H1 locked for almost 54hrs.
LOG:
TITLE: 06/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
Wind: 4mph Gusts, 3mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.12 μm/s
useism has taken a step below the 50th percentile in the last 14hrs. No winds. Going to be a hot one today (102degF forecast!).
QUICK SUMMARY:
H1 locked for 46+hrs. H1, L1, & V1 have been locked for the majority of the last 22hrs.
TITLE: 06/24 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 69Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Quiet shift
LOG:
Nothing to report. A couple small earthquakes, but locked for 45 hours now.
TITLE: 06/24 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 66Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY: Nothing much to report other than what was mentioned in 37103.
LOG:
Locked for 34 hours at 67Mpc.
DIAG_MAIN is showing "PCAL: Y RX PD is greater than 1% off". Trending the channel that is looks at (H1:CAL-PCALY_RX_PD_VOLTS_OUTPUT), it has dropped very slightly. This same message showed up about 12 hours ago, so I got suspicious of temperature. Sure enough, you can clearly see it dip with the temperature. See 2 day trend below
TITLE: 06/23 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
Wind: 11mph Gusts, 9mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.13 μm/s
QUICK SUMMARY: 30 hr lock, not much else to report
TITLE: 06/23 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Locked in Observing for the entire shift and ~27 hours total. No issues to report.
LOG: None
We have remained in Observing for the duration of the shift thus far. 26 hours locked and 23.5 hours in Observing.
At 05:27 6/23/2017 UTC (22:27 PDT Thursday night) we received a short timing GPS-EY error which cleared quickly. Looking at DAQ trends for this system, this appears to be another bogus GPS error. The attached dataviewer trend (second trend, 5 minutes duration, 20:25 - 20:30 PDT Thu 6/22) shows that the reported number of tracked satellites drops to zero, but the not-tracking-satellites flag does not report this. Also the number of visible satellites stays at 10 during the glitch.
model restarts logged for Thu 22/Jun/2017 - Wed 14/Jun/2017 No restarts reported
model restarts logged for Tue 13/Jun/2017
2017_06_13 09:24 h1isiham6
2017_06_13 09:29 h1broadcast0
2017_06_13 09:29 h1dc0
2017_06_13 09:29 h1fw0
2017_06_13 09:29 h1fw1
2017_06_13 09:29 h1fw2
2017_06_13 09:29 h1nds0
2017_06_13 09:29 h1nds1
2017_06_13 09:29 h1tw1
2017_06_13 10:19 h1isiham6
2017_06_13 11:23 h1iopoaf0
2017_06_13 11:23 h1oaf
2017_06_13 11:23 h1pemcs
2017_06_13 11:23 h1tcscs
2017_06_13 11:24 h1calcs
2017_06_13 11:24 h1iopseih45
2017_06_13 11:24 h1ngn
2017_06_13 11:24 h1odcmaster
2017_06_13 11:24 h1susprocpi
2017_06_13 11:26 h1hpiham4
2017_06_13 11:26 h1hpiham5
2017_06_13 11:26 h1iopoaf0
2017_06_13 11:26 h1isiham4
2017_06_13 11:26 h1isiham5
2017_06_13 11:27 h1calcs
2017_06_13 11:27 h1oaf
2017_06_13 11:27 h1odcmaster
2017_06_13 11:27 h1pemcs
2017_06_13 11:27 h1tcscs
2017_06_13 11:28 h1ngn
2017_06_13 11:28 h1susprocpi
Maintenance Tuesday. New isiham6 code with associated DAQ restarts. Unexpected problems with h1seih45 and h1oaf0 which required model restarts.
model restarts logged for Mon 12/Jun/2017 - Wed 07/Jun/2017 No restarts reported
model restarts logged for Tue 06/Jun/2017
2017_06_06 08:54 h1susomc
Maintenance Tuesday, minor model change to h1susomc.
model restarts logged for Mon 05/Jun/2017 - Sat 03/Jun/2017 No restarts reported
model restarts logged for Fri 02/Jun/2017
2017_06_02 10:17 h1caley
2017_06_02 10:17 h1iopiscey
2017_06_02 10:17 h1iscey
2017_06_02 10:17 h1pemey
2017_06_02 10:18 h1caley
2017_06_02 10:18 h1iopiscey
2017_06_02 10:18 h1iscey
2017_06_02 10:18 h1pemey
2017_06_02 10:19 h1alsey
h1iscey power cycle as part of ALS-Y problem investigation.
model restarts logged for Thu 01/Jun/2017
2017_06_01 11:59 h1nds1
2017_06_01 12:01 h1nds0
Completion of minute trend offloading required restart of NDS daqd.
model restarts logged for Wed 31/May/2017 No restarts reported
TITLE: 06/23 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 66Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
Wind: 4mph Gusts, 2mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.18 μm/s
QUICK SUMMARY: No issues handed off. Lock is ~22 hours old.
The last conversation that I had with Jim left me the understanding that switching to Large EQ anything is done after the lock is broken and is to simply keep the tripping under control. Unless I misunderstood, I don't think switching in-situ is going to help. Am I wrong? anyone?
Ed's right, the only intent of the large eq state is to keep the tables from tripping when the low frequency ground motion is large. Going to this state outside of some narrow circumstances will probably break the lock. The other eq states might work better, but the transition isn't fast enough and will also probably break the lock.
To remind everyone what the response is during an earthquake: While the IFO is locked, do nothing. AFTER the IFO goes down, if the earhtquake is big (probably like a mag 7+, but depends on distance) switch to the large eq state. When .03-.1 hz blrms are somewhere below 1 micron, switch back to the windy state. This is just to prevent tables from tripping, saving time and steps in recovery. The hope is that if the tables don't trip, you're less likely to have to do an initial alignment.
If you like resetting watchdogs and running through initial alignment, feel free to ignore these directions.