Telescopes
A telescope is the central unit of observation in Skynet. Each telescope is a physical system at an observatory site that can carry out observation tasks, and a record in Skynet that ties together a mount, devices, instruments, queues, and access policy.
If you’re an owner: this is the record SkyNode pairs against, and the record observers ultimately submit work to (through observing accounts + queues).
What a telescope record references
Section titled “What a telescope record references”Every Telescope points at:
- A Mount — the moving structure that tracks targets. A telescope has at most one mount.
- An optional Enclosure — dome or roll-off roof, with automation for rotation, shutter, and weather safety.
- A set of Devices — cameras, OTAs, filter wheels, focusers, instrument rotators, antennas, receivers, radio backends, weather sensors, IP cameras. The mix depends on whether the telescope is optical, radio, or hybrid.
- A set of Instruments — each instrument is a combination of devices that together can carry out a given observation type (an “imager” combines an OTA + camera + filter wheel; a “radio spectrometer” combines a receiver + radio backend). See Instrumentation.
- An ordered list of Observing queues — how time on the telescope is prioritized across users and programs. See Telescope access.
- A set of Operational constraints — telescope-level safety and scheduling rules that layer on top of the observatory-level ones.
Telescopes also carry:
- Identity — name, slug, short name, optional IAU code, description, hero image.
- Ownership — the entity (user or organization) that owns the telescope. This is who has top-level authority over access policy and configuration.
- Location — inherits from the observatory’s site, but the telescope carries its own latitude/longitude/elevation so a single observatory can host telescopes with subtly different pads.
- Availability flags —
isAvailable(Available for scheduling in Settings) gates scheduling entirely;isPublic(Publicly listed) lists the telescope on public surfaces such as the public Live page and the public telescope list. It does not open the telescope’s own pages to non-members; those follow the owning organization’s roles (a telescope access grant gives observing time, not access to these pages). - Calibration observing account — points at the account used to fund calibration tasks (flats, darks, biases) on this telescope.
- Local horizon — JSON-encoded local-horizon profile used during visibility calculations.
The flat-field source (twilight, or an enclosure screen with the mount and enclosure position to use for it) is not on the telescope record: it is part of each optical imager’s calibration configuration.
Manual control and SkyNode pairing
Section titled “Manual control and SkyNode pairing”SkyNode runs under one of two control authorities: remote (the default — SkyNode runs tasks scheduled by the hub) or manual (automated scheduling is paused; the local operator is driving). The authority is switched on the node itself, not on the telescope record, and the node reports it in the telescope’s status (controlAuthority). Separately, a web user can hold the telescope’s manual-control lease from the telescope console; while that lease is active, SkyNode pauses task execution even under remote, until the lease expires or is released.
The link between a telescope record and a running SkyNode install is the SkyNodeInstallation record, which is bound to an observatory and, for a telescope node, to one telescope. Pairing happens during install (see SkyNode → Overview).
In the web app
Section titled “In the web app”The owner-facing telescope UI is broad. An organization’s Telescopes page lists its telescopes, and each telescope has these tabs:
| Tab | What an owner does there |
|---|---|
| Overview | Status dashboard |
| Settings | Edit telescope configuration |
| Live | Live camera feed + mount position |
| Weather | Weather telemetry, constraint status |
| Log | Live log stream from the telescope’s SkyNode |
| Queues | Edit observing queues and prioritization |
| Schedule | Schedule view |
| Reports | Reports, such as imaging performance |
| Access | Manage who can access this telescope |
| API tokens | Issue API credentials for integrations (owners and device managers only) |
| IP cameras | Configure IP camera feeds |
Installers are not here: SkyNode, SkyCanary and SkyDesk are the same build for every telescope, so they live once per organization at Settings → Software — see Software downloads.
The web app runs against the same /v1/telescopes/* endpoints the API exposes.
Infrastructure model
Section titled “Infrastructure model”flowchart LR ORG["Organization"] --> OBS["Observatory"] SITE["Site"] -.- OBS OBS --> TEL["Telescope"] OBS --> OD["Observatory devices<br/>weather sensor · enclosure · IP camera"] TEL --> TD["Telescope devices<br/>mount · enclosure · OTA · camera · focuser<br/>filter wheel · instrument rotator<br/>antenna · receiver · radio backend<br/>weather sensor · IP camera"] TEL --> INS["Instruments"] INS --> OI["Optical imager<br/>OTA + camera + filter wheel<br/>(+ focuser, rotator)"] INS --> RS["Radio spectrometer<br/>receiver + radio backend"] TD -. combined into .-> INS
An organization owns observatories; an observatory may sit at a shared site. A device belongs to either a telescope or an observatory (an observatory-level weather sensor or all-sky camera serves every telescope there). Instruments are what observations are matched against.