rlancaste wrote: I'm confused by your statement about the fov. I recently added the option for fov to the ASTAP command, and it is based upon the scale information in the image just like in astrometry.net. So if you have the scale information in your image, it attempts to use that whenever you have "use scale" selected. If you don't want to use the scale, you don't have to. This isn't saved in the profile. It is definitely not always set to 1.7478 degrees. I expected that if the scale information is saved in the fits file, then setting the fov based on this information would speed up the solve. Is that not correct? If you load a jpeg image, it doesn't have the scaling information in it, so it should not even send the fov parameter to ASTAP at all. Did it try to set the fov when you loaded a jpeg?
RDBeck wrote: I'm happy to help, Rob. I duplicated your results for Han's M13, but it took my machine 1.08s to solve it .
rlancaste wrote: For INT SEP, EXT ASTAP, I will work on that later tonight. I will add the option to the code and set it up to export a file that could then be solved by ASTAP. I will include a warning that this function is not yet implemented in ASTAP, but it will try to do it anyway. That way you can try it out and test your new version of ASTAP so that you can see if it works. I will try to follow the guidelines you have set for how you would like to receive the file as input.