Does anyone know if this nightly update is available for Mac OSX as well?
EDIT: I just saw that it was indeed included in the latest Mac OSX nightly build. I will test it as soon we get a clear night.
It's monsoon season now here in NM.
iOptron CEM120 EC2 and CEM25P
Celestron C11 EdgeHD and William Optics Star71
ASI 1600MM Pro, ASI 462MC
Moonlight Litecrawler (C11) and Motorfocus (WOStar71)
LodeStar X2 and ZWO OAG
Nextdome, AAG Cloudwatcher
As you're probably aware the nightlies include the latest versions of s/w which may / may not work. I spent a few minutes with Build #1560 which appears to work from an L1P perspective. The latest version Build #1563 has problems with memory allocation somewhere and won't take any subframes so is unusable. Sure this will be fixed quickly.
Wow, this new algorithm fits perfectly what I was proposing
only 4 months ago (and you also had already in your mind by then) and even more that I didn't think of!! (different curves, weighting by HFR stdev, ...) Last night I gave it a try and it went quite smooth! I can afford to make focus exposures longer to get better SNR and even so, autofocus takes way less than before. Thanks so much for your effort, for me this is quite an improvement.
Playing with the parameters I occasionally ended up with a failed autofocus, that was quite expected as I pushed some of them. But although the log reflects the failure, it doesn't show why it failed:
[2022-06-25T23:46:39.443 CEST INFO ][ org.kde.kstars.ekos.focus] - "Linear autofocus algorithm aborted."
[2022-06-25T23:46:39.445 CEST INFO ][ org.kde.kstars.ekos.focus] - "Autofocus failed, moving back to initial focus position 5.448."
In this case, I guess it didn't meet the minimum R2 I configured, but I think it would be desirable if the failure reason gets logged.
Also, the Analyze tab didn't plot any HFR measurements in the graph, and "Iterations: 0" is shown under Details (in the log I see that this particular autofocus run took 9 HFR measurements).
Thanks very much for the feedback Sergio. If you configure logging like this:
Then you'll get all the focus related messages. For an R2 failure you should get:
2022-06-26 12:49:09.983722+0100 kstars[11402:2349276] [org.kde.kstars.ekos.focus] "Linear Curve Fit check failed R2=0.999893 R2Limit=1 retrying..."
After the rerun you'll get something like this...
2022-06-26 12:50:00.620048+0100 kstars[11402:2349276] [org.kde.kstars.ekos.focus] "Linear Curve Fit check failed R2=0.997972 R2Limit=1, but continuing..."
I suppose your point is that it could be a bit more obvious as to why the rerun happened (as opposed to having to go hunt through a detailed log file). Good point, I'll have a look at this.
In the Analyze tab you should get a focus entry for each autofocus run. If the run is successful it should log all the datapoints. If it fails, it will log the fact that there was an autofocus run but not the datapoints. L1P just fits in with the existing Analyze workflow here. This is how it works for the existing focus algorithms.
If you post the log here I can take a more detailed look.
Thanks John for your prompt answer. Truth is I even didn't think of enabling the debug logs... I was expecting these messages to appear in the status (bottom) panel of the Focus tab.
Yes, in the Analyze tab I do see the successful runs correctly. Sorry I didn't compare the failure case with the other algorithms, of course you're right.
Thanks for your time!
I used L1p yesterday for my (automated) observations. Looking at the analyze log, it always found a reasonable focus, even in bad conditions (I did have quite a lot of wind last night ). I strongly doubt any of the other algorithms would have found something better. For that, probably some machine learning would be needed (my brain BI would have picked slighly different values in some cases )
All in all a very valuable addition!
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
Just doing a first session with the Linear 1 pass and it works like a charm! First time I get really reproducible focus values and a focus run takes only half the time… Also, using weights for fitting is really a good thing to do!
Thanks John for the valuable extension!
254/1450 mm Newton, 130/730 mm APO, 70/336 mm APO, EQ6-R, ZWO EAF focusers, DeepSkyPro 2600c, ASI183MM, Intel NUC 8i5, Ubuntu 22.04