Rigs, Sites & Live

Every registered database is a rig. Give each rig its optics, site and limits, compare upcoming nights in Rigs › Nights, and check reporting rigs in Rigs › Live.

New in 0.12. Each catalog in Settings › Databases & rigs › Overview links to its rigs' calibration settings. Rig and site forms show Unsaved changes until you save. PSF Guard sends a missed activation again when the remote site responds.

The rig list

Settings › Databases & rigs › Overview lists registered databases and their rigs. Each entry shows the rig’s field of view and pixel scale, whether its plugin has reported a camera, its remote planning destination and its latest plugin status. A new database becomes a rig once the Library opens. Setup opens the rig's setup in place; Library opens its catalog.

Under Calibration:, each row lists the calibration rigs its catalog records, with the number of settings each overrides. A calibration rig is a telescope, camera, frame size and binning, as the calibration library records it. Each name opens that rig's settings under Settings › Processing › Calibration, and the note above Calibration's rig list links back here.

Review each rig's field of view, pixel scale and calibration settings.
Review each rig's field of view, pixel scale and calibration settings.

Rig setup

The selected rig's header stays above its setup. Choose a section from the sidebar on a desktop or the tabs on a narrow screen: Optics, Site, Limits and delivery, Weather and Collaboration. Edits stay in the form while you switch sections or collapse the setup; Save rig profile saves them, and Unsaved changes appears beside it until you save.

If you close Settings with unsaved changes, choose Keep editing or Close without saving. This applies to Done, × and clicking outside the dialog. The browser also asks before reloading a page with unsaved changes.

The rig's sensor and optics determine its field of view and pixel scale.
The rig's sensor and optics determine its field of view and pixel scale.

Optics

Under Optics, enter the unbinned sensor size in pixels, pixel size in micrometres, effective focal length and aperture in millimetres, and how the camera angle changes: a rotator, turned by hand between sessions, or fixed. The field of view and pixel scale update as you type.

Use frame headers copies sensor size, pixel size, focal length, aperture and site from the newest frame the server can find. The form shows the source file. Headers from N.I.N.A. record binned values; PSF Guard converts them to unbinned sensor values. Each section shows the source of its values: frame headers, set by hand, or reported by the plugin.

Sites and horizons

A site defines a location (latitude, east-positive longitude, elevation) and a horizon. Add and edit sites under Settings › Presets › Sites. Each rig picks its Planning site and takes the site's location and horizon, unless its own fields say otherwise: a location typed into the rig, or a horizon pasted there or reported by the plugin.

A horizon is a N.I.N.A. .hrz file: one azimuth altitude pair per line in degrees, # for comments. Paste or upload it, and download it back for N.I.N.A. PSF Guard sorts the points and closes the curve at north. It refuses a line that is not two numbers, an azimuth outside 0–360, an altitude outside −90–90, or a repeated azimuth, and identifies the invalid line.

Visibility, feasibility and the program sent to the plugin all use the resolved location and horizon. A rig with neither has no location, and its horizon is flat at its minimum altitude.

Opening another site keeps the edits of the one you left; Save site saves them, with Unsaved changes beside it until then.

A site can use a pasted horizon. This example has no coordinates and was not saved.
A site can use a pasted horizon. This example has no coordinates and was not saved.
Set the rig's planning site and horizon. Coordinates are blank in this example.
Set the rig's planning site and horizon. Coordinates are blank in this example.

Limits and delivery

Limits and delivery contains the altitude and meridian limits planning uses, the rig's Target Scheduler scheduling limits, and Remote site.

The rig's Target Scheduler limits also reach projects outside a saved plan, such as ones made in N.I.N.A. Below the fields, Target Scheduler projects compares the saved limits with every project in the rig's database and lists each one that differs, with what will change. Save the rig profile first; Apply to N projects then writes them, and sends the rows to the rig's remote site when it has one. A plan's own limits still win for its project. Apply is refused when a project or the limits changed since the list was read. Nothing applies by itself; a project made later waits for the next Apply.

Planning limits and Target Scheduler limits have separate controls.
Planning limits and Target Scheduler limits have separate controls.
Check existing projects and choose where to send plans. No remote peer is configured here.
Check existing projects and choose where to send plans. No remote peer is configured here.

Remote site

When the rig runs on another PSF Guard, set Plans push to, under Remote site, to the Sync peer that holds the rig's real database. Activation then pushes the plan to that peer. Leave it at This server only when N.I.N.A. writes this server's database. See Rigs at another site.

When a site misses an activation

A remote site can miss an activation: it was offline at Activate, the push failed, or it has not run yet. The plan then reads Needs activating even when the rows here match it, and says why, here for a site named observatory-pi:

The bar and the activation dialog offer Send to observatory-pi again (without "again" before a first try). The dialog lists each such rig with the error and when it was tried. Neither shows the button once every site has the activation.

