Hi,

2 questions:

1. I have used  5 order  LM, and run the tuning step but in moses.ini file 
still the LM order is 3! How it is may?
2. If i want to change the distortion limit or ttable-limit, is it enough to 
change it manually in the moses.ini, or it is needed to re-run tuning step? 
Does the change of DL or tt-limit effect other parameters of the moses.ini? 



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

Best Regards,

S.Bakhshaei

--- On Wed, 3/31/10, [email protected] 
<[email protected]> wrote:

From: [email protected] <[email protected]>
Subject: Moses-support Digest, Vol 41, Issue 40
To: [email protected]
Date: Wednesday, March 31, 2010, 5:31 PM

Send Moses-support mailing list submissions to
    [email protected]

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
    [email protected]

You can reach the person managing the list at
    [email protected]

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


Today's Topics:

   1. Re: MOSES Server installation: compilation error (Hieu Hoang)
   2. Re: MOSES Server installation: compilation error (Barry Haddow)
   3. Re: MOSES Server installation: compilation error (Zahurul Islam)
   4. Re: MOSES Server installation: compilation error (Barry Haddow)
   5. Re: Threads, moses, and expensive features (Lane Schwartz)


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

Message: 1
Date: Wed, 31 Mar 2010 11:25:34 +0100
From: Hieu Hoang <[email protected]>
Subject: Re: [Moses-support] MOSES Server installation: compilation
    error
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"

i've just compiled from a clean download (and a clean svn up) and it's 
built everything in 1 go.

there may be strange side effects if you do svn up of an existing 
project and make. My best guess is the new options to compile moses as a 
dynamic library is confusing the make process.

I would start the moses compile from the beginning:
    ./regenerate-makefiles.sh
   ./configure --with-srilm=/Users/hieu/Projects/srilm 
--with-irstlm=/Users/hieu/Projects/irstlm
   make -j 4


