Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: afw
-
Labels:
-
Story Points:30
-
Epic Link:
-
Sprint:Science Pipelines DM-W16-6, Alert Production X16 - 03, Alert Production X16 - 04
-
Team:Alert Production
Description
As part of the requirements document in DM-4155, we need a report-likely section(s) of that same document-on the currently available Wcs libraries (including, but not limited to AST Starlink and astropy.Coordinates) and summaries and references from the current literature about how other surveys and projects have managed their Wcs.
For each of the currently existing options, the report should include at a minimum:
- implementation language.
- API and languages that can interface to that API.
- how well supported (including number of contributors) is the project and how active is ongoing development.
- its performance and optimization for both scalar and vector calculations, and its scalability to large data sets.
We also need to look for and/or request technical reports and other literature from existing and completed surveys, including DES (Robert Gruendl), Pan-STARRS (Paul Price), STScI (Erik Tollerud), and SDSS (Lupton and/or Blanton?).
I'll just make the point here that Starlink AST and astropy.coordinates are not equivalent. AST is more like the STScI gWCS code whereas astropy.coordinates is more like the Perl Astro::Coords module (both are based on ERFA/SOFA). AST can transform J2000 to Galactic and the like but they are generally just how you define the inputs or outputs from a full world coordinate transformation from/to pixels via lots of mappings.