×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Full Automation and Weather handling in the Scheduler

  • Posts: 85
  • Thank you received: 40
Awesome. Do you generate kstars/ekos/observatory/observatory.ui with some tool ? and if so how does that work ?
4 years 10 months ago #39242

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370
I use QTCreator for development. It contains a graphical editor to generate the XMLs.
4 years 10 months ago #39245

Please Log in or Create an account to join the conversation.

  • Posts: 112
  • Thank you received: 9
Hi,

I was wondering if someone can help me understand the logic behind the Ekos Scheduler. In the attached screenshot I added eight targets to a schedule and assigned each Priority to 10 and constrained Altitude > 30, also Twilight is unchecked since I am using simulators. Thanks to all those who contributed to this thread. Lots of activity up until 6 months ago.

Right now the time is 0830 on December 11th. It is true that four targets meet the criteria of Altitude > 30: NGC 2683, NGC 2903, NGC 2841, and NGC 3198.

I was expecting the scheduler to bubble those four targets to the head of the job list with a Start Time of now; after all, they are visible. Instead it says I need to wait 7 hours for M33 to come around to the east again. 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 was hoping to create a schedule of hundreds of targets and have the scheduler run those jobs that meet my criteria (including also weather.) For example 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.

I'd like to run the Scheduler once, and have Ekos work continuously, day after day, waiting for darkness and good weather, and when that happens check to see which of the targets meet the criteria (i.e. Altitude > 30), and then begin imaging.

I understand that it is a lot to ask for but I was wondering what the roadmap looked like. Thank you, again.
4 years 3 months ago #46815
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370
Maybe having dozens of targets and a magic scheduler simply picking the optimal target and after two weeks in a row you can come back and everything is ready - well, that's slightly too ambitious - currently at least...

The scheduler always runs the list top down. If you choose the "Sort by altitude" option, the scheduler will sort the targets by altitude putting those with the closest earliest setting time first (roughly). But after this happens, the targets are run in sequence in a non-preemptive manner. The second one will only be started when the first is finished.

In case that the first one isn't finished but it hits its constraints (altitude, moon separation, ...), it will be postponed to a later time until these constraints are met again - and all others have to wait until the first one is finished. This is not optimal, but that's how it is working currently.

I personally never use the "Sort by altitude" option but I simply set a termination time so that the next job may start when it makes sense.

Does that answer your questions?

- Wolfgang
4 years 3 months ago #46817

Please Log in or Create an account to join the conversation.

  • Posts: 112
  • Thank you received: 9
Thanks Wolfgang.

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.

Thanks again.
4 years 3 months ago #46818

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370
Disable "Sort by altitude" in the EKOS Scheduler options. Then you can change the order manually.

4 years 3 months ago #46819
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 112
  • Thank you received: 9
Ahhhhhhh, I'll give it a try. Thanks!
4 years 3 months ago #46820

Please Log in or Create an account to join the conversation.

  • Posts: 112
  • Thank you received: 9
Wolfgang said: "I personally never use the "Sort by altitude" option but I simply set a termination time so that the next job may start when it makes sense."

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.
4 years 3 months ago #46822

Please Log in or Create an account to join the conversation.

  • Posts: 456
  • Thank you received: 76

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:-)
Derek
4 years 3 months ago #46838

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370
Shutdown when the weather turns bad should be working already. The scheduler listens to the weather driver and shuts down everything. The question is how robust and reliable this is - no idea.

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.
4 years 3 months ago #46840

Please Log in or Create an account to join the conversation.

  • Posts: 456
  • Thank you received: 76
Yes the shut down works really well. I start the scheduler and I trust it enough to go to bed. But what would be awesome is if it could do a 'suspend' on bad weather and resume on good weather. Suspend for me would mean park scope and dome, then wait for better conditions. Or shutdown if dawn comes.
Its not that straightforward to implement this though I think.
The following user(s) said Thank You: kamisan, Paul Muller
4 years 3 months ago #46845

Please Log in or Create an account to join the conversation.

Yes, this would be an awesome idea to have. Currently, it goes into total shutdown mode. Maybe with the right switch, it can also go into the current Park Wait mode. Park Wait is exactly this, it parks but doesn't shutdown, but this is used now when the next job is far away. Maybe it can be re-used for 'suspend' on bad weather if the option is set. However, looking at my own observatory, Park Wait would not suspend power or shutdown INDI , so you could end up in a situation where your equipment is wasting power. My shutdown script actually includes a Python script to turn off the power completely. Also, by the end of the shutdown, it would shutdown INDI server itself. At this stage, the scheduler has no idea what the weather is since the driver is down.

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.
4 years 3 months ago #46851

Please Log in or Create an account to join the conversation.

Time to create page: 0.636 seconds