Skip to content

Set up your observatory and telescope

This page walks a telescope owner through getting a telescope onto Skynet, from the application to a paired, connected SkyNode. For why you would join and the onboarding flow at a glance, see Onboarding and application. For what the records are, see Observatories and sites, Telescopes and Instruments and devices.

Some records are created by Skynet staff and the rest by you, in the website and in SkyNode:

Record Created by Where you edit it afterwards
Organization Skynet staff Settings → Profile (owner)
Site and observatory Skynet staff Observatory photo on its Overview; other fields through the API
Telescope, with its starting queues and access grants Skynet staff The telescope’s Settings, Queues and Access Grants tabs
Devices (mount, cameras, focusers, weather sensors, IP cameras, …) You, in SkyNode SkyNode Settings
Instruments (for example an optical imager) Through the API, with Skynet staff SkyNode Settings → Optical Imagers / Radio Spectrometers
SkyNode installation You, by pairing SkyNode SkyNode Settings → General; the telescope’s API Tokens tab
  • The owner role. Skynet staff create your organization and invite you as its owner. Pairing SkyNode needs the owner role; a device manager can do every other step on this page. See Roles and permissions.
  • Your team. Once you’ve accepted, invite the people who will run the telescope and give them roles on People → Members (Manage roles on a member’s row). Device manager is the usual role for operators; telescope viewer is for people who should follow the telescope without changing it.
  • A machine for SkyNode at the site that can reach your devices and make outbound HTTPS connections. See Installing SkyNode for requirements.

In your organization, open Settings → Telescope Application and click Start application (once you have applied, the button reads Apply for another telescope). Pick the telescope type (optical imaging, radio, or something else) and answer the questions about the site and hardware; rough answers are fine. Submitted applications are listed on the same page under Submitted Applications with their status as staff move them along. What each status means is on Onboarding and application.

Once your application is accepted, Skynet staff create the site, the observatory and the telescope, owned by your organization, and give the telescope its starting configuration: four observing queues (Maintenance, TOO, Calibration, General) and telescope access grants for your organization, Skynet and the Telescope Exchange. All of this is a starting point you can change; see Observing queues and Telescope access grants.

The records then appear in your organization’s header: Observatories and Telescopes, each with a menu that jumps to a single observatory or telescope.

Open Observatories, then your observatory. It has three tabs: Overview, Live and IP Cameras.

  • On Overview, use Upload photo (or Replace photo) to set the image shown for the observatory. The Telescopes card lists its telescopes.
  • The observatory’s name, description, site and public visibility have no form in the website. Ask Skynet staff to change them, or use PATCH /v1/observatories/{uid}.
  • Observatory-wide weather sensors, site IP cameras and operational constraints are set up from SkyNode (steps 6 to 8).

Open Telescopes, then your telescope, then its Settings tab.

  1. Use Upload photo to add a photo of the telescope.
  2. Under Identity, check Name, Short name, Slug, IAU code and Description.
  3. Under Location, Observatory and Site are shown read-only. Set the telescope’s own Latitude (°), Longitude (°) and Elevation (m): they can differ slightly from the observatory’s.
  4. Under Visibility, leave Available for scheduling and Publicly listed as they are for now; you set them when you go live (step 10).
  5. Click Save changes.

The name, description and location can also be edited later from SkyNode’s Settings → General, which saves them to the same record.

  1. Open Settings → Software in your organization and download the SkyNode installer. The page appears once your organization owns a telescope. See Software downloads.
  2. Install SkyNode on the site machine and start it.
  3. Sign in when SkyNode opens the browser. Sign in as a member with the owner role.
  4. SkyNode’s node selection asks for the Observatory, the Node type (a telescope node, or an observatory node for site hardware only) and, for a telescope node, the Telescope.

Pairing creates the SkyNode installation on Skynet; if another installation was already paired to the same telescope, it is signed out. The full procedure is in Installing SkyNode, and the difference between node types in SkyNode.

Afterwards the installation is listed under SkyNode installations on Settings → Software (owners only), and its token shows on the telescope’s API Tokens tab, where an owner or device manager can revoke it. To retire a node, use Unbind installation on SkyNode’s Settings → General.

Devices are added on the node, not in the website. In SkyNode, open Settings and the page for each kind of device you have (Enclosure, Mount, Cameras, OTAs, Filter Wheels, Focusers, Rotators, Weather Sensors, Antennas, Receivers, Radio Backends).

  1. Use Manage → Create new to add a device to Skynet, or Manage → Assign existing to attach one your organization already has on Skynet.
  2. In the device’s driver section, pick the Driver, click Configure driver, and click Connect.
  3. Fill in the device’s own settings below the driver section.

A new node starts held: nothing connects on its own and automation does not run until you connect each device once and click Start automation on Settings → Startup & Shutdown. The settings pages are described in Local GUI tour, the drivers in Drivers, and per-device wiring under Wiring.

An instrument is the combination of devices observations are matched against, for example an optical imager made of an OTA, a camera and a filter wheel. Neither the website nor SkyNode has a control to create one today: instruments are created through the API (POST /v1/instruments, which needs edit rights on the telescope), and Skynet staff set them up with you once your devices exist.

Once an instrument exists, edit it in SkyNode: Settings → Optical Imagers holds its focus calibration, plate solving and pointing refinement, and calibration-frame settings (biases, darks, flats); Settings → Radio Spectrometers holds a radio instrument’s settings. If Optical Imagers says no imagers are assigned to the telescope, the instrument has not been created yet.

  • IP cameras are added in SkyNode on Settings → IP Cameras with Add IP Camera, and their viewing and control settings are also on the website’s IP Cameras tabs. See IP cameras.
  • Operational constraints (weather, sun altitude, mount-Sun separation and so on) are set on SkyNode’s Settings → Operational Constraints. See Observatories and sites for how observatory and telescope constraints combine.
  • SkyCanary (a synthetic weather station built from public radar and satellite feeds, read by a SkyNode weather-sensor driver) and SkyDesk (the remote-support client staff use to help you on the control computer) are on the same Settings → Software page as SkyNode.

With SkyNode connected, open the telescope in the website:

  • Live shows the mount, enclosure, cameras and instruments as SkyNode reports them.
  • Overview shows the telescope’s status, frame quality, nightly activity and recent observations.
  • Weather shows the weather sensors and constraint status.
  • Log streams the node’s live log.

If a page stays empty, check the hub connection in SkyNode’s status bar and see Troubleshooting.

  1. Review the queues and who has time on the telescope: see Configure queues and Grant access.
  2. Run a shakedown observation through your own observing account, as described in Onboarding and application.
  3. On the telescope’s Settings, tick Available for scheduling so the scheduler places work on the telescope, and Publicly listed if you want it on public pages such as the public Live page. Click Save changes.

Untick Available for scheduling whenever you take the telescope offline for maintenance; access grants and queues stay as they are.