Moses-support Digest, Vol 99, Issue 42

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. Re: Question about mosesserver binary (Tom Hoar)
2. Re: Fuzzy Match Rule segfaults (Hieu Hoang)
3. Constrained decoding (Jes?s Gonz?lez Rubio)
4. Re: Constrained decoding (Hieu Hoang)


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

Message: 1
Date: Tue, 20 Jan 2015 08:04:31 +0700
From: Tom Hoar <tahoar@precisiontranslationtools.com>
Subject: Re: [Moses-support] Question about mosesserver binary
To: moses-support@mit.edu
Message-ID: <54BDA99F.2080508@precisiontranslationtools.com>
Content-Type: text/plain; charset=windows-1252; format=flowed

Solution found. Previous Ubuntu versions required the package
libxmlrpc-core-c3-dev. It doesn't work any more.

The new package is libxmlrpc-c++8-dev. Install this package. It is
currently at version 1.33 (Ubuntu 14.04.1). Then, simply include the
argument --with-xmlrpc-c on the bjam command line. No need to define the
path. It will be found automatically.


On 01/16/2015 05:04 PM, Hieu Hoang wrote:
> i personally compile xmlrpc-c myself and get moses to link to it
> ./bjam --with-xmlrpc-c=/path/to/xmlrpc-c
> That way, you have more control. Moses doesn't like xmlrpc-c v. 1.25.29
> (off the top of my head). Also, you can delete the .so file and force
> moses to link to the static libraries. This will allow you to move your
> executable around different servers easier
>
>
> On 16/01/15 09:54, Tom Hoar wrote:
>> I compiled the yesterday's github commit. It seems to have gone well...
>> but I forgot to redirect output to a log file. Oops.
>>
>> Before restarting, I noticed the mosesserver binary is missing. On
>> closer inspection, default Ubuntu 14.04 does not include libxmlrpc. Does
>> anyone now the Debian package that adds this support? I think it should
>> be `libxmlrpc-core-c3-dev`.
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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



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

Message: 2
Date: Tue, 20 Jan 2015 12:15:47 +0000
From: Hieu Hoang <Hieu.Hoang@ed.ac.uk>
Subject: Re: [Moses-support] Fuzzy Match Rule segfaults
To: Jon Olds <joft_uk@yahoo.co.uk>
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CAEKMkbhQ5fUto_=BMs1DqZBdXwUpVWZGrMztoqr2+97bUjyfbw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

it should work, but no-one asked about it for a long time. It may not be
used by many people and fallen into a state of disrepair.

If you want to send me your data files, I can take a look at it when I've
got time

On 16 January 2015 at 15:51, Jon Olds <joft_uk@yahoo.co.uk> wrote:

