we post the angular noise budget computed after a set of measurements performed this morning.
working conditions of the ITF: decentered position of the beam on the WE (12mm offset on vertical).
DIFFp TX (blue curve) shows higher coupling.
we post the angular noise budget computed after a set of measurements performed this morning.
working conditions of the ITF: decentered position of the beam on the WE (12mm offset on vertical).
DIFFp TX (blue curve) shows higher coupling.
This is a report on the hardware installations, performed on May 13th, for the phase noise cancellation loop of the fiber between Inj and EQB1. The installations involved several laboratories
Atrium:
The fiber circuit of the phase camera and the squeezing in atrium has been modified (figures 1,2) in order to decouple the phase camera outputs from the one used to power the box “phase noise box” (fig3) containing the setup for the fiber phase noise cancellation loop . In this way, for the phase noise cancellation loop, we act on a dedicated AOM (operating at 100 MHz) independent from that of the phase camera.
Injection E-Lab:
The electronics for the phase noise cancellation have been installed in the Injection E-room. The installation includes a HP8656 RF generator equipped with a custom RF amplifier that serves to power the AOM at 100 MHz and a new 4-channel DDS generator that provide our low phase noise frequency reference (fig4)
DetLab (EQB1):
The optical fiber coming from the atrium to EQB1 has been split in two. One output goes to the main PLL of the squeezer as in the old set-up and the other branch to the fiber reflector (see fig 1 scheme).
Finally, 3 low attenuation RF cables (L=15 meters) were laid between the atrium and the E-room.
There was no time to test the loop operation, which will be done as soon as possible in agreement with the ITF planning. The feedback system is therefore left off.
The NE and NS NCal power supplies were left OFF at the end of the NCal work of yesterday. They have been turned back ON and the NE NCals restarted this morning at 5:42 UTC
I updated virgoData/VirgoOnline/SNEB_dbox_rack.cfg to set the reference positions of NW rotors to 0. Attached image shows the position histograms after this operation.
ITF found in LOCKING_ARMS_BEAT_DRMI_1F, we were able to reach ACQUIRE_LOW_NOISE_3, but the ITF unlocked 13:41 UTC.
From 14:00 UTC to 17:35 UTC the Cal Team worked at the both terminals for the planned NCal Activity (see reports #66781), after that the recovery of the ITF, carried out by Mantovani and Bersanetti, started (see reports #66782, #66784).
Activity concluded at 21:35 UTC, ITF left with AUTORELOCK_FAILSAFE engaged at CARM_NULL_1F.
We spent the evening in trying to recover the interferometer, activity which, by the way, we could not do for most of the day.
Despite scheduled times for the different activities, two locks were killed at the end of the acquisition by two ill-advised actions which both impacted SNEB_Fb:
2025-05-14-18h10m23-UTC>ERROR..-[TfbSource::StoreData] producer SNEB_Quadrants_DAQ_10000Hz: overflow at GPS 1431281441.199935050 (received 2001 / expected 2000) (2 times)
2025-05-14-18h10m23-UTC>ERROR..-[TfbSource::StoreData] producer SNEB_LC_DAQ_10000Hz: overflow at GPS 1431281441.199935050 (received 2001 / expected 2000) (47 times)
2025-05-14-18h10m23-UTC>ERROR..-[TfbSource::StoreData] producer SNEB_PSD_sensing_DAQ_10000Hz: overflow at GPS 1431281441.199935050 (received 2001 / expected 2000) (15 times)
2025-05-14-18h10m23-UTC>ERROR..-[TfbSource::StoreData] producer SNEB_Photodiodes_DAQ_10000Hz: overflow at GPS 1431281441.199935050 (received 2001 / expected 2000) (51 times)
2025-05-14-20h27m37-UTC>ERROR..-[TfbSource::StoreData] producer SNEB_Quadrants_DAQ_10000Hz: overflow at GPS 1431289675.199935070 (received 2001 / expected 2000) (2 times)
2025-05-14-20h27m37-UTC>ERROR..-[TfbSource::StoreData] producer SNEB_LC_DAQ_10000Hz: overflow at GPS 1431289675.199935070 (received 2001 / expected 2000) (47 times)
2025-05-14-20h27m37-UTC>ERROR..-[TfbSource::StoreData] producer SNEB_PSD_sensing_DAQ_10000Hz: overflow at GPS 1431289675.199935070 (received 2001 / expected 2000) (15 times)
2025-05-14-20h27m37-UTC>ERROR..-[TfbSource::StoreData] producer SNEB_Photodiodes_DAQ_10000Hz: overflow at GPS 1431289675.199935070 (received 2001 / expected 2000) (51 times)
This sums up to almost two hours lost, of the only five we could work today for recovery.
It is not acceptable not being able to coordinate the work in a decent way. During a lock recovery no other actions should be done on the interferometer.
We have recovered the LN3 configuration. The recovery went smoothly, reached LN3 at the second attempt after one unlock in locking LN2.
We tested first the configuration in which the beam is centered in the West end mirror.
In figure 1, the comparison between the "after-cleaning" in purple and the "pre-cleaning" in blue sensitivities is shown (beam centered).
- the 3Hz is not present and the low frequency sensitivity is back to the best level
- the frequency noise at high frequency is much higher than before.
We left the ITF in LN3 for ~15 mins and we decided to unlock to test the decentered position of the beam on the WE (12mm offset).
We unlocked at locking in LN3, see next entry.
We leave in auto-relock with the decentering offset on.
Erratum : the explained axis convention was wrong. We checked it on may 14 2025, here is the correct one:-Axial Lateral, along the x-axis, corresponding to the laser beam (increasing when moving away from the central building)
-Vertical along the z-axis (positive upward)-Lateral Axial, along the y-axis, with y = z ^ x
Erratum about logbook entry #66257 (https://logbook.virgo-gw.eu/virgo/?r=66257): the explained axis convention was wrong. Here is the correct one:-Axial Lateral, along the x-axis, corresponding to the laser beam (increasing when moving away from the central building)
-Vertical along the z-axis (positive upward)-Lateral Axial, along the y-axis, with y = z ^ x
All setups have been checked for conformity with this convention.
All reported times are in UTC.
Work on NCAL in North End Building
13/05/2025
Unload box and start the installation of the new NCal setup around the NE Mirror:
~6:30 Stop all rotors and switch off power supply
-7:13 -9:00 drill hole for new East table
-9:05-10:00 start drilling holes for new West table
-11:10-12:00 finish drilling holes for new West table
- East table screwed on tower base at 18:00
-18:00 Support #2 fixed on East table (NE)
-18:13 zero setting of the NE support
In parallel
- Disassemble “old” NEN and NEF setups:
-Rotor assembly:
Warning : a positioning reference hole of platform #3 are not correct. It must be reamed.
14/05/2025
We continued the NCal activities around the NE mirror:
- we fixed the West table on the floor on the morning
- we put the NW NCal support at it nominal position with reference spacers on the afternoon
- we update the SNEB_dbox_rack configuration to set their reference positions to 0:
- we put the NEN and NWN NCals in place:
Work on NCAL in West End Building
13/05/2025
Cf logbook entry https://logbook.virgo-gw.eu/virgo/?r=66763
14/05/2025
On WSN support, we installed counterweight and rotor 31 (box 11).
On WNN support, we installed counterweight and rotor 33 (box 2).
Electronic cabling done
Setup positions adjusted (see images)
Installation of all West end building rotors is complete. All have been runned between about 16:00 and 17:00 at around 18Hz.
For North End building (NEN and NWN), cabling and alignment must still be completed
I updated virgoData/VirgoOnline/SNEB_dbox_rack.cfg to set the reference positions of NW rotors to 0. Attached image shows the position histograms after this operation.
The NE and NS NCal power supplies were left OFF at the end of the NCal work of yesterday. They have been turned back ON and the NE NCals restarted this morning at 5:42 UTC
May, 14th, SQB1 FIs -I Ipart
Martinez, Bouvier, Bonnand, De Laurentis
Goal: check the SQB1 FIs temperature control loop.
Befor eto go on with the goal, the yesterday activities has been ended: the connector has been unsoldered to have the right connection (see picture below).
Corrected connection plugged to the Peltier controller
(gray wire : PT100, red wire : Peltier module)
It appeared, after testing using a multimeter, that the PT100 of the Faraday 1 is not working. It could be a false contact or a short circuit.
For this reason the control loop test has been made on ly on FI2
ANNOTATION on the cable and DAQ channel
From labels on the SQB1 HWPs cables in E-room, and from OpticLab in VPM (https://vpmrd.virgo.infn.it:40000/main.html?subsystem=Optic+Lab&process=SQZ_Rot):
A corresponds to Axis 1 -> HWP 1 (toward ITF)
B corresponds to Axis 2 → HWP 2 (betwen FI2 and FI3)
According with this FI1 and FI2 signals on dataDispaly icorrespond to the cable label A and B, repsectively (see picture below)
The control loop implemented by Alain in the configuration file, has been tested using - to start - the same parameters of the similar OMC temperature control. In practice we copy in the filter file
lines from 45 to 60 of the OMC temperature control configuration file.
The test was positive but some parameters and configurations (boost seems not working) must be checked. We plan to do this in the next days.
Goal: check the SQB1 FIs temperature control driver for the Peltier actuators and the pt100 sensors
Check the driver, yet mounted in the e-room rack (on the top of TCS rack (https://logbook.virgo-gw.eu/virgo/?r=66440https://logbook.virgo-gw.eu/virgo/?r=66440) stand alone with a Peltier module and pt100 sensor and a oscilloscope;
Connect to the DAC and check the dataDIsplay channels ()https://logbook.virgo-gw.eu/virgo/?r=66598;
Connect to the FI1 and FI2 peltiers and pt100 (cable ready)
First two steps, successufully resched. The last gave a current overload. Checking the possible causes, some swap of the wires on the connector pins has been found (see attached picture that compares the pin from the stand alone sensor and actuator and the ones of the connector plugged on the cable coming from SQB1). In th efollowing picture is it is possible to see: on the left handside, the connector plugged on the cable coming from SQB1; on the right handside : the connector of the stand alone sensor and actuator
In today's lock the 3Hz comb and the broadband noise underneath seem no more present. Also the 178Hz peak is (at least reduced).
While the ITF was locking this afternoon I took some images with the thermocamera installed on WE viewport.
Fig. 1: shows the ITF unlocked.
Fig. 2: shows the ITF locked in CARM_NULL.
Fig. 3: shows the reconstructed image including the baffles done by G. Cagnoli (red one is the inner baffle, cyan one is the outter baffle, the green circle is the mirror surface with 2cm grid lines and the orange sign is the center of the mirror) superposed to the thermocamera images. I also put a red dot to highlight the bright spot seen by thermocamera.
To be kept in mind for comparison when we will be able to do more tests with different offsets.
After Boschi recovered the WE inertial damping, we proceeded with the recovery.
The ITF reached LN2 by itself, but suffered un unlock, most likely due to a drift on BS_TX. Upon further investigation, we discovered that the galvo loop for B4_QD2, used for the high frequency branch of the error signal, was not engaged (Fig.1). This specific galvo loop is never engaged by Metatron, it probably never posed any problem. We manually re-engaged the loop and added a command in ITF_LOCK.py, line 3909, to engage it before switching the BS_TX error signal.
The next attempt was disrupted by an unlock in CARM_NULL_1F, which left the WI guardian open. We investigated and discovered that the suspension's top stage tilted by ~800 urad on TY in about half a second before the unlock (Fig.2). Ruggi and Pinto recovered the WI suspension and are investigating the issue. The top stage control disengaged due to a corrupted data package sent to the dsp.
The third attempt successfully reached ACQUIRE_LN3, but the ITF unlocked after a glitch on NE LN correction (Fig.3). Even though the acquisition of LN3 was not complete, the DCP was just ~20 Hz away from the threshold that triggers the transition and the sensitivity was about 32 Mpc.
In agreement with Mantovani and Was, we allow the work of Ncal for the moment.
ITF found in LOCKED_ARMS_IR in UPGRADING mode.
- WE ID loop recovery concluded (Ruggi, Pinto)
- Lock recovery in progress...
- SQB1 Faraday temperature controller (De Laurentis) in progress...
- NE Ncal support (Mours) in progress... In pause up to 14:00 UTC
At 11:00 UTC I started the lock acquisition (COMMISSIONING mode set).
After the usual cross-alignment in ACQUIRE_DRMI I locked ITF up to LN2 at first attempt. During the lock I re-enabled again SDB2 floating setpoint.
Today we investigated the issue experienced yesterday with the ID of the WE.
We performed a measument in order to recompute the calibration for the accelerometeres. We found out that ACC_H1 was the one miscalibrated, but the correct compensator was the one used before the last update. One possibility is that the accelerometer switches between two states. The reason of this behaviour is not clear. Some investigation is needed.
In the meantime, we reloaded the older compensation filter, and we modified the DSP card adding one switch for the two compensators in order to have the possibility to move between one 'state' and the other.
This is a good reminder.
Figure 1. shows that SDB1 has changed orientation compared to where it was a few weeks ago, and during the recovery it has moved further away.
This morning I have disabled the floating set points (the bench learning and remembering on its own what are the set points), and put back the set points to the average values of the bench orientation in TX and TY from beginning of May.
We will see if helps, the interferometer locked on DRMI for 20 seconds, and the B1p quadrants galvo close during that time.
The work on newtonian calibrators, both on north end and west end, went on in the afternoon in parallel with the west arm lock recovery; the west arm has been realigned and relocked with the green lock too, during this work we noted a strange behavior of the WE suspension control with a slow oscillation that grow up, switching off the ID control it disappeared; I called Valerio to work on this problem, he didn't able to solve it postponing any other intervention to tomorrow morning, we continued to work with the WE controlled without the inertial damping; the work on newtonian calibrator stopped at around 18:15UTC and we continued with the lock recovery, we succeded to lock up to the DRMI but the lock was not good; we stopped here, I left the cavities locked on the infrared. Oncall events
Oncall eventsSUSP
(13-05-2025 15:15 - 13-05-2025 16:00) From remote
Status: Ended
Description: WE inertial damping not working
What we see looks similar to something that happened recently (#66258), and some interplay between SR and SDB1 alignment was the cause, I don't know if that is the case also now.
After the recovery of the West Arm and the end of Ncal operations, we started the recovery of the ITF without WE inertial damping.
The recovery proceeded smoothly until the lock of the DRMI, but we couldn't continue because the galvo loops would not stay closed. The DRMI lock itself is unstable, and does not last more than a few minutes, because the alignment loops are not working properly.
The beam on B1p camera looks reasonably well centered, so it might not be related to a bench misalignment.
It is not clear whether this is related to the absence of inertial damping on the WE, we contacted Diego and, as instructed, we leave the ITF as is.
The recovery will be continued tomorrow.
What we see looks similar to something that happened recently (#66258), and some interplay between SR and SDB1 alignment was the cause, I don't know if that is the case also now.
This is a good reminder.
Figure 1. shows that SDB1 has changed orientation compared to where it was a few weeks ago, and during the recovery it has moved further away.
This morning I have disabled the floating set points (the bench learning and remembering on its own what are the set points), and put back the set points to the average values of the bench orientation in TX and TY from beginning of May.
We will see if helps, the interferometer locked on DRMI for 20 seconds, and the B1p quadrants galvo close during that time.
Between 6 am and 10:30 am UTC, we did the following activities on West-End NCal Setup:
- we adjusted the microphone gains,
- we recabled the power supply of south and west position sensors,
- we prepared for the installation of WNN and WSN.
We resumed WNN and WSN installation at 5 pm UTC by fixing both rotors on the corresponding platines.
Installation to be continued.
Today we started the recovery of the interferometer by working on the West Arm.
We could see from the beginning two (one and its reflection?) white spots on the WE camera, which we could not remember (see Figure, WARM unlocked but flashing).
We looked for flashes on both B8 and, after misaligning NI, B4, without finding any, even with the "snail". We then checked the old position of WE MAR LCs and they were quite different with respect to the current ones. We recovered those and the snail could find flashes quite soon, first on the camera markers signals, then on the photodiodes.
We could easily relock the West Arm (no change in demodulation phase or anything), but the locks did not last much, and we could see a very big oscillation on the MAR correction at about 80 mHz. Fabio pointed out that the Inertial Damping of the WE was not working as expected, probably since quite a while.
Valerio had a look at the ID loop, but in the end we kept it open (Position Control) and somebody will look at it tomorrow morning.
With the West Arm locked we checked the drift control on SWEB and slowly discharged its memory; also, we re-engaged the BPC loop for the West ALS. Then also the ALS could be locked without issue.
We also did the initial tuning of FmodErr, which was quite off, without problems.
At this point the automation was put back together so that later in the evening we could do some tests of the full lock acquisition. The reverted changes are the same ones of last time, with a few minor differences:
The CEB_DBOX_LNFS and CEB_DBOX_ALS Timing error flags was red since 2025-05-12-15h33m38-UTC .
These 2 DBOXes were reconfigured between 07h34m48-UTC and 07h51m25-UTC (see the plot)
The ALS_CEB servers have been stopped and restarted and the BPC_{N,W}ARM_PZT_{x,y} have been restored to theirs previous values.
During the maintenance period, the Timing error flag became red for the EQB1_DBOX_03 DBox ,. It has been reconfigured at 12h49m19-UTC as well the EQB1_DEMOD_03 Demodulation mezzaine, the EQB1_HD_CC_DAC FAST DAC , and the SQZ_CC_DAC FAST DAC one to ensure the FAST DAC synchronization .
After these operations , the DMS Timing and Fast_DAC flags are green
ITF found in Upgrading mode, Down state with north cavity locked.
At 6:00 UTC ITF in Maintenance mode, below the list of the activities communicated in control room:
All the maintenance activities concluded at 10:51 UTC.
At around 12:30 UTC the commissioning crew started to realign the WEST arm; the NCal activity will continue in the afternoon.
Vacuum
The WE large valve has been opened in the morning.
ISC
At 7:29 UTC the WI Etalon loop has been re-enabled.
Suspensions / SBE
Due to the CAL activities at NE the NE ID loop and SNEB loop were opened by the guardians; I left them opened.
SWEB loop closed at 12:45 UTC.
WE mir z damper closed at 12:46 UTC.
Other
Grass cutting around the tunnel