[Jim, Shoshana]
Yesterday when I went to put the cover on the CRS to get it ready to move to the clean area right next to HAM3, I noticed one of the flexures (SN 15) was broken [picture attached]. It's unclear how this flexure broke as it had been locked since last Wednesday (?), and it is strange that only one flexure broke.
We decided that it would be better to install a new pair of flexures and re-suspend next to the chamber rather than in the temporary clean room to reduce the risk of them breaking again. So today we wheeled the table the CRS is on to the space next to HAM3 and I re-suspended the CRS there and roughly balanced it.
Following the procedure outlined in E2600210 and work permit 13356, we moved the CRS to the table and lined everything up so that the CRS baseplate can be bolted directly to the table in one spot.
We installed the fiber feedthrough, and dealt with all the cabling (fiber and DB25) that required Jim to be physically inside the chamber and we'll install the rest of the cable clamps which we can reach from outside the chamber tomorrow and finish connecting all the cables and dog clamping the CRS down (hopefully)
Following the reboot of h0vacey at 15:37 this afternoon the CP7 PID fill parameters needed to be reset. Using the values in h1vacuumsdf's safe.snap file, I ran the following caput commands as user vacuum on zotvac0
caput H0:VAC-EY_CP7_400_LLCV_CTRL PID
caput H0:VAC-EY_CP7_400_LLCV_MAN_POS_PCT 8.80000000000000000000e+01
caput H0:VAC-EY_CP7_400_LLCV_PID_CYCLE_TIME 1.00000000000000000000e+04
caput H0:VAC-EY_CP7_400_LLCV_PID_ITERM_MAX_LIM 2.00000000000000000000e+01
caput H0:VAC-EY_CP7_400_LLCV_PID_ITERM_MIN_LIM -2.00000000000000000000e+01
caput H0:VAC-EY_CP7_400_LLCV_PID_KI 1.00000000000000008180e-05
caput H0:VAC-EY_CP7_400_LLCV_PID_KP 6.00000000000000000000e+00
caput H0:VAC-EY_CP7_400_LLCV_PID_OFFSET 8.00000000000000000000e+01
caput H0:VAC-EY_CP7_400_LLCV_PID_OUT_DEAD_BAND 0.00000000000000000000e+00
caput H0:VAC-EY_CP7_400_LLCV_PID_OUT_MAX_LIM 1.00000000000000000000e+02
caput H0:VAC-EY_CP7_400_LLCV_PID_OUT_MIN_LIM 2.50000000000000000000e+01
caput H0:VAC-EY_CP7_400_LLCV_PID_SETPT_PCT 9.20000000000000000000e+01
caput H0:VAC-EY_CP7_XV400_LLCV_ENABLE_CTRL Enable
caput H0:VAC-EY_CP7_LT400_PUMP_LEVEL_MA_SMOO 9.98999999999999999112e-01
TITLE: 07/01 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
CDS restarts started ~16:15:55 UTC
BS CPS glitch at 18:19:20 UTC <---- lots of these throughout the day.
Dome has been flown back on!
Beam splitter QOsums are shorting, and unfortunately there is now a shortage.
Ground Loops were checked.
PEM Stray light checks in HAM3.
CRS still on going.
CPS still on going.
Patrick went to EY to work on HEPI beckhoff, before he went he had me take the H1:HPI-PUMP_EX_CTRL_RMT_OUTPUT Voltage down Slowly while watching H1:HPI-PUMP_EX_CTRL_RMT_INPUT.
The following channels have been having technical difficulties while Fil and Patrick were at EY working on HEPI Beckhoff:
H0:VAC-EY_Y3_PT410B_PRESS_TORR
H0:VAC-EY_Y2_PT424B_PRESS_TORR
H0:VAC-EY_Y1_PT423B_PRESS_TORR
H0:VAC-EY_INSTAIR_PT499_PRESS_PSIG
Jordan is aware and watching it. Says it's a "waiting game now".
Ibrahim, Oli, Betsy, Thomas
Today, we had a call with Thomas to diagnose LHO's QOSEM shorting issues - found in alog 90864, alog 90838, alog 90834.
LHO broken QOSEMs:
S2600013 - Pins 23 and 10 grounded to chamber:
S2600025 S2600010 - Shorted (likely)
Tom's Suggestions On dead OSEMs
On Sat Amp
After the qosem broke, we swapped our last spare, requested more from LLO and carefully centered the QOSEM such that it's on the PD and roughly centered. Now, all our QOSEMs are working and are roughly (very roughly) centered.
Next:
We'll wait until the spare QOSEMs arrive to continue centering (now with a renewed meticulousness about shorting). Then, we can send the 3x broken LHO QOSEMs and 1x broken LLO QOSEM to CIT to Ali to resolder the LEDs and return them as viable spares.
Oli, Ibrahim
We likely shorted another QOSEM likely at the area of the microDB pins on top of the flexi-circuit. The counts went to 0 immediately. This was probably done during the OSEM centering where the Y centering involves having a tool on top of the danger area to move the Cams.
[Betsy, Oli, Ibrahim, Elenna, with online help from Arnaud, Marie and Gabriele]
Today we began by attempting to follow the same steps that LLO did to decouple pitch and yaw, as described in 81817. To summarize, they applied a length offset and adjusted coil driver gains to ensure the same amount of motion is sensed on M0 F2 and F3 oseminfs.
Betsy and I immediately found that following that same process was not going to work. As a reminder, Ibrahim and Oli swapped the F3 osem yesterday due to ground loops, 90838. To get straight to the point, here are some results:
Arnaud notes that overall this is an improvement, because last week the P2Y cross coupling was much worse, roughly 1x pitch to 2x yaw. The overall numbers are different depending on which sensor you trust. However, Betsy and I think that the top mass drive versus sensed motion (master outs versus oseminfs) should be relatively straightforward. It seems like we have a mechanical imbalance on the suspension. However, the improvement that has occured was only due to swapping an osem, which seems electrical.
Oli will revisit the derivation of the osem2eul/eul2osem matrices. We also plan to recheck the suspension transfer functions to see if the P2Y coupling is reduced.
ndscope-test can now show "scatter" plots.
Plot one channel against others. Each plot can have one channel giving the X value, and any number of channels giving Y values. The plot will show one trace per Y value channel using the color of that channel.
Create a scatter plot from the command line by running "ndscope-test --scatter <x-channel> <y-channel-1> <y-channel-2> ..."
Create a scatter plot from a time domain plot.
1. Right click to get the pop up menu.
2. Select configure channels.
3. Select at least two of the channel names in the window with Control + click or Shift + click. The first selected channel is always the X channel
4. Press the Add Scatter Plot button at the bottom of the screen.
5. Press the OK button.
The timespan of the traces matches the time span of the traditional time-domain plots. Pan and zoom a time domain plot to
change how much is shown on the scatter plot.
WARNING: This is a development release.
There may be bugs.
Some bits are not working for scatter plots. For example, the configure channels window does not appear for these plots.
Some needed interface is not yet included. There's no way to change the X channel for a scatter plot yet, other than to
open a new window and add the new X channel to the command line. Scatter plots cannot be saved to or configured in yaml files. Many more bits aren't done.
Rahul K, Ibrahim A., TJ S
SEI & SUS configuration: BSC3 ISI and HEPI were locked, suspension unlocked and damped.
Accelerometer position 1 - Mounted at the bottom of the cage near the 7oclock position as seen in this photo. Accelerometer axis=IFO axis.
Meas 1 - Hitting near the accelerometer at around the 7 o'clock position in the +X direction.
Meas 2 - Hitting -Y around the 9 o'clock position.
Meas 4 - Hitting in +Z at the 6 o'clock at the bottom of the cage.
Accelerometer position 2 - This was the analagous spot to the ITMY measurements, on the cross bar between the penultimate mass and the bottom stage. Accelerometer axis to IFO axis (X,Y,Z=-Z,+X,-Y)
Meas 5 - Hitting in +X(ifo) on the crossbar under where the accelerometer is mounted.
Meas 6 - Hitting down, -Z (ifo), on the crossbar near accelerometer.
Meas 7 - Hitting in t -Y(ifo) direction on the +Y structure around the 9 o'clock position around the TM.
The logitudinal and transverse modes were about 0.5Hz lower with the accelerometer mounted in the second position, but hard to tell with this resolution.
| First Mode | Frequency (Hz) |
| Longitudinal | 59-59.5 |
| Transverse | 66.5-67 |
LHO ITMY B&K results found at alog90512. To save you the click, ITYM long. = 57.5Hx and Trans.=64,67.5Hz
Rahul K, Ibrahim A., TJ S
SEI & SUS configuration: BSC2 ISI and HEPI were locked, suspension unlocked and damped.
Accelerometer position #1 - Mounted in a similar position from when Rahul B&K'd the BBSS in the staging building last year (T2500205). Axis for the accelerometer are +X=perpendicular to BS surface, +Y parallel to BS in the -X-Y direction, and +Z=IFO+Z. DOFs mentioned from here on will be in the accelerometer axis unless otherwise specified.
Meas 1 - Hitting in the +X direction on the corner opposite of the accelerometer.
Meas 2 - Hitting +Y on the same corner.
Meas 3/4 - Hitting in +Z on the same corner (data from measurement 4 but 3 in my notes)
Accelerometer position #2 - The accelerometer was then mounted on the bottom structure on the AR side, at the 4o'clock position. Unfortunately, the data from this set seems to all be noise, something I couldn't quite tell chamberside.
This isn't the best data and I don't' see any clear peaks other than the 21Hz and 47Hz on the 3/4 measurement. The first longitudinal mode that I see is maybe at 111Hz. If we compare to LLO (LLOalog81300), our 111Hz should be the second order of this mode, so we might be in the right ballpark. Either way, I don't see anything egregious, so that's a good sign. It's unfortunate we didn't get the second accelerometer position as I think that would have given us some better movement of the cage.
For reference LLO's inchamber BBSS results can be found at LLOalog81300.
Attached below are the screenshots of the transfer function measurements for ITMX and ITMY (main and reaction chain - all 6 dof.), I can confirm that they look healthy.
The templates are stored at the following location.
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGM0/Data
2026-06-29_2000_H1SUSITMX_M0_WhiteNoise_L_0p01to50Hz.xml
2026-06-29_2000_H1SUSITMX_M0_WhiteNoise_P_0p01to50Hz.xml
2026-06-29_2000_H1SUSITMX_M0_WhiteNoise_R_0p01to50Hz.xml
2026-06-29_2000_H1SUSITMX_M0_WhiteNoise_T_0p01to50Hz.xml
2026-06-29_2000_H1SUSITMX_M0_WhiteNoise_V_0p01to50Hz.xml
2026-06-29_2000_H1SUSITMX_M0_WhiteNoise_Y_0p01to50Hz.xml
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGR0/Data
2026-06-29_2100_H1SUSITMX_R0_WhiteNoise_L_0p01to50Hz.xml
2026-06-29_2100_H1SUSITMX_R0_WhiteNoise_P_0p01to50Hz.xml
2026-06-29_2100_H1SUSITMX_R0_WhiteNoise_R_0p01to50Hz.xml
2026-06-29_2100_H1SUSITMX_R0_WhiteNoise_T_0p01to50Hz.xml
2026-06-29_2100_H1SUSITMX_R0_WhiteNoise_V_0p01to50Hz.xml
2026-06-29_2100_H1SUSITMX_R0_WhiteNoise_Y_0p01to50Hz.xml
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGM0/Data
2026-06-30_1500_H1SUSITMY_M0_Mono_WhiteNoise_L_0p02to50Hz.xml
2026-06-30_1500_H1SUSITMY_M0_Mono_WhiteNoise_P_0p02to50Hz.xml
2026-06-30_1500_H1SUSITMY_M0_Mono_WhiteNoise_R_0p02to50Hz.xml
2026-06-30_1500_H1SUSITMY_M0_Mono_WhiteNoise_T_0p02to50Hz.xml
2026-06-30_1500_H1SUSITMY_M0_Mono_WhiteNoise_V_0p02to50Hz.xml
2026-06-30_1500_H1SUSITMY_M0_Mono_WhiteNoise_Y_0p02to50Hz.xml
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGR0/Data
2026-06-30_2000_H1SUSITMY_R0_WhiteNoise_L_0p01to50Hz.xml
2026-06-30_2000_H1SUSITMY_R0_WhiteNoise_P_0p01to50Hz.xml
2026-06-30_2000_H1SUSITMY_R0_WhiteNoise_R_0p01to50Hz.xml
2026-06-30_2000_H1SUSITMY_R0_WhiteNoise_T_0p01to50Hz.xml
2026-06-30_2000_H1SUSITMY_R0_WhiteNoise_V_0p01to50Hz.xml
2026-06-30_2000_H1SUSITMY_R0_WhiteNoise_Y_0p01to50Hz.xml
Since the ISI is locked, we see some cross coupling and peaks around 7Hz on some dof. I discussed it with Jeff K and he said its okay to ignore it for now. I will take another measurements later when the ISI is floating and damped.
The suspensions has been restored to ALIGNED state after the measurements were complete.
The security cover over the SPI Laser Prep Chassis is now locked. See alog 90585 for pictures. Keys are stored in the control room key box. A workpermit is required to unlock the security cover. Item should be added to LHO LVEA Laser Safe/Hazard Transition Procedure M1100115.
WP 13376
IOT2L field cabling reconnected. Picomotor driver chassis 5 was reinstalled.
WP 13069. "I found two instances of the EPICS IOC running on h0vaclx. I will close them both and start a single new one. I will also check the other Beckhoff vacuum machines and do the same for those if necessary." I also found two instances running on h0vacmx. Instead of closing both and opening one, I just closed one of the two instances on each of the two computers. Closed WP.
[Sheila, Camilla, Ryan, Eric]
We would like to verify that our recent mode measurements after ZM5 ( 90783) and before ZM4 (90815 ) make sense by connecting the two. We decided to use the q value from the measurement at the nominal ZM2 strain in 90815 (ZM2 strain = 3.15V) and propagate that mode through the path containing ZM4 and ZM5 and calculate the overlap with the q values from 90783 measured at different strain settings for ZM4/ZM5. The goals here are as follows:
First, I address item 1.
Mode Measurements with M2 > 1:
Our system seems to be adding some higher order abberations to the beam. As a result, our mode measurements indicate that we have an M^2 number significantly above 1 (between 1.2 - 1.5 depending on the PSAM settings). When M^2 is > 1, the presence of HOM content in the beam prevents one from focusing down to as tight of a waist, for the same divergence angle, the beam radius at the waist will be larger by a factor of M. The thorlabs beam profiler accounts for this by fitting the data to the following formula (which we confirmed by doing our own independent fit):
w(z)2 = wM2[1 +(z - z0)2 (pi*wM2/(M2*lambda))2]
Where wM2 = M2*w02 Is the waist for a beam with M2>1, and w0 is the waist for the TEM00 component of the beam (ie for M2 = 1).
The q parameter ends up the same as before:
q(z) = (z-z0) + i*zR
where zR = pi*w02/lambda = pi*wM2/(lambda* M2)
Knowing that M2 > 1 tells us that our beam is a mixture of TEM00 and some higher order mode content. However, from the M2 value alone we don't know which higher order modes are excited (in principle one might be able to make some rough projections using the surface abberation measurements of the PSAMs from Caltech, but that sounds tricky and is beyond the scope of today's post). If we want to do mode matching calculations, the only thing we can do at the moment is back propagate the TEM00 component and do all mode calculations for TEM00.
We use the same beam propagation matricies as always to back propagate the TEM00 component to determine what the TEM00 mode looks like in HAM 7.
Determination of the ZM4 and ZM5 ROCs
I then took the q value (for the nominal ZM2 = 3.15V) from the measurement before ZM4, back propagated it to ZM4 using our length measurements. I then propagated the q through ZM4 and ZM5 and calculated the overlap with the q values measured after ZM5 for various values of the ZM4/ZM5 strain gauge settings in ( 90783)
Then, the ROCs for ZM4 and ZM5 were chosen for each strain gauge settings to maximize the overlap. The overlap is => 98% over the entire 2D grid of ZM4/ZM5 strain gauge values, which gives us some confidence that the ROC values are accurate. One thing that gives us pause is that the change in ROC for ZM5 doesn't appear to change linearly in diopters with the strain gauge reading. ZM4, on the other hand is roughly consistant with a 5 mD/V change though because the beam spot is quite small on ZM4, we are relatively insensitive to its ROC value.
| ZM4 Strain (V) | ZM4 ROC (m) |
|---|---|
| 2.0 | -12 |
| 4.0 | -11 |
| 6.0 | -10 |
| 8.0 | -9 |
| ZM5 Strain(V) | ZM5 ROC (m) |
|---|---|
| -4.5 | 3.8 |
| -2.0 | 4.05 |
| 0.0 | 4.4 |
| 2.0 | 4.55 |
These values give the following overlaps for the x and y direction (our mode measurements indicate we have non-negligible asitgmatism on this path) for propagating the nominal q value from (90815 where ZM2 strain = 3.15) to the q vales from ( 90783) .
| ZM4 \ ZM5 | -4.5 | -2.0 | 0.0 | 2.0 |
|---|---|---|---|---|
| 2.0 | x = .994, y = .995 | x = .998, y = .997 | x = .990, y = .995 | x = .9874, y = .993 |
| 4.0 | x =.996, y = .997 | x = .994, y = .995 | x = .986, y = .992 | x = .983, y = .991 |
| 6.0 | x =.995, y = .997 | x =.992, y = .993 | x =.983, y = .989 | x =.980, y = .984 |
| 8.0 | x =.993, y = .995 | x =.990, y = .992 | x =.980, y = .984 | x =.977, y = .980 |
The fact that this set of ROC values gives good overlap over the entire 2D grid suggests that these ROCs are a resonable model for ZM4 and ZM5 at these strain gauge settings.
Attached is an a la mode file for doing the beam propagation. One could do some more intellegent fitting of the data to extract the best ROC estimates; I'm just sorta hand fitting it at the moment.
We have ZM5 SN4 installed now. Original data before we changed the preloading (E2100297) had the ROC range 3.0m to 3.9m. With at 0V applied 667mD optical power, with 200V applied 508mD.
In alog 75709 we increased the preload from 20 in lb to 47 in lbs. An estimated linear increase of 65mD as according to T2300426, changing the preloading changes the optical power by 2.4mD/in.lb.The preloading should make the magnitude of the optical power larger, so it should be increased to 667mD - 2.4mD/in lb * 27 in lbs = 602mD mD with 0 V on the PZT, 443mD with 200V on the PZT. This is an estimated ROC range of 3.3 to 4.5 meters for strain gauge -5.0 to +2.6V (it's range with 0V and 200V applied). This mostly agrees with Eric's data.
We have ZM4 SN1 installed now. Original data before we changed the preloading (E2100289) had the ROC range -19.3m to -9.0m. With at 0V applied -104mD optical power, with 200V applied -221mD.
In alog 75677 we increased the preload from 46 in lb to 75 in lb. An estimated linear increase of 70mD. This should be increased to -104mD - 2.4mD/in lb * 29 in lbs = -174mD mD with 0 V on the PZT, -291mD with 200V on the PZT. This is an estimated ROC range of -11.5 to -6.9 meters for strain gauge 1.0 to 8.3V. This mostly agrees with Eric's data.
We had two rounds of restarts. The first was a full models+EDC+DAQ restart with a longer TW outage to copy rawminute trends to preserve recent lookbacks. The second was an unplanned restart to add an IPC between CRS and ISIHAM3 which needed a DAQ restart.
WP13365 CRS and ISI HAM2,3,4,5
New models for h1isiham[2,3,4,5] were installed and the DAQ was restarted. I was then found that an IPC between h1crsproc and h1isiham3 was both not running and was the incorrect type (a PCIE channel which should be SHMEM). Jim fixed the h1crsproc sender and h1isiham3 receiver. Because this channel was already in H1.ipc as a PCIE, I hand edited this file to remove it so the build of h1crscproc added it back as a SHMEM channel.
WP13366 PEM add 5th ADC channels to DAQ
New h1pem[ex,ey] models were installed which acquire the first 8 channels of the recently added 5th ADC to the DAQ at 2kHz. DAQ restart was required.
WP13346 Remove CP1 Overfill
The EDC master file was edited to remove the H1EPICS_CP1.ini file. EDC+DAQ restart was required.
WP13304 New HEPI Pump Control IOC
Patrick installed a new EY HEPI pump control system which has new EPICS channel names. A new H1EPICS_HEPIPUMPEY.ini file was installed. 120 new channels had old channel equivalents, the raw minute trends for this files were copied to the new names as part of the trend writer restarts.
DUST LAB2 removal from EDC
A restart Lab Dust IOC removed the LAB2 channels from its IOC. As a temporary solution I had added these channels to the edc_green_ioc dummy IOC running as a the service-host container. Today these channels were removed from both the container and H1EPICS_DUST.ini, and then removed from the EDC as part of the DAQ restart.
DAQ Restarts
The first DAQ restart included a rawminute trend file copy on both trend writers:
1 Restart models
2 Stop TW0 and TW1
3 Run copy script on TW0 and TW1, some new hpipump channels will be starting from where the old channels left off
4 DAQ 0-leg plus EDC restart (also restarts TW0)
5 DAQ 1-leg restart (also restarts TW1)
No major issues with this restart.
The second DAQ restart was just a model restart, no EDC restart was required.
FW1 spontaneously restarted 53 minutes later.
Restart Log:
Wed01Jul2026
LOC TIME HOSTNAME MODEL/REBOOT
09:12:31 h1iscex h1pemex <<< add ADC channels
09:13:05 h1iscey h1pemey
09:16:07 h1seih23 h1isiham2 <<< New CRS components
09:16:33 h1seih23 h1isiham3
09:17:20 h1seih45 h1isiham4
09:17:48 h1seih45 h1isiham5
09:22:02 h1daqgds0 [DAQ] <<< first 0leg restart
09:22:06 h1susauxb13 h1edc[DAQ] <<< EDC restart
09:22:07 h1daqfw0 [DAQ]
09:22:07 h1daqtw0 [DAQ] <<< TW0 restart after file copy
09:22:08 h1daqnds0 [DAQ]
09:26:02 h1daqdc1 [DAQ] <<< first 1leg restart
09:26:11 h1daqfw1 [DAQ]
09:26:12 h1daqtw1 [DAQ] <<< TW1 restart after file copy
09:26:15 h1daqnds1 [DAQ]
09:26:21 h1daqgds1 [DAQ]
09:30:52 h1daqfw1 [DAQ] <<< spontaneous FW1 restart
10:05:40 h1seih23 h1crsproc <<< Fix CRS IPC
10:06:14 h1seih23 h1isiham3
10:06:52 h1daqgds0 [DAQ] <<< second 0leg restart
10:06:59 h1daqfw0 [DAQ]
10:07:00 h1daqnds0 [DAQ]
10:07:00 h1daqtw0 [DAQ]
10:10:54 h1daqdc1 [DAQ] <<< second 1leg restart
10:11:05 h1daqfw1 [DAQ]
10:11:06 h1daqtw1 [DAQ]
10:11:11 h1daqnds1 [DAQ]
10:11:15 h1daqgds1 [DAQ]
10:11:59 h1daqgds1 [DAQ] <<< GDS1 needed a restart
11:02:37 h1daqfw1 [DAQ] <<< spontaneous FW1 restart
I found a copy-paste error in h1pemey with its ADC_4 bus selector. This was fixed and the model restarted at 14:01. No DAQ restart was required.
The filtermodules feeding the new ADC_1_[00-07]_OUT_DQ channels were set to pass the signal through and the SDF safe.snap files were updated.
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.
I've been reading through the design document about the FC path and ZM2. One thing imay be important to note when making projections about the correct strain gauge setting for ZM2: According to the design document the mode matching is quite sensitive to the exact value of the FC1 AR surface ROC. One might find that, if we change our assumption about the ROC for S2 of FC1, our target strain gauge setting for ZM2 changes significantly. In fact, the discussion makes it sound like most of the point of having ZM2 be adjustable was to compensate for our uncertainty in the ROC of S2 for FC1.
See LIGO-T1900649 and the discussion on Page 18 as well as Figure 10.
Camille (CIT), Rahul
Just like ZM4 (see LHO alog 75677) we have offloaded ZM5 (P-SAMs) in HAM7 chamber to 47 in lbs. as per E2300463_V1. We followed the same procedure as described in alog 75677. Camille will post all the relevant pictures.
Post work transfer function measurements showed that the suspension is healthy.
Next we will work with Sheila et al on beam alignment in HAM7 chamber and mechanically offload the alignment sliders for both the suspension.
1st image: PSAMS secured to Fixture Plate 2nd image: PSAMS preloader being adjusted with torque wrench 3rd image: Dial indicator on torque wrench showing torque that was applied to preloader (47 in lbs)
In 90859 we've used measurements to find the new ROC.
Camille (CIT), Austin , Rahul
This morning we went to HAM7 chamber and changed the preload on ZM4 (P-SAMS) suspension as per the document E2300463_V1. This changed the RoC of ZM4 mirror without the PZT actuation. Given below are the details of our work - Camille will add pictures later on.
- After setting ZM4 into SAFE state we locked all three stages of the suspension. We had already taken healthy TF measurements before starting our work.
- The bottom mass cable was disconnected and carefully re-routed so that it stays away from the fixture plate.
- four add-on masses (basically 1/4-20 screws with washers) attached to the bottom mass was then removed.
- bottom mass Fixture plate (D2100121) was attached to the structure using six 8-32 screws.
- The bottom mass (already locked using EQ stops) was then further clamped using four 1/4-20 screws through the fixture plate. We had to adjust the height of the bottom mass to the align the threads with the holes on the fixture plate.
- Once the bottom mass was securely clamped, we removed the three set screws on the preloader.
- Using a torque wrench we increased the preload on the bottom mass by ~29 in.lb. (Total preload from torque after increase was 75 in.lb).
- We then followed all the above steps backwards (i.e set screws, add on mass put back, fixture plate removed, cable re-connected and the suspension set free).
- Once all done, we started damping the suspension and checked for any BOSEM flag changes - looked all fine.
- We took the transfer function measurements and ZM4 looked healthy.
Hence we took all the tools out and put the curtains back on HAM7 chamber.
Next, we will go into laser hazard with SQZ team and check for any changes in beam alignment and make adjustments as required.
1st image: PSAMS locked in place with EQ stops. 2nd image: PSAMS locked with bottom mass fixture plate. 3rd image: Removal of set screws. 4th image: Preload adjustment with torque wrench. 5th image: Preload adjustment with torque wrench. 6th image: Torque wrench dial with the blue needle showing the total torque on the preloader (75 in lbs.)
Excellent!
ZM5 offloaded as well, see LHO alog 75709.
This is ZM4 SN1, so it's original charachterization data (before this preloading) is in E2100289, where with 0 V applied to the PZT the optical power is -106mD (or ROC is -18.877m).
According to T2300426, changing the preloading changes the optical power by 2.4mD/in.lb. So, after this preloading the optical power with 0V on the PZT should have been -36mD, or the ROC should be -55.5meters.
Evan and Camille noticed that I flipped a sign here:
The preloading should make the magnitude of the optical power larger, so it should be increased to -106mD - 2.4mD/in lb * 29 in lbs = -175.6 mD with 0 V on the PZT. ROC = 1/-175.6e-3 = -11.4 meters
In 90859 we've used measurements to find the new ROC.