Observing policy and shutdown interlocks
This page covers three separate controls: the weather and safety operational constraints that hold your hardware when conditions are bad, the shutdown interlocks an operator places to stop a telescope on purpose, and the observing policies your organization can attach to its observing accounts. What each one is and how SkyNode acts on it is explained in Observing policy and constraints.
| Control | Where you set it |
|---|---|
| Weather-sensor constraints | SkyNode, Settings → Operational Constraints |
| Mount–sun separation constraints | The API only |
| Shutdown interlocks | SkyNode, the Lock button on the Overview page |
| Observing policies | The website, your organization’s Settings → Observing Policies |
Set up a weather constraint
Section titled “Set up a weather constraint”Weather constraints are set at the telescope, in the SkyNode that controls the devices. The page needs SkyNode to be bound to an observatory with at least one weather sensor configured.
- In SkyNode, open Settings and choose Operational Constraints (under Safety).
- Click Add constraint.
- Pick the Weather sensor and the Parameter to watch. Only the channels the sensor reports are listed; if the list is empty, set the channels under Settings → Weather sensors → Reported channels first.
- Enter a Min value, a Max value, or both. The constraint reads unsafe when the reading falls below the minimum or rises above the maximum.
- Click Create. The constraint now appears as a card marked Not enforcing: it is monitored but holds nothing yet.
- On the card, click + Add action for each device the constraint should hold. Pick the device and what to do to it (Keep enclosure closed, Prevent enclosure motion, Shut down camera, Stop mount motion, or Warn only; the menu offers only the actions that fit that device), and tick when the action fires: on unsafe, on unknown, on stabilizing. A new action defaults to keeping an enclosure closed on unsafe and unknown.
- Click Save changes…, review the summary, and click Save changes to apply.
The new constraint is scoped to the observatory, so one rain constraint can keep every enclosure on the site closed. A constraint takes effect at the telescope within about a second of saving.
Edit or remove a constraint
Section titled “Edit or remove a constraint”Each card on Settings → Operational Constraints can be edited in place. Changes stay as a draft (with an Unsaved changes bar and a Revert button) until you save.
| Field | What it does |
|---|---|
| Active | When off, the constraint is ignored and its protection no longer applies. |
| Min value / Max value | The safe range. Leave one blank for no bound on that side. |
| Stability threshold (s) | How long the reading must stay in range before the constraint reads safe again. |
| Max data age (s) | How long without a fresh reading before the sensor is treated as unknown (300 by default). |
| Actions | The devices the constraint holds and when. |
A card shows only the actions for devices this SkyNode controls. Actions for devices run by another SkyNode installation stay hidden and untouched, and a constraint that also protects such devices cannot be deleted from this one; remove this node’s own actions instead.
Mount–sun separation constraints have no editor in SkyNode or the website. Create them with POST /v1/operational-constraints (constraint type mount_sun_separation); this needs the owner role in the organization that owns the observatory. Sun-altitude, battery and storage constraints can also be created through the API, but SkyNode does not evaluate them.
To check constraint readings, limits and verdicts from the website, open the telescope’s Overview page; the website shows constraints but cannot edit them.
Skip a stabilizing wait
Section titled “Skip a stabilizing wait”After a constraint goes back in range it reads stabilizing until the stability threshold has passed. If you have checked the site in person and want to resume sooner, click Skip wait on that constraint’s panel on the SkyNode Overview page and confirm with Skip Wait. The reading must still be in range. The override applies to that SkyNode installation only, and the next out-of-range reading re-arms the wait.
Place a shutdown interlock
Section titled “Place a shutdown interlock”Use an interlock when the telescope must stop now and stay stopped: a hardware fault, people working on site, a known hazard. Interlocks are placed from SkyNode; the website shows them but has no control to create one.
- In SkyNode, open the Overview page and click Lock on the telescope’s panel.
- Choose the Scope: Current telescope only, or Entire observatory (every telescope at the observatory; only available once the telescope is assigned to an observatory).
- Enter a Name, shown on the dashboard banner, and optionally a Reason.
- Leave Enabled ticked. Starts at defaults to now; set it later to schedule the lock ahead. Set Expires at to have it lapse on its own, or leave it blank for a lock that holds until cleared.
- Click Create Lock.
While the interlock is active, SkyNode stops the running task, runs the telescope’s shutdown actions, and starts no new work. The SkyNode panel shows a SHUTDOWN INTERLOCK banner with the name, reason, scope and expiry, and the telescope’s Overview page in the website shows Shutdown interlock active with the name. Which shutdown steps run is set in SkyNode under Settings → Startup & Shutdown; see SkyNode operations → Shutdown actions.
Clear a shutdown interlock
Section titled “Clear a shutdown interlock”On the SkyNode Overview page, click Cancel shutdown on the interlock banner. This disables the interlock; SkyNode then runs the configured startup actions and resumes automation, as described in Bringing the telescope back up after a shutdown. An interlock with an expiry time also clears itself when it expires.
Through the API, interlocks are at /v1/shutdown-interlocks: PATCH with isEnabled: false disables one, DELETE removes it.
Create an observing policy
Section titled “Create an observing policy”An observing policy lists what accounts that use it may submit. Managing policies needs the owner role in the organization.
- In your organization, open Settings and choose Observing Policies.
- Click New policy.
- Fill in the rules:
- Name (unique within the organization) and an optional Description.
- Allowed request types and Allowed data policies: at least one of each.
- Maximum private period: tick Set a limit to cap how long private data may stay private before it becomes public; leave it off for no limit.
- Allowed target position types, Allowed catalog object types, Allowed coordinate types: leave empty to allow all.
- Hidden data: Allow hidden observations and Allow hidden telemetry.
- Click Create policy.
Attach a policy to an observing account
Section titled “Attach a policy to an observing account”- In your organization, open Observing Accounts and click the account.
- Click Edit, pick the policy under Observing policy, and save.
Set the policy on a root account; its subaccounts inherit it, and the field is locked on a subaccount. The policy’s own page, opened from the Observing Policies list, shows which accounts use it under Used by accounts.
A queue access grant can also reference a policy, but the website has no control for it yet: the Observing policy column in the access-grant dialog is a placeholder. Through the API, pass observingPolicyId when adding a queue access grant; the policy must belong to the telescope’s owner and the grantee must be an organization.
Edit or delete a policy
Section titled “Edit or delete a policy”On Settings → Observing Policies, use the pencil to edit a policy and the trash icon to delete it, or open the policy and use Edit and Delete. A policy that observing accounts still use cannot be deleted: assign those accounts another policy (or none) first.