I could have something wrong in the FOV calculation, I will check. One question about this for ASTAP though. Should the FOV be the width, the height, or an average? I ask because it isn’t a range like for astrometry.net

So if you click one of the parallel solvers profiles that I made, it is set to auto algorithm if it doesn’t have position or scale, it tries to do a range of scales. If it has scale and it doesn’t have position it tries to do a range of depths. If it has position and not scale it does a range of scales.

One point that might be confusing is that if you are downsampling, the pixel scale in app could be doubled

Thanks for making the new version of ASTAP, I will check it out.

I'm not using the xyls option for ASTAP anymore. Your message bout this earlier made me realize there was a much better way to achieve what I was trying to do.

Oh Han,

About this note on your website for the MacOS download: "If MacOS doesn't allow to install, go to Apple Icon, System preferences, Security & Privacy and allow astap.pkg to be installed. "

I usually find that the best way, at least for me, is to right click on the installer, click open in the contextual menu that pops up, and then click the Open button when the warning pops up.

The image height in degrees should be specified for -fov

oh ok, I had that backwards, I was doing the width

I just added INT SEP EXT ASTAP. I added the data table to the existing fits image (a copy in the temp directory of course). It does solve because it has the image data in there too. And the table loads in astap.

You can try to implement enhanced solving with the sextractor table now

I think I just corrected the FOV, you can check it out in the latest GIT

No problem. Today.
Do you have Windows executable for me?. The last one seems to be made 23 hours ago.

Cheers, Han

That is correct the last release with binaries was made last night. Right now it is around 2 am here so I will have to do it first thing tomorrow

No problem I will work on it. Any more columns except X and Y?

The version 0.9.363 is ready for Linux and Windows:

www.hnsky.org/astap_setup.exe
www.hnsky.org/astap_amd64.deb

The Mac version is more difficult to compile so has to wait.

The program reads the first to columns. The first should be X, the second Y. There is no check on the column names. The format could be either 4 or 8 byte float. Other columns are ignored for solving.
The stars should be the BRIGHTEST stars in the image. For this I normally use the SNR (signal to noise) value since the background can vary. There is no need to sort the stars.

As soon the image contains an valid table extension it will use that extension table for solving. No parameters required. Only a simple message will indicate the table is used:



I have created one test image containing an image and a X,Y table based on the brightest stars. Solving is lightning fast since normally maybe 2 seconds are required for the extractor :

ufile.io/t5qzzh8h

Han