Search criteria
Section: H1
Task: TCS
S. Muusse, C. Compton, G. Valente
Alignment of 4.65um beam on the ITMY was completed, excluding the QPD optics which require reflection off the ITM. I've attached a picture of the almost complete table with the notable optics modified today indicated. I'll get someone taller to add a better picture in the comments of the whole table.
Next steps:
The Medm screen is now in a workable form if not particularly finessed.The screen is called TCS_CHETA.adl and a shortcut was added for the X and Y arms by camilla to the TSC screen.
There is still work to be done here calibrating the powerdetectors and power meters.
note: currently power in for the rotation mount .adl is the laser diode current and should be changed to laser power when calibrated
S. Muusse, C. Compton, G. Vajente
We are still in the process of testing the CHETA electronics integration and have began fixing the optical setup on the ITMY Table to test the sensor in situ.
The optical system was realigned with the lenses, waveplate and polariser repositioned to ensure lower 4.65um intensity on the pickoff to prevent burning after the issues in post. All core optics for the 4.65um beam have been placed and we are in the process of adding the sensor paths and laser dumps.
Electronics:
We tested all the laser diode and TEC controller ports on the chassis which were working. It is worth noting when connected to the Laser Enable control the diode will not turn on unless this is enabled and can be used to shut off the laser power.
The thermal power meter input was also working and power changes can be seen on ndscope
I've put in a table the status of all the CDS I/O we've tested so far:
| Sensor | Status | Channel |
| Thermal Power Meter Voltage | Operational | H1:AWC-ITM(OPTIC)_PD_C_VOLTS |
| Laser Enable | Operational | H1:AWC-ITM(OPTIC)_LASER_ENABLE |
| Laser current | Operational | H1:AWC-ITM(OPTIC)_LASER_DIODECURRENTMONITOR |
| Laser Temperature monitor | Operational but uncalibrated | H1:AWC-ITM(OPTIC)_LASER_DIODETEMPMONITOR |
| Flipper | Operational but not installed | H1:AWC-ITM(OPTIC)_FLIPPER_1 |
| Rotation stage | Not operational | H1:AWC-ITM(OPTIC)_POWER |
Some notes are that:
PD_C is the thermal powermeter
PD_A and PD_B are the PDs
We aim to installl the PD setup tomorrow and test its electronics.
Medm
Adjacently, there was continued progress on the medm, a flipper control was installed using SQZT7 code, the slow PD was added using LSC_CUST_DCPD.adl and QPD using QPD.adl. Both will be tested in the coming days on the actual system and the rest of the controls added.
02/23 S. Muusse, C. Compton, G. Vajente, S.Goswami, B. Wu
The electronics chassis was brought into the lab today (thanks Phil and Dave) and we began testing the integration of the optomechanics with the CDS. An ethernet cable was run into the JOAT CHETA lab to connect to the server. A variable power supply was brought into the lab to power the chassis at the required 24V along with a linear power supply required for the rotation stage and translation stages.
The flipper I/O input and output had to be configured for Beckhoff communications using this guide.
The current status of our testing is as follows:
Working:
Not working:
Untested:
We have realised during this process that the flipper isn't powered by the SMA connectors and requires a seperate power source. This was not considered in the initial panel design and is not currently supplied by the chassis. There is a spare blank connector input/output slot which can be used.
We have begun making the medm display for the CHETA system based on the current CO2 medm which shares many optomechanical systems. CHETA isn't currently on the TCS screen so to run the medm display currently the following command must be run to access the work in progress.
medm -x -macro 'USERAPPS=/opt/rtcds/userapps/release/,SITE=LHO,site=lho,IFO=H1,ifo=h1,OPTIC=X,OPTICF=ITMX,name=AWCITMX,RT_MEDM=/opt/rtcds/lho/h1/medm' TCS_CHETA.adl
To open the medm in a configurable format:
medm TCS_CHETA.adl
Alternatively to edit the code files:
code medm TCS_CHETA.adl
Further alignment on the ITMY table was completed with almost all optics now mounted on the table.
The slow controls software was updated to include the ChetaX electronics. The chassis is currently in the MSR for test purposes, but will be moved to the cheta lab next week.
Channels are located under H1:AWC-ITMX.
Closes FAMIS#28228, last checked 88988
TCSX: 30.5 - Did not add water
TCSY: 10.4 - Did not add water
Flow and filters looked good, but had to remove a notification about preventative maintenance for the filter for both chillers (TCSX, TCSY) in order to see the flow rates.
No leak in water cup
FAMIS 38837
CO2 lasers have been off for the past month for vent activities and HWS SLEDs were just turned on a few days ago, so this month's trends don't show much activity.
M. Todd, S. Muusse, C. Compton, S. Dwyer
I wanted to get another measurement of what the HWS think the coupling factor is for thermal lens from ring heater power.
The HWS were not on, so after filling out a work permit Camilla and I went out and turned on the HWS SLEDs. Then we restarted the HWS codes in the individual computers. We also asked Jim to take ITMY ISI to fully isolated.
After waiting about 25 minutes for the HWS to get a baseline reading we turned up both ITMY and ITMX ring heaters by 4W (2W/segment). The HWS will track the defocus and I will compare with my models tomorrow morning. I wanted to do both ITM ring heaters to get a self-consistent measurement.
We also plan on doing single bounce OMC scans tomorrow morning with the ITMs being sufficiently thermalized after the RH turn on. This should give us another lens (punny pun here) to look at the thermalization business.
Closes FAMIS27833, last checked in alog88799
| TCS X | TCS Y | |
|---|---|---|
| Previous Level | 30.3 | 10.3 |
| New Level | 30.5 | 10.6 |
| Water added mL | 110 | 20 |
Values added to spreadsheet.
TCS Monthly Trends Famis 38836
There are some large spikes in this data on days where we have someDAQ restarts.
S. Muusse, M. Todd
Lens realigned on X-arm CHETA table for corrected focal lengths and the beam profiled which had better agreement with the model. ITM beam size from fit are much closer to ideal beamsize on ITM (≈ 52.7mm).
Fit for profile after L2 vs model
| Fit | Model | |
| w0x,w0y [um] | [970.5 ± 28.7, 940.8 ± 23.3] | [1023.9, 981.71] |
| z0x,z0y [mm] | [-1078.1 ± 32.0, -901.9 ± 22.5] | [1.046 , 0.928 ] |
| qx [mm] | 1.078 ± 32.0 + 0.643 ± 38j | 1.046 + 0.708j |
| qy [mm] | 0.902 ± 22.5 + 0.604 ± 30j | 0.928 + 0.651j |
| Beam radii at ITM [mm] | [54.442, 55.885] | [52.311, 54.385] |
Beam radii at ITM is foudnfrom fit by propagating the fit q to the ITM.
S Muusse, M. Todd
New QCL unit (0920) has been put in place of original unit (0923) which is malfunctioning (cause unknown). Initial profiling has taken place and L1 focal length is 10% larger than spec.
QCL unit failure summary:
All day on 2026-01-21 we were running the laser at 900mA doing beam profiles and alignment work. No malfunctioning was witnessed and the laser unit was operating as expected, similar to the laser unit we had run in December for a week. Before lasing we set the following limits on the LD and TEC, per the datasheet.
On 2026-01-22 we turned the laser on to do some more beam profiling with the same limit settings as yesterday, but setting the LD current to 1A (forward voltage was around 12.2V) as was done when we originally profiled this laser in September. We were in the middle of setting up for a new beam profiling measurement (alignment showed the beam was fine, as usual) and we blocked the beam with a high power beam dump at the laser head while installing the profiler. Upon removing the beam dump, we noticed no power was coming out of the laser, and then noticed the forward voltage had dropped to around 800mV. We noticed no sounds or smells or any other signs that something had stopped, only sudden lack of light coming from the unit. All other settings were fine, meaning the controller had not faulted and was still outputing 1A LD current and the TEC was maintaining 20C.
We ran the following checks to see if we could remedy the problem, without success.
QCL 0920 profiling summary:
Replaced broken unit with 0920 and confirms it lases as spec'd. We built telescope as modelled but beam profile was 75% of expected beam width at L2. We subsequently profiled the laser output and confirmed QCL output q measured previously by Matt was still correct. We became suspicious of the true focal length of L1. Then we profiled multiple places after L1 and fit a q parameter using a non-linear fit. A plot of this fit is attached. Using these 2 q parameters the focal length of L1 was estimated to be 220mm instead of 200mm as spec. We think this is mostly because L1 focal length stated by manufactorer is for 588nm where the refractive index is almost 3% larger than at 4.6um. Focal length in the model was modified to reflect our estimated f1 which predicted a beam size closer that measured earlier.
Side note: the scanning slit beam profiler reflects significant amount of 4.6um light which is observable on a thermal beam card.
This morning we continued profiling to characterize the true L2 focal length and install the modeled telescope and characterize it.
We replaced L1 with L2 in the telescope and made several measurements to fit for a q-parameter after L2, because we think we know the q going into it quite well. Then with the q parameters, you can estimate the focal length using ABCD matrix for a thin lens (our estimates yield relatively low complex angles, less than 1 deg, making confident estimates).
| Parameter | x [m] | y [m] |
| Input q (coming from the laser) | 0.411 + 0.067i | 0.376 + 0.056i |
| Output q (fit from profiles) | 1.496 + 1.289i | 1.221 + 0.632j |
| Focal Length (-q1/(q1/q2 - 1) | 0.503 | 0.511 |
Average focal length of L2 = 0.507 m. Which is around 1.5% different from the spec'd value. To reiterate Sophie's log above, the focal length of L1 is estimated to be 0.217 m. Which is almost 9% different than the spec'd value. With these values in hand (as well as the updated value for CaF2 refractive index at 4.6um), we can make a more accurate model and see if measurements of the outgoing q-parameter from the telescope match that model.
We installed a telescope as set up in a model and measured several proviles to fit for the q-parameter after L2. The modeled waist size in both the horizontal and vertical are within the fit uncertainty; however the waist position of the modeled beam is roughly 20cm off in both directions. I think this is because of the Gouy phase regime that we are sampling gives better estimates of the waist size and since we did not sample near the waist we do not have a good idea of where it is.
This afternoon we will try and re-build the telescope as optimized in our models with these measurements to see if we can get a q-parameter that will be 53mm at the "ITM" (propagated 35m from L2).
M. Todd, G. Vajente, L. Dartez
M. Todd, G. Vajente, L. Dartez
To do tomorrow:
--- Horizontal (A1) Fit ---
Data range: z = [339.0, 897.8] mm
Beam radii: [1525.0, 2150.0] µm
Fixing M² = 1
Fit converged: w₀=1034.2 µm, z₀=-465.0 mm, M²=1.00 (fixed)
BeamFitResult(w0=1034.2±49.9 µm, z0=-465.0±33.9 mm, M²=1.00±0.00)
--- Vertical (A2) Fit ---
Data range: z = [339.0, 897.8] mm
Beam radii: [1138.5, 1825.2] µm
Fixing M² = 1
Fit converged: w₀=828.8 µm, z₀=-80.0 mm, M²=1.00 (fixed)
BeamFitResult(w0=828.8±32.5 µm, z0=-80.0±21.1 mm, M²=1.00±0.00)
M. Todd, G. Vajente, L. Dartez
FAMIS 27830 TCS Chiller top off
12/16/2025 Tony 30.7 100 30.8 10.2 125 10.4 Top of ball reading
M. Todd, G. Vajente, L. Dartez
On Sept 4th we had a longer commissioning period to allow us to heat up OM2. The main goal was to use this to characterize the mode matching of the arm cavities to the OMC, but we also made some other interesting measurements.
Summary: heating up OM2 now costs us about 1% of optical gain, while it used to cost us 2%. Heating up OM2 also changed the SRCL offset needed to get flat squeezing significantly, and reduced the amount of squeezing that we could get (without adjusting psams).
The interferometer unlocked (86727) while Jennie Wright was running the DARM offset step script with OM2 cold, to get a measurement of HAM6 throughput and look at OMC refl before heating up OM2. As that link says, there wasn't an obvious connection between the DARM offset script which was in it's final steps (nearly back to normal) when the lockloss happened.
We turned on the OM2 heater while relocking after some back and forth, then had an commissioning caused lockloss while trying to recover. By the time we were relocked, OM2 was heated up according to thermistor 2, which is the thermistor who's timescale matched the timescale of optical gain changes in the past (see screenshot of June 2023 example). We also had a large earthquake while relocking, so we paused after power up and before going to nominal low noise, so we do not have tracking of the optical gain using pcal in the first 30 minutes of this thermalization.
The optical gain in this thermalization seemed to be fairly similar to the previous lock where OM2 was cold in the first hour. The change in optical gain between OM2 hot and cold was much smaller this time around, so we needed to see the full thermalization in order to see what the gain change was. We set the OM2 heater off 4 hours and 5 minutes after the power up, the attached screenshot shows a trend of optical gain during the previous thermalization while OM2 was cold, with a vertical cursor 4 hours 5 minutes into the lock. The horizontal cursors show where the optical gain was at 4 hours and once the thermalization was complete, the optical gain continued to increase by 0.2% after the first 4 hours. The next screenshot shows vertical cursors also at the time of power up and 4 hours later, and the horizontal cursors are the same as on the previous screenshot (OM2 cold). It seems that the optical gain was about 1.1% lower with OM2 hot than cold, although fitting these two thermalizations to an exponential might bring them closer by as much as 0.2%. Our current ring heater settings are 0W on ITMY, 1.5 W/segment on ETMY and 0.44W/segment on ITMX and 1W/segment on ETMX.
Since this is a different result than in the past times of OM2 changes, I've gone back to look at old times when we did this change. One possible explanation for the difference could be ring heater settings being different.
Once the OM2 heater was turned back on, the optical gain increased by nearly 1%, but the IFO lost lock before that thermalization finished. There was a 2% decrease in POP18 during the cool off and a 3 urad shift in SRM top mass.
While OM2 was hot, we did a few tests.
I crunched this data using Gabriele's calibration of OM2 temperature into RoC (LIGO-T2200274). Actually in both the 2023 and 2025 tests it seems like throwing OM2 from cold to hot reduces optical gain by about 2%. One might eke out a bit more data by allowing a bit more thermalization of OM2, but probably not much. kappa_c is a measure of only relative optical gain against a nominal value, so it's not clear that kappa_c = 1 means the same thing for these two datasets since they're two years apart.
Ansel, Sheila, Camilla
Last week, Ansel noticed that there is a 2Hz comb in DARM since the break, similar to that that we've seen from the HWS camera sync frequency and power supplies and fixed in 75876. The cabling has not been changed since, the camera sync frequency has been changed.
Our current camera sync frequencies are: ITMX = 2Hz, ITMY = 10Hz. We have typically seen these combs in H1:PEM-CS_MAG_LVEA_OUTPUTOPTICS_Y_DQ. With a 0.0005Hz BW on DTT I can't easily see these combs, see attached.
It may be difficult to see in a standard spectrum, but can be clearly seen in Fscan plots linked off of the summary pages. For the "observing" Fscan, the interactive spectrum plot shows the 2 Hz comb marked automatically. See the attached image of H1:GDS-CALIB_STRAIN_CLEAN
Verifed that the cabling has not changed since 75876.
Next steps we should follow, as listed in 75876 would be to try using a different power supply or lowering the voltage to +12V. Or, there is a note suggesting Fil could make a new cable to power both the camera and CLink's via the external supply (14V is fine for both).
Thanks Camilla. If anything can be done more rapidly than waiting another week, it would be very much appreciated. Continuing to collect contaminated data is bad for CW searches.
Matt and I turned down the Voltage supplied from 14V to 12V for each camera at ~22:00UTC when the IFO was relocking. Verified HWS cameras and code still running.
We also will plan to have Dave reimpliemnt the hws_camera_control.py script he wrote in 74951 to turn the HWS's off in Observing until we fix this issue.
The 2 Hz comb is still present in H1:GDS-CALIB_STRAIN_CLEAN after the voltage change (before the software update)
alog 85678 showed this 2Hz comb appeared to not be the HWS camera.