Addressed TCS Chillers (Thurs [Jun25] 934-945am local time) & CLOSED FAMIS #64383.
(Still not getting FAMIS notifications and not clear which FAMIS Schedule LHO is supposed to use due to duplicate schedules being generated with the new LIGO Lab FAMIS transition.)
For measurements below, measuring from "top" of the red floaty ball.
Recorded our added mass configuration on the Top Mass. See diagram and associated pictures.
Top Side: 100g total, both on Front (by convention, so the side opposite the OSEM flags)
Bottom Side: 200g total, 100g on Front, 100g on Back
Total Added: 300g
See the diagram.
Jeff, Betsy, Arnaud, Oli
Yesterday afternoon we went to the BBSS QOSEM satamp and checked the coil resistance. We did this by putting the BBSS in SAFE and then unplugging the Satamp to Duopus cables one by one. Each of these three cables have the pins for two QOSEMs, split as CH1 + CH2, CH3 + CH4, and CH5 + CH6. Each cable was unplugged and then the pins for each coil probed. Below are the results. These values are all pretty similar.
| Coil Resistance (Satamp to Duopus) | ||||||
| CH1-2 (SUS_BS_81) | CH3-4 (SUS_BS_82) | CH5-6 (SUS_BS_83) | ||||
| Channel | CH1 | CH2 | CH3 | CH4 | CH5 | CH6 |
| CH Coil Pins | 23 -> 10 | 18 -> 5 | 23 -> 10 | 18 -> 5 | 23 -> 10 | 18 -> 5 |
| OSEM Mapping | F1 | F2 | F3 | SD | LF | RT |
| Coil Resistance | 39.1 +/- 0.1 Ohm | 40.0 +/- 0.2 Ohm | 39.0 +/- 0.2 Ohm | 39.7 +/- 0.2 Ohm | 40.0 +/- 1.5 Ohm | 40.5 +/- 0.5 Ohm |
| Notes | Larger than normal variation | |||||
yesterday we had difficulty locking the OMC on the sqz beam. This was because the dither frequency change in 76587 never made it into the SDF safe, although it's written in the OMC guardian. Every time we went through SDF revert it is set incorrectly, then corrected when the OMC locks. I've accepted the change in SDF safe now.
TITLE: 06/25 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: 12mph Gusts, 6mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.06 μm/s
QUICK SUMMARY:
LVEA continues to be Laser SAFE as we move to finish this round of in-chamber work. Ongoing system activities: BBSS, SQZ, CRS, SPI
Untripped EY SEI from Venezuela EQ last night (HEPI to Robust Isolated + ISI to Damped).
Also taking ETMx back to ALIGNED (it tripped due to NorCal EQ and then had the hardware watchdog trip and had been left in damped).
DetChar meeting continues (unlocked kitchen door).
ALSO: Have "Red Flag" Warning from noon-9pm PDT with high winds and dry conditions.
Shoshana, Michael, Oli, Arnaud
CRS is ready for installation in chamber
Next:
Test that positive HOQI signal corresponds to the corner cube moving away from the sensor (same convention as OSEMs)
Calibrate the HOQI PDs to power
Install the fiber feedthrough and start cabling up in chamber
TITLE: 06/24 Day Shift: 2200-2330 UTC (1500-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
SHIFT SUMMARY: Two large earthquakes have rolled through in the last hour, a 7.1 from Venezula and a 6.9 from Japan. EY SEI has tripped, but all suspensions are still damping.
The LVEA is laser SAFE as we continue toward closing out chambers.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 20:18 | SAF | LVEA is LASER -SAFE- | LVEA | NO | LVEA is LASER -SAFE- | 12:18 |
| 22:55 | SPI | SPI LASER IS ON | LVEA | Y | SPI LASER is ON | 18:42 |
| 00:18 | CRS | CRS laser is ON | LVEA | Y | CRS laser is ON | 18:42 |
| 14:45 | fac | kim | lvea | - | technical cleaning | 16:45 |
| 15:06 | fac | chris.tyler.eric.randy | Y1-FCT Enclosures | - | tumbleweed clearing | 16:51 |
| 17:51 | sei | jim | HAM3 | - | CPS work | 19:47 |
| 17:53 | vac | gerardo | HAM3 | - | viewport work | 19:05 |
| 17:53 | pem | robert | EX | grounding studies | 17:55 | |
| 17:54 | fac | randy | lvea | - | WestBaycleanroom lights | 21:53 |
| 18:02 | faro | jason.ryanC | ham3 | - | FARO set up | 19:19 |
| 18:06 | - | Betsy | LVEA | - | Talk to HAM3 crew | 18:47 |
| 18:25 | crs | michaelR | lvea | - | Turning OFF CRS laser + CRS checks | 18:43 |
| 19:07 | vac | gerardo.jordan | Y-BeamManifold | - | scaffold search | 19:19 |
| 19:42 | CE/pem | carlos.shrey | x-arm | n | seismometers placement along arm | 23:15 |
| 20:12 | ops | betsy | lvea | n | walkthru | 20:32 |
| 20:26 | detchar | jenne group | lvea | - | DetChar tour | 21:19 |
| 20:29 | faro | ryanC.jason | lvea | - | faro @ham3 | 22:47 |
| 20:43 | SEI | Jim, Michael, Shoshana.mitch | LVEA | - | BSC2 weighting (all but Jim out @2222) | 23:04 |
| 20:55 | spi | oli.jeff.arnaud | lvea | - | susr2 check (please no BBSS work!) | 23:30 |
| 21:01 | vac | jordan.gerardo | lvea | - | viewport inspection @ham2 | 21:30 |
| 21:20 | ee | fil | lvea | - | checking cables at PSL Closet+tcsy rack | 21:28 |
| 22:45 | VAC | Jordan, Jake, Owen | LVEA | n | Checking on CP1 RGA | ongoing |
| 23:17 | PEM | Robert and others? | EX | n | Magnetometers | ongoing? |
| 23:30 | SEI | Arnaud | LVEA | n | CRS work | ongoing |
Ryan S, Sheila, Eric O, Camilla, Keita. Follow on from 90698.
This morning Sheila and Eric adjusted the SQZ IFO ASC to run centering loops from AS_A and AS_B to ZM4 and ZM5, in preparation for running OMC scans with a variety of psams settings. See attached.
Starting trying to take OMC scans with the SQZ beam, with less misalignment than we saw in 90615, to eventually use Begum’s scripts to repeat with different PSAMS settings.
Sheila and Ryan, went to the misalignment peak with the PZT offset and then started a dither over it and tired to change OM3 and OMC alignments but couldn't reduce the size of the beam, only make it worse. They undid the SRM alignment change, this did not help.
Sheila and Keita then tried to lock the OMC on the 00 mode, as in 80010 but it was not stable. Sheila then put a dither on the OMC PZT and we maximized the TEM00 peak with OMC and OM3 SUS, we improved the flashes 10%. OMC from (P-1900, Y -400) to (P -1300, Y -480) and OM3 from (P -1400, Y +95) to (P -1400, Y +65). The OMC scan after that was at a much better alignment, see data attached and below. Strangely this is showing worse mode mismatch than the the alignment was poor in 90615.
Shortly after this HAM5 and ZM6 WDs tripped (CPS WD trip) and afterwards, the OMC scan alignment was poor again. Sheila made some progress on getting the code to work /userapps/release/sqz/h1/scripts/HAM6_related/ham7_psams_sweep_QPD_center.py, but more work is needed.
| PSAMS | Dark | TEM00 | TEM02 (Mis-match) | TEM01 (Misalignment) |
Mismatch*
(% of TEM02)
|
| ZM4 6.2V, ZM5 -0.4V | 0.0209615 | 0.620414 | 0.0397442 | 0.0409605 | 3.04% |
*calculated with TEM02 / (TEM00 + TEM02)
We tried changing PSAMS while SQZ ASC was on, it took 30s to settle. The misalignment peak did change between scans but only a small amount. Misalignment peak was around 8.5% and then 10% of 00 peak.
We did not manage to get back to the lowest misalignment as above, even with dithering PZT2 around the 00 peak and maximizing with OMC and OM3.
TITLE: 06/24 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
Started out the day with a large "local" earthquake (this caused a Hardware Watchdog trip--see Dave's alog).
Went laser SAFE to switch to different work for the BBSS (and allowed for a DetChar tour and other activity without the need for laser goggles).
LOG:
Adjusted the dark offset of OMC DCPDs in A0 and B0 filters and zero-ed A and B offsets (and disabled them).
| H1:OMC-DCPD_A0_OFFSET | A_OFFSET | B0_OFFSET | B_OFFSET | |
| Old | -158 | 68e-6 | -134 | -803e-6 |
| New | -81.6 | 0 | -89.5 | 0 |
I don't know exactly why people split these offsets in two different places, maybe that's because dark offset scripts was written when 512k ADC didn't exist?
Let's use A0 and B0 offsets for ADC rather than putting ridiculously small numbers in A and B.
To aid in testing the BBSS M1 QOSEM coils for issues related to the cross coupling (see LHO alog 90665), below is the DC tranfer function from DAC counts (16 bit) to the voltage across the QOSEM coils. This assumes a coil resisatnce of 35ohms, which is the nominal spec, but they can vary by ~10%.
DAC drive to voltage across the coil = 3.18e-5 V/cts
I've made plots comparing three sets of transfer functions.
Here are the comparison plots between the three. The most important plots right now are the P2Y and Y2P plots. They can be found in /ligo/svncommon/SusSVN/sus/trunk/BBSS/Common/Results/allbbss_2026_teststand_vs_chamber_BOSEMs_vs_QOSEMs/ and have been committed as r13043.
Side note: Since Arnaud and I realized our calibration DAC compensation mistake yesterday (90720), I have reanalyzed the last few measurements, including the three being compared here, using /ligo/svncommon/SusSVN/sus/trunk/BBSS/Common/MatlabTools/plotBBSS_dtttfs_M1.m. These are three measurements that had been taken with the 28bit DAC compensation gain in the COILOUTF filter set to gain(4096) = gain(2^12), which is the correct compensation when accounting for the difference in DAC counts between a 28bit and 16bit DAC. This compensation means that the calibration factor in plotBBSS_dtttfs_M1.m should've just accounted for the 16-bit DAC (since the rest was already accounted for), but it had been set to 18-bit DAC, so I reran them. The measurements that had been reanalyzed were 2026-05-26_1700, 2026-06-01_1700, and 2026-06-10_1700, committed as r13041.
Note: All three of these measurements were taken before the sign swap was implemented in the COILOUTF filter banks.
Following up from 90723 we (roughly) calculated the BS top mass drive (cts) to bottom mass motion (urad) measured by the oplev. This will allow to (re)calibrate the top mass sliders in physical units. The screenshot attached show the ndscope used for this calculation. The data was taken before the sign convention was corrected (90725), so the signs were flipped from the ndscope in the table below:
| +0.15 [P_urad/P_cts] | +0.35 [Y_urad/P_cts] |
| +0.1 [P_urad/Y_cts] | +1.65 [Y_urad/Y_cts] |
The slider calibrations to implement (at next opportunity) in the gain of the slider filterbanks are :
P calibration = 1/0.15 = 6.6 [P_cts/P_urad]
Y calibration = 1/0.35 = 0.6 [Y_cts/Y_urad]
Follow on from 90719. Jennie, Keita, Betsy, Sheila, Camilla, Ryan S, Oli, Arnaud
Before doing any more mechanical BS offloading, we decide to put ITMX back too it's March DRMI top mass osems values, as described in alog90708, we expected we'd need to move ITMY to compensate for this, but did not.
Used the SQZ beam. Mis-aligned ITMY. Moved ITMX towards correct Pit value. Compensated with BS Pitch and Yaw to keep beam on AS AIR. Moved PR3 to keep beam on ISCT1 REFL camera. We did not fine tune fringing. Keita opened PSL light pipe an further tuned PR3 to get PSL beams both on cameras. Ending sliders here. Ndscope of the fringing on AS_A/B here.
BS pitch is now close enough we will do no further mechanical pitch offloading now, it will be Yaw offloaded SEI system. Arnaud checked the oplevs to known that for the -1500 counts of BS yaw slider, this is ~ 2.5mrad.
Both ITMX and ITMY are now at their March DRMI top mass osems locations (11:02 PDT 19 March 2026).
|
Starting today
|
After ITMX moved back to DRMI M0 OSEMs
|
|
| ITMX |
P -280, Y +94
|
P -96, Y +104
|
| BS |
P +520, Y -1677
|
P +115, Y -1557
|
| PR3 |
P -247, Y -245
|
P -195, -242
|
Given this calibration the newest BS offsets (P +115, Y -1557) [cts] corresponds to the calibrated offsets (P +17.25, Y -2569) [urad at M3] when only considering the P2P and Y2Y calibration. When taking into account the cross coupling those offsets are (P -138, Y -2529) [urad at M3].
This defines the amount of yaw motion (and direction) to offload this offset with HEPI : Rotate HEPI ~2.5mrad clockwise
As per WP 13208 the cdswiki was down yesterday for an OS upgrade.
Below is the analysis for data taken on the FC path: between ZM1 and ZM2 and between ZM2 and ZM3, with Nanoscan, see Camilla's log 90573. As a reminder, ZM1 are flat optics, ZM2 is a PSAM with variable curvature, FC1 HR side is flat, AR side is curved with RoC ~1m.
The data suggest that the OPO mode is slightly different from O4 OPO, and also strongly suggest a new optimal ZM2 PSAM voltage can be found within the range.
We measured the beam profile at 5 different points after ZM1 with A:L2 lens at its nominal 0 position (sled that the lens lives on is flush to its translation stage on both front and back edges). At the last point with A:L2 at 0, we realized it would be pertinent to measure beam profiles for the two extremities of the A:L2 translation stage: -13 mm, which is closer to ZM1 by 13 mm and +17 mm, which is 17 mm further from ZM1. We then proceeded to take 5 measurements (again downstream from ZM1) for each of these lens positions. The nanoscan screenshots for each measurement are attached in the .zip folder.
The attached gif shows the beam waist position estimation extracted from the beam profile scans downstream ZM1, for all three A:L2 positions. The "target" and "O4 x/y" come from Keita's log 59515. The overlap plot attached shows the field overlap in percentage for all three A:L2 positions, with target and O4 beam parameters. With A:L2@0, the overlaps are above 99%, which bodes well for the FC mode matching prospects. There could potentially be a better mode matching solution to the "target" or "O4" for A:L2 between 0 pos and -13mm pos. However, the following measurements betwen ZM2 and ZM3 suggest fine-tuning of A:L2 position will not be necessary.
We also measured beam profile between ZM2 and ZM3 for three different points, setting ZM2 PSAM voltage to 4 different values at each point. The "nominal" O4 strain gauge (S.G.) for ZM2 has been 3.15 V, which corresponds to ~ 60 or 90 V pzt supply voltage depending on which direction one scans from. The edges of the psam range are 0 V and 196 V, which corresponds to ~1.2-1.3 V and ~6.04 V S.G. respectively. In the interest of more uniform sampling of the available psam curvatures, we also chose to sample 4.5 V S.G. (~120 V or 150 V).
This table shows experimental data mapped to radii of curvature of the ZM2 mirror, using Camille's E2100298. The exact PZT strain gauge/ PZT supply voltage that gives a certain RoC is affected by the hysteresis curve i.e. sweep direction.
| Strain Gauge (V) | PZT Supply Voltage (V) | RoC (m) with increasing scan | RoC (m) with decreasing scan |
| 1.3 V | 0 | 0.8211 | 0.82202 |
| 6.0x V | 196 | 0.8911 | 0.89114 |
| 3.1x V | 60 (d) or 90 (i) V | 0.8523 | 0.85025 |
| 4.4x V | 120 or 150 V | 0.87534 | 0.87242 |
Attached gif for propagation between FC1 and ZM2 show esimated beam parameters for all four SG cases: 1.3, 3.1x, 4.4x and 6.0x V. The exact values for the strain gauge varied from one beam profile position to the next, however it should be good enough to tell if we have enough range on ZM2 or not.
The gif switches between different SG values once every 2 second, the lefthand plot is useful in looking at the beam divergence near FC1 while the righthand plot is a zoom-in around the beam waist. Looking at the estimated beam waist position for 1.3 V and 3.1x V cases switching across the "FC x/y waist", "VOPO target waist", ''O4 x/y waist", we can guess there could be a better mode matching solution between these two SG values. "FC x/y waist" comes from the Finesse eigenmode solution for the FC path (thanks Kevin Kuns!), target and O4 values are the same from the above-mentioned Keita log, assuming ZM2 curvature to be 0.85025 m (3.15V SG), and the following distances between the optics: A:M3 --> ZM1: 158.2 mm, ZM1--> ZM2: 1498.625 mm, ZM2 --> ZM3: 1821.497 mm, ZM3--> FC1: 1000.261 mm. Camilla extracted these distance values from D1900365-v1.
Knowing the applied PZT voltage and the corresponding RoC, we can use the measurements at 3.1x V and 1.3 V to estimate the mode matching we would obtain if we swept the RoC between that of these strain gauge values. The attached FC mode matching projection plot is computed by taking beam parameter estimated from the beam size measurements for 3.1x V, propagates the beam back to ZM2, unapplies the estimated RoC (decreasing RoC value was used informed by data, indicated in bold in the above table), then reapplies the RoC between these two values, after the overlap with the FC eigenmode is calculated. This projection suggests that mode-matching points with >99% overlap for both x and y axes are accessible. Clearly, there is varying astigmatism with strain gauge setting, see beam profile plots where 3.1x and 6.0x V shows beams with smaller astig. than the other two points. Since the PSAM characterization data gives only a single RoC number rather than separate x/y effective curvatures, the projection should be interpreted as approximate. In practice, the final optimization should be done empirically.
The effect of the astigmatism is also apparent in this defocus vs beam size at FC1 plot that shows mode matching contours. The calculation is made at the FC1.p2.o plane in Finesse.
The beam width data kindly tabulated by Camilla, the R(V) data from Camille's dcc E2100298, and the analysis code .py are attached, in the .zip. Fair warning, the analysis code also makes a bunch of plots I find useful to look at but another user may find irritating :)
Code for the data points upstream of ZM2 attached. The measured beam widths and their corresponding position are listed in the script. The real raw data with the screenshots from the beam profiler UI is attached to the main log.