Reports of 44233
Detector Characterisation (Data monitoring)
fiori - 23:43 Wednesday 08 April 2020 (48914) Print this report
O3 acoustic transfer functions

Attached here are the data files of acoustic transfer functions computed during O3. The computation follows LIGO document  LIGO-G1800121-v1 by P.Nguyen and R.Schofield. Also attached is one matlab script that demonstrates the reading of TF files and the projection computation for one assigned gps.

The full set of data is stored in /data/procdata/detchar/env/injections/acoustic/results/O3/.

Images attached to this report
Non-image files attached to this report
Environmental Monitoring (Environmental Monitoring)
fiori - 18:12 Wednesday 08 April 2020 (48913) Print this report
Comment to Acoustic noise projections in CEB hall and DET Lab (48905)

The acoustic noise coupling and projections reported in this entry are wrong, because of a bug in the software (my fault). They will be reposted shortly.

AdV-DAQ (Data collection)
masserot, chuimmo - 10:07 Wednesday 08 April 2020 (48911) Print this report
Comment to DAQ flux reduction (48896)

In order to reduce the data flow stored in the RAW_FULL stream and in the RAW stream, the following processes were stopped and made as optional in the VPM configuration file:

2020-04-08-04h39m19-UTC    info masserot     process:EnvDemod stopped

2020-04-08-04h46m15-UTC    info masserot     process:EOM_Demod stopped
2020-04-08-04h46m43-UTC    info masserot     process:LNFS_Moni stopped

2020-04-08-07h45m57-UTC    info masserot     process:ISYS_moni stopped
2020-04-08-07h46m00-UTC    info masserot     process:ISYSnoise stopped
2020-04-08-07h46m03-UTC    info masserot     process:ISYS_slow_pre stopped
2020-04-08-07h46m07-UTC    info masserot     process:ISYS_slow stopped
2020-04-08-07h46m15-UTC    info masserot     process:ISYS_Acl stopped


The RAW data fow is now 15MB/s and the RAW_FULL  at 41MB/s

Infrastructures (Air Conditioning)
soldani - 22:46 Tuesday 07 April 2020 (48910) Print this report
Comment to boiler maintenance (48907)
please, read "acting" instead of "aging"....
sorry!
AdV-DAQ (Data collection)
masserot - 22:13 Tuesday 07 April 2020 (48908) Print this report
Online latency

FbmAlp level

As all the Automation servers and the Reconstruction servers  are stopped, it remains only few servers providing data the Frame merger FbmAlp:

  • 3 Slow frame builders: FbsDet, FbsAlp and FbsVac
  • 2 python servers: PyDAQ and PyHVAC
  • and FbmMain

This plot show the FbmMain latency and  the ones of its frame providers where we can see that it latency is mainly due to the FbsDet one and sometime to the PyDAQ one.

PyDAQ

The PyDAQ compute the latency of the different data streams (RAW, RAW_FULL,RDS, TREND, RAW_BACK). It use the DAQ only as trigger to perform the stream latency computation and to make the result available in the DAQ. To reduce it latency, it can be connected to an upstream server:

  • FbmFE  from 2020-04-07-14h20 to 2020-04-07-15h05
  • FbsMoni since 2020-04-07-15h05 . The FbsMoni configuration has been modified to provide an frame stream ouput in the /dev/shm/VirgoOnline directory.

The improvement for PyDAQ latency can be seem in this plot

FbsDet

This plot show the relationship between the FbsDet latency and the FbmAlp one . Thanks  to the monitoring performed by the Fbs server, the culprits were easily identified: the SDB power monitoring servers , the SIB2, SDB2 and SNEB ones.

Using the advance request facility for these servers it was possible to reduce the FbsDet latency by 1s and to have FbmAlp latency independent of the FbsDet one . The operation was done around 2020-04-06-21h00UTC (see this plot )

During these operation the RdsFbm_20 server crashed and was not restarted quickly as consequence 1020s of data are missing in the RDS stream

2020-04-06-21h11m25-UTC>WARNING-FdIOGetFrame: miss 1020 seconds between 1270241640.0 and 1270242660.0

FbmMain level

This plot show the latency of its different frame providers, mainly the 50Hz processing servers,  where one can see that the FbmMain latency is due to  50Hz processing of the Injection channels (INJ_50Hz server).

It appears that for the  INJ_50Hz server  there is a lot of channels sampled at high frequency, Fs>100kHz  which are ended with the "_FS" suffix  .

