I started seeing the following problem in Kstars focusing module recenlty - the FHD of the star is measured as integer value - 1 for focused star and 2 for defocused star. I am seeing this only recently, within couple of months. Also it seems that the problem comes and goes. Has anyone noticed this?

Alex

I had a quick imaging session this night and again saw this issue. Kstars version is 3.3.6, running on RPi 4. The easiest way to reproduce the issue is to select one star for focusing.

FWIW, I tried to reproduce what you said and I couldn't. Seemed fine.
Got float values for the sub-framed star's HFR.
I'm running compiled from the head of the tree (post 3.3.7) on RPi4/Raspian.
Hy

I’m seeing this as well. 3.3.6 on RPi4. It does seem somewhat random? Not sure, but I have flipped between 1 star and full field.

I had also seen that sometimes with the standard (x86_64) version, especially when using the multi-star mode. No real idea what triggered it.
But in recent versions I ave not seen it anymore. AFAIR there had been some corrections in the code. So it might be worth trying some nightly build.

Looking into the git log, Jasem fixed a relevant bug on Sept 19.
It looks like the 3.3.6 release was cut on Sept 6, and 3.3.7 on Sept 23.
So, if you are using 3.3.6 or earlier, the fix he made wouldn't be included.

> git show 269e6fca8

Author: Jasem Mutlaq <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Thu Sep 19 13:26:43 2019 +0300

Fix HFR calculation, add HFR on focus view, adjust focus UI.

Summary:
Fixed HFR calculation in the FITSData class, which was accumulating integer instead of double values.
This led to incorrect consolidation of HFR over multiple stars in the focus procedure and incoherent results in full-frame mode.
...

Hy,

I pulled the latest build from nightly PPA and the issue seems to be fixed.
Thank you for your help!

Alex