the start and end points are still start and end. But the width no longer means the number of words. I think Chris Dyer added the floyd-walshall algorithm to find the shortest path between 2 points, but that doesn't mean the number of words either.
The size of the phrase in the InputPath is the number of words On 30/06/2015 20:41, Marcin Junczys-Dowmunt wrote: > Thanks, looks good. Does cur_hypo.GetCurrSourceWordsRange() still make > sense in the context of lattices? > > On 30.06.2015 18:28, Hieu Hoang wrote: >> cur_hypo.GetTranslationOption().GetInputPath() >> >> i hope >> >> Hieu Hoang >> Researcher >> New York University, Abu Dhabi >> http://www.hoang.co.uk/hieu >> >> On 30 June 2015 at 19:30, Marcin Junczys-Dowmunt <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi, >> is there a way to find the current source phrase (input path) for >> lattices in the following feature function hook? >> >> FFState* EvaluateWhenApplied( >> const Hypothesis& cur_hypo, >> const FFState* prev_state, >> ScoreComponentCollection* accumulator) >> >> Specifically I want to use the OSM with lattice input, but it is >> only >> written for sentence input. If I am not very wrong it should not >> easy to >> modify if only I can get the plain source word range from a lattice. >> Thanks, >> Marcin >> _______________________________________________ >> Moses-support mailing list >> [email protected] <mailto:[email protected]> >> http://mailman.mit.edu/mailman/listinfo/moses-support >> >> > > -- Hieu Hoang Researcher New York University, Abu Dhabi http://www.hoang.co.uk/hieu _______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
