1. The re-calibrated C01 hoft data now exist at CIT.
The results of some quick tests are given below.
The calibration group should decide if it wants to do further testing before we announce that this data is ready for analysis.
Updated missing data and DQ flags are also yet to be inserted into the segment database.
2. The filter files and command line arguments used with gstlal_compute_strain are documented here:
https://wiki.ligo.org/Calibration/GDSCalibrationConfigurations
3. The frame-types, channels names, and DQ flag names are documented in the DCC here:
https://dcc.ligo.org/LIGO-T1500502
Specifically, the frame-types are H1_HOFT_C01 and L1_HOFT_C01 and exist for:
H1: 1125969920 == Sep 11 2015 01:25:03 UTC to 1128398848 == Oct 09 2015 04:07:11 UTC
L1: 1126031360 == Sep 11 2015 18:29:03 UTC to 1128398848 == Oct 09 2015 04:07:11 UTC
4. I have update the times C01 exists on the GDS calibration configuration pages, on the O1 Run page, and in the DCC document:
https://wiki.ligo.org/Calibration/GDSCalibrationConfigurations
https://wiki.ligo.org/LSC/JRPComm/ObsRun1#Calibrated_Data_Generation_Plans_and_Status
https://dcc.ligo.org/LIGO-T1500502
(And the wiki pages, https://wiki.ligo.org/Calibration/T1500502_Prototype_Info points to the DCC document.)
5. Missing data flags and updated DQ flags are yet to be inserted into the segment database, pending generating these and an OK to proceed.
Here are some important details:
There is no missing H1_HOFT_C01.
There are gaps in L1_HOFT_C01 due to times when there were bad dataValid flags in the raw 64 s L1_R data. These gaps have been reduced down to the times of those raw frames -/+ 16 wings needed for filtering.
The times of the gaps in L1 C01 hoft intersected with L1_DMT-ANALYSIS_READY:1 are:
$ ./compareSegLists.tcl -f1 segs_MISSING_L1_HOFT_C01.txt -f2 segs_L1_DMT-ANALYSIS_READY_1.txt -i -s -T
1127128496 1127128592 96
1127353008 1127353104 96
1127387760 1127387856 96
1127435760 1127435856 96
1127687856 1127687952 96
1128122032 1128122075 43
1128122086 1128122128 42
1128320816 1128320912 96
Total duration = 661 seconds.
The UTC time of raw L1_R data with bad dataValid flags that intersect L1_DMT-ANALYSIS_READY:1 are:
$ ./compareSegLists.tcl -f1 segs_MISSING_L1_HOFT_C01.txt -f2 segs_L1_DMT-ANALYSIS_READY_1.txt -i | awk '{sum = $1 + 16; print sum}' | xargs -l tconvert
Sep 24 2015 11:14:55 UTC
Sep 27 2015 01:36:47 UTC
Sep 27 2015 11:15:59 UTC
Sep 28 2015 00:35:59 UTC
Sep 30 2015 22:37:35 UTC
Oct 05 2015 23:13:51 UTC
Oct 05 2015 23:14:45 UTC
Oct 08 2015 06:26:55 UTC
Most of the above seem associated loss or gain of lock. For example, see the drop out in L1 lock segments near Sep 24 2015 11:14:55 UTC here:
https://ldas-jobs.ligo-la.caltech.edu/~detchar/summary/day/20150924/
Gaps have been filled in when C00 was missing during maintenance days after DMT calibration restarts, but none of these intersect with L1_DMT-ANALYSIS_READY:1
Bottom line: The analysis using the C01 hoft will lose 661 s of L1 ANALYSIS_READY time due to bad dataValid flags.
6. The data is available via NDS2 and using gw_data_find.
Quick test show no issues, e.g., in these example comparison plots between GDS online and DCS offline C01 spectra from Oct 9 (i.e., after Oct. 6 filter updates):
https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=99928
https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=99929
And for example, calibration factors (which are not applied) now agree too, e.g., for L1:
https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=99835
https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=99836
https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=99839
The calibration group should decide if it wants to do further testing.