https://bugs.kde.org/show_bug.cgi?id=397969
Bug ID: 397969
Summary: Scheduler Unpark Dome/Mount/Cap are unclear and
dangerous
Product: kstars
Version: 2.9.8
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: eric.dejouha...@gmail.com
Target Milestone: ---
In the Scheduler, the Unpark Dome, Unpark Mount, Unpark Cap have unclear
meaning.
If the end-user checks them, Scheduler will, in order, unpark dome, then mount,
then cap. This is the expected sequence, and it occurs as part of the
observatory startup sequence.
If the end-user unchecks them, Scheduler will still unpark the mount when
starting a job. This is also expected, and it occurs as part of the job startup
sequence.
However, neither dome nor cap devices will be checked when starting a job. A
major issue occurs when there is actually a cap in the setup, and it is not
open when the job starts. A serious issue occurs when there is actually a dome
in the setup, and it is not opened when the job starts.
One single checkbox should be used, stating that dome, mount and cap should be
unparked when the observatory starts, in that order.
In the case the checkbox is not set, the state of the dome should be checked
when Scheduler starts to warn the user, considering that Scheduler will be
unable to open the dome. OR Scheduler should be able to control the open
procedure of the dome when a job starts, like it does for the mount.
In any case, the state of the cap should be handled in the same way as the
state of the mount, that is, unparked when a job starts. As stated in the
forum, the cap should even be unparked after the mount finished slewing, in the
case the observatory is too small to unpark the cap before that procedure.
--
You are receiving this mail because:
You are watching all bug changes.
