You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to provide an interface to the Astrolabe archive through (py)WWT in Jupyter, and the natural way to exchange data between the frontend and the backend is with the appropriate VO protocols. So, it should be drop-dead easy to get data into a pywwt view through VO queries, and to visualize VO query results in pywwt.
We have astroquery and related libraries to actually do the VO querying, so this issue is much more about working out a smooth and easy overall workflow rather than necessarily adding a bunch of code to pywwt. Some specialized functionality might be needed to smooth that workflow, but my intuition is that it would not be a large amount.
This work should coordinate with the Astrolabe team to make sure that we have a smooth and intuitive workflow for accessing that particular repository from a pywwt/Jupyter frontend.
The text was updated successfully, but these errors were encountered:
This issue was a bit broad. I'm narrowing this one down into the more specific concept of having pywwt provide a nice mechanism to help the user easily perform a VO cone search based on the current field of view of a WWT widget. Naively, I'd expect that this would involve something like taking a template query and filling in the cone-search specifics based on the current viewport settings.
We want to provide an interface to the Astrolabe archive through (py)WWT in Jupyter, and the natural way to exchange data between the frontend and the backend is with the appropriate VO protocols. So, it should be drop-dead easy to get data into a pywwt view through VO queries, and to visualize VO query results in pywwt.
We have astroquery and related libraries to actually do the VO querying, so this issue is much more about working out a smooth and easy overall workflow rather than necessarily adding a bunch of code to pywwt. Some specialized functionality might be needed to smooth that workflow, but my intuition is that it would not be a large amount.
This work should coordinate with the Astrolabe team to make sure that we have a smooth and intuitive workflow for accessing that particular repository from a pywwt/Jupyter frontend.
The text was updated successfully, but these errors were encountered: