Moses-support Digest, Vol 104, Issue 23

Send Moses-support mailing list submissions to
moses-support@mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.mit.edu/mailman/listinfo/moses-support
or, via email, send a message with subject or body 'help' to
moses-support-request@mit.edu

You can reach the person managing the list at
moses-support-owner@mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Moses-support digest..."


Today's Topics:

1. Low coverage in Moses forced decoding (praveen dakwale)
2. Re: Low coverage in Moses forced decoding (Hieu Hoang)
3. c++11 support (Rico Sennrich)


----------------------------------------------------------------------

Message: 1
Date: Tue, 16 Jun 2015 16:48:24 +0200
From: praveen dakwale <dakwale.praveen@gmail.com>
Subject: [Moses-support] Low coverage in Moses forced decoding
To: moses-support@mit.edu
Message-ID:
<CANSeoQn_OP1c+wuhpyecs5ebGDuSN_FqJyuZYsV1cc-H+jN=8g@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi All,

I am trying to implement forced decoding procedure of (Weubker et al 2010)
using Moses constrained decoding functionality for a Arabic-English bitext
of ~1 million sentence. For start, I am using Moses to decode a sample of
20000 sentences from this bitext. Though I have tried to relax all the
parameters to as maximum as possible, I haven?t been able to obtain a
coverage of more than 50%. I am describing below models and the parameters
I have used and their maximum/minimum value :

1. Phrase table built from the same bitext using moses training
(grow-diag-final-and algorithm) (~60 million phrase pairs)
2. Distortion penalty, phrase penalty
3. No LM or reordering models. Infinite distortion limit
4. ttable limit : 1000000
5. Stack size (maximum : 3000)
6. Beam size (10^(-10) to 10^(-30) (min))
7. Stack diversity : 0-1

Some of them I have used as discussed in this report (
http://www-labs.iro.umontreal.ca/~foster/papers/forcedecode-techrep12.pdf)


Can anyone explain if I am missing any other parameters set to default in
moses that I should relax to increase my coverage ? Or what are the default
values of all possible parameters in moses ?

Thanks and Regards
Praveen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20150616/dfedf999/attachment-0001.htm

------------------------------

Message: 2
Date: Tue, 16 Jun 2015 18:55:59 +0400
From: Hieu Hoang <hieuhoang@gmail.com>
Subject: Re: [Moses-support] Low coverage in Moses forced decoding
To: praveen dakwale <dakwale.praveen@gmail.com>, moses-support@mit.edu
Message-ID: <558038FF.7040804@gmail.com>
Content-Type: text/plain; charset="windows-1252"

can you please show me your moses.ini files, the exact command you are
using to do force decoding.

Also, can you send me few lines of your input file and your reference file.

On 16/06/2015 18:48, praveen dakwale wrote:
> Hi All,
>
> I am trying to implement forced decoding procedure of (Weubker et al
> 2010) using Moses constrained decoding functionality for a
> Arabic-English bitext of ~1 million sentence. For start, I am using
> Moses to decode a sample of 20000 sentences from this bitext. Though I
> have tried to relax all the parameters to as maximum as possible, I
> haven?t been able to obtain a coverage of more than 50%. I am
> describing below models and the parameters I have used and their
> maximum/minimum value :
>
> 1. Phrase table built from the same bitext using moses training
> (grow-diag-final-and algorithm) (~60 million phrase pairs)
> 2. Distortion penalty, phrase penalty
> 3. No LM or reordering models. Infinite distortion limit
> 4. ttable limit : 1000000
> 5. Stack size (maximum : 3000)
> 6. Beam size (10^(-10) to 10^(-30) (min))
> 7. Stack diversity : 0-1
>
> Some of them I have used as discussed in this report
> (http://www-labs.iro.umontreal.ca/~foster/papers/forcedecode-techrep12.pdf
> <http://www-labs.iro.umontreal.ca/%7Efoster/papers/forcedecode-techrep12.pdf>)
>
>
> Can anyone explain if I am missing any other parameters set to default
> in moses that I should relax to increase my coverage ? Or what are the
> default values of all possible parameters in moses ?
>
> Thanks and Regards
> Praveen
>
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support

--
Hieu Hoang
Researcher
New York University, Abu Dhabi
http://www.hoang.co.uk/hieu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20150616/d5611f24/attachment-0001.htm

------------------------------

Message: 3
Date: Tue, 16 Jun 2015 16:02:59 +0000 (UTC)
From: Rico Sennrich <rico.sennrich@gmx.ch>
Subject: [Moses-support] c++11 support
To: moses-support@mit.edu
Message-ID: <loom.20150616T171542-133@post.gmane.org>
Content-Type: text/plain; charset=us-ascii

Hi list,

some code in mosesdecoder (oxlm, c++tokenizer) already requires c++11. To
let people benefit from the usability and functionality improvements of
c++11, it would be beneficial to allow the use of c++11 features in all of
the code.

before people start making big changes to the codebase, we should make sure
that there are no good reasons against allowing c++11 features, such as lack
of compiler support.

I pushed a minimal commit (6c0f875) to test the waters. If this introduces
bugs, or if users still rely on old compilers without c++11 support, please
complain here.

best wishes,
Rico



------------------------------

_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support


End of Moses-support Digest, Vol 104, Issue 23
**********************************************

Tweet