Moses-support Digest, Vol 97, Issue 97

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 error (iamzcy_hit iamzcy_hit)
2. sentence is always too short for cleaning step !!! (emna hkiri)
3. Re: -target-word-insertion-feature (Prashant Mathur)


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

Message: 1
Date: Fri, 28 Nov 2014 16:56:59 +0800
From: iamzcy_hit iamzcy_hit <iamzcyhit@gmail.com>
Subject: Re: [Moses-support] bjam error
To: Raj Dabre <prajdabre@gmail.com>
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CAGLowvJauy_4N3NwtzuC4tShuaKO-Cg9O5M4YS7C-zfo-R7QCw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi,all
I I modified the sanity.jam as follows,
---------------------------------
constant BOOST-VERSION : [ MATCH "#define BOOST_VERSION ([0-9]*)" :
$(boost-shell[1]) ] ;
-->
constant BOOST-VERSION : [ MATCH "#define BOOST_VERSION ([0-9]*)" :
"#define BOOST_VERSION 105500" ] ;

boost-lib-version = [ MATCH "#define BOOST_LIB_VERSION \"([^\"]*)\"" :
$(boost-shell[1]) ]
-->
boost-lib-version = [ MATCH "#define BOOST_LIB_VERSION \"([^\"]*)\"" :
"#define BOOST_LIB_VERSION \"1_55\"" ] ;
----------------------------------
And success!
But I still don't know why?

2014-11-28 16:01 GMT+08:00 iamzcy_hit iamzcy_hit <iamzcyhit@gmail.com>:

> Thanks for your reply.
> I tired your suggestions, however ,the error is still the same
>
> 2014-11-28 14:40 GMT+08:00 Raj Dabre <prajdabre@gmail.com>:
>
>> Hey,
>>
>> Have you tried downloading and installing boost as a standalone:
>>
>> wget http://downloads.sourceforge.net/project/boost/boost/1.55.0/boost_1_55_0.tar.gz?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fboost%2Ffiles%2Fboost%2F1.55.0%2F&ts=1389613041&use_mirror=kent
>> tar zxvf boost_1_55_0.tar.gz
>> cd boost_1_55_0/
>> ./bootstrap.sh
>> ./b2 -j8 --prefix=$PWD --libdir=$PWD/lib64 --layout=system link=static install || echo FAILURE
>>
>> And then do:
>> ./bjam -j8 --with-boost=<path to boost installation which contains the folder lib64>
>>
>> This should work.
>>
>>
>>
>>
>> On Fri, Nov 28, 2014 at 3:31 PM, iamzcy_hit iamzcy_hit <
>> iamzcyhit@gmail.com> wrote:
>>
>>> hi,all
>>> I just downloaded the latest Moses source code from github and tried to
>>> install it. After running ?./bjam ?j8?, I got the error messages as follows:
>>> -----------------------------------
>>> [cyzhang@mit108 mosesdecoder-master]$ ./bjam -j8
>>> /home/cyzhang/Moses/mosesdecoder-master/jam-files/sanity.jam:168: in
>>> boost
>>> *** argument error
>>> * rule constant ( name : value + )
>>> * called with: ( BOOST-VERSION : )
>>> * missing argument value
>>> /home/cyzhang/Moses/mosesdecoder-master/jam-files/boost-build/build/project.jam:1006:see
>>> definition of rule 'constant' being called
>>> Jamroot:81: in modules.load
>>> /home/cyzhang/Moses/mosesdecoder-master/jam-files/boost-build/build/project.jam:317:
>>> in load-jamfile
>>> /home/cyzhang/Moses/mosesdecoder-master/jam-files/boost-build/build/project.jam:62:
>>> in load
>>> /home/cyzhang/Moses/mosesdecoder-master/jam-files/boost-build/build/project.jam:168:
>>> in project.find
>>> /home/cyzhang/Moses/mosesdecoder-master/jam-files/boost-build/build-system.jam:570:
>>> in load
>>> ./jam-files/boost-build/kernel/modules.jam:283: in import
>>> ./jam-files/boost-build/kernel/bootstrap.jam:142: in boost-build
>>> ./jam-files/boost-build/boost-build.jam:8: in module scope
>>> -------------------------------------------------
>>> So I checked the sanity.jam and tried to debug it according the error
>>> hints. I found this line code
>>> ```
>>> 168: constant BOOST-VERSION : [ MATCH "#define BOOST_VERSION ([0-9]*)"
>>> : $(boost-shell[1]) ] ;
>>> ```
>>> was very strange. It seems that the BOOST-VERSION was not assigned any
>>> value according to error messages.
>>> However, I echo the ?boost-shell[1]? and got
>>> ```
>>> #define BOOST_VERSION_HPP
>>> #define BOOST_VERSION 105400
>>> #define BOOST_LIB_VERSION "1_54"
>>> 0
>>> ```
>>> It shows that my boost environment was right, and the "MATCH" command
>>> didn't match the value of BOOST-VERSION.
>>> So where should I change in order to install Moses?
>>> And what's the MATCH there? is it a function in JAM language?
>>> Best regards.
>>>
>>> --
>>> ???????????????.....
>>>
>>> _______________________________________________
>>> Moses-support mailing list
>>> Moses-support@mit.edu
>>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>>
>>>
>>
>>
>> --
>> Raj Dabre.
>> Research Student,
>> Graduate School of Informatics,
>> Kyoto University.
>> CSE MTech, IITB., 2011-2014
>>
>>
>
>
> --
> ???????????????.....
>



