Moses Support Digest:moses for cygwin

52nlp — Sun, 17 Jan 2010 02:41:19 +0000

[Moses-support] moses for cygwin

hello everyone:
Is there somebody install moses in cygwin? when i install it in cygwin, the srilm does not install¡.

Re:[Moses-support] moses for cygwin

hello,

srilm is not a part of moses, you need to install the LM library yourself (SRILM, RandLM or IRSTLM) and compile moses accordingly.

Regards
Marcin

NOTICE:This is digested from the Moses-support mailing list, which supports for the moses SMT decoder.

Moses Support Digest:moses decoder results on cygwin and dos

52nlp — Fri, 27 Nov 2009 12:27:43 +0000

[Moses-support] moses decoder results on cygwin and dos

Dear All

Running the moses decoder on cygwin and dos gives slightly different results, even though I’m using the same executable and the same models.

For example, translating from Welsh to English:

Welsh: bydd y bore ‘n oer .
English: the morning will be cold .

moses at cygwin: morning will be cold .
moses at dos: bydd the morning will be cold .

The main problem is that on dos, moses is always returning the first word of the source language, prepended to the translation itself. Easy to strip off but annoying. The translation itself is often slightly better on dos than on cygwin, as above (which is if anything even stranger).

Can anyone account for this strange behaviour? More important, how can I stop the first word of source language returning?

Thanks and best wishes

Ivan

Re:[Moses-support] moses decoder results on cygwin and dos

hi ivan

i think this might be a problem with line ending again. The non-printing 0×13 character is being appended to the 1st input word which causes it to be unrecognised so it is outputted ad-verbatim. Cygwin properly has internal code which strips out this character make sure you convert all text files to unix line endings using dos2unix.

Re:[Moses-support] moses decoder results on cygwin and dos

Hieu

Thanks for your comment.

How can this be a line-ending issue? Where are line-endings involved?

What is appending an extra character to the first word and why?

The 1st input word *is* being recognised and translated (as I said, the translations under dos are correct) — “bydd” translates to “will be”.

I’m using identical material under cygwin and dos, the only difference
is under cygwin I’m using a shell script and under dos I’m using a
“.bat” file. If it is a line-ending issue why is it affecting dos and
not cygwin?

Re:[Moses-support] moses decoder results on cygwin and dos

Hi,

I have seen text files under windows that add a starting byte to indicate the encoding of the file. Sine the first word is a problem,
this may be the cause.

-phi

Re:[Moses-support] moses decoder results on cygwin and dos

I am not sending text to moses from a text file, I am using the command-line:

m.bat contains:

echo %1 | c:\cygwin\path\to\moses.exe -f c:\cygwin\path\to\moses.ini 2> msc_tywyddTeletestun.err

usage

> m.bat “bydd y bore ‘n oer .”
“bydd the morning will be cold .”

Re:[Moses-support] moses decoder results on cygwin and dos

the echo in dos & unix works slightly differently.

dos: echo “c”
“c”

unix:echo “c”
c

the ” char is being appended to the 1st word. oh the joys of command line….

Re:[Moses-support] moses decoder results on cygwin and dos

Dear Hieu

This was the vital clue I needed. Thanks! If I make sure I use the cygwin echo instead of the dos echo, I get the expected result without the repeated first word.

Why is the dos echo idiosyncratic and unreliable? I think we all know the answer to that.

Thanks again for persevering with suggestions.

Best

Ivan

NOTICE:This is digested from the Moses-support mailing list, which supports for the moses SMT decoder.

52nlp's Learning Notes » cygwin

Moses Support Digest:moses for cygwin

Moses Support Digest:moses decoder results on cygwin and dos