is it possible you can make your moses.ini file available for us to see?
do you know if the same problem occurs if you use the command line moses,
rather than mosesserver?
Hieu Hoang
Researcher
New York University, Abu Dhabi
http://www.hoang.co.uk/hieu
On 21 July 2015 at 18:07, Barry Haddow
thanks for your replies.
I have done the full EMS with no errors. BLEU seems fine.
the EMS was dnoe with the WMT12 parallel data.
From here what should I do for real assessment.
I have real texts (human translation)
should they be used for training or for tuning ?
second question :
is there
here is what I got
make sense ?
MT evaluation scorer began on 2015 Jul 20 at 23:27:39
command line: /home/moses/mosesdecoder/scripts/generic/mteval-v13a.pl -c
-c -s /home/moses/working/data/dev/newstest2011-src.fr.sgm -r
/home/moses/working/data/dev/newstest2011-ref.en.sgm -t
Hi Barry,
Thanks for the quick response.
I added the switch -threads 18 to the command to raise moses server. The
slowness issue persists but in a different form. Most requests return right
away, even under heavy load, but some requests (about 5%) take far longer -
about 15-20 seconds.
Perhaps
Hi all,
I am running experiments on Bilingual Neural LM.
For extract_training.py, I set
--prune-target-vocab 1 --prune-source-vocab 1 --target-context 5
--source-context 4
For train_nplm.py, I set
--ngram-size 14 --output-embedding 512 --input-embedding 192 --hidden 512
--e 5
I use 2
Hi Oren
Does your host have 18 threads available? It could also be that xmlrpc-c
is limiting the number of connections - this can now be configured:
https://github.com/moses-smt/mosesdecoder/commit/b3baade7f022edbcea2969679a40616683f63523
Slowdowns in Moses are often caused by disk access
Hello Jian,
NPLM reports the log-likelihood of the whole training set, and the
number is plausible.
assuming you have a minibatch size of 1000, your training set perplexity
is exp(1.38122e+08/52853/1000)=13.64
you probably want to measure perplexity on a held-out development set
though,
On 21/07/15 14:51, Oren wrote:
I am using the in-memory mode, using about 50GB of RAM. (No swap
issues as far as I can tell.) Could that cause issues?
Yes, swapping would definitely cause issues - was that your question?
I looked at the commit you linked to, but it doesn't seem to be
