to my experience, below 400 I started to lose some BLEU point slightly.
Another thing to tune is the score-setting when building table.
score-settings = "--GoodTuring --MinScore 2:0.001"
standard value is 0.0001
I did not notice any BLEU score decrease with 0.001
But might be not relevant with MMAPTS
Le 08/10/2015 21:24, Michael Denkowski a écrit :
Hi Vincent,
That definitely helps. I reran everything comparing the original
2000/2000 to your suggestion of 400/400. There isn't much difference
for a single multi-threaded instance, but there's about a 30% speedup
when using all single-threaded instances:
pop limit & stack
procs/threads 2000 400
1x16 5.46 5.68
2x8 7.58 8.70
4x4 9.71 11.24
8x2 12.50 15.87
16x1 14.08 18.52
There wasn't any degradation to BLEU/TER/Meteor but this is just one
data point and a fairly simple system. I would be curious to see how
things work out in other users' systems.
Best,
Michael
On Thu, Oct 8, 2015 at 2:34 PM, Vincent Nguyen <[email protected]
<mailto:[email protected]>> wrote:
out of curiosity, what gain do you get with 400 for both stack and
cube pruning ?
Le 08/10/2015 20:26, Michael Denkowski a écrit :
Hi Vincent,
I'm using cube pruning with the following options for all data
points:
[search-algorithm]
1
[cube-pruning-deterministic-search]
true
[cube-pruning-pop-limit]
2000
[stack]
2000
Best,
Michael
_______________________________________________
Moses-support mailing list
[email protected]
http://mailman.mit.edu/mailman/listinfo/moses-support
