source: trunk/docs/app-install.tex @ 167

Last change on this file since 167 was 158, checked in by Matthew Whiting, 18 years ago

Changed the layout of the Guide, so that each section has its own .tex file.
This makes it a bit easier to edit.
Also changed the layout of the title page, and added some page breaks between
sections.
Bibliography is now a .bib file, controlled by mn2e.bst. Might look at
using a different one that can incorporate hyperlinks...

File size: 4.0 KB
Line 
1\secA{Obtaining and installing \duchamp}
2\label{app-install}
3
4The \duchamp\ web page can be found at the following location:\\
5\href{http://www.atnf.csiro.au/people/Matthew.Whiting/Duchamp}%
6{http://www.atnf.csiro.au/people/Matthew.Whiting/Duchamp}\\
7Here you can find a gzipped tar archive of the source code that can be
8downloaded and extracted, as well as this User's Guide in postscript
9and hyperlinked PDF formats.
10
11To build \duchamp, you will need three main external libraries:
12\textsc{pgplot}, \textsc{cfitsio} and \textsc{wcslib}. If these are not present on your system,
13you can download them from the following locations:
14\begin{itemize}
15\item \textsc{pgplot}:
16\href{http://www.astro.caltech.edu/~tjp/pgplot/}%
17{http://www.astro.caltech.edu/~tjp/pgplot/}
18\item \textsc{cfitsio}:
19\href{http://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio.html}%
20{http://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio.html}
21\item \textsc{wcslib}:
22\href{http://www.atnf.csiro.au/people/Mark.Calabretta/WCS/index.html}%
23{http://www.atnf.csiro.au/people/Mark.Calabretta/WCS/index.html}
24\end{itemize}
25
26\duchamp\ can be built on Unix/Linux systems by typing (assuming that
27the prompt your terminal provides is a \texttt{> } -- don't type this
28character!):
29\begin{quote}
30\texttt{%
31> ./configure\\
32> make\\
33> make clean (optional -- to remove the object files)}
34\end{quote}
35
36Run in this manner, \texttt{configure} should find all the necessary
37libraries, but if some libraries have been installed in non-standard
38locations, it may fail. In this case, you can specify additional
39directories to look in by giving extra command-line arguments. There
40are separate options for library files (eg. libcpgplot.a) and header
41files (eg. cpgplot.h).
42
43For example, suppose \textsc{wcslib} had been locally installed in
44\texttt{/home/mduchamp/wcslib}. There will then be two libraries
45created that are likely to be in the following subdirectories:
46\texttt{C/} and \texttt{pgsbox/}. Each subdirectory needs to be
47searched for library and header files, so one could build Duchamp by
48typing:
49\begin{quote}
50\texttt{%
51>  ./configure $\backslash$ \\
52LIBDIRS="/home/mduchamp/wcslib/C /home/mduchamp/wcslib/pgsbox"
53$\backslash$\\
54INCDIRS="/home/mduchamp/wcslib/C /home/mduchamp/wcslib/pgsbox"}
55\end{quote}
56And then just run make in the usual fashion:
57\begin{quote}
58\texttt{> make}
59\end{quote}
60
61This will produce the executable \texttt{Duchamp}. You can verify that
62it is running correctly by running the verification shell script:
63\begin{quote}
64\texttt{> VerifyDuchamp.sh}
65\end{quote}
66This will use a dummy FITS image in the \texttt{verification/}
67directory -- this image has some Gaussian random noise, with five
68Gaussian sources present, plus a dummy WCS. The script runs
69Duchamp on this image with three different sets of inputs, and
70compares to known results, looking for differences and reporting
71any. There should be none reported if everything is working correctly.
72
73You can then run \duchamp\ on your own data. This can be done in one
74of two ways. The first is:
75\begin{quote}
76\texttt{> Duchamp -f [FITS file]}
77\end{quote}
78where \texttt{[FITS file]} is the file you wish to search. This method
79simply uses the default values of all parameters.
80
81The second method allows some determination of the parameter values by
82the user. Type:
83\begin{quote}
84\texttt{> Duchamp -p [parameter file]}
85\end{quote}
86where \texttt{[parameterFile]} is a file with the input parameters,
87including the name of the cube you want to search. There are two
88example input files included with the distribution. The smaller one,
89\texttt{InputExample}, shows the typical parameters one might want to
90set. The large one, \texttt{InputComplete}, lists all possible
91parameters that can be entered, and a brief description of them. To
92get going quickly, just replace the "your-file-here" in
93\texttt{InputExample} with your image name, and type
94\begin{quote}
95\texttt{> Duchamp -p InputExample}
96\end{quote}
97
98The following appendices provide details on the individual parameters,
99and show examples of the output files that \duchamp\ produces.
Note: See TracBrowser for help on using the repository browser.