Journal article
GW170817A as a hierarchical black hole merger
- Abstract:
- Despite the rapidly growing number of stellar-mass binary black hole mergers discovered through gravitational waves, the origin of these binaries is still not known. In galactic centers, black holes can be brought to each others' proximity by dynamical processes, resulting in mergers. It is also possible that black holes formed in previous mergers encounter new black holes, resulting in so-called hierarchical mergers. Hierarchical events carry signatures such as higher-than-usual black hole mass and spin. Here we show that the recently reported gravitational-wave candidate, GW170817A, could be the result of such a hierarchical merger. In particular, its chirp mass ~40 M⊙ and effective spin of χeff ~ 0.5 are the typically expected values from hierarchical mergers within the disks of active galactic nuclei. We find that the reconstructed parameters of GW170817A strongly favor a hierarchical merger origin over having been produced by an isolated binary origin (with an odds ratio of > 103).
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Accepted manuscript, 2.8MB, Terms of use)
-
- Publisher copy:
- 10.3847/2041-8213/ab745d
Authors
- Publisher:
- IOP Publishing
- Journal:
- Astrophysical Journal Letters More from this journal
- Volume:
- 890
- Issue:
- 2
- Article number:
- L20
- Publication date:
- 2020-02-18
- Acceptance date:
- 2020-02-10
- DOI:
- EISSN:
-
2041-8213
- ISSN:
-
2041-8205
- Language:
-
English
- Keywords:
- Pubs id:
-
1128030
- Local pid:
-
pubs:1128030
- Deposit date:
-
2020-08-24
Terms of use
- Copyright holder:
- American Astronomical Society
- Copyright date:
- 2020
- Rights statement:
- © 2020. The American Astronomical Society. All rights reserved.
- Notes:
- This is the accepted manuscript version of the article. The final version is available online from the American Astronomical Society at: https://doi.org/10.3847/2041-8213/ab745d
If you are the owner of this record, you can report an update to it here: Report update to this record