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

Add FoV as a parameter #56

Open
aboucaud opened this issue Feb 13, 2022 · 5 comments
Open

Add FoV as a parameter #56

aboucaud opened this issue Feb 13, 2022 · 5 comments

Comments

@aboucaud
Copy link
Collaborator

I think the field of view would be a nice value to have in galcheat, even though not useful at the BTK level.

What do you think @ismael-mendoza, @HironaoMiyatake @mpaillassa ?

@ismael-mendoza
Copy link
Contributor

Sorry, could you give more details on what you mean by field of view in the context of galcheat? Is it like the extent of each survey ?

@aboucaud
Copy link
Collaborator Author

I mean the footprint of a single exposure of the survey on the sky.
We could also add the full area covered by the survey.

@ismael-mendoza
Copy link
Contributor

yeah I think that would be useful actually, I remember people in the BL meeting were saying that would like to have that. What do you think @mpaillassa ?

@ismael-mendoza
Copy link
Contributor

In fact I have some notes from the BL meeting some months ago suggesting:

Location for survey footprints, whether two surveys have any overlapping region? or some approximation to them (arcseconds)

@mpaillassa
Copy link
Collaborator

Yes I think it could be nice to have both. I propose a definition and different names for each:

  • Area covered by a single frame/exposure or by the CCD mosaic: field of view, field size, field area.
  • Area covered by the survey: survey area, survey size, survey (sky) footprint.

With the second we can then imagine having a small script to display the survey areas or compute overlap regions between surveys.

@aboucaud aboucaud changed the title FoV currently missing Add FoV as a parameter Mar 11, 2022
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