Reports 1-1 of 1 Clear search Modify search
Detector Characterisation (Spectral lines)
swinkels - 19:21 Thursday 27 April 2017 (37385) Print this report
Calibration lines
I wrote a quick script to search for all possible calibration or other lines in the 10 minutes of yesterday's good data, to see if they show up in the spectrum of B1s2_PD1_Blended (which was the one used for LSC_DARM, but sampled at 20 kHz). To find the frequency of the lines, I parsed the configuration files of all processes in VPM for the keywords ACL_SINELINE_CH and ACL_SINEWAVE_CH. The various dither lines added in the DSPs are still missing, parsing the DSP code is still work in progress.

Some quick observations:
-the low-frequency permanent lines are not visible, see fig 1. They might have been off or too low. They also seem to fall in a forest of the angular dither lines generated in the DSPs (which still have to be lowered).
-the medium and high frequency calibration lines on the mirrors, and lines on the LSC degrees of freedom are mostly well visible, see fig 2.
-at high frequency (fig 3), the lines used for the LVDTs of SDB1 can be clearly seen, as are the (aliased) lines used to drive the PZT of the OMCs.

Images attached to this report
Non-image files attached to this report
Comments to this report:
rolland - 9:19 Friday 28 April 2017 (37389) Print this report

Indeed, the "low frequency calibration lines" are not yet  sent : their frequencies were not yet choosen carefully, and they will be useful mainly for monitoring of hrec and marionette actuation monitoring which is not yet measured.

narnaud, fiori - 17:06 Tuesday 01 August 2017 (38981) Print this report

Running Bas' script yesterday, there was a configuration file which could not be properly decoded. The part of the script which was crashing was inserted inside a

try:

   (...)

except:

block to protect the code. The updated script is attached to this entry.

Non-image files attached to this comment
swinkels - 11:53 Thursday 03 August 2017 (39020) Print this report
The error is caused by a typo in the configuration file of the InfraMoni process, around line 261:

QC_MONITOR * Lights "mean(INF..MCB_TUNNEL_LUX,100)<10000" "MC tunnel lights could be ON" "* <100" "MC tunnel lights could be ON"
QC_MONITOR * Lights "mean(INF..IER_LUX,100)>150" "Injection Electronic room lights could be OFF" "* <=== something missing here
#QC_MONITOR * Lights "mean(INF..IER_LUX,100)<10000" "Injection Electronic room lights could be ON" "* <200" "Injection Electronic room lights could be ON"
QC_MONITOR * Lights "mean(INF..EER_LUX,100)<10000" "EE room could be ON" "* <100" "EE room lights could be ON"
dattilo, sposito - 16:32 Thursday 03 August 2017 (39024) Print this report

The configuration file of the InfraMoni process has been corrected (there was a "*" in excess) and process restarted at around 12 UTC.

Thanks to Bas for having pointed out the typo.

fiori - 12:18 Monday 05 November 2018 (43402) Print this report

here attached is the latest version of Bas' code: added "try, catch" statement to avoid the script to stop on missing .cfg files

Non-image files attached to this comment
Search Help
×

Warning

Error

The present report has been modified outside this window. Please check for its integrity in the main page.

Refreshing this page will move this report into drafts.

×