Missing Segments in locklost data
Been seeing more of these issues lately with lockloss events. Seems like the code is not getting the data during the allotted locklost time. Maybe a nds thing? Weird thing is though, I've seen this issue on multiple locklosses, but they eventually seem to just reconcile themselves somehow. Example event: https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1346176567