Papers › Does the Black Hole Merger Rate Evolve with Redshift?
Does the Black Hole Merger Rate Evolve with Redshift?
Maya Fishbach, Daniel E. Holz, Will M. Farr
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
We explore the ability of gravitational-wave detectors to extract the redshift distribution of binary black hole (BBH) mergers. The evolution of the merger rate across redshifts 0 < z ≲1 is directly tied to the formation and evolutionary processes, providing insight regarding the progenitor formation rate together with the distribution of time delays between formation and merger. Because the limiting distance to which BBHs are detected depends on the masses of the binary, the redshift distribution of detected binaries depends on their underlying mass distribution. We therefore consider the mass and redshift distributions simultaneously, and fit the merger rate density, dN/dm₁ dm₂ dz. Our constraints on the mass distribution agree with previously published results, including evidence for an upper mass cutoff at ∼40 M_⊙. Additionally, we show that the current set of six BBH detections are consistent with a merger rate density that is uniform in comoving volume. Although our constraints on the redshift distribution are not yet tight enough to distinguish between BBH formation channels, we show that it will be possible to distinguish between different astrophysically motivated models of the merger rate evolution with ∼100--$300$ LIGO-Virgo detections (to be expected within 2--5 years). Specifically, we will be able to infer whether the formation rate peaks at higher or lower redshifts than the star formation rate, or the typical time delay between formation and merger. Meanwhile, with ∼100 detections, the inferred redshift distribution will place constraints on more exotic scenarios such as modified gravity.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections