I’m running version v3.1.0.457 of SGPro and have experienced the following issue when plate solving.
I’ve been testing the new plate solver ASTAP as well has checking that my change to using the local instance ‘ANSVR ‘ of the Astrometry.net blind solver has worked. The testing has been undertaken due to seeing odd behaviour during my last imaging session whereby:
-
If I initiated a ‘Scope Centering’ | ‘Solve & Sync’ process the new ASTAP utility quickly solved after taken its first plate solve frame, leaving the image in a Plate Solve window.
-
In addition, whenever I right-click action either a ‘Centre Here’ or ‘Plate Solve’ request when the image currently displayed is in a ‘Plate-Solve’ window the ASTAP or local blind solver completes satisfactorily.
-
If instead I took a ‘Frame and Focus’ image at the same location using a known object, followed by a right-click ‘Plate Solve’ using the ASTAP option as well as entering the target object and RA & Dec in the hint fields the process fails to complete. Indeed, on one occasion a division by zero error message was displayed.
To further this investigation, I cleared any old log files so as to run the sequence from a clean starting point. As I was not at my dome, I started SGPro without any equipment connected. Instead, I loaded a previously taken image that contained all the necessary header data to identify image centre, etc. [copy in Dropbox]
- I initiated a right-click ‘Plate Solve’ using the ASTAP option as well as entering the target object given the centre RA & Dec were auto-read from the header in the hint fields. Again, the process failed to complete. And after a while a floating-point division by zero error message was displayed, as shown in the screenshot. [in this One Drive folder. As are copies of the Log file, test image, User and Equipment profiles]
I am running SGPro under Windows 10 Pro with the latest version for both, and have been rebuilding the PC after a drive crash, hence the My User Profile has only limited information in. That said the image being used does contain this data. This of course may be the issue? This is also the first time I’ve changed both the plate solving utilities, so am quite expecting this report to highlight an erroneous setting somewhere that I’ve either made or omitted to make.
Regards
Dave