source: branches/pixel-map-branch/docs/hints.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: 4.0 KB
Line 
1\secA{Notes and hints on the use of \duchamp}
2\label{sec-notes}
3
4In using \duchamp, the user has to make a number of decisions about
5the way the program runs. This section is designed to give the user
6some idea about what to choose.
7
8The main choice is whether or not to use the wavelet
9reconstruction. The main benefits of this are the marked reduction in
10the noise level, leading to regularly-shaped detections, and good
11reliability for faint sources. The main drawback with its use is the
12long execution time: to reconstruct a $170\times160\times1024$
13(\hipass) cube often requires three iterations and takes about 20-25
14minutes to run completely. Note that this is for the more complete
15three-dimensional reconstruction: using \texttt{reconDim=1} makes the
16reconstruction quicker (the full program then takes about 6 minutes),
17but it is still the largest part of the time.
18
19The searching part of the procedure is much quicker: searching an
20un-reconstructed cube leads to execution times of only a couple of
21minutes. Alternatively, using the ability to read in previously-saved
22reconstructed arrays makes running the reconstruction more than once a
23more feasible prospect.
24
25On the positive side, the shape of the detections in a cube that has
26been reconstructed will be much more regular and smooth -- the ragged
27edges that objects in the raw cube possess are smoothed by the removal
28of most of the noise. This enables better determination of the shapes
29and characteristics of objects.
30
31A further point to consider when using the reconstruction is that if
32the two-dimensional reconstruction is chosen (\texttt{reconDim=2}), it
33can be susceptible to edge effects. If the valid area in the cube (\ie
34the part that is not BLANK) has non-rectangular edges, the convolution
35can produce artefacts in the reconstruction that mimic the edges and
36can lead (depending on the selection threshold) to some spurious
37sources. Caution is advised with such data -- the user is advised to
38check carefully the reconstructed cube for the presence of such
39artefacts. Note, however, that the 1- and 3-dimensional
40reconstructions are \emph{not} susceptible in the same way, since the
41spectral direction does not generally exhibit these BLANK edges, and
42so we recommend the use of either of these.
43
44If one chooses the reconstruction method, a further decision is
45required on the signal-to-noise cutoff used in determining acceptable
46wavelet coefficients. A larger value will remove more noise from the
47cube, at the expense of losing fainter sources, while a smaller value
48will include more noise, which may produce spurious detections, but
49will be more sensitive to faint sources. Values of less than about
50$3\sigma$ tend to not reduce the noise a great deal and can lead to
51many spurious sources (this depends, of course on the cube itself).
52
53When it comes to searching, the FDR method produces more reliable
54results than simple sigma-clipping, particularly in the absence of
55reconstruction.  However, it does not work in exactly the way one
56would expect for a given value of \texttt{alpha}. For instance,
57setting fairly liberal values of \texttt{alpha} (say, 0.1) will often
58lead to a much smaller fraction of false detections (\ie much less
59than 10\%). This is the effect of the merging algorithms, that combine
60the sources after the detection stage, and reject detections not
61meeting the minimum pixel or channel requirements.  It is thus better
62to aim for larger \texttt{alpha} values than those derived from a
63straight conversion of the desired false detection rate.
64
65Finally, as \duchamp is still undergoing development, there are some
66elements that are not fully developed. In particular, it is not as
67clever as I would like at avoiding interference. The ability to place
68requirements on the minimum number of channels and pixels partially
69circumvents this problem, but work is being done to make \duchamp
70smarter at rejecting signals that are clearly (to a human eye at
71least) interference. See the following section for further
72improvements that are planned.
Note: See TracBrowser for help on using the repository browser.