LOG-IN
Displaying reports 1-25 of 34685.Go to page 1 2 3 4 5 6 7 8 9 10 End
Detector Operation (Operations Report)
Print this report.
berni - 22:59, Monday 24 April 2017 (37357)Get code to link to this report
OPerator report - Afternoon shift 24 Apr
The first part of the shift was dedicated to Calibration.
After that started the planned activity on SPRB; still in progress...


INF
As side effect of the network outage the UpsServer is not able to communicate with the UPS of the TB; experts have been informed.
AdV-COM (AdV commissioning (1st part) )
Print this report.
bersanetti - 17:29, Monday 24 April 2017 (37356)Get code to link to this report
Comment to Low Noise automatic activation (Click here to view original report: 37301)

The adjustment of the UGF lines' amplitudes (DARM, MICH and PRCL as of now) has been added to the LOW_NOISE_1 configuration, with tentative (lower) values saved in the configuration file, to be tested during the next full lock.

AdV-COM (AdV commissioning (1st part) )
Print this report.
mwas - 17:07, Monday 24 April 2017 (37354)Get code to link to this report
Comment to More alpha tuning (Click here to view original report: 37334)
Made a noise budget (and calibration) for the quiet data with MICH (alpha) subtraction. For now the subtraction is modeled not measured so the noise projection doesn't fit well everywhere. The calibrated noise below 100Hz is well reduce compared to 10 days ago, about a factor 10, with the sensitivity limited by PD electronic (dark) noise from 40Hz, and the lowest point a ~1e-20/rtHz.

This correspond to a range of 145 kpc for BNS and 2 Mpc for 30 solar mass BBH. Still a long way to go, but it will soon start to make sense to look at the range!
Images attached to this comment
37354_20170424163804_screenshotfrom20170424161130.png
AdV-DAQ (Calibration)
Print this report.
bersanetti - 17:03, Monday 24 April 2017 (37355)Get code to link to this report
Comment to Permanent calibration lines started (Click here to view original report: 37220)

The amplitude reduction, and possibly more the frequency change of the WE line, successfully lowered the DARM spectrum in such range and removed some low-frequency pattern that were seen in DARM error signal in time domain; as a double check I tried an additional factor 10 reduction of the lines' amplitudes, but the additional effect is negligible, as the RMS is dominated by the UGF line of DARM itself, which we still have to optimize in the LOW_NOISE_1 confguration. In Figure, blue is the new amplitude, red is 10% of the new amplitude.

Images attached to this comment
37355_20170424170250_darmpermlines.png
AdV-COM (automation)
Print this report.
carbognani - 16:21, Monday 24 April 2017 (37353)Get code to link to this report
Comment to ITF_STATUS Troubles (Click here to view original report: 37335)

Checking the PySb code for possible causes of those crashes I spotted the fact that on the SET_OUTPUTS command implementation a burst of 24  single modbus coil setting commands was generated. I have inserted a small delay between the commands (0.2 sec) and I was not able to replicate the crash while commanding the relays from the VPM interface or from ITF_LOCK. The use of the relays in the DOWN and LOW_NOISE_1 states of ITF_LOCK has been provisionally restored.

AdV-DAQ (Calibration)
Print this report.
rolland - 16:08, Monday 24 April 2017 (37352)Get code to link to this report
Comment to Permanent calibration lines started (Click here to view original report: 37220)

Following the sensitivity improvement, I reduced by a factor 10 the permanent calibration lines around 50 Hz, and moved the line 53.8 Hz WE line down to 50.8 Hz, to be further from the PRCL line around 54.1 Hz.

AdV-DAQ (Calibration)
Print this report.
rolland, estevez, germain, verkindt - 15:59, Monday 24 April 2017 (37351)Get code to link to this report
Calibration shift summary

Calibration shift lasted from 13h to ~15h20 LT, with some unlocks  in-between.

We first did injections to measure the input to end mirror actuation ratio in dark fringe with the controls sent to the end mirrors in LN1 mode, and the input mirrors set in HP mode (relay not opened for this measurement): from 13h15 to 13h45 LT.

