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

Closed
Open
Created Jul 25, 2019 by Carl Schaffer@schafferOwner

lars wavelength

Lars l1 files do not contain a Wavelength keyword by default. JLB provided a dirty fix:

; Routine to add the correct wavelength to a given LARS fits file

PRO ldrc_insert_wavelength, file

data=readfits(file,hdr)
lam =mrdfits(file,1,h1)
meta=mrdfits(file,2,h2)
lambda = round(mean(lam)*1d10)

;;copy par and insert value
val = sxpar (hdr, 'WAVELNTH', comment=comment, count=count)
print,'Adding Wavelength',lambda,' to ',file
fxaddpar, hdr, 'WAVELNTH', lambda, comment

mwrfits, data, file, hdr,  iscale=[1, 32768], /silent, /create
mwrfits, lam, file, h1, /silent
mwrfits, meta, file, h2, /silent

END

This fix works for adding wavelengths to *chvtt.fits files. On the long run, this should be added to the LARS pipeline.

Assignee
Assign to
Time tracking