Raspberry Pi 4 Memory
Apparently 64-bit Raspberry Pi OS is a thing . The forum post seems quite old and has no mention of it going out of beta, but the latest build is as recent as August of last year.

I might give it a go to see if I can build everything against it to squeeze that extra memory into userland processes. Hopefully it doesn't wind up being a waste of time...!



Use FITS Viewer Setting

At the risk of misunderstanding the way things work, I had a dive into the KStars source last night.
On Line 6298 of kstars/ekos/capture/capture.cpp , I found the following chunk (some bits removed for brevity):

// Check if we need to do flat field slope calculation if the user specified a desired ADU value
if( ..... ) {
    if (Options::useFITSViewer() == false)
    {
        Options::setUseFITSViewer(true);
        qCInfo(KSTARS_EKOS_CAPTURE) << "Enabling FITS Viewer...";
    }
    ....

So it appears that the "Use FITS Viewer" option is intentionally automatically enabled by the application.

At the risk of severely misunderstanding the reasons behind this operation, I can only assume that this is *required* in order for the software to process/gain access to the flat frames that are being captured, or the features of the software that allow it to perform operations against the captured flat frames (e.g., calculation of ADU peaks, and so on?)

If that block of code is literally just there to show the flats as they are being captured, can it just be removed? I suggest this change as the application currently alters the user-configured options without "consent", and also does not restore the state after it is done.

I don't really know anything about the internals of KStars so if anyone has anything to add on this front it would be appreciated!

Read More...