Skip to content

Issues: nasa-fornax/fornax-s3-subsets

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.

Sign up for GitHub

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

5 Open 0 Closed
5 Open 0 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Develop a MVP product to obtain HST+Spitzer+Galex postage stamps for a specific galaxy in COSMOS in S3 bucket which can be leveraged with other mission data like TESS
#5 opened Feb 21, 2022 by sshen-stsci
Draft a proposal to address different approaches for solving the S3 subsetting problem for COSMOS data documentation Improvements or additions to documentation
#4 opened Feb 21, 2022 by sshen-stsci
@barentsen
Create a notebook as baseline knowledge to document GALEX dataset (COSMOS field) data access in cloud using existing tools/services/package documentation Improvements or additions to documentation
#3 opened Feb 21, 2022 by sshen-stsci
1
@jaymedina
3
Create a notebook as baseline knowledge for handling Spitzer dataset (COSMOS field) in Cloud using existing package/tools documentation Improvements or additions to documentation
#2 opened Feb 21, 2022 by sshen-stsci
@barentsen
Document the baseline knowledge of COSMOS HST image subsetting in S3 bucket documentation Improvements or additions to documentation
#1 opened Feb 21, 2022 by sshen-stsci
@barentsen
1
ProTip! Add no:assignee to see everything that’s not assigned.