Thu Mar 28 10:13:28 2024 INFO: Fill completed in 13min 23secs

Gerardo confirmed a good fill curbside.

Here's a BruCo scan for last night: https://ldas-jobs.ligo-wa.caltech.edu/~gabriele.vajente/bruco_1395660903_GDS_CALIB/ using GDS-CALIB_STRAIN_CLEAN

Some observations on the low frequency range (<50 Hz):

1. there is coherence with PRCL, MICH and SRCL. My guess is that PRCL couples through MICH and SRCL, since there is some coherence MICH vs PRCL and SRCL vs PRCL.
2. however, similar coherence pattern is visible with REFL_RIN, and I'm not sure what to make of that
3. there is coherence with CHARD_Y and lower with DHARD_Y. There is also coherence with HAM1 motion, that's probably due to the known HAM1 to CHARD coupling
4. below 20 Hz it looks like there is high coherence with IMC angular yaw signals, so maybe we're limited by low frequency jitter there?

It looks like we could try to improve the low frequency by:

1. doing A2L again to fix CHARD_Y
2. see if that improves PRCL coherence, if not
3. redo MICH FF and SRCL FF, hopefully that will reduce PRCL too. If not
4. investigate the interesting fact that PRCL and REFL_RIN seem to show the same coherence with DARM

TITLE: 03/28 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 8mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.52 μm/s
QUICK SUMMARY:

H1's been locked 20.75hrs and is currently in OBSERVING at a range just under 160Mpc.

Robert mentioning needing to fix some accelerometers at an End Station and then start PEM injections (he also mentioned commissioning work possibly going on while he looks at the accelerometers).

TITLE: 03/28 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: None
SHIFT SUMMARY: We're Observing and have been Locked for over 12.5 hours now. Very quiet night!
LOG:

2300UTC Detector locked for 4.5 hours, commissioning wrapping up

2308 Into Observing

Closes FAMIS#25984, last checked in 76634

They all look very similar to at least the last few weeks of checks. The only thing that stood out to me was ITMY stage 2 V2 around 100Hz and 170Hz - the spikes there are slightly thicker than all the other stage 2 higher frequency spikes.

We've now been Locked for over 9 hours and are Observing.

Vicky, Naoki, Nutsinee

To scan the ZM alignment, we copied the SCAN_ALIGNMENT state in SQZ_MANAGER guardian in LLO. After some debugging, we successfully ran this state. The result is saved in here.

https://lhocds.ligo-wa.caltech.edu/exports/SQZ/GRD/ZM_SCAN/

This state scans the ZM4/ZM6 COM and DIF P/Y. We need the proper diagonalization to define the COM and DIF, but we have not done it today. The state fits the BLRMS6 at 1.7kHz and finds the optimal ZM slider value for minimizing the BLRMS6 as shown in the first attachment. After each ZM scan, the SQZ angle is also scanned and the optimal SQZ angle is found as shown in the second attachment.

The third attachment shows the BLRMS. The T1 cursor shows when the sqz-optimized scan was done. After the scan, the BLRMS6 looked good, but the BLRMS3 (yellow) was not so good and the BNS range was below 150 Mpc. So we tweaked the sqz angle and the BNS range reached more than 150 Mpc.

The original SCAN_ALIGNMENT tries to find the minimum of squeezing, but we modified it so that it can also try to find the maximum of anti squeezing. The T2 cursor in the third attachment shows when the asqz-optimized scan was done. The result is saved here.

sqz-optimized: https://lhocds.ligo-wa.caltech.edu/exports/SQZ/GRD/ZM_SCAN/240327132206/

asqz-optimized: https://lhocds.ligo-wa.caltech.edu/exports/SQZ/GRD/ZM_SCAN/240327144407/

The fourth attachment shows the ZM slider after the sqz-optimized and asqz-optimized scan. The ZM4 Y is almost the same, but other ZM alignment is different by 10-20 counts between the sqz-optimized and asqz-optimized scan. The proper diagonalization of ZM4/6 would resolve it.

Since the SCAN_ALIGNMENT touches the TRAMP of ZM slider, we reverted it after the scan as shown in the fifth attachment.

