D22446: Adding error handling strategy control to Scheduler

Wolfgang Reissenberger noreply at phabricator.kde.org
Sat Sep 21 10:32:33 BST 2019

wreissenberger added a comment.

  > So we try to set jobs to COMPLETED based on frame count, we make sure we do not touch the frame count except when receiving a frame or recounting storage frames, and we do that state change when starting evaluation only? In other words, we never complete jobs during execution? The problem with states is that we must not jitter between values needlessly. Do you have a state diagram in head?
  Let me give a try defining COMPLETED for a sequence job `seq_j`:
    completed(seq_j) <--> if repeats exist -> (forall filters in seq_j: sum(relevant_frames(filter)) >= repeats * (sum frames for filter in seq_j)) 
                                          else if repeat until date valid --> current time >= repeat until date
    relevant_frames(filter) = if remember job progress -> all matching frames in the frames directory 
                                              else all matching frames from the current scheduler run
  I know, there is (at least) one deviation from the current implementation: if a sequence contains more than one entry for a filter, they are counted separately: 
  `3xL + R + G + B + 2xL` is not equivalent to `5xL + R + G + B`

  R321 KStars


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

More information about the kde-edu mailing list