if no-one is answering questions on mert-moses-multi.pl, we should move it to /contrib to avoid confusion

On 19/12/2011 01:49, Daniel Schaut wrote:

Hi all,

I've gotthreequickquestionsregarding the behavior ofmert-moses-multi.pl, because my system runs out of memory after some iterations.Both, my phrase/reordering tablesare binarized.That's my call

./mert-moses-multi.pl

/home/user/smt/phrase/tuning/devset-1.tok.lw.en

/home/user/smt/phrase/tuning/devset-1.tok.lw.de

/home/user/smt/decoder/dist/cb5213a/bin/moses

/home/user/smt/phrase/model/moses.ini

--working-dir /home/user/smt/phrase/tuning/mert

--mertdir=/home/user/smt/decoder/mert

--rootdir /home/user/smt/scripts/cb5213a

--threads=2

--decoder-flags "-v 0 -threads 2"

And, that's themessagemert-moses-multi.plgivesmewhen running out of memory:

Executing: gzip--frun3.best100.out

Scoring the nbestlist.

exec: /home/user/smt/decoder/mert/extractor --scconfig case:true --scfile run3.scores.dat.BLEU --ffile run3.features.dat.BLEU --sctype BLEU -r /home/user/smt/phrase/tuning/rainbow/devset-1.tok.lw.de -n run3.best100.out.gz

Executing: /home/user/smt/decoder/mert/extractor --scconfig case:true --scfile run3.scores.dat.BLEU --ffile run3.features.dat.BLEU --sctype BLEU -r /home/user/smt/phrase/tuning/rainbow/devset-1.tok.lw.de -n run3.best100.out.gz > extract.out.BLEU 2> extract.err.BLEU

Executing: \cp -f init.opt run3.init.opt

exec: /home/user/smt/decoder/mert/mert -d 22 --scconfig case:true --sctype MERGE --sctype MERGE --sctype MERGE --ffile run1.features.dat,run2.features.dat,run3.features.dat --scfile run1.scores.dat,run2.scores.dat,run3.scores.dat --ifile run3.init.opt -n 20

Executing: /home/user/smt/decoder/mert/mert -d 22 --scconfig case:true --sctype MERGE --sctype MERGE --sctype MERGE --ffile run1.features.dat,run2.features.dat,run3.features.dat --scfile run1.scores.dat,run2.scores.dat,run3.scores.dat --ifile run3.init.opt -n 20 > mert.out 2> mert.log

Exit code: 134

ERROR: Failed to run '/home/user/smt/decoder/mert/mert -d 22 --scconfig case:true --sctype MERGE --sctype MERGE --sctype MERGE --ffile run1.features.dat,run2.features.dat,run3.features.dat --scfile run1.scores.dat,run2.scores.dat,run3.scores.dat --ifile run3.init.opt -n 20'. at ./mert-moses-multi.pl line 1374.

When I run thea similar commandusing mert-moses.plon the same devset,mert-moses.plis able to complete the tuning process. That's the command

./mert-moses.pl

/home/user/smt/phrase/tuning/devset-1.tok.lw.en

/home/user/smt/phrase/tuning/devset-1.tok.lw.de

/home/user/smt/decoder/dist/cb5213a/bin/moses

/home/user/smt/phrase/model/moses.ini

--working-dir /home/user/smt/phrase/tuning/mert

--mertdir=/home/user/smt/decoder/mert

--rootdir /home/user/smt/scripts/cb5213a

--decoder-flags "-v 0 -threads 2"

So my questions arenow:

What am I doing wrong?

Is thisbehaviorof mert-moses-multi.pl normal?

What can I do topreventmert-moses-multi.plfrom stoppingthe tuning process?

If needed, I can provide further information.Help is very much appreciated.

Regards,

Daniel



_______________________________________________
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

Reply via email to