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

BGS SV fields #11

Open
changhoonhahn opened this issue Nov 11, 2020 · 1 comment
Open

BGS SV fields #11

changhoonhahn opened this issue Nov 11, 2020 · 1 comment
Assignees
Labels
question Further information is requested sv
Projects

Comments

@changhoonhahn
Copy link
Member

BGS SV fields were revised back in April in order to maximize overlap with the DR9 SV footprint. At the time, SV was scheduled to happen before DR9 would be processed for the full footprint. So, DR9 imaging would be run on these SV regions, specified in the link, first. Now that this is not an issue we may want to revisit the BGS SV fields.

Here's the BGS SV fields from April --- selected using this notebook
image

@changhoonhahn changhoonhahn added question Further information is requested sv labels Nov 11, 2020
@changhoonhahn changhoonhahn added this to To do in feasiBGS via automation Nov 11, 2020
@michaelJwilson
Copy link

Potential to dos:

-- Revisit CMX TILEIDs, making sure any tile with same ID has the same center.
-- Prioritize the fields.
-- Check we didn't lose avoiding shallow GAMA data, and pointing at the deeper GAMA data.
-- PAU & JPAS overlap?

@changhoonhahn changhoonhahn moved this from To do to In progress in feasiBGS Nov 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested sv
Projects
feasiBGS
In progress
Development

No branches or pull requests

2 participants