Skip to content

FAQ

It is an alternative for the plate-solving step: a small, self-contained program that fetches its own catalogues, runs on Windows, macOS and Linux, and is open source under the MIT licence. It takes the same options and writes the same files as ASTAP’s command-line solver, so trying it in N.I.N.A. means changing one path, and changing it back is just as easy. On our test images it solves more fields than ASTAP, faster and with slightly better accuracy at the corners: see arcsec compared with ASTAP.

Only ASTAP’s command-line solver, astap_cli. ASTAP is also an image viewer, stacker and photometry tool, and arcsec does none of that. If you use those parts of ASTAP, keep it; the two can share one set of star databases.

arcsec is an independent program. It is built on the star-pattern method Han Kleijn published for ASTAP and reads ASTAP’s database files, but contains no ASTAP code and is not affiliated with the ASTAP project.

Typically well under a second per image: a median of 0.10–0.15 seconds across the test images, about half the time ASTAP took on the same images. A blind solve with the index takes a second or two. See arcsec compared with ASTAP.

Only to download catalogues with arcsec catalog install. Solving is entirely offline, and arcsec sends nothing anywhere.

It depends on your field of view. The Which catalogue do I need? page works it out from your focal length and camera. For most telescopes it is one of the D-series; camera lenses need g05, and all-sky lenses w08.

In a per-user folder that the solver searches automatically:

Platform Default folder
Linux ~/.local/share/arcsec/catalogs (or under $XDG_DATA_HOME)
macOS ~/Library/Application Support/arcsec/catalogs
Windows %LOCALAPPDATA%\arcsec\catalogs

arcsec catalog path prints it, and the ARCSEC_CATALOG_DIR environment variable moves it. See where they are stored.

Can I use the star databases I already have for ASTAP?

Section titled “Can I use the star databases I already have for ASTAP?”

Yes. Set ARCSEC_CATALOG_DIR to ASTAP’s database folder, or pass it with -d. arcsec reads ASTAP’s .1476, .290 and .001 files directly and never modifies them. See sharing with ASTAP.

Yes. Installing a solving catalogue also builds arcsec’s blind index from it, with nothing more to download, and with that arcsec finds a field anywhere on the sky in a second or two:

Terminal window
arcsec -f image.fits -i "$(arcsec catalog path)"

It does not even need the field size: without --fov or FOCALLEN and XPIXSZ in the header it tries pixel scales from 0.3″ to 60″. A wide search (-r of 10° or more, as N.I.N.A.’s blind solve sends) uses the index without -i. If your catalogues were installed before arcsec built the index, or are ASTAP’s, run arcsec catalog index build once; arcsec catalog list shows whether you have one.

The index covers fields from 0.3° up by default; add --index-min-fov 0.15 when you install D80 for narrower ones. Astrometry.net index files (arcsec catalog install anet-4100) also work with -i, but are slower and find fewer fields.

Why does installing a catalogue build an index, and can I skip it?

Section titled “Why does installing a catalogue build an index, and can I skip it?”

The blind index is what makes solving with no position (and N.I.N.A.’s blind mode) take seconds instead of minutes, and it can only be built from a catalogue you have. arcsec catalog install says what it will cost before it starts (about 287 MB, half a minute and 0.6 GB of memory for D50 on a desktop) and asks about a larger build separately. --no-index skips it, and arcsec catalog remove takes it away with the catalogue.

FITS, XISF (PixInsight) and ASDF (used by the Roman telescope and astropy), and JPEG, PNG and TIFF. The format is recognised from the file’s contents, not its name. Compressed FITS is read directly in gzip (.fits.gz), bzip2 and Unix compress (.Z) form. Colour images are averaged to greyscale for solving.

JPEG, PNG and TIFF files say nothing arcsec can use about where the camera pointed or its pixel scale, so pass --ra and --spd (or install a blind index) and preferably --fov. As in ASTAP, the solution’s pixel 1,1 is the picture’s bottom-left corner, the FITS convention. Camera raw files (CR2, NEF, ARW, …) are not read; convert them to FITS or TIFF first.

N.I.N.A. and SharpCap have been tested: set arcsec as their ASTAP solver. Other programs that run ASTAP’s command-line solver may work too, since arcsec takes the same options and writes the same files, but that is untested. If you try one, please report how it went.

Siril has also been tested, in a different way: it has no setting for an external ASTAP solver, so you solve the image with arcsec --update and Siril reads the solution from the FITS header when it opens the file.

Only if you ask for it. By default arcsec fits a linear (TAN) solution, which suits most telescopes. With --sip it also fits third-order distortion terms and writes them to the .wcs file (and the header with --update), but only when the stars show significant distortion across the frame: on an undistorted field extra terms just add noise at the corners. Strongly distorted fields, such as very wide camera lenses, are the hardest case for any linear solve.

An experimental matcher that uses three-star triangles instead of ASTAP-style four-star quads. It solves far fewer images than the default (29 of the 98 solvable benchmark images, against 90) and is not recommended yet.

Prebuilt downloads are available for Windows (x86-64), macOS (Apple silicon) and Linux (x86-64 and arm64, glibc 2.35 or newer). Anywhere else that Rust supports, including Intel Macs, cargo install arcsec builds it from source with Rust 1.96 or newer.

Open an issue on GitHub. For a failed solve, include:

  • the full command line (it is on the CMDLINE= line of the .ini file),
  • the output of the same command run with --progress, or the .log file from --log,
  • the arcsec version (arcsec --version),
  • and the image, if you can share it.

Security problems should be reported privately, as described in the security policy.