REVIEW 4 cited by
A Rule of Thumb for the Detectability of Gravitational-Wave Bursts
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
We derive a simple relationship between the energy emitted in gravitational waves for a narrowband source and the distance to which that emission can be detected by a single detector. We consider linearly polarized, elliptically polarized, and unpolarized gravitational waves, and emission patterns appropriate for each of these cases. We ignore cosmological effects.
Forward citations
Cited by 4 Pith papers
-
All-sky search for long-duration gravitational-wave transients in the first part of the fourth LIGO-Virgo-KAGRA Observing run
No long-duration gravitational-wave transients were found in O4a data; 50% efficiency amplitude limits improved by about 30% over O3, and eccentric CBC rate limits improved by factors of 2-7.
-
Guiding interferometer improvements with the frequency-dependent inspiral range
The cumulative normalized range and its two-curve difference make it easier to see which frequency bands actually limit a gravitational-wave detector's inspiral range.
-
Search for gravitational waves associated with high-energy neutrinos detected by IceCube during the third observing run of LIGO-Virgo
An unmodeled targeted X-Pipeline search finds no significant GW counterparts to IceCat-1 neutrinos in O3 and reports 90% exclusion distances of tens to a few hundred Mpc depending on waveform model.
-
All-sky search for short gravitational-wave bursts in the first part of the fourth LIGO-Virgo-KAGRA observing run
An all-sky search of O4a LIGO data finds no new gravitational-wave bursts and improves burst sensitivity and rate limits by factors of 2 to 10 over the previous run.
Discussion (0). Continue with ORCID to comment.