source: trunk/README @ 382

Last change on this file since 382 was 382, checked in by MatthewWhiting, 17 years ago

Minor changes to documentation

File size: 8.5 KB
Line 
1-----------------------------------------------------------------------
2               The Duchamp Source Finder
3-----------------------------------------------------------------------
4Duchamp 1.1.2 -- an object finder for spectral-line data cubes
5Copyright (C) 2006, Matthew Whiting, ATNF
6
7Duchamp is free software; you can redistribute it and/or modify it
8under the terms of the GNU General Public License as published by the
9Free Software Foundation; either version 2 of the License, or (at your
10option) any later version.
11
12Duchamp is distributed in the hope that it will be useful, but WITHOUT
13ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
14FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
15for more details.
16
17You should have received a copy of the GNU General Public License
18along with Duchamp; if not, write to the Free Software Foundation,
19Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA
20
21Correspondence 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
30Introduction
31============
32
33Duchamp is a stand-alone program designed to find objects in
34astronomical data cubes, particularly spectral-line observations. Its
35features include a wavelet-based reconstruction technique for reducing
36the noise in the cube (and thereby enhancing detectability of
37sources), easy-to-use text-based interface, flexibility to control all
38relevant parameters such as detection thresholds, and a useful range
39of text- and graphics-based output.
40
41Duchamp works on any FITS image using the CFITSIO package, and uses
42Mark Calabretta's WCSLIB library to provide accurate position and
43velocity information for all detected sources.
44
45
46Obtaining and Building Duchamp
47==============================
48
49The Duchamp web page is at
50http://www.atnf.csiro.au/people/Matthew.Whiting/Duchamp
51where you can download a gzipped tar archive of the source code.
52
53Duchamp uses three main external libraries: pgplot (although see note
54below), cfitsio (version 2.5 and greater, version 3+ preferred) and
55wcslib. If you do not have the libraries, they can be downloaded from
56the following locations:
57
58PGPLOT -- http://www.astro.caltech.edu/~tjp/pgplot/
59cfitsio -- http://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio.html
60wcslib -- http://www.atnf.csiro.au/people/Mark.Calabretta/WCS/index.html
61
62Note that PGPLOT is optional. Duchamp can be compiled and run without
63PGPLOT, but you will miss out on the useful graphical outputs!  The
64other two libraries, cftisio and wcslib, are essential.
65
66
67Basic Compilation and Installation
68----------------------------------
69
70Duchamp can be built and installed on Unix systems by typing (note
71that the terminal prompt here is represented by > -- don't type this
72character!):
73
74 >  ./configure
75 >  make
76 >  make clean (optional -- to remove the object files from the src
77                directory)
78 >  make install
79
80This default setup will search in standard locations for the necessary
81libraries, and install the executable ("Duchamp") in /usr/local/bin (a
82copy will also be in the current directory). If you want this to go
83somewhere else, eg if you don't have write-access to that directory,
84or you need to tweak the libraries, see the next section. Otherwise,
85jump to the testing section.
86
87
88Tweaking the installation setup
89-------------------------------
90
91To install Duchamp in a directory other than /usr/local/bin, use the
92--prefix option with configure, specifying the directory above the
93\texttt{bin/} directory. eg:
94
95 >  ./configure --prefix=/home/mduchamp
96
97which, if you run "make" and "make install", will result in the binary
98being put in the directory /home/mduchamp/bin.
99
100If the above-mentioned libraries have been installed in non-standard
101locations, or you have more than one version installed on your system,
102you can specify specific locations by using the --with-cfitsio=<dir>,
103--with-wcslib=<dir> or --with-pgplot=<dir> flags. For example:
104
105 >  ./configure --with-wcslib=/home/mduchamp/wcslib-4.2
106And then just run make in the usual fashion:
107 >  make
108
109Duchamp can be compiled without PGPLOT if it is not installed on your
110system -- the searching and text-based output remains the same, but
111you will not have any graphical output.
112To manually specify this option, use the --without-pgplot flag, eg:
113
114 >  ./configure --without-pgplot
115
116(Note that CFITSIO and WCSLIB are essential, however, so
117--without-wcslib or --without-cfitsio will not work.).
118Even if you do not give the --without-pgplot option, and the PGPLOT
119library is not found, Duchamp will still compile (albeit without
120graphical capabilities).
121
122
123Installing on Mac OS X with gfortran
124------------------------------------
125
126Some recent testing on a Mac with OS X and gfortran has shown that
127slight tweaking needs to be done with the use of configure. In
128addition to the options noted above, configure should be run with F77
129set to the desired fortran compiler command. Note that this should be
130the same as that used to compile the pgplot package, if you are using
131it: gfortran is probably the best choice.
132This is done simply by:
133
134 >  ./configure F77=gfortran ...[other options]...
135
136
137Testing
138=======
139
140There is a script included in the distribution that allows you to make
141sure Duchamp is running correctly. It will use a dummy FITS image in
142the verification/ directory -- this image has some Gaussian random
143noise, with five Gaussian sources present, plus a dummy WCS. The
144script runs Duchamp on this image with three different sets of inputs,
145and compares to known results, looking for differences and reporting
146any. There should be none reported if everything is working
147correctly. To run, enter the command
148
149 >  ./VerifyDuchamp.sh
150
151Once you know it is working, you can install Duchamp on your system
152with the command
153
154 > make install
155
156You can also use the dummy image for your own testing if you like (for
157instance, testing different thresholds to get a feel for how the
158program works).
159
160
161Using Duchamp
162=============
163
164There are two possible ways to run Duchamp. The first is:
165
166 >  Duchamp -f image.fits
167
168where image.fits is the data cube to be searched. This method simply
169uses the default values of all parameters.
170
171The second method allows some determination of the parameter values by
172the user. Type:
173
174 >  Duchamp -p parameterFile
175
176where parameterFile is a file with the input parameters, including the
177name of the cube you want to search. There are two example input files
178included with the distribution. The smaller one, InputExample, shows
179the typical parameters one might want to set. The large one,
180InputComplete, lists all possible parameters that can be entered, and
181a brief description of them. To get going quickly, just replace the
182"your-file-here" in InputExample with your image name, and type
183
184 >  Duchamp -p InputExample
185
186By default, a map of detections is displayed in a PGPLOT
187X-window. This can be disabled by using the flagXOutput parameter, or
188using the -x command-line option along with the -f or -p options. The
189-x option will override the setting in the parameter file.
190
191A User's Guide in the docs/ directory provides complete
192documentation. It comes in both postscript and portable document
193format (pdf -- note that this contains hyperlinks). This guide will
194provide full descriptions of all parameters, and of all steps in the
195execution of Duchamp.
196
197Any questions, please contact me. To report problems or bugs, or to
198suggest improvements, please go to the Duchamp Trac wiki site:
199http://svn.atnf.csiro.au/trac/duchamp/newticket
200and submit a "ticket", or view previously submitted reports.
201
202Acknowledging the use of Duchamp
203================================
204
205Duchamp is provided in the hope that it will be useful for your
206research. If you find that it is, I would ask that you acknowledge it
207in your publication by using the following:
208"This research made use of the Duchamp source finder, produced at
209the Australia Telescope National Facility, CSIRO, by M. Whiting."
210
211There is a journal paper under preparation that describes Duchamp, but
212until that is published, you can refer to the following conference
213proceedings paper:
214"Astronomers! Do you know where your galaxies are?", M.Whiting,
215proceedings of Local Volume meeting (held July 8-13 2007),
216Astrophysics & Space Science, Eds. B.Koribalski & H.Jerjen, in press.
217
218-------
219Author:
220  Matthew Whiting, Australia Telescope National Facility, November 2007
221  Matthew.Whiting [at] csiro.au
222
Note: See TracBrowser for help on using the repository browser.