REVIEW 3 cited by
GstLAL: A software framework for gravitational wave discovery
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
The GstLAL library, derived from Gstreamer and the LIGO Algorithm Library, supports a stream-based approach to gravitational-wave data processing. Although GstLAL was primarily designed to search for gravitational-wave signatures of merging black holes and neutron stars, it has also contributed to other gravitational-wave searches, data calibration, and detector-characterization efforts. GstLAL has played an integral role in all of the LIGO-Virgo collaboration detections, and its low-latency configuration has enabled rapid electromagnetic follow-up for dozens of compact binary candidates.
Forward citations
Cited by 3 Pith papers
-
Detecting regular precession using a new gravitational waveform model directly parameterized by both precession amplitude and frequency
A new toy inspiral waveform parameterized directly by precession amplitude and frequency predicts that precession is most detectable at 'plus nulls' and in a majority of isotropic maximal-spin black-hole binaries out ...
-
GW230814: investigation of a loud gravitational-wave signal observed with a single detector
GW230814 is a binary black hole merger seen in a single detector, yielding the first confident l=4 mode detection and a ringdown damping anomaly that noise or waveform models can explain.
-
Searches for Binary Mergers with Sub-solar Mass Components in Data from the First Part of LIGO--Virgo--KAGRA's Fourth Observing Run
No sub-solar-mass compact-binary mergers were found in LIGO O4a data, giving 90% merger-rate upper limits of 110-10000 Gpc^-3 yr^-1 and weak new dark-matter constraints.
Discussion (0). Continue with ORCID to comment.