J. Kissel, S. Dwyer, P. Marsh, for team DetChar
 
Paul just gave an excellent walk-through of the summary page for the DetChar tool "hveto," (see summary page and descriptive paper). In the walk through, he pointed out that the noise monitor channels for the H1 SUS ETMY L1 (UIM) stage (e.g. H1:SUS-ETMY_L1_NOISEMON_LR_OUT_DQ) are consistently "winning" the veto rounds for a given day, and have been for quite some time.

I attach a plot courtesy of DetChar that shows how many h(t) triggers have been removed after vetoing using these UIM NOISEMON channels from Jun 30 to Jul 15 2017.

We should begin investigating this in more detail. 

While I don't yet advocate a replacement of this coil driver, I suggest we at least power cycle the drive signal chain (analog electronics) ASAP. 

   IFO locked at NLN. Commissioning work under way. 
At 18:59 (11:59PT) there was a mag 4.5 near Brookings Or. The P-Wave arrival is forecast to arrive around 19:30 (12:30PT). We should be OK, but time will tell.     

J. Kissel, S. Dwyer

Similar to the BSC ISI ST2 X/Y (longitudinal) broad-band excitations taken and projections made two weeks ago (see LHO aLOG 37752), I've processed the RX / RY (pitch) broad-band injections I took a few days ago (see LHO aLOG 38031).

As with longitudinal, All test masses show significant coupling with ambient pitch motion, and more so than in longitudinal especially around 70 Hz. In the first two attachments, I show the projection to DARM, both as a total sum compared with other terms in the noise budget, and as individual optics (including the two worst offenders in longitudinal). Thanks to Sheila for her help making these plots using her "simple" noise budget.
The couplings may be a little underestimated: the coherence between X/Y IN1s and RX/RY IN1s is non-negligible, but it's still small enough (0.1 to 0.2) that adding these noise predictions are incoherent (i.e. adding them in quadrature) is close enough.
Remember that ST2 RX/RY are uncontrolled, but even if they were, the bandwidth could only be 30-40 Hz.

Unfortunately, though these excitations are *loud* as reported by the BSC ISI ST2 GS13s and DARM, the excitations are still too small to be visible in the optical levers* or OSEMs. *Strangely, the coherence between Sus. Point Motion (the projected and calibrated GS13s) and Optical levers goes *down* with the load excitation ON. The second two attachments show the details of the excitations.
But this means meas can't rule out that this *only* motion of the cage.

I'll attach measurement descriptions, calibration functions, and further support material eventually, but the data and templates have been (re)committed to the SeiSVN repo, now with excitation references included: 
/ligo/svncommon/SeiSVN/seismic/BSC-ISI/H1/Common/Data/
    2017-08-06_BSCISI_ST2_BB_RXRY_Injections_ETMX.xml
    2017-08-06_BSCISI_ST2_BB_RXRY_Injections_ETMY.xml
    2017-08-06_BSCISI_ST2_BB_RXRY_Injections_ITMX.xml
    2017-08-06_BSCISI_ST2_BB_RXRY_Injections_ITMY.xml
    2017-08-06_BSCISI_ST2_BB_RXRY_Injections.xml

I also provide a references key text file eventually as well, but I want to get this data up and get on to processing the RZ excitations also taken that day.

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.

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.