Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
user:zeman:addicter [2010/02/22 13:26] zeman How to install and configure Apache. |
user:zeman:addicter [2010/02/22 14:39] zeman joshua -> system |
||
---|---|---|---|
Line 22: | Line 22: | ||
* Under Windows, you will also want to set < | * Under Windows, you will also want to set < | ||
* Restart the server. On the main Windows panel, there is (typically in the lower right corner) a set of icons, including a new one for Apache. Right-click on it, select Open Apache Monitor, then Restart. | * Restart the server. On the main Windows panel, there is (typically in the lower right corner) a set of icons, including a new one for Apache. Right-click on it, select Open Apache Monitor, then Restart. | ||
+ | |||
+ | ==== How to install Addicter ==== | ||
+ | |||
+ | We use '' | ||
+ | |||
+ | * Check out the current version of Addicter from the SVN repository. In Linux, the following command will do that: < | ||
+ | * All you need at this moment is in the folder '' | ||
===== Alignment viewer ===== | ===== Alignment viewer ===== | ||
Line 35: | Line 42: | ||
* '' | * '' | ||
* '' | * '' | ||
+ | |||
+ | The '' | ||
The indexer splits the output index into multiple files in order to reduce size of any individual file. All index files must be stored in the same folder as the viewing CGI scripts. | The indexer splits the output index into multiple files in order to reduce size of any individual file. All index files must be stored in the same folder as the viewing CGI scripts. | ||
+ | |||
+ | ==== How to prepare a corpus for viewing ==== | ||
+ | |||
+ | We assume that your corpus is already sentence-aligned and tokenized. I.e., source and target files have the same number of lines (sentences, segments), and tokens (words, punctuation) on each line are space-separated. If you are using Addicter to perform analysis of errors made by a machine translation system, you probably already have such a corpus. You may also want to use a lowercased version of your corpus. Unless stated otherwise, all files are supposed to be plain text files in the UTF-8 encoding. | ||
+ | |||
+ | You will also need some alignment files that define bi-directional word alignments. If you have trained a statistical MT system such as Moses, chances are that you already have such files for the training data. They result from the first three steps of the Moses training pipeline, namely from two runs of Giza++ and an alignment symmetrization algorithm. In order to get alignments for test data, too, you can do the following: | ||
+ | |||
+ | * Join the source training file with the source test file. Similarly, join the target sides of the two data sets. | ||
+ | * Re-run Giza++ over the joint corpus. | ||
+ | * The resulting alignment file has the same number of lines as the source and the target side of the corpus. By cutting off the last N lines, you easily separate the training and test alignments from each other. | ||
+ | * Alternatively, | ||
+ | |||
+ | Once all the input files are ready, the indexer is invoked as follows: | ||
+ | |||
+ | < | ||
+ | -trs train.en -trt train.hi -tra train.ali \ | ||
+ | -s test.en -r test.hi -h test.system.hi -ra test.ali -ha test.system.ali \ | ||
+ | -o $CGI</ | ||
+ | |||
+ | The indexer will copy the input files and output all index files into the '' | ||
+ | |||
+ | ==== How to use the viewer ==== | ||
+ | |||
+ | Now if your web server is running and configured properly and your index and data files have been prepared in the correct place, launch your web browser and point it to http:// |