there's no reason why it shouldn't work. the only thing i can think of is that the input type hasn't been set to lattice. In the moses.ini, there should be something like [inputtype] 2 or on the command line moses -inputtype 2
Hieu Hoang Research Associate (until March 2015) ** searching for interesting commercial MT position ** University of Edinburgh http://www.hoang.co.uk/hieu On 7 February 2015 at 20:05, Jorg Tiedemann <[email protected]> wrote: > > I have a problem with lattice decoding and optimizing input-feature > weights. I have edge weights in my lattice input (one per edge) and I > defined one input feature that I'd like to optimize using MERT. However, my > the input feature value is always 0 in the nbest lists even though none of > the input edges has value 1 (or 0). What do I do wrong? > > My initial config file includes: > > [feature] > InputFeature num-features=1 num-input-features=1 real-word-count=0 > ... > # dense weights for feature functions > [weight] > InputFeature0= 1 > > The lattice input is valid and looks like this: > > ((('word',0.8,1),('word',0.6,1), .... > > MERT tuning fails in the end especially because the input feature cannot > be set. > Any help is very much appreciated. > Thanks, > Jörg > > > > _______________________________________________ > 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
