POP90 still jumped during Noise Tuning but I haven't seen a jump during NLN.

We have been struggling to lock all day today.  

I think the root of the problem is that our alingment references are not giving us a good power recycling gain after inital alingment.  The soft loops bring us back to a good alignment, but it seems like our references for the green arms are off and may need to be reset in DC readout.  This means that we have had a lot of random locklosses durring the CARM offset reduction, especially durring the analog CARM transition.  We have added some extra sleeps here, since we have had more sucsess doing this step by hand.  

I zeroed the pit offset in POP A, because looking at the last 2 weeks of algnment, no pit offset gave us the best ranges, and the recycling gain was a bit better than the current -0.2 offset.  This hasn't improved the recycling gain when we first lock much, but it does reduce the amount that the recycling gain drops when we engage CHARD, which has caused a few of our locklosses today.  

We also had some bugs in the SRM_ASC high power state, which Kiwamu and I changed earlier today for the new SRM dither loop.  For now I have commented out the line where it sets the gain, this morning we used a gain of -100 if anyone wants to try turning it on by hand later. 

I think that the next step might be to lock at the alignment references (next time we reach DC readout) but don't want to start changing references now, so we will leave it for tonight.  

I've scheduled 9 burst injections to be injected coherently into both IFOs. They will begin at 10:10 UTC (2:10 PT) and are spaced 20 minutes apart. The IFO will need to be in observation mode for these injections to go in. Here are the relevant lines in the schedule file.

1164276617 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-c_9_0.2.txt

1164277817 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-c_13_0.6.txt

1164279017 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-c_20_0.99.txt

1164280217 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-e_12_0.4.txt

1164281417 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-e_16_0.9.txt

1164282617 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-e_20_0.9.txt

1164283817 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_ShortDuration/SG_4.0e-22_8.9_70.txt

1164285017 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_ShortDuration/SG_2.0e-22_8.9_153.txt

1164286217 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_ShortDuration/SG_2.0e-22_8.9_285.txt

The waveforms are on the hardware injection svn. The schedule file gives the path to the text files from the Details directory.

For some reason a +50 degree filter was turned on in the ETMY top mass damping on October 12th, it was not good and we got no real top mass damping. Nutsinee and I just turned it off, so the settings are now the same as for ETMX.  This fixed the problem

TITLE: 11/27 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Nutsinee
SHIFT SUMMARY: There was one nice 2hr lock during my shift, but other than that we have been struggling to find what has been causing us to drop during various parts of acquisition. Not sure if this is some remnant of the Beckhoff problems from earlier, but we have only been locked once since then. We have gone through one initial alignment, numerous DRMIs, and some DC Readouts. Sheila is working hard and has some theories about the recycling gain, I'm sure there will be an update when there is more news. PEM is done for the night.
LOG:

• 01:05 Sheila heading into the LVEA to take a quick measurement of the IMC UGF in the hopes to help solve our locking woes.
• 01:18 Sheila back
• 01:56 NLN. Kiwamu and Sheila have been watching and investigating the POP90 bump issue, we just got here but will sit tight while they check a few more things.
• 02:00 LLO called to double check that we are also missing the last 20hours of their range on SENSMON. We were.
• 02:49 Running the 3 a2l scripts by commissioner request.
• 03:09 All a2ls done.
• 03:45 Lockloss. PEM crew seems to be the cause.

Commissioners and the PEM crew are working when we have the IFO up, but we have had a few unknown issues causing locklosses in some of the states after DRMI making it take a bit longer to get there. Currently working to get back up to resume PEM work.

Sheila, Kiwamu

Since last wensday, we have had several sudden changes in SRC alingment that started in the middle of the week and have continued (31865  31849 31844 31823)   We don't know what causes this, but it only shows up in the alignment of SRM and SR2, (as well as the OMs and OMC) and it seems to be a pitch problem. 

One likely suspect is the AS36I sensing, allthough we don't have any reason to suspect it changed mid week.  We decided to try running a dither loop on SRM pitch for a few days as a test.  We changed the demodulated signal to SRCL control, which has a higher SNR than any of the build ups.  We reduce the amplitude of the dither line from 600 counts on the clock gain to 100 counts, use a gain of -100 and no 60dB filter (FM1).  We set the lock point of this loop by adjusting the P2L gain in SRM M3, which we set to -1.3 for now to get the best build ups.  

We are hoping to see if problems continue in the next few days with this on, or if there are jumps in the AS36 I signals.   We have added it to guardian but this is not tested yet. 

CDS: The python nds2 client that the script uses could not get data today and yesterday.

FAMIS#:4703

Since the script was not working, I had to do this the old fashioned way. I'm glad this was made into a script!

ITMX P, ETMY P are getting close to out of bounds, but other than that it all looks good.

