source: tags/release-1.3.1/README

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

Updating the CHANGES for the upcoming 1.3.1 release, plus updating the version number everywhere.

File size: 10.8 KB
Line 
1-----------------------------------------------------------------------
2               The Duchamp Source Finder
3-----------------------------------------------------------------------
4Duchamp 1.3.1 -- an object finder for spectral-line data cubes
5Copyright (C) 2006-2012
6Matthew Whiting, CSIRO Astronomy & Space Science
7
8Duchamp is free software; you can redistribute it and/or modify it
9under the terms of the GNU General Public License as published by the
10Free Software Foundation; either version 2 of the License, or (at your
11option) any later version.
12
13Duchamp is distributed in the hope that it will be useful, but WITHOUT
14ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
15FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
16for more details.
17
18You should have received a copy of the GNU General Public License
19along with Duchamp; if not, write to the Free Software Foundation,
20Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA
21
22Correspondence concerning Duchamp may be directed to:
23   Internet email: Matthew.Whiting [at] atnf.csiro.au
24   Postal address: Dr. Matthew Whiting
25                   Australia Telescope National Facility, CSIRO
26                   PO Box 76
27                   Epping NSW 1710
28                   AUSTRALIA
29-----------------------------------------------------------------------
30
31Introduction
32============
33
34Duchamp is a stand-alone program designed to find objects in
35astronomical data cubes, particularly spectral-line observations. Its
36features include a wavelet-based reconstruction technique for reducing
37the noise in the cube (and thereby enhancing detectability of
38sources), easy-to-use text-based interface, flexibility to control all
39relevant parameters such as detection thresholds, and a useful range
40of text- and graphics-based output.
41
42Duchamp works on any FITS image using the CFITSIO package, and uses
43Mark Calabretta's WCSLIB library to provide accurate position and
44velocity information for all detected sources.
45
46
47Obtaining and Building Duchamp
48==============================
49
50The Duchamp web page is at
51http://www.atnf.csiro.au/people/Matthew.Whiting/Duchamp
52where you can download a gzipped tar archive of the source code.
53
54Duchamp uses three main external libraries: pgplot (although see note
55below), cfitsio (version 2.5 and greater, version 3+ preferred) and
56wcslib. If you do not have the libraries, they can be downloaded from
57the following locations:
58
59PGPLOT -- http://www.astro.caltech.edu/~tjp/pgplot/
60cfitsio -- http://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio.html
61wcslib -- http://www.atnf.csiro.au/people/Mark.Calabretta/WCS/index.html
62
63Note that PGPLOT is optional. Duchamp can be compiled and run without
64PGPLOT, but you will miss out on the useful graphical outputs!  The
65other two libraries, cftisio and wcslib, are essential.
66
67
68Basic Compilation and Installation
69----------------------------------
70
71Duchamp can be built and installed on Unix systems by typing (note
72that the terminal prompt here is represented by > -- don't type this
73character!):
74
75 >  ./configure
76 >  make
77 >  make lib   (optional -- this makes a library for use in code
78                development)
79 >  make clean (again optional -- to remove the object files from the
80                src directory)
81 >  make install
82
83This default setup will search in standard locations for the necessary
84libraries, and install the executable ("Duchamp") in /usr/local/bin (a
85copy will also be in the current directory). It also installs the
86library libduchamp.a in /usr/local/lib and the header (.hh) files in
87/usr/local/include/duchamp. If you want these to go somewhere else, eg
88if you don't have write-access to that directory, or you need to tweak
89the libraries, see the next section. Otherwise, jump to the testing
90section.
91
92
93Tweaking the installation setup
94-------------------------------
95
96To install Duchamp in a directory other than /usr/local/bin, use the
97--prefix option with configure, specifying the directory above the
98\texttt{bin/} directory. eg:
99
100 >  ./configure --prefix=/home/mduchamp
101
102which, if you run "make" and "make install", will result in the binary
103being put in the directory /home/mduchamp/bin. Similarly the library
104will be put in /home/mduchamp/lib and the header files in
105/home/mduchamp/include/duchamp and subdirectories thereof.
106
107If the above-mentioned libraries have been installed in non-standard
108locations, or you have more than one version installed on your system,
109you can specify specific locations by using the --with-cfitsio=<dir>,
110--with-wcslib=<dir> or --with-pgplot=<dir> flags. For example:
111
112 >  ./configure --with-wcslib=/home/mduchamp/wcslib-4.2
113And then just run make in the usual fashion:
114 >  make
115
116Duchamp can be compiled without PGPLOT if it is not installed on your
117system -- the searching and text-based output remains the same, but
118you will not have any graphical output.
119To manually specify this option, use the --without-pgplot flag, eg:
120
121 >  ./configure --without-pgplot
122
123(Note that CFITSIO and WCSLIB are essential, however, so
124--without-wcslib or --without-cfitsio will not work.).
125Even if you do not give the --without-pgplot option, and the PGPLOT
126library is not found, Duchamp will still compile (albeit without
127graphical capabilities).
128
129
130Installing on Mac OS X with gfortran
131------------------------------------
132
133Some recent testing on a Mac with OS X and gfortran has shown that
134slight tweaking needs to be done with the use of configure. In
135addition to the options noted above, configure should be run with F77
136set to the desired fortran compiler command. Note that this should be
137the same as that used to compile the pgplot package, if you are using
138it: gfortran is probably the best choice.
139This is done simply by:
140
141 >  ./configure F77=gfortran ...[other options]...
142
143
144Fixing problems with the Makefile
145---------------------------------
146
147While the configure script tries to get everything right, it can
148exhibit some quirks. For instance, in getting the X11 library
149configuration right, it will sometimes provide a -R/path/to/X11
150argument for the linking string. This is accepted by ld, but not by
151all versions of gfortran. This can cause the final linking step to
152fail (and for the -lpgplot argument to be left off).
153
154To fix this, a shell script is provided to quickly patch the Makefile
155if necessary. If you run make and it fails, due to this error:
156   gfortran: error: unrecognized command line option ‘-R’
157or similar, run
158
159 > ./fixMakefile.sh
160
161and try again. If it still fails, you may have to manually edit the
162Makefile. Please log a bug report to let me know!
163
164Testing
165=======
166
167There is a script included in the distribution that allows you to make
168sure Duchamp is running correctly. It will use a dummy FITS image in
169the verification/ directory -- this image has some Gaussian random
170noise, with five Gaussian sources present, plus a dummy WCS. The
171script runs Duchamp on this image with three different sets of inputs,
172and compares to known results, looking for differences and reporting
173any. There should be none reported if everything is working
174correctly. To run, enter the command
175
176 >  ./VerifyDuchamp.sh
177
178This performs basic checks on the output files, but ignoring most of
179the actual values of source parameters (to avoid picking up just
180differences due to precision errors). For complete checks of the
181files, run
182
183 > ./VerifyDuchamp.sh -f
184
185Be warned that on some systems this could provide a large number of
186apparent errors which may only be due to precision differences.
187
188Once you know it is working, you can install Duchamp on your system
189with the command
190
191 > make install
192
193(this may need to be run as sudo depending on your system setup and
194your prefix directory).
195
196You can also use the dummy image for your own testing if you like (for
197instance, testing different thresholds to get a feel for how the
198program works).
199
200
201Using Duchamp
202=============
203
204There are two possible ways to run Duchamp. The first is:
205
206 >  Duchamp -f image.fits
207
208where image.fits is the data cube to be searched. This method simply
209uses the default values of all parameters.
210
211The second method allows some determination of the parameter values by
212the user. Type:
213
214 >  Duchamp -p parameterFile
215
216where parameterFile is a file with the input parameters, including the
217name of the cube you want to search. There are two example input files
218included with the distribution. The smaller one, InputExample, shows
219the typical parameters one might want to set. The large one,
220InputComplete, lists all possible parameters that can be entered, and
221a brief description of them. To get going quickly, just replace the
222"your-file-here" in InputExample with your image name, and type
223
224 >  Duchamp -p InputExample
225
226By default, a map of detections is displayed in a PGPLOT
227X-window. This can be disabled by using the flagXOutput parameter, or
228using the -x command-line option along with the -f or -p options. The
229-x option will override the setting in the parameter file.
230
231You can specify a flux threshold from the command line by using the -t
232option. This is particularly useful when combined with -f to enable a
233quick search to some flux level:
234
235 >  Duchamp -f image.fits -t 0.001
236
237A User's Guide in the docs/ directory provides complete
238documentation. It comes in both postscript and portable document
239format (pdf -- note that this contains hyperlinks). This guide will
240provide full descriptions of all parameters, and of all steps in the
241execution of Duchamp.
242
243Any questions, please contact me. To report problems or bugs, or to
244suggest improvements, please go to the Duchamp Trac wiki site:
245http://svn.atnf.csiro.au/trac/duchamp/newticket
246and submit a "ticket", or view previously submitted reports.
247
248Acknowledging the use of Duchamp
249================================
250
251Duchamp is provided in the hope that it will be useful for your
252research. If you find that it is, I would ask that you acknowledge it
253in your publication by using the following:
254"This research made use of the Duchamp source finder, produced at
255the Australia Telescope National Facility, CSIRO, by M. Whiting."
256
257The journal paper describing Duchamp, and providing basic comparative
258tests of its different functions, is Whiting 2012, MNRAS 421,
2593242, which can be found online at
260http://onlinelibrary.wiley.com/doi/10.1111/j.1365-2966.2012.20548.x/full.
261This paper should be cited when describing Duchamp.
262
263An earlier conference proceedings paper briefly describing it was:
264"Astronomers! Do you know where your galaxies are?", M.Whiting, in
265"Galaxies in the Local Volume", Eds. B.Koribalski & H.Jerjen,
266Astrophysics & Space Science Proceedings, Springer, 2008, p.343-344
267http://adsabs.harvard.edu/abs/2008glv..book..343W
268
269Those interested in the development of a source-finder for ASKAP
270(known for now as Selavy), which make use of the Duchamp code, should
271read Whiting & Humphreys 2012, PASA 29, 371, which can be found online
272at http://www.publish.csiro.au/paper/AS12028.htm
273
274-------
275Author:
276  Matthew Whiting, Australia Telescope National Facility, October 2012
277  Matthew.Whiting [at] csiro.au
278
Note: See TracBrowser for help on using the repository browser.