--
???????????????.....
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20141128/eb7e0159/attachment-0001.htm

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

Message: 2
Date: Fri, 28 Nov 2014 16:32:23 +0100
From: emna hkiri <emna.hkiri@gmail.com>
Subject: [Moses-support] sentence is always too short for cleaning
step !!!
To: moses-support@mit.edu
Message-ID:
<CAAp-nZ3KXJhsQApOXitfwxOgP_oOj9C4fVw7zhcH++zssu-U4w@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Dear friends
i need your help please
i have a problem of the cleaning phase of the arabic text
every time moses returns the message sentences number 1562783 is too
short!!!
(in fact it is the last sentence in the text) so i delete it and again and
again he tell me that this new last sentence is too short !!!!
and i do delete the last sentences and i have always the same problem

Can someone please throw some light on this.

Thanks & Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20141128/d39c83dd/attachment-0001.htm

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

Message: 3
Date: Fri, 28 Nov 2014 17:25:55 +0100
From: Prashant Mathur <prashant@fbk.eu>
Subject: Re: [Moses-support] -target-word-insertion-feature
To: Philipp Koehn <pkoehn@inf.ed.ac.uk>
Cc: moses-support <moses-support@mit.edu>
Message-ID:
<CAK3pNhKGoRz3HTepWnspdv76kUM=mX67eRGuzOGT06+NzyO3zQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

blast from the past!
Which paper should I cite if I use this feature?




On Fri, Apr 12, 2013 at 8:30 PM, Philipp Koehn <pkoehn@inf.ed.ac.uk> wrote:

> Hi,
>
> I wrote a little longer documentation of the sparse features:
> http://www.statmt.org/moses/?n=Moses.SparseFeatures
>
> -phi
>
> On Fri, Apr 12, 2013 at 6:12 PM, Philipp Koehn <pkoehn@inf.ed.ac.uk>
> wrote:
> > Hi Francis,
> >
> > thank you for your question - the documentation in this respect has
> > not caught up yet.
> >
> > Th target word insertion feature is a sparse feature, so it behaves a
> > bit different from the features that you are used to.
> >
> > What it is intended to do is to learn lexical features, one feature
> > for each word, which indicates if inserting the word in the output is
> > a good thing or not. The indication if a word has been inserted is
> > detected from the word alignment within each phrase pair. If the
> > target word is not aligned to any source word, then it is deemed to be
> > inserted.
> >
> > The options you have to specify is a factor number (typically 0 for
> > the surface form of the word), and optionally a file that contains a
> > restricted list of words. If such a file is present, then only target
> > words that are in the file (one word per line) are considered for the
> > feature. In other words: words that are not in the file may be
> > inserted or not, no feature calculation takes place.
> >
> > Sparse lexical features require a special weight file that contains
> > the weight for each instantiation of a feature. So this may look like
> > the following:
> > twi_I -0.00529196301346302
> > twi_had -4.16585913937328e-05
> > twi_was -0.00612071371830685
> > [...]
> >
> > Of course, you want to learn these feature weights during tuning,
> > which requires the use of either PRO or kbMIRA - it does not work with
> > plain MERT.
> >
> > The moses.ini that is used to run tuning must contain:
> >
> > [report-sparse-features]
> > twi
> >
> > in addition to the
> >
> > [target-word-insertion-feature]
> > 0 /path/to/word/list
> >
> > Let me know if this description helps you.
> >
> > -phi
> >
> > On Fri, Apr 5, 2013 at 2:23 PM, Francis Tyers <ftyers@prompsit.com>
> wrote:
> >> Hello everyone!
> >>
> >> I'm a bit interested in the -target-word-insertion-feature to Moses.
> The
> >> help output is as follows:
> >>
> >> -target-word-insertion-feature: Count feature for each unaligned target
> >> word
> >>
> >> I tried calling it without any options and it didn't seem to do
> >> anything, so I checked out the code and found a couple of hints:
> >>
> >> 1) in build-sparse-lexical-features.perl:
> >>
> >> [target-word-insertion-feature]
> >> 0 $file
> >>
> >> 2) in moses/StaticData.cpp:
> >>
> >> UserMessage::Add("Format of target word insertion feature parameter is:
> >> --target-word-insertion-feature <factor> [filename]");
> >>
> >> So, this would suggest that it requires a factor, and a filename is
> >> optional. The code instantiates a class TargetWordInsertionFeature.
> >>
> >> If we look at the TargetWordInsertionFeature, it seems to:
> >>
> >> * Load a file with a list of words if it exists
> >> * Make a boolean array of size 16 (I guess this is because of the limit
> >> on feature score length in ScoreComponentCollection)
> >> * For each word in the phrase it sets if it is aligned or not
> >> * If the word is unaligned it adds 1 to the score for that word
> >> feature.(?)
> >>
> >> ... this is where I get lost.
> >>
> >> Can anyone give a better description of what this option does, and how
> >> it effects the translation (if at all).
> >>
> >> My initial interest was in getting statistics on unaligned words that
> >> appeared in the output. Can this option give that ?
> >>
> >> Thanks in advance for any help!
> >>
> >> Fran
> >>
> >> _______________________________________________
> >> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20141128/2947b846/attachment.htm

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

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


End of Moses-support Digest, Vol 97, Issue 97
*********************************************

Tweet