Firstly, some Jason induced phenomenon:

• Sharp spike up to 40 on 70W DCUR2 plot in the WeeklyXtal template
• .7 degree decrease in 70W D2 and D3 Temp plots which in turn affected the ....
• PMC Trans, which has been trending upwards as of late

Chiller :

• the sharp downward movements in the DCHILFLOW that Jason noiced last week has changed a bit into longer ramp up times and also resulting in the flow not returning to what had previously been the nominal rate. Jeff B explained that this was likely due to power fluctuations and the motors that we have are not power/speed regulated.

Shifter: Adrian Helmling-Cornell

Fellow: Vlad

DQ Shift Summary:

• Duty factor of 63.81% for the week
• High sustained winds, gusts and high microseism lead to lower range, lots of scattering glitches
• Mistakenly out of observing for over 3.5 hours on Thursday
  • Detchar group resolved to make new flag "H1:DMT-ANALYSIS_READY_9JAN2020_OBS_INTENT_FIX:1" and to add active segment by hand
• A PEM radio channel appeared in the HVeto results on Thursday
• When not windy, range was approximately 120 Mpc, when windy, range was 95-100 Mpc

TITLE: 01/13 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 120Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_CONF state: USEISM_WINDY
    Wind: 12mph Gusts, 8mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.49 μm/s
QUICK SUMMARY:

I have nothhing to add to Corey's parting summary  regarding the current state of the IFO and site at this time

TCS-X chiller water level is good. Did not add any water. 
TCS-Y chiller was down to 9.0. Added 125ml to bring it up to 10.1. 
Everything else looks good. 

Closing FAMIS #11526

TITLE: 01/13 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 118Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY:

After the windy weekend, I forgot what it was like to have a shift like today!  H1's been locked for 18.5hrs, and for most of the shift hovering at around 118.5Mpc.  And now the day starts with addressing:  tumbleweeds!

Microseism is still at the 90th percentile, so SEI_CONF hasn't been touched (it is in USEISM_WINDY).
LOG:

• 15:27 TCS Chiller weekly check (Jeff B)
• 15:35 Tumbleweed work begins with the Big Green Harvester off to first clear the Y-arm (Tyler, Chris).

• Smooth sailing for H1 (15hrs locked w/ a nice steady range for the last 7hrs just under 120Mpc).  
• Microseism steady at 90th percentile (0.5um/s) & winds are mostly under 10mph for last 4hrs (for End & Corner Stations).

    Laser Status:
    Front End Power is 32.32W (should be around 30 W)
    70W Output Power is 70.37W
    Front End Watch is GREEN
    70W Watch is GREEN

    PMC:
    It has been locked 11 days, 16 hr 57 minutes (should be days/weeks)
    Reflected power = 11.51Watts
    Transmitted power = 52.38Watts
    PowerSum = 63.89Watts.

    FSS:
    It has been locked for 0 days 15 hr and 15 min (should be days/weeks)
    TPD[V] = 5.252V (min 0.9V)

    ISS:
    The diffracted power is around 2.5%
    Last saturation event was 0 days 15 hours and 15 minutes ago (should be days/weeks)

The following CPS is listed as over threshold (all others OK & all spectra attached):

• BS_ST2_CPSINF_V1_I high freq noise is high!

TITLE: 01/13 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 118Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    SEI_CONF state: USEISM_WINDY
    Wind: 8mph Gusts, 5mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.51 μm/s

Walked in and there were no winds for a change!  Microseism is holding at the 90th percentile.
QUICK SUMMARY:

• H1 locked for over 10.75hrs & for the last 3hrs the range is fairly flat around 119Mpc.
• SEI_CONF = USEISM_WINDY; BRS-Y was in the Damping state, but is now in the green READY state (probably due to reduced winds).

TITLE: 01/13 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: locked all shift, useism is hovering around 0.5um/s, winds are below 20mph
LOG:

• SEI config is USEISM_WINDY

