Reports of 63926
AdV-ISC (Alignment control scheme conceptual design)
mantovani, pinto - 16:51 Friday 09 October 2026 (69889) Print this report
SR alignment phases and DCP calibration

This morning we have finished to retune the phases for SR alignment

CARM null

SR tx ; error signal ASC_SR_TX_DCP_HF_B1p_I; measurement UTC 9 Oct 7:27 - 7:41 ; initial phase -0.31; new phase 0; Figure 1 

SR ty : error signal ASC_SR_TY_DCP_HF_B1p_I; measurement UTC 9 Oct 7:41 - 8:10 ; initial phase -1.47; new phase -1.2; Figure 2 

LN 2

SRtx : error signal ASC_SR_TX_DCP_HF_phi_B1_I; measurement UTC 8 Oct 8:42- 8:51 ; initial phase 2.2; new phase 3.8; Figure 3

SRty : error signal ASC_SR_TY_DCP_HF_phi_B1_I; measurement UTC 8 Oct 8:25- 8:41 ; initial phase -1.47; new phase -1.6; Figure 4

the phases have not been implemented yet

DCP calibration

the DCP calibration hase been done by injecting DARM broadband noise (ampl 20) and fitted by manuel for different alignment of SR

8:54:25 UTC (120sec ) DCP online = 375Hz DCP fitted = 345Hz

9:15:55 UTC (120sec) DCP online = 290Hz DCP fitted = 260Hz

9:31:55 UTC (120sec) DCP online = 200Hz DCP fitted = 178Hz

 

Images attached to this report
Detector Operation (Operations Report)
lunghini - 16:18 Friday 09 October 2026 (69883) Print this report
Operator Report - Morning shift

