Before driving in this morning, I checked the H1 Summary Page.  This page has been down for almost a day (L1's Summary Page appears to be fine).  

• I sent an email to the LHO CDS Admin group (not sure they are responsible for this page though).  
• On the H1 Summary Page, there is a "Report An Issue" link on there.  After a few minutes, I received the email verification (but it did not like my ligo-wa.caltech.edu, so I added my ligo.org email & then it worked).  I have reported the issue (I was wondering if there is someone we should email about issues with this page as well...or is the "Report An Issue" link best?)

TITLE: 11/05 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 68.4202Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    Wind: 7mph Gusts, 3mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.67 μm/s
QUICK SUMMARY:

TJ handed over a nicely locked & steady H1 (flat and only 1 visible glitch on the range); been Undisturbed for last ~7.5hrs (the Observatory Mode was set to Locked, but I set it to Observing.)

Other Notes:

Robert is here and would like to do PEM Injections with a locked H1.

Bubba is on-site to search for possible leak in the water system.

H1 Summary Page down (making separate alog).

useism is high (~0.6um/s).  But our handy SEI CONFIG says we are good at the WINDY state (until we get up to 1.0um/s).  Staying put.

TITLE: 11/05 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Aquisition
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Lost lock as I sat down, the ITMY swinging happened to me as well. Misaligning and aligning didn't seem to help, but it eventually damped on its own. Then went up to Coil Drivers before it lost it again, but brought it back to NLN and it has been sitting there since with the intent bit Observing. I was planning on doing some tasks for commissioners but couldn't connect to the oscope, and I didnt want to go into the LVEA to disturb the lock. I will try these tomorrow.

LOG:

• 08:34 Observing
• 10:02 GRB

Up and observing for a bit while it looks like livingston is about to be up, then I'll drop the intent bit to do some tasks from commissioners.

TITLE: 11/05 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Aligning
INCOMING OPERATOR: TJ
SHIFT SUMMARY:  IFO has been up and down all night for various reasons.  After 2 of the 4 locklosses, ITMy swung around for a long time, slowing relocking.  Stefan looked for the cause but was unable to find one.  Also, the ASAIR and POPAIR signals have been oscillating during full lock.  Matt and Stefan are looking into the cause of this, but as of the end of my shift have not come to a conclusion.  I ran A2L for 2.5 of the locks, the 0.5 being that I was halfway through the 2nd script when we lost lock.  Stefan said that it was useless to run A2L with the AS and POP oscillations, so I haven't run it for the last lock.  Microseism is still above the 90%ile level.  Wind is calm.  Locked at ~70MPc.
LOG:

23:59 Updated LSC and ASC SDF OBSERVE.snap files per Hugh's request.  If the Owl shift operator has a lockloss, he'd like to update the LSC and ASC DOWN.snaps as well.
 

Evan, Stefan, Matt (writing)

We've been seeing for a few days the bouncing of the harmonics of the 1kHz violins (exact harmonics, not higher violin modes).  Watching these on a fast spectrum shows an ~18s period, in which the harmonics appear out of the noise and grow by more than a factor of 10 as the beating at 1kHz reaches a maximum.  The 1kHz peak (in which the violin modes are unresolved) is only changing by a factor of about 5 (see attached).

We noticed that the sidebands buildups started to oscillate at the microseism once we switched to low-noise (lower ASC bandwidth ?). We suspect something with ITMY or its suspension is mistuned, because it would hardly damp after4 lock-loss. Not sure whether it is related.

Stefan, Kiwamu, Matt

To test the theory that the ILS is gain limited, and that more gain might help with DARM noise, we measured the loop and used the TF input to add some gain at low frequency.

The open-loop TF was as previously reported (see 31121 and photos to follow).  We had computed that an SR560 with a gain of 10 and a pole at 100Hz accompanied by a 10kHz passive low-pass would make for a good test without destabilizing the loop (see attachment 1).  With this test-rig attached the TFB and TFIN ports on the ILS front panel (photos to follow), we relocked the IFO and found that the coherence with DARM had been reduced as expected (see attachment 2).  Noteabley the PMC HV signal was significantly reduced (black to brown in attachment 2), indicating that this gain was preventing noise in the PMC.  Unfortunately, this simple test was not able to apply much gain to the 1kHz, where the highest coherence with DARM is seen.

Kiwamu has offered to investigate the possibility of using a new CDS FE running at 65kHz to implement a tailored gain profile which will suppress the 1kHz peak and other HPO features while keeping the ILS loop stable.

Sheila, Matt

We wanted to see if there was anything interesting in the voltage between the ESD cable grounds and the chamber grounds (similar to tests done at LLO), so we installed a couple of SR560s which we clipped to the ESD grounds and the chambers at both end stations.  The SR560s have a gain of 1000 and a LP at 10kHz.

A little coherence with DARM is seen around 280Hz and 140Hz (see image).  Robert says that these are likely to be due to fans.

These SR560s can be recovered whenever someone is next at the end stations (we don't  want to disturb the BRSs at the moment).

[Sheila, Jenne]

We were interested to see if the scatter peaks could be significantly reduced by moving the IMC WFS offsets, and if they're repeatable lock-to-lock.  Sheila moved DOF1_P to +350 counts and DOF2_P to -100 counts.  The DOF1 move was significant, but the DOF2 and DOF3 moves that we tried weren't.  We advocate leaving in the DOF1 offset, but not bother with the other two.  In the attached screenshot, yellow is Sheila's reference from before changing offsets, and purple is with the offsets.  The spectrum looked pretty much the same with and without the DOF2 offset, but this spectrum had it in.  We note that the IMC trans power went down a bit with the DOF1 offset and the IMC REFL camera looked pretty non-symmetric, so maybe this isn't so ideal, but the recycling gain went up and some peaks went down.

In the attached spectra, the rectangle noise between 410-440 Hz is an injection on the input pointing PZT.  Sheila's offsets improved this by not quite a factor of 2.  The improvement at the 260Hz peak is a little over exaggerated - it was bouncing up and down and we happen to have caught it at a relatively low point.

I started trying the yaw offsets, but broke the lock.  For the next person who tries this, I had gone to -350 in DOF1 yaw.  -300 was stable, but we lost lock shortly after I went to -350.  I think negative was the wrong direction, although I wasn't seeing all that much effect.  It seems like it's worth trying this some more, although if the peaks are gone after Matt's efforts tonight on the PSL ILS loop then maybe it's not so critical. 

As was brought up at this afternoon's commissioning meeting, I have computed the test mass spot positions over the last year. T(0) on the plot is 10-Oct-2015, the date of the first A2L measurement that I have data for.  The data through the end of O1 has been seen before, but I haven't looked at it since then.  The spots have been moving a whole lot, so probably I should be better about updating these plots more often.

The 3 attached plots all show the same data, but with differing amounts of extra info.  The dots are the spot positions, and the magenta horizontal line is the average position of all the measurements taken through O1. 

The second plot adds to this a series of vertical lines of notable events, either for the IFO or for the alignment.  The third plot is the same, but zoomed in to the last 75 days. 

The lines are from the following "events":

1. 2015-09-15 00:00:00 (start of O1)
2. 2016-01-19 00:00:00 (end of O1)
3. 2016-04-02 00:00:00 (no HPO, but after HAM1 grouting work and subsequent realignment)
4. 2016-05-17 00:00:00 (first lock with the HPO)
5. 2016-07-11 00:00:00 (ER9 end)
6. 2016-07-16 00:00:00 (Good July spectrum from Sheila's G1602240)
7. 2016-09-02 00:00:00 (Big POP_A offset move, resetting of initial alignment setpoints, to improve 50W recycling gain)
8. 2016-09-26 00:00:00 (Moved IMs closer to their O1 OSEM values, trying to keep rest of IFO alignment roughly constant)
9. 2016-10-08 00:00:00 (Bad October spectrum from Sheila's G1602240)
10. 2016-10-13 00:00:00 (Moved POP_A and SOFT offsets again to improve 50W recycling gain more)
11. 2016-10-23 05:25:00 (TCS and alignment settings back to July values)
12. 2016-10-27 05:00:00 (Alignment recovery after PSL shift - IM3 now close to actuation edge)

You can see that after #7 many of our spot positions moved pretty significantly, although they continued to move after event 7 and I just didn't find / remember an event to explain this specifically.  But, we'd been doing lots of alignment searching during that time.  Also, after #11 when we went back to our July TCS and alignment values our spot positions largely went back to where they were before the big POP_A move.  We could try more to get closer to the O1 spots, and that may be somewhat helpful.  Food for thought.

The Hartman codes for both ITMs had been off for some days in order to upgrade the computer to Ubuntu 14. The new codes, which are written in python, were started at around 21:40 UTC today. No major issues so far. We did not check the Hartman beam alignment with respect to the cameras yet.

As Sheila pointed out, back in May we had a 25W lock that lasted >5h and never showed any indication of jitter peaks.

The attached plot 1 shows spectra from May 17 (25W), July 16 (40W) and Nov 3 (25W). Note that the May 17 spectrum is taken 4h into the lock.

Plot 2 shows inputy power and range of the May 17 lock.

Plot 3 shows all TCS settings of the May lock.

Plot 4 shows all TCS settings currently used.

Based on this, I would like to turn off the ITM ring heaters.

The HPO length locking servo is gain limited, and the error signal has coherence with down-stream sensors, including DARM.  Decreasing the ILS gain increases the coherence with DARM at several peaks above 200Hz (see attached).  We can't increase the gain much with the current servo shape (see 31121, servo board here), but a small gain increase reduces the coherence with DARM.

In the image: BLUE is low gain (servo gain 3.0 V), GREEN is nominal gain (servo gain 1.0 V), RED is max gain (servo gain 0.0 V)