Troubleshooting 255 I/O Errors - Offsource Runs
I am still getting the following for about 2/200 (on average) of our offsource background/offsource injection runs (bayeswave.sub). Here is an example error from /home/johnmichael.sullivan/Projects/o4-IWC-analy/iwc-run-tutorial/o3b/GW200311B/GW200311B_o4_TGR_revComplete_11_10_prod_regressionTest_nOffs200/offsource_background/logs/BayesWave_trigtime_1267959794.030570030_0.0_0.0_0-323777715-0.err
:
Estimating PSD for H1 using 1 segments of 8192 samples (4.000000s)
Slid PSD estimation of H1 by -0.000000 s from 1267959792.0305700302 to 1267959792.0305700302
XLAL Error - XLALFrameUFrFileOpen_FrameL_ (/home/conda/feedstock_root/build_artifacts/lalframe-split_1681285144449/work/lib/LALFrameL.c:188): FrFileINew failed.
XLAL Error - XLALFrameUFrFileOpen_FrameL_ (/home/conda/feedstock_root/build_artifacts/lalframe-split_1681285144449/work/lib/LALFrameL.c:188): I/O error
XLAL Error - XLALFrFileOpenURL (/home/conda/feedstock_root/build_artifacts/lalframe-split_1681285144449/work/lib/LALFrameIO.c:117): Could not open frame file /ceph/mirror/frames/O3/hoft_C01_clean_sub60Hz/H1/H-H1_HOFT_CLEAN_SUB60HZ_C01-12679/H-H1_HOFT_CLEAN_SUB60HZ_C01-1267953664-4096.gwf
In iwc_pipe (here, from 1184-1203) we have some checking to make sure we choose from frame files returned by `gw_data_find`.
If the following is the issue: does anyone have suggestions in Python for making sure we choose readable times for our offsource runs?
Edited by John Sullivan