Summary of H1's nice night.  (Almost 9hr lock with range going from 60 to 70Mpc).

• SEI:  Earthquake State tests on Fri., 
• SUS:  Nothing
• CDS:  Issues--0.5Hz comb still there---repower IO chasis with alt power supplies.  Test whitening chasis for 3rd filter bank.  Open Work Permits.  3IFO
• Software:  GDS software update tomorrow.
• PSL:  Mentioned issue from over weekend
• VAC:  CP4 at MY tomorrow, Kyle at EX for RGA, scroll maintenance at EY by Kyle.
• Facilities:  Issues with RO System, duct work at LSB receiving by Apollo

Discussion about running over before/after holiday break, O2 Break, operator 24/7 coverage.

Open Work Permit review.

Maintenance:  

• EY PCAL calib tomorrow (Travis)
• Flush TCS Chillers (Betsy)
• End station HEPI pump station swap (Hugh)
• Beckhoff work (Patrick)

Trouble with MODE17 (ITMX 15542 Hz) could be due to instability from large phase changes with slight frequency drift in our damping loop. Mechanical mode frequency at beginning of a cold lock sits around 15541.875 Hz and has drifted to 15541.95 Hz after about three hours. The previous bandpass filter carried ~40 deg phase change over that time. In an effort to fix this, I've made two BP filters that are shifted versions of one another to be turned on as the frequency migrates. The guardian uses the PLL frequency monitor to track the average frequency change of the mode peak and make the filter change switch at the appropriate time. Fall offs and notches in the filters are such that center of BP --> switching point ~10 deg. I've watched the guardian successfuly make this change.

I have moved IM2 and IM3 closer to their O1 alignment values, as indicated by Cheryl's alog 29948.  At the same time, I was walking the POP_A offsets to keep the jitter coupling low.  I had an excitation from 310-350Hz on IM3 yaw, but the effect it had on DARM didn't really change during this series of moves.  But, the other jitter/intensity peaks seem to have perhaps gotten a teeny bit better.  More significantly, this set of moves improved the carrier recycling gain as well as the 45 MHz sideband buildup in the SRC. 

IM2 and IM3 I only moved in yaw, however this made their pitch values also line up more closely with their O1 values.  IM2's witness sensors read (P: 608, Y: -209) while IM3's witness sensors read (P: 1954, Y: -32).  The POP_A offsets are currently (P: 0.39, Y: 0.47).  This gives a carrier recycling gain of 30.5. 

If the IFO is a struggle to lock tomorrow, trend the IM2 and IM3 witness sensors and put them back.  I'm leaving them in their new spots for tonight.

I also ran a2l.

We should check in the morning if these IM2 and IM3 positions help get us away from the REFL PD clipping that Sheila has been looking into.

IFO left undisturbed starting 08:20:00 utc.

Especially with the DRMI needing alignment help during most re-locks, I have created a new state to help check BS-only alignment.

Recall that if the DRMI flashes don't look so good, you can select the PRMI_Locked state that Sheila created some time ago.  This state will misalign the SRM and attempt to lock the power recycling cavity with the arms held off resonance. 

Sometimes though even these flashes aren't very good, and the PRMI isn't catching lock.  Now you can select the new state Check_MICH_Fringes in the ISC_LOCK guardian, and it will misalign the PRM.  This state is currently not set to try to lock MICH, so it'll never look quite like MICH_dark_locked from initial alignment.  But, you can watch the flashes on the AS air camera, and move the BS until they are as circularly symmetric as possible.  Note that sometimes you'll only see a few flashes per minute, so this requires a bit of patience, but it's often still faster than giving up and doing a full initial alignment.  Once the flashes on the AS air camera are circularly symmetric, re-select PRMI_locked.  This will realign the PRM, and go back to the usual locking sequence.

The PSL tripped around 21:37 UTC, it took us about an hour to recover from this . We called Jason and Peter, Jason called back and walked me through restarting it remotely.  I added about 200mL of water to the chiller, there was water on the floor in front of the chiller.  Jason confirmed that this is normal, and that the turbulence and bubbles in the chiller tube are from a known slow leak. 

Before restarting all the models on OAF, I accepted diffs on CAL CS, OAF, and SUS proc PI.  a screenshot is attached for PI.

There were two periods of unexplained motion of ITMY during undisturbed overnight lock on Sep 23. Both ISIs, plus all levels of the suspension (including oplevs) saw it, but there's nothing evident in the HEPI sensors or the ground.

These events made two periods of large noise in DARM (first plot), a few minutes apart, and a few minutes before lockloss due to PI. At that point, the PI didn't seem to be having any effect. The full Omega scan shows that ITMY has lots of anomalous motion. The second-stage ISI GS13s see a quick transient with rich structure (plots 2 and 3). The ST1 sensors see something similar but much less distinctly.

