Back to Observing after planned commissioning and calibration.

Locked for 7 hours.

Andrei, Sheila

This morning we are taking the commissioning time to get a sqz data set similar to 77133 with longer averaging time and no other changes to the IFO happening in parrallel.

• NLG maximium seed is 0.2146
• unamplified seed (pump blocked) is 0.0127
• dark offset (seed and pump blocked) -2.55e-5
• NLG = 16.9

Data times:

• No SQZ- 15:59:30-16:19:00 UTC  (1399219188 -1399220361) there was a large glitch right at the end of the time (ref 0)
• ran scan SQZ alignment, results are here: 240508092035  everything went well except COMM P which seems to not have found the maximum.  We manually moved ZM4 + ZM6 down in pitch and restarted SCAN SQZ alignment.
• FDS 16:36:48- 16:46:48 (1399221426) RF6 phase 175.81 (ref1)
• FDS -10deg 16:47:14- 17:02:57 RF6 phase 165.79 (ref2) big glitch at 16:52:57
• FDS + 10 deg 17:03:14-17:13:14 UTC RF6 phase 185.84 (ref 3)
• +mid sqz FDS 17:14:01-17:28:45 RF6 phase 206.83 (ref4) big glitch at 17:18-17:19
• FDAS 17:33:37-17:44:50 RF6 phase 106.19 (CLF servo sign -) ref 5 (glitch at end so we stoped the time a few seconds early.  glitch at 17:42:45
• -mid sqz FDS 17:46:36-17:56:36 RF6 phase 104.84 ref6
• - mid FIS 17:58:28-18:08:28 RF6 phase 104.84 small glitch 18:02:30 ref 7
• FIS 18:08:49-18:18:49 RF6 phase 175.81 ref 8
• +mid FIS 18:19:00-18:35:00 RF6 phase 206.83 big glitch 18:24 ref 9
• FIAS (106.19 CLF servo sign -) 18:35:45-18:45:45 ref 10
• no sqz repeat 18:47:00-18:57:00 ref11
• FDS -10 deg 19:00:30-19:10:35 RF6 165.79 ref 12 (repeating because we didn't get enough time the first time)

After this data collection, we ran SCAN_SQZANG, which resulted in a demod phase of 184.35

In the attached screenshots the units are different in the top and bottom plots, I filed a dtt bug because the plot disappears if I try to change the units on the bottom plot: 403

Wed May 08 10:11:08 2024 INFO: Fill completed in 11min 5secs

Gerardo confirmed a good fill curbside.

Erik, TJ, Camilla. 16:00UTC to 16:45UTC

Continued troubleshooting awg issues in ITM in-lock charge measurements 77059. Erik had new code to monitor awg and we took ESD_EXC_ITMX to COMPLETE with amplitude of excitation 1000 smaller (so it will not effect SQZ data taking). 

First time the excitation didn't come though, Erik suggested restarting the GRD code 'guardctrl restart ESD_EXC_ITMX'. After this, it worked fine. Tested with both the production awg (tested on ITMY) and Erik's awg version (tested on ITMX).

Unsure why we didn't have this issue on ETMs. Had to take the nodes back to manged when complete by taking SUS_CHARGE though INIT. Reverted amplitudes to nominal values.

FAMIS27788

I ended up not adding water to either chiller as Y was still overfilled and X was just getting to the ruler markings. The Y filter is starting to green and we should think about replacing it soon. This was all updated in the google sheet at T2200289.

Ran our usual calibration sweep with a broadband and simulines following the instructions on the TakingCalibrationMeasurements wiki.

Simulines start:

PDT: 2024-05-08 08:37:21.772712 PDT
UTC: 2024-05-08 15:37:21.772712 UTC
GPS: 1399217859.772712
 

Simulines end:

2024-05-08 15:58:52,248 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20240508T153722Z.hdf5
ICE default IO error handler doing an exit(), pid = 571885, errno = 32
PDT: 2024-05-08 08:58:52.297522 PDT
UTC: 2024-05-08 15:58:52.297522 UTC
GPS: 1399219150.297522

TITLE: 05/08 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 2mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.19 μm/s
QUICK SUMMARY: Observing for 2 hours after an automated relock. Commissioning planned for today.

TITLE: 05/07 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:

H1 has been running with a range of ~150Mpc (lower than normal) & rung up violins.  Additionally, there were high winds for half of the shift, so H1 was not down for most of the shift.  But once the sun set, the winds died down and finally allowed for an opportunity to lock and get back to Observing!

LOG:

• MX VAC tour (janos + contractor)
• 2323 Tyler returning from EX fan bearing/chiller work.
• 2330-2356 Optics Lab clean-up (camilla)
• 2333 GRB Short verbal alert
• 2352 Lockloss at CHECK AS SHUTTERS (probably due to wind)
  • 0115 Taking H1 to IDLE due to wind with gusts over 45mph (will check back in an hour)
  • 0235 Giving Locking another try with gusts around 35mph
  • 0333-0353 INITIAL ALIGNMENT:  Since PRMIs have been looking completely dead.
  • 0431-0509 Lock to NLN & OBSERVING @0512.
• 0155-0204 Checking pump (janos)
• nuc30's DARM dtt had all live signals disappear.  Eventually able to close window and relaunch the startup to get DTT back. 

H1 had a lockloss within the 1st hour of shift.  Winds were rising at this time (gusts touching 25mph), and for the next few hours the winds have increased with gusts just under 50mph.  Needless to say, have spent several hours in the IDLE state due to winds.  The sun just set and wind gusts have been slowly coming down to 25mph and returning to locking.

Although the last couple of attempts for PRMI looked horrible and have immediately triggered CHECK MICH FRINGES.  May run an alignment next.

Since the A2L script that measures a transfer function isn't quite minimizing our ASC noise in DARM, Sheila suggested re-finding the old A2L script that we used to use, which just looks at the height of the peak in DARM.

I think I've found it, in /opt/rtcds/userapps/release/isc/common/scripts/decoup/al2_min_LHO.py .  I made sure that it, and other scripts in that directory, were checked in to svn (they were last modified somewhere between 2018 and 2019, depending on the script).

The script (as wrtitten) uses the ADS to actuate each of the quads, and uses the demods to find the size of the signal (it does a sum of the squares of the I and Q of the demodulated signal).  The script just guess-and-checks several A2L gain values for each optic, makes a step, and checks again.  Once it's finished, it does a linear fit to find the A2L value at which the peak height is expected to be zero.  The script runs 8 dither lines (pit and yaw from each quad) around 20 Hz, so that it can do this guess-and-check for all the optics at the same time. 

The values in the script are out of date (we've slightly modified the frequencies we use for ADS while locking), so those values and the filter numbers for the matching bandpasses need to be checked.  Also, the excitation amplitude in the script is probably higher than we need (they are set to be 300 counts, but we use 30 counts at full power right now, but we may want a little better SNR so we might want to find a value that is between those two.

Also, we may find that we want to instead do the optics one at a time, at 30 Hz, where the coupling of ASC to DARM is more important to our range.

We can try this out during one of our commissioning windows later this week, to see how it goes.

TITLE: 05/07 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Lighter maintenance today but we managed to do some more SR3/2 moving to investigate our recent required alignment shift. On the relock we had some lock losses that had to be fixed with some filter changes (alog77698). Violins have also come up during these relocks, but they are damping nicely. We are now observing for almost an hour.
LOG:

2240 Observing                                                                                              

Jenne D, Ryan S, Camilla C, TJ S

Today in a single bounce 10W configuration we set SR2 to center AS_C with the SRC2 ASC loops via the ALIGN_IFO guardian in the SR2_ALIGN state, then moved SR3 in steps to see how our AS_C power would change in different positions. We found that there is an area, or spot, that we lose significant throughput to AS_C, but moving around this spot in any direction recovers our nominal single bounce power. This is followup from Jenne Driggers SR3/2 move (alog77388) to bring back our power at the AS port on April 24th, and Jennie Wright, Minhyo, and Sheila's efforts searching in yaw to find where we are losing the power (alog77513). This time we went further than Jennie W and team went and managed to get back almost all of the AS_C sum back. Almost all because just before we got there we starting running into a different, perhaps clipping, issue that changed the shape of the AS air camera in a much different way than when around this spot.

More details:

We started out by reverting the alignment to a time during DRMI locking from the Tuesday morning of April 23. We then brought up tried to move SR2 and SR3 as was done previously, then Jenne suggested that we turn on SRC2 to have SR2 follow our SR3 moves and keep AS_C centered. This worked great along with a little extra SRC2 gain to help move things along faster. Moving in pitch in either direction yielded fairly quick power gains (trends SR3 -P move & SR3 +P move). Jenne suggested that we try to go further in yaw than the Jennie W. team did to see if it ever improves, and we were able to get AS_C almost back after ~550urad in SR3 (trend SR3 -Y move today, and SR3 +Y move April 24 ). If I had the time I'd love to make a nice graphic to show where we can't go but we'll have to deal with this table for now.

TITLE: 05/07 Eve Shift: 23:00-08:00 UTC (16:00-01:00 PST), all times posted in UTC
STATE of H1: Observing at 66Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 16mph Gusts, 12mph 5min avg
    Primary useism: 0.08 μm/s
    Secondary useism: 0.22 μm/s
QUICK SUMMARY:

TJ has H1 back to observing w/ a range just under 150Mpc and passed on some changes to keep an eye on for next-locks.  Will also keep an eye on the rung up violins we have been dealing with the last few days. 

It's a bit breezy, with gusts just touching 25mph (so hopefully not an issue).  useism has slowly been ramping up from the 50th percentile for the last ~18hrs.

Maintenance recovered, back to Observing at 2240 UTC.

We struggled with a handful of lock losses at inconsistent spots and two lock losses just after Transition_from_ETMX. Jenne and Ryan S tracked this down to some changes made yesterday and changed a filter (alog77698), then we made it through one time. Unsure if this will be ok net relock or if it will interfere with locking though.

Sheila, Camilla.

After this morning's windy lockloss from TRANSISITON _FROM_ETMX, we continued previous 77366 troubleshooting.

Sheila manually stepped though TRANSISITON _FROM_ETMX:

• We found that only the L1 history was cleared, giving unwanted outputs when we turned on L2 and L1 gains.
  • Sheila added a line to clear L2 history (line 5115: ezca['SUS-ETMX_L2_LOCK_L_RSET']=2).
• We then lost lock when turning off two DARM1 filters  (ezca.switch('LSC-DARM1', 'FM1', 'FM2', 'OFF')). This seems the cause of our glitch, attached shows this DARM1_SWSTAT change at the same time as the glitch on a successful lock.
  • FM1 "8^2:2^2" has a 20dB gain at low frequency and 10s ramp, but FM2 "MadHatter" has a 40dB gain and 0.09s ramp so is probably to blame.
  • Sheila notes that "MadHatter" used to be left on during the transition (74798, 75451). To check this, I see that FM2 was kept on though a successful transition from 75631, plot attached.
  • Sheila edited ISC_LOCK to leave DARM1 FM2 on during TRANSISITON _FROM_ETMX but turn it off during the next state:  LOWNOISE_ESD_ETMX, once we are already on NewDarm and effect of this low frequency filter is suppressed.
• After these changes, our locking was successful with no glitches: plot attached.

In the observing stretch that started Monday around 8 pm, there was a drop in optical gain (by 4%), and power at AS port PDs (4% drop in AS_A sum, AS_B sum, AS_C sum, and OMC REFL).  There not at that time any change in circulating power in the arms, PRG, coupled cavity pole, or alignment of suspensions (shown are SR2, SRM, OM1+2, but we have also looked at many other suspension, ISI and HEPI related channels for this time 77382 ).  This time is shown by the first vertical cursor in the attachment. 

We were unable to relock the interferometer after that Monday evening lock (a new lockloss type appeared early Tuesday morning, 77359), and after the maintence window we were uable to lock with difficulties powering up (77363) and an AS camera imagine that had lobes whenever the beam was well centered on AS_C.  We locked that evening by adding large offsets to AS_C's set point, (77368).  This is the cause of the large alignment shifts seen in the screenshot on Tuesday evening to Wed morning, which allowed us to lock the IFO but created a large scatter shelf and resulted in a lower coupled cavity pole, and lower optical gain, and we did not have much squeezing that night. 

We do not think that Tuesday maintence activities are the cause of our problems, although some of the Tuesday work has been reverted (77350 77369).

Yesterday we spent much of the day with SRY locked, single bounce or using the squeezer beam reflected off SRM to investigate our AS port alignment.  77392, We are able to recover the same throughput of a single bounce beam to HAM6 by moving the alignment of SR2 + SR3 by a huge amount 77388, which also produced a round looking beam on the AS camera.  We haven't since tried to explore this aperture, to see if we could have also recovered this thoughput with a pitch move, for example.  We also saw that the squeezer beam does not arrive in HAM6 with a good transmission when injected with the alignment used previously, but that we could recover good transmission to HAM6 by moving ZM5 by 150-200 urad, in pitch or yaw.   With this shift in SRC axis, and squeezer alignment we were able to relock and not have the large scattering issues we had Tuesday night.

Today's time was spent recovering from a seemingly unrelated problem in the SQZ racks, and some commissoning aimed at recovering our previous (165Mpc) sensitivity with this new alignment.  This will continue during tomorow's commissoning time.

additional related information:

• (no SQZ, HWS, OFI voltmons)  77374
• Move of SQZ beam in lock to get squeezing: 77400
• OFI transfer functions: 77391
• other suspension health checks: 77383
• dark offset script: 77362
• SRM and SR2 beam positions after the shift: 77443
• Further look at powers on HAM6 PDs: 77441
• AS port fringe wrapping worse than Summer 2023: 77452