[158] | 1 | \secA{Obtaining and installing \duchamp} |
---|
| 2 | \label{app-install} |
---|
| 3 | |
---|
| 4 | The \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}\\ |
---|
| 7 | Here you can find a gzipped tar archive of the source code that can be |
---|
| 8 | downloaded and extracted, as well as this User's Guide in postscript |
---|
| 9 | and hyperlinked PDF formats. |
---|
| 10 | |
---|
| 11 | To 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, |
---|
| 13 | you 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 |
---|
| 27 | the prompt your terminal provides is a \texttt{> } -- don't type this |
---|
| 28 | character!): |
---|
| 29 | \begin{quote} |
---|
| 30 | \texttt{% |
---|
| 31 | > ./configure\\ |
---|
| 32 | > make\\ |
---|
| 33 | > make clean (optional -- to remove the object files)} |
---|
| 34 | \end{quote} |
---|
| 35 | |
---|
| 36 | Run in this manner, \texttt{configure} should find all the necessary |
---|
| 37 | libraries, but if some libraries have been installed in non-standard |
---|
| 38 | locations, it may fail. In this case, you can specify additional |
---|
| 39 | directories to look in by giving extra command-line arguments. There |
---|
| 40 | are separate options for library files (eg. libcpgplot.a) and header |
---|
| 41 | files (eg. cpgplot.h). |
---|
| 42 | |
---|
| 43 | For example, suppose \textsc{wcslib} had been locally installed in |
---|
| 44 | \texttt{/home/mduchamp/wcslib}. There will then be two libraries |
---|
| 45 | created that are likely to be in the following subdirectories: |
---|
| 46 | \texttt{C/} and \texttt{pgsbox/}. Each subdirectory needs to be |
---|
| 47 | searched for library and header files, so one could build Duchamp by |
---|
| 48 | typing: |
---|
| 49 | \begin{quote} |
---|
| 50 | \texttt{% |
---|
| 51 | > ./configure $\backslash$ \\ |
---|
| 52 | LIBDIRS="/home/mduchamp/wcslib/C /home/mduchamp/wcslib/pgsbox" |
---|
| 53 | $\backslash$\\ |
---|
| 54 | INCDIRS="/home/mduchamp/wcslib/C /home/mduchamp/wcslib/pgsbox"} |
---|
| 55 | \end{quote} |
---|
| 56 | And then just run make in the usual fashion: |
---|
| 57 | \begin{quote} |
---|
| 58 | \texttt{> make} |
---|
| 59 | \end{quote} |
---|
| 60 | |
---|
| 61 | This will produce the executable \texttt{Duchamp}. You can verify that |
---|
| 62 | it is running correctly by running the verification shell script: |
---|
| 63 | \begin{quote} |
---|
| 64 | \texttt{> VerifyDuchamp.sh} |
---|
| 65 | \end{quote} |
---|
| 66 | This will use a dummy FITS image in the \texttt{verification/} |
---|
| 67 | directory -- this image has some Gaussian random noise, with five |
---|
| 68 | Gaussian sources present, plus a dummy WCS. The script runs |
---|
| 69 | Duchamp on this image with three different sets of inputs, and |
---|
| 70 | compares to known results, looking for differences and reporting |
---|
| 71 | any. There should be none reported if everything is working correctly. |
---|
| 72 | |
---|
| 73 | You can then run \duchamp\ on your own data. This can be done in one |
---|
| 74 | of two ways. The first is: |
---|
| 75 | \begin{quote} |
---|
| 76 | \texttt{> Duchamp -f [FITS file]} |
---|
| 77 | \end{quote} |
---|
| 78 | where \texttt{[FITS file]} is the file you wish to search. This method |
---|
| 79 | simply uses the default values of all parameters. |
---|
| 80 | |
---|
| 81 | The second method allows some determination of the parameter values by |
---|
| 82 | the user. Type: |
---|
| 83 | \begin{quote} |
---|
| 84 | \texttt{> Duchamp -p [parameter file]} |
---|
| 85 | \end{quote} |
---|
| 86 | where \texttt{[parameterFile]} is a file with the input parameters, |
---|
| 87 | including the name of the cube you want to search. There are two |
---|
| 88 | example input files included with the distribution. The smaller one, |
---|
| 89 | \texttt{InputExample}, shows the typical parameters one might want to |
---|
| 90 | set. The large one, \texttt{InputComplete}, lists all possible |
---|
| 91 | parameters that can be entered, and a brief description of them. To |
---|
| 92 | get 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 | |
---|
| 98 | The following appendices provide details on the individual parameters, |
---|
| 99 | and show examples of the output files that \duchamp\ produces. |
---|