J. Kissel 

The message: I tried to improve the Bounce mode damping, I've installed some new filters; no change in the amount of damping for the bounce modes, and they haven't been cooled any more than when I got started. I've made no changes the guardian code, so in the next lock stretch my work will be erased / cleaned up (except for the new filters), and what used to be turned on turned on before today will be turned on again.

After spending an hour or so trying to get better results out of the installed bounce mode damping filters to no avail, I tried installing much more narrow band-pass filters. I did this because of Shiela's entry (LHO aLOG 18440) seemed to indicate we know the frequencies really well, and I could see what I thought was ETMX at 9.77 [Hz] interacting with what I thought was ITMX at 9.83 [Hz]. However, I found after exploring the parameter space (with gains and +/- 30 or 60 [deg] filters) with the more narrow filters, the situation got more confusing because the top mass of ETMY, ETMX, and ITMX would come in and out of showing 9.83 [Hz]. See for example the attached .pdf of the top mass vertical OSEMs for each. Yuck! After a while I convinced myself that having both IX and EX using the narrow band bp9.7-9.8 (in FM10 of IX and FM5 in EX) with a small gain of +0.1 and +0.05 and their normal -60 [deg] and +60 [deg] filters wasn't making it worse, but I couldn't get any improvement.

This mode interaction are stable / non-existent at low power, but as soon as we elevate to 23 [W], the MICH oscillation creeps in mentioned earlier today (LHO aLOG 18478) creeps in and breaks the lock.

J. Kissel

I've processed the DARM OLG TFs from Thursday (see 18443), and found that the DARM Coupled Cavity Pole Frequency seems relatively stable at 350 +/- 10 [Hz] with respect to IFO power. Admittedly, the data at 23 [W] is only over a small frequency range and is varying by ~5% (even though, as usual, I applied at 0.99% coherence threshold cut on the data points), so that's why I put a +/- 10 [Hz] on the number I quote. I think we'll either have to (a) get more DARM sweeps, (b) use Kiwamu's LSC DCCP tracker, and/or (b) get the PCAL demodulation up and running to check it this is consistent from lock-stretch to lock stretch.

The ITMs are under control for all of these data sets, and the SRC1 yaw loop is tuned as described in LHO aLOG 18442 for the latter three. For all four measurements SRCL to DARM subtraction, ("FF") was off.

IFO back up; bounce mode looks better (maybe a slightly different alignment?); 2.5 [kHz] violin harmonic is still quite rung up. 

Turns out our DMT session had just frozen on the wall -- the IFO has been locking itself for the past 8 hours!! The lock stretches have only been ~1/2 hours long though, I'll see if its these poorly damped modes.

Robert has joined the party, and he plans to do injections later in the morning, but for now I've checked the undisturbed bit at 2015 May 16 16:10:00 UTC.

J. Kissel

I came in ~10 minutes ago, and found that the IFO had just finished getting to low noise, in the LSC_FF state. ITMX's highest vertical (bounce) mode and the 4th harmonic (2.5 [kHz]) of somebody's violin mode are very rung up, but the IFO appears to be stable(-ish). I briefly turned on the undisturbed bit, but when I noticed that DMT wasn't computing the inspiral range, I found there was a state above LSC_FF, "NOISE_TUNINGS" so I've turned off the undisturbed bit, changed the nominal state to NOISE_TUNINGS, and went for it (since all it appeared to do was turn on a SRCL offset). This broke the lock after a minute or so. Hurumph.

I've now changed the nominal state back to LSC_FF, and I'm gunna leave it there is time. Once it gets back up (hopefully), I'll reengage the undisturbed bit.

J. Kissel, for B. Lantz and J. Harms

There's been some interesting discussions on the DetChar mailing list about seasonal variation of ground motion around the world's network of gravitational wave observatories. Two things (of many) that have come out of it that might be of particular interest to LHO:
- Jan Harm's data set from 2009/2010 T1500224, showing what I'm calling "meta" ASDs showing the percentile ASDs for each month over a year. 
- Brian Lantz has used that data, shown it in a slightly different way which can be found in SEI aLOG 766.

