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. Fwd: Server development (Ulrich Germann)
----------------------------------------------------------------------
Message: 1
Date: Tue, 5 May 2015 16:38:36 +0100
From: Ulrich Germann <ulrich.germann@gmail.com>
Subject: [Moses-support] Fwd: Server development
To: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CAHQSRUop7A1t_t5jd3MoCuciN9SDq-A7z2z5jSjD6KXNhhwhyA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
This response was meant to go to moses-support as well Tomas.
---------- Forwarded message ----------
From: Tomas Fulajtar <TomasFu@moravia.com>
Date: Fri, Apr 3, 2015 at 5:03 PM
Subject: RE: [Moses-support] Server development
To: "ugermann@inf.ed.ac.uk" <ugermann@inf.ed.ac.uk>
Hi Ulrich,
Thanks for the thorough explanation - the idea of merging the server code
back to moses is great.
Apart from this (and I know is is a huge workload), were there any changes
in the thread support? I know this part had some limitations ? as
discussed on the forum.
Kind regards,
Tomas
*From:* Ulrich Germann [mailto:ulrich.germann@gmail.com]
*Sent:* Thursday, April 2, 2015 12:57 AM
*To:* Tomas Fulajtar
*Subject:* Re: [Moses-support] Server development
Hi Tomas,
the plan is to fold server capabilities into the main moses executable. In
fact, that has already happened (in the sense that you can run the main
moses executable in server mode), but functional equivalence with the old
code has not been tested.
There are currently no server tests included in the regression tests, so I
left the old code mostly intact (adjusting only for changes in the API of
functions called) for legacy reasons, but adding new functionality to
mosesserver is extremely strongly DIScouraged.
Supplying regression tests for server functionality, on the other hand, is
equally strongly ENcouraged. In a nutshell, what you get back from calling
mosesserver and moses --server should be identical.
The long-term plan is to offer through RPC calls (almost) everything that
moses offers in batch mode (i.e., send search and output parameters through
json/RCP calls and have them noticed and respected). Notice the "long-term"
there.
So mosesserver is on its way out, and moses --server-port=<port> --server
will replace the old call to mosesserver.
Best regards - Uli
On Wed, Apr 1, 2015 at 9:48 AM, Tomas Fulajtar <TomasFu@moravia.com> wrote:
Dear all,
I have spotted there were numerous commits in the server side development -
could the developers share the news/goals with the forum? I think it
might be interesting for more users ? especially those out of core team.
Thank you,
*Tom?? Fulajt?r* | Researcher
*T:* +420-545-552-340
tomasfu@moravia.com | moravia.com <http://www.moravia.com/> | *Skype:*
tomasfulajtar
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support
--
Ulrich Germann
Senior Researcher
School of Informatics
University of Edinburgh
--
Ulrich Germann
Senior Researcher
School of Informatics
University of Edinburgh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20150505/bd2bf506/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 103, Issue 13
**********************************************
Subscribe to:
Post Comments (Atom)
0 Response to "Moses-support Digest, Vol 103, Issue 13"
Post a Comment