We are havgin trouble using the lockloss tool, but it has been working since Jamie made a change on October 19th. Is this related to problems with NDS2? TJ and I used lockloss plot earlier in the day today without problems.
Here's what I get:
lockloss select
Segmentation fault (core dumped)
Manually finding a time to ask for:
lockloss -c channels_to_look_at_NOISE_TUNINGS.txt plot 1161580111
.......
INFO: plotting: Adding subplot with the following channels:
H1:LSC-ASAIR_A_LF_OUT_DQ
2016-10-26 22:14:23,904 : NDSAxes : Initializing NDSAxes for the following channels:
H1:LSC-SRCL_GAIN
INFO: plotting: Initializing NDSAxes for the following channels:
H1:LSC-SRCL_GAIN
2016-10-26 22:14:23,938 : NDSBufferDict : Buffers requested at start time 1161580081 and end time 1161580110 for the following channels:
H1:LSC-SRCL_GAIN
INFO: bufferdict: Buffers requested at start time 1161580081 and end time 1161580110 for the following channels:
H1:LSC-SRCL_GAIN
terminate called after throwing an instance of 'NDS::connection::daq_error'
what(): Low level daq error occured [13]: Requested data were not found.
None of the selected channels returned data.
Aborted (core dumped)
The lockloss tool now uses NDS to find the lockloss times. Since both the time determination and data plotting both use NDS and they're both failing, this is definitely an NDS issue. Talk to Jonathan and/or Jim.
NDS1 access with the nds2-client python bindings.