Removing the channels stored only in the RAW_FULL stream from the online 50Hz computation allows to reduce by 0.2s the latency at  the FbmMain level.

This operation was done the 2020-04-07-08h50UTC.(plot)

DAQ status

This plot show

  • the online latency close to 2s at FbmAlp level without Automation servers running
  • the online data flow, around 63MB/s
  • and
    • the RAW_FULL stream flow at 42MB/s  or not  83MB/s as reported in the logbook 48896
    • the RAW stream flow at 18MB/s

As consequence for the online disk buffers

  • raw_back 36TB , so 24days with an input data flow of 18MB/s
  • raw_full 50TB, so 14days with an input data flow of 42MB/s

Conclusions

For the processing servers before the Automation level, if they don't use the 50Hz channels, it s better if they take their data for FbmFE  or for an upstream server with a  /dev/shm facility..

Maybe all the PyALP servers in the Automation VPM subsystem could use at least FbmFE instead of FbmMain .

The 2020-04-07-12h04UTC the PyHVAC server was restarted with as Frame input the FbsMoni /dev/shm .

Images attached to this report
Detector Operation (Operations Report)
ciardelm - 15:27 Tuesday 07 April 2020 (48909) Print this report
Comment to TCS CO2 laser cooling chillers check (with water refilling to both chillers) (48876)
The CO2 laser cooling chillers have been checked this morning (around 10:00 UTC).
No need of refill.
Infrastructures (Air Conditioning)
soldani - 12:33 Tuesday 07 April 2020 (48907) Print this report
boiler maintenance
this morning a maintenance intervention for boilers (TEB+WEB+NEB+ 1500West) has been performed, trying to minimize the effects aging on buildings eurotherms;
here the time of shut down, in Local Time:
Caldaia TEB off dalle 9,15 alle 10,15
Caldaia NEB off dalle 10,10 alle 11,00
Caldaia WEB off dalle 10,30 alle 11,05
Caldaia 1500W off dalle 11,15 alle 12,00

davide
Comments to this report:
soldani - 22:46 Tuesday 07 April 2020 (48910) Print this report
please, read "acting" instead of "aging"....
sorry!
AdV-EGO (Contamination Control)
carbognani - 17:48 Monday 06 April 2020 (48906) Print this report
Checks on Particle Counters network

Today, during the periodic checks tour I have verified the INJ Particle Counter which was always giving zero counting. After some verifications I have swapped the CEB counter (partcount5) with the INJ one (partcount3) and the situation will be kept monitored.

I also reset the Particle Counter at WEB (partcount7) since it was providing a flat reading in the last weeks. Data seems fine after the reset (See Fig. 1)

Images attached to this report
Environmental Monitoring (Environmental Monitoring)
fiori, tringali, paoletti, menendez - 23:15 Sunday 05 April 2020 (48905) Print this report
Acoustic noise projections in CEB hall and DET Lab

Here attahed are acoustic noise transfer functions and projections computed with the injections performed on March 26 and  on March 28:

  • Figure 1 and first attached file: noise projection and TF in CEB hall with SQZ engaged
  • Figure 2 and second attached file: noise projection and TFin CEB hall with SQZ shutter closed
  • Figure 3 and 3rd attached file: noise projection and TF in Detection LAB with SQZ engaged
  • Figure 4 and 4th attached file: noise projection and TF in Detection LAB with SQZ shutter closed

The difference with standard LN3+SQZ condition and that with SQZ shutter closed is a bit reduced projection and TF around 50Hz and 160Hz

Also attached is the matlab file to read the TF file and plot the data.

Images attached to this report
Non-image files attached to this report
Comments to this report:
fiori - 18:12 Wednesday 08 April 2020 (48913) Print this report

The acoustic noise coupling and projections reported in this entry are wrong, because of a bug in the software (my fault). They will be reposted shortly.

Electronics and Software (Configuration change)
verkindt - 17:42 Saturday 04 April 2020 (48904) Print this report
restart of Moni processes

Today, around 15:35 UTC, I have restarted all the Moni processes with a new version of Moni package which allows the Moni flags to be computed as if META_ITF_LOCK_index=1, when the channel META_ITF_LOCK_index is missing. In the previous Moni version, all the flags itfState-dependent were grey when META_ITF_LOCK_index was missing.

AdV-DET (Commissioning)
mwas, gouaty - 10:27 Saturday 04 April 2020 (48903) Print this report
Comment to Removing offset in SNEB_LC_COIL_BL_V (48899)

