Following on from Sheila's alog 77427, checked on VAC trends and OFI temperature around April 22nd.

I checked (maybe a repeat of someone else) that there were no vacuum spikes during the locks when Kappa_C dropped or the locklosses afterwards. Plot of Kappa_ C with VAC channels attached.

Looking at the OFI TEC readbacks during that time, they were significantly noisier than usual during Tuesday maintenance after the 5% optical gain drop, before out alignment shift.  Noisy between 6:30am and 4pm. This is before any Tuesday maintenance 77363 or injections start. Plot attached, including zoom out and zoom in. It also happened the May 28th to May 30th.

TITLE: 06/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Locked most of the shift then a lockloss with a suspicious ETMX signal  just before lockloss ended a 18 hour lock. We just got back to low noise again.

Relocking:

DRMI, PRMI, and MICH wouldn't lock with poor alignment, so I ran an initial alignment, all automatic. After initial alignment it went up to PREP_DC_READOUT_TRANSITION and then ran into the same issue Tony saw last night (alog78383). Ryan and I discussed a way to fix this in ISC_LOCK and he will make a change to remove ISC_LOCK's requesting of OMC_LOCK to Down too early.

LOG:

• 2134 Lock loss ending a 18 hour lock
• 2328 Observing

Over the last week, we had a locking difficulty that started last Tuesday (shown roughly by the first vertical line in the attached screenshot), and caused poor range with high ASC and LSC noise, as well as locking difficulty in DRMI and when engaging the DARM offset. This has been largely solved over the weekend by adjusting triggering in DRMI(), and introducing offsets into the AS72 WFS, which control the alignment of SRM (78382). 

We attempted to move the beam in the OFI starting on Thursday, 78290, this resulted in pressure spikes that Dave and Gerardo alerted us to on Friday evening.   On Friday morning we reverted these alignment changes.

The attached screenshot shows that the PRG and arm powers are the same now as before the pressure spikes.  The optical gain seems to be better, and the cavity pole worse.  These changes may be related to the SRM alignment changes, and there was a similar lock on May 30th. 

I made a little plot to see if/how the ETMs charge has changed, from before and after the vent. ETMY seems to be trending towards zero for both the inlock and oplev measurements, ETMX on the other and seems fairly static on the inlocks and is slightly rising as seen by the oplev measurements. ETMX also show opposite signs of charge for the different measurements.

TITLE: 06/12 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 6mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.14 μm/s
QUICK SUMMARY: H1 is in the process of relocking and currently up to PREP_DC_READOUT_TRANSITION. We ran into the issue with the OMC DCPDs not having the same gains after the whitening change again, so TJ and I are looking into a fix.

• Wind is low and microseism is trending down
• All other systems nominal

Sheila and Keita have double-checked the sign convention of what beam positions mean given some A2L gain on an optic.  Since we have had some errors in the past few weeks, I'm summarizing their findings in this alog (and will link to this alog from the 3 measurements we have over the last few weeks).

• P2L gains that are positive mean beam is below center of optic (all optics)
• Y2L gains that are positive on SR3 mean beam is on the -X side of SR3
• Y2L gains that are positive on SR2 mean beam is on the +X side of SR2
• Y2L gains that are positive on SRM mean beam is on the -X side of SRM

Here is a summary table, in units of A2L gain:

Here is that data translated into inferred position on the SRC optics, in mm:

Wed Jun 12 10:12:30 2024 INFO: Fill completed in 12min 25secs

Gerardo confirmed a good fill curbside.

TITLE: 06/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 4mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY: Locked for 11 hours, much quieter environment today. Just within the last 30 min the range seems to be going down. The 1-2kHz DARM BLRMS are moving up, but perhaps not appreciably. I'll keep an eye on this and run a few checks.

TITLE: 06/12 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 13mph Gusts, 8mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.24 μm/s
SHIFT SUMMARY:

1:09 UTC got to PREP_DC_READOUT_TRANSITION
Noticed about about 15 minutes later that we were in this state for much longer than usual.

OMC should be trying to get to READY_W_NO_WHITENING but it is saying :

[SET_WHITENING.run] USERMSG 0: DCPD gains not equal after whitening switch -- yikes!
I tried poking it around to a few different states but it seemed to get stuck at the same state each time.

