Issue with Align with StellarSolver

[Giles Coochey]

When I run the StellarSolverTester on my RPi4 8GB, I get the following 
alarming log line:

###

Evaluating Installed RAM for inParallel Option.  Total Size of Index 
files: 31.7369 GB, Installed RAM: 1.71799e+10 GB
There should be enough RAM to load the indexes in parallel.

###

Naturally, it bombs out every time out-of-memory except with some very 
specific settings.

I've never changed Astrometry.net defaults and it completes a solve very 
easily. I'm now inundated with settings, some of which appear to be able 
to crash kstars / stellarsolvertester...

I compiled the latest kstars 3.5.0 after today's commits on my 
Astroberry, but have reverted to Astroberry's packaged 3.4.3 for the 
time being.


On 14/10/2020 18:28, Hy Murveit wrote:
> I'm forwarding an issue I've seen re plate solving with the latest 
> KStars using stellarsolver.
> I did report this to Rob, but on Jasem's suggestion, am forwarding to 
> Devel also.
> I really appreciate the efforts Rob and Jasem are putting in for this 
> release.
>
> (Not sure where to report bugs that might block 3.5, other than this 
> email list)
>
> The TL;DR is that I cannot successfully plate solve using the 
> StellarSolver internal methods
> on a Raspberry Pi 4 (running Raspberry Pi OS). Lots of detail below.
>
> Have others successfully plate solved on a RPi4?
>
> Hy
>
> -------------------------------------
>
> I pulled the latest stellarsolver and kstars, and then added your new 
> MR <https://invent.kde.org/education/kstars/-/merge_requests/104> on 
> top of it, and compiled on my RPi4.
>
> TL;DR With your new code, WCS works, but the only plate solving that 
> works for me is local astap. 'SEP/StellarSolver/4ParallelSmallScale' 
> and switching to 'local astrometry' both fail to solve the captured 
> images. Going to my old KStars with local astrometry works. I tried 
> other .fits files (meaning other locations in the sky) and they also 
> failed.
>
> I ran these tests.
> (1) Load and Slew with your MR 
> and SEP/StellarSolver/4ParallelSmallScale.  This looks like it 
> successfully pulled the WCS info from the file, but the plate solve 
> after slewing failed and stopped.
> (2) I switched to local ASTAP and it worked (e.g. it got the WCS, 
> slewed, then iterated 3 times on image capture and successful plate solve.
> (3) I switched to 'local astrometry'. Seemed to get the WCS, then 
> quickly fail to solve.
> (4) I switched to my old/saved KStars (pre your changes, no 
> stellarsolver). Worked fine.
> (5) Parked, Unparked, repeated #4, still worked.
> (6) Went back to the "new Kstars". Retried #3. Still failed.
> (7) Retried #2. Still Succeeded.
> (8) Retried #1. Still failed.
> (9) I tried #1 with several other fits files. All seemed to load WCS 
> then fail plate solving very quickly. Probably same issue as with #1 
> (I gave you lots of details below).
>
> Hy
>
> Details:
>
> *Test #1.
> Load and Slew, using the same .fits file I shared, Internal 
> SEP/StellarSolver/4ParallelSmallScale. (load all in memory is UNchecked).*
>
> I got the below (just cut/pasted the bottom logging window in the 
> align tab).
> Honestly, with all the output blowing by, it's hard to see what 
> happened, but from looking at the cut/paste, I see
> that it looks like it got the WCS position from the .fit header, 
> slewed, and then failed to solve.
> The image on the screen looks reasonable.
> (See below, I retried with ASTAP)
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20201015/7fc942e3/attachment.htm>