> Hi,
>
> I?ve been taking another look at the fuzzy match rule for hierarchical
> models. I am really not sure how to set it up but seem to have got some
> response by using the moses.ini below.
>
> Unfortunately, it then segfaults every time after the following output.
>
> I?m probably doing something very stupid, but any assistance would be
> much appreciated.
>
> Cheers,
>
> Jon
>
> (6.6) consolidating the two halves @ Fri Jan 16 15:21:28 UTC 2015
> Executing: /home/ubuntu/tools/mosesdecoder/scripts/../bin/consolidate
> /tmp/moses.gpitcm/fuzzyMatchFile.pt.half.f2e.gz
> /tmp/moses.gpitcm/fuzzyMatchFile.pt.half.e2f.gz /dev/stdout
> --Hierarchical | gzip -c > /tmp/moses.gpitcm/fuzzyMatchFile.pt.gz
> Consolidate v2.0 written by Philipp Koehn
> consolidating direct and indirect rule tables
> processing hierarchical rules
> Executing: rm -f /tmp/moses.gpitcm/fuzzyMatchFile.pt.half.*
> Start loading fuzzy-match phrase model : [41.633] seconds
> Line 0: Initialize search took 0.116 seconds total
> Translating: <s> ce v?hicule est ? ce jour le plus important d?di? ? l'
> immobilier tertiaire en Ile - de - France . </s> ||| [0,0]=X (1) [0,1]=X
> (1) [0,2]=X (1) [0,3]=X (1) [0,4]=X (1) [0,5]=X (1) [0,6]=X (1) [0,7]=X
> (1) [0,8]=X (1) [0,9]=X (1) [0,10]=X (1) [0,11]=X (1) [0,12]=X (1)
> [0,13]=X (1) [0,14]=X (1) [0,15]=X (1) [0,16]=X (1) [0,17]=X (1)
> [0,18]=X (1) [0,19]=X (1) [0,20]=X (1) [0,21]=X (1) [0,22]=X (1) [1,1]=X
> (1) [1,2]=X (1) [1,3]=X (1) [1,4]=X (1) [1,5]=X (1) [1,6]=X (1) [1,7]=X
> (1) [1,8]=X (1) [1,9]=X (1) [1,10]=X (1) [1,11]=X (1) [1,12]=X (1)
> [1,13]=X (1) [1,14]=X (1) [1,15]=X (1) [1,16]=X (1) [1,17]=X (1)
> [1,18]=X (1) [1,19]=X (1) [1,20]=X (1) [1,21]=X (1) [1,22]=X (1) [2,2]=X
> (1) [2,3]=X (1) [2,4]=X (1) [2,5]=X (1) [2,6]=X (1) [2,7]=X (1) [2,8]=X
> (1) [2,9]=X (1) [2,10]=X (1) [2,11]=X (1) [2,12]=X (1) [2,13]=X (1)
> [2,14]=X (1) [2,15]=X (1) [2,16]=X (1) [2,17]=X (1) [2,18]=X (1)
> [2,19]=X (1) [2,20]=X (1) [2,21]=X (1) [2,22]=X (1) [3,3]=X (1) [3,4]=X
> (1) [3,5]=X (1) [3,6]=X (1) [3,7]=X (1) [3,8]=X (1) [3,9]=X (1) [3,10]=X
> (1) [3,11]=X (1) [3,12]=X (1) [3,13]=X (1) [3,14]=X (1) [3,15]=X (1)
> [3,16]=X (1) [3,17]=X (1) [3,18]=X (1) [3,19]=X (1) [3,20]=X (1)
> [3,21]=X (1) [3,22]=X (1) [4,4]=X (1) [4,5]=X (1) [4,6]=X (1) [4,7]=X
> (1) [4,8]=X (1) [4,9]=X (1) [4,10]=X (1) [4,11]=X (1) [4,12]=X (1)
> [4,13]=X (1) [4,14]=X (1) [4,15]=X (1) [4,16]=X (1) [4,17]=X (1)
> [4,18]=X (1) [4,19]=X (1) [4,20]=X (1) [4,21]=X (1) [4,22]=X (1) [5,5]=X
> (1) [5,6]=X (1) [5,7]=X (1) [5,8]=X (1) [5,9]=X (1) [5,10]=X (1)
> [5,11]=X (1) [5,12]=X (1) [5,13]=X (1) [5,14]=X (1) [5,15]=X (1)
> [5,16]=X (1) [5,17]=X (1) [5,18]=X (1) [5,19]=X (1) [5,20]=X (1)
> [5,21]=X (1) [5,22]=X (1) [6,6]=X (1) [6,7]=X (1) [6,8]=X (1) [6,9]=X
> (1) [6,10]=X (1) [6,11]=X (1) [6,12]=X (1) [6,13]=X (1) [6,14]=X (1)
> [6,15]=X (1) [6,16]=X (1) [6,17]=X (1) [6,18]=X (1) [6,19]=X (1)
> [6,20]=X (1) [6,21]=X (1) [6,22]=X (1) [7,7]=X (1) [7,8]=X (1) [7,9]=X
> (1) [7,10]=X (1) [7,11]=X (1) [7,12]=X (1) [7,13]=X (1) [7,14]=X (1)
> [7,15]=X (1) [7,16]=X (1) [7,17]=X (1) [7,18]=X (1) [7,19]=X (1)
> [7,20]=X (1) [7,21]=X (1) [7,22]=X (1) [8,8]=X (1) [8,9]=X (1) [8,10]=X
> (1) [8,11]=X (1) [8,12]=X (1) [8,13]=X (1) [8,14]=X (1) [8,15]=X (1)
> [8,16]=X (1) [8,17]=X (1) [8,18]=X (1) [8,19]=X (1) [8,20]=X (1)
> [8,21]=X (1) [8,22]=X (1) [9,9]=X (1) [9,10]=X (1) [9,11]=X (1) [9,12]=X
> (1) [9,13]=X (1) [9,14]=X (1) [9,15]=X (1) [9,16]=X (1) [9,17]=X (1)
> [9,18]=X (1) [9,19]=X (1) [9,20]=X (1) [9,21]=X (1) [9,22]=X (1)
> [10,10]=X (1) [10,11]=X (1) [10,12]=X (1) [10,13]=X (1) [10,14]=X (1)
> [10,15]=X (1) [10,16]=X (1) [10,17]=X (1) [10,18]=X (1) [10,19]=X (1)
> [10,20]=X (1) [10,21]=X (1) [10,22]=X (1) [11,11]=X (1) [11,12]=X (1)
> [11,13]=X (1) [11,14]=X (1) [11,15]=X (1) [11,16]=X (1) [11,17]=X (1)
> [11,18]=X (1) [11,19]=X (1) [11,20]=X (1) [11,21]=X (1) [11,22]=X (1)
> [12,12]=X (1) [12,13]=X (1) [12,14]=X (1) [12,15]=X (1) [12,16]=X (1)
> [12,17]=X (1) [12,18]=X (1) [12,19]=X (1) [12,20]=X (1) [12,21]=X (1)
> [12,22]=X (1) [13,13]=X (1) [13,14]=X (1) [13,15]=X (1) [13,16]=X (1)
> [13,17]=X (1) [13,18]=X (1) [13,19]=X (1) [13,20]=X (1) [13,21]=X (1)
> [13,22]=X (1) [14,14]=X (1) [14,15]=X (1) [14,16]=X (1) [14,17]=X (1)
> [14,18]=X (1) [14,19]=X (1) [14,20]=X (1) [14,21]=X (1) [14,22]=X (1)
> [15,15]=X (1) [15,16]=X (1) [15,17]=X (1) [15,18]=X (1) [15,19]=X (1)
> [15,20]=X (1) [15,21]=X (1) [15,22]=X (1) [16,16]=X (1) [16,17]=X (1)
> [16,18]=X (1) [16,19]=X (1) [16,20]=X (1) [16,21]=X (1) [16,22]=X (1)
> [17,17]=X (1) [17,18]=X (1) [17,19]=X (1) [17,20]=X (1) [17,21]=X (1)
> [17,22]=X (1) [18,18]=X (1) [18,19]=X (1) [18,20]=X (1) [18,21]=X (1)
> [18,22]=X (1) [19,19]=X (1) [19,20]=X (1) [19,21]=X (1) [19,22]=X (1)
> [20,20]=X (1) [20,21]=X (1) [20,22]=X (1) [21,21]=X (1) [21,22]=X (1)
> [22,22]=X (1)
>
>
> ### MOSES CONFIG FILE ###
> #########################
>
> # input factors
> [input-factors]
> 0
>
> # mapping steps
> [mapping]
> 0 T 0
>
> [cube-pruning-pop-limit]
> 1000
>
> [non-terminals]
> X
>
> [search-algorithm]
> 3
>
> [inputtype]
> 3
>
> [max-chart-span]
> 20
>
> # feature functions
> [feature]
> PhraseDictionaryFuzzyMatch source=/home/ubuntu/data/tok/base.clean.fr
> target=/home/ubuntu/data/tok/base.clean.en
> alignment=/home/ubuntu/train/model/aligned.grow-diag-final-and
> num-features=0
> KENLM lazyken=0 name=LM0 factor=0 path=/home/ubuntu/train/lm/base.blm.en
> order=3
>
> # dense weights for feature functions
>
>
> [weight]
> LM0= 0.0866615
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>



