Developing Applications with Terrier
Terrier provides APIs for indexing documents, and querying the generated indices. If you are developing applications using Terrier or extending it for your own research, then you may find the following information useful.
Terrier has a very flexible and modular architecture, with many classes, some with various alternatives. It is very easy to change many parts of the indexing and retrieval process. Essential to any in-depth extension of Terrier is to examine the very many properties that can be configured in Terrier. For instance, if you write a new Matching class, you can use this in a TREC-like setting by setting the property trec.matching, while if you write a new document weighting model you should set the property trec.model to use it, or add it in etc/trec.models. For more information about extending the retrieval functionalities of Terrier, see Extending Retrieval, and Extending Indexing for more information about the indexing process Terrier uses.
All File IO in Terrier (excluding the Desktop application and Terrier configuration) is performed using the Files class. This affords various opportunities for allowing Terrier to run in various environments. In Terrier 2.1, a FileSystem abstraction layer was integrated into the Files class, such that other FileSystem implementations could be plugged in. By default, Terrier ships with two implementation, namely LocalFileSystem for reading the local file system using the Java API, and HTTPFileSystem for reading files accessible by HTTP or HTTPS protocols. A filename is searched for a prefixing scheme (eg "file://"), similar to a URI or URL. If a scheme is detected, then Terrier will search through its known file system implementations for a file system supporting the found scheme. file:// is the default scheme if no scheme can be found in the filename; if the filename starts http://, then the file will be fetched by HTTP.
The Files layer can also transform paths to filenames on the fly. For example, if a certain HTTP namespace is accessible as a local file system, the Files layer can be informed using Files.addPathTransformation().
Additional implementations can implement methods of the FileSystem interface that they support, and register themselves by calling the Files.addFileSystemCapability() method. The FileSystem denotes the operations it supports on a file or path by returning the bit-wise OR of the constants named in Files.FSCapability.
The main Terrier distribution comes pre-compiled as Java, and can be run on any Java 1.5 JDK. You should have no need to compile Terrier unless:
Terrier is distributed with two scripts for compiling Terrier for Unix-like platforms:
NB:Currently we suggest that you use the Makefile instead of the script bin/compile.(sh,bat), and that you always execute make clean compile to compile Terrier. This ensures that the TerrierParser is always built correctly.
There are files missing from the Terrier source code? This is correct as in the source for some classes aren't included. This is because these files are generated automatically by Antlr during the compiling process. The build process invokes the Antlr "compiler compiler", which generates the missing Java source files from the queryparser specification (the .g files in src/uk/ac/gla/terrier/querying/parser/).
If you want to compile your application code that uses functionalities of Terrier, then it is preferable to make the compilation having the file lib/terrier-2.X.jar in your classpath, instead of the folder src/.
How do I run the test harness? On the command line, run make test. There are many tests for various indexing and retrieval functionalities. In all cases, Mean Average Precision (MAP) should be 1.0000. If this it not the case, check test.log to see what went wrong. The test harness will be extended as Terrier matures.[Previous: List of Terrier properties] [Contents] [Next: Extending Indexing]
Copyright © 2015 University of Glasgow | All Rights Reserved