Hi Matt
That seems right. When reading an nbest list, sparse and dense features
are stored differently so you just need to know how many there are,
whereas in hypergraphs all features look like sparse features. This
needs a cleanup ...
cheers - Barry
On 05/03/15 19:33, Matt Post wrote:
> Yes,
HI all, i try to train english arabic system and every thing is ok untill i try
to tuning the system using this command
nohup nice ~/mosesdecoder/scripts/training/mert-moses.pl
~/thesiscorups/tuning.true.en ~/thesiscorups/tuning.true.ar
~/mosesdecoder/bin/moses train/model/moses.ini --mertd
Yes, passing --dense-init worked. Although, it seems to ignore the feature
names: so long as I have enough lines matching the number of dense parameters,
it works, and it always outputs the following:
477/3000 updates, avg loss = 0.36341, BLEU = 0.356527
F0 3.663
F1 0.221152
F2 0
Hi Matt
This was part of the changes to support hypergraph mira, since the
hypergraphs don't have the FEATURES_TXT_BEGIN_0 sections. In fact they
don't differentiate between sparse and dense features.
Does it work correctly when you use the --dense-init paramater?
cheers - Barry
On 05/03/15 1
Okay, the old kbmira works, so this must be part of the 3.0 changes.
It seems that the names of features in the header line (FEATURES_TXT_BEGIN_0)
are ignored entirely. The 2.1 kbmira would output dense feature weights using
names F1..FN, which I would then re-map back to the list in the header.
Hello all,
We are implementing machine translation for one of our application and
after some research we chose Moses to use. Our application is coded in C#
.NET. I am facing problems to compile the Moses decoder using *VS 2010*.
The steps I followed to compile:
- Downloaded *Moses Release 3.0
