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. problem in generating phrase table after tuning (Apurva Joshi)
2. Re: use placeholder with mosesserver (Evgeny Matusov)
3. Re: use placeholder with mosesserver (Vito Mandorino)
----------------------------------------------------------------------
Message: 1
Date: Tue, 17 Nov 2015 12:47:20 +0530
From: Apurva Joshi <apurvajoshi1992@gmail.com>
Subject: [Moses-support] problem in generating phrase table after
tuning
To: moses-support@mit.edu
Message-ID:
<CAMfCXbW6_1sR20Av-FvkHUzT4cLKZm4LnMDMo3XDuyzX-+tG6g@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
hello ,
initially i trained with corpora containing 7 lac sentnses...i trained
it..and its giving good translation...
then for tuning i took new small size corpora containing 2k lines ....
now i run tuning with this new processed corpora as input along with my
moses.ini (generated after training) as input ....then mert-work folder is
generated with run6.moses.ini ....
along with this ,phrase table.gz and reordering table is also generated in
mert-work folder...
now problem is ....
1st problem :
before tuning , size of phrase table is 2.5Gb
after tuning , size of phrase table is 256.5Mb
2nd problem:
now while running moses, should i use moses.ini(in mert-work/filtered
folder) OR moses.ini(run6.moses.ini) ...?
i ran moses using both above mentioned moses.ini....
from both m not getting proper o/p...
eg
ip = hello
op =
*BEST TRANSLATION: hello|UNK|UNK|UNK *
before tuning , it was giving me correct translation of hello i.e
op= ?????? (hindi translation of hello)....
so whether is it taking memory problem or what ?? plzz help...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20151117/55753796/attachment-0001.html
------------------------------
Message: 2
Date: Tue, 17 Nov 2015 14:43:16 +0000
From: Evgeny Matusov <ematusov@apptek.com>
Subject: Re: [Moses-support] use placeholder with mosesserver
To: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<SN1PR08MB2000DD5191150E1E13D9D6EAAC1D0@SN1PR08MB2000.namprd08.prod.outlook.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi active Moses developers,
As promised, I am working on adding the correct placeholder output to Moses in the server mode. Currently, passing the n-best size through xmlrpc is commented out. Any reason why this is the case? It might be convenient to run server queries with/without N-best output and with different N-best sizes without having to restart the server (currently, this is the only way to do it).
If there are no objections, I will put this parameter back into the code.
Best,
Evgeny.
________________________________
From: Evgeny Matusov
Sent: Wednesday, November 11, 2015 10:30 AM
To: ugermann@inf.ed.ac.uk
Cc: moses-support@mit.edu
Subject: Re: [Moses-support] use placeholder with mosesserver
Hi Uli,
thanks a lot! We will try to add some test cases for Mosesserver, including XML input with/without placeholders.
Best,
Evgeny.
________________________________
From: Ulrich Germann <ulrich.germann@gmail.com>
Sent: Wednesday, November 11, 2015 2:58 AM
To: Evgeny Matusov
Cc: moses-support@mit.edu
Subject: Re: [Moses-support] use placeholder with mosesserver
Hi all,
I've just pushed what I believe might address a few of the issues in this thread:
- the more fine-grained configuration options for request handling and queuing, server timeouts etc. (added in August due to threading issue) have been transferred to the main moses executable.
- the server now pays attention to the xml-input option specified via json; the range of accepted values is the same as when specified on the command line. I have not written the xml-input handling and do not actively use it, so it may or may not work. I don't think there are any regression tests that test this right now. Reports from the trenches are welcome.
- mosesserver.cpp is deprecated. It is now merely a shell around the regular moses call with --server. I did not remove it from the code base entirely, as I assume that there's a plethora of setups out there that rely on the existence of mosesserver. What the wrapper does is add --server to the options and then call run regular moses.
- anyone adding stuff to mosesserver.cpp from now on owes me a lifetime supply of the finest Laphroaig. Just send me a quarter cask every year for Burns Nicht for the rest of my life if you do. If I haven't pushed anything for two years, you may assume I'm dead.
- Uli
On Tue, Nov 10, 2015 at 2:58 PM, Ulrich Germann <ulrich.germann@gmail.com<mailto:ulrich.germann@gmail.com>> wrote:
Hi all,
mosesserver is deprecated and should not be used any more. I'll transfer the threading-related changes to the server implementation in the regular moses executable and let you know once I'm done so that other things (like passthrough) can be added. By the looks of it, the changes are fairly straightforward, so it shouldn't take long. However, I can't guarantee that the new server will do everything the old server did, (or do it the same way).
It would be fantastic if a few people could design and contribute test cases so that we can do some regression testing for the server. Ideally a test case should provide:
- tiny models to work with (or we may be able to recycle some that already exist)
- sample input (json)
- expected output (json)
Cheers - Uli
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20151117/076454bb/attachment-0001.html
------------------------------
Message: 3
Date: Tue, 17 Nov 2015 17:53:25 +0100
From: Vito Mandorino <vito.mandorino@linguacustodia.com>
Subject: Re: [Moses-support] use placeholder with mosesserver
To: undisclosed-recipients:;
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CA+8mSmGasRJXfa45v_3xdQUefapTix9Uurdsm1Wx7upz_-RrTw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
thanks for the fixes and modifications. Actually we have compiled the Moses
taken from the master branch but get an error with mosesserver. More
precisely,
/mosesdecoder/bin/moses -f moses.ini
works fine, but both commands
/mosesdecoder/bin/mosesserver -f moses.ini --server-port 8080
/mosesdecoder/bin/moses --server -f moses.ini --server-port 8080
give a Segmentation Fault error. More details are in the attached log.txt
file.
What could have possibly gone wrong ?
Vito
2015-11-17 15:43 GMT+01:00 Evgeny Matusov <ematusov@apptek.com>:
> Hi active Moses developers,
>
>
> As promised, I am working on adding the correct placeholder output to
> Moses in the server mode. Currently, passing the n-best size through xmlrpc
> is commented out. Any reason why this is the case? It might be convenient
> to run server queries with/without N-best output and with different N-best
> sizes without having to restart the server (currently, this is the only way
> to do it).
>
>
> If there are no objections, I will put this parameter back into the code.
>
>
> Best,
>
> Evgeny.
>
>
> ------------------------------
> *From:* Evgeny Matusov
> *Sent:* Wednesday, November 11, 2015 10:30 AM
> *To:* ugermann@inf.ed.ac.uk
>
> *Cc:* moses-support@mit.edu
> *Subject:* Re: [Moses-support] use placeholder with mosesserver
>
>
> Hi Uli,
>
>
> thanks a lot! We will try to add some test cases for Mosesserver,
> including XML input with/without placeholders.
>
>
> Best,
>
> Evgeny.
>
>
> ------------------------------
> *From:* Ulrich Germann <ulrich.germann@gmail.com>
> *Sent:* Wednesday, November 11, 2015 2:58 AM
> *To:* Evgeny Matusov
> *Cc:* moses-support@mit.edu
> *Subject:* Re: [Moses-support] use placeholder with mosesserver
>
> Hi all,
>
> I've just pushed what I believe might address a few of the issues in this
> thread:
>
> - the more fine-grained configuration options for request handling and
> queuing, server timeouts etc. (added in August due to threading issue) have
> been transferred to the main moses executable.
>
> - the server now pays attention to the xml-input option specified via
> json; the range of accepted values is the same as when specified on the
> command line. I have not written the xml-input handling and do not actively
> use it, so it may or may not work. I don't think there are any regression
> tests that test this right now. Reports from the trenches are welcome.
>
> - mosesserver.cpp is deprecated. It is now merely a shell around the
> regular moses call with --server. I did not remove it from the code base
> entirely, as I assume that there's a plethora of setups out there that rely
> on the existence of mosesserver. What the wrapper does is add --server to
> the options and then call run regular moses.
>
> - anyone adding stuff to mosesserver.cpp from now on owes me a lifetime
> supply of the finest Laphroaig. Just send me a quarter cask every year for
> Burns Nicht for the rest of my life if you do. If I haven't pushed anything
> for two years, you may assume I'm dead.
>
>
> - Uli
>
> On Tue, Nov 10, 2015 at 2:58 PM, Ulrich Germann <ulrich.germann@gmail.com>
> wrote:
>
>> Hi all,
>>
>> mosesserver is deprecated and should not be used any more. I'll transfer
>> the threading-related changes to the server implementation in the regular
>> moses executable and let you know once I'm done so that other things (like
>> passthrough) can be added. By the looks of it, the changes are fairly
>> straightforward, so it shouldn't take long. However, I can't guarantee that
>> the new server will do everything the old server did, (or do it the same
>> way).
>>
>> It would be fantastic if a few people could design and contribute test
>> cases so that we can do some regression testing for the server. Ideally a
>> test case should provide:
>>
>> - tiny models to work with (or we may be able to recycle some that
>> already exist)
>> - sample input (json)
>> - expected output (json)
>>
>> Cheers - Uli
>>
>>
>>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
>
--
*M**. Vito MANDORINO -- Chief Scientist*
[image: Description : Description : lingua_custodia_final full logo]
*The Translation Trustee*
*1, Place Charles de Gaulle, **78180 Montigny-le-Bretonneux*
*Tel : +33 1 30 44 04 23 Mobile : +33 6 84 65 68 89*
*Email :* *vito.mandorino@linguacustodia.com
<massinissa.ahmim@linguacustodia.com>*
*Website :* *www.linguacustodia.com <http://www.linguacustodia.com/> -
www.thetranslationtrustee.com <http://www.thetranslationtrustee.com/>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20151117/53ae4812/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 4421 bytes
Desc: not available
Url : http://mailman.mit.edu/mailman/private/moses-support/attachments/20151117/53ae4812/attachment.jpg
------------------------------
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support
End of Moses-support Digest, Vol 109, Issue 35
**********************************************
Subscribe to:
Post Comments (Atom)
0 Response to "Moses-support Digest, Vol 109, Issue 35"
Post a Comment