Re: [Moses-support] Which symal?

You shouldn't assume that. symal predates Moses, I'm not sure who wrote it. It may be that the author allowed it to be dual licensed. The license for Moses is clear and has not changed since it started - LGPL 2.1. The license for mgiza and GIZA++ is also looks clear - GPL 2 On 12/01/16

Re: [Moses-support] Error when running moses server with sample code

Hi Lane Can you get a stack trace to see which line the message is coming from? That error message is repeated in a few files. From looking at the code, I'd guess that the OutputFactorOrder is not being initialised correctly. Possibly due to the refactoring of the config code. Does your

Re: [Moses-support] Which symal?

So, you can sublicense Moses (LGPL) but not mgiza (GPL): http://choosealicense.com/licenses/ ​​ ​Which I guess may m​ean something like that you can re-license a modified version of Moses without symal but not with symal. ​In other words, to license a modified version of​ Moses with your own

Re: [Moses-support] Error when running moses server with sample code

Thanks. I don't use the switch. I just found that it was enabled in the sample client.py On Tue, Jan 12, 2016 at 12:43 PM, Ulrich Germann wrote: > Fixed, but chances are you won't like the output. --report-all-factors > appears to be a legacy debugging switch that

Re: [Moses-support] Error when running moses server with sample code

Fixed, but chances are you won't like the output. --report-all-factors appears to be a legacy debugging switch that dumps the value of all factor slots provided by moses (the maximum number of factors is set at compile time), regardless of whether or not they are used by the system. Normal users

Re: [Moses-support] Error when running moses server with sample code

I compiled with variant=debug. What else do I need to do to get a stack trace? On Tue, Jan 12, 2016 at 3:16 AM, Barry Haddow wrote: > Hi Lane > > Can you get a stack trace to see which line the message is coming from? > That error message is repeated in a few files.

Re: [Moses-support] Error when running moses server with sample code

Never mind. I figured out how. (gdb) bt > #0 0x75d905e9 in raise () from /lib64/libc.so.6 > #1 0x75d91cf8 in abort () from /lib64/libc.so.6 > #2 0x768b09b5 in __gnu_cxx::__verbose_terminate_handler() () from > /lib64/libstdc++.so.6 > #3 0x768ae926 in ?? () from

Re: [Moses-support] Error on lmplz

Steps to reproduce this error: $ ~/mosesdecoder.git/bin/lmplz -o 2 <<< "that is what happens ? cssd has > nothing more or voldemort or pastries in prague ." > === 1/5 Counting and sorting n-grams === > Reading /tmp/sh-thd-107574999377 (deleted) > >

Re: [Moses-support] Tiny sample data uses outdated file format

Hi, I fixed it. -phi On Mon, Jan 11, 2016 at 4:33 PM, Lane Schwartz wrote: > http://www.statmt.org/moses/sample-data/complete/tiny.zip > > The config file included in the above sample doesn't work anymore, > presumably due to a change in the ini format. > > $

Re: [Moses-support] Error on lmplz

Pushed the fix from kenlm master in October to Moses master. On 01/12/2016 10:34 PM, Lane Schwartz wrote: > Steps to reproduce this error: > > $ ~/mosesdecoder.git/bin/lmplz -o 2 <<< "that is what happens ? cssd > has nothing more or voldemort or pastries in prague ." > === 1/5

Re: [Moses-support] Error when running moses server with sample code

Looks like this is not specific to mosesserver. Same error occurs when running moses with --report-all-factors. On Tue, Jan 12, 2016 at 9:59 AM, Lane Schwartz wrote: > Never mind. I figured out how. > > (gdb) bt >> #0 0x75d905e9 in raise () from /lib64/libc.so.6 >>