Try running in a new working directory, your experiment was 4. It may have picked up some bad moses.ini file from a previous experiment.
The training pipeline seems ok to me. I ran with the toy data all the way through to reporting the BLEU score without problems. I've added the my actual config and run command to the example directory https://github.com/moses-smt/mosesdecoder/commit/6e82e11adf58576bbe37ed1203e6b74fd3cd42b9 (I used the same data for tuning and testing, rather than split the training data. Not very correct but that shouldn't make a big difference). On 10 October 2013 18:21, Lane Schwartz <[email protected]> wrote: > One of the people in my lab has been attempting to add a custom > component to EMS. In trying to do this, we have uncovered what appears > to be an inconsistency in experiment.meta. > > Lines 750 (under split-input in [TUNING]) and 758 (under > split-input-devtest in [TUNING]) defines the template as: > > template: $input-splitter -model IN1.$input-extension $input-extension > < IN > OUT > > > However, these lines are in contrast to the templates on line 320 > (under split-indomain-source in [MML]) and line 949 (under split-input > in [EVALUATION]) defined as: > > template: $input-splitter -model IN1.$input-extension < IN > OUT > > > We can't explain the above inconsistency. We are assuming that the > extra "$input-extension" right before "< IN" in lines 750 and 758 > should be removed. Is that correct, or is there some other reason for > the extra $input-extension parameter that we're not seeing? > > Thanks, > Lane > _______________________________________________ > Moses-support mailing list > [email protected] > http://mailman.mit.edu/mailman/listinfo/moses-support > -- Hieu Hoang Research Associate University of Edinburgh http://www.hoang.co.uk/hieu
_______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
