Here's a thing I feel is strange. I have a series of jobs saved as a single file (attached) that I terminated due to errors. THen I clicked the circle to set them all as active again. And clicked Run. THen the schduler wants to sleep for almost 24 hours.... ??
I shut down Kstars, restart, reload the file, and same thing happens. That's what is in the log (attached).
THen I try to set up a new job. Same thing happens.
OK, I might understand something. THere is an altitude restriction making the second job impossible tonight. But why on earth is it not either downprioritized to last, or marked invalid? Does this mean I can not use altitude restrictions to have the scheduler de-select jobs that are too low? That was my plan - to have a list of variables and have the scheduler just run the ones that are feasible....
Hi Magnus, that‘s right, altitude restrictions lead to a postponement of the entire schedule. You could use the „repeat until“ feature as a workaround.
Fixing this is one of the features on my List to be fixed...
- Wolfgang
I guess you have at least two jobs in your schedule, where the first one has the altitude restriction. Put another job *before* that one with the altitude restriction that is restricted by "repeat until".
Now select the "repeat until" such that for the other one the altitude is on the desired height.
Does that make sense? If you have further questions, it might be useful if you post your schedule.