There's no reason to stop guiding, nor stop capturing just because of a hiccup. PHD2 continues to try to find a guide star and with re-enter guiding when it does, meanwhile image capturing should also not stop so that things can return to normal when a passing cloud is gone. All that needs to happen is to send an alarm that there is an issue. Again PHD2 does this until its back on its feet. Ekos stops everything, sends out 1 ding and thats it. Most of the time this kind of alarm is missed. An alarm should persist until acknowledged.
Thanks. Just to really press my point, Kstars should NEVER abort a capture session. There is no reason to. We’re not trying to save film here. I should be able to leave my rig going all night without stopping or until it hits mount limits. Sky conditions are always changing and I need to have it running until I decide to stop it.
I think I saw a option that appeared to disable abort but it seemed to not work. Again it was a couple outings ago that I was struggling with it.
Capture is aborted if guiding was aborted and autoguiding was started before capture process was started. So if you started capture and guide was active, this only means you depend on guiding for capture. So when guiding is aborted, capture is stopped. However, capture was not resumed when guiding was started again. So I just fixed this aspect, but the overall behavior is the same.