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 the ability to use a FITS skymap as input to pycbc_make_sky_grid #4995

Open
titodalcanton opened this issue Dec 18, 2024 · 0 comments
Open
Assignees
Labels
PyGRB PyGRB development

Comments

@titodalcanton
Copy link
Contributor

titodalcanton commented Dec 18, 2024

After #4267 and #4984, the next and last step for using HEALPix skymaps as input to PyGRB is to generate a sky grid that is constrained by a HEALPix skymap.

Some considerations to drive the design of the CLI interface:

  • Well-formed skymaps should contain the trigger time in their DATEOBS header field, so in principle the FITS file is all that should be needed to specify both the time and sky location.
  • It would be good to keep the ability to use the existing CLI arguments (central sky location + radius) as well, in case we want to follow up external triggers that do not provide HEALPix skymaps.
  • It would be good to have the ability to construct an all-sky grid, for experimenting with all-sky coherent searches.

In terms of the overall code (re)design, it would be good (if possible) to maintain a certain separation (i.e. modularity) between the various possible constraints on the sky location (no constraint = all-sky grid, constraint based on center and radius, constraint based on a HEALPix skymap) and the various possible ways to define the density of grid points (constant density, density defined by timing considerations only, density defined by fractional loss of incoherent SNR, density defined by fractional loss of coherent SNR, exact SNR loss vs metric approximation, etc).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PyGRB PyGRB development
Projects
Status: In Progress
Development

No branches or pull requests

2 participants