Hi,

I just had a look at last night guiding using phdlogview. This is absolutely great that the logfiles are compatible!

But I noticed that, other than when using PHD2 for guiding, the dither sections are not automatically greyed out. Looking in the logfile, for the internal guider a dither looks like this:whereas PHD2 reports the 'settling started' right away after the dither info. As phdlogview only marks the points between the 'started' and 'completed' lines, in the EKOS case nothing gets marked as settle...
Would be great if that could be done the same in EKOS. Marking all the dithers of a night by hand is a bit cumbersome

(Hmm, should this have gone to 'Wishlist'?)

Edit: Why does the edit command convert square brackets to angled ones, and then doesn't understand them!?

Pit,

I'd be happy to help, I introduced this log just for people like you who want to use phdlogview, however let me know what you think...

So, are you saying that the moment dithering starts (i.e. it changes its target pixel values, but hasn't even pulsed the mount yet) the 'Settling Started' message should be printed?
If that's the case, then why do they even bother with a 'Settling Started' message. They could just use the "DITHER by" message.
The way I implemented it, was to put the settling started message after the dithering was complete (i.e. it changed the target, pulsed the mount a few times to get 'close enough' to the target). Then, there is a Settle parameter in Guide Options, which means "after the dithering is done, wait N more seconds before starting to capture (defaults to 0)." This (potentially 0-second-long) settling interval is what you're currently seeing.

It seems to me that you're pointing out a bug in phdlogview, more than one in KStars. However, from a practical point of view, it may be easier to fix KStars, as this log is really only useful for phdlogview.

What do you think, should it be changed in KStars?
Hy

At least this is how it's done in PHD2:That is well true...I can well follow there. But what it leads to is that I always get the 'started' message directly followed by the 'settled' message. And as the INFO entries don't have timestamps that effectively is a zero settling. But TBH, I would indeed rather take the new lock point as something that cancels the 'settled' state, taking the settling as the time it needs to reach that new position. So I think both views have an argument...
I'd say yes. As you write, the log was set up in a way to be compatible with PHD2 and especially phdlogview. So it would be more straightforward to take the pragmatic approach and copy it's view of things (even if you'd rather consider it wrong). But unless you can convince Andy to change phdlogview (and probably also PHD2), not doing it would reduce the 'user experience'.

My 2¢

Merge Request submitted.
invent.kde.org/education/kstars/-/merge_requests/96
It may be merged into KStars after Jasem reviews it.
I tested with the simulator and my dithers were now greyed out by phdlogview.
Thanks!

FWIW, this was my favorite kind of bug report--one where you tell me exactly what I need to do to fix the problem!

To get the internal guide logs to exclude dither and settling in PHD Log Viewer, I had to enable 'Exclude Settling Parametrically' in the log viewer settings.

Whee! Indeed, that works. Didn't even know about that option

But Hy's patch already made it to the main repo