Re: APPM and Pinpoint
I looked at the APPM log file, and it doesn’t have any additional information as to what happened with the plate solve. Actually, it considers the solve successful, which it was not (unless success is defined as “done”). Here is an excerpt:
0000034 2018-03-03 09:06:18.360: Info, PinPoint Test Solve, File = C:\Users\wadeh\Desktop\Cone-1x1800-Ha.fit
0000035 2018-03-03 09:06:18.360: Info, PinPoint Test Solve, RA/Dec = 6.66811666666667 / 9.64386944444444
0000036 2018-03-03 09:06:18.360: Info, PinPoint Test Solve, Use FITS for Hints = True, X/Y Scale = 1.62 / 1.62
0000037 2018-03-03 09:06:18.360: Info, PinPoint Test Solve, AllSky = False
0000038 2018-03-03 09:06:18.360: Info, PinPoint Test Solve, Timeout = 120
0000039 2018-03-03 09:08:27.650: Info, PinPoint Test Solve, Solve Successful
0000040 2018-03-03 09:08:31.421: Exception, Plate Solving, User Clicked Cancel or Close
Regarding a sample image, I don’t have a Dropbox account, but you can download a FITS file from https://www.faintfuzzy.net/2018/cone-1x1800-ha.fit. This is a wide field setup, so there are lots of stars. To solve it efficiently in Visual Pinpoint with USNO A2.0, I am using Min sigma of 8 and Max magnitude of 10. This one took 22 seconds when I tried it right now. My 2x2 binned images off the same system take about 5 or 6 seconds. Here is the output from Visual Pinpoint for this image and the above settings:
Plate-solve run at 3/3/2018 11:07:45 AM
Use File/Save As to save this file
3751 image stars found.
(doing spiral search...)
172 catalog stars found.
Solved using 50 of max 500, RMS residual is 0.50 arcsec, order =4
Solution took 22.8 seconds
Centerpoint RA = 06h 41m 03.766s Dec = 09° 37' 25.91"
Pointing error 0.3 arc minutes
WCS: Roll = -0.48 HScale = -1.622 VScale = -1.623
PA = 0.485°
FWHM = 6.39 arcsec
ZeroPoint = 16.44 (1 sec.)
From: ap-gto@... [mailto:ap-gto@...]
Sent: Saturday, March 3, 2018 10:38 AM
Subject: RE: [ap-gto] APPM and Pinpoint
Is there any way to get either a more complete error message, or enable logging to get more details as to the progress of the attempt?Yes, you can look at the APPM log file.
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro: <http://www.ccdware.com/> http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com <http://www.pulseguide.com/>
Author of Sigma: http://www..gralak.com/sigma <http://www.gralak.com/sigma>
From: ap-gto@... [mailto:ap-gto@...]
Sent: Saturday, March 3, 2018 9:49 AM
Subject: [ap-gto] APPM and Pinpoint
I am using APCC Pro (version 22.214.171.124) and have been using Pinpoint v6 as the plate solver for APPM. This has been working reasonably well for me with the GSC 1.1 catalog. Still, I do get some occasional plate solve failures, perhaps about 5% of the time. I have had it on my "to do" list for a while to switch to the USNO A2.0 catalog, and today is the day that I'm playing with it.
The problem that I am having is that APPM's Image Link Test fails all attempts at solving with this catalog.
Prior to testing with APPM, I worked with Visual Pinpoint to verify that the catalog works correctly. It is able to solve my test images in about 5 to 6 seconds. To get it working efficiently, I needed to tune the Min Sigma and Max Magnitude settings in Visual Pinpoint.
< p>I have matched these settings in the Sigma Above Mean and Catalog Max Mag settings in APPM. I have also verified that the coordinates and image scale from the FITS headers are correct when Image Link Test reports them.
The issue is that Image Link Test times out nearly 100% of the time on my test images. I bumped the Max Solve Time up to 120 seconds and it still times out. I have seen a couple of tests fail at about the 90 second point with an error that no stars were matched.
Is there any way to get either a more complete error message, or enable logging to get more details as to the progress of the attempt? In particular, Visual Pinpoint reports the number of image stars detected and the number of catalog stars found on both failed and successful solves. This would be very valuable information in troubleshooting this.
I'm also open to any other suggestions.
[Non-text portions of this message have been removed]