Re: [Moses-support] osg and osgx
> @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 Germán for doing the changes. Moses is now on github https://github.com/moses-smt/mosesdecoder If you can send me a github id, then I can give you push access. cheers - Barry ___ Moses-support mailing list Moses-support@mit.edu http://mailman.mit.edu/mailman/listinfo/moses-support
Re: [Moses-support] osg and osgx
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 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. Cheers, Germán On Wed, 26 Oct 2011, Barry Haddow wrote: 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 outputting both of these options is in mose/src/Manager.cpp and should be fairly easy to work with, so if you want to make the options more consistent then please go ahead. cheers - Barry On Wednesday 26 Oct 2011 11:34:32 Germán Sanchis Trilles wrote: 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 ___ Moses-support mailing list Moses-support@mit.edu http://mailman.mit.edu/mailman/listinfo/moses-support
Re: [Moses-support] osg and osgx
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 outputting both of these options is in mose/src/Manager.cpp and should be fairly easy to work with, so if you want to make the options more consistent then please go ahead. cheers - Barry On Wednesday 26 Oct 2011 11:34:32 Germán Sanchis Trilles wrote: > 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 > ___ Moses-support mailing list Moses-support@mit.edu http://mailman.mit.edu/mailman/listinfo/moses-support
Re: [Moses-support] osg and osgx
I believe the conclusion of that thread was that using KenLM makes Moses deterministic. On 10/26/11 11:34, Germán Sanchis Trilles wrote: > 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 Wed, 26 Oct 2011, Hieu Hoang wrote: > >> 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. >> >> You might wanna talk to Christian Buck who I think is trying to bash >> the search graph >> output into something more useful >> http://article.gmane.org/gmane.comp.nlp.moses.user/4374/ >> >> On 24/10/2011 23:05, Germán Sanchis Trilles wrote: >> 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 >> best choice >> would be to output both files by rerunning Moses (since they >> seem to be >> exclusive) and then merge both into a single file. However, I >> found a >> problem when doing so, which is that both files do not have the >> same number >> of lines (and hence I assume that the original search-graphs >> did not have >> the same amount of edges. So I would have two questions, I guess: >> >> - Why is there information produced by -osg that is not present >> when >> specifying -osgx? >> - Why are -osg and -osgx exclusive? Is this really the desired >> behaviour? >> - Finally, if the same moses.ini is specified with the same >> models, why are >> the search graphs not identical? Are there random >> initialisations (or >> something similar) that account for this behaviour? >> >> the command lines used when observing these results were pretty >> simple, >> i.e. moses -f -i [-osg|-osgx] >> >> Thanks in advance for your answer, >> >> best regards, >> >> Germán Sanchis-Trilles >> >> >> ___ >> Moses-support mailing list >> Moses-support@mit.edu >> http://mailman.mit.edu/mailman/listinfo/moses-support >> >> >> > > ___ > Moses-support mailing list > Moses-support@mit.edu > http://mailman.mit.edu/mailman/listinfo/moses-support ___ Moses-support mailing list Moses-support@mit.edu http://mailman.mit.edu/mailman/listinfo/moses-support
Re: [Moses-support] osg and osgx
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 Wed, 26 Oct 2011, Hieu Hoang wrote: 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. You might wanna talk to Christian Buck who I think is trying to bash the search graph output into something more useful http://article.gmane.org/gmane.comp.nlp.moses.user/4374/ On 24/10/2011 23:05, Germán Sanchis Trilles wrote: 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 best choice would be to output both files by rerunning Moses (since they seem to be exclusive) and then merge both into a single file. However, I found a problem when doing so, which is that both files do not have the same number of lines (and hence I assume that the original search-graphs did not have the same amount of edges. So I would have two questions, I guess: - Why is there information produced by -osg that is not present when specifying -osgx? - Why are -osg and -osgx exclusive? Is this really the desired behaviour? - Finally, if the same moses.ini is specified with the same models, why are the search graphs not identical? Are there random initialisations (or something similar) that account for this behaviour? the command lines used when observing these results were pretty simple, i.e. moses -f -i [-osg|-osgx] Thanks in advance for your answer, best regards, Germán Sanchis-Trilles ___ Moses-support mailing list Moses-support@mit.edu http://mailman.mit.edu/mailman/listinfo/moses-support ___ Moses-support mailing list Moses-support@mit.edu http://mailman.mit.edu/mailman/listinfo/moses-support
Re: [Moses-support] osg and osgx
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. You might wanna talk to Christian Buck who I think is trying to bash the search graph output into something more useful http://article.gmane.org/gmane.comp.nlp.moses.user/4374/ On 24/10/2011 23:05, Germán Sanchis Trilles wrote: 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 best choice would be to output both files by rerunning Moses (since they seem to be exclusive) and then merge both into a single file. However, I found a problem when doing so, which is that both files do not have the same number of lines (and hence I assume that the original search-graphs did not have the same amount of edges. So I would have two questions, I guess: - Why is there information produced by -osg that is not present when specifying -osgx? - Why are -osg and -osgx exclusive? Is this really the desired behaviour? - Finally, if the same moses.ini is specified with the same models, why are the search graphs not identical? Are there random initialisations (or something similar) that account for this behaviour? the command lines used when observing these results were pretty simple, i.e. moses -f -i [-osg|-osgx] Thanks in advance for your answer, best regards, Germán Sanchis-Trilles ___ Moses-support mailing list Moses-support@mit.edu http://mailman.mit.edu/mailman/listinfo/moses-support ___ Moses-support mailing list Moses-support@mit.edu http://mailman.mit.edu/mailman/listinfo/moses-support
[Moses-support] osg and osgx
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 best choice would be to output both files by rerunning Moses (since they seem to be exclusive) and then merge both into a single file. However, I found a problem when doing so, which is that both files do not have the same number of lines (and hence I assume that the original search-graphs did not have the same amount of edges. So I would have two questions, I guess: - Why is there information produced by -osg that is not present when specifying -osgx? - Why are -osg and -osgx exclusive? Is this really the desired behaviour? - Finally, if the same moses.ini is specified with the same models, why are the search graphs not identical? Are there random initialisations (or something similar) that account for this behaviour? the command lines used when observing these results were pretty simple, i.e. moses -f -i [-osg|-osgx] Thanks in advance for your answer, best regards, Germán Sanchis-Trilles___ Moses-support mailing list Moses-support@mit.edu http://mailman.mit.edu/mailman/listinfo/moses-support
