Pipeline Virgo time slide datafind issue
It looks like the datafind call from the pipeline sometimes misses to take time slides properly into account when Virgo is involved. This results in frame read errors.
For example, in a run I've seen the following time slide:
Slid PSD estimation of V1 by -188717.000000 s from 1257292021.2765998840 to 1257103304.2765998840
And the Virgo datafind call was this:
gw_data_find --observatory V --type V1Online -s 1257177929 -e 1269349198 --lal-cache -u file > datafind/V1.cache
So the start time of datafind is later than the new time where Virgo was shifted to.
One example run is in this batch on CIT:
The one that failed with this error is this one:
The corresponding err file with time slide info and frame read error is here:
I was able to get these runs done by rerunning datafind by hand, but it would be good to fix this in the pipeline.
Maybe @meg.millhouse can add something to this, as I think she was the one to code up Virgo time slides.