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
  • #271

Closed
Open
Created Mar 22, 2021 by Carl Schaffer@schafferOwner

clean GRIS header

After discussing with Manolo and Carlos while working on the slit orientation issue I found out that some of the values we are propagating in the GRIS header are not correct, they might:

  • be historic values such as SLITORIE which do not have a well-defined or obvious function
  • be values that apply only to observations but not single slit positions (e.g. AZIMUT, ELEVATION)
  • be unreliable due to different ephemerides code used for producing them/not be compliant with the telescope's definitions (again AZIMUTH)

For fully consistent headers, we would need to go through each value, assess the definition and validity, document that and throw out all confusing values.

Assignee
Assign to
Time tracking