Then we tried to inject colored noise to measure the TF and sensivity, but the injected noise was not the good one (white noise instead of colored), and the ITF unlocked at 13h58m LT. The succession of commands from injection script to CALnoise must be checked carefully to fix the issue. We have added SMS channels to the {MIR}_colornoise so that we can check which filter is loaded in the script before starting the filter computation.

We did free Michelson measurements from 14h13 to 14h40 LT. At the beginning, the B1p_PD1 photodiode was unexpectedly closed (the automation sends a command to open it, but does not check its effect yet ; this check must be added for more robustness). We opened it manually and restarted the measurement procedure from CALI: from 14h24 to 14h40 LT. Note that DeltaL reconstructed online was using B1p_PD1_DC and B1p_PD1_6MHz ; we saw a few saturation on the B1p_PD1_Audio channel, but not much, hence it must be useful to recompute DeltaL offline with the Blended channel.

The ITF has then been relocked in dark fringe LN1, we put back NI in HP mode and did some colored noise injections on NI playing with CALnoise directly. We had some coherence from the noise to DARM in the range 10 Hz 100 Hz, but then unlocked at 15h24 LT.

Detector Operation (Operations Report)
Print this report.
menzione - 15:47, Monday 24 April 2017 (37349)Get code to link to this report
Operator Report - Morning Shift 24/04

Upon arrival I found ITF unlocked with the problem on network outage still not solved.
Under request of Carbognani, at 10:20 LT  I went in NE and WE to unplug and plug the switch box crate connecions.
During the scheduled maintenance Commissioners, Carbognani and Boschi (called and went on site) solved the problem at ~10:45 LT.

See dedicated entries:
37340, 37341, 37343, 37344, 37346, 37347.

 

FmodErr performed at 10:45 LT.
Once recovered the standard state ITF has been realigned and easily relocked in Low Noise configuration in order to allow the planned activity on Calibration which started at ~13:00 LT and concluded at ~15:00 LT
.

 

As foreseen, DET/SBE: SPRB under Vacuum setup activity is now in progress.

SAT
10:40 LT SatServer restarted.

 

 

VPM - Suspension
10:44 LT CoilsSbNE restarted after a crash.

AdV-PSL (Commissioning of SS)
Print this report.
Coulon, Genin, Pillant, Cleva - 15:37, Monday 24 April 2017 (37350)Get code to link to this report
Pstab check
on Thursday April the 6th, we have worked on the characterization of the power stabilization loop as planned.
The goal of the shift was to:
1. check with the SR780 spectrum analyser the ultimate performances of the Pstab loop
2. swap the set of Phd1&2 (named PD1) with Phd 3&4 (named PD2) of the Pstab optics box to check that both configurations are equivalent in term of performances and therefore demonstrate that each Phd set could act as the spare of each other.
3. check that both pstab electronics are working (test the spare rampeauto crate).

# First plot shows the RIN @ inloop (PD2), OutOfLoop (PD1)
- The green curve is the RIN of the free-running laser.
- The blue one is the RIN at the in-loop photodiode group (PD2 in this case).
- The red curve the RIN at the out-of loop photodiode group (PD1).
- The black curve is the expected shot noise at the OoL Phd for V_PD2 = 0.8567 Volt <-> 17 mA (1); which is the contribution pf both in and OoL Phds.
 We are thus within the specs define in the AdV TDR for wrt the PR ITF@25W (10^-8/sqrt(Hz)).
- The magenta curve is the RIN at the in-loop photodiode group (PD2 in this case) using the spare rampauto. Both rampeautos gains and offsets have been tuned so that swap is easy and in theory nothing should be retuned before reaching the best performances.

# Second plot shows the RIN @ inloop (PD1), OutOfLoop (PD2): we swap PD1 and PD2 wrt previous plot

