edmond.merilh@LIGO.ORG - posted 04:07, Monday 26 June 2017 (37132)
Mid-Shift Summary
H1 locked and observing fort 2hr58min @ 65Mpc. There were a couple of glitches. Everything looks fine.
H1 locked and observing fort 2hr58min @ 65Mpc. There were a couple of glitches. Everything looks fine.
9:39UTC confirmed with Danny at Livingston.
08:20UTC 66.2Mpc
TITLE: 06/26 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
Wind: 4mph Gusts, 3mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.17 μm/s
QUICK SUMMARY:
TITLE: 06/26 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ed
SHIFT SUMMARY: A weird instability started a little into my shift. I think an initial alignment fixed this, but now I am still having trouble locking. It doesn't seem to be dropping at any particular place, and it has been difficult to get past DRMI. Passing it off to Ed with DRMI locked.
LOG:
Not the same issue as last time, no obvious reasons why at this point.
Same as last one, I'll try an initial alignment since DRMI wasn't great ast time.
The control signals started ringing up for the past 40min or so. They got to the point where I felt like we were going to lose it any second. CSOFT P and CHARD P seemed to be rung up the most, so in an act of desperation I went to ramp down the gain on those one at a time. It didn't work.
There are no obvious clues to me as to why the control loops started to ring up. I attached the lockloss plot and some trends
Back to Observing 01:09 UTC
The instability continues, but doesn't seem to be getting worse to the point of lock loss. It is hurting our range as we are now down to 56Mpc.
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 68Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
Wind: 11mph Gusts, 9mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.11 μm/s
QUICK SUMMARY: Almost 12hr lock, Corey had an earthquake that we rode through.
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 68Mpc.
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
Nice quiet shift with H1 up the entire shift.
LOG:
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:
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.
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:
Doing and initial alignment seemed to help, but it broke as I reached NOMINAL_LOW_NOISE. Time to try again.
Observing 03:35 UTC