CamillaC, CoreyG, RyanS (locked up the IMC at low power for us, with help from Sheila & JennieW)
For reference, see the following alogs & DCC page: alog61866, alog17788, D1201430
Initial delay to this work was trying to get low power (250mW) from the IMC for a beam to use for this check. However, we now have JAC, so this added some complications for low-power locking; additionally, IMC locking is still fairly new & fresh post-recent-vent-work.
Once we had a nice beam to work with we went out to HAM2. Before we went upstairs, we grabbed an IR card, lexan plate (from the standard guillotine), and a CDS laptop. This time around we don't have the scaffolding at HAM2's West Side, so we decided to climb up from the East Side since we had several blank flange ports to use for hand/foot holds. For each climb, we stepped on the steel platform above the HEPI cage (but this still would break IMC lock...but it came back fast). Did NOT use fall protection since there is a handrail right where we would be working atop HAM2.
Steps For The Check:
Below are photos from this activity along with "before" photos of beams as we found them. Camilla will alog the "after" photos of how the beam looked after some PRM tweaks.
Attached are photos of the beam as we left it on the steering mirror and beamdump.
We moved the PRM alignment sliders +500urad in Pitch to get the beam unclipped looking. This was saved as an addition to the misalignment values in sus/h1/guardian/susconst.py, see attached. We then reloaded SUS_PRM and checked when taking it t misaligned that the top mass osems when to the location we expected.
During this work PRM alignment sliders nominal was Pitch -1115, Yaw -270
As a part of trying to diagnose the mode cleaner locking issues, I ran a transfer function of MC2 M3 to M3 to see if everything looked normal. Unfortunately, there is nothing in the sus svn to provide a reference, so we don't know what it is supposed to look like.
I immediately noticed strange behavior above 10 Hz that is related to the BIO state. I thought I was on to something, however, I found out that this is a long known problem that comes from coil driver coupling to the osem. Nonetheless, here is a measurement, in case anything else jumps out as strange to anyone.
I took two transfer functions in BIO state 4 - Acq On LP On, and one in BIO state 3 (nominal)- Acq Off LP On.
[Oli, Elenna]
Oli has taken some lovely BBSS OLG tfs of the damping loops, which show significant gain peaking for the LPY dofs. Oli and I took time to determine how much we should reduce the gain for each of these dofs to get enough phase back to reduce the gain peaking. For each dof we were able to reduce the gain peaking from roughly 15 dB to 6 dB.
For length and yaw, this is a reduction of gain of a factor of 2, for pitch we needed a factor of 2.5
Based on the loop suppression, each dof still shows 20 dB suppression around the modes, so I think should be good for locking.
I put the new gains into FM4, and SDFed this filter to be on. This ensures that the BBSS epics gain should still be -1 for all dofs.
The only tricky dof was yaw, since there is a sharp feature close to 2.5 Hz. However, the resulting OLGTF looks fine.
The attached plots show reference traces from Oli's measurements, and live traces showing the new damping with the reduced gains. Final image is SDF screenshot.
I took a set of OLGs yesterday for the BBSS now that it's in vac. I was just comparing them to the last BSFM ones that we have from 2023 (in blue), which obviously will look a bit different.
Settings
- BS in HEALTH_CHECK but with:
- DAMP ON (you need damping on to run OLGs)
- HEPI and ISI are in their nominal ISOLATED states (ISI no ST2 boost)
Data
/ligo/svncommon/SusSVN/sus/trunk/BBSS/H1/BS/SAGM1/Data/2026-07-20_2200_OLG_tfs/2026-07-20_2300_H1SUSBS_M1_CDBIOState_1_WhiteNoise_{L,T,V,R,P,Y}_0p01to50Hz_OpenLoopGainTF.xml
r13075
This doesn't seem to be related to our problem of locking IMC, but anyway I found a funny DAC behavior for MC2 M3 DAC.
See attached, I'm giving a huge offset to the coil output filter so the coil master output (bottom left) becomes larger than 2**27~134million counts most of the time. The user model DAC output (pink on the bottom right) rails as the master out increases, and so does the IOP DAC output (green on the bottom right), but when the master output goes larger than about 2 billion, the DAC outputs flip the sign and so do VOLTMON and FAST_IMON.
If you look at the transition at around 2 billion master out (between two markers), there seems to be a range where the IOP DAC flips the sign while the user model DAC doesn't, and the IMON as well as VOLTMON drops to zero. Here the driver voltage is not following IOP DAC.
Erik made a new git issue here: https://git.ligo.org/cds/software/advligorts/-/work_items/748
Because we are missing the out of vac crs damping driver, we have to use the ISI to damp the CRS down. This is temporary, we will eventually get a driver for the CRS. This works pretty well for the CRS, but imposes CRS motion on the table. This is enabled by setting the HAM3 ISI RY blend to blend 7, and turning up the gain on the INERT_LO path. The minimum effective gain is somewhere around 10-15, 30 works pretty good, we've gone as high as 100.
We turned the damping on this morning, while Jeff was doing some measurements on one of the MC suspensions, we have kept it running at low gain (3) while the IMC started locking, and so far I don't think this gain interferes with the IMC. There is still some crs signal visible on the RY CPS signal. The CRS is still rung up, and I don't think this gain is sufficient to damp the CRS but I don't see any evidence we are causing problems. I do think a gain of 10 would still allow us to lock (if the CRS is not too rung up) and slowly damp the CRS.
Attached trend shows ISI and IMC trends during the IMC locking this morning. Top trace is (blue) the CRS input into the blends in nrad, second trace (yellow) is the damping signal, third trace (green) is the table motion seen by the RY CPS, fourth trace (red) is the gain applied to the damping signal, last trace is the IMC F. The IMC was finally locked at about -15minutes on the X-axis, you can see we left the CRS damping at gain at 3 when they finally locked, the the CPS is still seeing some of 25mhz CRS motion imposed by the damping, but it doesn't really show up in the IMC signal. I think the bigger issue for the IMC at this time was people climbing on HAM2, for some reason this also seems to be a bigger impact on the HAM3 CPS as well, the extra "hair" on the CPS at -5minutes is not due to the CRS.
Currently with a gain of 3 on the CRS damping, the signal is barely visible on the CPS, not visible in the IMC. CRS is moving about 1 urad peak to peak, CPS motion is ~40nrad peak to peak from the CRS damping. The IMC seems to be losing lock from exterior disturbances (people walking nearby or climbing on the chamber) when the CPS peak to peak is over 200nrad.
Jennie W, Sheila D, Ryan S,
This morning Ryan and co were trying to lock at 200mW to allow the porcupine beam dump for the PRM misalignment beam to be checked at low powers. They were having trouble locking JAC at power below 2W. I improved the alignment of the PZT mirror (H1:JAC-PZT_PIT_OFFSET and H1:JAC-PZT_YAW_OFFSET are the channels) an the JM1 suspension while we were locked at 2W so I could look at the transmitted power.
We seem to be falling out in the 'SCANNING' state during locking at 200mW and if we lock at 2W and try and turn down the power it also falls out.
Sheila checked the JAC guardian and found out that the 'JAC_locked' checker function has a threshold of 0.5 which must be passed before we stop scanning the PZT and jump to the LOCKING state.
It uses the Beckhoff channel H1:JAC-TRANS_A_DC_NORMALIZED which gets normalised by H1:JAC-TRANS_A_DC_NOMINAL to do this check.
H1:JAC-TRANS_A_DC_NOMINAL is a scalar mA value that does not change with input power (Daniel rescaled this value on Monday manually to make the H1:JAC-TRANS_A_DC_NORMALIZED = 1 when the input power is 2W).
This was not happening so the check failed and the guardian jumped to DOWN.
Therefore Sheila has divided the H1:JAC-TRANS_A_DC_NORMALIZED by input power and set the threhold to 0.2, so this check should always come out about 0.5 for a well-aligned JAC and will therefore pass the 0.2 threshold.
I have committed the JAC guardian to the svn at userapps/isc/h1/guardian
Included pic of alignment changes for PZT mirror and JM1 plus input power monitor (H1-IMC_PWRIN_OUT16) and JAC lock check channel (H1:JAC-TRANS_A_DC_NORMALIZED).
There is still some failure mode in the SCANNING state when below 2W. The Beckhoff PZT controller does not trigger on the fringes on the JAC TRANS PD as the inbuilt trigger on the Beckhoff screen for JAC_PZT_SINGLE (lower limit of which is circled in blue is channel H1:JAC-PZT_DRIVER_SCAN_TRIGGER_CHANNEL_1_LEVEL) only works if LSC_CUST_WHITENING screen for JAC-REFL_A PD has a value for H1:JAC-TRANS_A_DC_NORMALIZED (circled in red) above H1:JAC-PZT_DRIVER_SCAN_TRIGGER_CHANNEL_1_LEVEL. We might need guardian to scale these values in the future with the input power if we ever want to regularly lock below 2W.
This isn't really how this is supposed to work. The PD has a normalization coeffcient that should be set so that the normalized power is 1 when the cavity is locked. If we want to automatically scale for different input powers, we should scale the normalization. This could be added to the PD screen using the laser power measured on the PSL table.
Addressed TCS Chillers (Tues [Jul21] 919-934am local time) & CLOSED FAMIS #64385.
For measurements below, measuring from "top" of the red floaty ball.
Ryan S, Camilla
We put the nanoscan profiler downstream of ZM2 (between ZM2 and ZM3) in 6 different locations. We used a steering mirror to get the two locations closest to ZM2.
At each location we took data:
Data is attached, we also have photos of all data. The photos of each location are attached.
Data was taken upstream of ZM2 in 90573
TITLE: 07/21 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
SEI_ENV state: MAINTENANCE
Wind: 2mph Gusts, 0mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY: Commissioning of the JAC and more IMC/corner locking work planned for today along with continued leak checking of the vacuum volumes. Looks like the IMC is staying locked nicely with it only dropping out a few times overnight, where most of these correspond wiht JAC unlocking as well.
Work stations were updated and rebooted. This was an os packages update. Conda packages were not updated.
(Travis, Jordan, Gerardo)
We are using the same setup as before, see here, leak detector attached to the MTP on the XBM. Today's helium background reported by the leak detector was 2.0x10-10 torr*l/sec.
List of items that we have leak checked is below, if crossed no signal detected above the background.
Input manifold:
VP5 (+X side)
VP7 (-X side)
Output manifold:
VP5 (-Y side)
VP7 (+Y side)
Filter cavity tube section B:
Bellows flange connecting to FCB1.
X-manifold
A-1C VP4
A-1C VP5
The 8" port on the X-manifold that was blanked off.
Y-manifold
A-1F VP2
A-1F VP3
HAM5:
A1F2
Viewport, adapter, and components, jig for getting beam from HAM5 to HAM7.
BSC2:
G11
4.5" blank on dome gauge tree adapter. Was gappy, so new gasket installed and re-torqued.
HAM2:
A2F1
A2F2
A2F4
A1F1 <-- signal detected at 4.7x10-10 torr*l/sec, we may replace the seal on the next vent.
HAM3:
D4
This flange is divided into 3 4.5" CF ports, two of the 4.5" are fiber ports, both of them were tested and no leak was detected above the background (D4-1J1 and D4-2J1).
On the last 4.5" port there is a 5WX, and on the first conflat that we tested there is a noticeable gap on the gasket joint, see photo. A leak was detected, and the signal peaked to 1.2x10-09 torr*l/sec, we may replace the seal on the next vent.
We still have other flanges to test on this cross, and the rest of the chamber, but once again the background on the LD saturated due to the leak, we will continue leak checking once the background drops to acceptable numbers.
Other items left to check:
HAM3:
D4 The rest of the flanges on the cross.
A1F3
A1F4
D3
D2
D6
HAM7 and relay tube will be checked later, once the chamber is closed and pumped down.
Leak detector background at start today was ~2.8e-10 TorrL/s. Following Gerardo's convention, the crossed out flanges mean we saw no signal above the background.
HAM3:
D4 The rest of the flanges on the cross.
A1F3
A1F4
D3
D2
D6
IMC Fast path looks good.
I and Elenna went to the floor and measured the OLTF of the IMC loop, injecting into the IMC CM board. UGF was 43.2kHz with 54deg phase margin, a bit high in frequency but not crazy high, and the TF shape was good in amplitude as well as phase. See PXL_20260720_192425851MP.jpg.
FYI the UGF was 38.5kHz back in March 09 2026 (alog 89438).
M3 stage acquire ON/OFF switching question.
We have noticed that the TF from M3 coil input (or drvalign_L2L_OUT) to VOLTMON and FASTIMON changes as Acqire ON/OFF changes. Is this supposed to be the case? And none of these TFs are flat. Is this supposed to be the case?
MC2-MC3-M3_BIO_TF.png shows the TF from M3 DRIVEALIGN_L2L_OUT to FASTIMON for MC2 and MC3 in various BIO states. State 1 (Acq Off, LP Off) and state 3 (Acq Off, LP On, this is our nominal state) give the same TF, which is different from state 2 (Acq On, LP Off) and state 4 (Acq On, LP On). We can say that LP On/Off is properly compensated for in digital but I'm not sure if this means that Acq On/Off is not switching in analog, because I don't know how the IMON in implemented.
Caveats: For MC2 all four states were tested. For MC3 only state 2 and 3 were measured. MC2 and MC3 are consistent with each other. TFs are only plotted for LL because all coils look similar.
FYI, on Friday we have tested to acquire in all four of M3 BIO states and never successfully locked IMC with nominal M3 gain for any state. Even if acquire ON/OFF is stuck to one state in analog (which I'm not sure if that's the case), it's not the only problem.
Today I tested locking with state 2, it didn't lock with nominal gain but it locked with the same reduced gain setting we've been using since Friday (ISCINF_L_GAIN=0.035, DRIVEALIGN_L2L_GAIN=0.2). I switched the state back to state 3 after that.
M3 stage comparison with MC1 and MC3
Screenshot_2026-07-20_11-51-08.png shows the M3 stage DRIVEALIGN_L2L_OUT to M3 witness L transfer function for MC1, MC2 and MC3 from left to right. They all look different but MC2 shows an extra bump at 3Hz.
Other observations
IMC sometimes locks without M3 stage feedback, but fails much more often than with M3 stage feedback, seemingly due to larger kick to the FSS.
Once IMC locks, you can easily switch between the following gains. Both seem to be very stable:
| M3 DRIVEALIGN_L2L_GAIN | M3 ISCINF_L_GAIN | |
| M1 and M2 reduced, M3 reduced further | 0.2 | 0.035 |
| M1 and M2 full, M3 disabled. | 0 (ramp down first) | 1 |
I never successfully transitioned to "all full" actuation (i.e. M3 DRIVEALIGN_L2L_GAIN=1 and M3 ISCINF_L_GAIN=1) nor M3 reduced by 0.2 and M1 M2 full (i.e. M3 DRIVEALIGN_L2L_GAIN=0.2 and M3 ISCINF_L_GAIN=1).
Jeff K, Sheila-
The blue trace in the first sreenshot is with the reduced ISCINF and M3 drivealign gain that Keita describes above, this is a measurement of MCL crossover, which should be (M1+M2+M3)/fast gain.
The red trace in the second screenshot is taken in the same state, with the excitation in M2 lock, which should measure (M1+M2)/(M3+F). These two measurements look the same, which would indicate that the M3 gain is low.
We also repeated the IMC_L measurement with the M3 gain set to 0 and ISC_INF at its normal gain, shown in the first attachement.
TITLE: 07/21 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: LVEA is LASER HAZARD. The dust alarms keep going off for the optics lab since there's so much stuff in the air despite the low wind.
Still some confusion regarding MC2's M3 BIOs. I went into the CER and tried turning the BIO chassis for MC2 off and back on (SUS-C1 U17 and U18). Checked plugs to chassis and to BIO cards. Tightened a couple screws but plugs didn't seem to be loose. Don't think tha would've done anything, but we'll keep looking at it tomorrow.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 20:58 | VAC | Gerardo | LVEA | YES | Leak checking | 23:35 |
| 21:46 | SQZ | Camilla & Ryan | LVEA HAM7 | YES | Profilin beams | 23:57 |
| 00:16 | SUS | Oli | CER | YES | Checking MC2 BIO chassis | 00:23 |
The first image is sdf diffs created after we phased the JAC WFS readouts this morning, the next two are cdsFilt banks that have no filters and a gain 1 but need to be on to route signals from the wavefront sensor readout matrixes I_mtrx and Q_mtrx to the normalised channels H1:JAC-WFS_A_I_PIT_NORM, H1:JAC-WFS_A_I_YAW_NORM, H1:JAC-WFS_B_I_PIT_NORM, H1:JAC-WFS_B_I_YAW_NORM. Confusingly, these are not displayed on the standard 'JAC_WFS_Settings' screens so I might have to put them on there so this doesn't happen in future (this is probably some legacy infrastructure I copied over from the IMC_WFS model blocks that we don't really need).
Sheila, Keita
I went to ISCT1 and Keita aligned PRM. We saw the beam on the periscope, it was making it to the camera. The camera normally gets the transmission through an HR steering mirror pointed at REFLAIR B, this was moved out of the way during in chamber work so the camera could be used. When I put this back in it deflects the beam, so it is no longer on the camera. I think we need two people to realign this camera.
I aligned REFLAIR A + B. REFLAIR A has two ND filters on it that make it easy to align some kind of glint to the diode.
In O4, in the guardian state 101 which is DRMI locking (2W input, PRM aligned), REFLAIR B had 6 counts DC, REFL AIR A was about 2 counts. Now REFLAIR A is 1.8 counts, but REFLAIR B is 3.6 counts. So we should revisit the alignment of REFLAIR B.
Before Sheila put back the splitters for REFLAIR sensors, the ISCT1 REFL camera showed a dark blob with somewhat lighter background (or, more like dark background with even darker blob) as soon as PRM was alighned. I assumed that the beam was not hitting the camera, but when we reduced the camera gain and exposure at the same time, it turned out that the dark blob was actually the beam. Too much light seems to make the camera go in a weird state.
Anyway, this means that the path from PRM to ISCT1 is still close to where it was when in air.
Even though the camera path (with the splitters for REFLAIR sensors in place) is not yet done, we can work on the PRM parking position if we want.