fenriques wrote: awesome work! thank you. All the insight needed to monitor and review the session in one window; to me it should replace the Setup tab.
@Rick, I'm thinking to use the .analyze file as the only source of information for Astrodom. What do you think?
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
fmozza wrote: Regarding the Z-filter comment, a core member from PHD2 told me that Z-filter used an offset. See the discussion here .
hy wrote: Ferrante: wasn't aware of Astrodom, looks very cool. Take a look at the .analyze files and in particular the method processInputLIne()
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.