Reading the .analyze file is quite straightforward thanks to the descriptive naming you added to the events.

Astrodom keeps track of imaging frames only, so the main source of information (beside reading fits headers) would be the CaptureComplete tagged line.
To me it would be nice to have on that line also data not directly related to the frame. For example, average RMS during capture and SNR.

Other capture related data like eccentricity and noise would also be nice to have, when will be available. I would rather read those from .analyze than from PI because have to run SubframeSelector first.

ferrante

hy wrote: Ferrante: wasn't aware of Astrodom, looks very cool. Take a look at the .analyze files and in particular the method processInputLIne()
invent.kde.org/education/kstars/-/blob/m...yze/analyze.cpp#L621
Note that I'm monitoring real-time processes, so some signals come in in awkward ways.

Let me know if there are other things you'd like to see in the file, or perhaps something like a header line that might make things more future proof.
Right now, the file has no header lines, but there's no good reason for that omission. I guess it does have a version header
#KStars version 3.5.0. Analyze log version 1.0.

It is very early in the evolution of Analyze, it's possible that I'll change the file format...though I have no such current plans.
Of course it would also make a lot of sense to make sure people can real old logs...
Still thinking this through.

BTW, I'd love to include more capture-related analysis (like you get from PixInsight files). Right now the only signal computed
is the HFR. I was waiting on @Rlancaste's StellarSolver software release, which was planned for KStars v3.5.0, as it was a
rework of the whole SEP/Sextractor framework for KStars. Not sure of his schedule, though.

Hy