@rbarberac
Hey, if you have some sample images I could look at, that would be nice - theoretically small rings could work out just fine. The Watney built-in algorithm fairly crude, but works

- Jussi

ROB LANCASTER WROTE:
"I think the issue is just the stable version because the stable PPA is building the old version of KStars that doesn't have the kstars updates to use the new StellarSolver API that I added yesterday. "

Exactly. It's a mismatch in the ubuntu ppa between the "stable" Kstars and StellarSolver.

I was on stable Kstars ppa but my stellarsolver updated anyway and killed Kstars completely.

Once I updated to Kstars nightly ppa, I can run again.

But there's no point to having a "stable" Kstars that can't run!

Not at hand right now. Next clear night I'll generate some of them

Jussi, Saarvirta, please check to see that this fixes what you were observing in terms of the typos, file paths, and tooltips:

invent.kde.org/education/kstars/-/merge_requests/559/diffs

Also this change
github.com/rlancaste/stellarsolver/commi...f5dc91ee4807221ece80

Paolo,  here is the patch I made for 3.5.7.  Please test and make sure it works ok for you. 

Note that I did have to change the file extension to .txt  It should be .patch

Jussi, please check that this helps the detected crash in KStars if INDI gets disconnected while running Watney or ASTAP.  I believe what was happening was that StellarSolver was logging that it was aborting when it was getting deleted, but KStars hadn't disconnected it from the object it had been logging to, but the object it was logging to had already been deleted, so it was logging to a non-existent object.  There really is no need for any logging if it is getting deleted, so I think this is a good solution.

github.com/rlancaste/stellarsolver/commi...b7d6d1f78792a6e27089

 

Right, so the crashes are solved. I haven't really found anything after that. Just very, very minor details: in KStars, the tooltip for both Watney solver and ASTAP solver reads 'Astrometry.net solve-field binary'

Wait, I could swear I fixed that a couple of days ago. Note this change here:  github.com/KDE/kstars/commit/961575df986...4c4b0f403b84c9c2ce1d
Are you using the latest KStars from GIT master?  

github.com/KDE/kstars
or
invent.kde.org/education/kstars

Oh you're probably right! My bad... I must have forgot to pull before I started testing.

With regards to detecting out of focus donut stars. I had thoughts about whether it would be more robust if two star detection passes with different algorithms could be employed. One algorithm tailored to large FWHM donut star shape; then switch to a reliable point like star algorithm such as gaussian when donuts are not detected.