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

Last change on this file since 1441 was 208, checked in by Matthew Whiting, 18 years ago
  • Enabled saving and reading in of a smoothed array, in manner directly analogous to that for the recon array.
    • New file : src/Cubes/readSmooth.cc
    • The other new functions go in existing files eg. saveImage.cc
    • Renamed some functions (like writeHeader...) to be more obvious what they do.
    • The reading in is taken care of by new function Cube::readSavedArrays() -- handles both smoothed and recon'd arrays.
    • Associated parameters in Param class
    • Clarified names of FITS header strings in duchamp.hh.
  • Updated the documentation to describe the ability to smooth a cube.
  • Added description of feedback mechanisms in the Install appendix.
  • Also, Hanning class improved to guard against memory leaks.


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