Ops Day Shift End

TITLE: 10/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Currently Observing at 158Mpc and locked for 5 hours. A lot of time out of Observing today due to continued PSL troubleshooting and commissioning. Relocking after our one lockloss wasn't too bad.
LOG:

14:30 Observing and Locked for 4 hours

15:02 Out of Observing for Commissioning
15:29 Lockloss
    16:24 Going through CHECK_MICH_FRINGES a second time, so decided to run an initial alignment only for PRC, MICH, and SRC
    15:29 manual initial alignment done, relocking
    16:39 Lockloss from LOCKING_ALS
    16:49 IDLE for PSL power swap
    17:45 Started relocking
    17:51 Lockloss from ACQUIRE_DRMI_1F
18:42 NOMINAL_LOW_NOISE
20:25 Observing

21:45 Out of Observing to run calibration sweep
22:51 Observing

23:25 - 23:37 Trash truck onsite - tagging PEM, DetChar                                                                                                                                                                                                                                                                                                                                                                                                                                                                             

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
15:17	FAC	Tyler		n	Running well pump (started 14:55)	19:11
16:56	PSL	RyanS, Fil, Fernando	LVEA	n	Swap power box	17:18
16:56	FAC	Tyler	YARM	n	Driving along YARM backside	18:17
17:21	PSL	RyanS, Fil	LVEA	n	Re-swap power	17:47
19:14	FAC	Tyler		n	Running well pump	20:14
19:16		Sheila	LVEA	n	Plugging cable in	19:25
20:20		Sheila	LVEA	n	Unplugging cable	20:25
21:24	VAC	Fil, 1 VAC guy	YARM	n	Fixing solar panel	22:47

Beam needs recentering on IMC IM4 Trans QPD

The sum of the counts on the QPD IMC-IM4_TRANS_NSUM_OUT has been around 53W since July 2nd, 2024(attachment1). Before this, the nsum value was around 58W. On July 2nd, the PMC was swapped (78813), and so the pointing into the ifo changed. After the PMC change the IMC alignment was updated to realign the beam(78816), but the IM4 trans beam is still not hitting in the same place as it was before. As a result, the beam is very off in yaw when it hits the QPD, so yaw is currently at +0.98 so it's on the edge. You can also tell the beam is partially off the QPD because of how much change we see in the IM4 trans values as compared to before July 2nd.

Solar Panels on Y2-8

WP 12136

One of the solar panels on Y2-8 was replaced. Panels provide power to a vacuum gauge inside the beamtube enclosure.

F. Clara, G. Moreno

OPS Eve Shift Start

TITLE: 10/10 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 5mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.23 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING

Oli gave me the updates regarding fixes to the dolphin crash from yesterday.

 

Calibration Measurements October 10 2024

Calibration measurement run after being locked for 3 hours

calibration monitor screenshot (accidently taken after going into NLN_CAL_MEAS)

Broadband 10/10 21:50 - 21:56UTC

File:

PCALY2DARM_BB/PCALY2DARM_BB_20241010T215057Z.xml
 

Simulines* 10/10 21:57 - 22:21UTC

*Simulines was run using the ini file settings_h1_20241005_lowerPcal.ini instead of the usual

settings_h1_newDARM_scaled_by_drivealign_20231221_factor_p1.ini, both of which are found in /ligo/groups/cal/H1/simulines_settings/newDARM_20231221/

Files:

DARMOLG_SS/DARMOLG_SS_20241010T215755Z.hdf5

PCALY2DARM_SS/PCALY2DARM_SS_20241010T215755Z.hdf5

SUSETMX_L1_SS/SUSETMX_L1_SS_20241010T215755Z.hdf5

SUSETMX_L2_SS/SUSETMX_L2_SS_20241010T215755Z.hdf5

SUSETMX_L3_SS/SUSETMX_L3_SS_20241010T215755Z.hdf5

PSL Control Box 1 Tested on Rack Power (WP 12133)

R. Short, F. Clara, S. Dwyer

