TITLE: 07/28 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 54Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 7mph Gusts, 5mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.05 μm/s

(4) EQs seen in the last 24hrs, but now the winds have just died down and useism is still low.
QUICK SUMMARY:

Current lock is almost 5hrs long.

I walked toward the Control Room to the howls of coyotes just before midnight; they didn't return my howls. 

Sheila, with many conversations with Keita, Jeff K, and others

We have several reasons to believe that something changed in our suspensions durring the Montana EQ.  (See alog from Beverly Berger and Josh Smith, (37775) which got us started looking at this, and Cheyl's log about the large triples, (37674).  We are still looking at some of the data from alignment sensors, but here arer some things we can say:

• The torque required to produce a fixed top mass pitch has changed after the EQ.
  • The 1st attachment shows the top mass applied force (calibrated in urad using sliders) vs osem readback for all 4 quads, color coded for before and after the EQ.  The linear relationship before the earthquake is offset from the relationship after the EQ. The torque applied to the top mass are calibrated into urad using the slider calibrations, I will update this alog in the morning with torques in torque units.
• The top mass pitch required to produce the same test mass alignment is 100s of uradian different before/after the EQ.
  • We trust the oplevs because restoring them after the EQ allowed us to lock the IFO with roughly the same spot positions as before the EQ.   (37451).  The second attachment shows you the change in top mass pitch required to produce a similar opLev pitch for each test mass.  
• We think that the osems (at least on the quad top masses) are OK.  
  • Jeff Kissel's top to top transfer functions which look the same as before the EQ. (37689)
  • The top mass actuation strength seems to be the same as before the EQ. In the first attachment the slope of the linear relationship before the EQ is the same as the slope after, meaning the actuation strenth is the same. 

There is more to be done checked on here, for example, checking if this has happened at any other times during the run (I checked one large EQ, I see no shifts like this), checking yaw (which has much smaller shifts than pitch), checking the triples, and looking at the alignments of the reaction chains.  Can we interpret the information we have to make a gues aout what might have changed in the suspension? Wire slipping or some kind of damage to the prisms are some things we have been thinking about. 

6:53UTC INJ_TRANS node active. LLO acknowledged.

06:23UTC As per Sudarshan's aLog, I changed the calibration line configuration. Below is an image of the SDF diffs accepted to go back into Observing.

All BS spectra look fine. ETMY shows the only slightly elevated HF noise. Nothing to be concerned with.

All HAM spectra looks good.

Violin modes.

• After taming the strings over a course of several hours and several failed attempts at NLN, fundamental modes dropped below the requisite level of e-15. Thanks again for the support of Dr Kissel
• HFD came on site to check the radio at MX which hadn't reported properly this afternoon
• PI modes (mode 28) were troublesome and caused one lockloss while trying to damp earlier in the shift. Later, I was having a bit more difficulty so I got Terra on phone support and ended up handling it without much intervention. Thank you Terra.
• Sudarshan and Rick are currently doing PCal cal line testing. In a little while I'll be getting a call from Sudarshan to turn off a couple of lines and turn another one back on. This will take H1 out of Observing briefly. I may take the opportunity to run a2l if necessary.
• a2l was run. A few more gain mods were made to violin mode damping and H1 is back into OBSERVING! ...and I just noticed that I'm 46 minutes late switching the Observatory mode.
• there has also been a smattering of small earthquake activity but nothing destructive for H1.

We are running two Pcal lines at ENDX at 333.9 and 1083.3 Hz with amplitudes twice as  large as yesterday to get better SNRs. These lines will be on for two hours. The SDF changes as a result of changing the amplitudes were accepted and monitored. Ed will turn these lines off in two hours and start a high frequency line at 3001.3 Hz.

~01:00UTC It didn't report this afternoon.

J. Kissel

I'm behind on my documentation as I slow process all the data that I'm collecting these days. 
This aLOG is to document that on this past Tuesday (2017-07-25) I took standard top-to-top mass transfer functions for the Triple SUS (BS, HLTS, and HSTS; 10 SUS in total), as I've done for the QUADs (see LHO aLOG 37689 and associated comments).

I saw no evidence of rubbing during the act of measurement, but I'd like to confirm with a thorough comparison. As such, I'll post comparisons against previous measurements, other suspensions, and the appropriate model in due time.

This leaves: 3 doubles, 9 singles.

Data is stored and committed here:
/ligo/svncommon/SusSVN/sus/trunk/BSFM/H1/BS/SAGM1/Data/
2017-07-25_1501_H1SUSBS_M1_WhiteNoise_L_0p01to50Hz.xml
2017-07-25_1501_H1SUSBS_M1_WhiteNoise_P_0p01to50Hz.xml
2017-07-25_1501_H1SUSBS_M1_WhiteNoise_R_0p01to50Hz.xml
2017-07-25_1501_H1SUSBS_M1_WhiteNoise_T_0p01to50Hz.xml
2017-07-25_1501_H1SUSBS_M1_WhiteNoise_V_0p01to50Hz.xml
2017-07-25_1501_H1SUSBS_M1_WhiteNoise_Y_0p01to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/PR3/SAGM1/Data/
2017-07-25_1507_H1SUSPR3_WhiteNoise_L_0p01to50Hz.xml
2017-07-25_1507_H1SUSPR3_WhiteNoise_P_0p01to50Hz.xml
2017-07-25_1507_H1SUSPR3_WhiteNoise_R_0p01to50Hz.xml
2017-07-25_1507_H1SUSPR3_WhiteNoise_T_0p01to50Hz.xml
2017-07-25_1507_H1SUSPR3_WhiteNoise_V_0p01to50Hz.xml
2017-07-25_1507_H1SUSPR3_WhiteNoise_Y_0p01to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/SR3/SAGM1/Data/
2017-07-25_H1SUSSR3_M1_WhiteNoise_L_0p01to50Hz.xml
2017-07-25_H1SUSSR3_M1_WhiteNoise_P_0p01to50Hz.xml
2017-07-25_H1SUSSR3_M1_WhiteNoise_R_0p01to50Hz.xml
2017-07-25_H1SUSSR3_M1_WhiteNoise_T_0p01to50Hz.xml
2017-07-25_H1SUSSR3_M1_WhiteNoise_V_0p01to50Hz.xml
2017-07-25_H1SUSSR3_M1_WhiteNoise_Y_0p01to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/
PR2/SAGM1/Data/2017-07-25_1607_H1SUSPR2_M1_WhiteNoise_L_0p01to50Hz.xml
PR2/SAGM1/Data/2017-07-25_1607_H1SUSPR2_M1_WhiteNoise_P_0p01to50Hz.xml
PR2/SAGM1/Data/2017-07-25_1607_H1SUSPR2_M1_WhiteNoise_R_0p01to50Hz.xml
PR2/SAGM1/Data/2017-07-25_1607_H1SUSPR2_M1_WhiteNoise_T_0p01to50Hz.xml
PR2/SAGM1/Data/2017-07-25_1607_H1SUSPR2_M1_WhiteNoise_V_0p01to50Hz.xml
PR2/SAGM1/Data/2017-07-25_1607_H1SUSPR2_M1_WhiteNoise_Y_0p01to50Hz.xml

PRM/SAGM1/Data/2017-07-25_1607_H1SUSPRM_M1_WhiteNoise_L_0p03to50Hz.xml
PRM/SAGM1/Data/2017-07-25_1607_H1SUSPRM_M1_WhiteNoise_P_0p01to50Hz.xml
PRM/SAGM1/Data/2017-07-25_1607_H1SUSPRM_M1_WhiteNoise_R_0p01to50Hz.xml
PRM/SAGM1/Data/2017-07-25_1607_H1SUSPRM_M1_WhiteNoise_T_0p01to50Hz.xml
PRM/SAGM1/Data/2017-07-25_1607_H1SUSPRM_M1_WhiteNoise_V_0p01to50Hz.xml
PRM/SAGM1/Data/2017-07-25_1607_H1SUSPRM_M1_WhiteNoise_Y_0p01to50Hz.xml

SR2/SAGM1/Data/2017-07-25_1715_H1SUSSR2_M1_WhiteNoise_L_0p01to50Hz.xml
SR2/SAGM1/Data/2017-07-25_1715_H1SUSSR2_M1_WhiteNoise_P_0p01to50Hz.xml
SR2/SAGM1/Data/2017-07-25_1715_H1SUSSR2_M1_WhiteNoise_R_0p01to50Hz.xml
SR2/SAGM1/Data/2017-07-25_1715_H1SUSSR2_M1_WhiteNoise_T_0p01to50Hz.xml
SR2/SAGM1/Data/2017-07-25_1715_H1SUSSR2_M1_WhiteNoise_V_0p01to50Hz.xml
SR2/SAGM1/Data/2017-07-25_1715_H1SUSSR2_M1_WhiteNoise_Y_0p01to50Hz.xml

SRM/SAGM1/Data/2017-07-25_1814_H1SUSSRM_M1_WhiteNoise_L_0p01to50Hz.xml
SRM/SAGM1/Data/2017-07-25_1814_H1SUSSRM_M1_WhiteNoise_P_0p01to50Hz.xml
SRM/SAGM1/Data/2017-07-25_1814_H1SUSSRM_M1_WhiteNoise_R_0p01to50Hz.xml
SRM/SAGM1/Data/2017-07-25_1814_H1SUSSRM_M1_WhiteNoise_T_0p01to50Hz.xml
SRM/SAGM1/Data/2017-07-25_1814_H1SUSSRM_M1_WhiteNoise_V_0p01to50Hz.xml
SRM/SAGM1/Data/2017-07-25_1814_H1SUSSRM_M1_WhiteNoise_Y_0p01to50Hz.xml

The C00 vs. C01 comparison pages have been updated and include all C01 data between 2016-11-30 0:00 and 2017-06-20 0:00.

As part of this analysis, I've got updated PCAL-to-DARM ratio trends at 36.7, 331.9 and 1083.7 Hz. Plots of both magntidue and phase residual timeseries trends are attached. As a reminder, these trends are computed by demodulating 300-second segments at each PCAL line frequency, then averaging to get a magnitude and phase out of each channel. In practice, I break up each 300-second segment into overlapping 100-second chunks, apply a Kaiser window, and then average over chunks to get a less noisy measurement. (It's basically Welch's method, except I'm demodulating rather than computing a PSD.) Finally, I remove outliers that are due to locklosses and loud transient glitches.

