source: tags/release-1.2.2/docs/app-param.tex @ 1441

Last change on this file since 1441 was 1078, checked in by MatthewWhiting, 12 years ago

Updating user guide with DS9 parameters & example, and slightly improved VOTable example. Also updated the version number.

File size: 21.0 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  that contains 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 and the pixel content of the final list of
109  detections are logged. These are detections that have not been
110  merged. This is primarily for use in debugging and diagnostic
111  purposes: normal use of the program will probably not 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  \S\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  \S\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 \S\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 \S\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 \S\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[{flagDS9 [false]}] A flag to say whether to create a
156  DS9 region file corresponding to the information in
157  \texttt{outfile}. This can be used as an overlay in SAOImage DS9 or
158  casaviewer.
159\item[{karmaFile [duchamp-\\Results.ann]}] The DS9 region file showing
160  the list of final detections.
161\item[{annotationType [borders]}] Which type of annotation plot to
162  use. Specifying ``borders'' gives an outline around the detected
163  spatial pixels, while ``circles'' gives a circle centred on the
164  centre of the object with radius large enough to encompass all
165  spatial pixels.
166\item[{flagMaps [true]}] A flag to say whether to save postscript
167  files showing the 0th moment map of the whole cube
168  (\texttt{momentMap}) and the detection image
169  (\texttt{detectionMap}). If PGPlot has not been enabled, this
170  parameter defaults to \texttt{false}.
171\item[{momentMap [duchamp-\\MomentMap.ps]}] A postscript file
172  containing a map of the 0th moment of the detected sources, as well
173  as pixel and WCS coordinates.
174\item[{detectionMap [duchamp-\\DetectionMap.ps]}] A postscript
175  file with a map showing each of the detected objects, coloured in
176  greyscale by the number of detected channels in each spatial
177  pixel. Also shows pixel and WCS coordinates.
178\item[{flagXOutput [true]}] A flag to say whether to display a
179  0th moment map in a PGPlot X-window. This will be in addition to any
180  that are saved to a file. This parameter can be overridden by the
181  use of the \texttt{-x} command-line option, which disables the
182  X-windows output. If PGPlot has not been enabled, this parameter
183  defaults to \texttt{false}.
184\item[{newFluxUnits [no default]}] Flux units that the pixel values
185  should be converted into. These should be directly compatible with
186  the units in the FITS header, given by the BUNIT keyword.
187\item[{precFlux [3]}] The desired precision (\ie number of decimal
188  places) for flux values given in the output files and tables.
189\item[{precVel [3]}] The desired precision (\ie number of decimal
190  places) for velocity/frequency values given in the output files and
191  tables.
192\item[{precSNR [2]}] The desired precision (\ie number of decimal
193  places) for the peak SNR value given in the output files and tables.
194\end{Lentry}
195
196\secB*{Modifying the cube}
197\begin{Lentry}
198\item[{flagTrim [false]}] A flag to say whether to trim
199  BLANK pixels from the edges of the cube -- these are typically
200  pixels set to some particular value because they fall outside the
201  imaged area, and trimming them can help speed up the execution.
202\item[{flagMW [false]}] A flag to say whether to ignore
203  channels contaminated by Milky Way (or other) emission -- the
204  searching algorithms will not look at these channels.
205\item[{maxMW [112]}] The maximum channel number that contains
206  ``Milky Way'' emission. This is the channel number in the original
207  cube, before any subsection is applied.
208\item[{minMW [75]}] The minimum channel number that contains ``Milky
209  Way'' emission. This is the channel number in the original cube,
210  before any subsection is applied.  Note that the range specified by
211  \texttt{maxMW} and \texttt{minMW} is inclusive.
212\item[{flagBaseline [false]}] A flag to say whether to remove
213  the baseline from each spectrum in the cube for the purposes of
214  reconstruction and detection.
215\end{Lentry}
216
217\secB*{Detection related}
218
219\secC*{General detection}
220\begin{Lentry}
221\item[{searchType [spatial]}] How the searches are done. Only
222  ``spatial'' and ``spectral'' are accepted. A value of ``spatial''
223  means each 2D channel map is searched, whereas ``spectral'' means
224  each 1D spectrum is searched.
225\item[{flagStatSec [false]}] A flag indicating whether the
226  statistics should be calculated on a subsection of the cube, rather
227  than the full cube. Note that this only applies to the statistics
228  used to determine the threshold, and not for other statistical
229  calculations (such as those in the reconstruction phase).
230\item[{StatSec [ [*,*,*] ]}] The subsection of the cube used
231  for calculating statistics -- see \S\ref{sec-input} for details on
232 the subsection format. Only used if \texttt{flagStatSec=true}.
233\item[{flagRobustStats [true]}] A flag indicating whether to use the
234  robust statistics (median and MADFM) to estimate the noise
235  parameters of the cube, rather than the mean and rms. See
236  \S\ref{sec-stats} for details.
237\item[{flagNegative [false]}] A flag indicating that the
238  features of interest are negative. The cube is inverted prior to
239  searching.
240\item[{snrCut [5.]}] The threshold, in multiples of $\sigma$ above
241  the mean.
242\item[{threshold [no default]}] The actual value of the
243  threshold. Normally the threshold is calculated from the cube's
244  statistics, but the user can manually specify a value to be used
245  that overrides the calculated value. If this is not specified, the
246  calculated value is used, but this value will take precedence over
247  other means of calculating the threshold (\ie via \texttt{snrCut} or
248  the FDR method).
249\item[{flagGrowth [false]}] A flag indicating whether or not to
250  grow the detected objects to a smaller threshold.
251\item[{growthCut [3.]}] The smaller threshold using in growing
252  detections. In units of $\sigma$ above the mean.
253\item[{growthThreshold [no default]}] Alternatively, the threshold to
254  which detections are grown can be specified in flux units (in the
255  same manner as the \texttt{threshold} parameter). When the
256  \texttt{threshold} parameter is given, this option \textbf{must} be
257  used instead of \texttt{growthCut}.
258\item[{beamFWHM [0.]}] The full-width at half maximum of the beam, in
259  pixels.  If the header keywords BMAJ and BMIN are present, then
260  these will be used to calculate the beam area, and this parameter
261  will be ignored. This will take precedence over \texttt{beamArea}
262  (but is ignored if not specified).
263\item[{beamArea [0.]}] The \textbf{area} of the beam in pixels (\ie
264  how many pixel does the beam cover?). As above, if the header
265  keywords BMAJ and BMIN are present, then these will be used to
266  calculate the beam area, and this parameter will be ignored.
267\end{Lentry}
268
269\secC*{\Atrous reconstruction}
270\begin{Lentry}
271\item[{flagATrous [false]}] A flag indicating whether or not to
272  reconstruct the cube using the \atrous wavelet
273  reconstruction. See \S\ref{sec-recon} for details.
274\item[{reconDim [1]}] The number of dimensions to use in the
275  reconstruction. 1 means reconstruct each spectrum separately, 2
276  means each channel map is done separately, and 3 means do the whole
277  cube in one go.
278\item[{scaleMin [1]}] The minimum wavelet scale to be used in the
279  reconstruction. A value of 1 means ``use all scales''.
280\item[{scaleMax [0]}] The maximum wavelet scale to be used in the
281  reconstruction. If the value is $\le0$ then the maximum scale is
282  calculated from the size of the input array. Similarly, if the value
283  given is larger than this calculated value, the calculated value is
284  used instead.
285\item[{snrRecon [4]}] The thresholding cutoff used in the
286  reconstruction -- only wavelet coefficients at least this many $\sigma$ above
287  the mean are included in the reconstruction.
288\item[{reconConvergence [0.005]}] The convergence criterion used in
289  the reconstruction. The \atrous algorithm iterates until the
290  relative change in the standard deviation of the residuals is less
291  than this amount.
292\item[{filterCode [1]}] The code number of the filter to use in
293  the reconstruction. The options are:
294  \begin{itemize}
295  \item \textbf{1:} B$_3$-spline filter: coefficients =
296    $(\frac{1}{16}, \frac{1}{4}, \frac{3}{8}, \frac{1}{4}, \frac{1}{16})$
297  \item \textbf{2:} Triangle filter: coefficients =
298    $(\frac{1}{4}, \frac{1}{2}, \frac{1}{4})$
299  \item \textbf{3:} Haar wavelet: coefficients =
300    $(0, \frac{1}{2}, \frac{1}{2})$
301  \end{itemize}
302\end{Lentry}
303
304\secC*{Smoothing the cube}
305\begin{Lentry}
306\item[{flagSmooth [false]}] A flag indicating whether to
307  smooth the cube. See \S\ref{sec-smoothing} for details.
308\item[{smoothType [spectral]}] The smoothing method used: either
309  ``spectral'' (with a 1D Hanning filter) or ``spatial'' (with a 2D
310  Gaussian filter). 
311\item[{hanningWidth [5]}] The width of the Hanning smoothing
312  kernel.
313\item[{kernMaj [3]}] The full-width-half-maximum (FWHM) of the
314  2D Gaussian smoothing kernel's major axis.
315\item[{kernMin [3]}] The FWHM of the 2D Gaussian smoothing kernel's
316  minor axis.
317\item[{kernPA [0]}] The position angle, in degrees,
318  anticlockwise from vertical (\ie usually East of North).
319\end{Lentry}
320
321\secC*{FDR method}
322\begin{Lentry}
323\item[{flagFDR [false]}] A flag indicating whether or not to use
324  the False Discovery Rate method in thresholding the pixels.
325\item[{alphaFDR [0.01]}] The $\alpha$ parameter used in the FDR
326  analysis. The average number of false detections, as a fraction of
327  the total number, will be less than $\alpha$ (see
328  \S\ref{sec-detection}).
329\item[{FDRnumCorChan [2]}] The number of neighbouring spectral
330  channels that are assumed to be correlated. This is needed by the
331  FDR algorithm to calculate the normalisation constant $c_N$ (see
332  \S\ref{sec-detection}).
333\end{Lentry}
334
335\secC*{Merging detections}
336\begin{Lentry}
337\item[{minPix [2]}] The minimum number of spatial pixels for a
338  single detection to be counted.
339\item[{minChannels [3]}] At least one contiguous set of this many
340  channels must be present in the detection for it to be accepted.
341\item[{minVoxels [minPix $+$ minChannels - 1]}] The minimum size of
342  the object, in terms of the total number of voxels, for it to be
343  accepted. This will be \textit{at least} minPix$+$minChannels$-$1,
344  but can be set higher.
345\item[{flagRejectBeforeMerge [false]}] A flag indicating whether to
346  reject sources that fail to meet the \texttt{minPix} or
347  \texttt{minChannels} criteria \textbf{before} the merging
348  stage. Default behaviour is to do the rejection last.
349\item[{flagTwoStageMerging [true]}] A flag indicating whether to do an
350  initial merge of newly-detected sources into the source list as they
351  are found. If \texttt{false}, new sources are simply added to the
352  end of the list for later merging.
353\item[{flagAdjacent [true]}] A flag indicating whether to use
354  the ``adjacent pixel'' criterion to decide whether to merge
355  objects. If not, the next two parameters are used to determine
356  whether objects are within the necessary thresholds.
357\item[{threshSpatial [3.]}] The maximum allowed minimum spatial
358  separation (in pixels) between two detections for them to be merged
359  into one. Only used if \texttt{flagAdjacent = false}.
360\item[{threshVelocity [7.]}] The maximum allowed minimum channel
361  separation between two detections for them to be merged into
362  one.
363\end{Lentry}
364
365\secC*{WCS parameters}
366\begin{Lentry}
367\item[{spectralType []}] The user can specify an alternative WCS
368  spectral type that the spectral axis can be expressed in. This
369  specification should conform to the standards described in
370  \citet{greisen06}, although it is possible to provide just the first
371  four letters (the ``S-type'', \eg 'VELO').
372\item[{restFrequency [-1]}] If provided, this will be used in
373  preference to the rest frequency given in the FITS header to
374  calculate velocities and related quantities. A negative value (such
375  as the default) will mean this is not used and the FITS header
376  value, if present, is used instead.
377\item[{spectralUnits []}] The user can specify the units of
378  the spectral axis, overriding those given in the FITS header. If the
379  spectral type is being changed, these units should be appropriate
380  for that quantity. If not provided, the FITS header information is
381  used.
382\end{Lentry}
383
384\secC*{Other parameters}
385\begin{Lentry}
386\item[{spectralMethod [peak]}] This indicates which method is used
387  to plot the output spectra: \texttt{peak} means plot the spectrum
388  containing the detection's peak pixel; \texttt{sum} means sum the
389  spectra of each detected spatial pixel, and correct for the beam
390  size. Any other choice defaults to \texttt{peak}.
391\item[{pixelCentre [centroid]}] Which of the three ways of
392  expressing the ``centre'' of a detection (see \S\ref{sec-results}
393  for a description of the options) to use for the X, Y, \& Z
394  columns in the output list. Alternatives are: \texttt{centroid, peak,
395  average}.
396\item[{sortingParam [vel]}] The parameter on which to sort the output
397  list of detected objects. Options are: xvalue, yvalue, zvalue, ra,
398  dec, vel, w50, iflux, pflux (integrated and peak flux respectively),
399  or snr. If the parameter begins with a '-' (\eg '-vel'), the order
400  of the sort is reversed.
401\item[{drawBorders [true]}] A flag indicating whether to draw
402  borders around the detected objects in the moment maps included in
403  the output (see for example Fig.~\ref{fig-spect}).
404\item[{drawBlankEdges [true]}] A flag indicating whether to
405  draw the dividing line between BLANK and non-BLANK pixels on the
406  2D images (see for example Fig.~\ref{fig-moment}).
407\item[{verbose [true]}] A flag indicating whether to print the
408  progress of any computationally intensive algorithms (\eg
409  reconstruction, searching or merging algorithms) to the screen.
410\end{Lentry}
411
412
413%%% Local Variables:
414%%% mode: latex
415%%% TeX-master: "Guide"
416%%% End:
Note: See TracBrowser for help on using the repository browser.