In the ongoing effort to diagnose the source of the glitches seen in the PSL, we decided to try moving the NeoLase control box in the PSL racks back to rack power, essentially undoing what was done in alog79593, and observe any changes in the glitch behavior. While H1 was unlocked during the commissioning window this morning, I shut down the PSL in a controlled manner (in order of ISS, FSS, PMC, AMP2, AMP1, NPRO), then Fil switched CB1 back to rack power, and I brought the system back up. When back in the control room, we very quickly noticed glitching in the NPRO output power channel as we've seen before, and after locking the RefCav, the FSS glitches also returned. Deciding this wasn't the solution we were looking for (and concluding it probably wouldn't have changed anything in the first place), I took the PSL down again for Fil to switch back to the bench-top power supply, then brough it back up all without issue. Fil also took the opportunity to install a longer cable for this power supply to reduce the trip hazard potential next to the PSL racks. This closes WP 12133.

I'm tagging DetChar since this separate power supply was noted to have helped reduce a 9.5Hz comb seen in DARM, but I'll reiterate that functionally nothing here has changed and CB1 remains on its own power supply.

NB injections taken

I ran the noise budget injections for frequency noise, input jitter (both pitch and yaw) and PRCL. All injections were run with CARM on one sensor (REFL B). The cable for the frequency injection is still plugged in as of this alog, but I reset the gains and switches so we are back on two CARM sensors and the injection switch is set to OFF.

All injections are saved in the usual /ligo/gitcommon/NoiseBudget/aligoNB/aligoNB/H1/couplings folder under Frequency_excitation.xml, IMC_PZT_[P/Y]_inj.xml, and PRCL_excitation.xml.

I realized an intensity noise injection might be interesting, but when I went to run the template for the ISS excitation, I was unable to see an excitation. I think there's a cable that must be plugged in to do this? I am not sure.

*********Edit************

Ryan S. sent me a message with this alog that has notes about how intensity noise injections should be taken. Through this conversation, I realized that I had misread the instructions in the template. I toggled an excitation switch on the ISS second loop screen, when I should have instead set the excitation gain to 1.

I was allowed another chance to run the intensity injections, and I was able to do so, using the low, middle, and high frequency injection templates in the couplings folder.

Also, the Input jitter injections have in the past been limited to 900 Hz, because the IMC WFS channels are DQed at 2048 Hz. However, the live IMC channels are at 16 kHz, so I edited the IMC injection templates to run up to 7 kHz, and use the live channels instead of the DQ channels. That allowed the measurements to run above 900 Hz. However, the current injections are band-limited to only 1 or 2 kHz. I think we can widen the injection band to measure jitter up to 7 kHz. I was unable to make those changes because we had to go back to observing, so this is future to-do item. I also updated the noise budget code to read in the live traces instead of the DQ traces.

Unfortunately, in my rush to run these injections, I forgot to transition over to one CARM sensor, so both the intensity and jitter measurements that are saved are with CARM on REFL A and B.

Ops DAY Midshift Status

Currently in Locked and in Commissioning. We are taking an extra hour for commissioning past the normal schedule, so we should be getting back to Observing around 20:10UTC.

sdf and ISC_LOCK argueing over ETMX_L3_LOCK_BIAS_OFFSET

Oli, Ryan S, Sheila, Camilla

This morning we didn't go through SDF_REVERT as I had a pending sdf change so we went to CHECK_SDF whihc skips SDF_REVERT. We then had the ETMX suspensions model saturating, tracked this down via cds overview of h1susetmx and ETMX L3 DAC screens to be the L3 bias saturating.

We found that the nominal ETMX_L3_LOCK_BIAS_OFFSET value (saved in sdf) is -8.9 but ISC_LOCK PREP_FOR_LOCKING sets this to -9.3 (saturates DAC). Can see them arguing in the attached plot.

A to-do would be to remove this control from ISC_LOCK but Sheila said this isn't simple as other gains need to be adjusted too. Can look at doing this is the future.

Thu CP1 Fill, TC-B iced

Thu Oct 10 10:10:59 2024 INFO: Fill completed in 10min 55secs

Non-optimal fill, TC-A went to -200C (unusual in autumn), TC-B only went to -115C. Early trip because TC-A started at -75C, but pressure spike indicates a good fill.

Jordan discovered the TCs were completely iced over.

Lockloss before Squeezing Data Set Taken

Sheila, Camilla

15:02:40-15:13:00UTC - Took No Squeezing time. IFO had been in NLN for 4h30m.

Checked NLG (0.1178/0.00872) = 13.5. Adjusted OPO temperature. 

After our no SQZ time, once in FDS, we let the IFO ASC converge and then turned it off, cleared histories in SQZ-ASC filter banks and ran scan sqz alignment. We never checked these were the same in 80506. Lost lock before scan sqz alignment could finish running. 

BBSS Top Mass F1 Drift: The Anthology

Ibrahim 

This alog is a summary of all the BBSS drift data we have, and what observations informed which next steps. The embedded table below shows each "regime", which is a span of data collection after a mechanical adjustment. I have then linked pictures of each regime's available OSEM readouts. In the case of BOSEMs, we've only had clean readings with working electronics for regimes 8, 9, 10. We briefly had a broken sat-amp box for regime 5 so we do have some readings. Either way, I don't believe these show significant drift. At the end, I also have attached an overview of the two main adjustment types over the course of the time we've been dealing with this issue. First is blade tip adjustment and second is added weight (grams) distribution adjustment (which also has a graphic for each config). I will add Transfer Functions later (IFO is misbehaving on EVE shift and want to get something out!). They are located on X1 under: /ligo/svncommon/SusSVN/sus/trunk/BBSS/X1/BS/SAGM1/Results and are dated. With limited further ado:


 Overview: Blade Tip Height Changes: 



 Blade Tip Height Changes: 

Regime 1:

  

Regime 2:

 

Regime 3:

 

Regime 4:

 

Regime 5:

 

Regime 5 PUM BOSEMs (Broken Sat Amp):



Regime 6:

 

Regime 7:

 

 Added Weight Distribution Changes:

Regime 8:

 

Regime 9:

 

Regime 10:

 

 Regime 8, 9, 10 (Weight Changes) PUM BOSEMs: 



 Added Weight Distribution Config Graphic: 

In reply

 Added Weight Changes Zoomed Out:



 Blade Tip Height Changes and Initial Drift Zoomed Out:

Correction to BBSS Added Weight 

Lockloss

Lockloss @ 10/10 15:29UTC during Commisioning

Ops Owl Update

H1 requested assistance around 11pm PT due to the SQZ filter cavity not being able to lock. Based on previous alogs, it sounds like there was some SQZ issues earlier today, but there's no mention as to what exactly. Looking at the FC green camera it was clearly trying to lock with a pitch misalingment, so I adjusted FC2 and maximized H1:SQZ-FC_TRANS_C_LF_OUTPUT. This seemed to help, but then after it would find IR it would lose lock. I'm not sure why, but we just lost lock (0720UTC) so I guess I'll see if it happens again when we get back.

SQZ ASC turned on using AS42 on ZM4/6

Sheila, Camilla.

New SQZ ASC using AS42 signals with feedback to ZM4 and ZM6 tested and implemented.  We still need to watch that this can keep a good SQZ alignment during thermalization. In O4a we used a SQZ ASC with  ZM5/6, we have not had a SQZ ASC for the majority of O4b.

Prep to improve SQZ:

• No squeezing from 15:31:30 to 15:41:30UTC.
• Adjusted OPO temperature following no observing instructions in 80461. Measured NLG to be 12.8. (0.1165/0.0091) following 76542.
• This improved the squeezing from 2.5dB above 300Hz to 3dB at 300Hz and 4.2bD above 1kHz.

Testing ASC from 80373:

• Ran the "reset as42 nosqz" offsets script while in no sqz. SDF accepted.
• Put the input matrices form 80373 into SQZ ASC and checked they were diagonalized correctly by moving ZM4/6 in turn and watching ASC_POZ/ANG input signals. ZM4 pitch wasn't completely diagonalized but that others looked good.
• Reduced ASC_WFS gain from 0.1 to 0.05, cleared histories, set all ASC_POS/ANG gains to 1 and one at a time turned on the inputs. We had some troubleshooting with POS_Y but there was a minus sign inside one of the filter banks we hadn't seen. In this troubleshooting we found the matrix was mostly diagonal so removed the cross-coupling terms for the YAW input matrix.
• Found WFS gain is better with lower WFS gain to 0.01 so we took a factor of 100 for the input matrix and left H1:SQZ-ASC_WFS_GAIN at 0.5. Accepted all in sdf. And edited sqzparams and reloaded SQZ_MANAGERT to turn on SQZ ASC.
• To test, we tried the "offload AS42 ASC" script with the plan to compare the AS42 alignment with the alignment from the guardians scan SQZ alignment. The script didn't work as expected, it's hard-coded to offload ZM45/6 rather than ZM4/6 that we are now using, we should fix this or go back to using ther guardian states. After turning off the ASC and running again to clear histories, this caused a lockloss, probably as ZM6 P moved 60urad in 0.3s. See attached lockloss plot.

10kHz HOM in ER16 simular to O4a

Plot attached showing that the Higher Order Modes around 10.4 to 10.6kHz are in a similar position during ER16 (blue) that they were at the end of O4a (yellow).

This is expected as we have not changed the TCS system (CO2 and RH settings the same). Unsure why in the last long (2024/03/28) they are larger, the noise floor changes with SQZ but wouldn't expect the peaks to change much.