Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-4156

Evaluate existing Wcs libraries and report on our options

    XMLWordPrintable

Details

    • Story
    • Status: Done
    • Resolution: Done
    • None
    • afw
    • 30
    • Science Pipelines DM-W16-6, Alert Production X16 - 03, Alert Production X16 - 04
    • 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?).

      Attachments

        Issue Links

          Activity

            tjenness Tim Jenness added a comment -

            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.

            tjenness Tim Jenness added a comment - 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.
            tjenness Tim Jenness added a comment -

            A paper on the AST concepts has been submitted to Astronomy & Computing journal and can be found at: https://github.com/dsberry/acast/blob/master/acast.pdf

            tjenness Tim Jenness added a comment - A paper on the AST concepts has been submitted to Astronomy & Computing journal and can be found at: https://github.com/dsberry/acast/blob/master/acast.pdf
            Parejkoj John Parejko added a comment -

            Thanks for the link, Tim. I'll take a look.

            Parejkoj John Parejko added a comment - Thanks for the link, Tim. I'll take a look.
            tjenness Tim Jenness added a comment - STScI gWCS: http://gwcs.readthedocs.org/en/latest/
            Parejkoj John Parejko added a comment -

            The first draft of DMTN-010 will be posted soon.

            Parejkoj John Parejko added a comment - The first draft of DMTN-010 will be posted soon.
            Parejkoj John Parejko added a comment -

            Initial draft of dmtn-010 is on github, with http://dmtn-010.lsst.io built version to appear shortly.

            Parejkoj John Parejko added a comment - Initial draft of dmtn-010 is on github, with http://dmtn-010.lsst.io built version to appear shortly.

            This initial report is fantastic. Thanks for putting this together and being so thorough.

            krughoff Simon Krughoff (Inactive) added a comment - This initial report is fantastic. Thanks for putting this together and being so thorough.

            Live at dmtn-010.lsst.io.

            Parejkoj John Parejko added a comment - Live at dmtn-010.lsst.io.

            People

              Parejkoj John Parejko
              Parejkoj John Parejko
              Simon Krughoff (Inactive)
              John Parejko, Simon Krughoff (Inactive), Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jenkins

                  No builds found.