Reports 1-1 of 1 Clear search Modify search
Detector Operation (Operations Report)
magazzu - 23:01 Sunday 17 February 2019 (44901) Print this report
Operator Report - Afternoon Shift 17 Febrary 2019

ITF found locked and stable at around 50 Mpc. At 15:25 UTC there were a first Fast unlock, I was able to reach LOW_NOISE_3 again at 16:05 UTC but from 16:50 UTC to 17:35 UTC there was a Fast Unlock Crisis. I waited in DOWN state until the end of the instability, ITF locked again at 17:58 UTC.
The last lock seems mostly stable at 50 Mpc, but from 20:00 UTC the Horizon went down to 37 Mpc. F. Sorrentino briefly verified the phase of the Squeezing Photodiode ( switched to Commissioning Mode from 20:12 UTC to 20:23 UTC ) but that wasn't the cause of the issue. The Horizon returned to its standard value at 20:30 UTC ( see attached plot ).
ITF left Locked in AUTORELOCK_FAILSAFE.

VPM
After a series of lock attempts DET_MAIN resulted stuck at 17:10 UTC. I manually restarted it from VPM and then it was possible to lock again.

TCS
From 15:15 UTC to 15:26 UTC I. Nardecchia went to Laser Lab Atrium to switch off the HWS Sled.

Guard Tour (UTC )
14:33 - 15:15;
16:29 - 17:05;
18:31 - 19:00;
21:14 - 21:48.

Images attached to this report
Comments to this report:
mwas - 8:22 Monday 18 February 2019 (44902) Print this report
DET_MAIN went into the stuck UNSAFE_B1p state as designed, because the fast unlock crisis interrupted the closing of the slow shutter more than 5 times (the laser beam is used to check the state of the slow shutter closure).
After waiting or solving the fast unlock crisis, a way to reset the safety is indeed to restart the metatron node.
A less brutal option, is to press the "LOAD" button in the DET_MAIN metamedm window, as mentioned in the user message:
"Too many failed metatron logic loops. Reload metatron to reset".
ilaria - 12:43 Monday 18 February 2019 (44908) Print this report
When I went in INJ, the ITF unlocked during the switching off of the HWS-INJ SLED.
swinkels - 18:50 Monday 18 February 2019 (44914) Print this report
I did a brute-force correlation of the half-hour long drop in the range with all channels in trend.ffl. Other than some expected correlation with some DARM BRMS and Hrec related channels, I could not find any smoking gun.
mwas - 9:34 Tuesday 19 February 2019 (44921) Print this report
I have run the noise budget at the time of the range drop.
Figure 1 shows it is an issue with one of the calibration injections
Figure 2 shows it is the WE photon calibrator.
The calibration team will look into why it happened, the pcal was running for the whole weekend, but something strange must have happened during these 30 minutes.

Images attached to this comment
curylo - 16:52 Thursday 21 February 2019 (44957) Print this report
Just before the first fast unlock there was a relativly broadband glitch (around 0Hz to 30Hz) around 15.00pm - 15.09pm seen in DARM and Hrec, highest SNR>616. BNS range drop of about 2/3 Mpc.
There might be a correlation with environmental condition: seismic activity seems to be increased at that time (added a plot from VIM and spectrogram)
Images attached to this comment
direnzo - 19:24 Friday 22 February 2019 (44978) Print this report

(A little late) I've run a brute force cross-correlation analysis with NonNA of the sensitivity drop in BNS Range. As reported by Michal, many sensor of the West End Building Photon CALibrator (PCAL_WEB_PSD*) have had a similar behaviour.

In Figure 1 they are shown in red the twelve most correlated channels with Hrec_Range_BNS (blu line). Dashed lines represent anti-correlations (signals are flipped vertically).

In Figure 2 and Figure 3 the same analysis has been repeated for LSC_DARM blrms in the two bands [65,85]  and [95,145] Hz.  The witness channels are similar (besides correlations have become anti-correlations).

Images attached to this comment
Search Help
×

Warning

×