"...kstars does not abort guiding when slewing."
YES! That's exactly my point. It should, it's broken and it should be a rather trivial problem to fix.
This was reported fixed a month ago but it's not fixed. The problem isn't just with the mosaic jobs. The only time the scheduler behaves correctly is when it detects a change in pier side, a crossing of the meridian. I set up a job sequence with 2 objects on the rising side of the meridian, then 2 on the setting side and then 2 more on the rising side. When switching to a job on the same side of the meridian, it behaves as if it still has the guide star when in fact it's many degrees away. Switching to a job on the opposite side, it recognizes the need to recalibrate and behaves correctly.
It should be a simple fix to have it set the recalibrate flag when it detects any SLEW, not just a meridian change.
Attached is a log. I edited out a bunch of focuser commands that are irrelevant.
Using both the nightly (2019-05-30 13:10:05) and stable (2019-05-30 9:48:47) I have the same problems - no change in behavior. Guiding fails to re-calibrate on mosaic panel changes and focus is not called on either panel changes or meridian flip. Log attached...
This is great. Thank you.
I don't know how to work with the Git link you provided. How long before it makes the nightly release if it's not there already? And how can we know when this or any other fix moves from nightly to stable?
Hi Wolfgang - I've re-run the simulation of a 2x2 mosaic of an object as it crosses the meridian. The logs show both the proper handling of the meridian flip and the poor behavior when switching from panel to panel in the mosaic. I've made some notes in the log and you can find them by searching for the string "????". In the meantime I'll be installing and trying to learn PHD2. Thanks for you help.
Yes, I'm using the EKOS guider. I was trying to keep everything in one unified package. I guess I'll have to install PHD2 and learn it. Do you know if it will run properly in the simulator?
In any case, I think this remains a bug in EKOS that should be looked into.
Hi Wolfgang -
Thanks for your quick reply. Yes, that's the right log. I live in one of the foggiest places in the US and only have limited time to observe. I'm running sims to get all the kinks out so I don't waste valuable observing time trying to figure things out while shivering in the dark.
The problem persists. When changing frames on a mosaic, the guider goes straight back to auto-guide without grabbing a new image and finding a new guide star. However if it does an automatic meridian flip, it detects that the pier side has changed and goes all the way back to find a new star and re-calibrate. Today I'll try to run a mosaic on an object at the meridian that requires a flip in the middle and send you that log so we can see it it shows any difference.
The remember-job-progress switch fixed the other problem, thanks.
Here are the logs....
When I'm doing a mosaic sequence, everything starts out ok. It slews to the 1st frame, focuses, aligns and begins auto guiding with a normal pick a star - calibrate - guide sequence. It then takes the required exposures.
The problem starts with the 2nd frame. It does a normal slew and align but then begins auto-guiding without selecting a new star. It tries to guide on "nothing" until it errors out. Only then does it select a new guide star and begin imaging. In the mean time it may have produced any number of unguided images.
Attempting to stop the guiding only makes things worse because it goes all the way back to re-calibration when that is unnecessary.
A second problem is that the job sequencer will not reset properly. It keeps all job status' at "completed" and will not re-run the set.
Problem solved - everything loaded correctly this morning.
Follow up to my last post. I tried using "aptitude" instead of "apt". Still no joy but I got a more complete error message....
The following packages have unmet dependencies:
indi-full : Depends: indi-astromechfoc which is a virtual package and is not provided by any available package
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) indi-full [Not Installed]
I see that similar problems have occurred in the past. I'm sure it's just a glitch in the new driver set that will be cured in a day or so.
"Hoping there is a quick fix!"
Me too! I've just made my problem worse by purging indi-full. I was hoping that a fresh start would fix things but it didn't and now I have no drivers at all.
I ran into this problem this morning...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
indi-full : Depends: indi-astromechfoc but it is not installable
Depends: indi-dreamfocuser but it is not going to be installed
E: Broken packages
I assume it's a glitch in the new library release. Any help?
If your issue #1 is correct - that's scary! A viewer should be just that - not an editor.
PixInsight can show FITS images and histograms but it may not be convenient to use during an observing session.