The server also sends it on its own once the site answers: a successful Test connection under Settings › Sync, a sync with that peer other than a pull that writes, or another push that reaches it. It sends only the latest activation of each plan, never one the site already applied. A pull that writes does not send, since the site's rows may have replaced the ones here; the plan may then ask to be activated again first. The server log records what it sent and what failed.

Live

Open Rigs › Live for reports from rigs running the Director plugin. The header's Rigs control opens this view and shows the fleet's status. The Tonight column links each rig to its predicted schedule on Nights.

On the Sky, each reporting rig is drawn on the coverage map where it points now. A list of rigs sits beside the map; choosing one turns the map to it. A quiet rig is drawn dashed red. A rig that reports no mount position is placed at its planned target, dotted and labeled at target.

Rigs Live with five rigs and Tonight links.
None of these five rigs has reported yet. Tonight links open the available schedules.

The Live table has one row per rig:

ColumnShows
LinkOnline within three minutes of any plugin call, Quiet within thirty, Offline beyond, Never seen before the first.
NowPhase, target, current operation and how long, wait reason, safety, queue depth and errors, from the last status report. A report older than its stated lifetime is marked stale.
WeatherN.I.N.A. reported weather and the site's forecast, shown separately with missing or stale data marked.
Program pullTime since the rig last pulled its program, with the revision when available.
Check-inTime since the rig last checked in, plus saved frames awaiting grading.
Status reportTime since the rig last reported status.
AssignedActivated plans assigned to the rig, linked to their workspaces.
TonightThe rig's predicted night schedule, with a link to open it.

The table refreshes every fifteen seconds. A read-only account cannot open Settings, so Rigs › Live shows rig setup and the template library read only under the table.

Check a rig's weather

Plugin update required. 0.13 includes server support for weather reports and optional holds between exposures. The published Director 0.1.0.3 Beta 1 does not include these controls; weather reporting and holds need a later plugin update.
  1. Open Rigs › Live to compare NINA reported weather and the site's Forecast.
  2. Open the rig's Weather tab for supported readings and forecast details.
  3. Expand Reported weather history (24 hours) for earlier reports once a compatible plugin sends them.

Missing readings stay blank. Refresh weather reads the server's cached data; it does not request a fresh forecast from the provider. N.I.N.A.'s source can be a sensor or a weather service. Reports do not change image grades.

With the later plugin update, enable Send NINA weather telemetry to PSF Guard in its settings to send readings. To use weather holds:

  1. Open Director Session › Session › Weather and roof.
  2. Choose Hold and resume.
  3. Enable Use PSF Guard site forecast, Use NINA reported cloud cover, or both. Both are off by default.

Every selected source must be fresh and clear before imaging can resume. Forecast holds use the site's cloud threshold and optional dew limit, including a paid source configured on the server. Missing cloud values, gaps, stale data or a forecast for the wrong location cannot clear a hold. Check the Weather tab for the problem and the rig's Site tab for its planning site and coordinates.

A weather hold lets the current exposure finish saving. The physical safety monitor and enclosure interlocks still govern immediate interruption and safe shutdown. See the weather timing and recovery limits.

Plan each rig's nights

Early beta. Open Rigs › Nights to compare your rigs across 7, 14 or 31 nights. Each rig needs a site. Choose From for a starting date or Tonight for the current observing night. Each cell shows clear dark hours, the Moon and the plans the rig would shoot. A red cell has no clear dark hours, even if the forecast leaves daylight hours clear.

The grid groups rigs whose sites are within one degree in latitude and longitude. Each group has Cloud, Dew and Moon bars. A red edge marks hours above the cloud threshold or at or within the dew limit. Brighter dew shading means a smaller gap between air temperature and dew point; brighter Moon shading means a higher or more fully lit Moon. Hover for details. A group without a forecast has no cloud or dew bar; a forecast without dew point data has no dew bar.

Each filter run shows the minimum separation between the Moon and its target. The angle is dimmed when the Moon stays below the horizon. Select a block to see each filter's minimum Moon separation and highest Moon altitude. The Moon strip below the weather bands shows its rise, highest point and set.

Select a cell to open its schedule. Choose a target block to see why Target Scheduler or Director would select it. Not this night lists excluded targets and their reasons. Tonight's schedule starts from now. Future-night schedules account for frames planned on earlier nights. Times include estimated overheads and are predictions, not a guarantee of what the rig will capture.

Updated shows when the displayed plans were computed. The server saves those plans and refreshes them when their inputs change. Compute again requests a fresh calculation, shown in the header's job list.

Two rigs with Cloud, Dew and Moon bars below their night plans.
November 4–10, 2026, from left to right. The drop on November 9 marks a night shortened by the dew limit. Site coordinates are outside the crop.
RedCat night schedule with IC 447 selected, filter Moon angles and excluded targets.
The November 4 schedule shows why IC 447 was selected, each filter’s minimum Moon separation and targets excluded from this night.

Mark available hours

With editor access, select a night and use Mark this night. Choose Available, Not available or Limited. For limited hours, a blank From starts at dusk and a blank To ends at dawn. Under For, choose one rig or every rig at its site, then click Save mark. Shift-click another night in the same rig's row to mark a range.

