refined time finding glitch instead of lock loss
There's a glitch here that's tricking the refined time algorithm:
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/?event=1224263564
There's a glitch here that's tricking the refined time algorithm:
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/?event=1224263564
assigned to @patrick.godwin
I think the second one might actually be correct (I think it is probably right to say the interferometer is not locked after that glitch).
added Bug label
added Analysis label
changed the description
marked this issue as related to #97
I think I'll close this issue since this seems mostly OK, and we have a more recent set of refine time issues to deal with.
closed