Journal article icon

Journal article

Search for multi-messenger sources of gravitational waves and high-energy neutrinos with advanced LIGO during its first observing run, ANTARES and IceCube

Abstract:
Astrophysical sources of gravitational waves, such as binary neutron star and black hole mergers or core-collapse supernovae, can drive relativistic outflows, giving rise to non-thermal high-energy emission. High-energy neutrinos are signatures of such outflows. The detection of gravitational waves and high-energy neutrinos from common sources could help establish the connection between the dynamics of the progenitor and the properties of the outflow. We searched for associated emission of gravitational waves and high-energy neutrinos from astrophysical transients with minimal assumptions using data from Advanced LIGO from its first observing run O1, and data from the ANTARES and IceCube neutrino observatories from the same time period. We focused on candidate events whose astrophysical origin could not be determined from a single messenger. We found no significant coincident candidate, which we used to constrain the rate density of astrophysical sources dependent on their gravitational wave and neutrino emission processes.
Publication status:
Published
Peer review status:
Peer reviewed

Actions

Access Document

Files:
Publisher copy:
10.3847/1538-4357/aaf21d

Authors

More by this author
Institution:
University of Oxford
Division:
MPLS
Department:
Physics
Sub department:
Theoretical Physics
Oxford college:
Linacre College
Role:
Author
ORCID:
0000-0002-3542-858X


Publisher:
American Astronomical Society
Journal:
Astrophysical Journal More from this journal
Volume:
870
Issue:
2
Publication date:
2019-01-16
Acceptance date:
2018-11-16
DOI:
EISSN:
1538-4357
ISSN:
0004-637X


Keywords:
Pubs id:
pubs:938373
UUID:
uuid:cf35f513-8018-483b-b64e-40bf6839cd4e
Local pid:
pubs:938373
Source identifiers:
938373
Deposit date:
2019-01-25
ARK identifier:

Terms of use


Views and Downloads






If you are the owner of this record, you can report an update to it here: Report update to this record

TO TOP