Later on March 29 2018 an intervention to fix the SNEB doors was finished. Around thes days the correction on BL_V jumped from -4V to -8V, see figure 1.

This correspond to a rebalancing of the bench on March 27 and March 29 (see log file below). The balancing was probably done by looking at the control loop correction signals, instead of the signals actually send in the coils. Which means that the balancing put the signal sent into the BL_V coil roughly at the offset constant left by mistake a year before. The right course of action is to keep the BL_V offset at zero, and once the beam in the north arm is found again, redo the bench balancing using the motorized counterweight (which should bring it back to the middle of the range).

SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h53m52-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 100 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h54m08-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 400 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h54m32-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 2000 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h54m49-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 2500 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h55m24-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h56m42-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h56m59-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h57m18-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h58m27-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps forward
SNEB_Pico_2018-03-29-07h16m29-UTC.log:PMC_MOTOR SNEB_NS    7 1
SNEB_Pico_2018-03-29-07h16m29-UTC.log:2018-03-29-07h17m11-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps backward
SNEB_Pico_2018-03-29-07h16m29-UTC.log:2018-03-29-07h18m18-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps backward
SNEB_Pico_2018-03-29-07h16m29-UTC.log:2018-03-29-07h18m29-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps backward

 

Images attached to this comment
Detector Operation (Operations Report)
dattilo - 17:59 Friday 03 April 2020 (48902) Print this report
Comment to TCS CO2 laser cooling chillers check (with water refilling to both chillers) (48876)
The CO2 laser cooling chillers have been checked this afternoon (around 15:40 UTC).
No need of refill.
AdV-DET (Commissioning)
mwas - 17:46 Friday 03 April 2020 (48901) Print this report
Comment to Removing offset in SNEB_LC_COIL_BL_V (48899)

This offset has been added in May 2017, see figure 1. It seems to have happened during work on comparing SNEB to SWEB that was done on May 9, see figure 2. The trend data for May 9 are missing, so we only have the information for the day before and after.

Looking at figure 1, the correction signal changed for BL_V and FR_V by about 4V. These are coils at opposite end of the bench, and checking the configuration they have the same sign of actuation. So this change in correction correspond to an offset on BL_V being compensated by the same force applied on FR_V to have a zero angular force, but some force pushing the bench up or down (I am not sure of the sign).

I expect this is an offset left on by mistake after testing the sign of the actuation for the 4 vertical coils, and it is better to keep the offset at 0 (and if confirmed use the balancing mass on SNEB to keep the correction closer to zero too).

I have checked the other suspended benches. And the only remaing non zero offsets are for SDB1, they are 4 equal horizontal offsets, which correspond to a TY force. Presumably this is a torsion on the three supension wires to keep the bench roughly aligned with the beam even when the controls are off. Presumably it would be better to move that feedback offset up the suspension chain, and have it applied on the marionette coils, especially because the marionette is suspneded only from 1 wire and from 3 wires like the bench.

Images attached to this comment
AdV-DET (Commissioning)
gouaty - 16:14 Friday 03 April 2020 (48899) Print this report
Removing offset in SNEB_LC_COIL_BL_V

Today we noticed that there was an offset of 8V left on the coil SNEB_LC_COIL_BL_V. It has been removed at 12h54 utc for the standalone state. We will put it back when normal operations are restored.

Images attached to this report
Comments to this report:
mwas - 17:46 Friday 03 April 2020 (48901) Print this report

This offset has been added in May 2017, see figure 1. It seems to have happened during work on comparing SNEB to SWEB that was done on May 9, see figure 2. The trend data for May 9 are missing, so we only have the information for the day before and after.

Looking at figure 1, the correction signal changed for BL_V and FR_V by about 4V. These are coils at opposite end of the bench, and checking the configuration they have the same sign of actuation. So this change in correction correspond to an offset on BL_V being compensated by the same force applied on FR_V to have a zero angular force, but some force pushing the bench up or down (I am not sure of the sign).

I expect this is an offset left on by mistake after testing the sign of the actuation for the 4 vertical coils, and it is better to keep the offset at 0 (and if confirmed use the balancing mass on SNEB to keep the correction closer to zero too).

I have checked the other suspended benches. And the only remaing non zero offsets are for SDB1, they are 4 equal horizontal offsets, which correspond to a TY force. Presumably this is a torsion on the three supension wires to keep the bench roughly aligned with the beam even when the controls are off. Presumably it would be better to move that feedback offset up the suspension chain, and have it applied on the marionette coils, especially because the marionette is suspneded only from 1 wire and from 3 wires like the bench.

