source: tags/release-1.1.12/docs/app-param.tex

Last change on this file was 840, checked in by MatthewWhiting, 13 years ago

Adding explanation about default behaviour of parameters when PGPLOT is not enabled.

File size: 19.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]}] 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[{flagPlotSpectra [true]}] Whether to produce a postscript file
92  containing spectra of all detected objects. If PGPlot has not been
93  enabled, this parameter defaults to \texttt{false}.
94\item[{SpectraFile [duchamp-\\Spectra.ps]}] The postscript file
95  containing the resulting integrated spectra and images of the
96  detections.
97\item[{flagTextSpectra [false]}] A flag to say whether the spectra
98  should be saved in text form in a single file. See below for a
99  description.
100\item[{spectraTextFile [duchamp-\\Spectra.txt]}] The file containing
101  the spectra of each object in ascii format. This file will have a
102  column showing the spectral coordinates, and one column for each of
103  the detected objects, showing the flux values as plotted in the
104  graphical output of \texttt{spectraFile}.
105\item[{flagLog [false]}] A flag to indicate whether the
106  details of intermediate detections should be logged.
107\item[{LogFile [duchamp-\\Logfile.txt]}] The file in which
108  intermediate detections are logged. These are detections that have
109  not been merged. This is primarily for use in debugging and
110  diagnostic purposes: normal use of the program will probably not
111  require it.
112\item[{flagOutputMomentMap [false]}] A flag to say whether or not to save a
113  FITS file containing the moment-0 map.
114\item[fileOutputMomentMap{ [see text]}] The file to which the moment-0 array is
115  written. If left blank (the default), the naming scheme detailed in
116  Section~\ref{sec-maskOut} is used.
117\item[{flagOutputMask [false]}] A flag to say whether or not to save a
118  FITS file containing a mask array, with values 1 where there is a
119  detected object and 0 elsewhere.
120\item[fileOutputMask{ [see text]}] The file to which the mask array is
121  written. If left blank (the default), the naming scheme detailed in
122  Section~\ref{sec-maskOut} is used.
123\item[{flagMaskWithObjectNum [false]}] If this flag is true, the
124  detected pixels in the mask image have the corresponding object ID
125  as their value. If false, they have the value 1. All non-detected
126  pixels have the value 0.
127\item[{flagOutputRecon [false]}] A flag to say whether or not
128  to save the reconstructed cube as a FITS file.
129\item[fileOutputRecon{ [see text]}] The file to which the reconstructed array
130  is written. If left blank (the default), the naming scheme detailed
131  in Section~\ref{sec-reconIO} is used.
132\item[{flagOutputResid [false]}] As for
133  \texttt{flagOutputRecon}, but for the residual array -- the
134  difference between the original cube and the reconstructed cube.
135\item[fileOutputResid{ [see text]}] The file to which the residual array
136  is written. If left blank (the default), the naming scheme detailed
137  in Section~\ref{sec-reconIO} is used.
138\item[{flagOutputSmooth [false]}] A flag to say whether or not
139  to save the smoothed cube as a FITS file.
140\item[fileOutputSmooth{ [see text]}] The file to which the smoothed array
141  is written. If left blank (the default), the naming scheme detailed
142  in Section~\ref{sec-reconIO} is used.
143\item[{flagVOT [false]}] A flag to say whether to create a
144  VOTable file with the detection information. This will be an XML
145  file in the Virtual Observatory VOTable format.
146\item[{votFile [duchamp-\\Results.xml]}] The VOTable file with
147  the list of final detections. Some input parameters are also
148  recorded.
149\item[{flagKarma [false]}] A flag to say whether to create a
150  Karma annotation file corresponding to the information in
151  \texttt{outfile}. This can be used as an overlay in Karma
152  programs such as \texttt{kvis}.
153\item[{karmaFile [duchamp-\\Results.ann]}] The Karma annotation
154  file showing the list of final detections.
155\item[{annotationType [borders]}] Which type of annotation plot to
156  use. Specifying ``borders'' gives an outline around the detected
157  spatial pixels, while ``circles'' gives a circle centred on the
158  centre of the object with radius large enough to encompass all
159  spatial pixels.
160\item[{flagMaps [true]}] A flag to say whether to save postscript
161  files showing the 0th moment map of the whole cube (parameter
162  \texttt{momentMap}) and the detection image
163  (\texttt{detectionMap}). If PGPlot has not been enabled, this
164  parameter defaults to \texttt{false}.
165\item[{momentMap [duchamp-\\MomentMap.ps]}] A postscript file
166  containing a map of the 0th moment of the detected sources, as well
167  as pixel and WCS coordinates.
168\item[{detectionMap [duchamp-\\DetectionMap.ps]}] A postscript
169  file with a map showing each of the detected objects, coloured in
170  greyscale by the number of detected channels in each spatial
171  pixel. Also shows pixel and WCS coordinates.
172\item[{flagXOutput [true]}] A flag to say whether to display a
173  0th moment map in a PGPlot X-window. This will be in addition to any
174  that are saved to a file. This parameter can be overridden by the
175  use of the \texttt{-x} command-line option, which disables the
176  X-windows output. If PGPlot has not been enabled, this parameter
177  defaults to \texttt{false}.
178\item[{newFluxUnits [no default]}] Flux units that the pixel values
179  should be converted into. These should be directly compatible with
180  the existing units, given by the BUNIT keyword.
181\item[{precFlux [3]}] The desired precision (\ie number of decimal
182  places) for flux values given in the output files and tables.
183\item[{precVel [3]}] The desired precision (\ie number of decimal
184  places) for velocity/frequency values given in the output files and
185  tables.
186\item[{precSNR [2]}] The desired precision (\ie number of decimal
187  places) for the peak SNR value given in the output files and tables.
188\end{Lentry}
189
190\secB*{Modifying the cube}
191\begin{Lentry}
192\item[{flagTrim [false]}] A flag to say whether to trim
193  BLANK pixels from the edges of the cube -- these are typically
194  pixels set to some particular value because they fall outside the
195  imaged area, and trimming them can help speed up the execution.
196\item[{flagMW [false]}] A flag to say whether to ignore
197  channels contaminated by Milky Way (or other) emission -- the
198  searching algorithms will not look at these channels.
199\item[{maxMW [112]}] The maximum channel number that contains
200  ``Milky Way'' emission. This is the channel number in the original
201  cube, before any subsection is applied.
202\item[{minMW [75]}] The minimum channel number that contains ``Milky
203  Way'' emission. This is the channel number in the original cube,
204  before any subsection is applied.  Note that the range specified by
205  \texttt{maxMW} and \texttt{minMW} is inclusive.
206\item[{flagBaseline [false]}] A flag to say whether to remove
207  the baseline from each spectrum in the cube for the purposes of
208  reconstruction and detection.
209\end{Lentry}
210
211\secB*{Detection related}
212
213\secC*{General detection}
214\begin{Lentry}
215\item[{searchType [spatial]}] How the searches are done. A value of
216  ``spatial'' means each 2D channel map is searched, whereas
217  ``spectral'' means each 1D spectrum is searched.
218\item[{flagStatSec [false]}] A flag indicating whether the
219  statistics should be calculated on a subsection of the cube, rather
220  than the full cube. Note that this only applies to the statistics
221  used to determine the threshold, and not for other statistical
222  calculations (such as those in the reconstruction phase).
223\item[{StatSec [ [*,*,*] ]}] The subsection of the cube used
224  for calculating statistics -- see \S\ref{sec-input} for details on
225 the subsection format. Only used if \texttt{flagStatSec=true}.
226\item[{flagRobustStats [true]}] A flag indicating whether to use the
227  robust statistics (median and MADFM) to estimate the noise
228  parameters, rather than the mean and rms. See \S\ref{sec-stats} for
229  details.
230\item[{flagNegative [false]}] A flag indicating that the
231  features of interest are negative. The cube is inverted prior to
232  searching.
233\item[{snrCut [3.]}] The threshold, in multiples of $\sigma$ above
234  the mean.
235\item[{threshold [no default]}] The actual value of the
236  threshold. Normally the threshold is calculated from the cube's
237  statistics, but the user can manually specify a value to be used
238  that overrides the calculated value. If this is not specified, the
239  calculated value is used, but this value will take precedence over
240  other means of calculating the threshold (\ie via \texttt{snrCut} or
241  the FDR method).
242\item[{flagGrowth [false]}] A flag indicating whether or not to
243  grow the detected objects to a smaller threshold.
244\item[{growthCut [3.]}] The smaller threshold using in growing
245  detections. In units of $\sigma$ above the mean.
246\item[{growthThreshold [no default]}] Alternatively, the threshold to
247  which detections are grown can be specified in flux units (in the
248  same manner as the \texttt{threshold} parameter). When the
249  \texttt{threshold} parameter is given, this option \textbf{must} be
250  used instead of \texttt{growthCut}.
251\item[{beamFWHM [0.]}] The full-width at half maximum of the beam, in
252  pixels.  If the header keywords BMAJ and BMIN are present, then
253  these will be used to calculate the beam area, and this parameter
254  will be ignored. This will take precedence over \texttt{beamArea}
255  (but is ignored if not specified).
256\item[{beamArea [0.]}] The \textbf{area} of the beam in pixels (\ie
257  how many pixel does the beam cover?). As above, if the header
258  keywords BMAJ and BMIN are present, then these will be used to
259  calculate the beam area, and this parameter will be ignored.
260\end{Lentry}
261
262\secC*{\Atrous reconstruction}
263\begin{Lentry}
264\item[{flagATrous [false]}] A flag indicating whether or not to
265  reconstruct the cube using the \atrous wavelet
266  reconstruction. See \S\ref{sec-recon} for details.
267\item[{reconDim [1]}] The number of dimensions to use in the
268  reconstruction. 1 means reconstruct each spectrum separately, 2
269  means each channel map is done separately, and 3 means do the whole
270  cube in one go.
271\item[{scaleMin [1]}] The minimum wavelet scale to be used in the
272  reconstruction. A value of 1 means ``use all scales''.
273\item[{scaleMax [0]}] The maximum wavelet scale to be used in the
274  reconstruction. If the value is $\le0$ then the maximum scale is
275  calculated from the size of the input array. Similarly, if the value
276  given is larger than this calculated value, the calculated value is
277  used instead.
278\item[{snrRecon [4]}] The thresholding cutoff used in the
279  reconstruction -- only wavelet coefficients this many $\sigma$ above
280  the mean (or greater) are included in the reconstruction.
281\item[{filterCode [1]}] The code number of the filter to use in
282  the reconstruction. The options are:
283  \begin{itemize}
284  \item \textbf{1:} B$_3$-spline filter: coefficients =
285    $(\frac{1}{16}, \frac{1}{4}, \frac{3}{8}, \frac{1}{4}, \frac{1}{16})$
286  \item \textbf{2:} Triangle filter: coefficients =
287    $(\frac{1}{4}, \frac{1}{2}, \frac{1}{4})$
288  \item \textbf{3:} Haar wavelet: coefficients =
289    $(0, \frac{1}{2}, \frac{1}{2})$
290  \end{itemize}
291\end{Lentry}
292
293\secC*{Smoothing the cube}
294\begin{Lentry}
295\item[{flagSmooth [false]}] A flag indicating whether to
296  smooth the cube. See \S\ref{sec-smoothing} for details.
297\item[{smoothType [spectral]}] The smoothing method used: either
298  ``spectral'' (with a 1D Hanning filter) or ``spatial'' (with a 2D
299  Gaussian filter). 
300\item[{hanningWidth [5]}] The width of the Hanning smoothing
301  kernel.
302\item[{kernMaj [3]}] The full-width-half-maximum (FWHM) of the
303  2D Gaussian smoothing kernel's major axis.
304\item[{kernMin [3]}] The FWHM of the 2D Gaussian smoothing kernel's
305  minor axis.
306\item[{kernPA [0]}] The position angle, in degrees,
307  anticlockwise from vertical (\ie usually East of North).
308\end{Lentry}
309
310\secC*{FDR method}
311\begin{Lentry}
312\item[{flagFDR [false]}] A flag indicating whether or not to use
313  the False Discovery Rate method in thresholding the pixels.
314\item[{alphaFDR [0.01]}] The $\alpha$ parameter used in the FDR
315  analysis. The average number of false detections, as a fraction of
316  the total number, will be less than $\alpha$ (see
317  \S\ref{sec-detection}).
318\item[{FDRnumCorChan [2]}] The number of neighbouring spectral
319  channels that are assumed to be correlated. This is needed by the
320  FDR algorithm to calculate the normalisation constant $c_N$ (see
321  \S\ref{sec-detection}).
322\end{Lentry}
323
324\secC*{Merging detections}
325\begin{Lentry}
326\item[{minPix [2]}] The minimum number of spatial pixels for a
327  single detection to be counted.
328\item[{minChannels [3]}] At least one contiguous set of this many
329  channels must be present in the detection for it to be accepted.
330\item[{minVoxels [4]}] A detection must have at least this many voxels
331  in it to be counted.
332\item[{flagRejectBeforeMerge [false]}] A flag indicating whether to
333  reject sources that fail to meet the \texttt{minPix} or
334  \texttt{minChannels} criteria \textbf{before} the merging
335  stage. Default behaviour is to do the rejection last.
336\item[{flagTwoStageMerging [true]}] A flag indicating whether to do an
337  initial merge of newly-detected sources into the source list as they
338  are found. If \texttt{false}, new sources are simply added to the
339  end of the list for later merging.
340\item[{flagAdjacent [true]}] A flag indicating whether to use
341  the ``adjacent pixel'' criterion to decide whether to merge
342  objects. If not, the next two parameters are used to determine
343  whether objects are within the necessary thresholds.
344\item[{threshSpatial [3.]}] The maximum allowed minimum spatial
345  separation (in pixels) between two detections for them to be merged
346  into one. Only used if \texttt{flagAdjacent = false}.
347\item[{threshVelocity [7.]}] The maximum allowed minimum channel
348  separation between two detections for them to be merged into
349  one.
350\end{Lentry}
351
352\secC*{Other parameters}
353\begin{Lentry}
354\item[{spectralMethod [peak]}] This indicates which method is used
355  to plot the output spectra: \texttt{peak} means plot the spectrum
356  containing the detection's peak pixel; \texttt{sum} means sum the
357  spectra of each detected spatial pixel, and correct for the beam
358  size. Any other choice defaults to \texttt{peak}.
359\item[{spectralUnits [km/s]}] The user can specify the units of
360  the spectral axis. Assuming the WCS of the FITS file is valid, the
361  spectral axis is transformed into velocity, and put into these units
362  for all output and for calculations such as the integrated flux of a
363  detection.
364\item[{pixelCentre [centroid]}] Which of the three ways of
365  expressing the ``centre'' of a detection (see \S\ref{sec-results}
366  for a description of the options) to use for the X, Y, \& Z
367  columns in the output list. Alternatives are: \texttt{centroid, peak,
368  average}.
369\item[{sortingParam [vel]}] The parameter on which to sort the output
370  list of detected objects. Options are: x-value, y-value, z-value,
371  ra, dec, vel, w50, iflux,  pflux (integrated and peak flux
372  respectively), or snr.
373\item[{drawBorders [true]}] A flag indicating whether to draw
374  borders around the detected objects in the moment maps included in
375  the output (see for example Fig.~\ref{fig-spect}).
376\item[{drawBlankEdges [true]}] A flag indicating whether to
377  draw the dividing line between BLANK and non-BLANK pixels on the
378  2D images (see for example Fig.~\ref{fig-moment}).
379\item[{verbose [true]}] A flag indicating whether to print the
380  progress of any computationally intensive algorithms (\eg
381  reconstruction, searching or merging algorithms) to the screen.
382\end{Lentry}
383
Note: See TracBrowser for help on using the repository browser.