Skip to content

Alerts

Skynet can create observations automatically from external astronomical alert streams — gamma-ray bursts, gravitational-wave events, and survey transients. Alerts are a first-class Skynet resource, not something you wire up per telescope: Skynet maintains the connections to the alert brokers (NASA GCN and Fink) centrally, so neither owners nor observers configure a feed or a credential.

This page is the owner-side view — how alert-driven observations reach your telescopes. For the full subscription workflow (sources, filters, response templates, lifecycle), see the observer-facing Alert subscriptions page.

An alert subscription belongs to an observer or organization. When an alert matches, Skynet builds a normal observation — target filled in from the event — and submits it to the scheduler against the subscriber’s observing grants, exactly like an observation created by hand. It competes for time, respects access, and runs through your queues like anything else.

So the levers you already have as an owner apply unchanged:

  • Queues and access grants. Alert observations only reach your telescope through a queue access grant behind the subscriber’s observing grants. To carve out time for rapid follow-up without it competing with normal science, use the telescope’s target-of-opportunity (TOO) queue (part of the standard queue set) and grant access on it to the users or organizations that should be able to trigger on it. Because an observing account reaches at most one queue per telescope, the subscriber funds alert observations from an account that references the TOO queue.
  • Prioritization. Give that queue the position you want urgent events to have relative to your standing programs — see Queue prioritization. A higher queue goes first at the next scheduling pass, but does not interrupt a task that is already running.
  • Instruments. A subscription’s response templates can be restricted to specific instruments; combined with the queues the subscriber can reach, that bounds which hardware an alert can actually use.
  • Broker connections and credentials — handled centrally by Skynet; there is nothing to install or authorize on your side.
  • Filters, response templates, and lifecycle policies — these live on the observer’s subscription, not on your telescope.

If you want a telescope to participate in coordinated rapid follow-up, the setup is a queue-and-grant exercise, not an integration.

  • AlertSource
  • AlertSubscription
  • AlertTrigger
  • AlertEvent
flowchart LR
  BRK["Alert brokers<br/>NASA GCN · Fink"] --> SUB["Alert subscription<br/>filters + response spec"]
  SUB --> OBS["Observation"]
  OBS --> ACC["Subscriber's observing account<br/>(references the TOO queue on each telescope)"]
  ACC --> Q1(["Telescope 1 · TOO queue<br/>Organization A"])
  ACC --> Q2(["Telescope 2 · TOO queue<br/>Organization B"])

One subscription can reach telescopes owned by different organizations, as long as the subscriber holds a queue access grant on each telescope’s TOO queue and funds the response from an account that references those queues.