Images attached to this comment
mwas, gouaty - 10:27 Saturday 04 April 2020 (48903) Print this report

Later on March 29 2018 an intervention to fix the SNEB doors was finished. Around thes days the correction on BL_V jumped from -4V to -8V, see figure 1.

This correspond to a rebalancing of the bench on March 27 and March 29 (see log file below). The balancing was probably done by looking at the control loop correction signals, instead of the signals actually send in the coils. Which means that the balancing put the signal sent into the BL_V coil roughly at the offset constant left by mistake a year before. The right course of action is to keep the BL_V offset at zero, and once the beam in the north arm is found again, redo the bench balancing using the motorized counterweight (which should bring it back to the middle of the range).

SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h53m52-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 100 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h54m08-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 400 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h54m32-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 2000 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h54m49-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 2500 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h55m24-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h56m42-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h56m59-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h57m18-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps forward
SNEB_Pico_2018-03-27-14h52m35-UTC.log:2018-03-27-14h58m27-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps forward
SNEB_Pico_2018-03-29-07h16m29-UTC.log:PMC_MOTOR SNEB_NS    7 1
SNEB_Pico_2018-03-29-07h16m29-UTC.log:2018-03-29-07h17m11-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps backward
SNEB_Pico_2018-03-29-07h16m29-UTC.log:2018-03-29-07h18m18-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps backward
SNEB_Pico_2018-03-29-07h16m29-UTC.log:2018-03-29-07h18m29-UTC>INFO...-PicoControl> Motor 'SNEB_NS' moved 10000 steps backward

 

Images attached to this comment
Electronics and Software (Configuration change)
verkindt - 13:15 Friday 03 April 2020 (48898) Print this report
MdVim and MdDQ reconfigured

To reduce the number of useless or empty plots in the VIM pages, I have reconfigured and restarted the processes MdVim and MdDQ.
Let me know if you observe in VIM pages some plots that are not updated anymore but that you still need for monitoring during this shutdown period.

AdV-DAQ (Data collection)
masserot - 10:51 Friday 03 April 2020 (48897) Print this report
EDB_B1s1_PD1_{DC,Audio}_raw renamed with _FS suffix

These channels are acquired at 100kHz  and with the renaming they are now stored in the RAW_FULL stream

  • 2020-04-03 07h34m53 UTC    SDB_EDB_dbox_rack saved - masserot: add the suffix _FS on the channels EDB_B1s1_PD1_{Audio,DC}_raw acquired at 100KHz (rev. 92665)
  • 2020-04-03 07h35m09 UTC    Reconfigure EDB_MezzPD in SDB_EDB_dbox_rack
AdV-DAQ (Data collection)
masserot - 12:12 Thursday 02 April 2020 (48896) Print this report
DAQ flux reduction

In order to reduce the data flow stored in the RAW_FULL stream and in the RAW stream, the following processes were stopped and made as optional in the VPM configuration file:

2020-04-02-09h22m11-UTC    info masserot     process:SWEB_PSD_sensing stopped
2020-04-02-09h22m20-UTC    info masserot     process:SWEB_Quadrants stopped
2020-04-02-09h22m27-UTC    info masserot     process:SWEB_Photodiodes stopped
2020-04-02-09h24m34-UTC    info masserot     process:SNEB_PSD_sensing stopped
2020-04-02-09h24m36-UTC    info masserot     process:SNEB_Quadrants stopped
2020-04-02-09h24m37-UTC    info masserot     process:SNEB_Photodiodes stopped
2020-04-02-09h26m14-UTC    info masserot     process:SDB2_Readout stopped
2020-04-02-09h26m25-UTC    info masserot     process:SDB2_Quadrants stopped
2020-04-02-09h26m28-UTC    info masserot     process:SDB2_Photodiodes stopped
2020-04-02-09h31m12-UTC    info masserot     process:SPRB_Photodiodes stopped
2020-04-02-09h31m16-UTC    info masserot     process:SPRB_Quadrants stopped
2020-04-02-09h31m30-UTC    info masserot     process:SDB2_spy stopped
2020-04-02-09h32m52-UTC    info masserot     process:SIB2_Photodiodes stopped
2020-04-02-09h32m53-UTC    info masserot     process:SIB2_Quadrants stopped
2020-04-02-09h35m20-UTC    info masserot     process:SUSP_rd stopped
2020-04-02-09h38m11-UTC    info masserot     process:SQZ_CC_Ctrl stopped
2020-04-02-09h39m38-UTC    info masserot     process:SQZ_CC_noise stopped
2020-04-02-09h57m01-UTC    info masserot     process:HInjector stopped
2020-04-02-09h57m02-UTC    info masserot     process:HRecPD2 stopped
2020-04-02-09h57m03-UTC    info masserot     process:HRecPD1 stopped
2020-04-02-09h57m04-UTC    info masserot     process:HRecClean stopped
2020-04-02-09h57m39-UTC    info masserot     process:FreeMich_Rec_B1pPD2_DC_20kHz stopped
2020-04-02-09h57m39-UTC    info masserot     process:FreeMich_Rec_B1pPD1_DC_20kHz stopped
2020-04-02-09h57m40-UTC    info masserot     process:FreeMich_Rec_B1pPD2_DC stopped
2020-04-02-09h57m41-UTC    info masserot     process:FreeMich_Rec_B1pPD2 stopped
2020-04-02-09h57m42-UTC    info masserot     process:FreeMich_Rec_B1pPD1_DC stopped
2020-04-02-09h59m22-UTC    info masserot     process:HRec stopped

