0.14 Release Notes
0.14 overview · 0.13 release notes
PSF Guard 0.14 adds live rig monitoring, clearer plan activation status and seasonal sky visibility. The current release is 0.14.2; see 0.14.2 fixes.
Download: Windows setup EXE · Windows MSI · macOS DMG · Linux AppImage · Debian/Ubuntu package
Start with: Upgrading · Live · Planning · Framing · Processing · Sync
0.14.2
PSF Guard 0.14.2 downloads ONNX Runtime for the Seiza noise model again, and lets you start a plan with no images and add its first rig.
- Download both in Settings › Processing › Stacking and
psf-guard-cli noise-model downloadwork again. Microsoft's GitHub repository for ONNX Runtime has been offline since about 18 November, so the download failed with a 404. PSF Guard now downloads a copy of the same ONNX Runtime 1.31.1 archive from its own GitHub release, checked against the same SHA-256 as before, and tries Microsoft's address second. A source that stops sending for a minute no longer holds the download open. (#1136) - You can start a plan with no images or database from New plan in the Library's toolbar or New plan... at the top of the header's project picker. Create plan opens the plan on Framing with Object name ready for the target. Before, New plan was only at the bottom of the Library, and saving left you in the list. (#1135)
- Rigs and Framing show an Add objective button for a plan with no objectives. A rig joins a plan by shooting its objectives, so Add a rig and the rig switches on Framing stay disabled until the plan has one; before, only a tooltip and a grey line explained why. The new objective starts on a band that a rig or the template library has a template for, so a rig can join. (#1135)
0.14.1
PSF Guard 0.14.1 gives each rig the right exposure templates when rigs share a Target Scheduler database, reads more horizon files, and lets Run now wait for other import work.
- When one Target Scheduler database serves several N.I.N.A. profiles, a rig now offers only its own profile's exposure templates. Before, the plan editor could give a plan another profile's template of the same name, with that profile's gain and exposure, and Copy from on Settings → Presets → Exposure templates listed each name once per profile. Copy from now shows how many templates from other profiles it leaves out. When the library has a template of the same name with other settings, the rig's template is marked differs from the library; click it to replace the library's settings with the rig's. (#1098)
- PSF Guard now reads a N.I.N.A. horizon file that lists one azimuth on several lines, as a file may do to draw the upright edge of a building, in Rig setup and Settings → Presets → Sites. Before, it refused the file. PSF Guard uses the highest altitude listed for that azimuth, so a target must clear every line. (#1126)
- Horizon files are now read as N.I.N.A. reads them in two more ways: commas, semicolons and tabs separate the columns, and when a file has neither 0° nor 360°, both ends get the altitude of the point nearest north. Before, PSF Guard drew a line across north between the last and first points, so its horizon near north could differ from N.I.N.A.'s by a few degrees. A horizon already saved keeps its curve until you paste or upload the file again.
- Run now no longer fails with "an import is already running for this database" while PSF Guard receives a remote upload or finishes other work on the catalog. The run waits for that work and then starts.
- Folders & limits heads each disk with the folder that holds its storage folders, such as
./cache. Before, it showed one database's folder inside the cache, such as./cache/db-e075b4ec, though the disk's use and limit cover every database on it. - Release downloads omit duplicate installers and the extra macOS app ZIP. Windows MSI installers remain available. Update notices keep dotted names such as N.I.N.A. within the first sentence.
Upgrading
- Back up your planning data before updating. After 0.14 upgrades the planning store, older PSF Guard versions cannot open it. Keep a pre-upgrade backup if you may need to return to 0.13. See the backup guide.
- Update stack workers with the server. Stack builds require the same PSF Guard release. Workers on the previous release can still run RC-Astro processing steps, but need 0.14 for remote license checks and the noise model.
- Allow time for stack and master rebuilds. Seiza 0.52 changes the stacking output version from 0.58.0 to 0.59.0. PSF Guard rebuilds stacks and calibration masters when next needed. Saved processing choices remain unchanged; compatible cached processing results are reused. PSF Guard already used quadratic registration, so the new Seiza default should not change those pixels.
- Update the N.I.N.A. plugins for their new features. Detailed Sync sequence status and new-project profile assignment need the matching Sync plugin. Director uploads, replacement flats, transit limits and recovery changes need the matching Director plugin. Director remains early beta. Live monitoring with Target Scheduler and PSF Guard Sync does not require Director.
- Keep SQLite companion files with a running catalog. Local-disk catalogs now use a write-ahead log. The
-waland-shmfiles beside a catalog are part of its active database state. Network-share catalogs keep their previous mode.
Your saved pairings, processing setups and sync connections keep working. Direct access to a Target Scheduler database remains deprecated but supported; 0.14 does not automatically replace it. For a new connection, use Settings › Databases & rigs › New / import to import a local TS file or connect the PSF Guard Sync plugin. If you skipped 0.13, also read its upgrade notes.
Follow your rigs on Live
Open Rigs › Live to see each rig's connection, current activity, weather, plugins, active projects and tonight's predicted work. Target Scheduler rigs appear through PSF Guard Sync, without opening Planning first.
- Now shows the exposure and count, autofocus, slews and waits reported by the updated Sync plugin. It also shows the last frame, dither and autofocus. Old reports are marked stale. A rig with no report is not shown as exposing.
- Plugins lists the plugins that have contacted PSF Guard. Open History for their recent actions and last contact. A failed or refused Sync action stays visible until that same action succeeds; successful uploads do not hide it.
- Projects links to that rig's active projects in the Library.
- Weather separates Observed conditions from the site's Forecast. Freshness no longer flickers when the browser and server clocks differ. Forecast providers are credited below the table.
Sync-reported exposures also count in the header's rig summary, appear on Sky › Live, and show in Night details. Rig polling now uses cached summaries instead of opening each database every 15 seconds.
Live with Sync is a regular monitoring feature. Director acquisition remains an early beta, with warnings on its controls rather than on the entire Live view. Night schedules remain estimates.
Set up both N.I.N.A. plugins in one place
Open a database in Settings › Databases & rigs, then choose Rig setup › Plugins. Separate cards show PSF Guard Sync, Image uploads and PSF Guard Director. Plugins on this rig shows which are on and what each does. Without planning enabled, Rig setup shows only the Sync plugin.
- Pair Sync with Generate Sync pairing code. Each paired client shows its plugin version and last connection; older clients get an explanation when they cannot assign new projects to the open N.I.N.A. profile.
- Scheduler sync and Image uploads have Turn on and Turn off controls that apply immediately. The former combined receive-and-pairing form is gone. The page refreshes when you return to it.
- Both plugins use the same image receive folder, folder layout, import and calibration matching. A Director-only rig can enable uploads without pairing Sync. Director uploads also appear in Live's History.
- Settings › Sync keeps transfers and Target Scheduler sync. Its Open Rig setup link opens plugin setup.
Under Rig setup › Optics › Filters, enter the rig's filter names or copy names from its templates and frames. Planning and activation warn about a filter that the rig does not have. No Director plugin is needed for this check. Rig setup › Weather › Edit site weather opens the site's forecast settings.
Remove is available beside a database and in Rig setup. It permanently deletes rig settings, Director history and pairing, and removes the rig from plans. The database file and images stay on disk. A rig with open work must close that work first; the confirmation dialog lists what will be removed.
Find and activate plans
In the Library, choose Show › Needs activating to find saved plans whose rigs do not have the current plan. Click a plan's Activate button to review its activation preview without leaving the Library.
This includes new plans, saved framing or exposure changes, added rigs, remote sites that missed an activation, and Target Scheduler rows edited in N.I.N.A. Plans imported from Target Scheduler and left unedited are excluded. For plans activated before 0.14, checking for later Target Scheduler changes starts after their next activation.
Plans assigned to a rig with no frames now appear under that database's Plans with nothing captured yet section, even if another rig has captured frames for the same plan. The header's Plans waiting for frames section opens these plans from any page and includes plans without a database.
Database, Show, search and Sort stay in the URL and survive a trip to Planning and back. Opening an unfiltered Library restores the last filters in that browser tab, except when returning to a specific project. The header and the Library's Database filter stay in sync.
A plan can activate on a new rig before any frames or plugin reports arrive. The updated Sync plugin places its project in the N.I.N.A. profile you have open on the next pull. Older plugins use the last reported profile. Pair each N.I.N.A. profile with its own PSF Guard database. Activation also tolerates leftover rows from deleted projects without failing a foreign-key check.
See which sky your rig can reach
In Planning › Framing, use Sky in view to check the rig's horizon and altitude limits before choosing a target. Open Time range and overlay key to set a minimum uninterrupted time above those limits while the Sun is more than 12° below the horizon.
- Now covers tonight and the next 30 nights.
- Year shows sky available on at least seven nights over the coming year; those nights need not be consecutive.
- Season shows a 31-night window. Drag Time of year to compare seasons.
Shading marks sky that falls short of the selected period's threshold; hatching marks sky never in view. The solid line marks the threshold and the dashed line marks sky reachable on at least one night. Year estimates the nights between weekly samples; its boundary is within about 1° of a calculation using every night. Season follows the coarser 2° grid. These are visibility estimates, not weather predictions or proof of captured coverage.
Install offline sky maps
Open Settings › Storage & backups › Offline sky maps. Choose one of N.I.N.A.'s three whole-sky image sets by size and license, then click Install. PSF Guard checks the download's size and SHA-256 before installing it. Progress appears in Settings and the job list, where Stop cancels the job. Nothing downloads until you ask, including the first-use offer in Framing.
Maps now live outside the cache, so clearing or moving the cache leaves them in place. Older maps still work; use Move to move one out of the cache. Remove deletes the selected map's files. The CLI installs into the same folder with psf-guard sky-maps install; use --dir instead of --cache-dir.
Choose processing tools
Stack processing groups tools under Sharpening, Noise reduction and Star removal. A single available provider has a checkbox. Where several are available, choose Off or a provider.
The new Seiza noise model needs no RC-Astro license. Adjust Grain and Mottle to control noise reduction. To install its model and ONNX Runtime, open Settings › Processing › Stacking › Processing tools and click Download both. Neither is bundled or downloaded automatically. You can instead enter the path to an ONNX Runtime you installed.
On a worker, run psf-guard-cli noise-model download, or use Download noise model in the desktop app's Worker on this computer, then restart the worker. The server sends processing only to a worker with the matching provider version. CPU processing of a 60-megapixel stack can take tens of minutes.
Settings › Performance › Workers › Where work runs now calls the policy Processing steps, replacing RC-Astro tools. It preserves your selection and applies to every provider.
Find RC-Astro and check its license
The desktop app and workers now find RC-Astro in its installer folders, including /Applications/RC-Astro/CLI and C:\Program Files\RC-Astro\CLI, even when those folders are absent from PATH.
Check license, under Processing tools or on a worker row, requests the current RC-Astro license report. It identifies the computer and operating-system account, the registered RC-Astro account, product status and any command needed to resolve a problem. It does not activate or deactivate licenses. Online checks run only when requested. The CLI equivalent is psf-guard-cli rc-astro license.
On Windows, psf-guard-cli worker-service install now installs the service under your Windows account so it can use your RC-Astro license and network shares. It checks your password first. Reinstalling an older service moves it from the virtual account and removes that account's old access, task files and profile. After changing your password, run the command with --new-password. Use --account NAME for another account or --virtual-account for the former service account.
Connect and maintain catalogs
Pair another PSF Guard server
On the receiving server, open Settings › Sync › Other PSF Guard servers and click Generate server pairing code. On the sending server, choose Remote PSF Guard › Add peer and enter the URL and code. Each peer gets its own credential. The receiver lists pairing dates and last syncs; Remove revokes one peer without disconnecting the others.
Existing peers using a Remote API key keep working. That key now lives in Other PSF Guard servers, with its last use and Remove key control. Server sync has its own switch, separate from the plugin's Scheduler sync. Where scheduler sync was enabled, both switches start enabled. New plugin pairings enable only plugin sync; server pairings enable only server sync.
Merge repeated catalog records
Merge imported copies joins frames imported separately from their Target Scheduler records. It keeps the Target Scheduler record, project, target and exposure plan so acquired and accepted counts do not drop. It can take a copy's grade when the retained record has none. Empty projects created by the import are removed unless active or used by a Director plan.
Merge renamed lights now handles several old-name records and targets renamed in N.I.N.A. It keeps Target Scheduler's record where available, otherwise the record in the renamed file's target. The retained record gets the new path and compatible grades; sync does not recreate the removed copies. Matching across renamed targets also requires the recorded airmass and focuser position to agree.
Conflicting grades prevent a merge until you resolve them. The merge backs up the database and refuses to apply a stale preview. New imports and sync also recognize these cases to avoid creating more copies.
Send planning and Pull planning transfer only exposure templates used by the plans. An identical destination template can adopt the source GUID; one that differs in any setting is preserved. Repeated identical templates within a N.I.N.A. profile are merged during a planning write, with their exposure plans retained. The preview counts the merged copies. Affected Director plans may show Needs activating once.
Local-disk catalogs now allow reads alongside writes, reducing delays during grading, imports and Sync. Reading the planning store during a write no longer produces a false corruption error.
Improve calibration and night planning
When all external flat masters exceed the Flat age limit, a night with its own raw flats now builds a master from those flats. An external master within the limit still takes priority under Whenever one matches.
Calibration › Flat coverage, formerly Scheduler flats, lists Director batches alongside Target Scheduler batches. Invalidating a suspect batch asks for replacement flats while keeping its image files. Director support requires the matching plugin's Director Flats feature, including flats for plans whose light frames are complete.
Rigs › Nights, Night details and Live's Tonight load faster by reusing each night's sky calculations. In the measured four-rig example, a cached week fell from about 11 seconds to 0.5 seconds and a month from 45 seconds to 1.5 seconds. The first request takes longer. The predicted schedules are unchanged. Director estimates count only activated plans and show Full when overlapping targets fill the night.
Try Director acquisition — early beta
Target Scheduler with PSF Guard Sync remains the main way to run a rig. The Director plugin is an optional early beta. Pair it and manage its equipment, work permission and session under Rig setup › Plugins.
- Sync and Director can remain paired together. Changing the rig's Mode preserves pairings, accepted equipment and work permission. Pairing Director does not switch a Target Scheduler rig's mode.
- Equipment reports apply automatically without resetting work permission or selected plans. Only a plugin permitted to take work updates the equipment.
- Templates with gain or offset
-1use the camera defaults reported by the updated plugin. For a database with several N.I.N.A. profiles, Director uses the profile reported by its plugin. - The Plugins tab explains why work is off or no activated plan can run. Updated plugins retire interrupted assignments after confirming idle equipment; new work uses current image counts. Saved images and receipts remain available. Close work recovers work held by a removed plugin; previously reported attempts remain spent.
- A plan can set separate transit-avoidance minutes before and after transit. Blank inherits the default; zero disables that side. N.I.N.A. meridian flips remain separate.
- Local safety and recovery checks tolerate clock offsets between the rig and server. Assignment windows still follow the server clock; safety freshness and shutdown deadlines keep their limits.
See Director setup and limits for the complete workflow and plugin requirements.