Moses-support Digest, Vol 98, Issue 51

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: bjam level of parallelism for various moses binaries
(Hieu Hoang)
2. Re: Getting OOV (Fatemeh Eskandari)


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

Message: 1
Date: Sat, 20 Dec 2014 01:38:07 +0530
From: Hieu Hoang <Hieu.Hoang@ed.ac.uk>
Subject: Re: [Moses-support] bjam level of parallelism for various
moses binaries
To: Martin Li?ka <marxin.liska@gmail.com>
Cc: moses-support <moses-support@mit.edu>
Message-ID:
<CAEKMkbgoDg5ZWTC2_0f7XSzi3=RDXrEV++fDaDbmR8vGo6o1iA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

There's no dependencies between the executables. But for so e reason, I
noticed the linking stage isn't done in parallel, just the compile stage
is parallel. This happens in bjam and the eclipse build

Sent while bumping into things
On 19 Dec 2014 18:24, "Martin Li?ka" <marxin.liska@gmail.com> wrote:

> Hello.
>
> I've been just building Moses with enabled LTO (-flto) and compilation
> process runs for quite long time just in one thread:
>
> There're are many of:
>
> gcc.link
> phrase-extract/bin/gcc-5.0.0/release/debug-symbols-on/link-static/threading-multi/relax-parse
> gcc.link
> phrase-extract/bin/gcc-5.0.0/release/debug-symbols-on/link-static/threading-multi/consolidate-reverse
>
> phrase-extract/bin/gcc-5.0.0/release/debug-symbols-on/link-static/threading-multi/extract
>
> ...
>
> And my question is if there are any dependencies between these
> executables that potentially block parallel build?
>
> Thanks,
> Martin
> _______________________________________________
> 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/20141220/c8cbc1ed/attachment-0001.htm

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

Message: 2
Date: Sat, 20 Dec 2014 18:11:28 +0330
From: Fatemeh Eskandari <fatemeh.eskandari.69@gmail.com>
Subject: Re: [Moses-support] Getting OOV
To: Rico Sennrich <rico.sennrich@gmx.ch>
Cc: moses-support@mit.edu
Message-ID:
<CAOoq+SYL3B05GTiome6NwH7Opw88r_grY9f0Bf1GE+M-FhDmSw@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Dear Rico,

Many thanks for your answer.

On 18 December 2014 at 21:24, Rico Sennrich <rico.sennrich@gmx.ch> wrote:

> Fatemeh Eskandari <fatemeh.eskandari.69@...> writes:
>
> > I need to have list of oov words in text file, is there any way to get
> them in moses?
>
> Hi Fatemeh,
>
> the moses option '-output-unknowns <filename>' might be what you want.
>
> It's also possible to get the OOV words without translating the text;
> there's a script in mosesdecoder/scripts/analysis/oov.pl that should do
> this
> if you run it with the option '--verbose'.
>
> best wishes,
> Rico
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>



--


*Best Regards--*

*Fatemeh EskandariM.Sc. *
*student*
* in *
*Artificial Intelligence*
*,*

*Computer Engineering and Electrical Department,Shiraz University, Iran*
eskandari@cse.shirazu.ac.ir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20141220/80c4b42c/attachment-0001.htm

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

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


End of Moses-support Digest, Vol 98, Issue 51
*********************************************

Tweet