2020-04-02-09h59m23-UTC    info masserot     process:FreeMich_Rec stopped

2020-04-02-10h17m06-UTC    info masserot     process:EPRB_PC stopped
2020-04-02-10h17m07-UTC    info masserot     process:EDB_PC stopped
2020-04-02-10h17m08-UTC    info masserot     process:EIB_PC stopped

 

The RAW_FULL data flow is now arround 83MB/s and the RAW data flow around 18MB/s

Images attached to this report
Comments to this report:
masserot, chuimmo - 10:07 Wednesday 08 April 2020 (48911) Print this report

In order to reduce the data flow stored in the RAW_FULL stream and in the RAW stream, the following processes were stopped and made as optional in the VPM configuration file:

2020-04-08-04h39m19-UTC    info masserot     process:EnvDemod stopped

2020-04-08-04h46m15-UTC    info masserot     process:EOM_Demod stopped
2020-04-08-04h46m43-UTC    info masserot     process:LNFS_Moni stopped

2020-04-08-07h45m57-UTC    info masserot     process:ISYS_moni stopped
2020-04-08-07h46m00-UTC    info masserot     process:ISYSnoise stopped
2020-04-08-07h46m03-UTC    info masserot     process:ISYS_slow_pre stopped
2020-04-08-07h46m07-UTC    info masserot     process:ISYS_slow stopped
2020-04-08-07h46m15-UTC    info masserot     process:ISYS_Acl stopped


The RAW data fow is now 15MB/s and the RAW_FULL  at 41MB/s

AdV-DAQ (Data collection)
verkindt - 11:35 Thursday 02 April 2020 (48895) Print this report
SegOnline, SpectroMoni changes

Following the ITF stop,
On Tuesday 2020-03-31 around 13:00 UTC, I stopped the process SegOnline that sends DQ flags segments to DQSEGDB.
Today around 09:30 UTC, I changed the configuration of SpectroMoni, so that data needed for spectrograms in VIM are stored only for Environment and Suspensions.

Infrastructures (Air Conditioning)
soldani - 9:55 Thursday 02 April 2020 (48894) Print this report
DET Lab rH
01/04/2010, 22.55 (LT): after receiving DMS alarm for low humidity in det lab, I changed the saturation temperature from 16 to 13 degrees; as a second corrective action, if necessary, given that the external humidity is 54%, it could be useful to exploit it by increasing the opening of the external air intake damper.
Room set point also changed from 55 to 65% and maximum humidity limit produced by the steam producer inside the AHU from 70 to 90%.

23.41 (LT): humidity inside DET Lab varies between 40 and 54%; since, although it is true that the external humidity is at favorable values ​​(54%), the external temperature at this moment is 4.5 degrees and there is a risk of putting the post-heating coil under too much stress with the risk of cooling the environment too much, I decide not to increase the flow of external air, currently at 200 mc / h.
However, the steam producer, although receiving a 100%-power by thermoregulator, cannot produce more than 60%.
I will request technical intervention from the maintenance company but a stop of the air handling unit is needed.
Last week we were only able to free up the holes present on this tube without turning off the uta, but a more decisive action aimed at freeing the inside of this tube is now not postponed.

