source: trunk/docs/app-param.tex @ 1322

Last change on this file since 1322 was 1322, checked in by MatthewWhiting, 11 years ago

Ticket #207 - Adding the data type & range/format information to the User Guide.

File size: 25.5 KB
Line 
1% -----------------------------------------------------------------------
2% app-param.tex: Section listing all the possible input parameters and
3%                their defaults.
4% -----------------------------------------------------------------------
5% Copyright (C) 2006, Matthew Whiting, ATNF
6%
7% This program is free software; you can redistribute it and/or modify it
8% under the terms of the GNU General Public License as published by the
9% Free Software Foundation; either version 2 of the License, or (at your
10% option) any later version.
11%
12% Duchamp is distributed in the hope that it will be useful, but WITHOUT
13% ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
14% FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
15% for more details.
16%
17% You should have received a copy of the GNU General Public License
18% along with Duchamp; if not, write to the Free Software Foundation,
19% Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA
20%
21% Correspondence concerning Duchamp may be directed to:
22%    Internet email: Matthew.Whiting [at] atnf.csiro.au
23%    Postal address: Dr. Matthew Whiting
24%                    Australia Telescope National Facility, CSIRO
25%                    PO Box 76
26%                    Epping NSW 1710
27%                    AUSTRALIA
28% -----------------------------------------------------------------------
29\secA{Available parameters}
30\label{app-param}
31
32The full list of parameters that can be listed in the input file are
33given here. If not listed, they take the default value given in
34parentheses. Since the order of the parameters in the input file does
35not matter, they are grouped here in logical sections.
36
37\secB*{Input related}
38\begin{Lentry}
39\item[{ImageFile [no default | string | filename]}] The filename of
40  the data cube to be analysed.
41\item[{flagSubsection [false | bool | true/false/1/0]}] A flag to
42  indicate whether one wants a subsection of the requested image.
43\item[{Subsection [full field | string | Subsection string]}] The
44  requested subsection -- see \S\ref{sec-input} for details on the
45  subsection format.  If the full range of a dimension is required,
46  use a \texttt{*} (thus the default is the full cube).
47\item[{flagReconExists [false | bool | true/false/1/0]}] A flag to
48  indicate whether the reconstructed array has been saved by a
49  previous run of \duchamp. If set true, the reconstructed array will
50  be read from the file given by \texttt{reconFile}, rather than
51  calculated directly.
52\item[{reconFile [no default | string | filename]}] The FITS file that
53  contains the reconstructed array. If \texttt{flagReconExists} is
54  true and this parameter is not defined, the default file that is
55  looked for will be determined by the \atrous parameters (see
56  \S\ref{sec-recon}).
57\item[{flagSmoothExists [false | bool | true/false/1/0]}] A flag to
58  indicate whether the Hanning-smoothed array has been saved by a
59  previous run of \duchamp. If set true, the smoothed array will be
60  read from the file given by \texttt{smoothFile}, rather than
61  calculated directly.
62\item[{smoothFile [no default | string | filename]}] The FITS file
63  that has a previously smoothed array. If \texttt{flagSmoothExists}
64  is true and this parameter is not defined, the default file that is
65  looked for will be determined by the smoothing parameters (see
66  \S\ref{sec-smoothing}).
67\item[{usePrevious [false | bool | true/false/1/0]}] A flag to
68  indicate that \duchamp should read the list of objects from a
69  previously-created log file, rather than doing the searching
70  itself. The set of outputs will be created according to the flags in
71  the following section.
72\item[{objectList [no default | string | comma-separated list]}] When
73  \texttt{usePrevious=true}, this list is used to output individual
74  spectral plots, as well as a postscript file for all spectral plots
75  as given by \texttt{SpectraFile}. The filenames of the plots will be
76  the same as \texttt{SpectraFile}, but with -XX at the end, where XX
77  is the object number (\eg \texttt{duchamp-Spectra-07.ps}). The
78  format of the parameter value should be a string listing individual
79  objects or object ranges: \eg 1,2,4-7,8,14.
80\end{Lentry}
81
82\secB*{Output related}
83\begin{Lentry}
84\item[{OutFile [duchamp-\\Results.txt | string | filename]}] The file
85  containing the final list of detections. This also records the list
86  of input parameters.
87\item[{flagSeparateHeader [false | bool | true/false/1/0]}] A flag to
88  indicate that the header information that would normally be printed
89  at the start of the results file (containing information on the
90  parameters, image statistics and number of detections) should
91  instead be written to a separate file.
92\item[{HeaderFile [duchamp-\\Results.hdr | string | filename]}] The
93  file to which the header information should be written when
94  \texttt{flagSeparateHeader=true}.
95\item[{flagWriteBinaryCatalogue [true | bool | true/false/1/0]}]
96  Whether to write a binary catalogue of the detections, for later
97  re-use (see \S\ref{sec-reuse} for details).
98\item[{binaryCatalogue [duchamp-Catalogue.dpc | string | filename]}]
99  The filename for the binary catalogue.
100\item[{flagPlotSpectra [true | bool | true/false/1/0]}] Whether to
101  produce a postscript file containing spectra of all detected
102  objects. If PGPlot has not been enabled, this parameter defaults to
103  \texttt{false}.
104\item[{SpectraFile [duchamp-\\Spectra.ps | string | filename]}] The
105  postscript file that contains the resulting integrated spectra and
106  images of the detections.
107\item[{flagPlotIndividualSpectra [false | bool | true/false/1/0]}]
108  Whether to produce individual spectral plots for listed sources.
109\item[{flagTextSpectra [false | bool | true/false/1/0]}] A flag to say
110  whether the spectra should be saved in text form in a single
111  file. See below for a description.
112\item[{spectraTextFile [duchamp-\\Spectra.txt | string | filename]}]
113  The file containing the spectra of each object in ascii format. This
114  file will have a column showing the spectral coordinates, and one
115  column for each of the detected objects, showing the flux values as
116  plotted in the graphical output of \texttt{spectraFile}.
117\item[{flagLog [false | bool | true/false/1/0]}] A flag to indicate
118  whether the details of intermediate detections should be logged.
119\item[{LogFile [duchamp-\\Logfile.txt | string | filename]}] The file
120  in which intermediate detections and the pixel content of the final
121  list of detections are logged. These are detections that have not
122  been merged. This is primarily for use in debugging and diagnostic
123  purposes: normal use of the program will probably not require it.
124\item[{flagOutputMomentMap [false | bool | true/false/1/0]}] A flag to
125  say whether or not to save a FITS file containing the moment-0 map.
126\item[fileOutputMomentMap{ [see text | string | filename]}] The file
127  to which the moment-0 array is written. If left blank (the default),
128  the naming scheme detailed in \S\ref{sec-momentOut} is used.
129\item[{flagOutputMomentMask [false | bool | true/false/1/0]}] A flag
130  to say whether or not to save a FITS file containing the moment-0
131  mask (a mask showing which spatial pixels are detected in one or
132  more channels).
133\item[fileOutputMomentMask{ [see text | string | filename]}] The file
134  to which the moment-0 mask is written. If left blank (the default),
135  the naming scheme detailed in \S\ref{sec-maskOut} is used.
136\item[{flagOutputMask [false | bool | true/false/1/0]}] A flag to say
137  whether or not to save a FITS file containing a mask array, with
138  values 1 where there is a detected object and 0 elsewhere.
139\item[fileOutputMask{ [see text | string | filename]}] The file to
140  which the mask array is written. If left blank (the default), the
141  naming scheme detailed in \S\ref{sec-maskOut} is used.
142\item[{flagMaskWithObjectNum [false | bool | true/false/1/0]}] If this
143  flag is true, the detected pixels in the mask image have the
144  corresponding object ID as their value. If false, they have the
145  value 1. All non-detected pixels have the value 0.
146\item[{flagOutputRecon [false | bool | true/false/1/0]}] A flag to say
147  whether or not to save the reconstructed cube as a FITS file.
148\item[fileOutputRecon{ [see text | string | filename]}] The file to
149  which the reconstructed array is written. If left blank (the
150  default), the naming scheme detailed in \S\ref{sec-reconIO} is used.
151\item[{flagOutputResid [false | bool | true/false/1/0]}] As for
152  \texttt{flagOutputRecon}, but for the residual array -- the
153  difference between the original cube and the reconstructed cube.
154\item[fileOutputResid{ [see text | string | filename]}] The file to
155  which the residual array is written. If left blank (the default),
156  the naming scheme detailed in \S\ref{sec-reconIO} is used.
157\item[{flagOutputSmooth [false | bool | true/false/1/0]}] A flag to
158  say whether or not to save the smoothed cube as a FITS file.
159\item[fileOutputSmooth{ [see text | string | filename]}] The file to
160  which the smoothed array is written. If left blank (the default),
161  the naming scheme detailed in \S\ref{sec-reconIO} is used.
162\item[{flagOutputBaseline [false | bool | true/false/1/0]}] A flag to
163  say whether or not to save the cube of spectral baseline values as a
164  FITS file.
165\item[fileOutputBaseline{ [see text | string | filename]}] The file to
166  which the baseline values are written. If left blank (the default),
167  the naming scheme detailed in \S\ref{sec-baselineOut} is used.
168\item[{flagVOT [false | bool | true/false/1/0]}] A flag to say whether
169  to create a VOTable file with the detection information. This will
170  be an XML file in the Virtual Observatory VOTable format.
171\item[{votFile [duchamp-\\Results.xml | string | filename]}] The
172  VOTable file with the list of final detections. Some input
173  parameters are also recorded.
174\item[{flagKarma [false | bool | true/false/1/0]}] A flag to say
175  whether to create a Karma annotation file corresponding to the
176  information in \texttt{outfile}. This can be used as an overlay in
177  Karma programs such as \texttt{kvis}.
178\item[{karmaFile [duchamp-\\Results.ann | string | filename]}] The
179  Karma annotation file showing the list of final detections.
180\item[{flagDS9 [false | bool | true/false/1/0]}] A flag to say whether
181  to create a DS9 region file corresponding to the information in
182  \texttt{outfile}. This can be used as an overlay in SAOImage DS9 or
183  casaviewer.
184\item[{ds9File [duchamp-\\Results.ann | string | filename]}] The DS9
185  region file showing the list of final detections.
186\item[{flagCasa [false | bool | true/false/1/0]}] A flag to say
187  whether to create a CASA region file corresponding to the
188  information in \texttt{outfile}. This can be used as an overlay in
189  casaviewer (when this functionality is available) or import into
190  casapy.
191\item[{casaFile [duchamp-\\Results.crf | string | filename]}] The CASA
192  region file showing the list of final detections.
193\item[{annotationType [borders | string | borders/circles/ellipses]}]
194  Which type of annotation plot to use. Specifying ``borders'' gives
195  an outline around the detected spatial pixels, ``circles'' gives a
196  circle centred on the centre of the object with radius large enough
197  to encompass all spatial pixels, and ``ellipses'' gives an ellipse
198  centred on the centre of the object of size given by the MAJ, MIN \&
199  PA values.
200\item[{flagMaps [true | bool | true/false/1/0]}] A flag to say whether
201  to save postscript files showing the 0th moment map of the whole
202  cube (\texttt{momentMap}) and the detection image
203  (\texttt{detectionMap}). If PGPlot has not been enabled, this
204  parameter defaults to \texttt{false}.
205\item[{momentMap [duchamp-\\MomentMap.ps | string | filename]}] A
206  postscript file containing a map of the 0th moment of the detected
207  sources, as well as pixel and WCS coordinates.
208\item[{detectionMap [duchamp-\\DetectionMap.ps | string | filename]}]
209  A postscript file with a map showing each of the detected objects,
210  coloured in greyscale by the number of detected channels in each
211  spatial pixel. Also shows pixel and WCS coordinates.
212\item[{flagXOutput [true | bool | true/false/1/0]}] A flag to say
213  whether to display a 0th moment map in a PGPlot X-window. This will
214  be in addition to any that are saved to a file. This parameter can
215  be overridden by the use of the \texttt{-x} command-line option,
216  which disables the X-windows output. If PGPlot has not been enabled,
217  this parameter defaults to \texttt{false}.
218\item[{newFluxUnits [no default | string | units string]}] Flux units
219  that the pixel values should be converted into. These should be
220  directly compatible with the units in the FITS header, given by the
221  BUNIT keyword.
222\item[{precFlux [3 | int | $> 0$]}] The desired precision (\ie number
223  of decimal places) for flux values given in the output files and
224  tables.
225\item[{precVel [3 | int | $> 0$]}] The desired precision (\ie number
226  of decimal places) for velocity/frequency values given in the output
227  files and tables.
228\item[{precSNR [2 | int | $> 0$]}] The desired precision (\ie number
229  of decimal places) for the peak SNR value given in the output files
230  and tables.
231\end{Lentry}
232
233\secB*{Modifying the cube}
234\begin{Lentry}
235\item[{flagTrim [false | bool | true/false/1/0]}] A flag to say
236  whether to trim BLANK pixels from the edges of the cube -- these are
237  typically pixels set to some particular value because they fall
238  outside the imaged area, and trimming them can help speed up the
239  execution.
240\item[{flaggedChannels [no default | string | comma-separated list]}]
241  Channels that are to be ignored by the source-finding. These should
242  be specified by a comma-separated list of single values and ranges,
243  such as 1,3,6-12,18. Channel numbers are zero-based, so that the
244  first channel in the cube has value 0.
245\item[{flagBaseline [false | bool | true/false/1/0]}] A flag to say
246  whether to remove the baseline from each spectrum in the cube for
247  the purposes of reconstruction and detection.
248\item[{baselineType [atrous | string | atrous/median]}] The algorithm
249  used to calculate the spectral baseline. Only \texttt{atrous} or
250  \texttt{median} are accepted.
251\item[{baselineBoxWidth [51 | int | odd integer $> 0$]}] The box width
252  used by the \texttt{median} baseline algorithm. Needs to be odd - if
253  even, it will be incremented by one.
254\end{Lentry}
255
256\secB*{Detection related}
257
258\secC*{General detection}
259\begin{Lentry}
260\item[{searchType [spatial | string | spectral/spatial]}] How the
261  searches are done. Only ``spatial'' and ``spectral'' are accepted. A
262  value of ``spatial'' means each 2D channel map is searched, whereas
263  ``spectral'' means each 1D spectrum is searched.
264\item[{flagStatSec [false | bool | true/false/1/0]}] A flag indicating
265  whether the statistics should be calculated on a subsection of the
266  cube, rather than the full cube. Note that this only applies to the
267  statistics used to determine the threshold, and not for other
268  statistical calculations (such as those in the reconstruction
269  phase).
270\item[{StatSec [full field | string | Subsection string]}] The
271  subsection of the cube used for calculating statistics -- see
272  \S\ref{sec-input} for details on the subsection format. Only used if
273  \texttt{flagStatSec=true}.
274\item[{flagRobustStats [true | bool | true/false/1/0]}] A flag
275  indicating whether to use the robust statistics (median and MADFM)
276  to estimate the noise parameters of the cube, rather than the mean
277  and rms. See \S\ref{sec-stats} for details.
278\item[{flagNegative [false | bool | true/false/1/0]}] A flag
279  indicating that the features of interest are negative. The cube is
280  inverted prior to searching.
281\item[{snrCut [5. | float | any]}] The threshold, in multiples of
282  $\sigma$ above the mean.
283\item[{threshold [no default | float | any]}] The actual value of the
284  threshold. Normally the threshold is calculated from the cube's
285  statistics, but the user can manually specify a value to be used
286  that overrides the calculated value. If this is not specified, the
287  calculated value is used, but this value will take precedence over
288  other means of calculating the threshold (\ie via \texttt{snrCut} or
289  the FDR method).
290\item[{flagGrowth [false | bool | true/false/1/0]}] A flag indicating
291  whether or not to grow the detected objects to a smaller threshold.
292\item[{growthCut [3. | float | any]}] The smaller threshold using in
293  growing detections. In units of $\sigma$ above the mean.
294\item[{growthThreshold [no default | float | any]}] Alternatively, the
295  threshold to which detections are grown can be specified in flux
296  units (in the same manner as the \texttt{threshold} parameter). When
297  the \texttt{threshold} parameter is given, this option \textbf{must}
298  be used instead of \texttt{growthCut}.
299\item[{beamFWHM [0. | float | $> 0.$]}] The full-width at half maximum
300  of the beam, in pixels.  If the header keywords BMAJ and BMIN are
301  present, then these will be used to calculate the beam area, and
302  this parameter will be ignored. This will take precedence over
303  \texttt{beamArea} (but is ignored if not specified).
304\item[{beamArea [0. | float | $> 0.$]}] The \textbf{area} of the beam
305  in pixels (\ie how many pixel does the beam cover?). As above, if
306  the header keywords BMAJ and BMIN are present, then these will be
307  used to calculate the beam area, and this parameter will be ignored.
308\end{Lentry}
309
310\secC*{\Atrous reconstruction}
311\begin{Lentry}
312\item[{flagATrous [false | bool | true/false/1/0]}] A flag indicating
313  whether or not to reconstruct the cube using the \atrous wavelet
314  reconstruction. See \S\ref{sec-recon} for details.
315\item[{reconDim [1 | int | $> 0$]}] The number of dimensions to use in
316  the reconstruction. 1 means reconstruct each spectrum separately, 2
317  means each channel map is done separately, and 3 means do the whole
318  cube in one go.
319\item[{scaleMin [1 | int | $> 0$]}] The minimum wavelet scale to be
320  used in the reconstruction. A value of 1 means ``use all scales''.
321\item[{scaleMax [0 | int | any]}] The maximum wavelet scale to be used
322  in the reconstruction. If the value is $\le0$ then the maximum scale
323  is calculated from the size of the input array. Similarly, if the
324  value given is larger than this calculated value, the calculated
325  value is used instead.
326\item[{snrRecon [4 | float | $> 0$]}] The thresholding cutoff used in
327  the reconstruction -- only wavelet coefficients at least this many
328  $\sigma$ above the mean are included in the reconstruction.
329\item[{reconConvergence [0.005 | float | $> 0.$]}] The convergence
330  criterion used in the reconstruction. The \atrous algorithm iterates
331  until the relative change in the standard deviation of the residuals
332  is less than this amount.
333\item[{filterCode [1 | int | 1/2/3]}] The code number of the filter to
334  use in the reconstruction. The options are:
335  \begin{itemize}
336  \item \textbf{1:} B$_3$-spline filter: coefficients =
337    $(\frac{1}{16}, \frac{1}{4}, \frac{3}{8}, \frac{1}{4}, \frac{1}{16})$
338  \item \textbf{2:} Triangle filter: coefficients =
339    $(\frac{1}{4}, \frac{1}{2}, \frac{1}{4})$
340  \item \textbf{3:} Haar wavelet: coefficients =
341    $(0, \frac{1}{2}, \frac{1}{2})$
342  \end{itemize}
343\end{Lentry}
344
345\secC*{Smoothing the cube}
346\begin{Lentry}
347\item[{flagSmooth [false | bool | true/false/1/0]}] A flag indicating whether to
348  smooth the cube. See \S\ref{sec-smoothing} for details.
349\item[{smoothType [spectral | string | spectral/spatial]}] The
350  smoothing method used: either ``spectral'' (with a 1D Hanning
351  filter) or ``spatial'' (with a 2D Gaussian filter).
352\item[{hanningWidth [5 | int | $> 0$]}] The width of the Hanning
353  smoothing kernel.
354\item[{kernMaj [3 | float | $> 0.$]}] The full-width-half-maximum
355  (FWHM), in pixels, of the 2D Gaussian smoothing kernel's major axis.
356\item[{kernMin [3 | float | $> 0.$]}] The FWHM (in pixels) of the 2D Gaussian smoothing kernel's
357  minor axis.
358\item[{kernPA [0 | float | any]}] The position angle, in degrees,
359  anticlockwise from vertical (\ie usually East of North).
360\item[{smoothEdgeMethod [equal | string | equal/truncate/scale]}] What
361  method to use for dealing with pixels on the edge of the spatial
362  image (\ie within the width of the kernel). Can be one of
363  \texttt{equal, truncate, scale}. See \S\ref{sec-smoothing} for
364  details.
365\item[{spatialSmoothCutoff [1.e-10 | float | $> 0.$]}] The cutoff
366  value for determining the width of the smoothing kernel. See
367  \S\ref{sec-smoothing} for details.
368\end{Lentry}
369
370\secC*{FDR method}
371\begin{Lentry}
372\item[{flagFDR [false | bool | true/false/1/0]}] A flag indicating whether or not to use
373  the False Discovery Rate method in thresholding the pixels.
374\item[{alphaFDR [0.01 | float | $0. - 1.$]}] The $\alpha$ parameter used in the FDR
375  analysis. The average number of false detections, as a fraction of
376  the total number, will be less than $\alpha$ (see
377  \S\ref{sec-detection}).
378\item[{FDRnumCorChan [2 | int | $> 0$]}] The number of neighbouring spectral
379  channels that are assumed to be correlated. This is needed by the
380  FDR algorithm to calculate the normalisation constant $c_N$ (see
381  \S\ref{sec-detection}).
382\end{Lentry}
383
384\secC*{Merging detections}
385\begin{Lentry}
386\item[{minPix [2 | int | $> 0$]}] The minimum number of spatial pixels for a
387  single detection to be counted.
388\item[{minChannels [3 | int | $> 0$]}] At least one contiguous set of this many
389  channels must be present in the detection for it to be accepted.
390\item[{minVoxels [minPix$+$minChannels$-$1 | int | $> 0$]}] The minimum size of
391  the object, in terms of the total number of voxels, for it to be
392  accepted. This will be \textit{at least} minPix$+$minChannels$-$1,
393  but can be set higher.
394\item[{maxPix [$-1$ | int | any]}] The maximum number of spatial pixels an object
395  can have. No check is made if the value is negative.
396\item[{maxChannels [-1 | int | any]}] The maximum number of channels an object can
397  have. No check is made if the value is negative.
398\item[{maxVoxels [$-1$ | int | any]}] The maximum size of
399  the object, in terms of the total number of voxels, for it to be
400  accepted. No check is made if the value is negative.
401\item[{flagRejectBeforeMerge [false | bool | true/false/1/0]}] A flag
402  indicating whether to reject sources that fail to meet the
403  \texttt{minPix} or \texttt{minChannels} criteria \textbf{before} the
404  merging stage. Default behaviour is to do the rejection last.
405\item[{flagTwoStageMerging [true | bool | true/false/1/0]}] A flag
406  indicating whether to do an initial merge of newly-detected sources
407  into the source list as they are found. If \texttt{false}, new
408  sources are simply added to the end of the list for later merging.
409\item[{flagAdjacent [true | bool | true/false/1/0]}] A flag indicating
410  whether to use the ``adjacent pixel'' criterion to decide whether to
411  merge objects. If not, the next two parameters are used to determine
412  whether objects are within the necessary thresholds.
413\item[{threshSpatial [$3.$ | float | $\ge 0$]}] The maximum allowed
414  minimum spatial separation (in pixels) between two detections for
415  them to be merged into one. Only used if \texttt{flagAdjacent =
416    false}.
417\item[{threshVelocity [$7.$ | float | $\ge 0$]}] The maximum allowed
418  minimum channel separation between two detections for them to be
419  merged into one.
420\end{Lentry}
421
422\secC*{WCS parameters}
423\begin{Lentry}
424\item[{spectralType ["" | string | A valid WCS type]}] The user can
425  specify an alternative WCS spectral type that the spectral axis can
426  be expressed in. This specification should conform to the standards
427  described in \citet{greisen06}, although it is possible to provide
428  just the first four letters (the ``S-type'', \eg 'VELO').
429\item[{restFrequency [-1 | float | any]}] If provided, this will be used in
430  preference to the rest frequency given in the FITS header to
431  calculate velocities and related quantities. A negative value (such
432  as the default) will mean this is not used and the FITS header
433  value, if present, is used instead.
434\item[{spectralUnits ["" | string | A valid units string]}] The user
435  can specify the units of the spectral axis, overriding those given
436  in the FITS header. If the spectral type is being changed, these
437  units should be appropriate for that quantity. If not provided, the
438  FITS header information is used.
439\end{Lentry}
440
441\secC*{Other parameters}
442\begin{Lentry}
443\item[{spectralMethod [peak | string | peak/sum]}] This indicates
444  which method is used to plot the output spectra: \texttt{peak} means
445  plot the spectrum containing the detection's peak pixel;
446  \texttt{sum} means sum the spectra of each detected spatial pixel,
447  and correct for the beam size. Any other choice defaults to
448  \texttt{peak}.
449\item[{pixelCentre [centroid | string | centroid/peak/average]}] Which
450  of the three ways of expressing the ``centre'' of a detection (see
451  \S\ref{sec-results} for a description of the options) to use for the
452  X, Y, \& Z columns in the output list. Alternatives are:
453  \texttt{centroid, peak, average}.
454\item[{sortingParam [vel | string | see text for options]}] The
455  parameter on which to sort the output list of detected
456  objects. Options are: xvalue, yvalue, zvalue, ra, dec, vel, w50,
457  iflux, pflux (integrated and peak flux respectively), or snr. If the
458  parameter begins with a '-' (\eg '-vel'), the order of the sort is
459  reversed.
460\item[{drawBorders [true | bool | true/false/1/0]}] A flag indicating whether to draw
461  borders around the detected objects in the moment maps included in
462  the output (see for example Fig.~\ref{fig-spect}).
463\item[{drawBlankEdges [true | bool | true/false/1/0]}] A flag indicating whether to
464  draw the dividing line between BLANK and non-BLANK pixels on the
465  2D images (see for example Fig.~\ref{fig-moment}).
466\item[{verbose [true | bool | true/false/1/0]}] A flag indicating whether to print the
467  progress of any computationally intensive algorithms (\eg
468  reconstruction, searching or merging algorithms) to the screen.
469\end{Lentry}
470
471
472%%% Local Variables:
473%%% mode: latex
474%%% TeX-master: "Guide"
475%%% End:
Note: See TracBrowser for help on using the repository browser.