Thanks everyone, it's working now. zınɹ ʞɔıu
On Fri, Jan 8, 2016 at 1:17 PM, Philipp Koehn <[email protected]> wrote: > Hi, > > the command > experiment.perl -config config.1 -continue 1 > actually is not defined. > > If you want to continue an experiment, you have to run > experiment.perl -continue 1 > > If you just want to add an additional test set, you have to > edit steps/1/config.1 before you re-run the command. > > Note that editing steps/1/config.1 is not recommended use > of experiment.perl (although I do it all the time), since it breaks > assumptions that the scheduler has about which steps need > to be run. If you aware of the implications, proceed with > caution. > > In you case you also need to remove the steps/1/REPORTING_report.1* > step, so it is re-run. > > -phi > > On Fri, Jan 8, 2016 at 12:47 PM, Matthias Huck <[email protected]> wrote: > >> Hi Nick, >> >> What you're attempting to do should generally be no problem. There's >> most likely some issue with your EMS configuration file. Doesn't it tell >> you something like: >> >> BUGGY CONFIG LINE (474): wrapping-frame = $tokenized-input >> >> I get this when I put two spaces between "wrapping-frame" and "=". >> >> Also, is /path/to/test4.tok.$output-extension some pre-translated >> hypothesis? If it's the reference, you might have to specify it as >> "tokenized-reference" rather than as "tokenized-output". >> >> Cheers, >> Matthias >> >> >> On Fri, 2016-01-08 at 12:16 -0500, Nicholas Ruiz wrote: >> > Thanks, Tomasz. Unfortunately modifying the config file in the steps >> > directory didn't work for me. My block looks something like this: >> > >> > [EVALUATION:test4] >> > >> > tokenized-input = /path/to/test4.tok.$input-extension >> > tokenized-output = /path/to/test4.tok.$output-extension >> > wrapping-frame = $tokenized-input >> > >> > zınɹ ʞɔıu >> > >> > On Fri, Jan 8, 2016 at 12:11 PM, Tomasz Dwojak <[email protected]> >> wrote: >> > >> > > Hi Nick, >> > > >> > > there is a way to do that. >> > > >> > > In your working directory is a "steps" directory, where the EMS writes >> > > outputs, etc... There is also the copy of the config file (e.g. >> > > steps/1/config.1). You have to edit this file and then run EMS once >> again. >> > > >> > > Shortly: >> > > 1. Edit steps/1/config.1 >> > > 2. run experiment.perl -continue 1 >> > > >> > > Best, >> > > Tomasz >> > > >> > > On 08.01.2016 17:45, Nicholas Ruiz wrote: >> > > >> > > Hi all, >> > > >> > > I have a few different experiments that have finished training. Let's >> say >> > > I have versions 0 1 2 3. I'd like to translate/evaluate an additional >> test >> > > set. I added another [EVALUATION:...] block to specify the paths of >> the >> > > eval data and now I'd like to run it with >> > > >> > > experiment.perl -config config.1 -continue 1 >> > > >> > > However, the steps for evaluating the new test set aren't in the list >> of >> > > steps. What's the best way to run this test without having to create >> > > another experiment folder? >> > > >> > > Thanks, >> > > Nick >> > > >> > > zınɹ ʞɔıu >> > > >> > > >> > > _______________________________________________ >> > > Moses-support mailing [email protected]:// >> mailman.mit.edu/mailman/listinfo/moses-support >> > > >> > > >> > > >> > _______________________________________________ >> > Moses-support mailing list >> > [email protected] >> > http://mailman.mit.edu/mailman/listinfo/moses-support >> >> >> >> -- >> The University of Edinburgh is a charitable body, registered in >> Scotland, with registration number SC005336. >> >> _______________________________________________ >> Moses-support mailing list >> [email protected] >> http://mailman.mit.edu/mailman/listinfo/moses-support >> > >
_______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
