panoptes / POCS

An Observatory Control System for the PANOPTES citizen-science project designed to help find transiting exoplanets! :telescope: :stars:
https://pocs.readthedocs.io/en/latest/
MIT License
80 stars 49 forks source link

Cloud-based scheduler #743

Open wtgee opened 5 years ago

wtgee commented 5 years ago

As a first step toward having a networked scheduler it would be nice to provide a simple cloud function that can return available "pretty image" fields.

This is motivated by the fact that I want PAN001 to dwell on the TESS sectors as specified in #742. However there are inevitably going to be some times where the unit cannot schedule a full two hour observation block. I don't want to pollute this file with other targets so it would be nice if during these scheduling attempts we could query a cloud function that could return a field that could be observed for 20-30 minutes.

Note that it is not at all necessary to do this with a cloud function or via the network but the idea would be to use it as a stepping stone toward a cloud-based scheduler.

Thoughts? @jamessynge @joshwalawender

jamessynge commented 5 years ago

Go for it!

On Wed, Nov 28, 2018, 10:48 PM Wilfred Tyler Gee <notifications@github.com wrote:

As a first step toward having a networked scheduler it would be nice to provide a simple cloud function that can return available "pretty image" fields.

This is motivated by the fact that I want PAN001 to dwell on the TESS sectors as specified in #742 https://github.com/panoptes/POCS/pull/742. However there are inevitably going to be some times where the unit cannot schedule a full two hour observation block. I don't want to pollute this file with other targets so it would be nice if during these scheduling attempts we could query a cloud function that could return a field that could be observed for 20-30 minutes.

Note that it is not at all necessary to do this with a cloud function or via the network but the idea would be to use it as a stepping stone toward a cloud-based scheduler.

Thoughts? @jamessynge https://github.com/jamessynge @joshwalawender https://github.com/joshwalawender

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/panoptes/POCS/issues/743, or mute the thread https://github.com/notifications/unsubscribe-auth/ABYmUxk2sfHwpc7ZfNfLZwUIZoAvGr9uks5uz1kYgaJpZM4Y445V .

joshwalawender commented 5 years ago

Sounds good. We should carefully think through the implications of going 100% cloud scheduled for the survey before going too far down this path as we had originally planned to allow units to be unconnected to internet. We might drop that and require a connection, but we should explicitly make a decision on whether or not we do that. This sounds like a reasonable way to explore that avenue without committing us.

jamessynge commented 5 years ago

I think we need the option of completely disconnected operation to remain viable, especially for survey mode. But we should also allow for many, if not most, scopes to have a good internet connection that we can take advantage of, both for coordinated campaigns and to enable the option of skynet style scheduling.

On Mon, Dec 3, 2018, 7:34 PM Josh Walawender <notifications@github.com wrote:

Sounds good. We should carefully think through the implications of going 100% cloud scheduled for the survey before going too far down this path as we had originally planned to allow units to be unconnected to internet. We might drop that and require a connection, but we should explicitly make a decision on whether or not we do that. This sounds like a reasonable way to explore that avenue without committing us.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/panoptes/POCS/issues/743#issuecomment-443924201, or mute the thread https://github.com/notifications/unsubscribe-auth/ABYmU2yCNc_hss_QQt8f9FhQTw8oWM2Oks5u1cMHgaJpZM4Y445V .

wtgee commented 5 years ago

The idea would definitely be to have this as an item in the config that can easily be turned on and off. I don't think we would ever really go 100% cloud scheduled, at least not in the sense that all units are required to query a central server before beginning nightly operations. There will inevitably (hopefully) be units that are remote and isolated (off-grid) that might only very infrequently want to connect to the internet.

We also need to keep in mind that there could be complications with internet connections for any units that are hosted at public schools as there will inevitably be firewall rules and protections in place.

I think we are all on the same page on this, i.e. supporting the ability to do cloud-based scheduling but not relying on it.

wtgee commented 5 years ago

Just as another small point although this is mostly the same as the pretty image. I kind of want to try to capture the comet 46P/Wirtanen. Obviously having a changing RA/Dec for a target would just be annoying for each unit to have to do whereas if we manage it on the server the unit doesn't need to care about that. Mostly putting this here for my own future reference.