02/04/2020 8,00 (LT):the corrective measures implemented yesterday evening seem to have given the desired results: this morning the ambient humidity rose to around 60% (DMS probe).





Detector Characterisation (Tools)
hemming - 8:48 Thursday 02 April 2020 (48893) Print this report
NoEMi daily run on Condor BQS stopped

The NoEMi SFDB launcher and line-finder tool was stopped following its daily run yesterday morning; the 1st of April.

The O3 dataset was closed following the run on Saturday morning, the 28th of March, and the post-O3 dataset was opened. NoEMi has been run from the date of the suspension until yesterday morning and the results can be found in this new dataset. O3 remains, of course, fully available - along with O2, ER14 and ER13. All are available via the web interface:

https://apps.virgo-gw.eu/noemi/

AdV-DAQ (Data collection)
masserot - 8:42 Thursday 02 April 2020 (48892) Print this report
Stop of some ACL processes

I stopped the following ACL processes to reduce the stored data flow and I marked them as optional in VPM, to stop them from appearing red:

2020-04-02-05h05m16-UTC   process:SSFS_Ctrl stopped
2020-04-02-05h05m17-UTC   process:SSFS_noise stopped
2020-04-02-05h05m18-UTC   process:SSFS_phi stopped

2020-04-02-05h16m14-UTC    process:LSC_Acl_Moni stopped
2020-04-02-05h19m09-UTC    process:LSC_Acl stopped
2020-04-02-05h19m09-UTC    process:ASC_Acl stopped
2020-04-02-05h19m12-UTC    process:CALnoise stopped

The same operation may be done for the SQZ coherent control loop, the PCAL loops

The attached plot show some DAQ monitoring channels since the  2020-03-31

  • first row: online latency
  • second row: online nAdc
  • third row: storage RAW_FULL data flow and storage RAW data flow
Images attached to this report
AdV-TCS (Ring Heater)
rocchi, pasqualetti - 22:27 Wednesday 01 April 2020 (48891) Print this report
Comment to RHs temperature sensors (48889)
Thanks to a quick e-mail interaction with Antonio, the issue is clear: tube valves closed obscure the cryotraps from the TMs view.
Detector Characterisation (Tools)
cieslar - 21:10 Wednesday 01 April 2020 (48890) Print this report
the daily-bruco stopped

I've stopped the dail-bruco scripts. They were run from the vrigorun's crontab on the detchar1 (olserver141) machine. To restart them - uncomment three lines in the crontab.

AdV-TCS (Ring Heater)
rocchi - 19:20 Wednesday 01 April 2020 (48889) Print this report
RHs temperature sensors
While checking the TCS status, RHs in particular, I noticed the strange behavior of the temperatures measured by all the sensors installed on the TM RH shields, as shown in figure. Note that the ITM RHs are both off. It would be interesting to track what piece of electronics (out of the many switched off yesterday) is interfering with the RH termometers.

The two small drops, clearly visible on the NE_RH, are, as usual, due to the unlocks of the ITF, in this case, those happened on March 30th.
Images attached to this report
Comments to this report:
rocchi, pasqualetti - 22:27 Wednesday 01 April 2020 (48891) Print this report
Thanks to a quick e-mail interaction with Antonio, the issue is clear: tube valves closed obscure the cryotraps from the TMs view.
DAQ (DAQ)
swinkels - 16:46 Wednesday 01 April 2020 (48887) Print this report
stop of some PyALP processes
I stopped the following PyALP processes and marked them as optional in VPM, to stop them from appearing red:
2020-04-01-14h21m37-UTC info swinkels process:PyPhaseCamB1p stopped
2020-04-01-14h21m42-UTC info swinkels process:PyPhaseCamB4 stopped
2020-04-01-14h21m53-UTC info swinkels process:PySFP stopped
2020-04-01-14h21m58-UTC info swinkels process:PySpectral stopped
2020-04-01-14h22m06-UTC info swinkels process:PyUGF stopped
2020-04-01-14h22m27-UTC info swinkels process:PyAATuning stopped
2020-04-01-14h22m41-UTC info swinkels process:PySaturationPD stopped
2020-04-01-14h22m48-UTC info swinkels process:PySQZ stopped
These should not be needed with the interferometer switched off. The only PyALP processes left running are PyDAQ (needed for DMS) and PyHVAC (needed for the HVAC loop of the laser lab).
Search Help
×

Warning

×