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

Well Pump Enabled

Because the fire water tank is in need of water both for it's primary function(s) as well as upcoming demand placed on it by DGR for the storage building work, I have enabled the pump to run beginning at 7:55a PST. The pump will run for a duration of 4 hours.

T. Guidry

Ops Day Shift Start

TITLE: 10/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 162Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.21 μm/s
QUICK SUMMARY:

Observing at 162Mpc and have been Locked for 4 hours. Looks like this last lock has been much smoother than the others during the night were.

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.

OPS Eve Shift Summary

TITLE: 10/10 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

IFO is LOCKING at CHECK_AS_SHUTTERS (although squeezing is broken).

Overall terrible shift and locking due to many affected suspension sliders due to a dolphin crash at 22:30 UTC (around 4:30 PM). Not one minute spent in observing due to this crash that somehow changed everything. Here's a rough story:

IR Not Found:

IR was not found. Went into Input_Align in Initial_Alignment, bright eyed and optimistic only to realize that this was also not working. Checked the ALS Overview to find that we were getting a beatnote, and that guardian had indeed swept the full frequency range, without finding any resonances. After some finagling and calling Daniel, he pointed me to check IMs and PRs, and indeed IM4 and PR2 were off in P and Y, so I trended those values and then set them to their original. We were able to Find IR, complete initial alignment and went all the way up to NLN.

Unable to SQZ:

Was happy to finally get to NLN (2:07 UTC) but then the SQZ was unable to lock FC. Breaking News: Lockloss due to 40mph winds! Lockloss alog 80579 After a lot of help from Sheila, we managed to get it working again. Now onto locking!

Lock Attempt 2 (and unable to SQZ again):

Got to NLN after losing lock frequently in ALS and PRMI/DRMI (winds). Wind calmed down and we were able to get all the way up to NLN (4:46 UTC) until yet again, SQZ was broken. Around 2 minutes after alerting Sheila, we lost lock again.. Lockloss alog 80580

LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
01:57	PEM	Dan Morraru	MSR	N	LSB Warehouse Connection	02:16

Lockloss 04:58 UTC

Another probably wind-related lockloss. While EX X-Axis ground motion was high, overall wind was not usually high enough to cause NLN lockloss. So more of a toss-up - lockloss tool does have a windy tag though...

Lockloss 03:21 UTC

Winds approaching 40mph so will assume environmental. EX X-axis was experiencing a lot of ground motion and ALSX was struggling to lock for a while.

Ops Day Shift End

TITLE: 10/09 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Currently relocking and at FIND_IR. The camera issue seems to have been fixed for now, but we are still seeing the glitches in the PSL.
LOG:

14:30 Observing and Locked for 7 hours

15:25 Out of Observing due to camera issues (80559)
15:34 Back into Observing (we were good to go back two minutes after we were taken out, but it wasn''t set to auto go back into Observing and I missed it being okay)

16:25 Out of observing from the camera issue
16:26 Back into Observing

16:50 Out of observing due to TCS CO2 laser unlock
16:52 Back into Observing

17:01 I took us out of Observing to try SQZ offloading before taking us down for corrective maintenance
17:03 I unlocked the IFO using the IMC REFL servo toggle, sitting in IDLE

18:49 Started a manual initial alignment
19:17 initial alignment done, relocking

20:08 NOMINAL_LOW_NOISE
20:14 Observing

20:28 Out of Observing so Keita can grab stuff from the LVEA
20:33 Back into Observing

22:05 Superevent S241009em

22:34 Lockloss                                                                                                                                                                                                                                                                                                                                                                                                   

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
15:19	FAC	Karen	OpticsLab/VacPrep	n	Tech clean	16:17
16:17	FAC	Karen	WoodShop	n	Tech clean	17:02
17:03	FAC	Richard, Karen	FCETube	n		17:09
17:10	FAC	Karen, Kim	FCETube	n	Tech clean	18:29
18:06	PSL	Keita, Sheila, Rick	LVEA, DiodeRoom	n	Swapping PSL controller	18:44
20:28		Keita	LVEA	n	Grabbing stuff	20:32

Corner station Dolphin crash, h1sush7 error caused crash of h1sush34, h1lsc0 and h1omc0

At 15:34:40 Wed 09oct2024 PDT a corner station dolphin glitch caused DACKILLs for h1sush34, h1lsc0 and h1omc0.

h1sush7 has other Dolphin logs associated with previous glitches. 

https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=75921
[Wed Feb 21 11:33:40 2024] IXH Adapter 0 : Port 0 is not operational -- UpTime: 0 sec - Event = 0

https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=79561
[Thu Aug 15 16:37:15 2024] IXH Adapter 0 : Port 0 is not operational -- UpTime: 0 sec - Event = 0

And today:
[Wed Oct  9 15:34:25 2024] IXH Adapter 0 : Port 0 is not operational -- UpTime: 0 sec - Event = 0
[Wed Oct  9 15:34:25 2024] dis-ix-ntb: dis-ix-ntb0: Detected IXS600 (601) switch, SUB2, port 1, global port 12
[Wed Oct  9 15:34:25 2024] IXH Adapter 0 : Local adapter is connected to IXS600 switch, SUB2, port 1
[Wed Oct  9 15:34:25 2024] IXH Adapter 0 : Link 0 is operational - Link width: x8 - PCIe Gen 2 -- Downtime: 0 sec

We might want to check cable when we get a chance, and if that dose not resolve the issue consider replacing the card. 

OPS Eve Shift Start

TITLE: 10/09 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 16mph Gusts, 9mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.22 μm/s
QUICK SUMMARY:

IFO is LOCKING following a Dolphin Crash that's still being investigated. alog 80572.

 

Lockloss

Lockloss @ 10/09 22:34UTC from PSL :( possibly from a CDS error

Weekly In-Lock SUS Charge Measurements

FAMIS 28374 Weekly In-Lock SUS Charge Measurements

 

The nominal set of plots that the Famis task requests are plotted as usual.
ETMX looks fine
ETMY also looks fine
ITMX has a point on the plot that skews the plot so much that we cant really see any recent relative motion of the measurement.
Same thing happened with ITMY.

I'm not sure if this is actually useful.... so here are the same ones but only 4 months of data instead to get those really low ones off the plots.

4 Month ETMX
4 Month ETMY
4 Month ITMX
4 Month ITMY

Maybe this isn't useful to anyone but I was mildly interested.