Hi Tomasz
The error message about missing the ini file is a consequence of the
tuning crash, so just ignore this.
To find out why Moses is failing, run it again in the console like this:
/home/moses/src/mosesdecoder/bin/moses -threads 16 -v 0 -config
Hi,
I have a problem with tuning crashed. It seems that moses.ini is missing in
temporary folder but I have no idea why. I attached link to my config file.
Please help.
Regards
Thomas
moses@smtserver:~/working/experiments/NGRAM5/steps/2$ more
TUNING_tune.2.STDERR
Using
Hi,
I tried to train a phrase-based baseline system from German to English.
But during the tuning step, mert crashed in the first run. I tracked it to
this error,
Check abs(leftmost-first-gradient.rbegin()-first) 0.0001 failed in mert
/Optimizer.cpp:170
I've already checked similar posts on
Hi Wei
This error (as far as I recall) tends to mean that one of your features
is flat (ie uninformative). I don't see that this is the case for your
features. The only thing I could think of is that your tuning set is
quite small (500 sentences) but that doesn't usually cause a problem.
My
Thanks, Barry. I will try mira.
Anyway, I share my model file here
https://www.dropbox.com/s/jko7aitnk9mqa8a/model.tar.gz
Best,
Wei
On Sat, May 24, 2014 at 10:13 AM, Barry Haddow
bhad...@staffmail.ed.ac.ukwrote:
Hi Wei
This error (as far as I recall) tends to mean that one of your
Thanks, Barry,
Both batches-mira and pro tuning don't crash. But the result of
batch-miratuning is very unstable due to the size of dev set.
Best,
Wei
On Sat, May 24, 2014 at 11:34 AM, Wei Qiu w...@qiu.es wrote:
Thanks, Barry. I will try mira.
Anyway, I share my model file here
Hi Jayendra
The fact that your bleu precisions are all zero (run1.scores.dat)
suggests that something went badly wrong
with the translation, or your reference set is incorrect. What do the
translations (in run1.out) look like?
The zeros in run1.features.dat are normal, but the very low lm
Sorry for bumping the thread again.
here's what I found after running the command by hand as suggested.
run1.init.opt:
* 0.30 0.30 0.30 0.30 0.30 0.30 0.30 0.50
-1.00 0.20 0.20 0.20 0.20 0.20
0 0 0 0 0 0 0 0 0 0 0 0 0 0
1 1 1 1 1 1 1 1
Hi Phi,
Thanks for the reply, I made a hand run of the command as you have
suggested and was able to repeat the crash. I have checked run1.init.opt
file, it seems to be fine
run1.init.opt:
* 0.30 0.30 0.30 0.30 0.30 0.30 0.30 0.50
-1.00 0.20 0.20