Sheila, Kiwamu,

This is a follow up of the latest AS90 jump incident reported in 31844.

We think this anomalous behaviour started in this past Wednesday (31804). This time, we looked into some other signals and found elevated noise in SRCL, although we are still unable to localize the issue.

[Time line]

• 5:45 UTC, fully locked
• 6:02 UTC, data evaluation point #1
• 6:17 UTC, AS90 jumped and increased
• 6:30 UTC, data evaluation point #2
• 7:10 UTC, TJ manually disabled SRC1 and steered SRM to a good alignment
• 7:30 UTC, data evaluation point #3
• 9:12 UTC, another manual SRM tweek by Nutsinee

[Some observations]

The symptom is very similar to what was reported in 31804. The POP 90 increased from 13 cnts to 16 cnts. Since the AS diverter was closed, it is hard to say whether there is a jump in AS90 or not. The jump also seems to have caused misalignment in SRC1 as was the case in 31804. The first attachment is trend of some relevant signals. The leftmost vertical line in each column represents the time when the POP90 jumped. The second vertical line represents the time when TJ opened the SRC1 loop and did manual alignment. Similarly to 31804, the POP90 became noisier after the jump. The LO signals in AS36 WFSs didn't show any obvious glitch or abrupt change.

This time we looked at the spectra of the AS A 36 signals and the SRCL error signal. See the second attachment. In each panel, the blue curve is taken before the jump or at evaluation point #1 (see the above list). The green curve is taken right after the jump or at evaluation point #2. Finally the red curve is taken after TJ's fix or at evaluation point #3. I was hoping to see an obvious change in the spectra that might indicate some electronics issue, but the AS 36 signals didn't really show an obvious change as far as the spectra are concerned. However, on the other hand, we found a difference in the SRCL length error signal although this is not easy to interpret. Right after the jump the SRCL noise increased in 3 - 30 Hz by roughly a factor of two. This cannot be explained by the change in the optical gain beucase the increased POP90 should mean a lower optical gain for seinsing SRCL. Another explanation might be a worse A2L coupling contaminating SRCL due to the different spot positions on the SR mirrors.

I was curious to see how the BRSX was doing, so attached is a quick 5 day trend. It seems that it may be slowly ringing down after Jim vistied on Thursday.

TITLE: 11/27 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
    Wind: 4mph Gusts, 3mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.36 μm/s
QUICK SUMMARY: On our way back up after some issues described in the log below mine.
 

TITLE: 11/26 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
LOG:

17:50 Kyle on site checking pumps.

18:01 Patrick to CER

18:05 Robert to EY

19:50 Robert and AnnaMaria to put beam dump in MC Refl, Patrick to CER taking top off of Beckhoff module.

20:30 ECat chassis is fixed.  Start relocking.

23:50 PCal X 5001.3 Hz line turned off.

At the request of Adam Mullavey (via a phone call from Rick), I have turned off the 5001.3Hz PCal line at EndX for some injection work.  I did this by zeroing the amplitude of the line, leaving all other parameters unchanged.  See attached screenshot for setting before I changed them.

In a later email forwarded by Rick, Shivaraj mentions having to change Guardian code to keep these lines off at LLO.  I'm unaware of any such PCal Guardian code at LHO (my guess is that this is due to the fact that LHO doesn't use PCal for locking like LLO does), so made no changes to Guardian.  If someone reading this knows otherwise, please contact myself and the current operator.

We are just starting to do initial alignment after the Beckhoff issue was resolved by Patrick and Richard.  So far, so good.

It appears the problem is either with ISC Common L20, ISC Common M0, or the link between (see attached screenshots). I will go out to the CER and take a look.

TITLE: 11/26 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC

STATE of H1: Unknown

INCOMING OPERATOR: Travis

SHIFT SUMMARY: H1 stayed locked most of the shift. Now I'm running into an issue I've never dealt with before. See alog31847 for details. This alog has disappeared magically. See alog31850 (comment below) for details.

LOG:

9:05 Noticed range slowly dropping, out of Observe to adjust SRM P

9:08 Back to Observe

9:12 Noticed that I made it worse, back to commissioning to move SRM P the other way round.

9:16 back to Observe.

13:39 Lockloss

14:24 THE confusing lockloss. Below I copied some of the Verbal Alarm message that might be useful in giving people insight of what's going on. It would be useful to know how long does the code take to loop though all the status of things.

          14:23:16 VIOLIN_MODE_DAMPING2

          14:23:28 TCS CO2 lasers tripped

          14:23:24 ISI HAM6 WD tripped

          14:23:48 ETMX ISI ST1 WD tripped

          14:23:48 ETMX ISI ST2 WD tripped.

          14:24:01 DOWN