The L1 OSEM clearly sees a line below 1 Hz rung up for more than a minute afterward (plot 4).

I was not able to find anything on the ground sensors or HEPI that could have rung this up. I haven't looked as closely at the second event. I think this warrants more followup by someone familiar with the seismic isolation.

Kiwamu, Terra, Lisa

3 earthquakes, 2 user errors and 1 PI gave us the opportunity to extensively test our lock acquisition sequence today. 

(It works pretty well actually. The weakest part is the DRMI lock: the interferometer ends up always misaligned right after an unlock, and it requires manual adjustments all the times to get DRMI to lock. Once the DRMI locks, than the locking sequence rarely fails.)

Today we explored the (allegedly) jitter/intensity noise as function of interferometer alignment (SRM alignment, CSOFT/DSOFT and PRC1 offsets).

More details will follow, but the bottom line is that we have been able to increase the recycling gain (max 31, typically 28-29, with PRC1_Y offset= -0.06, CSOFT_P = +0.120), the cavity pole (360, typically 340), and minimize "jitter", but we have not been able to do everything at the same time.

All the noise tuning steps (including the now standard CO2X 240 mW power) are in the guardian, except the IMC WFS offsets. We also run  A2L.

We leave the interferometer locked with the SRM aligned by hand to minimizes jitter noise (ASC still open), with recycling gain 29 and cavity pole ~340 (as measured by CAL_CS_TDEP_F_C channel). The range is approaching 70 Mpc.

Observe intent bit set at 9:17 UTC, Sep 25. 

Modes 17 (15542 ETMX) and 25 (15541 ETMY) continue to give us trouble; about three hours into the lock Mode 17 will get high enough that Mode 25's PLL will jump to it, after which Mode 17 rings up quickly. Matt had set up a lower bandwidth loop in the PLL of these to help prevent this and yesterday I tightened it up even more. We've still lost lock the past two nights from these modes. To this end, I'm leaving Mode 25 in BYPASS with a 1Hz BP (still wider than I've seen it shift in frequency over many locks).  

Kiwamu, Nutsinee

We did a quick test with the HWS yesterday hoping it might fix the issue of HWSY sled reflected off the CP (alog29905). We first moved the ITMX and ITMY CP by a few hundred counts to confirm that only HWSY has sled reflection from CP. Then we swapped the X(790nm) sled and Y(840nm) sled then repeat the process. HWSY still had most of its reflection from the CP. The conclusion is, using different wavelength didn't matter.

We removed the HWS plates and stopped the code. This configuration still remained.

During this test we noticed that HWSX looks clipped. Not sure when did this started happening but Kiwamu said the data from HWSX he's been using make sense. No major misalignment to the SR3, ITMX, and BS in the past few days. A small touch to the top and bottom periscope fixed this clipping.

Josh, Andy

Summary: The ASC AS_C INMONs were overflowing on 9/23 but not 9/24. We're not sure if this has any negative consequences. 

During O1 we were asked to report any overflows that happened in analysis ready time. The summary page for overflows for 9/23 had a lot of entries but nearly all of them were at the lock loss. Of the handfull of things that overflowed for longer periods we looked at the ASC AS_C INMONs.

These overflowed the entire lock on 9/23 (like in fig 1) but were not overflowing in O1 (fig 2) and were not overflowing in the most recent lock on 9/24.
The histograms of the values for segs 2 and 4 are compressed around -32768 (though these are not integer counts and that value is exceeded) (fig 3).
We're not sure if this translates into problems for AS_C, but there is somewhat elevated noise in those channels now compared to O1 (fig 4,5) and those channels are used for ASC SRC2 which in turn has ~5-10Hz coherence with SRCL (fig 6).
But AS_C channels have not much coherence with DARM (fig 7).  

We thought it was worth reporting even if there isn't an obviously bad consequence. 

Title:  09/23/2016, Evening Shift 23:00 – 07:00 (16:00 - 00:00) All times in UTC (PT)
State of H1: IFO is locked at DC_READOUT. Environmental conditions are not that favorable. Winds are a Fresh Breeze with gusts to Near Gale (19-24 base, gusts to mid-30s). Seismic activity is elevated but still below 0.5um/s, microseism is also elevated and getting worse due to a mag 6.3 EQ in the Philippines. Set ISI-Config set to EARTH_QUAKE_V2.            
Commissioning: The commissioning team is working feverishly ahead of projected arrival of the EQ. 
Outgoing Operator: TJ
 
Activity Log: All Times in UTC (PT)