More data is to come. 

Why do we care? It's merely to call attention to the fact that for the active isolation feed-back,
(a) We shouldn't expect a "one (blend filter / sensor correction) filter fixes all" solution for both LHO and LLO.
(b) Seasonal variations of the secondary microseismic may explain why we've needed to work harder at the microseism this past winter (i.e. use the 45 [mHz] DeRosa, LLO blend) and now we're doing just fine with a 90 [mHz] blend everywhere.

Dan, Keita, Stefan

- Updated the OMC model with correct math and enough monitor points to be useful.
- We tried commissioning the model sitting off fringe at 23W, but confused ourself a bit. Everything started to make sense when Keita pointed out that we have a fringe offset when sitting at zero digital offset, which manifests itself as different OMC trans DC power levels on the left and right side of the fringe.

- With the nominal 1e-5 DARM ERR counts offset (about 14pm), we observed 18mAmp, while -1e-5 gives 15mAmp. Thus we have about 0.6pm fringe offset when the RF length signal is zeroed.

- With that we laid out the strategy for setting up the parameters:
 0) Set H1:OMC-READOUT_SIMPLE_GAIN to 0 (Turns off simple path.)
 1) Estimate the minimum power at zero DARM offset to get a number for the contrast defect. It turns out this is close to 0, so 0 will do.
 2) Pick the transition point. In our case 14pm. Thus set both XF (fringe length) and X0 (fringe offset) to 0.
 3) Adjust H1:OMC-READOUT_PREF_OFFSET until H1:OMC-READOUT_STEP2 is equal to one on average. (H1:OMC-READOUT_STEP2 is the power normalized by the power at the transition point.)
 4) Set H1:OMC-READOUT_X0OFFSET_GAIN to 1 now the .H1:OMC-READOUT_ERR_INMON signal is zero on average.
 5) Use H1:OMC-READOUT_ERR_GAIN to match the gains in the RF sensor (H1:LSC-DARM_IN1) and the OMC path (H1:OMC-READOUT_ERR_OUT).
 6) Set H1:LSC-OMC_DC_OFFSET to minus the H1:LSC-DARM_OFFSET. Now the offsets are matched.
 7) Transition the input matrix.
 8) Ramp H1:LSC-OMC_DC_OFFSET and H1:LSC-DARM_OFFSET to 0 (at the same time)

- We had high winds for about two hours. But after that successfully tested the script that follows this logic.

Over the lock period last night, the CPS ASD appears to experience changes as time passes.

Just to focus on the BS, the ST2 Vertical between 1 and 5 hz see the largest variation.  See the two attached images, the lower right panel is the ST2 Vertical.  The lighter thicker colors are references before the CPS timing change on Tuesday.  The finer darker traces are current running.  I've look at the ITMY & ITMX too over the few hours of the lock loast night, and at some time or another, all the traces are at or below the reference, suggesting the CPS are okay.

Scott L. Ed P. Chris S. Cris M.(1/2 day)

5/14/15
Finished crevice cleaning and removed lights. Test results posted here. Hang lights in next section north, vacuum support tubes and spray bleach/water solution. Cleaned 49 meters ending 8.4 meters north of HNW-4-048.

5/15/15
Cleaned 73 meters today ending at HNW-4-052. Test results posted here.

Tube pressures are continually monitored by control room operator during cleaning operations.  

Total tube cleaned to date is 3024 meters.

Just posting data that Fabrice had requested for a talk. The setup: I wanted to measure the performance of sensor correction on ETMX. I turned off the feed forward (which I've seen add some noise at .5hz, not much, but I've been meaning to investigate) and got .001 bw measurments with the sensor correction on and off. The ISI was fully isolated, with 45mhz blends in Y and 90mhz blends in X. On the first 3 spectra (X,Y &Z) black (ground),orange(st1 t240's) and red(st2 gs13's) are sensor correction on, brown (ground), blue (st1 t240's) and grey (st2 gs13's) are sensor correction off. In X&Y, we are using Ryan's .5hz notch sensor correction on the ISI and in Z we are using RichM's broadband low frequency sensor correction on hepi (fourth & fifth plots).

