Indeed. Thank you very much, dear sir. On 12.02.2016 23:47, Hieu Hoang wrote: > i think this happens just before expansion, once all the translation > options have been collected > > On 12/02/16 22:36, Marcin Junczys-Dowmunt wrote: >> But this happens during hypothesis expansion? I think I need it before. >> >> I have a classifier for which I want to restrict softmaxing over all >> available target words for the complete sentence instead over all >> known vocabulary items. >> >> I will take a look at your second suggestion. >> >> On 12.02.2016 23:32, Hieu Hoang wrote: >>> sounds useful.There's >>> FeatureFunction::EvaluateTranslationOptionListWithSourceContext() >>> which is called for for every subphrase. It passes the feature >>> function a list of translation option for that subphrase. The method >>> is called in >>> TranslationOptionCollection::EvaluateTranslationOptionListWithSourceContext >>> >>> >>> Or you add yet another Evaluate() method that passes the feature >>> function the InputPathList, which really has every translation >>> options in 1 go >>> >>> Hieu Hoang >>> http://www.hoang.co.uk/hieu >>> >>> On 12 February 2016 at 22:19, Marcin Junczys-Dowmunt >>> <[email protected] <mailto:[email protected]>> wrote: >>> >>> Hi everybody, >>> Is there a nice way to access the complete set of translation >>> options >>> for a sentence from within a feature function? I just need the >>> bag of >>> possible words before any processing. Let's say from within >>> "EmptyHypothesisState", there is InputType, but I cannot really >>> find any >>> hook to get that easily. >>> >>> Thanks, >>> Marcin >>> _______________________________________________ >>> Moses-support mailing list >>> [email protected] <mailto:[email protected]> >>> http://mailman.mit.edu/mailman/listinfo/moses-support >>> >>> >> >> >
_______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
