TITLE: 08/11 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 51Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY:
LOG:

23:05 Lockloss while doing A2L, then ALS was uncooperative

5:30 Eq notification, 6.2 in the Philipines. I had 2500 seconds to think about it before the R-waves arrived, 1500 seconds before P&S, I switched the seismic configuration to Earthquake_V2, but the .03-.1 blrms never went above .3 microns. 

7:00 I switch seismic back to Windy. Never got exciting, seismically speaking.

TITLE: 08/11 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: 8mph Gusts, 7mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.05 μm/s
QUICK SUMMARY:

H1 locked. EQ ringing down.

J. Kissel

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

The ISI basis RZ couplings are significantly less than that from pitch or yaw, but ETMX remains the worst offender.

Recall that an ISI basis RZ drive does not just cause Yaw of the suspension point, it also creates Longitudinal and Translational for the QUAD as well (see T1100617). This is similar to an RX / RY drive causing some X/Y and Z motion. If we still had the CART2EUL drive matrices installed, we might be able to create a pure Yaw drive, but this is likely not worth it based on these results. My gut says that what coupling we do see from RZ drive, is just the small Longitudinal component of the RZ drive.

However, the L, P and Y couplings may be a little underestimated: the coherence between X/Y IN1s ,RX/RY IN1s, and RZ 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) may be close enough.
RZ of the platform is controlled, but bandwidths are limited to 30-40 Hz.

The remaining open questions regarding the L and P coupling / noise:
- Is this the cause of some transient features we've seen in the 70 and 90 Hz regions throughout aLIGO at H1?
    - The coupling is likely stationary, but we know the input is not ... 
- Should we check the HAMs or Beam Splitter for similar nastiness?
- What is the coupling mechanism?
    - Charge interactions between the cage / EQ stops / ring heaters and the test mass?
    - Scattered light?
    - Impressive that H1 was so much more unlucky than L1 in this...
- Is there any evidence of this happening before the July 6th 2017 EQ?
    - We'll be taking long-duration coherence measurements to check for coherence, but this may be thwarted by the non-stationary of the input noise (and jitter + new mystery noise masking the issue)
- What should we look for when we first go in chamber for vent in 1 month?
- We presume this is the pre-damped QUAD cage resonance. What can we do about it in the future?
    - Even the non-resonant, 1/f^2 slope is high enough that the noise is well above the designed sensitivity. We need to fix this if we're to get there!
    - Strive for increasing the bandwidth of the ISIs? We've run out of phase margin because of signal processing phase loss to go beyond where we are now, plus table motion is already below the GS13 sensor noise
    - Try to move the cage resonance by subtracting / adding weight, or make the vibration absorbers more lossy to reduce the Q further?

Thomas Vo, Sheila, Fil

We lost lock on our attempt to transition from ETMY ESD to the ITMX ESD, because of a mistake I made in the script.  We want to be able to lock DARM on the ITM ESD driver so that we can lock the interferometer with one of the end station ESDs grounded and still transition to low noise low voltage (it seems like we have plenty of range to do this on ITMX).  

While we were unlocked we went to the floor with Fil and grounded all 5 cables, shield and pin, from the ITM ESDs.  We were locked like this from 22:52:00 UTC until 23:01 UTC on August 10th.  We saw no difference in the spectrum compared to our normal noise.  I went to the floor and attempted to reconnect the ESD cables for ITMY, with the driver powered off.  I connected the cables for the 4 quadrants but unlocked the IFO connecting the bias cable.  At LLO they were able to disconnect and reconnect these cables while in lock. (3502)

Following up on some remote MEDM display problems Sheila was experiencing which could have been due to some screens with (x,y) origin coordinates at high values, I wrote a python script to find which ADL files with bad origins.

Rather than scan every ADL file under the userapps area (there are 9,449 of them) my code starts at the SITEMAP.adl and drills down through all the related displays. It is not totally inclusive as some related display paths heavily use macro substitution.

Of the 4085 files scanned, 111 of them have an origin outside of the single monitor iMac resolution range of (2560,1440). Since these files are under svn control, I'll see how we can go about fixing this.

23:00 (16:00) Turn over to Jim

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.

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.