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

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

Updating the documentation to describe the new flaggedChannels functionality.

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