Hi have set up the arm transmssion QPD monitor for storing the test mass resonant mode signals from 14.8-15.8kHz in 2kSa/sec channels: 
H1:SUS-ETMX_PI_DOWNCONV_DOWNCONV1_DEMOD_I_OUT_DQ 
H1:SUS-ETMX_PI_DOWNCONV_DOWNCONV2_DEMOD_I_OUT_DQ 
H1:SUS-ETMX_PI_DOWNCONV_DOWNCONV3_DEMOD_I_OUT_DQ 
H1:SUS-ETMX_PI_DOWNCONV_DOWNCONV4_DEMOD_I_OUT_DQ 
represent ETMX QPD A segments 1-4 downconverted such the 0Hz represents 14.8kHz and 1kHz represents 15.8kHz.

As you will recall, the usual "IN1/IN2" method for FFT-based OLTF measurement is fine if the IN1/EXC and IN2/EXC coherences are both high. Otherwise, the measurement biases toward 1, regardless of the actual loop shape.

As an illustration of this, I attach a DTT screenshot of one of Haocun's recent dHard pitch OLTF measurements, which apparently shows 1, 3, or 5 UGFs in this loop (depending on what mental coherence cutoff one is using). Next I attach an OLTF plot using the same data as above, but computed using IN1/EXC and converting the CLTF into the OLTF; this avoids the aforementioned bias. Evidently, there is only 1 UGF, and the loop gain below 1 Hz is stronger than what is suggested by DTT.

Since it's very difficult to get high coherence with these ASC loops, it seems like we should not be using IN1/IN2 FFT measurements for loopsmithing. Either we should switch to swept sine (which does demodulate both IN1 and IN2 against the excitation) or we should be exporting the FFT measurements as CLTFs and then plotting the OLTF elsewhere.

J. Kissel, S. Dwyer

While the IFO was held in the DOWN state, Shiela (while I watched) accepted all SDF differences for whichever SDF file they were currently comparing against. This brute force, half-reconciliation should get us some of the way toward an easier recovery after the power outage this weekend.

Thing we need to make SDF more maintainable:
1) Remove the distinction between SAFE and DOWN for SUS and SEI. Because SEI and SUS come up with the watchdog tripped, and the start up state for both systems guardian has the masterswitch off, there's no difference between these states. 
2) A rapid way to assess and change a group of front-end model's SDF reference files. I.e. we should be able to switch between OBSERVE and DOWN quickly instead of having the 4 screen, 15 clicks per front-end process it is now.
3) A easy, built in way to find out what channels of a given front-end are controlled by all guardians, such that we can un-monitor them.
4) A much easier way to reconcile non-initialized and not-found channels than the still-confusing SDF Save and SDF Restore screens.

Added 374 channels. Removed 596 channels. (List of changes attached)

State of H1: locking, and has had some issues with Engage Soft Loops

Site:

• no one in the LVEA or VEA's
• winds are 0-25mph

Activities:

• ESD driver work in the LVEA vertex - RichA, Calum, Fil, Ed - installation
• Vacuum work in the LVEA - John, Chandra - gate valve prep for power outage
• Property management - Gerardo, others - visiting LVEA, end-stations, mid-stations, other buildings
• Model restarts - DaveB - adding channels for ESD drive, modifying binary IO on QUADs
• DAC restart - DaveB - adding channels for ESD drive

Filiberto, Richard, Manny, Rich A.

The hardware for PI control and ESD actuation of ITMX and ITMY is mostly installed.  Power has been run to SUS rack R5 and R6, all signal and binary control functions are connected with one notable exception.  The two connections that were intended to be used for ADC monitoring of the ITM ESD Driver output voltages do not actually exist.  We are trying to come up with a workaround that will likely involve the addition of another ADC card.  The latest revision of the ITM wiring diagram is not accurate.  Either field changes crept in, or documents were updated but not implemented.  Either way, it will require work to fix things both from a document standpoint, and from the perspective of installed hardware.

At this point, no connections have been made from the ITM ESD Drivers to the cabling leading into the vacuum system and ultimately the ITMs.

One small thing to watch for is in the ITMX PUM coil drive signals.  The AI chassis serving this function was replaced to permit the use of the high frequency DAC signals intended for PI correction.  The PUM channels should not have been impacted, but it's worthy of note.  Here are the details:

Old AI chassis details located in CER Rack SUS-C6 at U23:
D1100815 Serial Number S1103818

New Chassis details replacing existing chassis SUS-C6 at U23:
D1600077 Serial Number S1600245, PI AI Chassis

John, Chandra

All pneumatic gate valves (GV 5,6,7,8) are sagged and resting on their locking pin. Just two (GV 6,8) passed the limit switch and transitioned to yellow state. 

Commissioners can still operate beam in this state. Sag is maybe 1/2" over 44" diam. 

Valves are locked out. The vacuum team will retain nominal state Monday morning after power comes back.

Attached are 7 day pitch, yaw, and sum trends for all active H1 optical levers as per FAMIS 4678.

The RTD/IR SENS. alarm tripped at 9:27 am local and shutdown the CO2X laser. There were no obvious cause. The laser was restored without a problem. h1oaf0 DAC was fine. Cheryl reported Gerado was out for a LVEA "clean up". Maybe some TCS cables got wiggled?

State of H1: locked and in Engage ASC Soft Loops

Activities:

16:13UTC - Gerard - LVEA cleanup, out at 16:45

16:20UTC - Evan / Tara - PI damping on ESD, ETMX and ETMY

