Skip to content

SystemInstallation

Jump to bottom
Will de Beaumont edited this page May 21, 2019 · 8 revisions

General TRIPS System Installation Notes

See also notes for some specific TRIPS systems:

See also instructions for installing TRIPS using in a virtual machine using the following command:

git clone http://github.com/mrmechko/vagrant-trips && cd vagrant-trips && vagrant up

TRIPS STEP System Vagrant Machine

Download Source

We have many different TRIPS systems that include the parser with different settings and other modules. Some of them are:

  • step
  • cogent
  • drum
  • bob
  • cabot
  • musica
  • cwms

Herein $TRIPS_SYSTEM is used to refer to the specific system you are installing, and $TRIPS_BASE is the directory you are installing it in.

github

git clone https://github.com/wdebeaum/$TRIPS_SYSTEM.git

CVS

You can only do this if you have an account on our CVS server. $USER is the username for that account.

cvs -d $USER@trips.cs.rochester.edu:/p/cvs/trips checkout -P $TRIPS_SYSTEM

Install Prerequisites

Which prerequisites you need depends on the specific system you want to install. But in general you will at least need a Lisp implementation (we tend to use SBCL 1.2+) as well as Java (1.7+), Perl, and some other relatively standard development tools. If you're on a Mac, I think XCode gets you most of this.

If you use SBCL, you need to make sure it has multithreading support (the pre-built binaries don't). On the Mac, an easy way to do this is through ​MacPorts, using this command:

sudo port install sbcl +threads

TRIPS systems also commonly require WordNet 3.0, which you can download from:

If you got TRIPS from CVS, get the first one; if you got TRIPS from github, get both. You should unpack these in /usr/local/share/wordnet/ (creating the directory if necessary). They both contain a WordNet-3.0/ directory, so after unpacking you should have the directory /usr/local/share/wordnet/WordNet-3.0/.

The TextTagger README's Installation section has information on installing most other possible prerequisites. You almost certainly do not need all of these; each TRIPS system uses only a subset.

Build

cd $TRIPS_BASE/src/
./configure [options]
make
make install

You can use configure options to let the TRIPS build system know where specific prerequisites are installed on your system, but if they are in the standard locations usually configure will find them on its own. In particular, SBCL's executable is often not called lisp but rather sbcl, so you may have to run ./configure --with-lisp=sbcl.

You can list all configure options by running ./configure --help=recursive in $TRIPS_BASE/src/.

Note that each time you run configure for real (i.e. not with --help) it will overwrite the previous configuration, so if you want to keep the options you passed it before, you need to pass them in again. Also, if you ran make with a previous configuration, you may want to run make clean before your next make, to avoid mixing different configurations.

Run

To run the system:

$TRIPS_BASE/bin/trips-$TRIPS_SYSTEM [options]

This will create a new timestamped log directory under the current directory each time you run it, so you may wish to create a logs directory and always run TRIPS from there, e.g.:

cd $TRIPS_BASE/
mkdir logs
cd logs
../bin/trips-$TRIPS_SYSTEM [options]
# the above creates logs in a directory like $TRIPS_BASE/logs/20181011T1642/
# ...3 minutes later:
../bin/trips-$TRIPS_SYSTEM [options]
# creates a directory like $TRIPS_BASE/logs/20181011T1645/

To run with a Lisp REPL, you must run the Lisp and non-Lisp parts of the system separately. To run the non-lisp parts, use the -nolisp option:

$TRIPS_BASE/bin/trips-$TRIPS_SYSTEM -nolisp

To run the Lisp parts, load the relevant test.lisp into Lisp and call (run). With SBCL, you can do this from the command line like this:

cd $TRIPS_BASE/src/Systems/$TRIPS_SYSTEM/
sbcl --load test --eval '(run)'

Depending on the system, you may also need to increase Lisp's heap size; insert the --dynamic-space-size=4096 option after sbcl to give it a 4GB heap.

Clone this wiki locally