(1 ) Note that the so-called "Photodiodes" PD1 and PD2 are a combination of two pairs of photodiodes. PD1 and PD2 are equivalent and can be used as in-loop or out-of-loop sensor
Each pair of photodiodes has its own transimpedance amplifier. The output of both amplifiers are sent in a 2-resistor network, providing the average of their outputs at the common point.
- The contribution of each single photodiode is then multiplied by 0.5.
-> The overall dark/shot noise is the quadratic sum of both individual contribution multiplied by 0.5.
-> The overall photocurrent is the linear sum of both individual contribution multiplied by 0.5.

One must use “2*V_PD2/50” as the contribution to the photocurrent when assessing the shot noise contribution at one photodiode PD1 or PD2 (50 states for the 50 ohms load of the photodiodes preamplifier).
That is RIN_shot = sqrt(2.e. 2*V_PD2/50)/[ 2*V_PD2/50] = 3,05 e-9 /sqrt(Hz).
Please note that the overall noise at the OoL is the quadratic sum of the shot contribution @PD1 and PD2, that is 4,32 e-9 /sqrt(Hz).

In the end, we left the ramstabp rampeauto installed. The spare unit is currently stored in the EEroom.
Images attached to this report
37350_20170424153648_170406pd2inlooprampautoter.png 37350_20170424153702_170406pd1inloop.png
AdV-COM (AdV commissioning (1st part) )
Print this report.
fiori - 12:47, Monday 24 April 2017 (37348)Get code to link to this report
Comment to DARM 16.8 17Hz lines coherence (Click here to view original report: 37287)

This morning I searched for the sources of these lines.  The two fans serving clean air flux to the SPRB minitower area seems the source. It is advisable to perform a switch off  once SPRB is in vacuum. Other tests done with CEB clean Rooms air conditioning, and with Antonio's fan cooling SR turbo pump.

--------------------------------------

Using the accelerometer of TCS NI bench (the one which showed the highest coherence with DARM) I tracked down the two lines which today are at 16.7Hz and 16.9Hz (Figure 1, top-left).

With Davide we first switched off the CEB Clean Rooms air conditioning between 9:07 and 9:012 LT: this affected Lines at 17.9Hz and 18.5Hz which disappered from many accelerometers (Figures 1 and 2) but not the hunted lines.

Lines which appear to correspond to the searched ones are emitted by the two fans serving clean air flux to the SPRB minitower area. Figure 3: picture.

  • Figure 4: accelerometer ENV_SPRB_LINK_ACC_Z was temporarely attached to the chassis of one of the two fans (the one on the right when looking east), this emits a vibration around 16.7Hz
  • Figure 5: the same accelerometer was temporarely attached to the chassis of the second fan, this emits a vibration around 16.9Hz.

