gwastro/1-ogc: v1.0 of the 1-OGC Catalog of Compact Binary Merger Candidates

<p>Introduction</p> <p>This repository contains the first Open Gravitational-wave Catalog (1-OGW), which is obtained by using the public data from Advanced LIGO&#39;s first observing run to search for compact-object binary mergers. Our analysis is based on new methods that improve the separation between signals and noise in matched-filter searches for gravitational waves from the merger of compact objects.</p> <p>We make available our complete catalog of events, including the sub-threshold population of candidates. The catalog contains approximately 150,000 candidate events. We note that since the vast majority of the events in the catalog are likely to be noise, we have provided information to rank and select candidate events. The three most significant signals in our catalog correspond to the binary black hole mergers <a href="https://journals.aps.org/prl/abstract/10.1103/PhysRevLett.116.061102">GW150914</a>, <a href="https://journals.aps.org/prl/abstract/10.1103/PhysRevLett.116.241103">GW151226</a>, and <a href="https://journals.aps.org/prd/abstract/10.1103/PhysRevD.93.122003">LVT151012</a>, respectively. We observe these signals at a true discovery rate of 99.92%. We find that LVT151012 alone has a 97.6% probability of being astrophysical in origin. No other significant binary black hole candidates are found, nor did we observe any significant binary neutron star or neutron star--black hole candidates.</p> <p>The catalog is stored in the file &#39;1-OGC.hdf&#39;. There are a variety of tools to access <a href="https://www.hdfgroup.org/">hdf files</a> from numerous computing languages. Here we will focus on access through python and <a href="www.h5py.org">h5py</a>.</p> <p>Analysis Details</p> <p>Details of the analysis are available in this <a href="https://arxiv.org/abs/1811.01921">preprint paper</a> and the configuration files needed to create the analysis workflows are provided in the <a href="https://github.com/gwastro/1-ogc/tree/master/workflow/configuration">workflow/configuration</a> directory.</p>