TITLE: 11/16 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.41 μm/s
QUICK SUMMARY: Have been out of lock for 9h38. Jims log  53289  explains the trouble he was having. I will try again.

Still trying to get locked after Niko left, but being stopped by some weird issues. First was an OM1 trip at during I think DRMI asc offload, IFO stayed locked for a bit while I tried to figure out where to clear histories because all of the OMs were railed.

After that, I couldn't move past DRMI at all. The buildups were gradually degrading through several attempts to get DRMI, and each time ISC_LOCK would get stuck after DRMI or PRMI initial acquisition, then refuse to move on simply reporting "IMC_LOCK has notification". When I looked at IMC_LOCK, it didn't seem to have any such notification.

After multiple rounds of that, I'm trying to run initial alignment, but that is starting to look equally fruitless. The input alignment state seems to be hanging, saying ALIGN_IFO has notification. But ALIGN_IFO seems to be waiting for the input to a DC YAW loop to come on. This has continued through a number of steps in initial alignment, and the only way I've been able to move on is by manually selecting the the next offload state. This is probably all wrong. 

Initial alignment is "done", so back to locking. With an incoming earthquake. Oy.

TITLE: 11/15 Eve Shift 00:00 – 08:00 (16:00-00:00), all times posted in UTC

STATE of H1: Locking

INCOMING OPERATOR: Jim

SHIFT SUMMARY: Very quiet shift until sudden lockloss at 07:33. One lockloss from PREP_DC_READOUT_TRANSITION

LOG:

07:33 (23:33) Sudden lockloss. Unsure as to cause.

08:00 (00:00) Lockloss from PREP_DC_READOUT_TRANSITION

Green arms locked without issue

IR was not found, had to adjust ALS_DIFF

DRMI locked without issue

CARM Reduction States ran without issue

Lockloss from PREP_DC_READOUT_TRANSITION

We hope this means future build noise will be much less but there will be genie man-lift work as the hardware and fabric are installed over the next few days.

Attached image collar now filled with concrete.

Marc P., Tyler G., Kyle R.

During lunch today, a driver of one of the multiple concrete delivery trucks came into the multi-purpose room where we were eating and asked us where he was supposed to make his delivery -> I phoned the control room and confirmed that it should be at the X-end (at that time, later deliveries were made to the Y-end).  In the 1/2 hour prior to this driver's inquiry, we had observed other trucks heading down the X-arm but I wanted to confirm with the CR.  The driver mentioned something about attempting to use the beam tube overpass road initially but that he had noticed the 20 TON limit signage.  We clarified that he could get to his location by following the X-arm 2 1/2 miles all of the way to the end building etc...

Marc P. suggested that we immediately place traffic cones at the entry point of the overpass so as to prevent further confussion, which we did. 

Later, I noticed "75,000 GVW" marked on the side of one of these trucks. 

Ops Shift Transition: 11/15/2019, Eve Shift 00:00–08:00 (16:00-00:00) - UTC (PT)

State of H1: Locked

Intent Bit: Observing

Weather: 0-5 mph wind

Primary 0.03 – 0.1Hz: 0.01 um/s

Secondary 0.1 – 0.3Hz: 0.15 um/s

Outgoing Operator: Jeff

Quick Summary: Locked and Observing for two hours. Wind fence trucks starting to leave EY.

Following the discussion on the ISC call, there was a question of mechanisms to generate or propagate 3.125MHz noise out of the interferometer that the AS port has over vacuum. I remember that the themal noise of bulk modes in the optics can reach up to rather high frequencies. While the arms are the usual place to look, they aren't a great lead for the 3.125MHz since that won't resonate, but MICH sensing is still likely plenty sensitive to see bulk modes of the ITMs, in fact with 4kW in MICH it is more sensitive that the 2kW in the Holometer experiment interferometers. Those were 2kW power recycled Michelson interferometers (no arm or signal recycling cavities). Take a look at the AS port RF spectrum of that instrument.

HOLO_T0_thermal.png

• duty factor for shift: 70.5%
• repetitive glitch every 40 minutes on Friday and Saturday
• significant range drops throughout shift

Full DQ Shift Report can be found here: https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20191028

Camilla & Jeff B. 

   Two lock losses so far this shift. Both are related to the elevated microseism and wind fence activity at End-X. At the commissioners request, Camilla is running an initial alignment to see if we can improve the range a bit. Will try relocking when Initial Alignment is complete. 

  

Shiela, Arnaud, Timesh

The lockloss at 17:16:32 UTC appears to have been caused by ground motion at the Y end. We see that in the H1:ISI-GND_STS_ETMX_Y_BLRMS_1_3 seismometer, there are multiple peaks in the time series amplitude indicating increased ground motion at the Y end. As a result, H1:IMC-F_OUT16 became unstable and the lockloss occurred. We think this could be attributed to the wind fence installation that is currently being undertaken at the Y end. 

It appears that during periods where there are spikes in the 1_3 BLRMS, the IMC-F responds i.e there is some correlation between loud events at the end station seismometers and the IMC-F.

The NDSCOPE attachment shows the timeseries of the IMC, Lockstate, 10_30 STS BLRMS and the 1-10 STS BLRMS around the time of the lockloss.The y axis units are nanometres per second.

We left the air compressor (in chiller yard) off and valved out all night, with only the compressed N2 bottle feeding the four pneumatic gate valves in corner station. This morning the bottle pressure is quite low i.e. consumption/loss is high. We have some ideas to improve this but need LVEA access first.

At 8:36 am (16:36 UTC) I turned air compressors back on and valved in to corner building (but not LVEA). Before we start receiving alarms on PT199, I will valve back into LVEA, and request DetChar to look at data again to confirm correlation between noise and air compressor turned ON/OFF, but not valved into LVEA.

Nov. 14 (UTC - locked)

18:01 - turned compressor OFF

Nov. 15 (UTC - locked)

0:12 UTC - turned compressor ON

1:30 UTC - turned compressor OFF

16:36 UTC - turned compressor ON

17:26 UTC - valved in compressor to LVEA (after losing lock)

I compared one year of temperature stability of the two LIGO facilities using the quadruple suspension blades sag as a proxy for changes in building temperature.
The first figure shows the corner station data, the second figure the end stations.
The LHO corner station looks more stable than LLO, whereas the LLO ends (after the temperature sensors were moved away from the walls) look more stable than LHO.
I am reviewing how LHO controls their corner temperature so LLO could benefit from their stability. My understanding so far is that several of the in-loop temperature sensors are located on top of the beamtube (see picture attached for the HAM5 temperature sensors for instance). It is not yet clear to me how many sensors are used in-loop for the LHO corner station, and if any still from the wall sensors. At LLO we use all 34 wall sensors and do not have sensors near the chambers.
LHO could certainly improve the end stations temperature by moving the sensors away from the walls. Robert mentioned at last commissioning meeting this was a planned upgrade. A picture of the newly placed LLO end stations sensors is shown in this alog.