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

The measured mode spacing is very similar in each scan but slightly larger in the recent scans.

Table 2 : West Cavity

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:

• WI instrumented baffle commissioning (Vallejo, Sadiq, Boldrini);
• cleaning activities of the experimental areas;

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:

• at first we could not see any 56MHz signal: we found the source of the issue being an unintended follow-up of the LNFS problem we had last week; the LNFS configuration was reset and we could continue (#69496); a very large FmodErr mistuning was found and corrected (~+800 um of MC end mirror Z position);
• after a pre-alignment of the PR/SR mirrors, we locked the DRMI with 1f signals without any tuning (gains, phases, etc.), but we saw the SRCL correction immediately diverge, with the already seen "fake lock" configuration; we started to study the issue, remembering that we never relocked after opening the SR tower in April to remove the diaphragm; indeed the SR actuators were quite unbalanced, especially the marionetta ones; after the rebalancing, though, there was no improvement;
• noticing a quite low level of the 112MHz power while "locked", and the fact that the SR OpLev had quite different readings, especially on TY, with respect to April, we rechecked the SR alignment position; we did find that we unluckily realigned on a secondary reflection, as SR_TY was off by ~ 60 urad;
• then, we could relock the DRMI in a proper way.

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

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):

• Figure 1: while the atrium door was open,  the 19 Hz acoustic mode shifted to 20 Hz. The shift-up is a bit counter-intuitive. A similar observation was done when we in Sept 2024 we did the test of opening this door, but with the HVAC on (https://logbook.virgo-gw.eu/virgo/?r=65126). It seems that  this is the acoustic mode that we excided when when repetitively closed and opened opened the atrium door. It is interesting to check if this up-shifting behaviour is reproduced by the ANSYS simulation that Lorenzo is implementing.
• Figure 2: shows that this peak's amplitudes changes by a factor 2 at the location of the three microphones inside the INJ room. It is the larges largest in the NW corner of the room. This change of amplitude within the room is a characteristic of acoustic modes, which also could be cheched with a simulation. We can also notice that the amplitude of the 12 Hz instead is very similar in the 3 positions.  

About acoustic peaks associated to the INJ and DET HVAC fans: 24 Hz and 27 Hz

•  Figure 3 shows the switch off of "just" the INJ and DET HVAC. The two lines disappearing at 24 Hz and 27 Hz are associated to the frequency of the outlet fan of the INJ and DET HVAC, respectively. Interestingly, they have roughly similar amplitude inside the respective labs, e.g. of the order of 0.01 Pa/sqrtHz. But, the 27 Hz is heard clearly inside the CEB HALL (also by the ENV_CEB_LLR_MIC that we positioned close to the EER). Figure 4 shows the time of disappearing lines.

About the acoustic peak at 12 Hz - this peak is associated to the main hall, it could be an acoustic mode of the hall

• Now we look at how the noise further progressively reduces inside the INJ room and in the DET lab when switching off the HVAC of the CEB Clean Rooms and finally that of CEB main hall. The INJ and DET HVAC are already off.
  • Figure 5: switching off CR HVAC. No significant effect is seen in the main hall and inside the DET lab. Some reduction of noise below 10 Hz meaning that CR is actually the main source of noise below 10 Hz (after the INJ HVAC itself). Also loud (aroud 0.01 Pa/sqrtHz) is the 18.6 Hz line associated to the CR HVAC outlet fan.
  • Figure 6: switching off HALL HVAC. The noise reduces below 10Hz in the hall, in DET lab and in INJ Lab. Noticeably an acoustic peak at 12 Hz reduces significantly in all microphones (but it does not disappear). The microphone close to EEroom clearly show a set of well shaped peaks at roughly 2.5, 4.5, 7 Hz, whose amplitude reduced, but did not disapear. These might be also acoustic modes of the hall (?)
  • Figure 7: the 12 Hz peak is coherent between EDB, EIB and the Hall.

Sound transmission measurement (a rough look) - we injected white noise with one loudspeaker in DET terrace while all HVACs were off.

• Figure 8 - shows the injected noise. It overcome the quiet level starting from about 30 Hz.
• Figure 9 - compares ASD spectra during the injection of microphones inside and outside DET lab (left) and inside and outside INJ lab (right). Also shown is the coherence. Roughly we see that effective isolation occurs above 100 Hz. These data should be further analyzed, and possibly injections repeated adopting standard techniques, as done for example in  https://logbook.virgo-gw.eu/virgo/?r=67440.

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:

• NI: 19.98 degC
• WI: 19.49 degC

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 saved the new aligned positions for the arm mirrors, and BS;
• we revived all the nodes:
  • DET_MAIN needed an update on the B1_PD3 threshold to allow the acknowledgement of the SDB1 shutter being close;
  • in ARMS_LOCK we removed any mention of the old FlipMirror_ATR for the old ALS setup, and we added the new one instead; this is done using relay 5 on the TTL_inj process. NOTE: we do not close the flip mirror when ALS is not needed anymore, as we observed today that acting on it makes even the standalone arms to unlock;
  • in ITF_LOCK we commented the opening of the Central Heating flip mirrors, as we are not using any TCS laser now;
• from now on any information based on ITF_LOCK is available again (index, monitoring from DMS and so on).

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).

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 ***

