Moses-support Digest, Vol 100, Issue 17

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: equal sign (=) in LM path (Tom Hoar)
2. Sparse feature error (jian zhang)


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

Message: 1
Date: Wed, 04 Feb 2015 21:29:02 +0700
From: Tom Hoar <tahoar@precisiontranslationtools.com>
Subject: Re: [Moses-support] equal sign (=) in LM path
To: undisclosed-recipients:;
Cc: moses-support <moses-support@mit.edu>
Message-ID: <54D22CAE.3040807@precisiontranslationtools.com>
Content-Type: text/plain; charset="utf-8"

Got it, built and tested. It's working fine. Thanks, Hieu.


On 02/04/2015 07:05 PM, Hieu Hoang wrote:
> it's fixed in master, but not in the release.
> https://github.com/moses-smt/mosesdecoder/commit/ee881734fe2d9176e001b1c92a71a51d61183697
> I'm not gonna put it into the release 'cos its too late. And the fix
> itself had to be fix!
>
> Hieu Hoang
> Research Associate (until March 2015)
> ** searching for interesting commercial MT position **
> University of Edinburgh
> http://www.hoang.co.uk/hieu
>
>
> On 4 February 2015 at 11:57, Tom Hoar
> <tahoar@precisiontranslationtools.com
> <mailto:tahoar@precisiontranslationtools.com>> wrote:
>
> Using R-3 and I got the same equal sign exception as below. I
> attached two moses.ini/moses.log file sets. The first example
> successfully loads the phrase & reordering tables with paths with
> equal signs. and a KENLM path without an equal sign.
>
> The second example fails to load after simply changing the KENLM
> path to a location with an equal sign.
>
> So Hieu, your comment "I think it's fixed" looks true for the
> phrase/reordering references, but not true for the LM references.
>
> Tom
>
>
>
> On 02/04/2015 01:54 PM, Lisa Kim wrote:
>>
>>
>> Thank you.
>> It is successful to change the LM name without "=" symbol.
>>
>> However, decoding still fails with following message.
>> Could you check the error message?
>>
>> --------------------
>> Start loading text phrase table. Moses format : [0.038] seconds
>> terminate called recursively
>> terminate called after throwing an instance of 'util::Exception'
>> what(): Aborted (core dumped)
>> Exit code: 134
>> The decoder died. CONFIG WAS -weight-overwrite 'LM1= 0.125000
>> PhrasePenalty0= 0.050000 WordPenalty0= -0.250000
>> TranslationModel0= 0.050000 0.050000 0.050000 0.050000
>> TranslationModel1= 0.250000 LM0= 0.125000'
>>
>> 2015. 2. 3. ?? 8:12? "Hieu Hoang" <hieuhoang@gmail.com
>> <mailto:hieuhoang@gmail.com>> ?? ??:
>>
>> as ken mentioned, don't use the = sign in the name of your LM
>> file. I think it's fixed in the latest version of moses.
>> Which version do you have, from when ago?
>>
>> moses_chart should handle factors. Again, if you version is
>> from long ago, I suggest your update
>>
>> On 02/02/15 10:06, ekkim214 wrote:
>>>
>>> I want to use some factor (class) in the hierarchical model.
>>> I am using the ems script and using KenLM for surface and
>>> factor both.
>>> The building of LM is successful with settings
>>> "-discount_fallback" but
>>> I got an error during tuning phase like this.
>>>
>>> Exception: moses/LM/Ken.cpp:399 in Moses::LanguageModel*
>>> Moses::ConstructKenLM(const string&) threw util::Exception
>>> because `args.size() != 2'.
>>> Incorrect format of KenLM property:
>>> path=/home3/ekkim/working/E2K_1501/hierarchical_class/lm/travel22=mkcls.binlm.5
>>> Exit code: 1
>>>
>>> Does not "moses_chart" decoder which is distributed in the
>>> package support factored training?
>>>
>>>
>>> _______________________________________________
>>> Moses-support mailing list
>>> Moses-support@mit.edu <mailto:Moses-support@mit.edu>
>>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>
>>
>>
>> _______________________________________________
>> Moses-support mailing list
>> Moses-support@mit.edu <mailto:Moses-support@mit.edu>
>> http://mailman.mit.edu/mailman/listinfo/moses-support
>
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu <mailto: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/20150204/e6af9de9/attachment-0001.htm

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

Message: 2
Date: Thu, 5 Feb 2015 00:32:25 +0800
From: jian zhang <zhangj@computing.dcu.ie>
Subject: [Moses-support] Sparse feature error
To: moses-support@mit.edu
Message-ID:
<CALA=z0CAb75c0pCzjjZdq=t9P1Xc8MXX+CVijMXZCF1t767YUw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi all,

My tuning with sparse features throws an error like:

kbmira with c=0.01 decay=0.999 no_shuffle=0
Initialising random seed to 4000
Found 829 initial sparse features
.terminate called after throwing an instance of
'MosesTuning::FileFormatException'
what(): Error in line "-0.897812 0 0 0 -0.956697 0 0 0 0 -27.6047 2 1 -6
3 -3.99712 -6.39143 -11.4808 -11.4945 PL_s1=2 PL_1,2=2 PL_t2=3 PL_2,2=1
PL_s2=1 WT_?~.=1 WT_OTHER~the=1 TWI_OTHER=1 " of run4.features.dat

Could you please check it, thanks. (I am using Moses 2.0)

Thanks,

Jian
--
Jian Zhang
Centre for Next Generation Localisation (CNGL)
<http://www.cngl.ie/index.html>
Dublin City University <http://www.dcu.ie/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20150205/8cb3eab6/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 100, Issue 17
**********************************************

Tweet