Switch branches/tags
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
134 lines (105 sloc) 5.12 KB
Basic steps to install:
1. Install FFTW3.X You need to compile FFTW for _single_
precision (see the config flags I recommend below).
For all architectures I recommend the following configuration:
./configure --enable-shared --enable-single
Use the --prefix=SOME_PATH option to install the library and
its related files to SOME_PATH. (If you have admin access to
your machine, --prefix=/usr/local is the default for FFTW and
is a safe bet).
If you are on a modern Intel processor and have a recent version
of GCC, you can get much improved performance by adding:
--enable-sse2 --enable-avx
Note that Ubuntu has good FFTW packages now (libfftw3-bin and
2. Install PGPLOT.
You need the X-windows and postscript drivers at a minimum.
Note that on 64-bit systems, compiling and linking PGPLOT can
be tricky!
It is very likely that you will need to have the PGPLOT_DIR
environment variable specified to allow the programs to link and to
allow PGPLOT to find its important files.
Note that Ubuntu has good PGPLOT packages now (pgplot5).
3. Install TEMPO. Make sure to set the TEMPO environment variable.
4. Install GLIB (v2.X). On Linux machines this
is almost certainly already on your system (check in /usr/lib
and /usr/include/glib*). Although you may need to install a
glib development package in order to have the required include
On Ubuntu, the package you need is: libglib2.0-dev
5. Install CFITSIO.
This is a very easy install and is now needed since PSRFITS
is now being written by several pulsar instruments (Nice!
a pulsar data standard that external tools can actually
view! How about that!)
Once again, Ubuntu has CFITSIO packages (libcfitsio3 and
6. Define the PRESTO environment variable to the top level
directory of the PRESTO distribution (i.e. this directory).
7. cd to $PRESTO/src. Check and modify the Makefile for your
machine of choice. Ensure that the library and include file
directories are correct for FFTW, PGPLOT, GLIB, CFITSIO,
and TEMPO.
8. If you are using FFTW, do a 'make makewisdom'. This gets
FFTW acquainted with your system. It is best if you are the
only user on the machine when you run this, as it is very
computation intensive and may take a while.
9. Just for safety's sake, do a "make prep". That will make sure
that make does not try to run Clig to re-generate all of the
command line interface files.
10. Do a 'make'. This will make all of the executables. If you
want mpiprepsubband (for parallel de-dispersion on clusters)
you will need to do a 'make mpi' as well.
11. The required libraries and miscellaneous files will be
located in $PRESTO/lib. The executable will be in $PRESTO/bin.
You may copy or move the executables wherever you like, but
the library files should stay put. (That's why you define the
PRESTO variable -- so the routines can find them).
Since dynamic linking will use $PRESTO/lib, you will need to make
sure that that is in your LD_LIBRARY_PATH environment variable (or
in some other way let your system know where to find the dynamic
libraries). Similarly, you will want $PRESTO/bin in your PATH.
12. If you want to save some disk space, do a 'make clean' in
the 'src' directory. This will leave the libraries and
binaries in their respective directories but will get rid of
all the extra stuff in the 'src' directory.
13. If you want to use all the python routines (which if you are
doing anything but the most rudimentary analyses you will want
to), you need Python >= version 2.7, and Numpy/Scipy and
In general, the following should work:
"cd $PRESTO/python ; make ; make fftfit"
If it doesnt, you will probably need to edit the Makefile
or (one problem that is common is that ppgplot_libraries
sometimes needs "gfortran" added...). Note that in order to
get python to find the modules and libraries, you should make
sure that your PYTHONPATH environment variable contains the
directory $PRESTO/lib/python.
14. Go find pulsars!
Couple quick trouble-shooting tips if you are having problems
compiling and running:
1. Environment variables!
-- Is PRESTO set to the top-level PRESTO source directory?
-- Is TEMPO set to the top-level TEMPO source directory?
-- Is PGPLOT_DIR set to the location of the PGPLOT utility files?
(Note: On Ubuntu, that should be /usr/lib/pgplot5)
-- Is $PRESTO/bin in your PATH?
-- Is $PRESTO/lib in your LD_LIBRARY_PATH?
-- Is $PRESTO/lib/python in your PYTHONPATH?
2. Have you have installed the relevant -dev packages for glib2, FFTW
and CFITSIO if you are using a Debian-based Linux distribution?
Here are the required packages:
3. If you are using a Mac, Paul Ray has been running PRESTO a lot and
knows several tricks to get it working...
Scott Ransom
February 2016