Hi Hieu,
thanks for your answer. I guess that, in case the search is not completely
deterministic, I will be better off by modifying the -osgx option so that
it will output all the info I need. I was trying to avoid that, but it
seems there will be no other option.
Thanks,
Germán
On
Hi Germán
I think the -osg and -osgx options were implemented for different purposes at
different times, and that one should interpret the 'x' as 'bigger' rather than
'extended'.
However it would certainly make more sense to have the osgx output a superset
of the osg output. The code for
Hi all,
@Kenneth: thanks for the hint. It is pretty unexpected to find that the
search is non-deterministic, and furthermore that such a thing depends on
the LM-tk used.
@Barry: Yes, in fact I have been doing some grep's and I already have what
I wanted (in the end, it took less to code it
@Barry: Yes, in fact I have been doing some grep's and I already have what
I wanted (in the end, it took less to code it than to ask...) Should I
upload the changes to the SVN? What I did is almost a paste between both
osg and osgx within Manager.cpp, but without redundant info.
Thanks s
hi german
I don't think decoding is guaranteed to give the same results in 2
consecutive runs, for the same model and input. This email thread was
discussing this issue
http://thread.gmane.org/gmane.comp.nlp.moses.user/4327/focus=4341
However, I'm not sure how much different 2 runs can be.
Hello list,
I was trying to output a search graph with both the single model scores
and the transition value. While the single model scores are produced by
the option -osgx, the transition value is only present when using the
option -osgx. Since I am not doing this myself, I thought that the