Set the site's Time zone in Settings › Presets › Sites. Without one, entry times use the browser's zone; the form shows the zone in use. A rig is available only during hours allowed by both its own mark and the site's availability. Clear mark removes the manual mark; a site forecast can still apply.

Marks change planning estimates only. Forecasts also change estimates by default; optional Director weather holds need a separate opt-in and a later plugin update. N.I.N.A. and the rig's safety monitor still control acquisition.

Use cloud and dew forecasts

Open Settings › Presets › Sites and click Edit for a site with latitude and longitude. Under Weather forecast → Forecast, choose Open-Meteo or MET Norway. Set Clear at or under to the maximum cloud cover, in percent, that counts as clear (30% by default).

To exclude hours close to the dew point, set No imaging within to a whole number from 0 to 20 °C. For example, 2 °C excludes hours when air temperature is 2 °C or less above the dew point. Leave the field blank to ignore dew. If the forecast lacks temperature or dew point for an hour, only cloud cover counts. Click Save site.

By default, No imaging within changes planning estimates only. With a compatible plugin update, a Director Session can also use this limit for optional weather holds. Forecasts do not confirm dew on your equipment or replace the observatory's safety monitor and enclosure interlocks.

Weather forecast settings with Open-Meteo, a 30% cloud threshold and a 2 °C dew limit.
This site excludes hours above 30% cloud cover or within 2 °C of the dew point. Receipt, coverage and expiry times show when the forecast can restrict planning.

Forecasts are off by default. Enabling one sends the site's coordinates, rounded to about 1 km, to the provider. The server requests updates every three hours. If a site has a dew limit but its stored forecast lacks dew points, the server requests an update after 30 minutes, subject to the provider's retry time. Fetch now requests an update subject to the displayed retry time. A manual site mark overrides the forecast for that night; a rig's own mark still applies.

The grid uses a cloud icon when cloud cover removes dark hours from a plan, and a drop when the dew limit removes hours that pass the cloud threshold. Both icons appear when both limits remove hours. A cloud icon also identifies a forecast that leaves all dark hours clear. The timeline shows hourly cloud and dew bands; its legend lists hours excluded by each limit. Hover a dew hour for temperature, dew point and humidity.

Night plans use a forecast for 12 hours after receipt. After it expires, or beyond its covered dates, the forecast no longer restricts availability: those hours count as clear for planning, not as a prediction of clear weather.

November 9 night schedule with clear hours ending at 4 AM and a dew limit from 4 AM to 7 AM.
The 2 °C dew limit ends this night's clear hours at 4 AM. Cloud cover stays within the 30% threshold throughout the night.

Override a Director rig's night

Mode in rig setup chooses whether Target Scheduler or Director runs the rig. Until set, PSF Guard infers the mode from reports; pairing Director sets it to Director.

For a Director rig, click Edit night. Drag a block to move it, or select it and use the arrow keys in 15-minute steps. Moving a block pins the target at its new time and prevents it from running during the original time slot. The block menu also offers pins and exclusions. Drag a pin's edges to change its duration, drag the hold line from the right to hold the rig, or choose Set a plan order.

Review the predicted schedule, then click Save changes or Discard changes. A running session finishes its exposure and follows saved overrides at its next check-in. Overrides only restrict the existing program: they cannot relax altitude, Moon or meridian limits. They expire at the end of the observing night, at noon. Another editor's conflicting save requires reloading the night.

Change Target Scheduler priorities

For a Target Scheduler rig, expand Target Scheduler settings and click Change settings. Set projects or targets active or inactive, or change a project's Priority. The schedule previews the changes before you click Save changes.

Saving requires editor access and a server with database management enabled. PSF Guard updates the rig's database and, for a synced catalog, its Target Scheduler file too. These changes apply to every night until changed again. Only projects in the rig's N.I.N.A. profile are edited. If another edit changed a row after you loaded it, PSF Guard refuses to save that row and explains the conflict.

If PSF Guard updates the rig database but cannot write the Target Scheduler file, the panel explains the failure. Use Sync → Data Transfer → Send planning to send the saved change. If the files disagree before saving, review them in Data Transfer: Merge databases uses Target Scheduler's settings, while Send planning sends the rig database's settings.

Try the Director plugin (early beta)

Director capture is in early beta. Target Scheduler with the PSF Guard Sync plugin is the recommended way to run a rig.

A paired Director plugin pulls its rig's program from the last activation over HTTP, keeps running on it through a network outage, checks in each saved frame, and reports live status. Saved frames count as pending credit until grading accepts them; a receipt is evidence a frame was taken, not that it passed. Pairing uses one-use codes an operator issues over the API; there is no pairing screen yet. Pairing does not start a sequence or grant equipment control. The Director plugin is separate from PSF Guard Sync, which transfers database changes and image files.

Without the plugin, activation still writes ordinary Target Scheduler rows, and the Target Scheduler plugin runs them as before.

More projects from theatr.us