Regarding the Z-filter comment, a core member from PHD2 told me that Z-filter used an offset. See the discussion here .

@fenriques, It seems does not install under RaspbianOS (buster)

OK. I'm the author of the Z-filter module. As Andy said it is normal for an offset to occur and it is not a problem for imaging BUT it does not inherently USE an offset. In addition to the situation I mentioned earlier, an offset can also occur with a drift arising from a large PA error where the Z-filter correction offsets the drift but does not return the star to the lock position

This looks fantastic. It seems to include some features I've posted for on the Wish List. Great work. Thank you.
Question: The RGB color coding is quite clear. But what about narrowband and calibration frames? I'm thinking you went with something along these lines?
Ha: Dark Red
S: Yellow
O: Cyan
Luminance: White
Dark Frame: Black
Bias Frame: 50% Grey
Flat Frame: 25% Grey
Other: Magenta

Wow, fantastic!

@kengs

I had a sense there was some authority behind response to my original post ...

Not directly related to topic, but are there any other conditions that would cause an offset other than PA? PHD2 reports my PA between 0.5 arcmin to 3.2 arcmin, so I'm not sure that's the issue. So, some other force must be in play. I'm guessing its either balance or cabling. I'm wondering if is possible to get a hint from looking at the corrections.

jmh

I would like to see temperature, barometric pressure, dew point, and possibly any other weather data (SQM comes to mind), plotted on the graph to to see how that that has an effect on SNR and HFR throughout the night.This would help people understand when to focus, if they're not doing it a appropriate times, or enough, or maybe too much. Right now, I refocus at every filter change, but maybe I should be doing it at every degree drop in temp, or every several degrees drop. Who knows, but this addition would be great in understanding what's happening.

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

If you included the solver, I suppose it would be possible to see how much drift is happening between frames, or after guide star loss? Are these results realtime?

@Lead_weight: Andrew, yes, agreed. I was planning on adding some plate-solver-related info someday/somehow after stellarsolver's release.

@lhoujin et al:

Below is a table of the colors in use when the capture or focus timeline is "striped". ( see here for the code ):

If you have no filter or the filter name is not recognized, there is no stripe.
The filter names correspond to what's filled in for the Indi filter wheel settings.

My apologies, I just 'hacked in' a US-English-centric version of filter names. Happy to internationalize it.

This is a great place to contribute. Please send me more filter synonyms and/or missing filters with synonyms & suggested colors!



I'm using Qt colors, which are defined here
but I could use RGB values as well].

@Lead_weight: Andrew,

I agree in principle about your weather-related info, but in practice:
(a) not sure where to get the info (outside of temperature, which is there already, though not plotted--see below).
(b) would need to figure out how to manage the display all the new numbers.

Temperature is the one of your suggestions that's already in the module. It's displayed in the details box for focus. I didn't plot it because I had so many stats already I thought there was only several measurements per night (i.e. "on every filter change" might mean every half hour?) but I suppose I could. I think I could fit one more line of stats, though things are already crowded.

Input on ways to manage all the possible stats would be good.
I.E. Jasem feels (and I agree) that KStars should work on small displays, e.g. displays where the horizontal resolution is ~800px and vertical ~738 and I did squeeze this tab in a bit to get it to fit that, more or less.

Hy