TITLE: 12/27 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 113Mpc
INCOMING OPERATOR: Camilla
SHIFT SUMMARY:
Nice shift with H1 locked almost 8.25hrs. We stil have high useism, but we have also have had over a day without any big EQs on the planet.
There were issues with a "DEAD SEISMON", but Jim & Dave were able to get it going again.
LOG:
Corey, Jim, Dave:
we are currently investigating a non-updating seismon.
Nice quiet morning with H1 locked almost 4.25hrs. The earth has been quiet and no big EQs for the last 24+hrs *knock on wood*!
TITLE: 12/27 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 112Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_CONF state: USEISM
Wind: 2mph Gusts, 1mph 5min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.62 μm/s
12hrs ago Microseism took tiny step back up. There's a light dusting of snow here on the site and we have thick cloud coverage (in town barely any dusting & partially clear skies).
QUICK SUMMARY:
Walked in to an OBSERVING H1 that's been locked 0.25hrs with a range hovering around 112Mpc so far.
TITLE: 12/27 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 60Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Lock loss that may have been useism related. Relocking I had to touch TMSY to get the flashes above 1 before it would stay locked. Switching SEI_CONF to USEISM helped. Made it to DC_READOUT and then lost it. Fully automated back up to NLN after that.
I added SEI_DIFF and IFO_CALIB guardian nodes to the excluded list so tehy shouldn't cause us trouble anymore.
LOG:
No obvious cause other than high useism.
37 hours locked. No issues to report.
TITLE: 12/27 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 112Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 7mph Gusts, 4mph 5min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.85 μm/s
QUICK SUMMARY: Locked for 32.5 hours with high useism. Restarted LVAlert because it didn't have a heartbeat.
In the past 2 hours microseism has moved solidly above 0.5. There are glitches showing up in the 25 to 30Hz bands on the DMT plot. Took SEI_DIFF to OFF (using MEDM). Will monitor to see if the glitches go away.
Other than elevated microseism, all is good. No issues to report.
Swift GRB Alert (E358529). Latency and trigger duration are good. LHO and Virgo are observing. In 15 minute stand down. Did not receive notice on verbal alarms. LLO did and called.
TITLE: 12/26 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 111Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:
Busy morning with Calibration measurement + Site Walk Thru, but H1's remained lock the whole shift and locked for ~24.5hrs.
Microseism is beginning to slowly trend down.
LOG:
Earlier today, decided to turn SEI_DIFF back "ON" by taking it to an operational CORNER_DIFF_CPS state. (it was turned OFF yesterday due to high microseism). This brought up a SDF Diff for the DIFF CONTROL BIT (see 1st attachement). Since this is a new guardian node which will change with microseism, I went ahead and NOT MONITORED this channel. Probably too early to tell and also hard to tell since microseism is also inching down, but 2nd attachement is a look of glitches via DMT OMEGA (where the microseism shelf noise/glitches is in the 20-35Hz region).
Wanted to also see how we've been locking with microseism, H1 range, SEI_DIFF states (200 is FULL & 190 is CORNER), ISI CONTROL BIT channel over the last ~7 days (see 3rd attachment)
After the Calibration mesurement this morning, and as I was getting ready to slip H1 back into OBSERVING, noticed some SDF diffs (SEI_DIFF will be noted later).
The odd one was 10^13 diff for an IM2 Yaw offset (see atached). I know we want to keep an eye on these slider values, so I just ACCEPTed it, but why did this SDF diff appear? Was it related to the short calibration measurements I ran or purely coincidental?
TJ mentioned having another Diff due to IM offset before going to OBSERVING this morning.
With LHO closed over the holidays, and O3 still taking place 24/7 over the holidays, Site-Walkthrus have been schedule to be performed by operators during their shifts (DAY). I performed one this morning per instructions here. Since inspection of the LVEA, EX VEA, EY VEA are required, these incursions would require us to go out of OBSERVING. I chose to lump those three inspections together to minimize/optimize time we were out of OBSERVING (where I would take H1 out of OBSERVING, walk through the LVEA, and then drive out to EY & then EX consecutively, AND then finally return H1 to OBSERVING & finish remaining items of the Walk-Through.)
This morning I had H1 down for 35min to run calibration measurements, I was going to tack on VEA incursions to this down time, but we received an Earthquake Alert, so instead, I took H1 to OBSERVING & monitored the EQ in case we needed to transition SEI_CONF to the EARTHQUAKE state (this wasn't needed). Instead, it was observed the Calibration measurement prossibly affected Calibration Lines. Took H1 out of Observing, fixed this, and then began VEA incursions. Here is log:
Duration Total of Site Walk-Thru: ~90min (18:14 - 19:45utc)
Duration out of OBSERVING: ~51min
Ice On Liquid Nitrogen Dewars
One item we were asked to check was the exhaust of the LN2 dewars as we drove the site. I wasn't totally sure where the exhaust was, but eventually figured it out.
As you inspect the dewars there is frost/ice build up at various points (i.e. input plumbing where Norco connects, output to VEAs, & output exhausts [see attached photos for examples]). I texted Chandra and she mentioned alot of this is normal, but she said posting photos is good. Found ice on exhausts at End Stations and LVEA. Notes:
Ice build up on LN2 exhaust looks normal, because the vertical pipe is not insulated and heat trace is not active. Thanks for checking, Corey.
TJ has updated the instructions so that we do not go into the VEAs if we are OBSERVING.
~23:28 Notice the SEISMON Dead RED box is gone and DIAG MAIN for this is also gone. And Seismon has more recent events listed on its medm screen.
But I do not see the box flashing on the SEISMON medm screen (it was flashing when we had the issues though).
It looks like it's back up and running now. Not sure at all what happened. Will try to summarize here.
I let Dave and Corey try to recover following the instructions on the wiki (which are still accurate as far as I know) : https://cdswiki.ligo-wa.caltech.edu/wiki/seismon
I then tried following the same steps, but also deleted the old data for the USGS productclient (which took many minutes to complete, the last time this may have been done is July or maybe February).
I then told Dave it would be worth trying to restart the VM. After he did that, I expected the seismon processes to restore on their own, but they didn't after several minutes. So I follow the wiki procedure again.
Seismon screen and DIAG_MAIN still reported dead, which can be due to the seismon calculated GPS time not updating. I poked around in the epics code and added a couple lines to us gpstime to get the right gpstime, then just write that. Still didn't seem to work. Then a couple restarts later (from me messing with just the seismon epics client) it just started working. The only material change to the code was something like adding:
gt=gpstime.now.gpstime() -> whatever the right call is to get the current gps time, I don't remember
counter=int(gt)
caput(seismon_gps_epics_time_channel, gt)
I tried to get the epics code to print the "counter" value in STDOUT, so I could see it was updating in the terminal, but couldn't get python to be happy with doing that. I think that would be a useful indicator in the code. The only thing I can think of is that sometimes after deleting the USGS data, it can take a little while for the USGS code to get to recent enough earthquakes for the seismon code to be happy.
Also, when I try to plot the eq reponse plot from home, python complains about not being able to find the epics package. I don't remember seeing that before.
We are able to bring up the EQ Response plots in the Control Room.