Moses-support Digest, Vol 110, Issue 1

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: Unable to build Moses: multiple undefined references in
the Moses namespace (Hieu Hoang)
2. Re: "Fixing" words on the target side of the decoder
(Philipp Koehn)
3. normalize punctuation (Vincent Nguyen)
4. System requiremnts for Moses (Hegde, Sujay)


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

Message: 1
Date: Mon, 30 Nov 2015 17:30:12 +0000
From: Hieu Hoang <hieuhoang@gmail.com>
Subject: Re: [Moses-support] Unable to build Moses: multiple undefined
references in the Moses namespace
To: Valmi Dufour-Lussier <valmid@gmail.com>, moses-support@mit.edu
Message-ID: <565C87A4.8090505@gmail.com>
Content-Type: text/plain; charset="windows-1252"

it works for me.

you should compile from the beginning, it looks like there's some
leftover dependencies from the last time you compiled. Do either
1. ./bjam ... -a
2. Delete & download moses again


On 30/11/15 16:31, Valmi Dufour-Lussier wrote:
> Hello,
>
> I'm afraid I must be doing something stupid because I built Moses in
> the past without any problem, but I have just got a new computer and
> I'm getting multiple linking errors, all related to things in the
> Moses namespace.
>
> Here are the first two errors, which look representative to me, and
> I'm attaching the build log:
>
> moses/bin/gcc-5.2.0/release/link-static/threading-multi/libmoses.a(ExportInterface.o):
> In function `batch_run()':
> ExportInterface.cpp:(.text+0x14d8): undefined reference to `typeinfo
> for Moses::Mmsapt'
> ExportInterface.cpp:(.text+0x1507): undefined reference to
> `Moses::Mmsapt::add(std::string const&, std::string const&,
> std::string const&)'
>
> For reference, /opt is a symbolic link to /home/valmi/opt.
>
> The file was generated with:
>
> ./bjam -j40 --with-irstlm=/opt/irstlm --with-boost=/opt/boost_1_59_0
> --debug-configuration -d2
>
> Moses is a fresh pull from this morning, IRSTLM is 5.80.08 and Boost is 1.59.0.
>
> Thanks and regards,
> Valmi
>
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support

--
Hieu Hoang
http://www.hoang.co.uk/hieu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20151130/d161e33c/attachment-0001.html

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

Message: 2
Date: Mon, 30 Nov 2015 22:51:22 +0100
From: Philipp Koehn <phi@jhu.edu>
Subject: Re: [Moses-support] "Fixing" words on the target side of the
decoder
To: Miguel Domingo <midobal@prhlt.upv.es>
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CAAFADDCSzmNbOQyDqyRr2QyHiJDo3-sf+eVcpG03GndJdHHYAw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi,

I would go about it this way.

1. Tag the words that are assumed to be translated correctly in the target.
2. Align them to the source words using the reported word alignment.
3. Specify translations for correctly translated source word spans with XML
markup.

For you example, the end result should be:
<x translation="the">la</x> gran <x translation="house">casa</x> roja

You may want to throw in <wall/> reordering constraints, when suitable.

Check the following paper, where TM matches were converted into such markup:
http://homepages.inf.ed.ac.uk/pkoehn/publications/tm-smt-amta2010.pdf

-phi


On Mon, Nov 30, 2015 at 10:13 AM, Miguel Domingo <midobal@prhlt.upv.es>
wrote:

> Hello,
>
> I know that you can bring external knowledge to the decoder with *XML
> Markup*, but this seems to be true only for the source side of the
> decoder. I was wondering if there is something similar that could be used
> on the target side.
>
> My idea was using moses both for translating and post-editing a sentence,
> so that once the sentence has been translated you could manually select
> those words that have been translated correctly and get a new translation
> of the sentence (using the new knowledge).
>
> As an example, imagine we want to translate the sentence in Spanish *la
> gran casa roja* (*the big red house*), and running moses' decoder we
> obtain the hypothesis *the small green house*. We want to mark those
> words that are correct (*the, house*) and obtain a new hypothesis in
> which those words are left untouched (e.g. *the big green house*).
>
> Is there any way to achieve this?
>
> Thanks in advance,
>
> Miguel
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20151130/0b93afcb/attachment-0001.html

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

Message: 3
Date: Tue, 1 Dec 2015 09:49:00 +0100
From: Vincent Nguyen <vnguyen@neuf.fr>
Subject: [Moses-support] normalize punctuation
To: moses-support <moses-support@mit.edu>
Message-ID: <565D5EFC.3000602@neuf.fr>
Content-Type: text/plain; charset=utf-8; format=flowed

Hieu,

here :
http://www.statmt.org/moses/RELEASE-3.0/models/fr-en/config.pb.recase

I read :

input-tokenizer = "$moses-script-dir/tokenizer/normalize-punctuation.perl $input-extension | $moses-script-dir/tokenizer/tokenizer.perl -a -l $input-extension"
output-tokenizer = "$moses-script-dir/tokenizer/normalize-punctuation.perl $output-extension | $moses-script-dir/tokenizer/tokenizer.perl -a -l $output-extension"


but shouldn't the language be prefixed by "-l" for the
normalize-punctuation.perl sript ?


thanks
V


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

Message: 4
Date: Tue, 1 Dec 2015 10:08:13 +0000
From: "Hegde, Sujay" <Sujay.Hegde@xerox.com>
Subject: [Moses-support] System requiremnts for Moses
To: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<586EA7C483504E48870F5BF54319B6EC4ECA20@USA7109MB006.na.xerox.net>
Content-Type: text/plain; charset="us-ascii"

Dear Moses Admin,

We are using Moses decoder for commercial environment.

We have 132GB RAM, 1TB disk and quadcore Virtual Machine with CentOs OS.

We have 2 language pairs installed, and when running both the models together the Translation hangs(Takes a LONG time).
It is fine when we run only one language model.

Is there any Specific System requirements needed for moses?
Please let me know

Thanks and Regards,
Sujay,
Xerox Business Services, Bangalore, India

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20151201/adf66d4f/attachment-0001.html

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

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


End of Moses-support Digest, Vol 110, Issue 1
*********************************************

0 Response to "Moses-support Digest, Vol 110, Issue 1"

Post a Comment