ITF found in COMMISSIONING mode and LOCKED_ARMS_IR state.
All times are UTC.
06:04 - 06:57 CEB visit (Bonnand).
06:05-07:10 WEB inspection (Fabozzi).
07:04 ITF in CARM_NULL_1F.
10:41 - 10:43 DAQ: Reconfigure EQB1_DBOX_03 in SQB1_dbox_rack (Masserot, #69885).
10:38 ITF unlocked from LOW_NOISE_3_ALIGNED due to an earthquake close to the site (ML 3.3 at Costa Livornese, INGV). After the unlock DET_MAIN node went in UNKNOWN and was stuck requesting SHUTTER_CLOSE, I restored it requesting INIT state. INJ_MAIN node went in FAULT state, since the INJ input power was not going to 12W I acted on EIBAgilisRot, 'moverel' by 5000, this lowered too much the IMC transmitted power because the automation put the input power back at 12W and the command is sent at some point independently by the state of INJ_MAIN and ITF_LOCK states. The consequencies of this action were the opening of SIB2_SBE (properly close) and the IMC not able to lock. The issue has been solved by manually increase the input power, the IMC locked and the automation has recovered by its own.

ITF left in COMMISSIONING mode and LOW_NOISE_3_ALIGNED state.

Images attached to this report
Detector Characterisation (Broadband noise)
Paoletti - 16:14 Friday 09 October 2026 (69888) Print this report
Comment to Bump at 54.8Hz (69886)

This is a quick look at ENV_EPRB_ACC_Y  (I don't know if this is a good witness)
It seems there is no coherence at 54.8 Hz
Maybe there are other sensors to look at.

Images attached to this comment
AdV-DAQ (Calibration)
verkindt, rolland, masserot - 15:13 Friday 09 October 2026 (69887) Print this report
Restart of HrecSR and HrecOR

Today, around 8h37 UTC, we have restarted HrecSR and HrecOR after discovering the error that made the missing data from Hrec
(HrecSR and HrecOR were writing in the same output "shared memory" as Hrec and with the same file name prefixes.
Now HrecSR writes into /dev/shm/VirgoOnline/HRecSRToSt and HrecOS writes into  /dev/shm/VirgoOnline/HRecOSToSt

FbmSt has been restarted also around 8h37 UTC after including in its configuration the two new inputs HRecSRToSt and HRecOSToSt

 

Detector Characterisation (Broadband noise)
mwas - 14:50 Friday 09 October 2026 (69886) Print this report
Bump at 54.8Hz

Figure 1. In the spectrum there is a new bump at 54.8Hz. It has not been there at the beginning of the year, and it isn't one of the dither lines that I am aware off. It is important to identify what is the origin of it.

The only thing that comes to my mind is the new cover of the EPRB bench. In the past there has been issues with a bump at 63Hz related to SPRB/EPRB, when EPRB was open. 

Images attached to this report
Comments to this report:
Paoletti - 16:14 Friday 09 October 2026 (69888) Print this report

This is a quick look at ENV_EPRB_ACC_Y  (I don't know if this is a good witness)
It seems there is no coherence at 54.8 Hz
Maybe there are other sensors to look at.

Images attached to this comment
AdV-DAQ (Data Acquisition and Global Control)
masserot - 14:47 Friday 09 October 2026 (69885) Print this report
EQB1_DBOX_03 dbox in timing error

The EQB1_DBOX_03  was found in timing_errorc since 06h48m_UTC (see the attached plot), usually this occurred dutrng each maintenance period . 

The recovery was performed between 2026-10-09-10h41m16-UTC and 2026-10-09-10h43m45-UTC.

Below the details of the procedure to perform to recover the correct running confitions

Fom this VirgoOnline VPM window 

  • remove the SQ1_dbox_rack server from the FbsDet server 
  • stop the  EQB1_HD_CC server 
  • from the SQB1_dbox_rack server
    • re-configure the full EQB1_DBOX_03 dbox board 
      • in the DMS interface, the Daq_EER_DBOX3_timing_error  flag shoud be green but the  EQB1_HD_CC_DAC_ssfs_flags  and the  SQZ_CC_DAC_ssfs_flags are red now
    • then re-configure the  EQB1_HD_CC_DAC  FAST_DAC mezzanine 
  • restart the  EQB1_HD_CC server 
    • in the DMS interface, the  EQB1_HD_CC_DAC_ssfs_flags  shoud be green

As there is some signals from the  EQB1_DEMOD_03  demodulation mezzanine sent the SQZ coherent control FAST_DAC mezzanine, this one has to be re-synchronized.

From this VirgoOnline VPM window 

  • stop the  SQZ_CC_Ctrl server
  • from the SQZ_DBOX_DET_EERoom server
    • re-configure the  SQZ_CC_DAC FAST_DAC mezzanine
  • restart the  SQZ_CC_Ctrl server
    • in the DMS interface, the  SQZ_CC_DAC_ssfs_flags  shoud be green
  • perform  the reloadConfig of FbsDet server to restore the SMS data collection of the SQB1_dbox_rack server
Images attached to this report
AdV-DAQ (Calibration)
mours - 11:30 Friday 09 October 2026 (69884) Print this report
Restart NCals

All NCals have been restarted around 9:23 UTC at their nominal frequencies: around 36 Hz in h(t).

Detector Operation (Operations Report)
zaza - 22:54 Thursday 08 October 2026 (69882) Print this report
Operator Report - Afternoon shift

The afternoon shift was spent testing BS alignment loop and locking LOW_NOISE_3_ALIGNED (#69881 Bersanetti, Ruggi) and reactivating CALnoise configuration lines (#69880 Verkindt)

The data losses observed on Hrec stopped around 15:00 UTC.

ITF left in LOCKED_ARMS_IR for the night.

Guard Tour 18:30 UTC

AdV-ISC (Automatic Alignment)
bersanetti, ruggi - 22:52 Thursday 08 October 2026 (69881) Print this report
Tests for BS alignment loop and LOW_NOISE_3_ALIGNED

To we worked on the BS alignment loop; the idea is to move from the current control scheme to a new one, based on the new B1s_QD1_50MHz signals.

The current control scheme is:

  • TX: BS_BL_B4_6MHz: blending between B1p_QD1_50MHz_I (low-passed) at low frequency and B4_QD1_6MHz_I at high frequency (high-passed)
  • TY: B1p_QD2_50MHz_I (low frequency), which is sent to the DSP where the blending with the OpLev at high frequency happens.

This is the sequence of the tests we made, in different locks, all on the TX DoF, since it is the less robust one and the one most easily tweakable:

  1. we replaced the whole signal with B1s_QD1_50MHz, intercalibrated at low frequency with the low frequency weight (sensing weight = 0.207) (we didn't use it, but for reference the weight for TY is 0.11): at 14:29:15 UTC we made the handoff in drift control, around 14:38 (briefly) and then again 14:30:30 we tested in full bandwidth, but we unlocked; not because of the 1.2 Hz oscillation, but some other disturbance, that could be also seen by PR_TX
  2. we used the usual signal, but increasing the blending frequency by increasing the gain of the low frequency branch: 15:28:52 UTC B1p gain 2x in drift control, 15:29:23 UTC full bandwidth, shortly followed by the unlock;
  3. we replaced only the low frequency branch with B1s_QD1_50MHz with the overall same calibration as B1p_QD1_50Hz: full bandwidth test just before 16:22 UTC, quickly reverted before unlocking.

All data will be analyzed offline, but in all tests the coupling with PR_TX looks the one thing which is the most impacting the full bandwidth loop.

After that, several lock acquisitions were tested, undisturbed both in terms of acquisition and steady state; we also moved to LOW_NOISE_3_ALIGNED without having to change anything (same power as in the past, just reduction of lines and noise there). The locks do not last much, and they sometimes look very glitchy, at least by looking at Hrec. In any case, Hrec itself looked glitchy and some data was missing. Also in this case, we will look at data offline.

Regarding the recent automation of the input power increase, that worked very well, but we gained one case to study: after an unlock, INJ_MAIN went into the INJ_FAULT state around 18:51 UTC.

 

AdV-DAQ (Calibration)
verkindt - 19:28 Thursday 08 October 2026 (69880) Print this report
New calibration lines around 13 Hz and two new processes HrecSR and HrecOS

Today around 17h15 UTC, I have reactivated in CALnoise configuration the lines BS_MIR_permline1, WE_MIR_permline1, NE_MIR_permline1
with the new frequencies 10.8, 12.8 and 14.8 Hz. Those new calibration lines will be used by the new Hrec to get periodically the parameters of the Optical Spring
to be included into the Optical Response Model.

Also, around 13h UTC, I have started two new Hrec processes (HrecOS and HrecSR) that run in parallel to Hrec.

- Hrec:  /virgoApp/Hrec/v5r15 uses the same configuration as in O4 with an Optical Response model that has only one pole

- HrecSR: /virgoApp/Hrec/v6r01  uses a configuration where the Optical Response model contains one simple zero a double pole and no Optical Spring

- HrecOS: /virgoApp/Hrec/v6r01  uses a configuration with same OR model as HrecSR but with also an Optical Spring at low frequency (currently 5 Hz).

Around 17h00 UTC, I have stopped temporarily HrecSR and HrecOS because I suspected that they may be the origin of some data loss in Hrec. I will investigate this tomorrow.

 

AdV-ISC (Alignment control scheme conceptual design)
mantovani - 15:49 Thursday 08 October 2026 (69879) Print this report
SR tx demodulation phase tuning in LN2

The tuning of the SR tx and ty demodulation phase is quite hard since it is a very noisy and slow signal.

This time I tried a different approach.

I opened the SR TX loop, I made some steps in the alignment and then I found the demodulation phase that best reconstructed the I signal as:

I_tuned = A*(I_initial*(cos(phi))-Q_initial*(sin(phi))+offset

the outcome of the analysis is shown in figure 1 and the phase has been tuned to be 3.4 rad

lets see if this approach is reliable enough

Images attached to this report
Detector Operation (Operations Report)
berni - 15:40 Thursday 08 October 2026 (69876) Print this report
Operator Report - Morning shift

ITF found in locked_arms IR.

After a manual prealignmet of PR/SR and a couple of failed attempts the ITF reached LN2 at 8:01 UTC; Maddalena started working at the locking.

The ITF unlocked at 9:06 UTC.

From 9:12 UTC to 10:15 UTC the following activities were carried out:

  • PC camera realignment (Matteo);
  • Inspection at WE (Elian, Lorenzo);

 

From 10:16 UTC to 10:19 UTC ITF in single_bounce_NI; from 10:20 UTC to 10:22 UTC ITF in single_bounce_NI with PR TY misaligned -60urad; see phase camera alignment check.

 

After that Diego worked on the automation, activity still in progress.

 

SUSP

Sa MC COIL H1 reset by Paolo.

AdV-COM (automation)
bersanetti - 15:33 Thursday 08 October 2026 (69878) Print this report
Comment to Automation of the in-lock IMC power increase (69875)

The new code is online since roughly 12:00 CEST; a couple of full acquistions were done and they were successful but please report any issue, as I expect some corner case.

AdV-DET (Phase camera (2 to be developed))
tacca, lunghini, berni - 14:14 Thursday 08 October 2026 (69877) Print this report
phase camera alignment check
On the morning of October 7th and October 8th, I took some time to check and improve the alignment of the two phase cameras. The ITF was set in CARM_NULL_1F with the input power at 17 W.
- B1p: the reference beam and the probe beam (B1p) were already well superposed; I reduced the neutral density of the reference beam to increase the power reaching the photodiode and the SNR; I improved a bit the centering on the photodiode.
- B4: the reference beam and the probe beam (B4) were already well superposed; the probe beam was clipped by one of the diaphragms used to avoid back-reflections entering on SPRB and I recentered it; I improved the centering on the photodiode.
Figure 1 shows the acquired images.

On October 8th, starting from 9:41:05 UTC we took some minutes of data in the LOCKED_MICH_HF state to have reference images for the phase camera data analysis. In order to remove some interference fringes on B1p caused by some ghost beams, we had to misalign PR_TY by -60 urad (figure 2).

Following Michal's request we set the ITF in SINGLE_BOUNCE_NI to have some reference data for detector characterization monitoring:
- from 10:16 UTC to 10:19 UTC ITF in single bounce. Some interference fringes on B1p caused by some ghost beams are visible (figure 3);
- from 10:20 UTC to 10:22 UTC ITF in single bounce with PR_TY misaligned by -60 urad. The beams acquired by the phase camera are a bit cleaner (figure 4).
Images attached to this report
AdV-COM (automation)
bersanetti, pinto - 1:39 Thursday 08 October 2026 (69875) Print this report
Automation of the in-lock IMC power increase

For about a week now, the lock acquisition starts with 12 W of input power, then when reaching CARM Null the power gets increased up to around 17.5 W, profiting of the several gain servos to cope with such increase for most of the main control loops.

Today the automation of the procedure has been written and saved in the nodes files: it involves both INJ_MAIN and ITF_LOCK, but this is still offline and the nodes should not be loaded yet.

This new procedure involves no new states, but just internal logic and a new file, INJ_MAIN.set (ITF_LOCK.set will follow shortly, for different topics but the same philosophy), which takes inspiration from a similar concept used in the SQZ_FLT node. The main point is two-fold:

  • configuration files like we use them can be written by the nodes, but this can be dangerous if one has the file open and re-saves it, if the editor doesn't prompt quickly enough that the file has changed on disk; additionally, writing them from the nodes the way we do completely wipes out comments, which can be very annoying;
  • global variables in the automation are reverted to the default declaration value when the node is loaded, as they are read back from their definition that can be out of the states; this can be annoying for state flags that need to be remembered from lock to lock; additionally, they now get to be visible in a file at all times, instead of being hidden in the code running online in RAM.

Therefore, the idea is to use INJ_MAIN.set only for parameters written by the automation itself (or to debug it or to force a specific behaviour), and not for general parameters like the ones in the .ini files. The one related to the power increase is inj_power_state ([POWER] section): given that we plan to increase the power in two big steps (and then a finer open loop tuning), such flag can be 0, 1 or 2, depending if we are respectively at low power (12 W), intermediate power (only one coarse increase) or full power (two coarse increases, the finer tuning is not important here).

Here is what happens:

  • when we unlock, INJ_MAIN will go to DOWN and check such flag: if 0, nothing will happen (we should be at low power already); if 1 or 2, the node will perform 1 or 2 coarse reductions of power (5000 steps each), each time updating the parameter in the file; then, the INPUT_POWER_TUNING state will deal with the fine tuning down (or up) to 12 W, as usual but with a new logic;
  • ITF_LOCK: towards the end of LOCKING_CARM_NULL_1F, in two distinct places separated by at least 15 s, two coarse increases of power will happen (-5000 and -4500 steps respectively), the inj_power_state variable will be updated, and then the fine tuning to the target power (17.5 W) will happen, by having ITF_LOCK asking INJ_MAIN to use the same INPUT_POWER_TUNING state but in a very different place of the acquisition: the new logic of the state acknowledges the power state and either targets the lower power (when it reads 0) or the higher one (when it reads 2); the same check will condition using one or the other set of parameters; to avoid killing the lock, the number of maximum attempts to tune the power in CARM Null is much higher than the one we use in DOWN.

The new logic will start to be tested tomorrow.

Comments to this report:
bersanetti - 15:33 Thursday 08 October 2026 (69878) Print this report

The new code is online since roughly 12:00 CEST; a couple of full acquistions were done and they were successful but please report any issue, as I expect some corner case.

AdV-ISC (Commissioning up to first full interferometer lock)
bersanetti, pinto, mantovani, gouaty, ruggi - 1:35 Thursday 08 October 2026 (69874) Print this report
LOW_NOISE_2 recovery and new violin modes for the IMs

Most of the work of today was devoted to the continuation of the recovery, that ended up previously in DC readout, systematically unlocking afterwards when trying to go to LOW_NOISE_2 (I remind that, mirror actuators-wise, we skip altogether LowNoise1 and move directly from HighPower to LowNoise2).

It was found that a DC correction of several Volts was left on the NE actuator, most probably during the mode matching measurements. After removing that, we could go flawlessly to LOW_NOISE_2, getting in this way the sensitivity curve back; in Figure 1 the comparison with the very last we had briefly on 10 April.

We initially had around 27 Mpc, slowly rising up to 30 Mpc in the second lock of the afternoon. It is not that bad, considering that: in LOW_NOISE_2 a lot of lines are up and high, we have no subtractions working on DARM, SR is aligned and we have no diaphragm installed on the SRM, new IMs, a new optical configuration and no calibration measurements yet.

While staying in LOW_NOISE_2, we immediately noticed a new comb of peaks around 413 Hz, whose amplitude started to grow over time. By looking into it with some more resolution, we observed eight main peaks, with minor ones around them. Our conclusion is that these are the violin modes of the new IMs, which are considerably lower than the ones we were used to have (~ 440 Hz).

Given that we could not adjust the current notches to cover the whole band, we started the development of a new notch filter, to be used in parallel to the old one, which now covers only the EMs; we tried to have a reasonable amount of depth in the transfer function, trying to find the best tradeoff in terms of modification of the DARM response that the new filter would induce. While the magnitude is not that big of a concern, the dephasing it induces could be instead: with the filter we left in operation (Figure 2), we had around 0.2 rad of dephasing at 491.3 Hz, which can possibly have an impact on everything that is computed with the DARM_HF line, namely: double-cavity pole estimator, SR alignment signals, optical gain estimator, OMC figures of merit, etc..

In particular we observed the SR alignment during the next lock, starting from CARM_NULL_1F and then LOW_NOISE_2 (Figure 3, zoom for just CARM_Null in Figure 4): the absolute starting value of the DCP looks a little lower, and the trend during the lock (when SR gets more aligned) shows a decrease of the pole frequency, which may be an hint that the error signals need to be checked.

Afterwards, we could see new peaks around the ones we identified for the violin modes (Figure 5); some of them were spaced by peculiar amounts, like exactly 3.3 Hz, which is the frequency of the DIFFp TX line, which is clearly very strong in DARM (Figure 6). Maybe the fact that we are working decentered increases the coupling, to be verified. In the last lock we reduced such line (and the TY one) by a factor of 2, improving the situation (Figure 7). More work is needed on this topic.

Other topics:

  • in the first lock in LOW_NOISE_2, we engaged the BS alignment loops in full bandwidth, with the old B1p-based strategy; while TY could be closed with no issues, closing the TX loop caused the infamous 1.2 Hz oscillation to show up and eventually kill the lock;
  • the OMC lock showed some difficulty (entry 69871), as the threshold to correctly find the good mode to lock onto was not crossed, either because the DARM offset was too low or the DARM_HF line was too low; being the latter more unlikely, given the amplitude of the line, the working theory is that the DARM offset on the RF signal is smaller than in the past in terms of meters; we then modified the lock acquisition, in order to use a higher offset at the beginning (-0.26 online, -0.3 set up for the next trials, instead of the usual -0.2), then allow the OMC to lock, then go back to the usual offset before the DARM handoff to B1_PD3, so not to modify the DC readout acquisition at all; we tried it once and it worked as expected, and this is now automated.
Images attached to this report
Detector Operation (Operations Report)
menzione - 21:45 Wednesday 07 October 2026 (69872) Print this report
Operator Report - Afternoon shift

ITF found in LN2 in COMMISSIONING mode with planned activity on "LN2 locking/tuning (Pinto Bersanetti)" in prigress.
It went on without major problems till the unlock around 18:51 UTC due to a thunder.

BAD_WEATHER mode set.
At 19:00 UTC an IPS black-out occurred in CB, WE, NE. All UPS systems worked properly waiting for the generators to turn on.
At 19:30 all systems went back in standard state: IPS ON, gaenerators OFF.

ITF left in LOCKED_ARMS_IR.

Sub-system reports

Air Conditioning
ACS cooling system in failure during the black-out.
HVAC..MCB_1_COLD_TE and HVAC..MCB_2_COLD_TE stuck
Upon recovered the IPS the ACS machine restarted automatically.

Pending actions

Other
(07-10-2026 19:00 - ) Automation - Do not LOAD ITF_LOCK and INJ_MAIN !!!

Oncall events

Air Conditioning
(07-10-2026 19:00 - 07-10-2026 19:30) From remote
Status: Ended
Description: ACS cooling system in failure during the black-out.
HVAC..MCB_1_COLD_TE and HVAC..MCB_2_COLD_TE stuck
Upon recovered the IPS the ACS machine restarted automatically.
Actions undertaken: No intervention needed

Images attached to this report
AdV-DAQ (Data Acquisition and Global Control)
masserot - 21:31 Wednesday 07 October 2026 (69873) Print this report
DBOXes with Timing error

The DMS reported some timing errors for the following DBoxes

  • CEB_DBOX_ALS, CEB_DBOX_LNFS and CEB_DBOX_SSFS 
  • EQB2_DBOX_01, EQB2_DBOX_02 and  SQB2_DBOX_SBE

The ITF locked in LOCKED_ARMS_IR  stare was put in DOWN 

They were reconfigured to recover the correct working conditions: operations performed between 2026-10-07-19h18m26-UTC and 2026-10-07-19h26m19-UTC . 

ITF successfully relocked at   LOCKED_ARMS_IR  after

Detector Operation (Operations Report)
lunghini - 17:21 Wednesday 07 October 2026 (69869) Print this report
Operator Report - Morning shift

ITF found in COMMISSIONING Mode and LOCKED_ARMS_IR State.
All times are UTC.
06:36 ITF in CARM_NULL_1F after CITF manual pre-alignment and manual increase of input power upt to 18W once reached the CARM_NULL_1F state.
07:08 - 08:31 Investigation on LOW_NOISE_1 unlocks (Mantovani, Bersanetti).
09:28 - 11:09 ITF in CARM_NULL_1F state for PC realignment (Tacca).
When trying to reach LOCKED_DC_READOUT the OMC did not locked, in order to prevent possible damages to the OMC I manually unlocked the ITF because the temperature was rising too much. I informed Gouaty about this issue and he will try to lock the OMC manually once the ITF will be in CARM_NULL_1F state. DET expert was able to lock the OMC by lowering from 1500 to 1000 the threshold on B1x_DC_DARM_norm_prod (#69871).
12:48:27 ITF in LOW_NOISE_2 since March 25, 2026, and for a short time on April 10, 2026. 

ITF left in LOW_NOISE_2 state and COMMISSIONING Mode.

Images attached to this report
AdV-DET (Commissioning)
lunghini, gouaty - 14:30 Wednesday 07 October 2026 (69871) Print this report
OMC locking issue due to too low signal on B1_PD3

Lorenzo noticed that during the OMC scan of 11h10-11h20 utc the OMC did not lock on the TEM00 resonance. This is due to the fact that the threshold of 1500 set on the B1x_DC_DARM_norm_prod signal was not reached. During the next attempt it happened again (Fig.1). Therefore I decreased the threshold from 1500 to 1000 and in this way the OMC could be locked (Fig.2). When the reaching DC readout the computed optical gain was about 0.9, which means that the OMC alignment seems to be good. Therefore the problem is rather related to a too low DARM line or to a too low DARM offset.

I think that the reduction of the B1x_DC_DARM_norm_prod can only be a temporary patch, but it is not a good solution as there are other modes that may be close to reaching this threshold (see for example the mode reaching 800 on Fig.1). I noticed that the power on B1_PD3 is now very small (order of 1uW). Therefore I would suggest to increase the DARM offset used to acquire the OMC lock. Once the OMC is locked the DARM offset can be reduced to its current value to reach DC readout.

Images attached to this report
AdV-ISC (Commissioning up to first full interferometer lock)
ruggi, pinto - 10:27 Wednesday 07 October 2026 (69870) Print this report
Comment to Local damper on PR mirror vertical mode at 11.6 Hz (69799)

One more issue has been observed concerning the local damper of PR vertical mode at 11.6 Hz, in addition to the permanent excitation due to the noisy sensor. As shown in fig 1, sometimes a fast glitch affects the sensor, inducing a strong reaction of the loop. The effect on PRCL is large and sometimes in can determine a lock loss (fig 2).

After the successful attempt to open the damper in a stable lock, reported in the previous entry, an attempt to acquire the lock keeping the damper always off was performed, but again the bouncing mode appeared to be unstable during some phase of the lock acquisition (fig 3).

Yesterday we decided to implement the correct strategy, profiting of the maintenance. In CARM NULL a much better sensor of PR vertical motion is available: this is the quadrant used to control the beam jitter. It has been used in the past to slowly control PR vertical position and it is still named 'ASC_PR_Y_INPUT'. Its signal to noise ratio at the resonance is about a factor of 1000 higher and the response to the actuation has the same shape. It was already available in PR DSP and it was just matter to implement a logic able to swap from the local sensor to the quadrant as soon as the second one is ready for the use. It happens at the beginning of CARM NULL and the switch already used to close the beam jitter control can be used also for the swap of the damper.

The implementation was quite straightforward, but the first attemp to use it after the maintenance failed because of a stupid error. In the following locks it worked fine and the advantages are quite evident (fig 4, 5, 6, 7).

Images attached to this comment
Detector Operation (Operations Report)
zaza - 22:36 Tuesday 06 October 2026 (69868) Print this report
Operator Report

The commissioning activity was carried on through the afternoon: #69867 and #69866 (Boldrini, Bossilkov, Bersanetti, Gouaty, Was)

At the end of the activity, the ITF was left in LOCKED_ARMS_IR

 

Guard Tours

18:00

20:35

AdV-DET (Commissioning)
boldrini, bersanetti, gouaty - 20:40 Tuesday 06 October 2026 (69867) Print this report
OMC alignment in DC readout

While the ITF was locked in DC readout this afternoon, we enabled the computation of the B1 DARM dither signal and engaged the B1 DARM beam drift control of SDB1 (Fig.1). This has the effect of increasing the optical gain by almost a factor 2, while the bench alignment changed by almost 10 urad in TX and by 1 or 2 urad in TY.

Accordingly after the unlock, the B5 QD2 offsets were updated (H=+40 and V=+200).

Images attached to this report
AdV-ISC (Commissioning up to first full interferometer lock)
boldrini, bossilkov, bersanetti, gouaty, was - 20:40 Tuesday 06 October 2026 (69866) Print this report
DC_READOUT recovery and B1s hand-off

We recovered the DC_READOUT state, after a few hiccups. We realized that the unlocks when attempting the hand-off to B1_DC were due to a "slow" oscillation on DARM that, when compounded with the high 491 Hz line, would trip the threshold of the fast shutter.

To cope with this, we restored the change of DARM_GAIN in the LOCKING_OMC_DARM_B1_PD3 state (line 5199) and prepared a gian in the ini file that was a bit higher than the one set up by the servo before this step. This allowed to acquire the DC_READOUT state, but the DARM servo further increased the gain substantially. We set a gain close to this final number in the ini file and tested the lock acquisition, successfully.

Before proceeding with the B1s hand-off, we allowed Gouaty to re-enable SDB1 drift control, which increased DARM OG substantially (Fig.1). DARM servo adjusted the gain of the loop to 0.074 after this change, therefore we corrected the corresponding parameter in the .ini file to a value closer to this (0.064), to leave some margin for further evolution during this state.

After that Gouaty opened the shutters for B1s_QDs and we measured the transfer function at low frequency between B1p and B1s and tested the hand-off with these commands:

  • ASC.BS_TY_INPUT.AcMatrixChSet(5.0, 0.0, "B1p_QD1_50MHz_H_I", -0.065, "B1s_QD1_50MHz_H_I")
  • ASC.BS_TX_INPUT.AcMatrixChSet(5.0, 0.0, "B1p_QD1_50MHz_V_I", 0.31, "B1s_QD1_50MHz_V_I")

The hand-off worked without issue, although the BS alignment is still on drift control so this test is not indicative of the final performance of the loop wih this new error signal.

The lock was disrupted by an earthquake, after the shock passed we attempted another lock acquisition, succesfully, but the ITF unlocked again while attempting to engage LN2.

The recovery of this state is postponed to tomorrow.

We leave the ITF with the arms locked.

Images attached to this report
AdV-DET (Commissioning)
gouaty, berni, bersanetti - 18:42 Tuesday 06 October 2026 (69863) Print this report
OMC slow shutter now being used in MOVELIMIT mode

This morning we performed some tests of the OMC slow shutter in order to investigate the issue faced yesterday afternoon.

Francesco put the ITF in single bounce mode. We put DET_MAIN in pause and tried to act on the OMC shutter from the SDB1_Rot process using the MOVELIMIT command. The first attempts of opening the shutter in this way failed. We also tried to close the shutter (in case the sign in the command was wrong), but this did not open the shutter neither.

Then we opened the shutter using the relative movement of 45000 steps. After this was done, we clicked on "Stop movement". After this, we tried to close the shutter using again the MOVELIMIT command, and this time it worked. We then performed a few cycles of opening/closing the shutter with MOVELIMIT which all worked fine.

We updated the DET_MAIN.py file in order to use the MOVELIMIT command instead of the relative motion. We put DET_MAIN back in exec and reloaded the node. We tested a couple of cycles of opening/closing using DET_MAIN and it worked fine.

We also updated the opening and closing durations set in the DET_MAIN.ini file, as the motion with the MOVELIMIT command is faster. Looking at an example of opening sequence (Fig.1) we can see that the opening takes between 25 and 30s. Therefore we set the opening duration to 45 s (we leave at least 15s of margin). For the closing (Fig.2), the duration is about 35 s. We set the closing time to 60s.

For the record previous values for the opening and closing durations were 80 and 100 s respectively.

These durations could be optimized further when we have more statistics.

Images attached to this report
Search Help
×

Warning

Error

The present report has been modified outside this window. Please check for its integrity in the main page.

Refreshing this page will move this report into drafts.

×