Where Does ASTAP Store Config and Catalogs?
ASTAP keeps settings in per-OS config files with star databases beside the install. Catalogs range from megabytes to gigabytes.
Last updated
ASTAP pairs a small config with giant catalogs. Settings save per OS in config files while star databases dwarf everything beside the install. Density grades span orders of magnitude for different fields.
Install spots vary by platform with fallback lookup chains on Linux. Catalog choice follows field-of-view rules with auto modes available. NINA integration points at the install tree with both halves required.
Where ASTAP stores this, by platform
%LOCALAPPDATA%\astap\astap.cfg
Settings file with install tree and star catalogs beside it. Density grades from small to huge per field of view. Copy config plus chosen catalogs for migration.
~/.config/astap/astap.cfg
Config under XDG config with program data splitting opt and share trees. Fallback chains resolve databases across prefixes. Same density grades as Windows.
Frequently asked questions
How do I back up ASTAP?
Copy the per-OS config plus the install tree with chosen star catalogs. Windows uses LocalAppData config with Program Files data while Linux splits opt, share and config homes. Mac nests catalogs under its opt tree.
Which ASTAP star catalog do I need?
Match density to field of view from small D05 through huge D80 with photometry and galaxy variants beside them. Auto-selection follows field rules when enabled. One catalog suffices per setup in most cases.
How does ASTAP work with NINA?
Through NINA profiles pointing at the install directory per setup guides. Command-line builds ride alongside with path flags. Integration needs both program and database present.
Notice an outdated path? Let us know.