source: branches/pixel-map-branch/docs/app-param.tex @ 1441

Last change on this file since 1441 was 255, checked in by Matthew Whiting, 17 years ago
  • Mostly Guide changes, thanks to the xspace package. Some alteration of the statistics calculation description, thanks to the new statsec parameter.
  • Also changed the default value of the reconDim parameter -- now default is 1-dimensional.
File size: 11.3 KB
Line 
1\secA{Available parameters}
2\label{app-param}
3
4The full list of parameters that can be listed in the input file are
5given here. If not listed, they take the default value given in
6parentheses. Since the order of the parameters in the input file does
7not matter, they are grouped here in logical sections.
8
9\secB*{Input related}
10\begin{entry}
11\item[ImageFile (no default assumed)] The filename of the
12  data cube to be analysed.
13\item[flagSubsection \texttt{[false]}] A flag to indicate whether one
14  wants a subsection of the requested image.
15\item[Subsection \texttt{[ [*,*,*] ]}] The requested subsection
16 -- see \S\ref{sec-input} for details on the subsection format.  If
17 the full range of a dimension is required, use a \texttt{*} (thus the
18 default is the full cube).
19\item[flagReconExists \texttt{[false]}] A flag to indicate whether the
20  reconstructed array has been saved by a previous run of \duchamp. If
21  set true, the reconstructed array will be read from the file given
22  by \texttt{reconFile}, rather than calculated directly.
23\item[reconFile (no default assumed)] The FITS file that contains the
24  reconstructed array. If \texttt{flagReconExists} is true and this
25  parameter is not defined, the default file that is looked for will
26  be determined by the \atrous parameters (see \S\ref{sec-recon}).
27\item[flagSmoothExists \texttt{[false]}] A flag to indicate whether the
28  Hanning-smoothed array has been saved by a previous run of \duchamp. If
29  set true, the smoothed array will be read from the file given
30  by \texttt{smoothFile}, rather than calculated directly.
31\item[smoothFile (no default assumed)] The FITS file that contains the
32  Hanning-smoothed array. If \texttt{flagSmoothExists} is true and
33  this parameter is not defined, the default file that is looked for
34  will be determined by the Hanning width parameter (see
35  \S\ref{sec-smoothing}).
36\end{entry}
37
38\secB*{Output related}
39\begin{entry}
40\item[OutFile \texttt{[duchamp-Results.txt]}] The file containing the
41  final list of detections. This also records the list of input
42  parameters.
43\item[SpectraFile \texttt{[duchamp-Spectra.ps]}] The postscript file
44  containing the resulting integrated spectra and images of the
45  detections.
46\item[flagLog \texttt{[true]}] A flag to indicate whether the
47  details of intermediate detections should be logged.
48\item[LogFile \texttt{[duchamp-Logfile.txt]}] The file in which
49  intermediate detections are logged. These are detections that have
50  not been merged. This is primarily for use in debugging and
51  diagnostic purposes -- normal use of the program will probably not
52  require this.
53\item[flagOutputRecon \texttt{[false]}] A flag to say whether or not
54  to save the reconstructed cube as a FITS file. The filename will be
55  derived according to the naming scheme detailed in
56  Section~\ref{sec-reconIO}.
57\item[flagOutputResid \texttt{[false]}] As for
58  \texttt{flagOutputRecon}, but for the residual array -- the
59  difference between the original cube and the reconstructed cube. The
60  filename will be derived according to the naming scheme detailed in
61  Section~\ref{sec-reconIO}.
62\item[flagOutputSmooth \texttt{[false]}] A flag to say whether or not
63  to save the smoothed cube as a FITS file. The filename will be
64  derived according to the naming scheme detailed in
65  Section~\ref{sec-smoothing}.
66\item[flagVOT \texttt{[false]}] A flag to say whether to create a
67  VOTable file corresponding to the information in
68  \texttt{outfile}. This will be an XML file in the Virtual
69  Observatory VOTable format.
70\item[votFile \texttt{[duchamp-Results.xml]}] The VOTable file with
71  the list of final detections. Some input parameters are also
72  recorded.
73\item[flagKarma \texttt{[false]}] A flag to say whether to create a
74  Karma annotation file corresponding to the information in
75  \texttt{outfile}. This can be used as an overlay for the Karma
76  programs such as \texttt{kvis}.
77\item[karmaFile \texttt{[duchamp-Results.ann]}] The Karma annotation
78  file showing the list of final detections.
79\item[flagMaps \texttt{[true]}] A flag to say whether to save
80  postscript files showing the 0th moment map of the whole cube
81  (parameter \texttt{momentMap}) and the detection image
82  (\texttt{detectionMap}).
83\item[momentMap \texttt{[duchamp-MomentMap.ps]}] A postscript file
84  containing a map of the 0th moment of the detected sources, as well
85  as pixel and WCS coordinates.
86\item[detectionMap \texttt{[duchamp-DetectionMap.ps]}] A postscript
87  file showing each of the detected objects, coloured in greyscale by
88  the number of channels spanned by each pixel. Also shows pixel and
89  WCS coordinates.
90\item[flagXOutput \texttt{[true]}] A flag to say whether to display a
91  0th moment map in a PGPlot Xwindow. This will be in addition to any
92  that are saved to a file.
93\end{entry}
94
95\secB*{Modifying the cube}
96\begin{entry}
97\item[flagBlankPix \texttt{[true]}] A flag to say whether to remove
98  BLANK pixels from the analysis -- these are pixels set to some
99  particular value because they fall outside the imaged area.
100\item[blankPixValue \texttt{[-8.00061]}] The value of the BLANK
101  pixels, if this information is not contained in the FITS header (the
102  usual procedure is to obtain this value from the header information
103  -- in which case the value set by this parameter is ignored).
104\item[flagMW \texttt{[false]}] A flag to say whether to ignore
105  channels contaminated by Milky Way (or other) emission -- the
106  searching algorithms will not look at these channels.
107\item[maxMW \texttt{[112]}] The maximum channel number that contains
108  ``Milky Way'' emission.
109\item[minMW \texttt{[75]}] The minimum channel number that contains
110  ``Milky Way'' emission. Note that the range specified by
111  \texttt{maxMW} and \texttt{minMW} is inclusive.
112\item[flagBaseline \texttt{[false]}] A flag to say whether to remove
113  the baseline from each spectrum in the cube for the purposes of
114  reconstruction and detection.
115\end{entry}
116
117\secB*{Detection related}
118
119\secC*{General detection}
120\begin{entry}
121\item[flagStatSec \texttt{[false]}] A flag indicating whether the cube
122  statistics should be calculated on a subsection of the cube, rather
123  than the full cube.
124\item[StatSec \texttt{[ [*,*,*] ]}] The subsection of the cube used
125  for calculating statistics -- see \S\ref{sec-input} for details on
126 the subsection format. Only used if \texttt{flagStatSec=true}.
127\item[flagNegative \texttt{[false]}] A flag indicating that the
128  features being searched for are negative. The cube will be inverted
129  prior to searching.
130\item[snrCut \texttt{[3.]}] The cut-off value for thresholding, in
131  terms of number of $\sigma$ above the mean.
132\item[threshold (no default assumed)] The actual value of the
133  threshold. Normally the threshold is calculated from the cube's
134  statistics, but the user can manually specify a value to be used
135  that overrides the calculated value. If this is not specified, the
136  calculated value is used. Also, when the FDR method is requested
137  (see below), the value of the \texttt{threshold} parameter is
138  ignored.
139\item[flagGrowth \texttt{[false]}] A flag indicating whether or not to
140  grow the detected objects to a smaller threshold.
141\item[growthCut \texttt{[2.]}] The smaller threshold using in growing
142  detections. In units of $\sigma$ above the mean.
143\item[beamSize \texttt{[10.]}] The size of the beam in pixels. If the
144  header keywords BMAJ and BMIN are present, then these will be used
145  to calculate the beam size, and this parameter will be ignored.
146\end{entry}
147
148\secC*{\Atrous reconstruction}
149\begin{entry}
150\item [flagATrous \texttt{[true]}] A flag indicating whether or not to
151  reconstruct the cube using the \atrous wavelet
152  reconstruction. See \S\ref{sec-recon} for details.
153\item[reconDim \texttt{[1]}] The number of dimensions to use in the
154  reconstruction. 1 means reconstruct each spectrum separately, 2
155  means each channel map is done separately, and 3 means do the whole
156  cube in one go.
157\item[scaleMin \texttt{[1]}] The minimum wavelet scale to be used in the
158  reconstruction. A value of 1 means ``use all scales''.
159\item[snrRecon \texttt{[4]}] The thresholding cutoff used in the
160  reconstruction -- only wavelet coefficients this many $\sigma$ above
161  the mean (or greater) are included in the reconstruction.
162\item[filterCode \texttt{[1]}] The code number of the filter to use in
163  the reconstruction. The options are:
164  \begin{itemize}
165  \item \textbf{1:} B$_3$-spline filter: coefficients =
166    $(\frac{1}{16}, \frac{1}{4}, \frac{3}{8}, \frac{1}{4}, \frac{1}{16})$
167  \item \textbf{2:} Triangle filter: coefficients =
168    $(\frac{1}{4}, \frac{1}{2}, \frac{1}{4})$
169  \item \textbf{3:} Haar wavelet: coefficients =
170    $(0, \frac{1}{2}, \frac{1}{2})$
171  \end{itemize}
172\end{entry}
173
174\secC*{Smoothing the cube}
175\begin{entry}
176\item [flagSmooth \texttt{[false]}] A flag indicating whether to
177  Hanning-smooth the cube. See \S\ref{sec-smoothing} for details.
178\item [hanningWidth \texttt{[5]}] The width of the Hanning smoothing
179kernel.
180\end{entry}
181
182\secC*{FDR method}
183\begin{entry}
184\item[flagFDR \texttt{[false]}] A flag indicating whether or not to use
185  the False Discovery Rate method in thresholding the pixels.
186\item[alphaFDR \texttt{[0.01]}] The $\alpha$ parameter used in the FDR
187analysis. The average number of false detections, as a fraction of the
188total number, will be less than $\alpha$ (see \S\ref{sec-detection}).
189\end{entry}
190
191\secC*{Merging detections}
192\begin{entry}
193\item[minPix \texttt{[2]}] The minimum number of spatial pixels for a
194  single detection to be counted.
195\item[minChannels \texttt{[3]}] The minimum number of consecutive
196  channels that must be present in a detection.
197\item[flagAdjacent \texttt{[true]}] A flag indicating whether to use
198  the ``adjacent pixel'' criterion to decide whether to merge
199  objects. If not, the next two parameters are used to determine
200  whether objects are within the necessary thresholds.
201\item[threshSpatial \texttt{[3.]}] The maximum allowed minimum spatial
202  separation (in pixels) between two detections for them to be merged
203  into one. Only used if \texttt{flagAdjacent = false}.
204\item[threshVelocity \texttt{[7.]}] The maximum allowed minimum channel
205  separation between two detections for them to be merged into
206  one.
207\end{entry}
208
209\secC*{Other parameters}
210\begin{entry}
211\item[spectralMethod \texttt{[peak]}] This indicates which method is used
212  to plot the output spectra: \texttt{peak} means plot the spectrum
213  containing the detection's peak pixel; \texttt{sum} means sum the
214  spectra of each detected spatial pixel, and correct for the beam
215  size. Any other choice defaults to \texttt{peak}.
216\item[spectralUnits \texttt{[km/s]}] The user can specify the units of
217  the spectral axis. Assuming the WCS of the FITS file is valid, the
218  spectral axis is transformed into velocity, and put into these units
219  for all output and for calculations such as the integrated flux of a
220  detection.
221\item[drawBorders \texttt{[true]}] A flag indicating whether borders
222  are to be drawn around the detected objects in the moment maps
223  included in the output (see for example Fig.~\ref{fig-spect}).
224\item[drawBlankEdges \texttt{[true]}] A flag indicating whether to
225 draw the dividing line between BLANK and non-BLANK pixels on the
226 2-dimensional images (see for example Fig.~\ref{fig-moment}).
227\item[verbose \texttt{[true]}] A flag indicating whether to print the
228  progress of any computationally-intensive algorithms (\eg
229  reconstruction, searching or merging algorithms) to the screen.
230\end{entry}
231
Note: See TracBrowser for help on using the repository browser.