I also checked the fan which is being used to cool down the SR turbo (I used channel ENV_SR_ACC_Z temporarely connecting it  to a meggit accelerometer attached to the fan' base. See picture in Figure 6). It emits vibration lines at 4.5Hz and around 31.Hz plus several harmonics above 50Hz, which however presently do not show evident coherence with accelerometers or microphones: Figure 6.

Images attached to this comment
37348_20170424123715_utacleanroomsswitchofflinesaround18hz.png 37348_20170424123721_utacleanroomsswitchofflinesaround18hzffts.png 37348_20170424123728_20170424114726.jpg 37348_20170424123740_sprbcleanroomfandx.png 37348_20170424123747_sprbcleanroomfansx.png 37348_20170424123759_20170424114742.jpg 37348_20170424123811_srantoniofan.png
AdV-COM (AdV commissioning (1st part) )
Print this report.
Boschi, Trozzo - 11:47, Monday 24 April 2017 (37347)Get code to link to this report
Comment to Recovery after network outage (Click here to view original report: 37340)
The network outage caused some DSP boards of several SAs (MC, PR, IB, NI, BS) to lose their IPs as happened recently (see entry #37246). All affected boards are now up and the associated control loops have been closed and are properly working.
AdV-COM (AdV commissioning (1st part) )
Print this report.
mohan - 11:40, Monday 24 April 2017 (37346)Get code to link to this report
Comment to Recovery after network outage (Click here to view original report: 37340)

Because of the problem reported in #37341 it was also necessary to restart some tango servers in vacuum and injection which were red.

injection:

setenv TANGO_HOST tangoitf:10000; astor & 

"Start sdt2011/DDS1"

vacuum:

setenv TANGO_HOST olserver122:10000;astor &

 "Start LN2Rack/NI" and "Start LN2Rack/WI".

( Note: LN2Rack/NE and LN2Rack/WE which are identical to the 2 servers above did not go red.)

Images attached to this comment
37346_20170424113823_astorvacinj2.png
AdV-COM (AdV commissioning (1st part) )
Print this report.
G. Ballardin and Vacuum team - 11:12, Monday 24 April 2017 (37344)Get code to link to this report
Comment to Recovery after network outage (Click here to view original report: 37340)
Because of the problem reported in #37341 it was necessary to restart the PLC for both INJ and DET small-cryotraps:
neither of the PLCs were accessible via the network. In the meantime I also updated the firmware to read temperatures better.
Now the temperatures of both small-cryotraps are conistent.
AdV-COM (AdV commissioning (1st part) )
Print this report.
G. Ballardin - 11:00, Monday 24 April 2017 (37343)Get code to link to this report
Comment to Recovery after network outage (Click here to view original report: 37340)
Because of the problem reported in #37341 it was necessary to restart some motor servers (TSrvMtr_IB,TSrvMtr_PR,TSrvMtr_SR,TSrvMtr_BS,TSrvMtr_NI,TSrvMtr_WI,TSrvMtr_WE,TSrvMtr_DET)
Now everythings is working correctly.
AdV-COM (AdV commissioning (1st part) )
Print this report.
cortese - 15:42, Sunday 23 April 2017 (37341)Get code to link to this report
Comment to Recovery after network outage (Click here to view original report: 37340)
The network problem affected many hosts on the site access network switches and was caused by the main radius server not working properly because of the filling of its system disk.
By configuration, for the majority of the hosts the network connections already up should not have been dropped, irrespectively of the radius server status. Why this didn't happen is under investigation.
AdV-COM (AdV commissioning (1st part) )
Print this report.
Carbognani, Cortese, Rolland - 14:53, Sunday 23 April 2017 (37340)Get code to link to this report
Recovery after network outage

This morning I received an alarm about TCS Chillers. Checking on the DMS and VPM I could see a flooding of red flags and I came onsite to check the situation.

Once onsite it was clear that the problem was at network level with some of the devices on the Central, NE and WE Buildings not reachable. I could not spot any evident electrical problem as a cause of the network outage.

After consulting with Antonella over the phone, Stefano came onsite and started fixing the problem (see his entry for details). The recovery also implied the reboot of the rtpc servers.

Situation could be almost fully recovered by resetting all devices disconnected from network (such as netcom bridges) and by restarting all processes running on rtpc and the whole DAQ with Loic support.

The communication with Cryo and Tower vacuum devices needed also to be restored (all corresponding Tango DAQ brides are back providing data).

The remaining problems are associated to missing SAT DSP g-names which are blocking the automation. The situation could not be recovered by stopping/restarting all SAT tango processes.

Since I could not find Valerio over the phone I leave the current situation and recovery will be continued tomorrow morning.

Comments related to this report
cortese - 15:42, Sunday 23 April 2017 (37341)
The network problem affected many hosts on the site access network switches and was caused by the main radius server not working properly because of the filling of its system disk.
By configuration, for the majority of the hosts the network connections already up should not have been dropped, irrespectively of the radius server status. Why this didn't happen is under investigation.
G. Ballardin - 11:00, Monday 24 April 2017 (37343)
Because of the problem reported in #37341 it was necessary to restart some motor servers (TSrvMtr_IB,TSrvMtr_PR,TSrvMtr_SR,TSrvMtr_BS,TSrvMtr_NI,TSrvMtr_WI,TSrvMtr_WE,TSrvMtr_DET)
Now everythings is working correctly.
G. Ballardin and Vacuum team - 11:12, Monday 24 April 2017 (37344)
Because of the problem reported in #37341 it was necessary to restart the PLC for both INJ and DET small-cryotraps:
neither of the PLCs were accessible via the network. In the meantime I also updated the firmware to read temperatures better.
Now the temperatures of both small-cryotraps are conistent.
Boschi, Trozzo - 11:47, Monday 24 April 2017 (37347)
The network outage caused some DSP boards of several SAs (MC, PR, IB, NI, BS) to lose their IPs as happened recently (see entry #37246). All affected boards are now up and the associated control loops have been closed and are properly working.
mohan - 11:40, Monday 24 April 2017 (37346)

Because of the problem reported in #37341 it was also necessary to restart some tango servers in vacuum and injection which were red.

injection:

setenv TANGO_HOST tangoitf:10000; astor & 

"Start sdt2011/DDS1"

vacuum:

setenv TANGO_HOST olserver122:10000;astor &

 "Start LN2Rack/NI" and "Start LN2Rack/WI".

( Note: LN2Rack/NE and LN2Rack/WE which are identical to the 2 servers above did not go red.)

Images attached to this comment
37346_20170424113823_astorvacinj2.png
AdV-COM (AdV commissioning (1st part) )
Print this report.
mours - 20:07, Saturday 22 April 2017 (37339)Get code to link to this report
SWEB air boxes leaks search

The SWEB minitower is under vacuum since April 11. The check made during the first hours of vacuum did not indicate any obvious leak (see 37218). We now have 11 days of vacuum, which allows us to get a better estimate of the possible leaks.

The attached figures are showing the trend data for the pressure and temperature of the cameras, photodiode, the second figure is for the quadrants, bench electronic air box and minitower pressure.

Small leaks are observed for some of the boxes:

  • QD1 and QD2: 60 mbar/year
  • PD1: 40 mbar/year

The uncertainty is about 10 mbar/year.

For the cameras, PD2, and bench, there are no observed leaks, with an upper limit of 10 mbar/year.

Like for SNEB, these leaks are small enough to not call for a venting of the minitower before the end of O2.

Images attached to this report
37339_20170422200542_swebpdcam.jpg 37339_20170422200558_swebqdbenchleak.jpg
AdV-COM (AdV commissioning (1st part) )
Print this report.
mours - 20:03, Saturday 22 April 2017 (37338)Get code to link to this report
Update on the SNEB air boxes leaks

The SNEB minitower is under vacuum since august 17, 2016. There was a short venting on November 29 (see the logbook entry 35672) were the camera B2_Cam2 was replaced as well as the B7_PD2 photodiode. This venting was short enough to not let the leaking boxes to refill. We have now a rather long history to check for leaks of the various air boxes.

The attached plots are showing the pressure and temperatures for the photodiodes (first figure), cameras (second figure, the temperature probe of Cam1 is not working and Cam2 was changed on November) quadrants (third figure) and electronic air tank as well as the minitower pressure (last figure)

  • PD1: 9 mbar/year
  • PD2: 16 mbar/year
  • QD1: 30 mbar/year
  • QD2: 67 mbar/year
  • Cam1: 14 mbar/year
  • Cam2: 25 mbar/year
  • Bench electronic air tank: < 2 mbar/year

The uncertainty on those values is one or two mbar.

These values are in good agreement with the ones reported after 26 days of vacuum.

Given these small values, there is no need to fix any of the air boxes before the end of O2.

Images attached to this report
37338_20170422200030_snebpd.jpg 37338_20170422200045_snebcam.jpg 37338_20170422200110_snebqdleak.jpg 37338_20170422200135_snebelecboxleak.jpg
AdV-TCS (Wavefront sensing)
Print this report.
aiello, chiummo, nardecchia, rocchi, sequino - 15:46, Saturday 22 April 2017 (37337)Get code to link to this report
Cross talk SLED-INJ HWS-DET and SLED-DET HWS-INJ
During yesterday shift the cross-talk between the INJ and DET SLEDs has been investigated.
After switching off the DET-SLED, we have measured the power of the INJ-SLED arriving on HWS-DET (order of 4uW wrt an input power of 130uW). We have also measured the power of the beam reflected back from the WI on the proper HWS-INJ equal to 26 uW.
Then we have adopted the same procedure to evaluate the extra-light coming from the DET-SLED on HWS-INJ and we measured approximately 30nW wrt an input power of 1.9 mW. The light power reflected back from the NI on the proper HWS-DET was approximately of 0.1 mW.
These measurements will be used to fine-tune the decoupling strategy between the two SLEDs.
AdV-COM (automation)
Print this report.
bersanetti - 14:09, Saturday 22 April 2017 (37336)Get code to link to this report
Comment to ITF_STATUS Troubles (Click here to view original report: 37335)

I didn't get the chance to verify the behaviour of ITF_STATUS as the CoilsSb* servers keep crashing, and everything was stuck in DOWN; I disabled the use of the relays in ITF_LOCK, and commented also the duplication of the reset of the 6MHz amplitude on the LNFS which was present in the DOWN state of ITF_LOCK.

AdV-COM (AdV commissioning (1st part) )
Print this report.
swinkels, bersanetti, allocca - 01:23, Saturday 22 April 2017 (37334)Get code to link to this report
More alpha tuning
We continued yesterday's work of tuning the MICH noise subtraction. We further improved the filters for shaping the MICH and DARM noise, so that the measurements give good coherence down to 10 Hz, where it is needed. After that, we were able to do the actual noise injections via the injection script prepared by Franco, see /virgoDev/Automation/scripts/LSC/inject_lsc.py. Logfiles with the gps times of the injections are stored in /virgoData/NoiseInjections/LSC.

Using these injections, we could finally do a reasonably good measurement of alpha. Fig 1 shows a comparison between alpha filter on and off while injecting noise on MICH, while fig 2 shows the same in quiet conditions. Fig 3 shows a noise budget with the filter turned on (to be compared with the same plot from yesterday). This plot uses 120 seconds of clean data starting at gps = 1176846162. The noise subtraction is switched on by Metatron at the end of the state LOW_NOISE_1, and is switched off in the DOWN state.

Figure 4 shows that the obtained suppression is about a factor 10 over a broad frequency range. It is likely that the suppression is currently limited by variations in the optical gain. To solve this, we need to servo the gain as in the past.

Some other remarks:
-Especially during the beginning of the shift, the IMC shows a large oscillation after every unlock of the interferometer, which eventually unlocks the IMC, see fig 5. It typically takes about 2 minutes before the system calms down again.

-We thought that we could safely restart the CALnoise to change some filters. Switching the process off causes however some weird glitches which oscillate at 5kHz in some of the suspension signals, see fig 6. This might be a bug in how a missing channel is handled in Acl or in the DSPs.

Images attached to this report
37334_20170422011528_darmnoisesubtr.png 37334_20170422011546_alphaonoffnonoise.png 37334_20170422011554_budgetalphaon.png 37334_20170422011601_suppression.png 37334_20170422011617_injoscillation.png 37334_20170422011624_calnoiseswitchof.png
Comments related to this report
mwas - 17:07, Monday 24 April 2017 (37354)
Made a noise budget (and calibration) for the quiet data with MICH (alpha) subtraction. For now the subtraction is modeled not measured so the noise projection doesn't fit well everywhere. The calibrated noise below 100Hz is well reduce compared to 10 days ago, about a factor 10, with the sensitivity limited by PD electronic (dark) noise from 40Hz, and the lowest point a ~1e-20/rtHz.

This correspond to a range of 145 kpc for BNS and 2 Mpc for 30 solar mass BBH. Still a long way to go, but it will soon start to make sense to look at the range!
Images attached to this comment
37354_20170424163804_screenshotfrom20170424161130.png
AdV-COM (automation)
Print this report.
bersanetti, allocca, swinkels - 01:23, Saturday 22 April 2017 (37335)Get code to link to this report
ITF_STATUS Troubles

Tonight after the shift we wanted to leave the ITF in AUTORELOCK mode, but as soon as we opened ITF_STATUS we noticed it was stuck with a ezca connection error,  complaining that "function does not have the method warning"; since the only "warning" method I could think about was the logger one, I commented all the log.warning lines in ITF_STATUS and then added the log = logging.getLogger(__name__) instruction to ITF_STATUS_library.py, but I'm not sure this is the right way to fix the problem. Notice that the DMS flags worked correctly all day long.

After that I found out that ITF_STATUS did not recognize the new [ACQUIRE_]LOW_NOISE_1 states, so I added them in the configuration file and updated the locked_state_index parameter to 122, which is the LOW_NOISE_1 state index.

I tried a manual unlock to verify the procedure, and it seems working. Unfortunately, due to the suppression of all the log.warnings I cannot be sure of definite success.

However, we leave the ITF in AUTORELOCK mode, and I will check remotely tomorrow if everything is working as expected.

Comments related to this report
bersanetti - 14:09, Saturday 22 April 2017 (37336)

I didn't get the chance to verify the behaviour of ITF_STATUS as the CoilsSb* servers keep crashing, and everything was stuck in DOWN; I disabled the use of the relays in ITF_LOCK, and commented also the duplication of the reset of the 6MHz amplitude on the LNFS which was present in the DOWN state of ITF_LOCK.

carbognani - 16:21, Monday 24 April 2017 (37353)

Checking the PySb code for possible causes of those crashes I spotted the fact that on the SET_OUTPUTS command implementation a burst of 24  single modbus coil setting commands was generated. I have inserted a small delay between the commands (0.2 sec) and I was not able to replicate the crash while commanding the relays from the VPM interface or from ITF_LOCK. The use of the relays in the DOWN and LOW_NOISE_1 states of ITF_LOCK has been provisionally restored.

Detector Operation (Operations Report)
Print this report.
menzione - 22:59, Friday 21 April 2017 (37333)Get code to link to this report
Operator Report - Afternoon Shift 21/04

Upon arrival I found ITF not locked due to the activities on TCS in DetectionLab.
Once concluded, at 17:00 LT, the planned activity on LSC started. It's going on without major problem.

VPM - Suspension
CoilsSbWI restarted after a crash at 16:06 LT.
CoilsSbNI restarted after a crash at 18:34 LT.

VPM - Detector s Environment Monitoring
ProcessUSGSData restarted after a crash at 18:42 LT.

DMS
Under request of V. Boschi I added BPC_Electr flag (subflag: SAT..BPC_satserverbpc1).

AdV-COM (AdV commissioning (1st part) )
Print this report.
bersanetti, allocca, swinkels - 22:21, Friday 21 April 2017 (37332)Get code to link to this report
Comment to Alpha subtraction - part I (Click here to view original report: 37318)

We implemented a notch filter for the 309 Hz line in the LOW_NOISE_1 state, as a last step with the switch of the coils' relays; in order to do that we added to the DARM loop the 'Arm_notch' filter, but disabling the already existing notch for a 16.85 Hz line, as it induced loop instability, but it was not used anyway. In addition, in order to use the additional filter we had to increase the maximal order of the 'LSC_NONE' filter placeholder from 80 to 100.

AdV-INF (Virgo Reference System Geometry)
Print this report.
paoli - 16:51, Friday 21 April 2017 (37327)Get code to link to this report
Floor heights in DET Lab for SQZ bench design
This morning we carried out the survey to determine the height of the floor in correspondence of the SQZ bench legs. The approximate position of the bench has been tracked on the floor, considering a footprint of about 2160x1260 mm.
The result is shown in Tab.1 which reports the Z coordinate of the 4 corners in VRS, named SQZNE-SQZSE-SQZSW-SQZNW in funcion of the orientation. Fig.1 shows a picture of the staff placed on SQZSW.
Images attached to this report
37327_20170421165027_fig1.jpg
Non-image files attached to this report