SGPro, in 4.4, added formal support for ASTAP, but did not remove support for the older ASTAP implementation that copied the PlateSolve2 communication contract in order to “fake” SGPro compatibility.
In a near future release of SGPro (you’ll have a couple months to do this) we will be officially removing the old ASTAP solver (that works only by pretending to be PlateSolve2) in favor of the “real” ASTAP solver integration.
What does this mean for you, your sequences and profiles?
For users that are using the ASTAP solver labeled ASTAP (native) there is no action required. As a note this solver will soon just be labeled ASTAP and remove the native differentiator text.
For users of the Plate Solver currently labeled ASTAP, you will need to migrate from this solver to the solver named ASTAP (native). Guidance below. If you do not migrate to the newer ASTAP implementation by the time SGPro 4.6 is released (at least a couple months from now). your ASTAP solver will be broken and, as a result, the Chain Solver will not attempt to use it when solving images.
How do I migrate from ASTAP to the ASTAP (native) solver?
Migrating is pretty straightforward and you don’t need to update ASTAP itself (BUT! an important note: if you renamed astap.exe to PlateSolve2.exe without copying astap.exe first, you will need to rename PlateSolve2.exe back to astap.exe first. Aside from this one issue, you can really just set up ASTAP (native) like it’s a new solver in SGPro. Detailed guidance on setting up ASTAP (native) is here: