D14684: Fixes for the Scheduler and Capture modules

Eric Dejouhanet noreply at phabricator.kde.org
Mon Aug 13 08:48:47 BST 2018

TallFurryMan added a comment.

  From the code perspective, it can't because it uses the same storage space as the first job. It is evaluated independently from the first job, and arrives at the same conclusion.
  From the user perspective, the main objective of the scheduler is to ensure N captures are made, translating to X hours of imaging. One solution is to setup one single job with enough captures for say 60 hours of imaging, which will get partitioned over multiple nights. If you want to fit another job in-between, you can use START_AT/FINISH_AT fixed-time jobs, and still keep track of the number of captures.
  There is still work to do on priorities, and interrupting jobs, which will make this feature clearer: jobs which update their priority at the end of a batch to let others run, or jobs which interrupt others when they are ready to start.

  R321 KStars


To: TallFurryMan, mutlaqja, wreissenberger
Cc: kde-edu, narvaez, apol
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-edu/attachments/20180813/1eef2cd3/attachment.html>

More information about the kde-edu mailing list