source: tags/release-1.1.7/README

Last change on this file was 529, checked in by MatthewWhiting, 15 years ago

Preparing for the next version: 1.1.7

File size: 8.9 KB
Line 
1-----------------------------------------------------------------------
2               The Duchamp Source Finder
3-----------------------------------------------------------------------
4Duchamp 1.1.7 -- 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 lib   (optional -- this makes a library for use in code
77                development)
78 >  make clean (again optional -- to remove the object files from the
79                src directory)
80 >  make install
81
82This default setup will search in standard locations for the necessary
83libraries, and install the executable ("Duchamp") in /usr/local/bin (a
84copy will also be in the current directory). It also installs the
85library libduchamp.a in /usr/local/lib and the header (.hh) files in
86/usr/local/include/duchamp. If you want these to go somewhere else, eg
87if you don't have write-access to that directory, or you need to tweak
88the libraries, see the next section. Otherwise, jump to the testing
89section.
90
91
92Tweaking the installation setup
93-------------------------------
94
95To install Duchamp in a directory other than /usr/local/bin, use the
96--prefix option with configure, specifying the directory above the
97\texttt{bin/} directory. eg:
98
99 >  ./configure --prefix=/home/mduchamp
100
101which, if you run "make" and "make install", will result in the binary
102being put in the directory /home/mduchamp/bin. Similarly the library
103will be put in /home/mduchamp/lib and the header files in
104/home/mduchamp/include/duchamp and subdirectories thereof.
105
106If the above-mentioned libraries have been installed in non-standard
107locations, or you have more than one version installed on your system,
108you can specify specific locations by using the --with-cfitsio=<dir>,
109--with-wcslib=<dir> or --with-pgplot=<dir> flags. For example:
110
111 >  ./configure --with-wcslib=/home/mduchamp/wcslib-4.2
112And then just run make in the usual fashion:
113 >  make
114
115Duchamp can be compiled without PGPLOT if it is not installed on your
116system -- the searching and text-based output remains the same, but
117you will not have any graphical output.
118To manually specify this option, use the --without-pgplot flag, eg:
119
120 >  ./configure --without-pgplot
121
122(Note that CFITSIO and WCSLIB are essential, however, so
123--without-wcslib or --without-cfitsio will not work.).
124Even if you do not give the --without-pgplot option, and the PGPLOT
125library is not found, Duchamp will still compile (albeit without
126graphical capabilities).
127
128
129Installing on Mac OS X with gfortran
130------------------------------------
131
132Some recent testing on a Mac with OS X and gfortran has shown that
133slight tweaking needs to be done with the use of configure. In
134addition to the options noted above, configure should be run with F77
135set to the desired fortran compiler command. Note that this should be
136the same as that used to compile the pgplot package, if you are using
137it: gfortran is probably the best choice.
138This is done simply by:
139
140 >  ./configure F77=gfortran ...[other options]...
141
142
143Testing
144=======
145
146There is a script included in the distribution that allows you to make
147sure Duchamp is running correctly. It will use a dummy FITS image in
148the verification/ directory -- this image has some Gaussian random
149noise, with five Gaussian sources present, plus a dummy WCS. The
150script runs Duchamp on this image with three different sets of inputs,
151and compares to known results, looking for differences and reporting
152any. There should be none reported if everything is working
153correctly. To run, enter the command
154
155 >  ./VerifyDuchamp.sh
156
157Once you know it is working, you can install Duchamp on your system
158with the command
159
160 > make install
161
162You can also use the dummy image for your own testing if you like (for
163instance, testing different thresholds to get a feel for how the
164program works).
165
166
167Using Duchamp
168=============
169
170There are two possible ways to run Duchamp. The first is:
171
172 >  Duchamp -f image.fits
173
174where image.fits is the data cube to be searched. This method simply
175uses the default values of all parameters.
176
177The second method allows some determination of the parameter values by
178the user. Type:
179
180 >  Duchamp -p parameterFile
181
182where parameterFile is a file with the input parameters, including the
183name of the cube you want to search. There are two example input files
184included with the distribution. The smaller one, InputExample, shows
185the typical parameters one might want to set. The large one,
186InputComplete, lists all possible parameters that can be entered, and
187a brief description of them. To get going quickly, just replace the
188"your-file-here" in InputExample with your image name, and type
189
190 >  Duchamp -p InputExample
191
192By default, a map of detections is displayed in a PGPLOT
193X-window. This can be disabled by using the flagXOutput parameter, or
194using the -x command-line option along with the -f or -p options. The
195-x option will override the setting in the parameter file.
196
197A User's Guide in the docs/ directory provides complete
198documentation. It comes in both postscript and portable document
199format (pdf -- note that this contains hyperlinks). This guide will
200provide full descriptions of all parameters, and of all steps in the
201execution of Duchamp.
202
203Any questions, please contact me. To report problems or bugs, or to
204suggest improvements, please go to the Duchamp Trac wiki site:
205http://svn.atnf.csiro.au/trac/duchamp/newticket
206and submit a "ticket", or view previously submitted reports.
207
208Acknowledging the use of Duchamp
209================================
210
211Duchamp is provided in the hope that it will be useful for your
212research. If you find that it is, I would ask that you acknowledge it
213in your publication by using the following:
214"This research made use of the Duchamp source finder, produced at
215the Australia Telescope National Facility, CSIRO, by M. Whiting."
216
217There is a journal paper under preparation that describes Duchamp, but
218until that is published, you can refer to the following paper in the
219proceedings of Local Volume meeting (held July 8-13 2007):
220
221"Astronomers! Do you know where your galaxies are?", M.Whiting, in
222"Galaxies in the Local Volume", Eds. B.Koribalski & H.Jerjen,
223Astrophysics & Space Science Proceedings, Springer, 2008
224
225-------
226Author:
227  Matthew Whiting, Australia Telescope National Facility, January 2009
228  Matthew.Whiting [at] csiro.au
229
Note: See TracBrowser for help on using the repository browser.