Table of Contents
ccdslice - takes slices and/or re-orient an image cube
ccdslice takes slices from an image cube,
along any (orthogonal) axis and can thereby also reorder the axes, or remove
a redundant axis.
A chain of ccdslice has to be applied if the first (x)
or second (y) axis needs to be reduced but the ordering of the cube coordinates
to remain the same (see EXAMPLES below), see also ccdsub(1NEMO)
for a better
can also remove redundant ("dummy") axes when
writing out a fits(5NEMO)
The following parameters are recognized
in any order if the keyword is also given:
Here is a cube, in which only the 2nd plane (z=1) is selected,
- Input filename, in image(5NEMO)
format. [no default]
- Output filename [no default]
- Slice variable
(x, y, or z), along which axis the cube is sliced. This axis will then become
the 3rd axis. [z].
- Slices to select. Multiple planes can be selected,
but must be in the range 1..NzvaR. If none given, all planes will be selected.
expression can be given, but only regular ranges will
result in a correct coordinate system. Default: the whole zvar axis is extracted.
ccdslice cube.in cube.out z 2
here is a cube which is re-oriented in YZX:
ccdslice cube.in cube.out x
and here a somewhat cumbersome three-step process to select a subset of
the X axis, but leaving the cube intact:
ccdslice cube.in - x 2:10:2 | ccdslice - - x | ccdslice - cube.out x
and the same for selecting a subset of the Y axis, now in two steps:
ccdslice cube.in - y 2:10:2 | ccdslice - cube.out y
This code depends on the fact that the data is 3-dimensional,
i.e. an image cube. This is a limitation of the image(5NEMO)
system description of the new zvar axis can easily be corrupted by choosing
an irregular layout with xrange=.
6-May-95 V1.0 Created PJT
Table of Contents