Creates a one-dimensional profile through an n-dimensional NDF
The samples can be placed at specified positions within the input NDF, or can be spaced evenly along a poly-line joining a set of vertices (see Parameter MODE). The positions of the samples may be saved in an output positions list (see Parameter OUTCAT).
A Domain name such as SKY, AXIS, PIXEL.
An integer value giving the index of the required Frame.
An IRAS90 Sky Co-ordinate System (SCS) values such as "EQUAT(J2000)"
(see SUN/163).
If a null (!
) value is supplied, the positions will be stored in the current Frame. [!]
"1996.8"
, for example). Such values are interpreted as a Besselian epoch if less
than 1984.0 and as a Julian epoch otherwise. ":"
will display details of the required co-ordinate
Frame). The position should be supplied as a list of formatted axis values
separated by spaces. This parameter is only accessed if Parameter MODE is set to
"Curve"
and a null (!
) value is given for INCAT. If the last (top-right) pixel in
the NDF has valid co-ordinates in the current co-ordinate Frame of the NDF,
then these co-ordinates will be used as the suggested default. Otherwise there
will be no suggested default. TRUE
then
the line segments which form the profile will be geodesic curves within the
current co-ordinate Frame of the NDF. Otherwise, the line segments are simple
straight lines. This parameter is only accessed if Parameter MODE is set to
"Curve"
.
As an example, consider a profile consisting of a single line segment which starts at RA=0h
DEC=+80d and finishes
at RA=12h DEC=+80d.
If GEODESIC is FALSE
, the line segment will be a line of constant declination, i.e. the
"straight"
line from the position (0,80) to the position (12, 80), passing through
(1, 80), (2, 80), etc. If GEODESIC is TRUE
, then the line segment will be the curve of
shortest distance on the celestial sphere between the start and end. In this
particaular case, this will be a great circle passing through the north celestial pole.
[FALSE]
!
) is given then Parameters START and FINISH will be used to
obtain the vertex positions. If Parameter MODE is given the value "Curve"
,
then the Parameter INCAT is only accessed if a value is given for it on the
command line (otherwise a null value is assumed). "Curve"
–- The samples are placed evenly along a curve specified by a set of vertices
obtained from the user. The line segments joining these vertices may be linear or
geodesic (see Parameter GEODESIC). Multiple vertices may be supplied using a text file
(see Parameter INCAT). Alternatively, a single line segment can be specified using
Parameters START and FINISH. The number of samples to take along the curve is specified
by Parameter NSAMP.
"Points"
–- The positions at which samples should be taken are given explicitly by
the user in a text file (see Parameter INCAT). No other sample positions are
used.
["Curve"]
"Curve"
. [!]
[!]
":"
will display details of the required
co-ordinate Frame). The position should be supplied as a list of formatted
axis values separated by spaces. This parameter is only accessed if Parameter
MODE is set to "Curve"
and a null (!
) value is given for INCAT. If the first
(bottom-left) pixel in the NDF has valid co-ordinates in the current co-ordinate Frame
of the NDF, then these co-ordinates will be used as the suggested default.
Otherwise there will be no suggested default. "wcsframe my_data pixel"
before running profile. A
FITS binary catalogue is created called samps.FIT
containing the positions
of all samples in the profile, together with information describing all the
co-ordinate Frames in which the positions of the samples are known. This file may be
examined using application LISTSHOW. prof_path.FIT
. Such catalogues can be created (for
example) using application CURSOR. Each line segment is a geodesic curve. The
profile is sampled at 200 points. The samples positions are written to the
output positions list aa.fit
. aa.fit
. Thus, the profiles created by
this example and the previous example will sample the two images allsky and
allsky2 at the same positions and so can be compared directly. This application uses the conventions of the Cursa package for determining the formats
of input and output positions list catalogues. If a file type of .fit is given, then
the catalogue is assumed to be a FITS binary table. If a file type of .txt is given,
then the catalogue is assumed to be stored in a text file in Small Text List (STL)
format. If no file type is given, then .fit
is assumed.
This routine correctly processes the DATA, VARIANCE, WCS, LABEL, TITLE, and UNITS components of the NDF.
All non-complex numeric data types can be handled. Only double-precision floating-point data can be processed directly. Other non-complex data types will undergo a type conversion before the profile is produced.