sheila.dwyer@LIGO.ORG - posted 10:52, Thursday 25 May 2017 - last comment - 17:29, Saturday 27 May 2017(36418)
problems with lockloss3
There seem to be a couple of problems with our new lockloss script, (alog 34878) I have filed bug 1093
For now if people are having trouble with it being extremely slow (more than 5 minutes to generate a list of locklosses) or getting errors when you try to use lockloss select, or want the guardian log displayed, you can use lockloss2 in exactly the same way you would normally use lockloss
Dave and Jonathan had a temporary fix for this problem, which has been working most of the weekend. However, I ran into a new problem when trying to use the saturation feature. Here is the error message:
0: 2017-05-28_00:25:54Z ISC_LOCK LOCKING_ARMS_GREEN -> LOCKLOSS
select event by index [0]: 1
selected event:
2017-05-28_00:25:37Z ISC_LOCK FIND_IR -> LOCKLOSS
/ligo/apps/linux-x86_64/guardian-1.0.3/bin/guardlog DB gc.xlaunch cmd = --after DB gc.xlaunch cmd = 2017-05-28T00:23:37+00:00 DB gc.xlaunch cmd = --before DB gc.xlaunch cmd = 2017-05-28T00:25:38+00:00 DB gc.xlaunch cmd = ISC_LOCK
The channel file: channels_to_look_at_ALS.txt
The number of given channels: 24
Saturation value is 131072.
lockloss gps time = 1179966355.0
saturation checking time window: [-10,30]
fetching data from h1nds1:8088...
Traceback (most recent call last):
File "/opt/rtcds/userapps/release/sys/common/scripts/lockloss3.py", line 699, in <module>
args.func(args)
File "/opt/rtcds/userapps/release/sys/common/scripts/lockloss3.py", line 368, in cmd_select
saturations = check_saturated(args,schannels,shortener,ll_time=time.gps())
File "/opt/rtcds/userapps/trunk/sys/common/scripts/lockloss_utils.py", line 1126, in check_saturated
nds_result = conn.fetch(start_time, end_time, channels[idx:idx+nds_chunk])
File "/ligo/home/jonathan.hanks/nds2/bin/nds2_scratch/lib/python2.7/site-packages/nds2.py", line 2815, in fetch
return _nds2.connection_fetch(self, *args)
RuntimeError: Low level daq error occured [13]: Requested data were not found.
There is a gap in H1:SUS-ETMX_M0_MASTER_OUT_F1_DQ