Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MAST: Move drizzlepac astroquery_utils upstream to astroquery.mast #2950

Open
s-goldman opened this issue Feb 15, 2024 · 4 comments
Open

MAST: Move drizzlepac astroquery_utils upstream to astroquery.mast #2950

s-goldman opened this issue Feb 15, 2024 · 4 comments

Comments

@s-goldman
Copy link

s-goldman commented Feb 15, 2024

Folks have found that the code in astroquery_utils.py should be moved upstream to astroquery to make them generally available. It would be very useful to make retrieve_observation available to everyone. It also might make sense to enable it to work well on AWS as well to pull the files from the right place easily.

@keflavich
Copy link
Contributor

That link gives me a 404 error. Is it publicly available?

@bsipocz
Copy link
Member

bsipocz commented Feb 15, 2024

I've commented in the original issue to say I don't think this is an astroquery issue but downstream. At best an astroquery.mast issue, but definitely not a generic astroquery one.

@bsipocz
Copy link
Member

bsipocz commented Feb 15, 2024

Note on the AWS front: we do work on adding tools to pyvo on that angle, and mast is involved in those efforts, so ideally we will need the mast module to move ahead and use those tools rather than add more efforts into a different approach.

@s-goldman
Copy link
Author

That link gives me a 404 error. Is it publicly available?

sorry, link now fixed.

@bsipocz bsipocz changed the title Move astroquery_utils upstream to astroquery MAST: Move drizzlepac astroquery_utils upstream to astroquery.mast Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants