Thanks! Yes, telling moses what to do with the scores is my next task. I was checking to make sure they were loaded at all in the first place. Based on your responses it sounds like they are but the specified model type controls the number of scores, not the model file or config option for number of features. For now I'll work under the assumption that all of the scores are being loaded.
Best, Michael On Fri, May 15, 2015 at 3:03 PM, Marcin Junczys-Dowmunt <[email protected]> wrote: > Every type of reordering model has a different number of scores. That's > why you have to provide a meaningful interpretation for them in the feature > function. The compact reordering model is just a stupid container, it will > provide the feature function with all the scores that were present in the > text file, but it does not just add them to the score component vector. > Best, > Marcin > > W dniu 15.05.2015 o 20:57, Matthias Huck pisze: > > Hi, >> >> Hmm, I thought the default number of lexical reordering scores was 8? >> At least for hier-mslr-bidirectional-fe it's 8. >> >> [feature] >> LexicalReordering name=LexicalReordering0 num-features=8 >> type=hier-mslr-bidirectional-fe-allff input-factor=0 output-factor=0 >> path=/model-dir/reordering-table.3.hier-mslr-bidirectional-fe >> >> Cheers, >> Matthias >> >> >> On Fri, 2015-05-15 at 20:46 +0200, Marcin Junczys-Dowmunt wrote: >> >>> Hi, >>> When I look at my code, I would say it's not hardcoded at all. It >>> inspects the first score set and uses that number later on. I guess you >>> would need to provide a reasonable interpretation for that additional >>> scores in the feature function itself. It probable gets that scores, but >>> does not use them. Retrieval should just work unless I am missing >>> something. >>> >>> W dniu 15.05.2015 o 20:35, Michael Denkowski pisze: >>> >>>> Hi all, >>>> >>>> Has anyone successfully used a compact reordering model with extra >>>> score components? I added some features to a reordering table and ran >>>> processLexicalTableMin, which appeared to encode everything (at least >>>> by output file size inspection), but moses still seemed to think it >>>> had only 6 scores. I didn't see a way to specify nscores like in >>>> processPhraseTableMin and a brief attempt to change the hard coded >>>> score numbers in LexicalReorderingTableCompact.cpp didn't work. Has >>>> anyone else looked at this? >>>> >>>> Best, >>>> Michael >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> >> >
_______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
