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
