Swiftly Chasing Gravitational Waves across the Sky in Real Time
Bibliographic record
Abstract
Abstract We introduce a new capability of the Neil Gehrels Swift Observatory, dubbed “continuous commanding,” that achieves 10 s latency response time on orbit to unscheduled target-of-opportunity requests received on the ground. We show that this will allow Swift to respond to premerger (early-warning) gravitational-wave (GW) detections, rapidly slewing the Burst Alert Telescope (BAT) across the sky to place the GW origin in the BAT field of view at or before merger time. This will dramatically increase the GW/gamma-ray burst (GRB) codetection rate and enable prompt arcminute localization of a neutron star merger. We simulate the full Swift response to a GW early-warning alert, including input sky maps produced at different early-warning times, a complete model of the Swift attitude control system, and a full accounting of the latency between the GW detectors and the spacecraft. 60 s of early warning can double the rate of a prompt GRB detection with arcminute localization, and 140 s guarantees observation anywhere on the unocculted sky, even with localization areas ≫1000 deg 2 . While 140 s is beyond current GW detector sensitivities, 30–70 s is achievable today. We show that the detection yield is now limited by the latency of LIGO/Virgo cyberinfrastructure and motivate a focus on its reduction. Continuous commanding has been integrated as a general capability of Swift, significantly increasing its versatility in response to the growing demands of time-domain astrophysics. We demonstrate this potential on an externally triggered fast radio burst (FRB), slewing 81° across the sky, and collecting X-ray and UV photons from the source position <150 s after the trigger was received from the Canadian Hydrogen Intensity Mapping Experiment, thereby setting the earliest and deepest such constraints on high-energy activity from nonrepeating FRBs. The Swift Team invites the community to consider and propose novel scientific applications of ultra-low-latency UV, X-ray, and gamma-ray observations.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".