Moses-support Digest, Vol 111, Issue 23

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: Which symal? (Tom Hoar)
2. kbmira died with SIGABRT when tuning (Dingyuan Wang)
3. Re: Error when running moses server with sample code
(Barry Haddow)
4. Re: Which symal? (Ergun Bicici)


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

Message: 1
Date: Tue, 12 Jan 2016 09:09:44 +0700
From: Tom Hoar <tahoar@precisiontranslationtools.com>
Subject: Re: [Moses-support] Which symal?
To: moses-support@mit.edu
Message-ID: <56946068.9020405@precisiontranslationtools.com>
Content-Type: text/plain; charset=windows-1252; format=flowed

Don't have experience with EMS, but our Slate packages (Linux & Windows)
include both MGIZA and Moses binaries the same `$bin` folder and we set
the train-model.perl --external-bin-dir=$bin value and all other binary
path references to that one folder. The symal binary is the only
conflict file name. So, we use the one from Moses. From what we could
tell, they are essentially the same source but the Moses copy seems to
have been maintained/updated more recently. Also be careful because the
two versions are published under different open source licenses.

I don't know if this approach will work with EMS, but it is a simple
solution.

Tom


On 1/12/2016 3:56 AM, moses-support-request@mit.edu wrote:
> Date: Mon, 11 Jan 2016 20:56:49 +0000
> From: Hieu Hoang<hieuhoang@gmail.com>
> Subject: Re: [Moses-support] Which symal?
> To: Ergun Bicici<ergun.bicici@dfki.de>
> Cc: moses-support<moses-support@mit.edu>
>
> I'm not sure if the bjam argument
> --with-giza
> is actually used during compilation. Where did you see this mention? The
> bad thing about bjam is it doesn't tell you if an argument is invalid,
> it simply ignores it.
>
> It would be nice to have 1 directory for all your MT tools. If you wanna
> make it happen, be my guest.
>
> I suppose we should be mindful of people who use mgiza but don't use
> Moses, they'll still need symal so we can't just delete it from mgiza.



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

Message: 2
Date: Tue, 12 Jan 2016 12:00:54 +0800
From: Dingyuan Wang <abcdoyle888@gmail.com>
Subject: [Moses-support] kbmira died with SIGABRT when tuning
To: moses-support@mit.edu
Message-ID: <56947A76.8090502@gmail.com>
Content-Type: text/plain; charset=utf-8

Hi all,

I'm using EMS for doing experiments. Every time the kbmira died with
SIGABRT when turning on one direction, while tuning on the opposite
direction (same config and test set) was successful.

The mert.log (stderr) shows follows:


kbmira with c=0.01 decay=0.999 no_shuffle=0
Initialising random seed from system clock
Found 15323 initial sparse features
....terminate called after throwing an instance of
'MosesTuning::FileFormatException'
what(): Error in line "-4.51933 0 0 -6.09733 0 0 0 -121.556 2 -20 12
-31.6201 -38.5211 -26.5112 -60.6166 WT_?~?=2 WT_?~?=1 PL_s1=4
PL_s3=1 PL_3,3=1 PL_2,2=3 PL_1,2=1 PL_2,1=3 PL_t1=6 PL_t2=4 PL_t3=2
PL_2,3=1 PL_s2=7 PL_1,1=3 WT_?~??=1 WT_?~??=1 WT_?~?=1 WT_?~?
?=1 WT_?~?=1 WT_?~?=2 WT_?~?=1 WT_?~?=1 WT_?~??=1 WT_?~?=1
WT_?~??=1 WT_?~?=1 WT_?~??=1 WT_?~??=1 WT_?~??=1 WT_?~
?=1 WT_?~??=1 " of run7.features.dat
Aborted


I think since run7.scores.dat is generated by some scripts, I wouldn't
be responsible for making the bad format. Last time it also died, I
removed the likely offending line in the test set, but this time another
line appears.

--
Dingyuan Wang


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

Message: 3
Date: Tue, 12 Jan 2016 09:16:12 +0000
From: Barry Haddow <bhaddow@staffmail.ed.ac.uk>
Subject: Re: [Moses-support] Error when running moses server with
sample code
To: Lane Schwartz <dowobeha@gmail.com>, "moses-support@mit.edu"
<moses-support@mit.edu>
Message-ID: <5694C45C.5090408@staffmail.ed.ac.uk>
Content-Type: text/plain; charset="windows-1252"

Hi Lane

Can you get a stack trace to see which line the message is coming from?
That error message is repeated in a few files.

From looking at the code, I'd guess that the OutputFactorOrder is not
being initialised correctly. Possibly due to the refactoring of the
config code. Does your example work with an earlier version of Moses?

cheers - Barry

On 11/01/16 21:43, Lane Schwartz wrote:
> Hi,
>
> I'm trying out mosesserver for the first time. I have a config file
> for fr-en that uses a smallish TM and LM, that work fine when run with
> Moses. When I try running the same config using mosesserver, and then
> use the sample Perl or Python code in contrib/server, mosesserver dies
> with the following error:
>
> Defined parameters (per moses.ini or switch):
> config: moses.tuned.ini.2.probing.noLexRO
> cube-pruning-pop-limit: 400
> distortion-limit: 6
> feature: UnknownWordPenalty WordPenalty PhrasePenalty ProbingPT
> name=TranslationModel0 num-features=4
> path=phrase-table.2.pruned100.probing/ input-factor=0
> output-factor=0 table-limit=20 Distortion KENLM lazyken=1 name=LM0
> factor=0 path=europarl.kenlm order=5
> input-factors: 0
> mapping: 0 T 0
> max-phrase-length: 20
> n-best-list: nbest.txt 111
> output-hypo-score: 1
> search-algorithm: 0
> server:
> threads: 1
> weight: Distortion0= 0.0222366 LM0= 0.0834208 WordPenalty0=
> -0.0654626 PhrasePenalty0= 0.0220686 TranslationModel0= 0.0520176
> 0.0415173 0.124293 0.027126 UnknownWordPenalty0= 1
>
> line=UnknownWordPenalty
> FeatureFunction: UnknownWordPenalty0 start: 0 end: 0
> line=WordPenalty
> FeatureFunction: WordPenalty0 start: 1 end: 1
> line=PhrasePenalty
> FeatureFunction: PhrasePenalty0 start: 2 end: 2
> line=ProbingPT name=TranslationModel0 num-features=4
> path=phrase-table.2.pruned100.probing/ input-factor=0
> output-factor=0 table-limit=20
> FeatureFunction: TranslationModel0 start: 3 end: 6
> line=Distortion
> FeatureFunction: Distortion0 start: 7 end: 7
> line=KENLM lazyken=1 name=LM0 factor=0 path=europarl.kenlm order=5
> FeatureFunction: LM0 start: 8 end: 8
> Loading UnknownWordPenalty0
> Loading WordPenalty0
> Loading PhrasePenalty0
> Loading Distortion0
> Loading LM0
> Loading TranslationModel0
> Initialized successfully!
>
> RUN SERVER at pid 1733327039
> [moses/server/Server.cpp:49] Listening on port 8080
> [moses/server/TranslationRequest.cpp:281] Input: il a souhait? que
> la pr?sidence trace ? nice le chemin pour l' avenir .
> Translating: il a souhait? que la pr?sidence trace ? nice le
> chemin pour l' avenir .
>
> Line 0: Collecting options took 0.038 seconds at moses/Manager.cpp
> Line 141
> Line 0: Search took 0.674 seconds
> terminate called after throwing an instance of 'util::Exception'
> what(): No factor 1 at position 0
>
>
> Any idea what's going on here? I'm using a basic single-factor model,
> so I don't get why it would be complaining about factors. I'm using
> the latest moses from git.
>
> Thanks,
> Lane
>
>
> _______________________________________________
> 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/20160112/472e647f/attachment-0001.html
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: not available
Url: http://mailman.mit.edu/mailman/private/moses-support/attachments/20160112/472e647f/attachment-0001.pl

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

Message: 4
Date: Tue, 12 Jan 2016 11:01:03 +0100
From: Ergun Bicici <ergun.bicici@dfki.de>
Subject: Re: [Moses-support] Which symal?
To: moses-support <moses-support@mit.edu>
Message-ID:
<CAB2pGnfss3HY_PeEKUTCXuV839xpcAM-DLG5BR-jiNPv9yEcbA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

So, you can sublicense Moses (LGPL) but not mgiza (GPL):
http://choosealicense.com/licenses/
??
?Which
I guess may m?ean something like that you can re-license a modified
version of Moses without symal but not with symal. ?In other words, to
license a modified version of? Moses with your own terms, you need to take
out symal from mgiza or any GPL or code having some more restrictive
license and keep symal that comes with Moses.


*Best Regards,*
Ergun

Ergun Bi?ici
DFKI Projektb?ro Berlin


On Tue, Jan 12, 2016 at 3:09 AM, Tom Hoar <
tahoar@precisiontranslationtools.com> wrote:

> Don't have experience with EMS, but our Slate packages (Linux & Windows)
> include both MGIZA and Moses binaries the same `$bin` folder and we set
> the train-model.perl --external-bin-dir=$bin value and all other binary
> path references to that one folder. The symal binary is the only
> conflict file name. So, we use the one from Moses. From what we could
> tell, they are essentially the same source but the Moses copy seems to
> have been maintained/updated more recently. Also be careful because the
> two versions are published under different open source licenses.
>
> I don't know if this approach will work with EMS, but it is a simple
> solution.
>
> Tom
>
>
> On 1/12/2016 3:56 AM, moses-support-request@mit.edu wrote:
> > Date: Mon, 11 Jan 2016 20:56:49 +0000
> > From: Hieu Hoang<hieuhoang@gmail.com>
> > Subject: Re: [Moses-support] Which symal?
> > To: Ergun Bicici<ergun.bicici@dfki.de>
> > Cc: moses-support<moses-support@mit.edu>
> >
> > I'm not sure if the bjam argument
> > --with-giza
> > is actually used during compilation. Where did you see this mention? The
> > bad thing about bjam is it doesn't tell you if an argument is invalid,
> > it simply ignores it.
> >
> > It would be nice to have 1 directory for all your MT tools. If you wanna
> > make it happen, be my guest.
> >
> > I suppose we should be mindful of people who use mgiza but don't use
> > Moses, they'll still need symal so we can't just delete it from mgiza.
>
> _______________________________________________
> 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/20160112/2eb3ce36/attachment.html

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

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


End of Moses-support Digest, Vol 111, Issue 23
**********************************************

Related Posts :

0 Response to "Moses-support Digest, Vol 111, Issue 23"

Post a Comment