source: tags/release-1.1.1/README-beta

Last change on this file was 305, checked in by Matthew Whiting, 17 years ago

Minor updates.

File size: 6.8 KB
Line 
1-----------------------------------------------------------------------
2               The Duchamp Source Finder
3-----------------------------------------------------------------------
4Duchamp -- 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 15/5/2007, is known as the beta
50version. (The version number when "Duchamp -v" is run is given as 1.1
51though.) It is more recent than the most recent release (v1.0.7), as
52it has several new functions and features. The user should be aware
53that these may not yet be documented and, while they have been tested
54on a limited number of cases, their stability is not assured to the
55same level as a proper numbered release.
56
57The beta version is provided more for testing purposes -- if users
58want a reliable version of the code that matches the documentation,
59please use the latest release available from the webpage given below.
60
61Having said all that, do note that I won't post a beta version on the
62website unless I know that it is functioning in most cases, so it
63should work to a large degree (and if it doesn't -- let me know!)
64
65Obtaining and Building Duchamp
66------------------------------
67
68The Duchamp web page is at
69http://www.atnf.csiro.au/people/Matthew.Whiting/Duchamp
70where you can download a gzipped tar archive of the source code.
71
72Duchamp uses three main external libraries: pgplot, cfitsio (version
732.5 and greater, version 3+ preferred) and wcslib. If you do not have
74the libraries, they can be downloaded from the following locations:
75
76PGPlot -- http://www.astro.caltech.edu/~tjp/pgplot/
77cfitsio -- http://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio.html
78wcslib -- http://www.atnf.csiro.au/people/Mark.Calabretta/WCS/index.html
79
80Duchamp can be built on Unix systems by typing (note that the terminal
81prompt here is represented by > -- don't type this character!):
82
83 >  ./configure
84 >  make
85 >  make clean (optional -- to remove the object files from the src
86                directory)
87
88This way, configure should find all the necessary libraries, but if
89the above-mentioned libraries have been installed in non-standard
90locations, you can specify additional directories to look in. There
91are separate options for library files (eg. libcpgplot.a) and header
92files (eg. cpgplot.h).
93
94For example, suppose wcslib had been locally installed in
95/home/mduchamp/wcslib. There will then be two libraries created that
96are likely to be in separate subdirectories: C/ and pgsbox/. Each
97subdirectory needs to be searched for library and header files, so one
98could build Duchamp by typing:
99
100 >  ./configure \
101LIBDIRS="/home/mduchamp/wcslib/C /home/mduchamp/wcslib/pgsbox" \
102INCDIRS="/home/mduchamp/wcslib/C /home/mduchamp/wcslib/pgsbox"
103And then just run make in the usual fashion:
104 >  make
105
106There is a script included in the distribution that allows you to make
107sure Duchamp is running correctly. It will use a dummy FITS image in
108the verification/ directory -- this image has some Gaussian random
109noise, with five Gaussian sources present, plus a dummy WCS. The
110script runs Duchamp on this image with three different sets of inputs,
111and compares to known results, looking for differences and reporting
112any. There should be none reported if everything is working
113correctly. To run, enter the command
114
115 >  VerifyDuchamp.sh
116
117You can also use the dummy image for your own testing if you like (for
118instance, testing different thresholds to get a feel for how the
119program works).
120
121
122Using Duchamp
123---------------
124
125There are two possible ways to run Duchamp. The first is:
126
127 >  Duchamp -f image.fits
128
129where image.fits is the data cube to be searched. This method simply
130uses the default values of all parameters.
131
132The second method allows some determination of the parameter values by
133the user. Type:
134
135 >  Duchamp -p parameterFile
136
137where parameterFile is a file with the input parameters, including the
138name of the cube you want to search. There are two example input files
139included with the distribution. The smaller one, InputExample, shows
140the typical parameters one might want to set. The large one,
141InputComplete, lists all possible parameters that can be entered, and
142a brief description of them. To get going quickly, just replace the
143"your-file-here" in InputExample with your image name, and type
144
145 >  Duchamp -p InputExample
146
147By default, a map of detections is displayed in a PGPLOT
148X-window. This can be disabled by using the flagXOutput parameter, or
149using the -x command-line option along with the -f or -p options. The
150-x option will override the setting in the parameter file.
151
152A User's Guide in the docs/ directory provides complete
153documentation. It comes in both postscript and portable document
154format (pdf -- note that this contains hyperlinks). This guide will
155provide full descriptions of all parameters, and of all steps in the
156execution of Duchamp.
157
158Any questions, please contact me. To report problems or bugs, or to
159suggest improvements, please go to the Duchamp Trac wiki site:
160http://sourcecode.atnf.csiro.au/cgi-bin/trac_duchamp.cgi/newticket
161and submit a "ticket", or view previously submitted reports.
162
163Author:
164  Matthew Whiting, Australia Telescope National Facility, May 2007
165  Matthew.Whiting [at] csiro.au
166
Note: See TracBrowser for help on using the repository browser.