23:00 (16:00) Start of shift
23:10 (16:10) Kyle – Back from Mid-Y
23:41 (16:41) Lockloss – Mag 6.3 EQ near the Philippines 
23:45 (16:45) Nutsinee – LVEA to adjust HWSX alignment
23:49 (16:49) Keita – Going into the LVEA
00:02 (17:02) Keita – Out of the LVEA
00:04 (17:04) Kiwamu – Tour in the LVEA
00:11 (17:11) Nutsinee – Out of the LVEA
00:30 (17:30) Kiwamu – Out of the LVEA
04:08 (21:08) Relocked at NOMINAL_LOW_NOISE with 51.0W & 53.2Mpc	
04:30 (21:30) Set Intent Bit to Observation
04:52 (21:52) Lockloss – Mag 5.8 EQ near New Zealand
05:25 (22:25) ETMX – RMS WD tripped - Reset
05:26 (22:26) HAM6 – SUS & ISI WD tripped – Reset
06:25 (23:25) Locked at NOMINAL_LOW_NOISE	
06:26 (23:06) Intent Bit Set to Observing
06:30 (23:30) Ending Shift 


Title: 09/23/2006, Evening Shift 23:00 – 07:00 (16:00 – 00:00) All times in UTC (PT)
Support:  Kiwamu, Sheila,         
Incoming Operator: N/A

Shift Detail Summary: It was a struggle to relock the IFO after the Philippines earthquake. With much assistance and perseverance, were able to relock and eventually take the IFO to NOMINAL_LOW_NOISE. The environmental conditions are good. Wind is no more than a Light Breeze (max 7mph), Microseism is centered around 0.08um/s. However, seismic started to ring up due to a Mag5.2 EQ near New Zealand, which eventually broke lock. Was able to switch the ISI to Eaeth_Quake_V3 before Lockloss, but not soon enough to prevent the Lockloss. 
  
The New Zealand EQ was followed by back to back Mag4.9 & Mag4.7 earthquakes near the Reykjanes Ridge. Seismic recovered in about an hour. Much trouble relocking, and Roll Modes still a bit elevated. Finally, able to get to NOMINAL_LOW_NOISE with Intent Bit set to Observing. Will take a small success and call it a night before another earthquake comes along to break the lock.   	   	 

Not much progress has been made toward understanding the ITM charge mystery of aLOG 29699 and earlier. I tried to get quad-specific charge information before the earthquake hit tonight, but I found the data had insufficient SNR at my excitation amplitude.

To measure effective bias voltage of an ITM, read /ligo/home/chris.whittle/Documents/ITM_CHARGE_README.txt, set appropriate excitation amplitude/frequency and run /ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/Scripts/ESD_TM_charge.py as (for example)

python ESD_TM_charge.py -l -m -o ITMX

(further instructions in the readme).

To perform a swept sine measurement, set the bias voltage to your desired value, then open the DTT template at /ligo/home/chris.whittle/Documents/charge/itm_charge_sweep_sine. You will have to set an envelope for the excitation frequencies. Previously, /ligo/home/chris.whittle/Documents/charge/analyse_sweep.py was used to calibrate and re-plot this data (requires transfer functions and coherences from charge measurement and pcal measurement).

Jeff K, Sheila, Chris Whittle

Having recently taken measurements for the CARM and IMC loops with the newly installed 200 kHz pole (aLOG 29735), we have begun an investigation into whether we can boost the gain in CARM to help mitigate frequency noise in DARM without compromising loop stability. We used the following form of the CARM open loop gain:

G_CARM ~= g_CARM * H * ( g_IMC * G_IMC / (1 - g_IMC * G_IMC) )

where g_IMC and g_CARM are tweaked, and G_CARM and G_IMC were measured (see above). H is a combination of the electro-optical CARM plant of the IFO and the electro-optical IMC plant, and is calculated from the above measurements. We are ignoring the slow path here as we are far above the 30 Hz crossover. See aLOG 22188 for more details.

Note that the closed loop gain of the IMC was extrapolated back to 1 kHz from 10 kHz (assuming a unity CLG below 10 kHz).

The OLG of the IMC loop shows that we can't get away with an IMC gain much grater than 2 dB without hurting our phase margin too much. Similarly, the loop suppression of the IMC loop significant gain peaking above 2 dB.

With g_IMC = 2 dB, our CARM phase margin suffers above g_CARM = 2 dB. This gives us a a factor of 2.08 dB suppression in our CARM loop suppression. We therefore propose increasing CARM and IMC loop gains to g_CARM = 2 dB and g_IMC = 2 dB. Although this introduces some additional UGFs, all are stable, and the worst of which has a phase margin of 31.6​​^∘​.

The script for producing these plots can be found at: