We can apply the same logic to the B1p and B1s photodiodes to confirm whether they give similar results to those obtained with the phase camera.

In order to better compare, we can use the phase camera and also compute the sidebands dark port transfer function and calibrate their power at the dark port. The sum carrier + sidebands should give a similar value to the one given by the B1p and B1s photodiodes.

Figure 1. shows the calibrated phase camera powers (carrier and sidebands) after 1 hour of science mode (30th April).

Figure 2. shows a comparison of the phase camera calibrated power vs the calibrated B1p and B1s photodiode signals. For comparison the carrier only power and carrier + sbs signals are shown. The carrier + sbs power seems in agreement with the B1p PD2 and B1s PD1 photodiodes (B1p PD1 had weird results, maybe because of the shutter being on at some point).

Analysis of the OMC scans might show if the relative power between carrier and sidebands matches that seen by the phase camera.

In order to try to mitigate this problem, we have increased the shutter pulse duration from 20 ms to 40 ms for both B1_PD1 and B1_PD2. The SDB2_dbox_bench process has been reloaded at 14h52m27-UTC.

Figure 1, the 157Hz bump decrease in the first hour of each lock, Figure 2 during the shift yesterday it did not decrease because the MICH SET loop was intentionally disable for an hour, and then MICH SET adjusted quickly by hand. 

Figure 3 confirms that RIN coupling due to a MICH offset is the dominant coupling path fo the 157Hz bump. Blue was with a large RIN coupling to DARM, red  and yellow are with the coupling intentionally increased by adding a MICH offset in the wrong direction, and green purple and green are with the MICH offset adjusted to minimize the RIN coupling (at 1.5kHz).

Figure 4. As seen benfore when the PRCL offset is adjusted to minimize the frequency to amplitude conversion on B2 (blue and red lines), the B2 Audio spectrum is much cleaner, especially at high frequency.

Figure 5 and 6 what is surprising is that looking at the B2 quadrants. In the vertical direction the coupling of frequency noise (227Hz line) decrease in the vertical direction by a factor few, but in the horizontal direction there is no significant change. Does that mean that the coupling has a significant contribution of HOM? Note that this is true only for B2 QD1, on B2 QD2 the line at 227Hz is not visible in neither the H nor V direction, at any of the times. And on both quadrant the sum channel sees the line clearly and decreases by a factor 10 when adjusting the PRCL offset.

/users/mwas/ISC/RINanalysis_20240506/analyseRIN.m

Shift started with a couple of unlocks.

17:56 UTC turned off MICH SET loop (putting MICH_SET_CAL to zero)

MICH set loop had not converged, so PSTAB was not yet at zero.

18:00 UTC (5min) PRCL set = 8.0 to zero the frequency to amplitude conversion on B2.

18:06 UTC (5min) PRCL set = 8.0, MICH set = -5.0, to increase PSTAB to DARM coupling

18:13 UTC (5min) PRCL set = 0.0, MICH set = -5.0

18:23 UTC (5min) PRCL set = 0.0, MICH set = 12.0 to zero the PSTAB to DARM coupling

18:29 putting back MICH SET loop (cali at -100000)

Figure 1. I have noticed any changes in the sensitivity during this test, appart from the 157Hz bump getting smaller when changing the MICH set to zero the PSTAB to DARM coupling. To be checked more carrefully if MICH set is really the cause.

Figure 2. Summarizes the change in PRCL and MICH offset. A PRCL offset of 8 changes the PSTAB to DARM coupling by about the same amount as a change of MICH offset of 5.

https://git.ligo.org/virgo/commissioning/commissioning-tasks/-/issues/52

Today during the lock acquisition I have noticed that there was power on B1 PD1 while trying to lock the OMC.

Figure 1 shows fluctuation on B1 PD1 even though the voltage bias is off.

Pressing the close button of the shutter in vpm worked to close it, but before that I panicked and closed B1 PD3  and turned off its voltage bias instead. Which caused an unlock first as DET_MAIN has seen the B1 PD3 being turned off and put the interferometer in DOWN.

Maybe the B1 PD shutters are starting to be stuck again because the interferometer locks are becoming too long, and they are not open/closed often enough. We may need to add checks in the automation to check they are indeed closed.

The DCP measurement is likely just a witness of something else changing.

Figure 1 shows the same as on Paolo's figure, the optical gain changes from 3e9 to 2.9e9 and the DCP frequency changes by ~5Hz.

Figure 2 shows the squeezing test of last week. The SR TY set point was changed intentionally by ~25Hz, and the optical gain changed from 3e9 to 2.85e9.

So the change in DCP that occured during the weekend could explain only ~30% of the change in optical gain.

One of the reason for having a CARM SLOW control is the OMC. If there are fluctuations in CARM the OMC length needs to follow, and with higher CARM fluctuation the OMC lock RMS will become worse and increase the thermorefractive coupling. However, this is seems to be very far from limiting.

Figure 1 shows the current noise budget (May 3 early afternoon), and the magenta line is the OMC length noise projection. about a factor 100 below the sensitivity curve.

Figure 2 shows last night when the ground motion was large (and presumably CARM RMS worse), the OMC length noise projection is still about a factor 20 below the sensitivity curve.

Figure 3 before the reduction in the CARM SLOW loop gain the OMC length noise projection was so low that it did not show on the figure.

So my impression is that if needed the CARM SLOW loop gain could be reduced by another factor 2. But there might be other aspects of the interferometer than the OMC that require a low CARM RMS.

The unlock at 3:41 UTC could have been due to an earthquake. There was a seismic disturbance in both NEB and WEB at about that time.

Figure 1. The CARM noise injection caused SR to move by ~0.5urad, because it made the B1 photodiodes saturate. It needs to be understood how the CARM noise injection shape needs to be changed so it doesn't cause B1 saturations which will spoil the measurement.

Figure 2. Normal daily hrec calibration measurements (between 16:00 UTC and 16:10 UTC)  are no longer kicking the SR alignment.

In 2017 the PRC was measured to have a wrong length by 3-4mm: https://logbook.virgo-gw.eu/virgo/?r=36884

I have checked in Optickle that mistuning the sideband frequency by a 2 kHz (which should be equivalent to a 4mm cavity length change), the sideband behavior becomes asymetric with PRCL offset. WIth the sideband power increasing by 1-2% in one direction and decreasing by 1-2% in the other direction, when changing the PRCL offset by ~0.2nm. This is similar to the measurements done last Friday, but it disagrees with the PRCL calibration done a year ago: https://logbook.virgo-gw.eu/virgo/?r=36884. That calibration would say that the PRCL offset was changed by 1.5nm, which would make the sideband power change by a few tens of percent. Maybe that calibration is no longer valid, as some normalizing factors could have been changed when chaning PRCL error signal from 8MHz to 6MHz sideband, or when installing the RAMS on the 6MHz.

Figure 1 shows in red the normal situation, in blue with the frequency to amplitude noise coupling divided by ~2 by adding the PRCL offset and in purple by adding the PRCL offset which zeros the coupling. The power fluctuation on B2 at ~1.5Hz improve by a factor 10 when reducing the coupling, on B4 there is also an improvement by a factor ~3, while on B4 12MHz the situation becomes worse, with fluctuations increasing by a factor 2. That would make sense if we improve the resonance condition for the carrier and degrade for the 6MHz sideband.

Figure 2 are the same times but with colors not in the same order. It includes also the B7 and B8 powers, and while on B8 the improvement is monotonic when improving the frequency to amplitude noise conversion, on B7 it is not the case. Is that a consequence of one arm being 3cm shorter than the other?

Lets assume that the PRC length is wrong by ~3mm, there are several options to resolve this:

1. Move PR by 3mm, which then requires retuning the input beam mode matching as it will change the input beam mode matching by one or a few percent
2. Change the sideband frequency by ~2kHz, but that would require moving the IMC end mirror by ~5cm to follow, so it is not a viable option
3. Move the input mirror by 3mm and maybe  also the end mirrors to keep the arm length the same. It might be the easiest to do and is the most reversible. It will also change the SRC length, but we have no measurements whether the SRC length is right or wrong, and it should be less critical because of the low finesse of the SRC.

Glitches might have stopped because the WI etalon loop error signal has finally become negative. The loop is asking for cooling the WI tower, which means turning the heating belt off. This switch off didn't happen immediately, but with an on/off for 10 minutes, so it is most likely due to the loop itself and not from an intentional switch off.

Nice find. Figure 1 and 2 made using omicron-plot show that these glitches in the WI MAG started at the same time as the glitches in h(t) around 20:00 UTC, and that they have not been happening the day before, and have been happening since then. There are magnetic glitches between 150Hz and 200Hz that have stopped a few hours before the glitches at ~30Hz started. The two might be related.

Figure 3 shows that this glitches are not visible on the NI MAG. So it is likely that the issue is close to the WI.

Next steps should be:

• Use the veto based on the WI MAG channel between 10Hz and 40Hz for GW analysis
• Try to find the source of the WI MAG glitches. Is there a piece of hardware that is starting to fail near WI

Figure 1. From about 20:00 UTC yesterday there are many glitches in h(t) around 30Hz. The glitches between 18:00-19:00 UTC are normal, these are due to injections to measure coupling to h(t) of various of degree of freedom. What happens starting from ~20:00 UTC is in science mode, and needs understanding.

Figure 2 The SNR of these glitches has grown from ~15 to ~30 over 1 hour, and has been relatively steady since then. There were several unlocks since the problem started and the glitches have continued at the same SNR after the relocks.

Doing a PRCL offset scan to minimize the frequency to amplitude coupling at the input of the interferometer: https://git.ligo.org/virgo/commissioning/commissioning-tasks/-/issues/12

Starting after the calibration measurements between 16:00 and 16:15 UTC. The steps are done at a speed of ~1 unit of PRCL per 20 second.

16:22 UTC (5min) PRCL_SET = 1.0
16:28 UTC (5min) PRCL_SET = 2.0
16:35 UTC (5min) PRCL_SET = 4.0
16:42 UTC (5min) PRCL_SET = 6.0
16:51 UTC (5min) PRCL_SET = 0.0
17:00 UTC (5min) PRCL_SET = 6.5
17:07 UTC (5min) PRCL_SET = 6.2
17:16 UTC (5min) PRCL_SET = 12 - interupted by unlock just after 17:18:40 UTC

just after reaching LN3

18:10 UTC (5min) PRCL_SET = -6.0
18:17 UTC (5min) PRCL_SET = 0.0

Figure 1 summarizes the scan done up to the unlock, PRCL_SET ~ 6 correspond to zeroing the frequency to amplitude conversion by the interferometer as seen on B2. It also shows that adding the offset in PRCL reduces the 6MHz gain as seen on B4 12MHz by 2%.

Figure 2 compares the time with the frequency noise coupling to minimized (blue) to the normal situation (purple). The B2 noise is 10 times lower between 1Hz and 3Hz, and it is also lower above 1kHz where the frequency noise is dominant. In between B2 is dominated by the pole at ~500Hz noise, subtracting it using B5 or B4 could reveal more clearly the improvement in coupling of frequency noise to B2 at other frequencies. There is no wideband impact on the h(t) noise.

Figure 3, 4, 5 show that the frequency noise lines (227Hz, 1111Hz and 3345Hz) are a factor ~30 lower on B2, and about a factor 2 lower in h(t).

Figure 6  my impression is that the coupling of frequency noise to h(t) becomes lower because for SSFS_LF the I and Q quadratures become more overlapped, so the BS TY minimizes both at the same time, and for SSFS_LINE the I and Q quadratures (that are very correlated), become of equal magnitude but opposite sign.

I wonder what it means that the frequency to amplitude noise coupling is zeroed, while the sideband gain decreases. Does it mean that the sidebands are not well tuned to the length of PRCL, and we need to choose to have carrier well resonant or sidebands well resonant?

Figure 7 the coupling of frequency noise to B2 has been quite stable since the beginning of the run

Figure 8 shows the PRCL offset scan done just after the unlock. This scan went with the same magnitude but in the wrong direction for the frequency to B2 noise coupling, and this time it increased the B4 12MHz mag signal by ~1.3%. So it points towards the current working point being in between being good for sideband gain and being good for the frequency to amplitude coupling at the interferometer input. That would intuitively make sense if the sideband frequency doesn't match the PRCL length, and the RF error signal that is the between sideband and carrier finds a working point in between being good for the carrier and for the sideband.

A question is if the optical gain for differential signals created inside the CITF is different from the DARM optical gain as a function of SR alignment. The 56MHz optical gain which involves being recycled by SR is not affected by the SR misaligment, because the ~1.5urad SR misalignment is small compared to the ~12m length of the CITF, and the CITF is marginally stable. Is it the same for differential perturbations created by the BS?

Figure 1 shows a lock acqusition, with SR aligned at the beginning (pole at 400Hz) and then 10 minutes later misaligned (pole at 200Hz)

Figure 2 shows three times, 21:10 UTC with SR still aligned (purple), 21:20 UTC with SR misaligned (red), 21:30 UTC with SR aligned (blue)

Figure 3 zooms on the BS drum mode (1872Hz VIR-0476A-16 https://tds.virgo-gw.eu/?content=3&r=12696). It is decreasing over the 10 minutes of SR misalignment, but then in the following 10 minutes is decreases again by the same fraction in h(t). Hence this decrease is not a change in optical gain, but just the drum mode damping. Meanwhile on B1 the first step is clearly larger, as the optical gain at high frequency changes due to the SR misalignment. So it seems the optical gain evolves the same way as the DARM gain. And there is no strange effect that the SR recycling work differently for perturbations created in the CITF and perturbations created in the arms.

Today between 8:00 UTC and 9:00 UTC we have done two tests to investigate the issue of the OMC slow shutter with a broken stop.

Stop and start the driver. This did not resolve the issue, the shutter when opening still runs without stopping when arriving to the end. We have stopped it manually after 1 minute.

Replace the driver with a spare, serial number FT4ZNKQD. The configuration of the rotation process was updated with the new serial number. The issue remained the same. The translation stage of the shutter still doesn't stop when closing.

All these actions were performed with DET_MAIN in pause and the interferometer in single bounce.

In conclusion the driver is not the issue, and probably the in-vacuum translation stage has one of the two stops that is broken.

This is very interesting. My interpretation of to these results is:

• The work on improving the EIB control has been effective. The scattered light glitches that its motion produces during bad weather is at frequencies below 20Hz, and maybe even 15Hz, which will be more difficult to improve on.
• The main source of scattered light glitches 30Hz-50Hz during bad weather comes from the west end building. The WE suspension local control signal Sa_WE_F0_X_500Hz, may mean the suspension is moving, or that the ground around the suspension is moving. A more detailed analysis of all the position sensors in the WE building is needed to determine what is the source of scattered light in the WE building, but it is unlikely to be the mirror itself.

This afternoon we performed a few tests on the OMC shutter with the ITF in NI single bounce in order to find a solution to the problem of OMC shutter getting stuck at the opening.

Fig.1 shows a test when sent a MOVETOLIMIT command via VPM to open the shutter. In this case the shutter motor get stuck, and we stopped it by sending the STOP MOTION command.

We have tested the opening of the shutter by sending some MOVEREL commands with a defined number of steps. We have found that with about 36000 steps the power on B1s reaches a plateau. Adding a bit of margin, we decided to perform 42000 steps to open the shutter. This is tested on Fig.2. We can see that it takes about 65 seconds to accomplish this motion.

We have then replaced the MOVETOLIMIT command by the MOVEREL command for the opening of the shutter in the class SHUTTER_OPENING of DET_MAIN. In the DET_MAIN.ini file, we have added the parameter nominal_open_steps = 42000, and we have updated the opening_duration to 80 seconds.

The opening and then closing of the shutter are tested with the automation on Fig.3. The closing is still performed with the MOVETOLIMIT command in order to be sure that we always start opening the shutter from the same position.

It was then possible to relock the ITF in Low Noise 3 at first trial.

Figure 1. Another channel that sees the noise is SDB1_B5_QD1_H (and all the other channels of the quadrants on SDB1). It sees the noise start when the slow shutter on SDB1 starts opening 15:59:16, then the noise level is constant, and the it stops. On B1 PD3 the noise level stops when it stops on B5 QD1, and it is present only when there is light on B1 PD3, so that is the reason why the level of noise on B1 PD3 varies in time during these 5 minutes.

This is most likely due to the slow shutter of the OMC which is mounted on an Agilis translation stage with electronic end of range stops. The stops are failing and the piezo-motor of the shutter keeps trying to push it further even though the translation stage arrived at the end of its range.

Figure 2. Shows that the OMC thermistor sees a line at ~1721 Hz when the slow shutter is in motion. This is likely the electrical cross-coupling of the voltage sent to the slow shutter showing up on the voltage readout used for the temperature measurement.  In blue is when the shutter moves and in purple when the shutter doesn't move. Unfortunately dataDisplay can't seem to handle the dynamic, and making an FFTtime plot of this channel doesn't seem to work.

FIgure 3. When the shutter is closing after an unlock there is also a 1721Hz line preens in OMC1 T1, but it is 10 times smaller.

Figure 4. OMC T1 also sees the 1721Hz when opening the OMC shutter in single bounce. The line stays on for about 30 minutes, before stopping by itself. The shutter is closed 20 minutes after the line stops by itself according to the shutter log file.

Action items to debug this further and mitigate it:

• To open the OMC slow shutter use a given number of step instead of moving the shutter to the limit. The needed number of steps to open the shutter need to be tested, for example in single bounce after the next unlock.
• Keep using the move to limit command for closing the shutter, so the shutter always goes back to the same position after a round trip.
• Test the operation of the OMC slow shutter in single bounce. The problem can be seen on OMC1 T1 when opening the shuter. Turn on/off the driver of the slow shutter and see if that restores the functioning of the translation stage stops.
• Investigate in past data if the shutter has started to slow down, if it takes more seconds between when the shutter command is sent and when the light appears on B1s.
• Check if the height of 1721Hz line is constant on OMC1 T1 when the shutter is opened, or if it changes in height after a fews tens of seconds when the translation stage arrives at the stop.
• Investigate in past data if the height of the 1721Hz line when the shutter is being opened has increased over the past months.

Are the transients corresponding to time that where outside of science mode during the same hour due to adjustments? See figure 1.

These should be nice scattered light injections from moving SWEB https://logbook.virgo-gw.eu/virgo/?r=63997. It would be nice if someone could confirm it by looking at the same spectrogram for DET_B8_DC, and also see if the frequency corresponds to the speed of the bench in the Z direction (along the beam).

We investigated the issues concerning DET_MAIN, which were reported in : https://logbook.virgo-gw.eu/virgo/?r=63964

During the night from April 14 to 15, DET_MAIN went to the UNKNOWN state after an ITF unlock. This happened two times, but the two events were actually uncorrelated.

The first time, at 22h57 utc, DET_MAIN went to the UNKNOWN state because of a failure of the injection system. As shown on Fig.1, the injected power (INJ_IMC_TRA_DC) falls to 0, while DET_MAIN was in the state SHUTTER_CHECK_OPEN checking for the shutter to be opened. Since there is no power due to the failure of the injection system, DET_MAIN is not able to recognize that the shutter is open and therefore goes to the UNKNOWN state. In this situation, putting the ITF in NI single bounce, and then requesting the DET_MAIN state "FORCE_CHECK_OPEN" would normally allow to unblock DET_MAIN (then the standard state SHUTTER CLOSED can be retored).

The second time, at 00h14 utc, the shutter has been closed, but the check that the shutter is actually closed (in the state SHUTTER_CHECK_CLOSED) fails (Fig.2 and Fig.3). This is almost certainly due to the fact that around 00h14m17 the power on B1p_PD2_DC is close to zero due to interference fringes. Therefore, as there is not enough power on the dark fringe beam, DET_MAIN is not enabled to confirm that the OMC shutter is open. In this situation, requesting with DET_MAIN the state "FORCE_CHECK_CLOSED" would probably allow to recover the standard state "SHUTTER CLOSED".

Figure 1. As reported by others at the daily meeting, there are new loud glitches in h(t) since the lock of this morning at ~4 UTC

Figure 2. These glitches are visible in the BNS range as drops that last 1-2 minutes, both in Hrec and Hrec raw (so it is not a noise subtraction filter in Hrec having issues). They don't seem to be due to PR F0 glitches nor to B1 photodiode saturations.

It would be good to know from detchar how much of a problem these glitches are for data analysis. And if any correlation with other sensors can be found.

The DIFFp set point loop that minimizes the DIFFp dither lines in B1p DC might not give the right set point to maximize the DARM optical gain and the BNS range.

Figure 1 shows that the BNS range was decreasing by 5 Mpc yesterday for most of the day between 6:00 UTC and 19:00 UTC (afterwards there is a drop for 3h because of the calibration noise injections).

Figure 2 shows that at the same the optical gain has been decreasing, and started increasing again between 21:00 UTC and 24:00 UTC.

One can do a double demodulation of B1 at the 491.3Hz DARM line frequency and then demodulate the line magnitude at the DIFFp dither line frequency.

Figure 3 shows that at 6:00 UTC that demodulation was relatively close to zero for TX and TY, but at 16:00 UTC DIFFp TX was very far from zero. Which means that changing the DIFFp TX set point should be able to increase the DARM optical gain (and probably the BNS range)

Figure 4 shows that around 24:00 UTC when the BNS range was getting better the measured double demodulation signal was getting closer to zero.

Figure 5 shows than on April 10 when the DIFFp TX was not working and there was a forest of bumps appearing in the sensitivity the signal was even further away from zero.

So a double demodulation of B1 at 491.3Hz + DIFFp dither line frequency might be giving a good signal for the DIFFp set point to increase the DARM optical gain and the BNS range.

/users/mwas/ISC/B1_doubleDemod_DIFFp_20240331/B1_doubledemod.m

There are noise projections and measurements done proving in a model dependent way that the CO2 DAS laser is not limiting the sensitivity (VIR-0911A-19, VIR-0199A-24).

Another proof that is model independent comes from the tuning of the TCS done in October last year starting from the TCS switched off: https://logbook.virgo-gw.eu/virgo/?r=62282 . Only the NI CO2 is a potential source of noise, as this is the one with a high power put on the CP to compensate the cold lens on the CP. The lock acquisition was done with 0.1W on the NI CP, and then two steps were performed in lock to increase the power to 0.4W.

Figure 1 shows the two steps done at 18:23 UTC and 20:28 UTC.

Figure 2 shows that there was no impact on the BNS range. If the CO2 laser was a noise source the impact on the sensitivity would be immediate and the noise level would be proportional to the CO2 laser power.

The noise fitting done a few days after that measurement had shown that the sensitivity was limited by the mystery noise at that time https://logbook.virgo-gw.eu/virgo/?r=62301. See figure 3. So if the CO2 laser was the origin of mystery noise (through RIN coupling, jitter coupling, or any other way). Then we should have seen increase in steps of the noise level in the sensitivity, which was not the case.

Looking at Bruco results from yesterday I have noticed broadband correlations that I don't remember seeing last time I looked a few weeks ago.

Figure 1. NEB IPS CURR is coherent between 20Hz and 60Hz. Did the NEB IPS CURR noise level increase in the past few weeks?

Figure 2 WI FF50Hz P ERR is coherent between 15Hz and 100Hz. I am surprised to see coherence with the 50Hz feed-forward very far from the 50Hz frequency.

It would be important to look at this in more detail. A more complete list of which channels become coherent with h(t), when did it become coherent, and if the corresponding environmental channels increase in noise level at the same time.