clarified some text (should fix #5)
Project: http://git-wip-us.apache.org/repos/asf/incubator-joshua-site/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-joshua-site/commit/3677ad28 Tree: http://git-wip-us.apache.org/repos/asf/incubator-joshua-site/tree/3677ad28 Diff: http://git-wip-us.apache.org/repos/asf/incubator-joshua-site/diff/3677ad28 Branch: refs/heads/master Commit: 3677ad286129308b61d55611d4dd1b604a22931a Parents: a0cf2f5 Author: Matt Post <[email protected]> Authored: Mon Jan 11 16:04:36 2016 -0500 Committer: Matt Post <[email protected]> Committed: Mon Jan 11 16:04:36 2016 -0500 ---------------------------------------------------------------------- 6.0/pipeline.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-joshua-site/blob/3677ad28/6.0/pipeline.md ---------------------------------------------------------------------- diff --git a/6.0/pipeline.md b/6.0/pipeline.md index 35d408d..4389435 100644 --- a/6.0/pipeline.md +++ b/6.0/pipeline.md @@ -144,10 +144,10 @@ Running the pipeline requires two main steps: data preparation and invocation. extension to a language identified by the "en" extension, that the training data can be found at `input/train.en` and `input/train.ur`, and so on. -*Don't* run the pipeline directly from `$JOSHUA`. We recommend creating a run directory somewhere - else to contain all of your experiments in some other location. The advantage to this (apart from - not clobbering part of the Joshua install) is that Joshua provides support scripts for visualizing - the results of a series of experiments that only work if you +*Don't* run the pipeline directly from `$JOSHUA`, or, for that matter, in any directory with lots of other files. +This can cause problems because the pipeline creates lots of files under `--rundir` that can clobber existing files. +You should run experiments in a clean directory. +For example, if you have Joshua installed in `$HOME/code/joshua`, manage your runs in a different location, such as `$HOME/expts/joshua`. Assuming no problems arise, this command will run the complete pipeline in about 20 minutes, producing BLEU scores at the end. As it runs, you will see output that looks like the following:
