edit · history · print

PulsarHunter Installation

Installation of PulsarHunter should be simple if the requirements are met, therefore it is important that you view the requirements page. This software has been made available principally for Linux, however if required it could be made to run on Solaris/MacOSX/Windows. If you need help installing on another operating system, contact the project maintainer. This guide assumes you are running Linux

To fetch the latest source and compile it yourself, see PulsarhunterBuildFromSource

1.  Requirements

Pulsarhunter is principally written in Java, as well as basic scripts in bash and some c libraries. You must have the things listed in the first section, and you should get the things listed in the second, or functionality will be reduced.

1.1  PulsarHunter will not install without

  • A Java installation of at least version 1.5
    • You can test the version of your Java install with ‘java -version’.
    • You can get a updated version of Java from http://java.sun.com/

1.2  ‘Optional’ Packages

  • PGPLOT
    • Clearly, if you don’t have pgplot installed, you cannot make plots using it
    • The PGPLOT_DIR/PGPLOT_FONT variables should also be set
    • libpgplot should be on your LD_LIBRARY_PATH

2.  Download

Always use the latest release as earlier versions may have serious bugs (This is new software after all).

2.1  Latest Release (v1.2.5 on 13-Apr-2007)

Unless you are planning to change the code, always use the ‘release’ option (rather than the ‘src’ version).

Download from SourceForge

See Pulsar Hunter Version History for changes since last version.

3.  Installation

Untar the release directory into your chosen install path. tar -xzf pulsarhunter-1.x.x.tar.gz

add the PULSARHUNTER_HOME environment variable

on bash:
export PULSARHUNTER_HOME=“/path/to/root/pulsarhunter/dir”
on csh/tcsh:
setenv PULSARHUNTER_HOME “/path/to/root/pulsarhunter/dir”
You may want to add this to your logon script.
If you don’t have the JAVA_HOME dir pointing to your Java >1.5 installation, add the following line to $PULSARHUNTER_HOME/scripts/includes/env
export JAVA_HOME=“/path/to/base/java/dir”
This should be the same on bash or csh, as it is only used by the scripts (which run bash only).

All the useful scripts are in $PULSARHUNTER_HOME/scripts/, so you might want to add this to your $PATH, else just call them on that path.

If all has gone well, this should be the end of the installation! It is always possible however that something is not working, so first let’s test it: Note that if you didn’t add the scripts to the path, you will have to add the path to the scripts dir to the front.

Launch the pulsarhunter test routine

pulsarhunter —test

This does some basic tests. If there are any errors reported, check the frequent problems below…

4.  Troubleshooting

4.1  UnsuportedClassVersionError

If you get a nasty looking Java error with the following header Exception in thread “main” java.lang.UnsupportedClassVersionError: pulsarhunter/PulsarHunter (Unsuported major.minor version 49.0)

It means that pulsarhunter tried to start with java version less than 1.5.

This is can be fixed by installing Java 1.5 or greater. Install to your chosen path, and add the following to $PULSARHUNTER_HOME/scripts/includes/env
export JAVA_HOME=“/path/to/base/java/dir”

4.2  /../../java: No such file or directory

If you are getting a java: No such file or directory, it means that your JAVA_HOME is pointing to the wrong place. It must point to a sensible directory that has bin/ and lib/ subdirectories (e.g. /usr /usr/java /home/freddy/java etc).

4.3  Native library error

If one of the native libraries failed to load, probably a library file is missing or not valid for your system. This may be a more difficult error to fix. First check the directory $PULSARHUNTER_HOME/lib/ (the this should be the same as the directory listed next to libdir in the output from pulsarhunter). The relevant files are the lib*.so files. The .jar files are java libraries and will not cause native library errors. Use ‘file’ or some other similar program to test the libraries to check they are rel event for your architecture. If not you will need to get the source code and recompile. This is available in the pulsarhunter source code under the src/native directory. There should be relevant build scripts in those directories.

4.4  NoClassDefFoundError

This is not a good error. If you get this just after it says Using Java Excutable: … , you might not have a pulsarhunter.jar file. This could be because you have downloaded a bad file. If this is the case, either get the source code and compile a new pulsarhunter.jar or get in touch.

edit · history · print
Page last modified on July 30, 2008, at 03:46 AM