Ryan told me he had seen this before, I found Ryan's Alog and read through it.  I'm not sure if I have the right channels or not.
H1:OMC-DCPD_{A,B}0_GAIN Is what I scoped back to June 6th and saw that they were indeed changed that day.
Seeing as I couldnt find the full length of those channels on the OMC screen I did a caget and caput and was greeted with a failure to to write error.

CA.Client.Exception...............................................
    Warning: "Channel write request failed"
    Context: "op=1, channel=H1:OMC-DCPD_A0_GAIN, type=DBR_STRING, count=1, ctx="H1:OMC-DCPD_A0_GAIN""
    Source File: ../oldChannelNotify.cpp line 159
    Current Time: Tue Jun 11 2024 18:48:43.327036542

I'm not sure why that was but  Jenne D told me to try: 
cdsutils write CHANNEL_NAME SetPoint
cdsutils write  H1:OMC-DCPD_A0_GAIN 1  worked out well for both A and B Channels and got the OMC going again.

2:24 UTC Reached OMC_Whitening, Waiting for Violins to go Down.
Incoming EQ from northern East Pacific Rise
https://earthquake.usgs.gov/earthquakes/eventpage/us7000mrv4/executive

3:17 UTC Nominal_LOW_NOISE reached

made it to NLN but not in Observing because SQZ_MAN got stuck in FC_WAIT_FDS:
I requested SCAN_SQZANG, to see if that would allow it to cycle through the stages but it got stuck there again.

Naoki jumped on the chance to help the SQZ Manager make it to FDS
I saved some SUS Spot Gain SDFs And an LSC SDF.
4:02 UTC Obsering was reached!

H1 has been Locked and OBSERVING for 4 and a Half hours.

 

FAMIS Weekly In-Lock SUS Charge Measurement 28357

[Jenne, Sheila, Tony]

DRMI ASC had been pulling the SRC out of alignment for the last few days, from where initial alignment leaves things.  This is pretty clearly seen in POP90's rise when DRMI ASC is engaged.

