TITLE: 08/10 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.05 μm/s 
QUICK SUMMARY: No issues to report.

TITLE: 08/10 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY: Quiet shift, I had arts and crafts night
LOG:

IFO was locked when I got here.

4:35 High temp alarm in LVEA, seems to have been a sensor glitch.

I tried putting the original 5 event seismon screen up on nuc1 with the USGS page, but that MEDM takes up a lot of real estate and the arrival lights are hard to see from across the room (first attached image). You can't see the fonts either (and a lot of the locations are unreadable, we need all the language packages!), so I made a slightly more compact screen with big lights (second image, edit view is on the left, the running copy is on the right). The 3 square lights on the right of each block go from yellow (more than 2 minutes till arrival), to orange (between 1 & 2 minutes left) to red (less than a minute) for each wave type. While the arrival time is still positive, the rectangular light on the left will be orange for surface velocities between .5 & 1 micron, or red for more than 1 micron.

There's also a light at the bottom if the seismon system time gets more than 5 seconds behind H1:DAQ-DC0_GPS. We've found seismon dead a couple times, with the system time being stopped being the only symptom. I'd like to put this last test in DIAG_MAIN, too.

Got a verbal notification that CS temps were high. After a bit of poking at the verbal code for a bit I found that it looks at :

temp_dict = {
        'CS' : {
                'channel' : 'H0:FMC-LVEA_CONTROL_AVTEMP_DEGF',
                'nominal' : 69.5
                },
        'EX' : {
                'channel' : 'H0:FMC-EX_VEA_AVTEMP_DEGF',
                'nominal' : 65.0
                },
        'EY' : {
                'channel' : 'H0:FMC-EY_VEA_AVTEMP_DEGF',
                'nominal' : 65.0
                }
        }    
 

Attached minute trends make it seem like this is just some momentary glitch in the LVEA sensor. First is 12 hours, second is 3 days.

Hanford Fire Maintenance was out today after the 2 false alarms at the LSB and determined that the fire alarm control panel is faulty. Apparently a control board has been fried. HFD has taken the panel out of service and will remain disabled until we can correct the problem. 

Meanwhile, I would ask that the swing and owl shift operators do a walk through of the LSB every 2 hrs for the rest of the week and then 2 hr checks for all 3 shifts on the weekend. Training the control room camera towards the LSB may also be a good idea.

PT110 (HAM6 pressure gauge) showed some sort of "hiccup" - see attached.

I lowered the exposure for the IO GigE cameras on the PSL from 4000 to 100.  At this new exposure the cameras are not saturated at 30W.  The beams are hard to see at 2W, but the SUM is still sufficient for reasonable x/y data.

Sheila, Fil, T Vo

We got a little time at the end of PEM injections to try a different method of disconnecting the ETMX ESD cables.  We had the sheildling box already installed at EX, so we went there and first disabled the HV ESD driver, then powered off the low voltage driver.  Fil grounded the sheilds of the ESD cables using the grounding box, and then disconnected the LL cable from the shielding box (on the chamber side) and connected it to the grounding box he made on monday.  The interferometer stayed locked and the noise didn't change, but just as we were touching the cables on the input side of the shielding box the interferometer unlocked.  It seems like something is extremly touchy here, which we already knew. 

IFO is locked at NLN, Intent Bit is Commissioning. Robert S. doing PEM injections from 16:00 to 20:00 (09:00 to 13:00PT). 

   HFD responded to fire alarm at LSB. Bubba and Richard were notified. Appears to have been a false alarm. 
 

PT343b at the X-mid went off at about 10:30 hrs. local.  I re-enabled it and it came back on in a few minutes.  John W. contacted Gil Hibbs who was in the X-mid VEA at the time.  Gil didn't think that he was near the area of the gauge.  Perhaps just coincidence.  We have had gauges along the X-arm turn off a few times this year when there was human traffic in the area of the gauge(s) but no causal determination has been shown.  Probably unrelated.  

John and I both got emails when the gauge dropped out but no texts (5 minute threshold for texts?)

   TJ swept LVEA before the start of commissioning. He unplugged one unused extension cord. 

TITLE: 08/09 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 53Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: No issues to report.
LOG:

14:36 UTC Ken pulling wire in OSB.

Have remained in observing. No issues to report.

TITLE: 08/09 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 54Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 2mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.06 μm/s 
QUICK SUMMARY:

0.03 - 0.1 Hz seismic BLRMS is coming down from after earthquakes near Alaska.

07:25 UTC Lock clock not updating. Lock timer python script not running. Started. Screenshot attached.

SudarshanK, RichardS

We moved the Pcal beam back to their optimal position at 111.6 mm away from the center of the optic. The actual position of the  current Pcal beams (last column) along with the history of where they were are in the table below. The number quoted on the table are distance of Pcal beam (in mm) from their optimal position of [0, +/- 111.6] mm. 

We also re-centered the Pcal beams on the receiver side to relieve it from any clipping that was happening outside the vacuum. The spectra attached below shows no significant clipping on the Rx beams.

We will run a set of calibration lines (from 4501.3 - 1501.3 at 500 Hz interval) with this Pcal beam configuration for about a week.