<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>When I run the StellarSolverTester on my RPi4 8GB, I get the
following alarming log line:</p>
<p>###<br>
</p>
<p>Evaluating Installed RAM for inParallel Option. Total Size of
Index files: 31.7369 GB, Installed RAM: 1.71799e+10 GB<br>
There should be enough RAM to load the indexes in parallel.</p>
<p>###<br>
</p>
<p>Naturally, it bombs out every time out-of-memory except with some
very specific settings.</p>
<p>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...<br>
</p>
<p>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.<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 14/10/2020 18:28, Hy Murveit wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+B1P8vdoOD4rCpMA0tQZobdDtzGWKisviHOFyy_CJjtqxy4Bw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">I'm forwarding an issue I've seen re plate solving
with the latest KStars using stellarsolver.
<div>I did report this to Rob, but on Jasem's suggestion, am
forwarding to Devel also.</div>
<div>I really appreciate the efforts Rob and Jasem are putting
in for this release.</div>
<div><br>
</div>
<div>(Not sure where to report bugs that might block 3.5, other
than this email list)</div>
<div><br>
</div>
<div>The TL;DR is that I cannot successfully plate solve using
the StellarSolver internal methods</div>
<div>on a Raspberry Pi 4 (running Raspberry Pi OS). Lots of
detail below.</div>
<div><br>
</div>
<div>Have others successfully plate solved on a RPi4?</div>
<div><br>
</div>
<div>Hy</div>
<div><br>
</div>
<div>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">-------------------------------------</div>
<div dir="ltr">
<div><br>
</div>
I pulled the latest stellarsolver and kstars, and then
added <a
href="https://invent.kde.org/education/kstars/-/merge_requests/104"
target="_blank" moz-do-not-send="true">your new MR</a>
on top of it, and compiled on my RPi4.
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>I ran these tests. </div>
<div>(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. </div>
<div>(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.</div>
<div>(3) I switched to 'local astrometry'. Seemed to get
the WCS, then quickly fail to solve.</div>
<div>(4) I switched to my old/saved KStars (pre your
changes, no stellarsolver). Worked fine.</div>
<div>(5) Parked, Unparked, repeated #4, still worked.</div>
<div>(6) Went back to the "new Kstars". Retried #3. Still
failed.</div>
<div>(7) Retried #2. Still Succeeded.</div>
<div>(8) Retried #1. Still failed.</div>
<div>(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).</div>
<div><br>
</div>
<div>Hy</div>
<div><br>
</div>
<div>Details:<br>
<br>
<b>Test #1. <br>
Load and Slew, using the same .fits file I shared,
Internal SEP/StellarSolver/4ParallelSmallScale. (load
all in memory is UNchecked).</b><br>
<br>
I got the below (just cut/pasted the bottom logging
window in the align tab).<br>
Honestly, with all the output blowing by, it's hard to
see what happened, but from looking at the cut/paste, I
see
<div>that it looks like it got the WCS position from the
.fit header, slewed, and then failed to solve.</div>
<div>The image on the screen looks reasonable.</div>
<div>(See below, I retried with ASTAP)</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>