https://bugs.kde.org/show_bug.cgi?id=497864
Bug ID: 497864
Summary: Ekos Scheduler starts observations when weather is
unsafe
Classification: Applications
Product: kstars
Version: 3.7.4
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: pe...@englmaier.ch
Target Milestone: ---
SUMMARY
I am using ekos/scheduler to schedule observations in my observatory. The
weather is enabled in the 'job constraints' section and the cloudwatcher/solo
device is reporting safe/unsafe state to ekos with the weather watcher driver.
When I started the scheduler (day before), the status was unsafe reported and
stayed so. However, at some point the scheduler somehow "lost contact" and the
status icon was no longer displayed in the scheduler screen. The scheduler then
considered the state 'safe' even if it had no information about the state. It
opened the observatory and started imaging. This is dangerous and I think ekos
should always consider situation unsafe if weather is job constrain and
condition is not reported safe.
STEPS TO REPRODUCE
1. Setup up observation in scheduler
2. Enable the weather condition, check that the icon next to the weather
condition is displayed
3. Start the scheduler
4. Somehow mock the icon to disappear, i.e. stop the weather driver
OBSERVED RESULT
The scheduler is starting the observation when the other conditions are met
(i.e. Altitude, Moon seperation, Twilight, Horizon) even if weather is not
reported to be safe. When this happens, the icon indicating the status is also
disappearing from the scheduler and the observatory tab. The driver (in the
INDI control panel), however, is reporting the status to be unsafe! That is why
I think, the communication inside kstars/ekos seems to hang or break.
EXPECTED RESULT
Scheduler should not start observations as long as weather is a constraint and
it has no current status information.
It knows that it has no current information, because the green icon is not
displayed.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 24.04 (all patches), kstars 3.7.4
ADDITIONAL INFORMATION
kstars was compiled and installed by hand. The precompiled version of kstars
has the same problem, but it does not install cleanly.
I am now trying to debug the problem myself and will submit a PR if I can fix
it. For now, I will focus on the behavior of the scheduler to be more 'safe'.
Next I will try to find out why the reporting is broken.
There is another reports (420437), for the same or a similar issue. I think it
should be fixed inside the scheduler first, to make it more resilient, and then
the reporting should be fixed.
--
You are receiving this mail because:
You are watching all bug changes.
