Consolidation of scheduler jobs must be more efficient
I'm doing rather complex Scheduler sequences for variable stars, with up to 50 jobs or more for one night. It is very slow and cumbersome to adjust them in Ekos. Also, these jobs needs to be evaluated in relation to altitude etc. It would be good with a scheduling assistant of some sorts, that made this easier. It would be good if that was easily doable "off site" so to speak, during the day, without needing to change the time settings for Kstars etc. Further, to get everything right (like camera sensor dimensions), it is tricky and cumbersome to do at another computer, for instance. So: is there a way to facilitate building, evaluating (in relation to for instance altitude etc), and adjusting complex jobs "off site", later to import the scheduler file to the Raspberry Pi by the scope?
-
Write tests for each Scheduler restriction usage in the plan. -
Lighten the UI by removing the year from timestamps. -
Optimise SchedulerJob::calculateAltitudeTime
, which is used extensively while planning. -
Add Most Recently Used (MRUs) items to Sequence/Scheduler file load and save buttons. -
Cache plan results for some time (Ekos option) to avoid recalculating target properties from similar parameters. -
Make manual refresh and Scheduler unattended execution discard the cache of target properties. -
Fix Sequence file misconfiguration when pasting Scheduler jobs. -
Provide Sequence file templates in a library (see #54 (closed), which will allow this). -
Allow Scheduler job files to embed Sequence job files. -
(!242 (merged)) Allow Scheduler job files to be appended to the queue, instead of replacing the queue.