This afternoon, both CH CO₂ lasers were successfully switched on using the new cooling system designed and installed by the EGO team.
Before switching on the lasers, Piernicola performed a complete check of both CO₂ benches. In particular, he reset the zero level of all power meters and verified the correct operation of all remotely controlled flip mirrors.
The lasers were then switched on sequentially:
For both lasers, the pulse width was set to 160 µs. For reference, the maximum output power is achieved with a pulse width of 199 µs.
The laser behaviours observed so far are shown in Fig. 1.
The lasers will remain ON overnight. According to the current plan, the main CO₂ lasers will be switched on tomorrow morning.
I also performed a quick check using the thermal cameras on both benches and acquired one thermal image of each CH beam. A comparison with the images acquired on 2026-04-07 did not reveal any significant changes in the beam propagation. The comparison is shown in Fig. 2.
Side note: while trying to copy the thermal camera images from PCINFRACAM to the control machines, I noticed that the procedure was no longer working. I therefore contacted the Computing Team, and Elian found that the old SSH Secure Shell client is no longer supported following the recent Linux upgrade. As a temporary workaround, Elian identified an alternative procedure and shared it with all operators to be used during the upcoming Tuesday maintenance.
ITF found in COMMISSIONING Mode and LOCKED_ARMS_IR State.
All times are UTC.
06:38 - 06:49 Recovered SBE_SPRB vertical position with loop closed (operator).
07:10 - 10:30 Instrumented baffle commissioning (Vallejo, Boldrini. #69514).
07:41 - 11:00 Activity on TCS AUX Cooling System (Dattilo, Cavalieri).
11:39 - 12:35 Safety inspection at MCB and WEB (Fabozzi, external personnel).
12:07 - 15:07 Activity on TCS AUX Cooling System (Dattilo, Menzione, Cavalieri).
13:20 - 14:00 TCS CH Lasers ON and Flip Mirrors checked (Spinicelli, Nardecchia from remote).
13:20 WE PCal laser turned ON (Rolland from remote, #69513).
13:31 - ONGOING Suspensions tuning (Ruggi, Pinto).
ITF left in DOWN State and in COMMISSIONING Mode.
We attempted to evaluate how the instrumented baffle could be used to prealign the end mirrors of the arm cavities.
Starting from the locked arms, we took references of the alignment condition of the test masses, of the BS and of the transversal position of the PR (Figs.1,2), we then unlocked the interferometer and misaligned both ITMs by 60 urad on TY to simulate the stage of the recovery when the beam has been centered on the ETMs using the markers by moving the PR and the BS, but the alignment of the test masses themselves is still unknown.
The starting position for the NE is (TX; TY) = (-107.8; 45.4) urad
Once we did that, we started sweeping the NE alignment until the sensors on the NI instrumented baffle detected power. We then refined the alignment of the NE until we maximized the power detected by sensors 0,1 and 2 of the column c17, in the left sector of the baffle. The goal was to use the detected power to attempt to center the beam on the middle sensor, equalizing the power on sensors 0 and 2, assuming that they correspond to the tails of the Gaussian profile of the beam. We achieved this result on the c17 column with intervals of 0.2 - 0.4 urad for the NE, notice that the procedure is cumbersome, because the detected power fluctuates significantly so one needs to be patient and consider an average over a minute or so.
We then swept the NE right by about 100 - 110 urad until we intersected the symmetrical column c5 and repeated the process. Overall, the power detected were:
The median point identified by these positions is (<TX>;<TY>) = (-105.53; 44.56) urad, that is remarkably close to the initial position.
We repeated the process with a vertical scan:
The median point identified by these positions is (<TX>;<TY>) = (-105.68; 43.96) urad, which is also close to the initial alignment of the NE.
Our conclusion is that the instrumented baffle is accurate enough to provide a prealignment of the beam that centers it on the NI withing a few urads from the correct alignment, so it seems a promising tool to be used in future recoveries.
We tried to repeat the process for the WI instrumented baffle, but we could not finish the procedure in the remaining time of our shift. Another commissioning windows has been allocated for this tomorrow morning.
WE PCal switch on at 13h20 UTC.
Yesterday afternoon, we performed a measurement of the current input beam mode mismatch toward the arms, with the CO2 lasers off (only PR Chrocc and SR RH are at nominal value).
Since the interferometer is not actually fully locked, we decided to use the green beam scan of the arms to assess the cold mistmach.
The scan started at 14.05UTC of the August 4th.
The results are shown in fig. 1, with both arms around ~1.5% of mistmatch.
N_matching = 1.6e-02
W_matching = 1.3e-02
The following report summarizes the measurement and analysis of scans performed on 03-08-2026 in order to measure the arm Gouy phase. The aim is to verify that we recover the same Gouy phase as it was during the end of the last observation run. The Gouy phase is measured from the mode spacing measured from the frequency scans. The procedure to perform the slow FSR scan can be found on this page https://wiki.virgo-gw.eu/Commissioning/OptChar/Opt_Char_shift
Measurements:
At 14:54 UTC, ITF is locked using the state LOCKED_ARMS_BEATING
At 14:55 UTC, 1 iteration of scan is run as a test to verify that everything work
At 15:00 UTC, 15 iterations of scan, ended at 15:33 UTC
Results:
Tables 1 and 2 compare the mode spacing of the first four higher-order modes during the end O4 run and in the scan measured on 2026-08-03 in the west and north cavity, respectively.
Table 1 : North Cavity
| HOM 1 | HOM 2 | HOM 3 | HOM 4 | |
| 02 December 2025 | 0.1035±0.0003 | 0.2092±0.0003 | 0.3191±0.0002 | 0.4276±0.0002 |
| 03 August 2026 | 0.1057±0.0003 | 0.2113±0.0002 | 0.3215±0.0002 | 0.429±0.002 |
The measured mode spacing is very similar in each scan but slightly larger in the recent scans.
Table 2 : West Cavity
| HOM 1 | HOM 2 | HOM 3 | HOM 4 | |
| 02 December 2025 | 0.10246±0.0007 | 0.2076±0.0002 | 0.3201±0.0002 | 0.4304±0.0005 |
| 03 August 2026 | 0.103±0.001 | 0.2085±0.0008 | 0.3195±0.0003 | 0.4290±0.0003 |
The measured mode spacing is very similar in each scan, larger in the recent scan for the first two higher-order modes and smaller for HOM 3 and HOM 4. A supposition to explain the discrepancy between the different higher-order modes could be the change of the input test masses, resulting in a different transverse RoC asymmetry. The higher-order modes, presenting a larger area, experience a different portion of the mirror surface and as a result experience a different effective RoC. This hypothesis could explain why for HOM 1 and HOM 2 the mode spacing is larger during the scan performed on 03 August 2026 and smaller for HOM 3 and HOM 4.
To visualize what the observed difference represents in the scan, Figure 1 and Figure 2 show two scans plotted together. The blue curve represents the median scan performed on 03 August 2026 and the orange curve the old scan performed on 02 December 2025. The four plots below the full scan are a zoom on the first four higher order modes. These plots show that the difference is actually very small, suggesting that the Gouy phase is almost the same as in December.
ITF found in DOWN with the automation requesting to lock in BEATING_DRMI_1F.
The DRMI_LOCK node was also stuck trying to reach the requested state MISALIGNED_PR_SR; to unblock the situation I restarted the nodes.
After that I performed a manual prealignment of WI mirror and I relocked the cavity.
At 6:00 UTC started the planned maintenance, below the list of the activity communicated in control room:
All the maintenance activities concluded around 10:30 UTC.
In the afternoon the INJ team worked input beam mode matching measurement, activity in progress.
Other
M 4.3 in Pisa; the earthquake opened the PR ID loop and all the SBE loops. Properly closed.
Over the last days, different VMs (ctrlX and farmnX) intermittently became unresponsive, leaving users temporarily unable to log in.
The cause was memory exhaustion: interactive user sessions were consuming nearly all of a machine's memory, starving the essential system services that handle authentication and access.
To prevent this, we have applied a memory limit to the aggregate of all user sessions on each machine, so that a share of memory is always reserved for essential system services.
It is a soft limit: when sessions approach the threshold the system gradually slows them down and reclaims memory. it does not terminate processes or interrupt anyone's work.
Under heavy load, large sessions may run somewhat slower; this is the intended trade-off to keep the machine reachable for everyone.
VMs should now stay responsive and authentication reliable even under heavy memory usage. Please report any unexpected behaviour.
The FdWRawBack server configuration has been updated to use the 117TB of disks available for the RAW_BCK online stream on the stol02 host
Operation perfromed at 2026-08-04 08h31m44 UTC
Yesterday, I put the sensors back in place and restarted the data acquisition
Yesterday, I put the sensors back in place and restarted the data acquisition.
Today we continued the work on the recovery of the lock. Just to put some context also here, during the limited time of these couple of weeks we are relocking on purpose without any TCS actuators, because of commissioning plan and forthcoming hardware interventions. The purpose is to restore things as much as possible, given that we've not been locking for four months, and we ancitipate not being able to go much farther than the beginning of the CARM offset reduction part of the lock acquisition.
We proceeded with the lock of the ALS system, that started already on Friday; today, thanks also to the increased stability of the WI actuation, we could move from the standalone arms to the beating signals and close the CARM and DARM control loops (same controllers as before, new improved ones that can profit of the ALS recent improvements will be developed later).
Then we moved to the CARM offset step, and then the realignment and lock of the DRMI:
We spent some time to check gains and phases (given that the optical configuration is different w.r.t. April): we did not find anything out of the ordinary with the exception of SRCL, which has half the gain of before; we then moved to the DRMI with 3f signals, and we could do the handoff with no problems. This configuration has a bigger deviation from the past: the 169MHz demodulation phase for MICH/SRCL has changed, and the gains of both loops needed some tuning. Nothing relevant for the PRC instead.
We took the occasion also to close the floating setpoints servo of the SDB1 local controls.
We saved the new parameters of the lock acquistion (labeled in the .ini files) and we left the DRMI locked with 3f signals.
The following report has been submitted to the On-call interface.
On-call events -> Air Conditioning
Title: Water Leak from the Autoclave System
Author(s): andreazzoli
| Called at: 21:00, 03-08-2026, by: Other colleague |
| Remote intervention: Started: ; Ended: |
| On-site intervention: Started: 21:22, 03-08-2026; Ended: 21:55, 03-08-2026 |
| Status: Resolved |
| Operator when issue resolved: None |
Details:
Following a report from the RSPP regarding a water leak from the pressure tank system, I conducted an inspection.
The water leak was attributable to the operation of the water treatment system. The system was left in normal operation.
* Note that any files attached to this report are available in the On-call interface.
The swap of the two LNFS done on July 15th has been done without exchanging the eth address of the devices. As a consequence, while restarting the automation, it was trying to communicate with the old address, thus inverting the {6, 8, 56 }MHz signals with the {22, 81}MHz. We stucked at the Fmoderr state of the INJ node, untill we swapped the ethernet cables of the two LNFS (to be noted: it seems there is the possibility to swap the ports directly into the configuration file of the LNFS server.
Because of this, we found a peculiar corner case of the FmodErr loop: after the exchange of address, the LNFS_FREQ_3 was not anymore setted on 56MHz (was instead the old 81). The check of the Fmod, however, is based on a 56MHz demodulated channel, that gave 0 correction to the loop. Eventually, no change (both MC_Z or LNFS) has been requested, and the 8Mhz frequency has not been changed (and so the 6 and 56, which are automatically updated once the 8 changes).
As a result, this morning we didn't have any modulation at 56MHz. The problem has been solved applied a reset of the 8MHz.
The Fmod loop will be updated consequently.
In order to better center the corrections for the Etalon control in the actuator dynamics we have changed in a 4 days ramp
NI to 20.1 and WI to 19.6
we report on additional results of the analysis:
About the acoustic bump at 19 Hz - we made two additional observations that support the hypothesis that is is an acousting mode of the INJ lab room (aka, laser lab bench room):
About acoustic peaks associated to the INJ and DET HVAC fans: 24 Hz and 27 Hz
About the acoustic peak at 12 Hz - this peak is associated to the main hall, it could be an acoustic mode of the hall
Sound transmission measurement (a rough look) - we injected white noise with one loudspeaker in DET terrace while all HVACs were off.
ITF found DOWN and IN UPGRADING Mode with only the north arm locked.
All times are UTC.
08:04 ALS arms realign (Boldrini, Lagabbe, Spinicelli).
10:30 ALS Recovered, Automation put back in operation, test to lock arms IR & Green via ITF_LOCK ongoing.
The automation has been restarted (#69477);
The recovery of the ITF is ongoing.
ITF left in COMMISSIONING Mode and DOWN State.
Today I re-enabled the etalon loops, using setpoints just slightly above the current temperatures, just to monitor the corrections:
These setpoints were changed online, and also in the configuration file.
Between yesterday and today we put back in operation most of the automation:
We tested up to LOCKED_ARMS_IR_ALS, we'll continue the recovery in the usual way from now on.
I received notification of WE PCal error via the DMS. The power on the Rx sphere is very unstable and goes close to 0. This must be related to the alignment of the WE mirror, which results in the PCal reflected beam going outside the sphere input port.
I have switched off the Pcal beam so the beam does not move around on the Rx bench. We will switch it on later (probably only on Monday, not being available in the next two days).
WE PCal switch on at 13h20 UTC.
The following information summarizes the directory structure and file naming convention for the measurements performed on the NI and WI instrumented baffles.
*** NI instrumented baffle ***
where
# is the measurement (SIG) number reported in the action list;ch1 = mono-axial reference accelerometer;ch2 = triaxial accelerometer, x-axis;ch3 = triaxial accelerometer, y-axis;ch4 = triaxial accelerometer, z-axis.*** WI instrumented baffle ***
The same file naming convention described above applies to the WI measurements.
An example MATLAB script (ReadInstrumentedBaffleData) is attached to show how to read the time-series data.
Plots showing the result of WI MIR actuation cheks are attached. If a voltage is generated by UL DAC (seen by the monitor inside the board), no effect is visible on the mirror orientation (fig 1). If the same is done with one of the other DACs, the rotation is well visible (fig 2).