WP13346 Retire CP1 Overfill System
Erik, Dave:
As a first step in dismantling the daily CP1 overfill system, I stopped and deleted its systemd service on zotvac0. Erik and I verified that this service was not being managed by puppet, and to further verify this we let the puppet agent run and then rebooted zotvac0.
To keep the EDC green for the rest of this week, I installed a dummy IOC on the container cluster which serves those CP1 channels being acquired by the EDC.
Project History
This might be good time to give a brief history of this project. The CP1 LN2 level sensor failed way back in August 2021. For many months we ran the overfill manually. Chandra suggested an automatic system be installed and the first version of my code was rolled out 17 December 2021 just before the holiday shutdown. It then ran daily through to 01 May 2026 when the CP1 regeneration was started. During this time the code had ran daily for 1595 days (4 years, 4 months, 14 days), skiping just 31 days (1.9%). During this time several improvements were made: ramping the LLCV opening to reduce mechanical noise, using rate-of-change on the thermocouples to indicate LN2 flow, sending text messages at start and completion of each fill.
After in-chamber crews physically moved the BS, I was able to restore both the IMC flashes and the sqz beam reflected by ITMX as well as ITMY in AS as well as ISCT1 REFL camera by just using the BS sliders. sqzbeam_as_isct1.png and the video PXL_20260625_204834048TS.mp4
show the sqz beam in the AS (left) and ISCT1 (right) camera when IMC was misaligned, while PXL_20260625_204905669TS~2.mp4 is the video of the IMC flashes when SQZ beam diverter was closed.
BS top suspension offsets were H1:SUS-BS_M1_OPTICALIGN_P_OFFSET = 107.00 and H1:SUS-BS_M1_OPTICALIGN_Y_OFFSET = 441.00.
Right now F2 coil is using ~10% of the DAC range (~13.3 million counts out of 135 million), F2 ~ 6%, and others are small. See BS_DAC_range.png. I don't think further trying to relieve this will be fruitful or useful.
Following on from alog 90738, we last had the corner alignment with the BBSS at PIT +115 and YAW -1557. We decided to offload this YAW to the HEPI so the team embarked on that yesterday, likely another alog from IAS/SEI on that move later. Today we went and looked at the corner beam pointing with Keita refining the BBSS alignment to PIT +107, YAW +441 (see his alog coming).
So now, Jim and Mitchell are embarking on Actuator attachment at the piers. We will relook at the BBSS cage position with the FARO shortly after they are complete, and then re-peek at the corner alignment likely early next week.
Meanwhile, the BBSS PIT to YAW cross coupling investigaton continues...
We took a FARO shot before the HEPI rotation, shown in the 1st attachment, and one after, shown in the 2nd attachment. The FARO measures the yaw rotation at 0.0773°, or 1.35 mrad, in the clockwise direction (44.9990 - 44.9217 = 0.0773; direction is CW since we rotated closer to the +X axis). At this point we had some interference between one of the spring caps for the -X/+Y HEPI pier and the -X blue HEPI crossbar, so we could not rotate any more (Jim cleared the interference this morning by removing the spring cap and grinding some material away). Regardless, this was enough to get us to an acceptable place. In addition to the rotation, we did see some -X position shift in the BBSS cage, as can be seen in the attachments. Averaging out the the rotation gives a shift of 1.4 mm in the -X direction. From the test stand alignment the BBS optic itself was +0.3 mm in the X direction w.r.t. the ISI, so the BBS is now roughly -1.1 mm from its ideal X axis position. Using the same position tolerance from the test stand of +/-1.4 mm, this means we're pretty close to the edge for X axis position but still within, so onward we go.
We'll measure the position again once all the HEPI actuators have been attached to ensure position is still good, as there is potential for things to move during actuator attachment.
Jeff, Arnaud, Betsy, Oli
Yesterday we checked the coil response for the BBSS QOSEMs. We did this at the BBSS M1 QOSEM satamp. Everything is looking good and as we expected.
We did this by putting the BBSS in SAFE, then unplugging the db15's that go to the coil drivers. In their place Jeff plugged in a fancy breakout board that separated out each of the 4 channel pins. The resistance of each of the reading device channels is listed below:
| Coil Voltage (Satamp to Coil Driver) | ||
| Resistance of reading device (no uncertainty to 0.1 Ohm) |
Used to measure
|
|
| Breakout (B/O) Channel 1 | 24.3 Ohm | CH1 (F1), CH5 (LF) |
| Breakout (B/O) Channel 2 | 20.9 Ohm | CH2 (F2), CH6 (RT) |
| Breakout (B/O) Channel 3 | 23.1 Ohm | CH3 (F3) |
| Breakout (B/O) Channel 4 | 23.4 Ohm | CH4 (SD) |
With this channel breakout board we then went channel by channel to measure voltage. We turned the master switch ON so counts can head out from the COILOUTF filter bank. For each channel, we noted the COILOUTF filter bank gain sign, and if there was any voltage read out when no offsets were put in. Then we put an OFFSET in the COILOUTF filter bank and noted the voltage that we were reading. We did this for multiple OFFSETs for each channel. After testing each channel, with an offset still on, we would check the other channels to see if anyone else was seeing anything more than their default reading with no offsets, which they never saw anything different from that. Here is that data:
| Cable | SUS_BS_85 | SUS_BS_87 | ||||||||||
| Channel | CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | ||||||
| OSEM | F1 | F2 | F3 | SD | LF | RT | ||||||
| COILOUTF gain | -1 | -1 | 1 | 1 | -1 | 1 | ||||||
| COILOUTF OFFSET | Voltage (V) (+/- 0.5 mV) |
COILOUTF OFFSET | Voltage (V) (+/- 0.5 mV) |
COILOUTF OFFSET | Voltage (V) (+/- 0.5 mV) |
COILOUTF OFFSET | Voltage (V) (+/- 0.5 mV) |
COILOUTF OFFSET | Voltage (V) (+/- 0.5 mV) |
COILOUTF OFFSET | Voltage (V) (+/- 0.5 mV) |
|
| 20,000 | -2.825 | 20,000 | -2.837V | 20,000 | 2.848 | 20,000 | 2.839 | 20,000 | -2.826 | 20,000 | 2.836 | |
| 10,000 | -1.413 | 10,000 | -1.419 | 10,000 | 1.424 | 10,000 | 1.419 | 10,000 | -1.413 | 10,000 | 1.418 | |
| 0 | 0 | 0 | -1.00E-03 | 0 | 0 | 0 | 0 | 0 | -1.00E-03 | 0 | 0 | |
| -10,000 | 1.412 | -10,000 | 1.416 | -10,000 | -1.424 | -10,000 | -1.42 | -10,000 | 1.412 | -10,000 | -1.418 | |
| -20,000 | 2.825 | -20,000 | 2.83 | -20,000 | -2.849 | -20,000 | -2.839 | -20,000 | 2.825 | -20,000 | -2.837 | |
| With OFFSET of -20,000 (in V): | With OFFSET of -20,000 (in V): | With OFFSET of -20,000 (in V): | With OFFSET of -20,000 (in V): | With OFFSET of -20,000 (in V): | With OFFSET of -20,000 (in V): | |||||||
| CH1 (B/O Ch1) | -- | CH1 (B/O Ch1) | 0 | CH1 (B/O Ch1) | 0 | CH1 (B/O Ch1) | 0 | CH5 (B/O Ch1) | -- | CH5 (B/O Ch1) | -1.00E-03 | |
| CH2 (B/O Ch2) | -1.00E-03 | CH2 (B/O Ch2) | -- | CH2 (B/O Ch2) | -1.00E-03 | CH2 (B/O Ch2) | -1.00E-03 | CH6 (B/O Ch2) | 0 | CH6 (B/O Ch2) | -- | |
| CH3 (B/O Ch3) | 0 | CH3 (B/O Ch3) | 0 | CH3 (B/O Ch3) | -- | CH3 (B/O Ch3) | 0 | |||||
| CH4 (B/O Ch4) | 0 | CH4 (B/O Ch4) | 0 | CH4 (B/O Ch4) | 0 | CH4 (B/O Ch4) | -- | |||||
You can see that the voltage signs are all consistant with the sign of the OFFSET * COILOUTF gain, and the values are all pretty consistant as well.
After we were done reading out the voltages for SUS_BS_85, we put offsets of -20,000 in F1, F2, and F3 and checked the voltages on all three channels. All three channels read the same voltage as they had when we had tested them individually at -20,000 counts. That table is below.
| OFFSET of -20,000 for F1, F2, F3 (in V) | |
| CH1 (F1) | 2.825 V |
| CH2 (F2) | 2.831 V |
| CH3 (F3) | -2.849 V |
Some pictures of the "DAC Voltage to Coils" setup that gathered the above data. 2026-06-24_QOSEM_CoilDriveDACVoltage_BigPicture.jpg Zoomed out photo of SUS_BS_85 cable disconnected from the Coil Driver 1-4 channel input to the QOSEM satamp chassis in SUS-R2, and connected to the dummy OSEM system (what Oli calls the "fancy breakout board"), with a DVM reading out the voltage across the resistors. In the pictured case, we're using the DVM (placed in the rack for convenience) reading out the voltage across the Channel 1 resistor of the dummy OSEM which is connects across the + and - legs of the Channel 1 output of the cable (i.e. F1). 2026-06-24_QOSEM_CoilDriveDACVoltage_Zoom_DummyCoilResistor.jpg Zoomed in photo of the clip leads hooked across the resistor. Since the sign of the voltage is critical, I made sure to find a dummy OSEM that had the + and - legs clearly called out, ensuring the positive, red, signal lead for the BNC connection was connected to the + leg of the drive signal, and black to the -, return, leg. 2026-06-24_QOSEM_CoilDriveDACVoltage_Zoom_DVM.jpg Zoom in photo of an example of the DVM read-out voltage during the given offset (in this case, it was the CH1, F1, 10,000 [ct] offset -- multipled by the -1 COILOUTF gain -- to read -1.413 [V]_DC). Note -- again because signs are under question in this investigation -- careful attention was paid to ensure the orientation of the BNC to banana adapter into the DVM; connecting in the standard "nub is negative" configuration i.e. the shield of the BNC cable, connected to the black clip lead on the other end, is connected to the black COM input of the DVM. 2026-06-24_QOSEM_CoilDriveDACVoltage_DisconnectedSatampCable.jpg Zoom in photo of where the SUS_BS_85 DAC drive cable connects into the QOSEM satamp.
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 | |||||
Picture of the setup: (in this instance) the QOSEM CH 3-4 (i.e. F3 and SD) SUS_BS_82 cable is disconnected at the QOSEM satamp in SUS-R2, and its "to chamber" end is connected to a standard D25 breakout board. Clip leads are connected across the pins as described above to gather the coil resistance. These results are as expected: the QOSEMs are up-cycle bodies and coils from BOSEMs, which are known to have resistance of ~40 [Ohm], in this case 40 +/- 2.5%. Note, this is markedly different than the 35 +/- 10% [Ohm] -- 31.5 to 38.5 [Ohm] -- assumed in LHO:90743. Maybe Tom is assuming that this is the coil resistance if measured directly at the coil flexi-circuit terminals, and the "extra" resistance is from the long cable run to the chamber which is what we typically measure. However, the 2.5% spread in coil resistance values between F1, F2, and F3, is NOT enough of an imbalance to explain the worrisome P to Y cross-coupling seen at DC (LHO:90728 and LHO:90739) and in the M1 to M1 transfer functions (LHO:90765).
Indeed, the ~35ohm nominal coil resistance I quoted in LHO:90743 is measured at the QOSEM uDB9, so not including cable or feedthrough resistance.
After assembly I measured the coil reistance of these LHO BBSS QOSEMs to be:
| QOSEM SN | LHO BBSS Channel | Coil Resistance at uDB9 |
| S2600012 | F1 / CH1 |
34.6 |
| S2600009 | F2 / CH2 |
35.6 |
| S2600013 | F3 / CH3 |
35.1 |
| S2600008 | LF / CH5 |
35.7 |
| S2600011 | RT / CH6 |
36.4 |
| S2600010 | SD / CH4 |
35.6 |
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.
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.
I wanted to try to get an idea of what sort of astigmatism we're seeing on the FC path. I was able to get good fits of Begum's data right after ZM1. This indicates that the astigmatism coming right off of the VIP looks quite good ( 99.9 +/- 0.1% overlap between X and Y). Plots of the fits are attached for each lens position.
I wasn't able to get particularly convincing fits of the data after ZM2. The points are several Rayliegh ranges away from the waist and I found that the fits were quite sensitive. I could get answers anywhere between 98%-100% mode overlap between X and Y depending on what parameters I used in a la mode for the seed waist. Someone might be able to do a more sophistocated fit of the data, but I think one would want to measure closer to the waist to better constrain the fit and get a more precise estimate of the astigmatism added by ZM2.