I'm getting familiar using the scheduler with simulators only at the moment before using it for real. Testing while the simulated weather conditions are good is working fine for me but when I force an 'out-of-line' weather condition its not sleeping as the tooltip suggests it should. can anyone confirm what actions should be expected in this scenario please? I'm running Kstars 3.6.0 and indi 1.9.6 on Ubuntu 20.04. This is the final log entries in the Ekos panel..
2022-08-17T20:31:31 Shutdown complete.
2022-08-17T20:31:31 Ekos stopped.
2022-08-17T20:31:30 INDI devices disconnected.
2022-08-17T20:31:18 Executing script /home/ray/shutdownScript.py...
2022-08-17T20:31:17 Dome already parked.
2022-08-17T20:31:16 Mount already parked.
2022-08-17T20:31:16 Starting shutdown procedure due to severe weather.
2022-08-17T20:31:16 Caution: weather conditions are in the DANGER zone!
2022-08-17T20:31:16 Ekos started.
2022-08-17T20:31:14 Weather conditions are OK.
2022-08-17T20:31:03 Executing script /home/ray/startupScript.py...
2022-08-17T20:31:02 Greedy Scheduler plan for the next 48 hours starting Wed Aug 17 20:31:02 2022 (0.024)s:
2022-08-17T20:31:02 Spica 08/17 20:31 --> 20:36 job completion
2022-08-17T20:31:01 Scheduler started.
2022-08-17T20:31:01 Scheduler is awake.
2022-08-17T20:30:49 Greedy Scheduler plan for the next 48 hours starting Wed Aug 17 20:30:49 2022 (0.021)s:
2022-08-17T20:30:49 Spica 08/17 20:30 --> 20:36 job completion
Hi, I appreciate your response to this. I May be misinterpreting the tooltip but the one I'm referring to is when hovering over the 'Aborted Job Management' title. on the Scheduler tab In particular this bit.
Define what should happen when a job steps into an error or aborts
Re-schedule after all terminated
If a job gets aborted, the scheduler will only re-schedule it if
when all jobs are finished or aborted. If this is the case, the
scheduler re-schedules all aborted jobs and sleeps for the given delay
I'm assuming that any active jobs at the time of a critical weather alert would result in an aborted job and the above would apply. As it stands the scheduler ends with Shutdown complete and needs manual intervention before it will do anything else. I thought, going by the tooltip above, it would shutdown then sleep for the entered amount of time and then retry in the hope that the weather situation has improved.
Maybe I can ask this differently. Is it by design that an aborted job, as a result of severe weather, is not rescheduled or is this a bug? I've tested this in all stable versions from 3.5.7 to current 3.6.0
Tested by, using all simulators, start a scheduler job capturing a few images. Raise a severe weather alert before the image captures complete. What should happen next?