Brute Force coherence report is available here for last night lock:

https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_1115716006/

Some highlights, which I find very interesting:

• What's going on with CARM, why is there coherence of basically 1 below 20 Hz? (fig. 1)
• There is coherence at the same peaks, and a bit at all frequencies with AS_A_DC_SUM: is it intensity noise? (fig. 2) This seems to be confirmed by the coherence with IM4_TRANS and ISS signals (fig. 6)
• SRCL is still a good channel to have coherence below 80 Hz. (fig. 3)
• AS_A_RF_45_Q_PIT has large coherence below 20-30 Hz, maybe we are limited by angular noise? Do we need a better balacing or centering of the ETMs? (fig. 4)
• At 17 Hz there is a small bump/line that is coherent with HPI-HAM1_BLND_L4C_HP_IN1 (fig. 5)
• Coherence with the PSL periscope is much smaller than in the past (fig. 7). However, there is still some significant coherence with IMC WFS at 200-400 Hz (fig. 8), so we're probably still suffering of some contamination due to beam jitter

Not much is happening at higher frequency, at least for broad band coherence. However there are a lot of single frequency bins with significant coherence, and I can't list all of them here (I'm too lazy). So look into the table at your favorite line frequency, you might be rewarded with some coherence.

I spent a bit of time this morning clearing out remaining SDF diffs in SUS, LSC, and ASC.  This involved the usual alog hunt followed by some clarifications from commissioners.  Things still showing diffs at the moment and why:

- We need to capture a new snap file for the OMC due to yesterday's model change which will clear out it's large SDF diff list. 

- The ASCIMC still has one diff due to a 10e-17 size change in one value.  I think this feature is due for an upgrade at some point, so until then, this 1 diff will be lingering.

- Same with ISCEX - there are 2 diffs with very small diffs which won't go away with the accept button.  Will linger until update.

- We need some assistance with clearing the PSL diffs from team PSL.

- I've not paid much attention to the bottom monitors, namely ODC and CAL.

Sheila, Evan, Stefan


- Reduced the whitening gain on both AS 36 ASC diodes. The new value is 24dB. We increase the input matrix values from 1 to 2 to compensate (for MICH and SRC1, i.e. the SRM loop).
- We tried to phase the AS_A_36 quadrants by wiggling SRM in yaw and pitch, maximizing the I signal. Not sure how meaningful that was though, because the actual signal we ended up using was Q.
- We switched the the sensor for SRC1_YAW (SRM) to 0.3*AS_A_36_Q + 0.3*AS_B_36I. This signal clearly reacted to our mysterious SRC cavity drifts, and had zero offset at the good locking point.
- We increased the power to 23W. This is the maximum power currently available. With this new SRM yaw sensor the 23W was very stable.
- The DARM offset was 14pm (or 1e-5 cts).
- This gave us a recycling gain of 38.
- Measured the open loop gain and verified the calibration.
- This configuration was stable for 1h.
- We took SRCL noise injections at: 8:46:15UTC and 8:59:40UTC (SRCL cut-off filter off and on)
- We took MICH noise injections at: 8:52:15UTC and 8:55:40UTC (SRCL cut-off filter on and off)
- Pushed the intent bit at 9:06:30 UTC.

- The inspiral range seems quite remarkably flat at 57 Mpc. A stron indication that we are now purley electronics noise limited at low frequencies.

To do tomorrow:
- Explore DARM offset: the new OMC code is ready to install, and will allow on-the-fly OMC offset tuning.
- Add the new ASC INMATRIX to Guardian.
- Add the new DARM offset to Guardian.
- Generate noise budget.