Jennie and I started the camera_servo_offset_stepper.py script to run for CAM2 (at 23:18UTC - 3:28UTC) should finish by 8:18pm and scheduled CAM1 for 8:30 to 12:30pm (3:30 to 7:30UTC). These didn't run yesterday 76732 as the IFO was unlocked. 

TITLE: 03/27 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing
INCOMING OPERATOR: Oli
SHIFT SUMMARY: We've been locked for over 4.5 hours and have just transitioned back to Observing for the rest of the evening. The one lock loss we had was possibly cuased by work on the floor. Relocking was straight forward, I ended up moving PRM to lock PRMI in an attempt to avoid an initial alignment. It took 57 min to relock.

• 1726 Lock loss. HAM1 HEPI tripped
• 1821Back to low noise
  • DRMI/PRMI looked awful when it first arrived. In an attempt to avoid an initial alignment, I let it run a Mich bright, then I moved PRM a fair amount in pitch and yaw to get PRMI to lock. DRMI locked up without issue after this. No other intervention was needed.
  • 57min from lock loss to NLN
• 2308 Observing

LOG:

TITLE: 03/27 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 13mph Gusts, 11mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.27 μm/s
QUICK SUMMARY:

Detector has been Locked for 4.5 hours and commissioning is wrapping up.

Since we have been moving input alignment, seeing strange behavior, and have an increased PRCL coupling that we can't explain, I figured we should answer this question.

Short answer: probably not.

Longer answer and explanation:

Going back in time in the alog, I found several great references. First, this alog 31381 from Kiwamu that shows at one point the PR2 Y2L gain was -9.5, greater than our current value of -7.4, and the miscentering corresponded to 19 mm miscentered.

I also found these other references, 31402, 42601, and Koji's elog (thanks to the above alog and also Georgia). The beam miscentering can be calculated via d = 2* alpha * beta / D. Alpha is calculated by alpha = A2L * L_eul / (A2A * A_eul)