• main directory:                         /data/prod/envmon/Instrumented_Baffles/NI_tower/
• measurement log/action list:    Installation_NI_Instrumented_baffle_16062026.txt
• time-series data:                     /txt_files/20260616/
• time series file named as:      SIG#_BLOCK(ch*).txt 

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 ***

• main directory:                          /data/prod/envmon/Instrumented_Baffles/WI_tower/
• measurement log/action list:     Installation_WI_Instrumented_baffle_20260618.txt
• time-series data:                     /txt_files/20260618/

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).

Pcal NE switched on on July 31 at 7:55 utc.

On July 30 afternoon, we went to the laser lab to realign the ALS laser beam on EIB. We used the CEB_PD_GREEN_MONI photodiode as reference for alignement. The mirrors before the green generator cristal (EIB_ALS_M4 and 5) were realigned to it maximize the power in that photodiode. Then the mirrors EIB_ALS_M6 and 7 were realigned with the IR fiber, using the IR power send to WEB and NEB as reference.

For a reason we still don't understand, CEB_PD_GREEN_MONI photodiode cease to work from 15h to 16h. But it started to work again after we disconnected and reconnected the power supply and Vbias cable.

We recalibrated the CEB_PD_GREEN_MONI photodiode gain and offset in the DAQ so it estimates the total green laser power on EIB. And we changed the threshold values on the DMS for the photodiodes CEB_PD_GREEN_MONI and CEB_PD_IR_MONI.

The green beam was also realigned with the fiber photodiodes CEB_NARM_BEAT and CEB_WARM_BEAT, but this alignment can still be improved by playing with the pico-motors EIB_ALS_pico1 and 2.

The up-left coil looking from the rear side has an issue with the shielding of its cable https://logbook.virgo-gw.eu/virgo/?r=69386

Is that the same coil-magnet pair which is not responding to DAC actuation? Electrical checks should be done as a priority in any case, but if the up-left coil-magnet pair is the issue, then it makes it more likely that this is an electrical problem.

Yesterday and today we worked on the realignment and the relock of the two arms. We spent many hours in finding the alignment again, for both arms.

In the end we managed with a mix of procedures:

• moving PR X/Y to get the beam on the NE markers, then putting it in the center of the mirror; moving NE TX/TY to get the beam back to NI, using the instrumented baffles to center it on NI; move NI TX/TY to get flashes in transmission;
• starting from OpLev readings of the last good position; use the B4 and B1p camera to prealign the reflection of the input mirrors; exploration of PR position and EMs orientations.

After a pause this afternoon to allow other activities, in the evening we managed to finally get some flashes.

We then started to work on the relock:

• we revived the SUS and the [N,W]ARM_LOCK nodes (the latter in standalone, used manually);
• we checked the demodulation phases; B7_6MHz was fine, B8_6MHz needed a small tuning (+0.28 rad);
• we could relock the arms, finding then several issues that we partially fixed:
  • we moved back PR to allow a better centering on the IMs and to recover smaller values of the BPC corrections;
  • we rebalanced NI MAR actuators;
  • we rebalanced WI MIR actuators as one coil is not responding to DAC inputs (see #69480).

We leave the two arms locked, in standalone, using the single arms lock nodes.