Home » Uncategories » Moses-support Digest, Vol 92, Issue 7

Moses-support Digest, Vol 92, Issue 7

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: Importing Eclipse projects (Hieu Hoang)
2. Re: Need help/suggestions in setup EMS (Hieu Hoang)
3. Re: Importing Eclipse projects (Lars Bungum)


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

Message: 1
Date: Tue, 3 Jun 2014 09:49:27 +0100
From: Hieu Hoang <Hieu.Hoang@ed.ac.uk>
Subject: Re: [Moses-support] Importing Eclipse projects
To: Lars Bungum <lars.bungum@idi.ntnu.no>
Cc: moses-support <moses-support@mit.edu>
Message-ID:
<CAEKMkbh4uVF1m59WaMO3On0Aatovv8ZATbY60BgcKBFUBwX+sA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Some advise:
1. Only use the eclipse build if you intend to debug & change the C++
code. There's no other reason otherwise
2. You must switch your workspace to
{MOSES}/contrib/other-builds
3. There is no flexibility in what external libraries you need to link
to. You must link to
i. boost
ii. DALM
iii. irstlm
iv. randlm
v. srilm
If you've never used these libraries before, I suggest you use the
Moses bjam build 1st and make sure the external libs are properly compiled.
4. The external libs must be in the root of the moses folder, with
specific names. I softlink them to my moses folder. For example, this is
the listing of my moses folder:
#ls -l
drwxr-xr-x 3 hieu hieu 4096 Jan 15 11:05 biconcor
drwxrwxr-x 2 hieu hieu 4096 Jun 2 18:17 bin
-rwxr-xr-x 1 hieu hieu 780 Jan 15 10:58 bjam
lrwxrwxrwx 1 hieu hieu 39 Jan 20 16:23 boost ->
/home/hieu/workspace/boost/boost_1_55_0
-rw-rw-r-- 1 hieu hieu 119 May 30 09:30 BUILD-INSTRUCTIONS.txt
drwxr-xr-x 24 hieu hieu 4096 Apr 30 16:50 contrib
drwxr-xr-x 3 hieu hieu 4096 Jan 15 10:58 cruise-control
lrwxrwxrwx 1 hieu hieu 33 Jan 20 16:23 DALM ->
/home/hieu/workspace/github/DALM/
drwxr-xr-x 2 hieu hieu 4096 Mar 12 19:27 defer
-rw-r--r-- 1 hieu hieu 3399 May 12 19:43 err
-rw-r--r-- 1 hieu hieu 2473076 Mar 21 21:17 err.ubuntu13.10
lrwxrwxrwx 1 hieu hieu 27 Jan 20 16:23 irstlm ->
/home/hieu/workspace/irstlm
drwxr-xr-x 5 hieu hieu 4096 Mar 16 15:44 jam-files
-rw-rw-r-- 1 hieu hieu 6835 Apr 29 16:42 Jamroot
-rw-r--r-- 1 hieu hieu 5848 Mar 3 14:51 Jamroot~
drwxrwxr-x 2 hieu hieu 4096 May 30 09:37 lib
drwxr-xr-x 5 hieu hieu 4096 May 8 17:09 lm
drwxr-xr-x 6 hieu hieu 4096 May 16 15:01 mert
drwxr-xr-x 3 hieu hieu 4096 Mar 13 17:27 mingw
drwxr-xr-x 4 hieu hieu 4096 May 16 14:26 mira
drwxr-xr-x 5 hieu hieu 4096 Mar 12 19:27 misc
drwxr-xr-x 7 hieu hieu 12288 May 20 19:52 moses
drwxr-xr-x 3 hieu hieu 4096 May 20 19:52 moses-chart-cmd
drwxr-xr-x 3 hieu hieu 4096 May 7 09:53 moses-cmd
-rw------- 1 hieu hieu 0 May 1 10:24 nohup.out
-rw-r--r-- 1 hieu hieu 159 Jan 15 10:58 NOTICE
drwxr-xr-x 3 hieu hieu 4096 Apr 17 19:13 OnDiskPt
drwxr-xr-x 8 hieu hieu 4096 Mar 16 15:44 phrase-extract
-rwxr-xr-x 1 hieu hieu 260 Jun 2 18:15 previous.sh
lrwxrwxrwx 1 hieu hieu 36 Jan 22 16:08 probingPT ->
/home/hieu/workspace/github/proj4.hh
lrwxrwxrwx 1 hieu hieu 28 Jan 20 16:29 randlm ->
/home/hieu/workspace/randlm/
drwxr-xr-x 3 hieu hieu 4096 May 12 19:16 regression-testing
drwxr-xr-x 16 hieu hieu 4096 Apr 29 16:42 scripts
drwxr-xr-x 3 hieu hieu 4096 Apr 17 19:13 search
lrwxrwxrwx 1 hieu hieu 26 Jan 20 16:23 srilm ->
/home/hieu/workspace/srilm
drwxr-xr-x 3 hieu hieu 4096 Jan 15 11:04 symal
drwxr-xr-x 5 hieu hieu 4096 May 8 17:08 util



