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

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

Solving #118 - have new parameter flagPlotSpectra (defaulting to true) that controls whether the spectral plots are done. Also, we take notice of whether the USE_PGPLOT flag is set. Updating docs etc for new parameter as well.

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