Bug 402709 - scheduler does not start a sequence when frames exist although repeat until terminated is selected
Summary: scheduler does not start a sequence when frames exist although repeat until t...
Status: REPORTED
Alias: None
Product: kstars
Classification: Applications
Component: general (show other bugs)
Version: 3.0.1
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: TallFurryMan
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-30 15:17 UTC by Wolfgang Reissenberger
Modified: 2019-01-03 19:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Reissenberger 2018-12-30 15:17:37 UTC
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.
Comment 1 TallFurryMan 2019-01-03 16:02:51 UTC
Version? There was a regression with a hotfix for that specific issue:

https://github.com/KDE/kstars/commit/a3e3b2c7c42d64548bb2052700e8aa5998261b37

I assume the problem is still here somehow.
Comment 2 Wolfgang Reissenberger 2019-01-03 19:18:28 UTC
The latest commit on the master branch is 2bd1ad0433ce9a0cabce2b693ebc4bc50be6e703

It seems like lightFramesRequired is not used properly, since it does not take into account, whether the image sequence is  multiply run.