source: branches/pixel-map-branch/README-beta

Last change on this file was 253, checked in by Matthew Whiting, 17 years ago
  • Added a mergeList(vector<Scan>) function to the PixelMap? namespace. This is usefu

l for combining lists of Scans into a set of independent ones.

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