--
Hieu Hoang
Research Associate
University of Edinburgh
http://www.hoang.co.uk/hieu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20150120/a7ba2e51/attachment-0001.htm

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

Message: 3
Date: Tue, 20 Jan 2015 14:10:41 +0000
From: Jes?s Gonz?lez Rubio <jesus.g.rubio@gmail.com>
Subject: [Moses-support] Constrained decoding
To: moses-support <moses-support@mit.edu>
Message-ID:
<CAF+=9hjo-AxV-SANerhx1TRj7FcifX7jgqBW0XDMtsX7aPJrSA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi all,

I have some questions about the constrained decoding feature implemented in
moses, (ConstrainedDecoding).

Which is the meaning of the 'max-unknowns' parameter?

I understand 'max-unknowns' as something like the maximum edit distance
allowed between the final translation and the reference, i.e the maximum
number of words in the final translation that are allowed to be different
to the reference. Is this interpretation correct?

Also, what is the interpretation of the 'negate' and 'soft' parameters?

Thanks in advance.

Cheers.
--
Jes?s
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20150120/58695129/attachment-0001.htm

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

Message: 4
Date: Tue, 20 Jan 2015 14:27:50 +0000
From: Hieu Hoang <Hieu.Hoang@ed.ac.uk>
Subject: Re: [Moses-support] Constrained decoding
To: Jes?s Gonz?lez Rubio <jesus.g.rubio@gmail.com>
Cc: moses-support <moses-support@mit.edu>
Message-ID:
<CAEKMkbj2jfTDbO7HEmqjduMu14NbWzL7psh5fj0sdi=5JB8aMA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

max-unknowns = like the edit distance. The maximum number of non-matching
words

negate = instead of allowing only translations that match the reference,
allow only translations that do NOT match

soft = don't throw away non-matching translations, just penalise it.

I was basically messing around, I didn't check the results very carefully.
there may be bugs.


On 20 January 2015 at 14:10, Jes?s Gonz?lez Rubio <jesus.g.rubio@gmail.com>
wrote:

> Hi all,
>
> I have some questions about the constrained decoding feature implemented
> in moses, (ConstrainedDecoding).
>
> Which is the meaning of the 'max-unknowns' parameter?
>
> I understand 'max-unknowns' as something like the maximum edit distance
> allowed between the final translation and the reference, i.e the maximum
> number of words in the final translation that are allowed to be different
> to the reference. Is this interpretation correct?
>
> Also, what is the interpretation of the 'negate' and 'soft' parameters?
>
> Thanks in advance.
>
> Cheers.
> --
> Jes?s
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
>


--
Hieu Hoang
Research Associate
University of Edinburgh
http://www.hoang.co.uk/hieu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20150120/55af7cf4/attachment.htm

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

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


End of Moses-support Digest, Vol 99, Issue 42
*********************************************

Tweet