Reports until 00:00, Tuesday 25 October 2016
LHO General
thomas.shaffer@LIGO.ORG - posted 00:00, Tuesday 25 October 2016 - last comment - 16:17, Tuesday 25 October 2016(30837)
Ops Eve Shift Summary

TITLE: 10/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Aquisition
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Locking DRMI/PRMI was not easy, it required large adjustments and waiting a good amount of time. useism is also getting pretty high so I tried the WINDY_USEISM state, brought it back to WINDY because I couldnt tell which was better. Aside form that the commissioners are working.

 

Comments related to this report
jim.warner@LIGO.ORG - 12:39, Tuesday 25 October 2016 (30848)SEI

I should probably just remove or rename the WINDY_USEISM state. It may have a use, but I think people are taking the configuration guide on the SEI_CONF screen too literally. I'm reluctant to try to make the guide more accurate because I'm not a cubist. The WINDY_USEISM state should be thought of as a more wind resistant state than the high microseism configuration we used during O1 (USEISM in SEI_CONF). Anyone remember how hard locking was with 15mph winds and high microseism during our first observing run?

We are getting into new territory with the current configuration (implemented during the windy, low microseism summer), but looking at the locks last night, it looks like the WINDY configuration is still what we want to use. The five attached plots are the ISC_LOCK state, SEI_CONF state (40 is WINDY, 35 is WINDY_USEISM), the ETMX Z 30-100mhz STS BLRMS (in nm, so 1000=1 micron) and the corner station windspeed. The last plot shows all four channels together, red is the ISC state, blue the SEI_CONF state, green is the STS BLRMS, black is the wind. It's kind of a mess, but it gives a better feel for the time line.

Microseism was high over this entire period (around 1micron RMS), wind was variable, so this was a good time to test. I think the take away is that the WINDY state was sufficient to handle the high microseism for the 2  NLN locks over this stretch, and is very probably more robust against the wind than the WINDY_USEISM state.

Images attached to this comment
thomas.shaffer@LIGO.ORG - 16:17, Tuesday 25 October 2016 (30868)

This is great to know. I was pretty sure that you said WINDY is good for almost every situation, but I thought it worth a try.

Tagging OpsInfo so we can get the lastest