16:49UTC - JonathanH - to and from H2 building throughout the day

16:50UTC - Chandra and John - donein LVEA, monitoring GV5, GV6, GV7, and GV8

16:59UTC  - Russ - to EX to join Evan and Tara

18:28UTC - RichA / Calum / Fil - all out of the LVEA

All persons are out of the LVEA and VEAs.

Please do not remove.

There is a bunch of extension cords spread through out the site VEAs, along with some power strips.  This components will be used to power all the annulus ion pumps, some vacuum racks and other components during the power outage over the weekend.

Please do not remove.

Down script in guardian will reset high voltage, so should not be run, so guardian is paused.

State of H1: H1 stuck at locking arms green

Activity:

Filiberto / RichA / Calum - ESD in LVEA

Richard - quick test of binary control

Me - working on TFs for ETMs L2 to Oplev, per request Corey / Rana

Craig, Sheila, Rana, Terra, Jim, Evan

In light of 27483, we wanted to try to balance the test mass PUM common/differential and hard/soft actuation. As a start, we wanted to make better common/differential actuation for the ETMs and ITMs (next we will try to make better hard/soft actuation).

We drove the ETMs in common-mode (pitch and yaw) and looked at the AS 45 Q pitch/yaw signals. We then adjusted the L2 LOCK P/Y filter gains in order to minimize the AS 45 Q signals. Gain adjustments of a few percent were required. The biggest reduction in AS 45 Q was a factor of a few; the smallest was basically nil.

Along the way we noticed that there was essentially a 1:1 cross-coupling between cHard pitch and cHard yaw when driving ETMs (i.e., driving cHard pitch would produce equally sized signals in both cHard pitch and cHard yaw). This could be explained by the transmon roll orientation causing a rotation of pitch into yaw at the QPDs. However, removing the QPD blending (i.e., using REFL A/B 9I only) for cHard reduced the cross-coupling by a factor of a few.

So it seems that the transmon QPDs are not aligned with the ETMs pitch/yaw alignment. However, the REFL pitch/yaw seems rotated from ETM pitch/yaw by ~30 deg. The ITM drives do not produce this cross-coupling. We want to minimize this to reduce the Hard looop pit/yaw instability that we saw. Should we rotate the REFL WFS matrix to align with the ETMs or ITMs?

We lost lock twice trying to switch CARM to in-vac control, so that needs to be debugged tomorrow.

Rana, Evan

WE measured the SRM to SRCL TF today to find the frequency and Q of the internal mode. Our hypothesis is that the thermal noise from the PEEK screws used to clamp the mirror into the mirror holder might be significant contribution to DARM.

The attached Bode plot shows the TF. The resonance frequency is ~3340 and the Q ~150. Our paper and pencil estimate is that this may be within an order of magnitude of DARM, depending upon the shape of the thermal noise spectrum. If its steeper than structural damping it could be very close.

"But isn't this ruled out by the DARM offset / noise test ?", you might be thinking. No! Since the SRCL->DARM coupling is a superposition of radiation pressure  (1/f^2) and the 'HOM' flat coupling, there is a broad notch in the SRCL->DARM TF at ~80 Hz. So, we need to redo this test at ~50 Hz to see if the changing SRCL coupling shows up there.

Also recall that the SRCLFF is not doing the right thing for SRM displacement noise; it is designed to subtract SRC sensing noise. Stay tuned for an updated noise budget with SRM thermal noise added.

** see  https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=27455  for pictures of the SRM compsoite mass.

Below are the past 10 day trends for thye PSL and it's environment. Unfortuntely it remains riddled with higher than normal incursions and the ongoing chiller woes.

J. Oberling, J. Bartlett, P. King (via phone)

Following yesterday's initial investigation into the PSl diode chiller issues (see alogs here), we swapped the control panel for the diode chiller with the one from the chiller we recently removed from service (this is a known working unit, just installed last year).  After installation the chiller restarted without issue and ran for several minutes, also without issue.  The serial number of the control panel we installed in the diode chiller is 44806P605; the faulty unit we removed from the diode chiller had no SN on it.

We then took the time to restart the PSL Beckhoff PC to unstick the frozen diode chiller channels.  According to Dave Barker these channels froze sometime on Saturday morning.  Fortunately the PSL interlocks are not tied to these channels, otherwise we would not have the PSL shutting down when the diode chiller shuts down (as we did yesterday).  Once restarted the channels appeared to be reading OK.  It is possible that these channels freezing for no reason can be used as an early warning sign of imminent chiller failure.  The chiller communicates with the PSL Beckhoff PC via a serial RS-232 interface and we have seen channels freeze when the cables are unplugged and plugged back in but the PC not restarted (which is expected behavior as RS-232 is not hot swappable), but this is the first time I've seen the chiller spontaneously loose communication with the PSL Beckhoff PC.  Jeff Bartlett is setting up a temporary Strip Tool on the PSL monitor in the control room that will monitor these channels.  If anyone sees that these are flatlined (there should always be some variation), please let someone on the PSL team (Peter King, Jeff Bartlett, Ed Merilh, Rick Savage, or myself) know immediately.  Thank you.

We then turned on the HPO, which came up with no problems.  We let it sit and run for a little while, then restarted the rest of the PSL.  As of now, everything is up an running.  We are going to continue to monitor over the next couple days to ensure that everything is working correctly.  The removed control panel will go back to Termotek with the chiller we are sending back and will be replaced as part of the service being done on that chiller.