D19998: Remove bypass of preliminary steps when no light frames are needed.

Eric Dejouhanet noreply at phabricator.kde.org
Sun Mar 24 08:08:03 GMT 2019


TallFurryMan added a comment.


  @mutlaqja If you want to mix lights with calibration, I wonder if that is really clearer that you need to remember the progress of jobs in that case. In that situation the scheduler will be able to determine what's left to do, and not redo lights if only calibration remain.
  If not remembering, the minimal granularity of the work to do is the full job, which contains in your case lights and calibration.
  This may push users to run lights and calibration frames as separate jobs just to be sure on what happens. 
  But in both cases starting the execution will still schedule the job for capture as if there were lights. There are two sides to this: scheduling and running. This differential is lacking work on scheduling, agreed.  
  You get a good point. Also a scheduler job with only calibration frames should issue a certain amount of warnings: twilight, altitude, etc. The current UI is not prepared for this...

REPOSITORY
  R321 KStars

BRANCH
  improve__remove_calibration_frame_bypass (branched from master)

REVISION DETAIL
  https://phabricator.kde.org/D19998

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/20190324/7b02c8e3/attachment.html>


More information about the kde-edu mailing list