FYI - We've received the new LHO and LLO AERMs (QUAD Annulus End Reaction Masses) which now have a hole in the middle. These will be swapped in during the upcoming vent. Gerardo and I have been busy in the lab bonding prisms and bumps stops to these optics in prep for their use. We are currently 6 of 16 steps through the process to complete all 4 optics before shipping to the end stations for use in a few months.
Checked the PSL Chiller water levels and filters. Water levels in both chillers are good. The filters for both chillers show no accumulation of debris or discoloration. All appears normal at this time.
Ran the SEI seismometer mass monthly checks (FAMIS #6089) There are 4 T240 proof masses out of range ( > 0.3 [V] )! ETMY T240 1 DOF Z/W = -0.308 [V] ETMY T240 3 DOF X/U = -0.336 [V] ITMY T240 3 DOF X/U = -0.389 [V] ITMY T240 3 DOF Z/W = -0.534 [V] 2017-08-10 08:41:32.353313 All STSs prrof masses that within healthy range (< 2.0 [V]). Great!
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 INCOMING OPERATOR: Jeff SHIFT SUMMARY: Remained in observing the entire shift. No issues to report. LOG: 08:30 UTC - 08:47 UTC Walked through LSB (fire check). 10:30 UTC - 10:47 UTC Walked through LSB (fire check). 12:12 UTC - sometime before 12:53 UTC Chris moving GSA vehicles from OSB parking lot to near carpenter shop (from camera). 14:54 UTC Seal Coat Solutions through gate to work on parking lot.
Have remained in observing. No issues to report.
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.
I added this check to DIAG_MAIN under the SEISMON function. It simply just checks that the time difference between H1:SEI-SEISMON_SYSTEM_TIME_GPS_V2 and H1:DAQ-DC0_GPS is not greater that 60 seconds. I bumped the threshold from the 5 you suggested to 60sec because when watching the two channels it got close to that a number of times.
Also, I really like the new screen as an FOM.
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.
Also PT 170 and PT180 glitched at same time although with a different shape curve.
Hmmm. Wonder when Fil was installing his Cable Pulling Guide...
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.