Out of observing at 2205 UTC
We would like to reconcile safe.snaps at 8am, for Ops team.
Safety:
Tues. Maintenance: See attachment for whiteboard of scheduled activities.
Edit- updated picture
FAMIS#12859
I didn't notice any new features.
FAMIS#11229
ITMY P is greater than 10urad from center. ETMY P is nearing 10.
PMC power on it's usual downward excursion and FSS TPD currently at 4.1 which is approx 1V down from the last alignment on 7/02/2019.
TITLE: 08/05 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
Wind: 7mph Gusts, 4mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.05 μm/s
QUICK SUMMARY: 26 hour lock, calm environment.
TITLE: 08/05 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC STATE of H1: Observing at 113Mpc INCOMING OPERATOR: TJ SHIFT SUMMARY: Remained locked and in observing entire shift. Rode through earthquake in Tonga. LOG: 09:11 UTC SEI_CONF to EARTH_QUAKE for earthquake from Tonga 11:01 UTC SEI_CONF to WINDY
Have remained locked and in observing. Rode through earthquakes in Tonga.
TITLE: 08/05 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
Wind: 5mph Gusts, 4mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.05 μm/s
QUICK SUMMARY: No issues.
TITLE: 08/05 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY:locked, out of Observe for violins, into SEI EQ, and back to WINDY
LOG:
TITLE: 08/04 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 116Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
Wind: 10mph Gusts, 6mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.05 μm/s
QUICK SUMMARY: locked in Observe.
TITLE: 08/04 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: Breezy, but locked for 10hours. Sqz kicked us out of observing once, but quickly relocked.
LOG:
The squeezer lost lock, but then quickly relocked within a minute or two.
[JeffK, Jenne]
After Jeff noted that last night's lock had a somewhat low optical gain (kappa_C value of ~0.93), we moved the offsets in the OMC ASC QPDs to try to maximize optical gain. The attachment shows the moving that we did. It's possible that we could get a bit more if we were able to move in the direction that saturates the OMC SUS, but I'm not 100% sure about that, and to get it we'd have to pico the AS WFS so that we can move OM1 and OM2 to offload some of the alignment move.
We were able to convice the optical gain to come back to a value of 0.96ish, which is closer to what we've been having at 37W injected power for the last several weeks of O3. The offsets aren't very different from what they had been - for the most part the optical gain was happier where the alignment had been.
@DetChar -- This change in OMC alignment position appears to coincide with the drastic increase in glitches (below ~15 Hz, as reported by DMT Omega and Omicron) since Aug 1 2019.
You can confirm this by looking at trends of offsets in the OMC ASC system, under
H1:OMC-ASC_QPD_A_PIT_OFFSET
H1:OMC-ASC_QPD_A_YAW_OFFSET
H1:OMC-ASC_QPD_B_PIT_OFFSET
H1:OMC-ASC_QPD_B_YAW_OFFSET
We had changed these offsets to increase the DARM optical gain, but at the time we'd not considered that this position may be worse for things like coupling of seismic / acoustic noise, alignment jitter, scattered light, etc.
We'll bring this up at today's commissioning meeting and see if we can address it *and* improve the optical gain.
C. Gray, K. Kawabe, J. Kissel, D. Sigg
After initial alignment was complete (2019-07-24 ~20:00 UTC), we spent a bit of time stuck with several lock losses upon reaching LOCKING_ALS. Manually running what happens in LOCKING_ALS, we narrowed down the problem to ALS DIFF, and after 45minutes of searching, I happened to lance at the ETMX ESD driver's analog voltage monitors and noticed they looked abnormal. At 2019-07-24 20:42 UTC, I hit the H1:SUS-ETMX_BIO_L3_RESET ("HV ON/OFF") button on the QUAD overview screen once to turn OFF the driver, then once again a few seconds later to turn it ON.
It's likely that the ETMX ESD driver got locked up in a funky state after all of the power and computer issues over night.
The bigger question is why (what we thought were several) warnings that should have been triggered didn't:
(1) DIAG_MAIN guardian node "used to" (our memory of the O2 past) have a check of the analog voltage monitors, and would throw a warning.
(2) The DOWN / PREP_FOR_LOCKING state should have a similar check of the analog voltage monitors, throw and error when failed, and not allow progress until fixed.
Others are investing further and will comment / fix later.
The DIAG_MAIN test would notify if H1:IOP-SUSAUX_EX_MADC4_EPICS_CH0 was between +/-16200 when the ISC_LOCK state was below 515. This has been changed to look at the DC and the quadrants' inmon channels (ex. H1:SUS-ETMX_L3_ESDAMON_DC_INMON) to check that the DC signal is within 10% of -32300, the quadrants are less than 8000, and ISC_LOCK is under 500 before notifying. This seems to be a better way to confirm that the ESD is off.
Lock loss at 2219