well spotted, there seemed to have been a mistake which I've just fixed
https://github.com/moses-smt/mosesdecoder/commit/b8bc4a9fb64731b593ba56cce1da1af0bbb6138e
But are you sure the problem was in Moses 3? It seemed the bug was
introduced only in Dec 2015
https://github.com/moses-smt/mosesdecoder/commit/65f4f1f92af3d645b1dfc2f161bbcf47bdce1402
whereas Moses 3 was released in Jan 2015
On 28/03/2016 16:58, Mohammad Salameh wrote:
Hi
I have recently started using Moses 3.0 and I noticed the following
difference compared to Moses 2.1
Assuming ttable-limit is set to 20, Moses 3.0 retrieves the 20
translation options of each source segment from the phrase table. But
before calculating the future costs and while it is checking the
translation options spans, Moses 3.0 only considers the top 8 options
for each span.
Moses 2.1 considers the exact 20 options for each source span.
I have tested this using the same configuration files on both systems.
Although it never mentions that it pruned anything, but it seems most
of the translations options are pruned
*Moses 2.1*
Total translation options: 814
Total translation options pruned: 0
translation options spanning from 0 to 0 is 20
...
*
*
*Moses 3.0*
Total translation options: 206
Total translation options pruned: 0
translation options spanning from 0 to 0 is 8
...
Is there a parameter I can set to consider exactly the top 20 without
discarding any?
Regards,
Salameh
_______________________________________________
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