STATE of H1: Observing at 115Mpc
CURRENT ENVIRONMENT:
    SEI_CONF state: USEISM_WINDY
    Wind: 24mph Gusts, 20mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.50 μm/s

I looked at the very noisy period over the weekend associated with the high microseismic peak to double check that the noise was consistent with https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=54298, and that the R0 path we are hoping to incoporate into models on Tuesday would likely help.  The figure shows that the arch frequency spacing in DARM pretty well predicts the relative velocity of L2 and R2. The hypothesis is that the scattering path is between the ESD traces on the RM and the HR coating on the TM, with the arch frequency spacing given by the TM-RM relative velocity and the arch stacking in frequency due to multiple cycles on this path with 90% power loss each cycle. R0 tracking would reduce the TM-RM relative motion and appears to have helped at LLO https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=50897 .

Cheryl, Jenne, Rahul

On Jan 8, 2020 we had a lockloss due to rung up violin modes. When the operators attempted to re-lock the interferometer, we suffered another lock-loss (at Guardian state 430, Engage_ASC_FOR_FULL_IFO). Hence, we analyzed the typical noise floor during lock acquisition and then tried to define a threshold before attempting full IFO lock. Figure attached below shows the DARM spectrum for 08 Jan 2020, focussed on the 1st and 2nd harmonics for the violin modes. In the plot (Darm.jpg, during the 2nd attempt for re-locking the IFO), the noise floor at Guardian state 430 is shown in red line (UTC 00:02:32). As one can see, several of the modes are rung up, ranging from 10^-15 m/sqrtHz to 10^-14m/sqrtHz (while the typical rms of the floor was around 10^-17m/sqrtHz). The IFO remained at this state for 4 hours, during which the rung up violin modes were damped (1st harmonic for this case). Later, several of the peaks subsided, except for a couple of them, following which a full IFO lock was achieved as shown in the ndscope.

Based on this experience we can set some guidance for the violin mode noise floor during locking attempts. Once Guardian state reaches  PREP_ASC_FOR_FULL_IFO (429), at this point if no more than 1-2 modes are above 10^-15m/sqrtHz, while the others are below 10^-16m/sqrtHz then the operators can proceed to the next Guardian state. If at all the rung up modes are required to be damped then during this time the Guardian can remain at the same state.

TITLE: 01/13 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 113Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    SEI_CONF state: USEISM_WINDY
    Wind: 28mph Gusts, 19mph 5min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.60 μm/s
QUICK SUMMARY: locked in Observe

TITLE: 01/12 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 118Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:

• The wind may or may not be what caused a lock loss but locking was able to be done within the following lull. There were two more windy uproars that H1 survived.
• The wind clearly had more of a negative effect on the range tha the shelf noise caused by the high uSeism
• Handing off to Cheryl

LOG:

21:11 H1 back to Observing

H1 had a 4hr lock and this was with sustained winds near 20mph, and then there was a random lockloss.  

Once again, FSS would not lock and the PSL_FSS said it was due to "FSS Oscillating".  (most recent alog of this I see is from June 2018)  

I did the same thing I did earlier in the shift for this:  toggled FSS autolocker, took ISC_LOCK to INIT/DOWN, took IMC_LOCK to INIT/LOCKING (& DOWN).  Then I took PSL_FSS to INIT/DOWN (then FSS locked).  This time it took 8min vs 20min after the last lock.

I marked this down time as CORRECTIVE MAINTENANCE since this isn't normal.  (although Ed has just walked in, he mentioned addressing this before and Jason mentioned to him that there was a special way to "toggle" the FSS autolocker....so don't turn it off and wait a while.  Just turn off and then on....but I'm pretty sure I tried that and other variants.)

Anyway, FSS during my shift wasn't happy.  Am curious to know if this is a trend.

Looking at a trend of the wind speeds shows that the end stations are consistently below the other buildings. This is obviously dependent on the direction of the wind, but this looks very promising.

The attachment shows the last ~15 hours with the end station traces (blue and purple) consistently below the other buildings. Zooming out got messy, but you get the idea with this shot.