On 3 June 2014 08:44, Lars Bungum <lars.bungum@idi.ntnu.no> wrote:

> Hi,
>
> I try to import the Eclipse projects in the contrib/other-builds
> directory, but I am having some problems. Despite following the steps
> exactly, the projects fail to build with this error message:
>
> /usr/bin/ld: cannot find -lmoses
>
> (and more for the other modules I didn't symlink in yet). When I look
> into the other-builds/moses directory, it is empty. What do I have to
> do to get this working?
>
> //LB
> _______________________________________________
> 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/20140603/c32e5bef/attachment-0001.htm

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

Message: 2
Date: Tue, 3 Jun 2014 10:00:51 +0100
From: Hieu Hoang <Hieu.Hoang@ed.ac.uk>
Subject: Re: [Moses-support] Need help/suggestions in setup EMS
To: Attilio Santocchia <attilio.santocchia@unipg.it>
Cc: moses-support <moses-support@mit.edu>
Message-ID:
<CAEKMkbg3-1eZtcYYFy=qfmn+QDh+6qNt643=5J-uP+MTmqDPVw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I personally wouldn't bother with SGE. Moses has support for
multi-threading for a long time now.

However, I would choose a solution where the machines have LOTS of ram. A
typical server I currently use has 144GB RAM

lots of CPU cores and disk space is also useful


On 1 June 2014 11:12, Attilio Santocchia <attilio.santocchia@unipg.it>
wrote:

> Hello,
>
> I'm starting to use moses and I'm going through the documentation.
> The how-to is quite clear and I was able to setup a test machine for the
> Experiment but now I'd like to have some advice. Our plan is to start an
> intensive test of a lot of public and private corpora we already have for
> learning what's the best result/configuration for our needs. Here is my
> question: we have different options to install our test bench and I don't
> know which one is the better one...
>
> 1) A openstack private cloud: here I can instantiate many VM (up to 10).
> Each VM could get 8GB and 4 vCPU
>
> 2) A commercial cloud (not S3) where I guess I can instantiate more
> powerfull VM (probably I can go up to 8-16 vCPU and an unlimited
> memory... not sure yet how much) but here I have to pay for what I use
>
> In both case I can (if it's useful) install SGE but reading few threads in
> the
> mailing list I'm not sure it's worth the effort. So what's your suggestion?
> Do I invest some time in installing and setup the SGE in
> the cloud or it's better to stick with a single powerful machine?
> In the Moses FAQ I read "takes 1-2 days to tune using 15 CPUs.
> 10-15 iterations are typical"... is this the amount of resources needed?
> If I can shorten the test phase I can also to consider to get more
> resources but I don't have any feeling...
>
> Suggestion and/or comments are very welcome!
>
> Thanks
>
> Attilio
>
> _______________________________________________
> 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/20140603/5722edd4/attachment-0001.htm

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

Message: 3
Date: Tue, 03 Jun 2014 13:39:23 +0200
From: Lars Bungum <lars.bungum@idi.ntnu.no>
Subject: Re: [Moses-support] Importing Eclipse projects
To: Hieu Hoang <Hieu.Hoang@ed.ac.uk>
Cc: moses-support <moses-support@mit.edu>
Message-ID: <538DB3EB.7050608@idi.ntnu.no>
Content-Type: text/plain; charset="utf-8"

Hi Hieu,

thanks!

It's a lot better now. I'm going to do some feature development (for DA
purposes), so I would like to get into the code, kind of to get a better
feel of what I'm working on.

It mostly works now, after adding the directory mosesdecoder/lib to the
g++ linker includes in Eclipse (or doing it manually at the command line).

What remains now are several errors from DALM when building moses
itself. To me this sounds like a version error, as it seems to pertain
to arity changes, e.g.

mosesdecoder/moses/LM/DALMWrapper.cpp: In member function ?virtual void
Moses::LanguageModelDALM::Load()?:
mosesdecoder/moses/LM/DALMWrapper.cpp:213:48: error: no matching
function for call to ?DALM::LM::LM(std::string&, DALM::Vocabulary&,
DALM::Logger&)?
mosesdecoder/moses/LM/DALMWrapper.cpp:213:48: note: candidates are:
mosesdecoder/contrib/other-builds/../../DALM/include/dalm.h:23:4: note:
DALM::LM::LM(std::string, DALM::Vocabulary&, unsigned char, DALM::Logger&)
mosesdecoder/contrib/other-builds/../../DALM/include/dalm.h:23:4:
note: candidate expects 4 arguments, 3 provided
mosesdecoder/contrib/other-builds/../../DALM/include/dalm.h:22:4: note:
DALM::LM::LM(std::string, std::string, DALM::Vocabulary&, size_t,
unsigned int, DALM::Logger&)

I just downloaded the latest DALM version and compiled it. Is this the
correct one?

//LB

On 03. juni 2014 10:49, Hieu Hoang wrote:
> Some advise:
> 1. Only use the eclipse build if you intend to debug & change the
> C++ code. There's no other reason otherwise
> 2. You must switch your workspace to
> {MOSES}/contrib/other-builds
> 3. There is no flexibility in what external libraries you need to
> link to. You must link to
> i. boost
> ii. DALM
> iii. irstlm
> iv. randlm
> v. srilm
> If you've never used these libraries before, I suggest you use
> the Moses bjam build 1st and make sure the external libs are properly
> compiled.
> 4. The external libs must be in the root of the moses folder, with
> specific names. I softlink them to my moses folder. For example, this
> is the listing of my moses folder:
> #ls -l
> drwxr-xr-x 3 hieu hieu 4096 Jan 15 11:05 biconcor
> drwxrwxr-x 2 hieu hieu 4096 Jun 2 18:17 bin
> -rwxr-xr-x 1 hieu hieu 780 Jan 15 10:58 bjam
> lrwxrwxrwx 1 hieu hieu 39 Jan 20 16:23 boost ->
> /home/hieu/workspace/boost/boost_1_55_0
> -rw-rw-r-- 1 hieu hieu 119 May 30 09:30 BUILD-INSTRUCTIONS.txt
> drwxr-xr-x 24 hieu hieu 4096 Apr 30 16:50 contrib
> drwxr-xr-x 3 hieu hieu 4096 Jan 15 10:58 cruise-control
> lrwxrwxrwx 1 hieu hieu 33 Jan 20 16:23 DALM ->
> /home/hieu/workspace/github/DALM/
> drwxr-xr-x 2 hieu hieu 4096 Mar 12 19:27 defer
> -rw-r--r-- 1 hieu hieu 3399 May 12 19:43 err
> -rw-r--r-- 1 hieu hieu 2473076 Mar 21 21:17 err.ubuntu13.10
> lrwxrwxrwx 1 hieu hieu 27 Jan 20 16:23 irstlm ->
> /home/hieu/workspace/irstlm
> drwxr-xr-x 5 hieu hieu 4096 Mar 16 15:44 jam-files
> -rw-rw-r-- 1 hieu hieu 6835 Apr 29 16:42 Jamroot
> -rw-r--r-- 1 hieu hieu 5848 Mar 3 14:51 Jamroot~
> drwxrwxr-x 2 hieu hieu 4096 May 30 09:37 lib
> drwxr-xr-x 5 hieu hieu 4096 May 8 17:09 lm
> drwxr-xr-x 6 hieu hieu 4096 May 16 15:01 mert
> drwxr-xr-x 3 hieu hieu 4096 Mar 13 17:27 mingw
> drwxr-xr-x 4 hieu hieu 4096 May 16 14:26 mira
> drwxr-xr-x 5 hieu hieu 4096 Mar 12 19:27 misc
> drwxr-xr-x 7 hieu hieu 12288 May 20 19:52 moses
> drwxr-xr-x 3 hieu hieu 4096 May 20 19:52 moses-chart-cmd
> drwxr-xr-x 3 hieu hieu 4096 May 7 09:53 moses-cmd
> -rw------- 1 hieu hieu 0 May 1 10:24 nohup.out
> -rw-r--r-- 1 hieu hieu 159 Jan 15 10:58 NOTICE
> drwxr-xr-x 3 hieu hieu 4096 Apr 17 19:13 OnDiskPt
> drwxr-xr-x 8 hieu hieu 4096 Mar 16 15:44 phrase-extract
> -rwxr-xr-x 1 hieu hieu 260 Jun 2 18:15 previous.sh
> lrwxrwxrwx 1 hieu hieu 36 Jan 22 16:08 probingPT ->
> /home/hieu/workspace/github/proj4.hh
> lrwxrwxrwx 1 hieu hieu 28 Jan 20 16:29 randlm ->
> /home/hieu/workspace/randlm/
> drwxr-xr-x 3 hieu hieu 4096 May 12 19:16 regression-testing
> drwxr-xr-x 16 hieu hieu 4096 Apr 29 16:42 scripts
> drwxr-xr-x 3 hieu hieu 4096 Apr 17 19:13 search
> lrwxrwxrwx 1 hieu hieu 26 Jan 20 16:23 srilm ->
> /home/hieu/workspace/srilm
> drwxr-xr-x 3 hieu hieu 4096 Jan 15 11:04 symal
> drwxr-xr-x 5 hieu hieu 4096 May 8 17:08 util
>
>
>
> On 3 June 2014 08:44, Lars Bungum <lars.bungum@idi.ntnu.no
> <mailto:lars.bungum@idi.ntnu.no>> wrote:
>
> Hi,
>
> I try to import the Eclipse projects in the contrib/other-builds
> directory, but I am having some problems. Despite following the
> steps
> exactly, the projects fail to build with this error message:
>
> /usr/bin/ld: cannot find -lmoses
>
> (and more for the other modules I didn't symlink in yet). When I look
> into the other-builds/moses directory, it is empty. What do I
> have to
> do to get this working?
>
> //LB
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu <mailto: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/20140603/c8458515/attachment.htm

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

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


End of Moses-support Digest, Vol 92, Issue 7
********************************************

0 Response to "Moses-support Digest, Vol 92, Issue 7"

Post a Comment

Subscribe to: Post Comments (Atom)