These scripts provide short-cuts for commonly used kappa commands with
ACSIS data. Just run the commands without any parameters to see a
brief help:

  sp_get   : copy acsis file from observation directory to the
             local dir and do a 'sp_axis ... vrad'

  sp_axis  : set an old-style spectral axis (pixel, freq, vrad etc.)

  sp_trim  : trim noisy channels off the edges. NOTE: the boundaries
             now are in spectral axis units NOT channels!

  sp_coadd : coadd spectra. It will do a sp_get for any files not
             found locally.

  sp_merge : frequency-merge two cubes with a DC adjustment of each
             spectrum determined from the overlap.

  sp_plot  : plot a spectrum optionally overlaying a second one.
             sp_plot now understand starlink slices like:
             sp_plot ac20061026_00044_01_01_trim'(~1,~1)' 263.5 264

  sp_bsl   : remove a baseline

  sp_bin   : bin over a number of channels

  sp_stats : combined stats over one or more ranges.
             sp_stats now understand starlink slices like:
             sp_stats ac20061026_00044_01_01_trim'(~1,~1)' -200 -100 100 200

  sp_col   : collapse cube over velocity/freq range

Details:

     === sp_get ===

     sp_get obsnr1 obsnr2 ...
     e.g. 'sp_get 10 11 13 15'

     Get a spectra file and run makecube on it.
     set the variable obsdate to the correct obsdate of
     the files to copy. E.g. 'setenv obsdate 20061025'
     sp_get will do a 'sp_axis .. vrad' on the resulting file.

     === sp_axis ===

     sp_axis file axis
     e.g. 'sp_axis myfile [pix | freq | vrad | vopt | velo | red]'

     Axis names: pixel, freq, vrad, vopt, velo, redshift

     === sp_trim ===

     sp_trim file [nunits1 [nunits2]]
     e.g. 'sp_trim myfile 100'

     Trims off channels from the edges of the spectrum.
     Nunits is in units of the spectral axis as set by sp_axis.
     The default is 50 pixels/kms-1/Ghz. With only one value
     the same number of channels is trimmed from each side.

     === sp_coadd ===

     sp_get obsnr1 obsnr2 ...
     e.g. 'sp_get 10 11 13 15'

     Get a spectra file and run makecube on it.
     set the variable obsdate to the correct obsdate of
     the files to copy. E.g. 'setenv obsdate 20061025'
     sp_get will do a 'sp_axis .. vrad' on the resulting file.

     === sp_merge ===

     sp_merge file1 file2 outfile [nodisplay]

     Merge two cubes in frequency by adjusting for the DC offset in
     the overlap region of the spectra before using wcsmosaic to
     combine them.  The DC levels are determined from the median in
     the overlap region of each spectrum. If there is no overlap
     between the cubes the median over the full frequency range of
     each cube is used instead.

     === sp_plot ===

     sp_plot file1 [file2] [xleft xright] [linplot options]

     Plot spectrum of file 1, with optionally file 2 overlayed in red.
     There is limited support for Starlink sections: a command like
         sp_plot myfile'(~1,~1)' -200 200     will result
     a plot of:  myfile'(~1,~1,-200.:200.)'
     i.e. the boundaries get appended to any section specified in
     the filename. Linplot options can be added to the end of the
     line e.g. ybot=-1 ytop=10. Ones that require quotes probably
     won't work.

     === sp_bsl ===

     sp_bsl file order v1:v2 [[v3:v4] ...]
     e.g. 'sp_bsl myfile 1 -300:-100 100:300 ...'

     Note: the boundaries must be in increasing order!

     === sp_bin ===

     sp_bin file nchan
     e.g. 'sp_bin myfile 10'

     === sp_stats ===

     sp_stats file v1:v2 [[v3:v4] ...]
     e.g. 'sp_stats myfile -300:-100 100:300 ...'

     Note: the boundaries must be in increasing order!
     There is limited support for Starlink sections: a command like
         sp_stats myfile'(~1,~1)' -200 -100 100 200 will result
     in the combined stats of:
                 myfile'(~1,~1,-200.:-100.)' and myfile'(~1,~1,100.:200.)' 
     i.e. the boudaries get appended to any section specified in
     the filename.

     Note: the boundaries must be in increasing order!

     === sp_col ===

     sp_col  file  v1:v2
     e.g. 'sp_col myfile -300:-100'

     Note: the boundaries must be in increasing order!

 (version 20080207)