Nadi, I don't know what would be causing the segfault, but others on the mailing list might have an idea.
Does the segfault occur with using the "-translation-details" switch without "-constraint"? Lane On Fri, Apr 15, 2011 at 2:35 PM, Nadi Tomeh <nadi.to...@limsi.fr> wrote: > Hi, > Thank you for your response. > I tried to run moses (latest version in the trunk) with the "-constraint" > switch. Apart from Bill Lang's remark it works fine. > Once a translation that matches the given reference is found, I am > interested in outputting the set of phrase pairs used to produce it. > I tried to use the "-translation-details" switch, but it results in a > segmentation fault after translating the first sentence! > Do you have any idea about the source of this problem? How can I get the > output I am interested in? > > Here's the log up to the segmentation fault: > > Defined parameters (per moses.ini or switch): > config: moses.ini > constraint: test.en > distortion-file: 0-0 wbe-msd-bidirectional-fe-allff 6 > /vol/raid220/nadi/sigpt/wmt11/mgiza/moses-standard/eval-final/filtered/reordering-table.wbe-msd-bidirectional-fe > > distortion-limit: 6 > input-factors: 0 > input-file: test.fr > mapping: 0 T 0 > translation-details: translation-details > ttable-file: 0 0 0 5 > /vol/raid220/nadi/sigpt/wmt11/mgiza/moses-standard/eval-final/filtered/phrase-table.0-0.1.1 > > ttable-limit: 0 > weight-d: 0.0774037 0.0622227 -0.0044269 0.0603762 0.0713655 > 0.0164707 0.0622227 > weight-t: 0.0411563 0.0979125 0.0414816 0.063458 0.0850244 > weight-w: -0.212775 > Loading lexical distortion models...have 1 models > Creating lexical reordering... > weights: 0.062 -0.004 0.060 0.071 0.016 0.062 > Loading table into memory...done. > Finished loading LanguageModels : [10.000] seconds > Start loading PhraseTable > /vol/raid220/nadi/sigpt/wmt11/mgiza/moses-standard/eval-final/filtered/phrase-table.0-0.1.1 > : [10.000] seconds > filePath: > /vol/raid220/nadi/sigpt/wmt11/mgiza/moses-standard/eval-final/filtered/phrase-table.0-0.1.1 > Finished loading phrase tables : [10.000] seconds > Start loading phrase table from > /vol/raid220/nadi/sigpt/wmt11/mgiza/moses-standard/eval-final/filtered/phrase-table.0-0.1.1 > : [10.000] seconds > Finished loading phrase tables : [26.000] seconds > Created input-output object : [34.000] seconds > Translating: le président américain Barack Obama s' envolera pour Oslo en > Norvège , pour y passer 26 heures et être le quatrième président américain > de l' histoire à recevoir le prix Nobel de la paix . > > Search constraint to output: the American president Barack Obama will fly > into Oslo , Norway for 26 hours to receive the Nobel Peace Prize , the > fourth American president in history to do so . > Collecting options took 0.820 seconds > Search took 0.880 seconds > > Thank you in advance, > Nadi > > > On 12/02/2010 02:22 AM, Bill_Lang(Gmail) wrote: > > Hi Lane, > Such constraint decoding function is interesting. Before several > days, I have tried this "-constraint" setting of moses. It can do force > decoding mostly with one bug. > For example, if target sentence is "ABCDE". I have got one forced > translation by "ABCD". I guess it is caused by no length limit of translated > sentence by the last hypothesis. > Anyway, such functionality is very useful. Thank you Lane. > > Best regards, > Lang Jun > > 2010/12/2 Lane Schwartz <dowob...@gmail.com> > >> Hi all, >>> >>> I'm trying to figure out if Moses, in its current state, allows for >>> forced decoding? >>> >>> I've understood that Lane Schwartz implemented it for his multi-source >>> translation (Schwartz, 2008) >>> and it is used by Auli et al. (2009). Is this implementation merged back >>> to the trunk? >>> If not in which branch could it be found? >>> >>> Any guidance would be highly appreciated. >>> >>> Cheers, >>> Nadi >>> >> Nadi, >> >> The code that I used for my multi-source translation paper (Schwartz, >> 2008) is in trunk (since r1857, as per the footnote in the paper). To use, >> specify a file of existing translations using the -constraint flag. This >> file needs to have one sentence per line, and should be the same number of >> lines as your input. >> >> The constraint decoding implemented for -constraint is pretty restrictive. >> If it can't find an path through the translation lattice that exactly >> produces the constraining sentence, it will fail to produce any translation >> for that sentence. In other words, if you specify "the man walks there" as >> your constraint, and the best the decoder can find is "the man walk there", >> translation will fail for that sentence. >> >> I did some work at the Prague MT Marathon to try and fix this issue, but >> that code is not in trunk, and I haven't touched it in a long time. Most of >> that code should be in the lane_mtm3 branch, but some also may be in the >> mt3_constraint branch (Hieu helped by implementing a WER component), >> >> Let me know if you plan to do any coding to extend constraint decoding. >> >> Cheers, >> Lane >> >> >> _______________________________________________ >> Moses-support mailing list >> Moses-support@mit.edu >> http://mailman.mit.edu/mailman/listinfo/moses-support >> >> > > > -- > Nadi Tomeh > Univ. Paris XI, LIMSI-CNRS > LIMSI Bât 508, Bureau 118 > BP 133 F-91403 ORSAY CEDEX > Tél : +33/0 1 69 85 80 68nadi.to...@limsi.fr > > -- When a place gets crowded enough to require ID's, social collapse is not far away. It is time to go elsewhere. The best thing about space travel is that it made it possible to go elsewhere. -- R.A. Heinlein, "Time Enough For Love"
_______________________________________________ Moses-support mailing list Moses-support@mit.edu http://mailman.mit.edu/mailman/listinfo/moses-support
