source: trunk/README-beta

Last change on this file was 1181, checked in by MatthewWhiting, 11 years ago

Updating version number and date in preparation for tagging 1.3

File size: 8.8 KB
Line 
1-----------------------------------------------------------------------
2               The Duchamp Source Finder
3-----------------------------------------------------------------------
4Duchamp 1.3-beta -- 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
46The "Beta" Version
47==================
48
49This distribution of Duchamp, dated 11/5/2009, is known as the beta
50version. It is more recent than the most recent release (v1.1.7), as
51it has several new functions and features. It is being released as a
52beta version as it is close to a full release, but there are a few
53checks and so on that still need to be done. When 1.2 is released,
54it should be used instead.
55
56The beta version is provided more for testing purposes -- if users
57want a reliable version of the code that matches the documentation,
58please use the latest release available from the webpage given below.
59
60Having said all that, do note that I won't post a beta version on the
61website unless I know that it is functioning in most cases, so it
62should work to a large degree (and if it doesn't -- let me know!)
63
64
65
66Obtaining and Building Duchamp
67==============================
68
69The Duchamp web page is at
70http://www.atnf.csiro.au/people/Matthew.Whiting/Duchamp
71where you can download a gzipped tar archive of the source code.
72
73Duchamp uses three main external libraries: pgplot (although see note
74below), cfitsio (version 2.5 and greater, version 3+ preferred) and
75wcslib. If you do not have the libraries, they can be downloaded from
76the following locations:
77
78PGPLOT -- http://www.astro.caltech.edu/~tjp/pgplot/
79cfitsio -- http://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio.html
80wcslib -- http://www.atnf.csiro.au/people/Mark.Calabretta/WCS/index.html
81
82Note that PGPLOT is optional. Duchamp can be compiled and run without
83PGPLOT, but you will miss out on the useful graphical outputs!  The
84other two libraries, cftisio and wcslib, are essential.
85
86
87Basic Compilation and Installation
88----------------------------------
89
90Duchamp can be built and installed on Unix systems by typing (note
91that the terminal prompt here is represented by > -- don't type this
92character!):
93
94 >  ./configure
95 >  make
96 >  make clean (optional -- to remove the object files from the src
97                directory)
98 >  make install
99
100This default setup will search in standard locations for the necessary
101libraries, and install the executable ("Duchamp") in /usr/local/bin (a
102copy will also be in the current directory). If you want this to go
103somewhere else, eg if you don't have write-access to that directory,
104or you need to tweak the libraries, see the next section. Otherwise,
105jump to the testing section.
106
107
108Tweaking the installation setup
109-------------------------------
110
111To install Duchamp in a directory other than /usr/local/bin, use the
112--prefix option with configure, specifying the directory above the
113\texttt{bin/} directory. eg:
114
115 >  ./configure --prefix=/home/mduchamp
116
117which, if you run "make" and "make install", will result in the binary
118being put in the directory /home/mduchamp/bin.
119
120If the above-mentioned libraries have been installed in non-standard
121locations, or you have more than one version installed on your system,
122you can specify specific locations by using the --with-cfitsio=<dir>,
123--with-wcslib=<dir> or --with-pgplot=<dir> flags. For example:
124
125 >  ./configure --with-wcslib=/home/mduchamp/wcslib-4.2
126And then just run make in the usual fashion:
127 >  make
128
129Duchamp can be compiled without PGPLOT if it is not installed on your
130system -- the searching and text-based output remains the same, but
131you will not have any graphical output.
132To manually specify this option, use the --without-pgplot flag, eg:
133
134 >  ./configure --without-pgplot
135
136(Note that CFITSIO and WCSLIB are essential, however, so
137--without-wcslib or --without-cfitsio will not work.).
138Even if you do not give the --without-pgplot option, and the PGPLOT
139library is not found, Duchamp will still compile (albeit without
140graphical capabilities).
141
142
143Installing on Mac OS X with gfortran
144------------------------------------
145
146Some recent testing on a Mac with OS X and gfortran has shown that
147slight tweaking needs to be done with the use of configure. In
148addition to the options noted above, configure should be run with F77
149set to the desired fortran compiler command. Note that this should be
150the same as that used to compile the pgplot package, if you are using
151it: gfortran is probably the best choice.
152This is done simply by:
153
154 >  ./configure F77=gfortran ...[other options]...
155
156
157Testing
158=======
159
160There is a script included in the distribution that allows you to make
161sure Duchamp is running correctly. It will use a dummy FITS image in
162the verification/ directory -- this image has some Gaussian random
163noise, with five Gaussian sources present, plus a dummy WCS. The
164script runs Duchamp on this image with three different sets of inputs,
165and compares to known results, looking for differences and reporting
166any. There should be none reported if everything is working
167correctly. To run, enter the command
168
169 >  VerifyDuchamp.sh
170
171Once you know it is working, you can install Duchamp on your system
172with the command
173
174 > make install
175
176You can also use the dummy image for your own testing if you like (for
177instance, testing different thresholds to get a feel for how the
178program works).
179
180
181Using Duchamp
182=============
183
184There are two possible ways to run Duchamp. The first is:
185
186 >  Duchamp -f image.fits
187
188where image.fits is the data cube to be searched. This method simply
189uses the default values of all parameters.
190
191The second method allows some determination of the parameter values by
192the user. Type:
193
194 >  Duchamp -p parameterFile
195
196where parameterFile is a file with the input parameters, including the
197name of the cube you want to search. There are two example input files
198included with the distribution. The smaller one, InputExample, shows
199the typical parameters one might want to set. The large one,
200InputComplete, lists all possible parameters that can be entered, and
201a brief description of them. To get going quickly, just replace the
202"your-file-here" in InputExample with your image name, and type
203
204 >  Duchamp -p InputExample
205
206By default, a map of detections is displayed in a PGPLOT
207X-window. This can be disabled by using the flagXOutput parameter, or
208using the -x command-line option along with the -f or -p options. The
209-x option will override the setting in the parameter file.
210
211You can specify a flux threshold from the command line by using the -t
212option. This is particularly useful when combined with -f to enable a
213quick search to some flux level:
214
215 >  Duchamp -f image.fits -t 0.001
216
217A User's Guide in the docs/ directory provides complete
218documentation. It comes in both postscript and portable document
219format (pdf -- note that this contains hyperlinks). This guide will
220provide full descriptions of all parameters, and of all steps in the
221execution of Duchamp.
222
223Any questions, please contact me. To report problems or bugs, or to
224suggest improvements, please go to the Duchamp Trac wiki site:
225http://svn.atnf.csiro.au/trac/duchamp/newticket
226and submit a "ticket", or view previously submitted reports.
227
228-------
229Author:
230  Matthew Whiting, Australia Telescope National Facility, May 2009
231  Matthew.Whiting [at] csiro.au
232
Note: See TracBrowser for help on using the repository browser.