On 31/03/2010 11:03, Lee Ball (Applied Language) wrote:
> Not sure how relevant this is, but often when I've compiled Moses I've 
> had to dive into the src directory and run a make in there as well as 
> running it from the root directory for moses.
>
> Maybe navigate to /src and run a make separately?
> Kind regards,
>
> Lee Ball
> Infrastructure Manager
> [email protected] <mailto:[email protected]>
> Skype: lee.ball_appliedlanguage
> Tel: +44 (0)844 854 8945
>
> Applied Language Solutions
> High quality language solutions delivered on time
> ...with a smile!
>
> www.appliedlanguage.com <http://www.appliedlanguage.com>
> Tel (UK): +44 (0)845 367 7000
> Tel (US): +1 (800) 579-5010
>
> Riverside Court, Huddersfield Road, Delph, Oldham, OL3 5FZ. UK
> Registered in the UK 5122429
>
> Pride in everything we do | Respect everyone like a friend
> Think of the environment; please don't print this e-mail unless you 
> really need to.
> On 31 March 2010 11:00, Barry Haddow <[email protected] 
> <mailto:[email protected]>> wrote:
>
>     Hi Zahurul
>
>     It looks as though libmoses.a did not build - the server build is
>     unable to
>     find it. Could you check back through the build logs to see what
>     happened?
>
>     regards
>     Barry
>
>     On Wednesday 31 Mar 2010 10:42:30 Zahurul Islam wrote:
>     > Dear Barry,
>     > Thank you very much. Here is the command list, i executed in the
>     top level
>     > of moses directory:
>     >
>     > $./regenerate-makefiles.sh
>     > $./configure
>     --with-srilm=/project/piqasso/Experiments/MT/tools/srilm/
>     > -with-irstlm=/project/piqasso/Experiments/MT/tools/irstlm-5.22.01/
>     > --with-boost --enable-threads --with-xmlrpc-c
>     > $make
>     >
>     > boost and xmlrpmc-c are accessible in the PATH. Thats why, I did not
>     >  provide arguments. Two older revision of MOSES with server
>     feature are
>     >  installed in my machine. I am trying to upgrade to new
>     revision. Thanks
>     >  again.
>     >
>     > Regards,
>     > Zahurul
>     >
>     > On Wed, Mar 31, 2010 at 11:31 AM, Barry Haddow
>     <[email protected] <mailto:[email protected]>> wrote:
>     > > Hi Zahurul
>     > >
>     > > Did moses build correctly? Did you run make at the top level?
>     The server
>     > > build
>     > > is failing because it can't find the moses library.
>     > >
>     > >
>     > > Your configure line looks a little strange as the
>     --with-xmlrpmc-c flag
>     > > should
>     > > take an argument
>     > > eg. --with-xmlrpc-c=/disk3/bhaddow/xmlrpc-c/bin/xmlrpc-c-config
>     > >
>     > > regards
>     > > Barry
>     > >
>     > > On Wednesday 31 Mar 2010 10:08:51 Zahurul Islam wrote:
>     > > > Hi,
>     > > > I was trying to install new version of MOSES. I tried twice
>     by svn
>     > > > update and downloaded source from:
>     > > > https://sourceforge.net/projects/mosesdecoder/ . Both time i met
>     > >
>     > > following
>     > >
>     > > >  error:
>     > > >
>     > > > $Making all in server
>     > > > $make[2]: Entering directory
>     > > >
>     `/l/disc1/project/piqasso/Experiments/MT/tools/moses-march31/server'
>     > > > $g++ -DHAVE_CONFIG_H -I. -I..  -W -Wall -I../moses/src
>     -I/usr/include
>     > > >  -pthread -I/usr/include -DTRACE_ENABLE=1 -DWITH_THREADS
>     > > > -I/project/piqasso/Experiments/MT/tools/srilm//include
>     > > >
>     -I/project/piqasso/Experiments/MT/tools/irstlm-5.22.01//include
>      -g -O2
>     > >
>     > > -MT
>     > >
>     > > > mosesserver-mosesserver.o -MD -MP -MF
>     .deps/mosesserver-mosesserver.Tpo
>     > >
>     > > -c
>     > >
>     > > > -o mosesserver-mosesserver.o `test -f 'mosesserver.cpp' || echo
>     > > > './'`mosesserver.cpp
>     > > > $mv -f .deps/mosesserver-mosesserver.Tpo
>     > > > .deps/mosesserver-mosesserver.Po $make[2]: *** No rule to
>     make target
>     > > > `../moses/src/libmoses.a', needed by `mosesserver'.  Stop.
>     > > > $make[2]: Leaving directory
>     > > >
>     `/l/disc1/project/piqasso/Experiments/MT/tools/moses-march31/server'
>     > > > $make[1]: *** [all-recursive] Error 1
>     > > >
>     > > > My configuration command was:
>     > > > ./configure
>     --with-srilm=/project/piqasso/Experiments/MT/tools/srilm/
>     > > >
>     -with-irstlm=/project/piqasso/Experiments/MT/tools/irstlm-5.22.01/
>     > > > --with-boost --enable-threads --with-xmlrpc-c
>     > > >
>     > > > Regards,
>     > > > Zahurul
>     >
>
>     -------------------------------------------------------
>
>     _______________________________________________
>     Moses-support mailing list
>     [email protected] <mailto:[email protected]>
>     http://mailman.mit.edu/mailman/listinfo/moses-support
>
>
>
> _______________________________________________
> Moses-support mailing list
> [email protected]
> 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/20100331/79b2d2e0/attachment-0001.htm

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

Message: 2
Date: Wed, 31 Mar 2010 11:52:30 +0100
From: Barry Haddow <[email protected]>
Subject: Re: [Moses-support] MOSES Server installation: compilation
    error
To: Zahurul Islam <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: Text/Plain;  charset="utf-8"

On Wednesday 31 Mar 2010 11:12:28 Zahurul Islam wrote:
> Dear Barry,
> Where i can find build logs? I saw config.log in the top level moses
> directory which contains log of moses configuration.  Thanks,
> Zahurul
> 

Hi Zahurul

By 'build logs', I mean the output of running make at the top level. Running 
make at the top level should compile all the pieces of moses that you have 
configured. It does for me. There have been some recent changes to the build 
system which could have introduced errors, so it would be good to track them 
down.

Which platform are you working on?

regards
Barry



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

Message: 3
Date: Wed, 31 Mar 2010 13:52:21 +0200
From: Zahurul Islam <[email protected]>
Subject: Re: [Moses-support] MOSES Server installation: compilation
    error
To: Barry Haddow <[email protected]>
Cc: [email protected]
Message-ID:
    <[email protected]>
Content-Type: text/plain; charset="utf-8"

Dear Barry,

We use Ubuntu 9.10. The problem is solved now. I had to change the extension
of moses library file: "libmoses.a" to "libmoses.la" in the Makefile.am
(last line) in sever directory:

mosesserver_DEPENDENCIES = $(top_srcdir)/moses/src/libmoses.la

The moses library "libmoses.la" is being generated
in $(top_srcdir)/moses/src directory but mosesserver depends on
"libmoses.a", which was creating problem.

I did not face compilation errors when I compiled without moses-server
feature. Thank you very much.

Regards,
Zahurul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.mit.edu/mailman/private/moses-support/attachments/20100331/da30deb4/attachment-0001.htm

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

Message: 4
Date: Wed, 31 Mar 2010 13:04:53 +0100
From: Barry Haddow <[email protected]>
Subject: Re: [Moses-support] MOSES Server installation: compilation
    error
To: Zahurul Islam <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: Text/Plain;  charset="utf-8"

Hi Zahurul

Thanks for that. I've updated Makefile.am in svn as you suggested. The main 
build system for moses was changed recently, and the server makefile wasn't 
updated at that time. It still worked for me because I had an old libmoses.a 
in the directory,

regards
Barry

On Wednesday 31 Mar 2010 12:52:21 Zahurul Islam wrote:
> Dear Barry,
> 
> We use Ubuntu 9.10. The problem is solved now. I had to change the
>  extension of moses library file: "libmoses.a" to "libmoses.la" in the
>  Makefile.am (last line) in sever directory:
> 
> mosesserver_DEPENDENCIES = $(top_srcdir)/moses/src/libmoses.la
> 
> The moses library "libmoses.la" is being generated
> in $(top_srcdir)/moses/src directory but mosesserver depends on
> "libmoses.a", which was creating problem.
> 
> I did not face compilation errors when I compiled without moses-server
> feature. Thank you very much.
> 
> Regards,
> Zahurul
> 



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

Message: 5
Date: Wed, 31 Mar 2010 08:01:45 -0500
From: Lane Schwartz <[email protected]>
Subject: Re: [Moses-support] Threads, moses, and expensive features
To: Philipp Koehn <[email protected]>
Cc: moses-support <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii

Philipp & Barry,

Thanks for the info. At the moment, I'm treating my feature as only 
quasi-stateful. 

To calculate the feature function score, I need to have the previous state and 
the current word, which allows me to calculate the current state, from which I 
get the current feature function score. However, the domain of the state space 
is extremely large, rendering it extremely unlikely that any two states will be 
identical.

For this reason, I'm trying to treat the feature as stateless for the purposes 
of hypothesis recombination. I'm not sure if I've correctly implemented this.

In my feature's FFState implementation, I am currently always returning zero 
from the function virtual int Compare(const FFState& other) const;

Is that the correct way to ensure that for hypothesis recombination, this 
feature will not be taken into account?

Thanks,
Lane


On 30 Mar 2010, at 4:48 PM, Philipp Koehn wrote:

> Hi Lane,
> 
> multi-threading in Moses works the same: different sentences
> are distributed to different threads.
> 
> Adding stateful feature functions has two costs: one is the
> calculation of the function and one is the additional state splitting
> which hurts recombination is the beam search. The first cost
> is easy to measure, but the second one is more tricky - a different
> trade-off between search errors and speed has to be found.
> 
> -phi
> 
> On Tue, Mar 30, 2010 at 8:36 PM, Lane Schwartz <[email protected]> wrote:
>> Barry,
>> 
>> Hieu may have mentioned that I'm working on a (more or less) stateful new 
>> feature that uses an incremental parser as a syntactic language model.
>> 
>> In this feature, calculating the next state from a word and the previous 
>> state is not ridiculously expensive, but it certainly takes longer than most 
>> feature calculations.
>> 
>> I'm wondering what parts of the decoding process are sped up when 
>> multithreading is enabled. In Joshua, we handle this by simply giving each 
>> thread a different sentence to translate.
>> 
>> Thanks,
>> Lane
>> 
>> 
>> _______________________________________________
>> Moses-support mailing list
>> [email protected]
>> http://mailman.mit.edu/mailman/listinfo/moses-support
>> 




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

_______________________________________________
Moses-support mailing list
[email protected]
http://mailman.mit.edu/mailman/listinfo/moses-support


End of Moses-support Digest, Vol 41, Issue 40
*********************************************



      
_______________________________________________
Moses-support mailing list
[email protected]
http://mailman.mit.edu/mailman/listinfo/moses-support

Reply via email to