In each plot below I show PCAL/strain trends for C00 (blue) and C01 (red) data. The trend shown in aquamarine applies a correction for f_cc to C01 data at the appropriate PCAL line frequency. Gray shaded regions correspond to times when we had a break in O2, once during the holiday season and once for commissioning work. This is identical to a similar study done on Livingston data; see L1 aLog 35102.

You can see that in the bucket (331.9 Hz) we continue to have no systematics and only very small (~1%) statistical fluctuation when we correct for f_cc. At high frequency (1083.7 Hz) there's a slight systematic offset in magnitude and phase, but it's at the level of 2% or so which is consistent with Craig's error budget. At low frequency (36.7 Hz) there's a 3-4% systematic offset since we came back after the break on June 8 that isn't accounted for by f_cc, but I'll bet it's due to optical spring detuning. The offset also shows up in ASD ratio spectra; see the DetChar summary page from the first day after break. I have it as an action item to look into this in the next few days, so stay tuned!

I have restarted SegGener_H1 to include the H1:DMT-ITMY_L2_DAC_OVERFLOW as defined by TJ. This shouldn't have any side effects other than a loss of 1-2 secons of segment data. The H1 IFO was not in low noise data taking at the time so this shouldn't matter much.

I think I have the seismon code running a bit better now. At least it is running on it's own, and hasn't needed restarting since last week. The main differences are now the 5 event epics code looks like its running, and the seismon_run_info script I'm using now touches on the current event folder every loop. I think this was getting "cleaned up" before and not getting recreated or something. I've added a test to diag main if any earthquake has an arrival time in the future, so there is at least some notification that an earthquake is coming. This should be in addition to the verbal test (which may need updated? I'm not sure what TJ has done) that also has a threshold on the predicted ground velocities. The earthquake today was below the verbal threshold, so didn't get noticed by verbal alarms, but seismon gave us plenty of warning.

TITLE: 07/27 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
    Wind: 15mph Gusts, 12mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:

J. Kissel, J. Warner

We've lost lock due to a non-exciting earthquake, re-acquired up to DC Readout Transition watching the violin modes carefully, but we lost lock there (while sill controlling DARM with ETMX). Upon the *next* re-acquisition, though, the ETMX violin modes were incredibly rung up. 

As such, we stopped at Shutter ALS and baby-sat the ETMX modes until the DCPD RMS was reduced from 1e4 to 2e3. We used Ed Merilh's as our babysitter configuration for the now-problematic ETMX MODE 4 at 505.805 Hz, namely driving in Length, Pitch, and Yaw, ~75 gain, FMs 1 (505.805), 2 (-60 deg), and 4 (100dB).

This was successful, so we've now programmed this into the guardian.

We highly recommend operators hold any re-acquisition from now on at SHUTTER_ALS, wait for the OMC to lock, then grab a ~0.005 mHz spectra, and opening the outputs of ETMX first 5 violin MODE filters to make sure that violin modes are not rung up. Then, if violins are OK (i.e. RMS of DCPDs is less that 2e3 [ct]), you can go to the first Violin Mode Damping state but be prepared to turn the damping filters off before things get terrible!

Only one more month of this, team -- we can do it!