For an HSTS, d = 39.28 mm * alpha (Craig's comment in 42601)

PR2 Y2L = -7.4, L_eul = 0.25, Y2Y = 1 and A_eul = -5.23820 (for the UL coil).

Therefore, d = 39.28 mm * 0.37 = 14.53 mm

From Kiwamu in 31381, PR2 is 150 mm in diameter and the beam is about 6 mm. So this Y2L gain is fine, assuming that the coils are balanced.

A good test is probably to check that the PR2 coils are balanced.

Daniel plugged in the SR785 into the common mode board this morning. 

I've followed the instructions in 64204, and 67214 summarized here:

make sure the excitation A is enabled on the common mode board, the 785 is plugged in.

cd /ligo/gitcommon/psl_measurements/templates
conda activate /ligo/home/craig.cahillane/.conda/envs/psl
python ../code/SRmeasure.py carm_olg_template.yml

The plot options in the template don't work.

to find your data go to: /ligo/gitcommon/psl_measurements/data/carm_olg and try ls -lrtp to find the most recent file 

To make a plot:

python ../code/quick_tf_plot.py /ligo/gitcommon/psl_measurements/data/carm_olg/CARM_OLG_27-03-2024_131841.txt

The CARM olg right now is something like 17 kHz, consistent with 76448  but a little higher than 70920 and 65676 and 67584.  These all look fine according to the loop stability, but we could try reducing the CARM gain a bit to be more similar to O4a.

I reduced the gain by 3dB on both inputs 1 and 2, resulting in the second attachment.  I've lowered the gain setting in laser noise supression to 3dB from 6dB as well so that we will run like this.

TJ, LouisD, TonyS, DriptaB, FranciscoL

There was an unexpected "bump" on PcalX at around GPS 1395546818. This was shortly after TJ attempted Detchar safety injections (76727).

Looked into H1:CAL-PCALX_TX_PD_OUT, RX_PD_OUT, OFS_PD_OUT, OFS_AOM_DRIVE_MON_OUT and OFS_ERR_OUT for any issues.

Observations:

• Bump travels across spectrum from 0 Hz to 120 Hz for an indefinite amount of time. The figures "PcalX_DTT_120.png", "...85.png", and "...40.png" illustrate the bump appearing at 120 Hz, 85 Hz, and 40-ish Hz, respectively.
• OFS_ERR_OUT sees the bump at what seemed to be a loop troubleshooting. The top plot on "PcalX_DTT_zoom_ERR.png" shows the bump appearing at ERR_OUT.
• Troubleshooting did not solve the issue. We did not see any bumps this morning so the issue seems to be gone.

Some ideas on where to look for the source:

• AOM issues
• "RF whistling"

There was a similar issue on (70817) where the "OFS servo was saturating" after Detchar injections. The OFS was not happy after troubleshooting this time.

Further investigation is on process.

Ryan C, Austin, Oli, Jeff K, Betsy, Dave, Eric, Fil, RAL/CIT team and Rahul

Happy to report that we have finished the assembly of our first A+ HAM Relay Triple Suspension (HRTS) (freestanding version) with Class A parts as per the assembly procedure described in D1900449_V7.  HRTS is a new small scale triple pendulum suspension required for Balanced Homodyne Detection system. This is first of the twelve suspensions we have to deliver for both the sites (six each for LHO and LLO, which includes one spare per site) for observing run O5.

HRTS comes in two configuration, freestanding (table mounted which is discussed in this alog) and suspended (to be built, will be attached to the new beamsplitter suspension BBSS). The details about the assembly and characterization along with pictures are discussed below,

Attachment01 shows the AR side of the SUS, attachment02 shows the HR side. For isometric view, please see attachment03.

This multistage suspension (three suspended stages) has blade springs at the upper stage and top mass for vertical isolation. There are two blade springs at the very top stage (D2100389) as shown in the picture here. The blade spring are mounted on spring loaded clamps which can be adjusted for Yaw dof and height (sus point). The two wires (diameter 0.006in) from the two top stage blade springs suspends the Top Mass (D2100362) which has four blade springs, as shown here.

Wire diameters are as follows:-

Top Stage to Top Mass = 0.006in, length 115mm

Top Mass to Penultimate Mass = 0.004in, length 115mm

Penultimate Mass to Optic = 0.0025in, length 160mm

Suspended masses (as per specifications):-

Top Mass = 750gm

Penultimate mass = 802gm

Dummy optic = 300gm

The Top Mass blade spring clamps are spring loaded (just like the top stage) which gives them the ability to adjust for blade tip height. We use a tool (T2400063) provided by the RAL UK team for measuring (while adjusting) the blade spring tip height (this tool can only be used for this stage) - as shown in this picture. A calibration block has also been provided for calibrating the tool before using it. The penultimate mass is suspended from the top mass blade springs using four wires of diameter 0.004in. The Optic (dummy optic for now) is suspended using two wires in a loop from the penultimate mass - see picture here. All the wires were pulled using their dedicated wire jigs, which defines the wire length and position within the wire clamps.

We had some issues with wire installation procedure (wires at the top mass stage kinks/breaking too often during handling). After discussions with colleagues here and at RAL we now have a new tool (currently under fabrication) which will aide in wire installation procedure. Also, with practice we are getting better at handling wires of this thickness (thinner than human hair).

Once the assembly was complete, we measured and adjusted the height of the top stage blade springs, which comes out to be 22.5mm from the top plate. This adjustment was made to lower the entire chain such that each stage aligns with their respective position, as marked on the frame. The bottom edge of the dummy optic is now approximately suspended at 40.5mm from bottom of the frame (s/n 002) - which as per the design specifications. The other degrees of freedom like pitch, yaw, roll also looks respectable without any major adjustment, although we can further improve the pitch on penultimate mass (using balance mass and pitch adjuster mechanism provided at two stages).

HRTS is controlled using six BOSEMs, their flag/magnet attachment are as per the controls arrangement document E2300341. After attaching the BOSEMs and with little adjustment all six flags looked nicely centered.

Before centering them we measured their Open Light Current (OLC) and calculated the offsets and gains which are as follows,

We have a dedicated test stand at the triples lab in the Stagings building, thanks to Fil, Eric and Dave. The hardware (power supply, satellite boxes, Triple Coil driver, IO, AA and AI chassis) can be seen in this picture. We also have a working MEDM screen for HRTS on X1 controls thanks to Jeff Kissel and Oli. Using this infrastructure we started testing out our suspension. The first challenge was too much vibration in the lab due to turbulent air, vibration due to building doors opening/closing etc. Our suspension is sitting on a heavy optical bench and we have also used a teflon sheet for absorbing some of the ground vibrations. However, since the turbulent air in the lab was too much for us to take any meaningful measurements, hence we covered the SUS in two layers of foil and then clean room cloth - as shown over here. We then exited the lab and it took 30mins or so for things to calm down (while HVACs in the lab are still running). Long story short, we took the first top to top transfer function measurements for HRTS and the plots are attached below. I am attaching the DTT plots as well as the ones processed in Matlab.

If you look at the DTT plots, the coherence is not too bad despite all the external vibrations leading to saturations (we have 18bit DAC). In Matlab we can compare our results against the model (Mathematica from M Barton, imported to Matlab). The Longitudinal (L),Transverse (T) and Yaw (Y) dof aligns nicely with the model, ie all peaks and magnitude looks good. Pitch (P) also has most of the peaks at right places (except a missing peak at 4.5Hz), and is off in magnitude which we are investigating. Vertical (V) is noisy (which is expected as the suspension can be easily excited in vertical motion) and has a cross-coupling from Roll (R) (at around 1.8Hz)? Roll (page8) looks the worst of all especially the shape and magnitude at frequency below 2Hz.

I am still fine tweaking the balancing of the suspension, further isolating it environmental noise and discussing with colleagues to take better measurements. In the meanwhile this is a decent start for us, eleven more to go.

Artem, Sheila

We changed the bias on ETMX while adjusting the drivealign gain to compensate, similar to what was done in 73913.  We might be seeing a small difference in the DARM spectrum between 30-40 Hz. 

We scaled the drivealign gain with the bias, but also adjusted the gain at each step to keep the DARM OLG the same. 

People walking in LVEA and plugging in CM board seemed to cause some glitches. no evidence of people walking on seismometers from 16:37 on.

The first attachment shows the DARM OLG after gain adjustments.  The second attachment shows long spectra at the various biases we checked.  We also looked at coherence with the susrack magnetometer (Y)  and ESD power monitor 18 V, and saw no coherences there.

The third attachment shows a comparison of the spectrum with 190V bias and 415V, making it easier to see that there might be a difference in noise.  A next step would be to do some repeated steps between these bias settings to see if the difference is repeatable, and doing a broadband PCAL to DARM injection to check that the calibration is as consistent as we think it is between these settings.

We tried the in-lock charge measurements but forgot about the New-DARM configuration so caused a lockloss in the SWAP_TO_ITMX state.

Camilla, Nutsinee, Sheila

• No SQZ time 16:07-16:25  March 20th UTC
• Camilla measured NLG at this time: amplified seed 0.170 counts, unamplifed 0.0098 (dark offset too small)= NLG 17.3
  • while Camilla was doing we added the seed pzt scan to the SQZ Manager state and turning it off in down.
• moved ADF to 322 Hz, measured 5dB of SQZ with PSAMs at ZM4 150 ZM5 90 (strain guage 8.46V ZM5, -1.26 V ZM5) 16:39 UTC (no long data stretch), filter cavity ASC on, 42 MHz ASC off.
• mean sqz with filter cavity misaligned, ADF off, touched ZMs to maximize BLRMS.  This was confusing and didn't show clear changes due to our alignment shifts.
• We locked FDS anti-squeezing, and we spent quite a lot of time adjusting the alignment of ZM 5 +6, as shown in the screenshot.  We ended up with an alignment that was ~40 urad different in
• A SQZ 18:10-18:16 UTC 107.55 SQZ phase CLF servo polarity was negative ref 3
• SQZ 18:23-18:29 SQZ phase 207.1 clf servo polarity positive ref 9
• SQZ +10 18:30-18:35:29 217.53 SQZ phase clf servo positive ref 18
• SQZ  -10 18:36:30 SQZ phase 197.62 CLF polarity positive ref 19
• mid sqz 18:44-18:50 SQZ ang 240.83 polarity positive ref 20
• mid sqz 18:52:25-18:59 SQZ ang 95.76 polarity positive ref 21
• sqz clf flip 19:02-19:08 polarity negative phase 35.08 ref 22
• no sqz time: 19:12 until lockloss at 19:25:12 UTC ref 23

Screenshot of different sqz angles attached.  Nutsinee's final attachment compares sqz with two different CLF servo signs.