source: trunk/README @ 338

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

Getting the trunk up to date with the improvements to the configure/make setup, plus the documentation, that was done for v1.1.1.

File size: 7.0 KB
Line 
1-----------------------------------------------------------------------
2               The Duchamp Source Finder
3-----------------------------------------------------------------------
4Duchamp 1.1.1 -- 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. eg:
93
94 >  ./configure --prefix=/home/mduchamp/bin
95
96
97If the above-mentioned libraries have been installed in non-standard
98locations, or you have more than one version installed on your system,
99you can specify specific locations by using the --with-cfitsio=<dir>,
100--with-wcslib=<dir> or --with-pgplot=<dir> flags. For example:
101
102 >  ./configure --with-wcslib=/home/mduchamp/wcslib-4.2
103And then just run make in the usual fashion:
104 >  make
105
106Duchamp can be compiled without PGPLOT if it is not installed on your
107system -- the searching and text-based output remains the same, but
108you will not have any graphical output.
109To manually specify this option, use the --without-pgplot flag, eg:
110
111 >  ./configure --without-pgplot
112
113(Note that CFITSIO and WCSLIB are essential, however, so
114--without-wcslib or --without-cfitsio will not work.).
115Even if you do not give the --without-pgplot option, and the PGPLOT
116library is not found, Duchamp will still compile (albeit without
117graphical capabilities).
118
119
120Testing
121=======
122
123There is a script included in the distribution that allows you to make
124sure Duchamp is running correctly. It will use a dummy FITS image in
125the verification/ directory -- this image has some Gaussian random
126noise, with five Gaussian sources present, plus a dummy WCS. The
127script runs Duchamp on this image with three different sets of inputs,
128and compares to known results, looking for differences and reporting
129any. There should be none reported if everything is working
130correctly. To run, enter the command
131
132 >  VerifyDuchamp.sh
133
134You can also use the dummy image for your own testing if you like (for
135instance, testing different thresholds to get a feel for how the
136program works).
137
138
139Using Duchamp
140=============
141
142There are two possible ways to run Duchamp. The first is:
143
144 >  Duchamp -f image.fits
145
146where image.fits is the data cube to be searched. This method simply
147uses the default values of all parameters.
148
149The second method allows some determination of the parameter values by
150the user. Type:
151
152 >  Duchamp -p parameterFile
153
154where parameterFile is a file with the input parameters, including the
155name of the cube you want to search. There are two example input files
156included with the distribution. The smaller one, InputExample, shows
157the typical parameters one might want to set. The large one,
158InputComplete, lists all possible parameters that can be entered, and
159a brief description of them. To get going quickly, just replace the
160"your-file-here" in InputExample with your image name, and type
161
162 >  Duchamp -p InputExample
163
164By default, a map of detections is displayed in a PGPLOT
165X-window. This can be disabled by using the flagXOutput parameter, or
166using the -x command-line option along with the -f or -p options. The
167-x option will override the setting in the parameter file.
168
169A User's Guide in the docs/ directory provides complete
170documentation. It comes in both postscript and portable document
171format (pdf -- note that this contains hyperlinks). This guide will
172provide full descriptions of all parameters, and of all steps in the
173execution of Duchamp.
174
175Any questions, please contact me. To report problems or bugs, or to
176suggest improvements, please go to the Duchamp Trac wiki site:
177http://svn.atnf.csiro.au/trac/duchamp/newticket
178and submit a "ticket", or view previously submitted reports.
179
180-------
181Author:
182  Matthew Whiting, Australia Telescope National Facility, July 2007
183  Matthew.Whiting [at] csiro.au
184
Note: See TracBrowser for help on using the repository browser.