Full Automation and Weather handling in the Scheduler
I keep seeing tooltips that make mention of "Sort by altitude" but I see no way of engaging it. I've tried clicking all buttons but nothing approximate what you described.
Disable "Sort by altitude" in the EKOS Scheduler options. Then you can change the order manually.
kamisan wrote: I've tried clicking buttons to alter the behavior but the only control I seem to have is changing the priority. The up and down arrow buttons don't appear to do anything.
I like your idea best. It takes care of an important criterion of mine: I have a relatively small east-facing visibility window due to trees. It's best that I control this.
if it is cloudy at sunset it would wait until the weather cleared at say 2am. If the weather goes from good to bad then suspend imaging, close the dome, and wait for conditions to improve again.
This would be a fantastic feature to have. For me, in Ireland, it often happens that clouds roll over for 20min and then its clear again. In these cases, the scheduler runs the shutdown procedure and I'm sleeping soundly so there are no human's around to restart everything:-)
Additionally, the observatory module has also features for closing the shutter and the dome.
But I do not have an own observatory, so I cannot answer how this all works in real life.
Its not that straightforward to implement this though I think.
Perhaps one idea is to have the weather driver on in its own INDI server always running regardless. Or ... Ekos can be smart enough about this and requests shutdown of everything except the weather driver (INDI server is essentially running in protected mode) which it then listens to intently to monitor the weather conditions and upon favorable conditions, it runs the startup sequence again. Though at this time, instead of running a new INDI server, you will just request the startup of the drivers you previously shut down.
If we think in that direction that we want an automated setup that is able to startup everything as soon as the weather is better again, I think we need something like an observatory agent that is running separately.
Ekos could use both INDI servers so that everything is at hand from one UI. And a separate web application sitting on top of the observatory server would control the observatory devices only and in addition communicate with the scheduler via DBUS for starting, stopping etc.
Now, it could be Ekos Scheduler module itself or a separate process that monitors weather and commands the scheduler to shutdown or startup. The current "Park Wait" implementation is fine for short periods, but inefficient for long periods of inactivity, and therefore a complete power-off shutdown would be the way to go (given you don't cut off power from weather station!). The dedicated process or Ekos can then start the scheduler when the weather improves. The scheduler has no idea and would start as it would have been started by a human operator. That intelligence just acts as the decision maker. It's not just weather, for could be used perhaps for the holy grail we've been seeking for a long time: multi-night scheduling.