Since the AS72 offsets have been working well in EngageASCforFullIFO and bringing POP90 back down, I have put the same AS72 offsets into DRMI ASC.  This has worked well twice now (although we're not getting all the way to DC readout, likely because of the high wind).  I've also moved where in EngageASCforFullIFO the AS72 offsets come on, so that it's using those offsets all the time (rather than how I had it in alog 78333 where the offset came on later).

WP11914, WP11918 Install ADC in h1iscex for h1pemex readout

Fil, Marc, Erik, Jonathan, Dave

In preparation for testing the new LIGO DAC card in h1susex, an ADC was installed in h1iscex which will read the new DAC's signals.

This ADC belongs to PEM, it was purchased to expand the number of accelerometers.

The ADC, its ribbon cable and interface card were installed in the h1iscex IO Chassis (see drawing). A PEM AA-Chassis was installed and connected to the ADC.

Two models were changed:

h1iopiscex: add 5th ADC

h1pemmx: readout the 5th ADC, route all 32 channels into filter modules with the names H1:PEM-EX_ADC_4_CHAN_n where n=0-31

DAQ restart was needed.

Add WAP channels to DAQ

Erik, Dave:

We took the DAQ restart as an opportunity to use the latest H1EPICS_WAP.ini which adds the missing corner station WAPs. EDC and DAQ restart needed.

Add IRIG-B signals back to end station CAL models

Keita, Fil:

The CNS-II Clock GPS receivers independent IRIG-B signals were reattached to the h1isc[ex,ey] AA chassis.

DAQ Restart

Dave, Jonathan:

The DAQ was restarted for the above model and EDC changes. There were several issues:

gds0 needed a second restart

FW1 spontaneously restarted itself after 728 seconds.

On Friday 06/07/2024 Dave Barker sent an email to the vacuum group noting 3 spikes on the pressure of the main vacuum envelope, I took a closer look at the 3 different events and noticed that the events correlated to the IFO losing lock.  I contacted Dave, and together we contacted the operator, Corey, who made others aware of our findings.

The pressure "spikes" were noted by different components integral to the vacuum envelope.  Gauges noted the sudden rise on pressure, and almost at the same time ion pumps reacted to the rise on pressure.  The outgassing was noted on all stations, very noticeable a the mid stations, and with less effect at both end stations, and for both with a delay.

The largest spike for all 3 events is noted at HAM6 gauge, we do not have a gauge at HAM5 or HAM4.  The one near HAM6 is the one on the relay tube that joins HAM5/7 (PT152), with the restriction of the relay tube, then the next gauge is at BSC2 (PT120), however the spike is not as "high" as the one noted on HAM6 gauge.

A list of aLOGs made by others related to the pressure anomalies and their findings:
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=78308
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=78320
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=78323
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=78343

Note: the oscillation visible on the plot of the outer stations (Mids and Ends) is the diurnal cycle, nominal behavior.

Naoki, Sheila

To investigate the origin of whistles and rms increase in FC IR signal as reported in 78263 and 78344, we turned off the FC green VCO lock after FC IR transition.

In TRANSITION_IR_LOCKING state of SQZ_FC guardian, the FC CMB servo is disabled after FC IR transition. Since we use the green QPD at FC trans for beam spot control, we also turned off the beam spot control. The SDF is accepted as shown in the attachment.

Jennie W, Sheila

After our picoing efforts, at 22:50 UTC today Sheila and I measured the A2L gains of the SRM and SR2.

Sheila notched 31 Hz out of the SRCL control loop and I injected a line at this frequency first at SUS-SRM_M3_LOCK_P_EXC, then SUS-SRM_M3_LOCK_Y_EXC.

Sheila changed the A2L gains for the corresponding degree of freedom so that the line height was minimised in SRCL_IN1 and in DARM using the channels H1:SUS-SRM_M3_DRIVEALIGN_P2L_GAIN and H1:SUS-SRM_M3_DRIVEALIGN_Y2L_GAIN.

SRM spot position:

P2L -1 with precision of 1

Y2L 6 with a precision of 0.5

(not too sure of the precisions as I lost my alog halfway through (d'oh).

We then did the same thing for SR2 by injecting in the M3_LOCK P and Y channels and changing the DRIVE ALIGN gains for SR2.

SR2 spot position was

Y2L 1.5 with precisioon of 0.25

P2L is 8 with precision of 1

The templates for these measurements are in: /ligo/home/jennifer.wright/Templates/Measure_spot_size_SR2.xml and Measure_spot_size_SRM.xml

Last night and today we are in a different spot through the OFI.  See Sheila's alog 78096 for the move that was made. 

Overall, SR2 and SRM yaw are much closer to center in this position, however SRM pitch is farther from center.  I did a quick double check of the SRM pit, and indeed this is where it wants to be.

The previous spots (with the previous SR3 alignment) are recorded in alog 77443.

Attached are the saved SDF diffs for both Observe and Safe snap files.

There had been a suggestion (passed to me by Sheila) that we should measure the beam positions on SRM and SR2 after the big move that we made this week (which is summarized in alog 77427). 

We don't have a premade script to do this like we have for the test masses, so I just did it by hand.  One at a time, I put in a line using the ADS screen to SR2 or SRM pit or yaw, then changed the corresponding A2L element to minimize the line height in CAL-DELTAL_EXTERNAL.  I was also watching SRCL_IN1 and SRCL_OUT, but the lines disappeared in the SRCL signals before they disappeared in the DARM signal, so I just used DARM. 

All A2L values for SR2 and SRM had been 0.0, so I'm not going to bother putting in a 'before' column in the table below since they were all the same value of zreo.

After finding those values, I ran /opt/rtcds/userapps/release/isc/common/scripts/decoup/BeamPosition/CalcSpotPos.py to get from A2L coefficient to beam spot.  This script had been made for IMC optics, but since SRM and SR2 are the same style, the calculation should be the same.  Reminder of where this calc comes from (it's referenced in the script): alog 31402.

We don't have any 'before' measurements to compare to, but at least we now have some amount of information of where we are on these optics after the big move.

I'm pretty sure that these new A2L values can only be good, so I've accepted them in both safe and observe snaps for SR2 and SRM (see first and second attachments, only 2 rows per SDF table are accepted).  These A2L gains for non-test mass suspensions are not under guardian control, so this should be good enough to keep them in place.

In the table below, the Cal-Deltal line reduction factor ends up really just being the ratio of the peak height in DARM before I started doing anything to that dof, and the noise level.  To do a better job of measuring this, I would have had to increase my excitation amplitude, but that didn't seem important enough to do given the limited commissioning time we had. 

I don't have time right now to think through the whole left-vs-right sign convention (it's discussed in alog 31402), but it does look like we're rather 'diagonal' in the SRC now, since the signs of the spot positions are opposite for SR2 vs SRM (eg one positive P2L and one negative P2L means the beam is on opposite sides of center).