source: tags/release-1.6.1/README

Last change on this file was 1391, checked in by MatthewWhiting, 10 years ago

Changing the version number to 1.6.1 in preparation for patch release #228

File size: 10.0 KB
Line 
1-----------------------------------------------------------------------
2               The Duchamp Source Finder
3-----------------------------------------------------------------------
4Duchamp 1.6.1 -- an object finder for spectral-line data cubes
5Copyright (C) 2006-2014
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 libraries 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
86libraries libduchamp.1.6.a and libduchamp.1.6.so in /usr/local/lib and
87the header (.hh) files in /usr/local/include/duchamp. If you want
88these to go somewhere else, eg if you don't have write-access to that
89directory, or you need to tweak the libraries, see the next
90section. Otherwise, jump to the testing section.
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
113
114And then just run make in the usual fashion:
115
116 >  make
117
118Duchamp can be compiled without PGPLOT if it is not installed on your
119system -- the searching and text-based output remains the same, but
120you will not have any graphical output.
121To manually specify this option, use the --without-pgplot flag, eg:
122
123 >  ./configure --without-pgplot
124
125(Note that CFITSIO and WCSLIB are essential, however, so
126--without-wcslib or --without-cfitsio will not work.).
127Even if you do not give the --without-pgplot option, and the PGPLOT
128library is not found, Duchamp will still compile (albeit without
129graphical capabilities).
130
131Troubleshooting the installation
132--------------------------------
133
134There may be issues with the configure/make/install process that arise
135from non-standard locations of key libraries. The User's Guide has a
136section in Appendix A discussing some of the more common problems
137and potential solutions.
138
139Feeback is welcome if you have trouble getting Duchamp working -- see
140the feedback section below.
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
157This performs basic checks on the output files, but ignoring most of
158the actual values of source parameters (to avoid picking up just
159differences due to precision errors). For complete checks of the
160files, run
161
162 > ./VerifyDuchamp.sh -f
163
164Be warned that on some systems this could provide a large number of
165apparent errors which may only be due to precision differences.
166
167Once you know it is working, you can install Duchamp on your system
168with the command
169
170 > make install
171
172(this may need to be run as sudo depending on your system setup and
173your prefix directory).
174
175You can also use the dummy image for your own testing if you like (for
176instance, testing different thresholds to get a feel for how the
177program works).
178
179
180Using Duchamp
181=============
182
183There are two possible ways to run Duchamp. The first is:
184
185 >  Duchamp -f image.fits
186
187where image.fits is the data cube to be searched. This method simply
188uses the default values of all parameters.
189
190The second method allows some determination of the parameter values by
191the user. Type:
192
193 >  Duchamp -p parameterFile
194
195where parameterFile is a file with the input parameters, including the
196name of the cube you want to search. There are two example input files
197included with the distribution. The smaller one, InputExample, shows
198the typical parameters one might want to set. The large one,
199InputComplete, lists all possible parameters that can be entered, and
200a brief description of them. To get going quickly, just replace the
201"your-file-here" in InputExample with your image name, and type
202
203 >  Duchamp -p InputExample
204
205By default, a map of detections is displayed in a PGPLOT
206X-window. This can be disabled by using the flagXOutput parameter, or
207using the -x command-line option along with the -f or -p options. The
208-x option will override the setting in the parameter file.
209
210You can specify a flux threshold from the command line by using the -t
211option. This is particularly useful when combined with -f to enable a
212quick search to some flux level:
213
214 >  Duchamp -f image.fits -t 0.001
215
216A User's Guide in the docs/ directory provides complete
217documentation. It comes in both postscript and portable document
218format (pdf -- note that this contains hyperlinks). This guide will
219provide full descriptions of all parameters, and of all steps in the
220execution of Duchamp.
221
222Feedback
223========
224
225Any questions, please contact me. To report problems or bugs, or to
226suggest improvements, please go to the Duchamp Trac wiki site:
227http://svn.atnf.csiro.au/trac/duchamp/newticket
228and submit a "ticket", or view previously submitted reports.
229
230Acknowledging the use of Duchamp
231================================
232
233Duchamp is provided in the hope that it will be useful for your
234research. If you find that it is, I would ask that you acknowledge it
235in your publication by using the following:
236"This research made use of the Duchamp source finder, produced at
237the Australia Telescope National Facility, CSIRO, by M. Whiting."
238
239The journal paper describing Duchamp, and providing basic comparative
240tests of its different functions, is Whiting 2012, MNRAS 421,
2413242, which can be found online at
242http://onlinelibrary.wiley.com/doi/10.1111/j.1365-2966.2012.20548.x/full.
243This paper should be cited when describing Duchamp.
244
245An earlier conference proceedings paper briefly describing it was:
246"Astronomers! Do you know where your galaxies are?", M.Whiting, in
247"Galaxies in the Local Volume", Eds. B.Koribalski & H.Jerjen,
248Astrophysics & Space Science Proceedings, Springer, 2008, p.343-344
249http://adsabs.harvard.edu/abs/2008glv..book..343W
250
251Those interested in the development of a source-finder for ASKAP
252(known for now as Selavy), which make use of the Duchamp code, should
253read Whiting & Humphreys 2012, PASA 29, 371, which can be found online
254at http://www.publish.csiro.au/paper/AS12028.htm
255
256-------
257Author:
258  Matthew Whiting, Australia Telescope National Facility, April 2014
259  Matthew.Whiting [at] csiro.au
260
Note: See TracBrowser for help on using the repository browser.