masktracker V.2.7.1beta1 installation instructions

FOR ESO INTERNAL USE ONLY!

1  masktracker V.2.7.1beta1

The latest version of MT is V.2.7.1beta1. Before trying to install and run it, you should read the release notes.

2  masktracker V.2.7.1beta1 System Requirements

MT V.2.7.1beta1 is written in Java and it will run on all major platforms including Unix, Win32 and MacOS.
Details of memory and CPU usage are not available at this time, but we do expect the system to be pretty resource-intensive.

3  Installing and running masktracker V.2.7.1beta1

To install OT V.2.7.1beta1 you will need to retrieve the distribution kits for your architecture, unpack and install them, and start the p2pp executable.
Note
In order to retrieve the distribution kits, you may need to configure your Web browser so that it knows how to deal with the files we distribute -- either gzipped tar files (.tar.gz filename extension; Unix, Linux) or zip files (.zip extension; Windows).

If you click on one of the links below, your browser should display a file selection panel; if you end up instead with a page full of strange characters, you definitely need to configure your browser.

Alternatively, try clicking on the link while holding the Shift key down.

3.1  Solaris, HP-UX and Linux

  1. Change directory to where you want to install OT V.2.7.1beta1 -- in the following, we'll call this directory the installation directory.

  2. Retrieve the Unix distribution kit into the installation directory:

  3. You should retrieve the Java Runtime Environment for your architecture into the installation directory:

  4. Retrieve into the installation directory all the needed Instrument Packages.
    See the USG Instrument Packages Web page for more information.

  5. Run the following sequence of commands:
        gunzip -c ot-2.7.1beta1-<your-os>.tar.gz | tar xvf -
        cd ot-2.7.1beta1-<your-os>
        make     This completes the installation process.
To run the executable, just add <installation-directory>/ot-2.7.1beta1/bin to your $PATH environment variable, then give the
    ot
command, possibly after issuing rehash.

Beware of possible conflicts with OT V.1.x installations: if that is the case, you can use the jot alias instead of ot.

3.2  Win32

TBD

3.3  MacOS

TBD

$Revision: 1.3 $,