Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • kis_tools kis_tools
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sdc
  • kis_toolskis_tools
  • Issues
  • #282

Closed
Open
Created May 05, 2021 by Carl Schaffer@schafferOwner

wcs wavelength retrieval shifted by one pixel

Philip pointed out to me that the wcs retrieval of wavelengths might be off by one pixel. We narrowed the problem down to the definition of the CRPIXkeyword. We set it to 0 meaning to indicate the beginning of the array, but using the WCS.wcs_pix2world(pixels,0) method to retrieve the value yields a wavelength array with larger by CDELTthan we would expect.

We either need to set the CRPIX keyword to 1 or use 1 for the origin value of the retrieval method.

It is unclear which of these solutions should be preferred.

Links:

  • related issue on github
  • wcs paper
  • astropy docs for WCS.wcs_pix2world
Assignee
Assign to
Time tracking