https://bugs.kde.org/show_bug.cgi?id=402709
Bug ID: 402709
Summary: scheduler does not start a sequence when frames exist
although repeat until terminated is selected
Product: kstars
Version: 3.0.1
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: wreis...@gmx.de
Target Milestone: ---
SUMMARY
A scheduler job where
1. "repeat until terminated" is selected,
2. "remember job progress" is selected and
3. there exist more frames as the single image sequence requires
does not slew to its target, but immediately starts capturing. The log shows
the following entry:
Job 'test' is proceeding directly to capture stage because only calibration
frames are pending.
I would expect that the scheduler option "repeat until terminated" starts a
sequence no matter how many frames have been taken.
STEPS TO REPRODUCE
1. Select the Ekos Scheduler option "Remember Job Progress".
2. Open the scheduler tab
3. Select an arbitrary target and an image sequence for light frames
3. Select the job completion option "Repeat until terminated"
4. Create a new job
5. Let the job run for at least one complete loop to create sufficient frames
6. Abort the job
7. Restart the job
OBSERVED RESULT
The scheduler starts immediately with capturing and issues the message that the
job does contain only calibration frames.
EXPECTED RESULT
Slewing to the target, aligning, ..., and finally looping the capturing until
it is terminated manually.
--
You are receiving this mail because:
You are watching all bug changes.
