1 | ----------------------------------------------------------------------- |
---|
2 | The Duchamp Source Finder |
---|
3 | ----------------------------------------------------------------------- |
---|
4 | Duchamp 1.0.7 -- an object finder for spectral-line data cubes |
---|
5 | Copyright (C) 2006, Matthew Whiting, ATNF |
---|
6 | |
---|
7 | Duchamp 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@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 | |
---|
30 | Introduction |
---|
31 | ------------ |
---|
32 | |
---|
33 | Duchamp is a stand-alone program designed to find objects in |
---|
34 | astronomical data cubes, particularly spectral-line observations. Its |
---|
35 | features include a wavelet-based reconstruction technique for reducing |
---|
36 | the noise in the cube (and thereby enhancing detectability of |
---|
37 | sources), easy-to-use text-based interface, flexibility to control all |
---|
38 | relevant parameters such as detection thresholds, and a useful range |
---|
39 | of text- and graphics-based output. |
---|
40 | |
---|
41 | Duchamp works on any FITS image using the CFITSIO package, and uses |
---|
42 | Mark Calabretta's WCSLIB library to provide accurate position and |
---|
43 | velocity information for all detected sources. |
---|
44 | |
---|
45 | |
---|
46 | Obtaining and Building Duchamp |
---|
47 | ------------------------------ |
---|
48 | |
---|
49 | The Duchamp web page is at |
---|
50 | http://www.atnf.csiro.au/people/Matthew.Whiting/Duchamp |
---|
51 | where you can download a gzipped tar archive of the source code. |
---|
52 | |
---|
53 | Duchamp uses three main external libraries: pgplot, cfitsio (version |
---|
54 | 2.5 and greater, version 3+ preferred) and wcslib. If you do not have |
---|
55 | the libraries, they can be downloaded from the following locations: |
---|
56 | |
---|
57 | PGPlot -- http://www.astro.caltech.edu/~tjp/pgplot/ |
---|
58 | cfitsio -- http://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio.html |
---|
59 | wcslib -- http://www.atnf.csiro.au/people/Mark.Calabretta/WCS/index.html |
---|
60 | |
---|
61 | Duchamp can be built on Unix systems by typing (note that the terminal |
---|
62 | prompt here is represented by > -- don't type this character!): |
---|
63 | |
---|
64 | > ./configure |
---|
65 | > make |
---|
66 | > make clean (optional -- to remove the object files from the src |
---|
67 | directory) |
---|
68 | |
---|
69 | This way, configure should find all the necessary libraries, but if |
---|
70 | the above-mentioned libraries have been installed in non-standard |
---|
71 | locations, you can specify additional directories to look in. There |
---|
72 | are separate options for library files (eg. libcpgplot.a) and header |
---|
73 | files (eg. cpgplot.h). |
---|
74 | |
---|
75 | For example, suppose wcslib had been locally installed in |
---|
76 | /home/mduchamp/wcslib. There will then be two libraries created that |
---|
77 | are likely to be in separate subdirectories: C/ and pgsbox/. Each |
---|
78 | subdirectory needs to be searched for library and header files, so one |
---|
79 | could build Duchamp by typing: |
---|
80 | |
---|
81 | > ./configure \ |
---|
82 | LIBDIRS="/home/mduchamp/wcslib/C /home/mduchamp/wcslib/pgsbox" \ |
---|
83 | INCDIRS="/home/mduchamp/wcslib/C /home/mduchamp/wcslib/pgsbox" |
---|
84 | And then just run make in the usual fashion: |
---|
85 | > make |
---|
86 | |
---|
87 | There is a script included in the distribution that allows you to make |
---|
88 | sure Duchamp is running correctly. It will use a dummy FITS image in |
---|
89 | the verification/ directory -- this image has some Gaussian random |
---|
90 | noise, with five Gaussian sources present, plus a dummy WCS. The |
---|
91 | script runs Duchamp on this image with three different sets of inputs, |
---|
92 | and compares to known results, looking for differences and reporting |
---|
93 | any. There should be none reported if everything is working |
---|
94 | correctly. To run, enter the command |
---|
95 | |
---|
96 | > VerifyDuchamp.sh |
---|
97 | |
---|
98 | You can also use the dummy image for your own testing if you like (for |
---|
99 | instance, testing different thresholds to get a feel for how the |
---|
100 | program works). |
---|
101 | |
---|
102 | |
---|
103 | Using Duchamp |
---|
104 | --------------- |
---|
105 | |
---|
106 | There are two possible ways to run Duchamp. The first is: |
---|
107 | |
---|
108 | > Duchamp -f image.fits |
---|
109 | |
---|
110 | where image.fits is the data cube to be searched. This method simply |
---|
111 | uses the default values of all parameters. |
---|
112 | |
---|
113 | The second method allows some determination of the parameter values by |
---|
114 | the user. Type: |
---|
115 | |
---|
116 | > Duchamp -p parameterFile |
---|
117 | |
---|
118 | where parameterFile is a file with the input parameters, including the |
---|
119 | name of the cube you want to search. There are two example input files |
---|
120 | included with the distribution. The smaller one, InputExample, shows |
---|
121 | the typical parameters one might want to set. The large one, |
---|
122 | InputComplete, lists all possible parameters that can be entered, and |
---|
123 | a brief description of them. To get going quickly, just replace the |
---|
124 | "your-file-here" in InputExample with your image name, and type |
---|
125 | |
---|
126 | > Duchamp -p InputExample |
---|
127 | |
---|
128 | A User's Guide in the docs/ directory provides complete |
---|
129 | documentation. It comes in both postscript and portable document |
---|
130 | format (pdf -- note that this contains hyperlinks). This guide will |
---|
131 | provide full descriptions of all parameters, and of all steps in the |
---|
132 | execution of Duchamp. |
---|
133 | |
---|
134 | Any questions, please contact me. To report problems or bugs, or to |
---|
135 | suggest improvements, please go to the Duchamp Trac wiki site: |
---|
136 | http://sourcecode.atnf.csiro.au/cgi-bin/trac_duchamp.cgi/newticket |
---|
137 | and submit a "ticket", or view previously submitted reports. |
---|
138 | |
---|
139 | Author: |
---|
140 | Matthew Whiting, Australia Telescope National Facility, November 2006 |
---|
141 | Matthew.Whiting@csiro.au |
---|
142 | |
---|