This page documents the offline analysis of O4 Ligo and Virgo data to detect GW signals from coalescences of compact objects (black holes or neutron stars) using the MBTA code.
The data were split in several chunks of 2 weeks length, analysed separately. The official chunk limits are given in this page.
The data analysed in this page correspond to chunk03 from 2023-06-20 14:21 (UTC) to 2023-07-04 22:47 (UTC) (GPS time range 1371306087 - 1372546081)
Data quality
The list of actually analysed segments (analysis ready segments considered good after removal of CAT1 vetoes and after MBTA gating) can be found here for H1 and L1 and the table below summarises the corresponding times.| after CAT1 (in days) | after Gating (in days) | |
| Duration of overall data taking | 14.35 | 14.35 |
| Duration with HL good | 8.75 (61.0 %) | 8.74 (60.9 %) |
| Duration with H good | 9.57 (66.7 %) | 9.55 (66.6 %) |
| Duration with L good | 11.74 (81.8 %) | 11.73 (81.7 %) |
| Duration with at least one detector (singles) good | 12.55 (87.5 %) | 12.55 (87.4 %) |
These directories contain the files with list of good segments after CAT1 and list of good segments after gating for this chunk and summary is given here
Run monitoring
Fig Mon.1 : Data quality flag (a value different from 0 means good data) as a function of time, for the different type of triggers.
Fig Mon.2 : Single-detector trigger rate in H1, raw (in black) and after all cleaning (in red).
Fig Mon.3 : Single-detector trigger rate in L1, raw (in black) and after all cleaning (in red).
Fig Mon.4 : The grey band shows the periods in which the data is considered good (ANALYSIS-READY segments after CAT1 vetoes and gating). Black crosses show the template index for HL coincidences, with a combined ranking statistic of at least 7.
Fig Mon.5 : Combined ranking statistics (reweighted SNR times SNR excess) of HL coincidences as a function of the template duration and of the coincidence time.
MBTA data location
The gwf files and log files produced by MBTA can be found in the following directories:Preprocessing: /sps/virgo/USERS/mbta/O4/preprocessing/chunk03/mbtaD/v02 /sps/virgo/USERS/mbta/O4/preprocessing/chunk03/mbtaI/v03/batchs-0-2 /sps/virgo/USERS/mbta/O4/preprocessing/chunk03/mbtaI/v03/batchs-1-3 Filtering: /sps/virgo/USERS/mbta/O4/results/chunk03/mbtaD/run07 /sps/virgo/USERS/mbta/O4/results/chunk03/mbtaI/run07/batchs-0-2 /sps/virgo/USERS/mbta/O4/results/chunk03/mbtaI/run07/batchs-1-3 Postprocessing: /sps/virgo/USERS/mbta/O4/results/chunk03/mbtaD/run07/postfiltering/v01 /sps/virgo/USERS/mbta/O4/results/chunk03/mbtaI/run07/batchs-0-2/postfiltering/v01 /sps/virgo/USERS/mbta/O4/results/chunk03/mbtaI/run07/batchs-1-3/postfiltering/v01
In each directory:
- one .seff file gives the slurm performance
- one .checks file summarizes the production consistency checks
In each chunk root dir of preprocessing, filtering or postprocessing, a README file gives the description of the different productions available.
Checks of the production
A description of the checks is given herePreprocessing of data: performance and checks
Preprocessing of injection trains 0 and 2 spaced by 12s: performance and checks
Preprocessing of injection trains 1 and 3 spaced by 12s: performance and checks
Filtering of data: performance and checks
Filtering of injection trains 0 and 2 spaced by 12s: performance and checks
Filtering of injection trains 1 and 3 spaced by 12s: performance and checks
Postprocessing of data: performance and checks
Postprocessing of injection trains 0 and 2 spaced by 12s: performance and checks
Postprocessing of injection trains 1 and 3 spaced by 12s: performance and checks
The checks and performance files are in this directory