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: Fwd: Server development (Hieu Hoang)
2. Re: Fwd: Fwd: Server development (Barry Haddow)
----------------------------------------------------------------------
Message: 1
Date: Tue, 5 May 2015 21:27:17 +0400
From: Hieu Hoang <hieuhoang@gmail.com>
Subject: [Moses-support] Fwd: Fwd: Server development
To: moses-support <moses-support@mit.edu>
Message-ID:
<CAEKMkbi_qnKoGG8vD+-y+1DDsncWNpX9hbUmg+um6bugubwxcg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
What limitations are you referring to?
---------- Forwarded message ----------
From: "Ulrich Germann" <ulrich.germann@gmail.com>
Date: 5 May 2015 19:49
Subject: [Moses-support] Fwd: Server development
To: "moses-support@mit.edu" <moses-support@mit.edu>
Cc:
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
_______________________________________________
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/20150505/564c0e20/attachment-0001.htm
------------------------------
Message: 2
Date: Tue, 05 May 2015 20:26:55 +0100
From: Barry Haddow <bhaddow@inf.ed.ac.uk>
Subject: Re: [Moses-support] Fwd: Fwd: Server development
To: Hieu Hoang <hieuhoang@gmail.com>, moses-support
<moses-support@mit.edu>
Message-ID: <5549197F.1050603@inf.ed.ac.uk>
Content-Type: text/plain; charset="iso-8859-1"
HI Tomas
There were some issues in v2 with the way that caching was done in the
binarised phrase table. It used a cache per thread, and mosesserver used
a thread per request, so caching was effectively broken in the server.
Since last Autumn, mosesserver uses a thread pool ... and the binarised
phrase table is gone now anyway,
cheers - Barry
On 05/05/15 18:27, Hieu Hoang wrote:
>
> What limitations are you referring to?
>
> ---------- Forwarded message ----------
> From: "Ulrich Germann" <ulrich.germann@gmail.com
> <mailto:ulrich.germann@gmail.com>>
> Date: 5 May 2015 19:49
> Subject: [Moses-support] Fwd: Server development
> To: "moses-support@mit.edu <mailto:moses-support@mit.edu>"
> <moses-support@mit.edu <mailto:moses-support@mit.edu>>
> Cc:
>
> This response was meant to go to moses-support as well Tomas.
>
> ---------- Forwarded message ----------
> From: *Tomas Fulajtar* <TomasFu@moravia.com <mailto:TomasFu@moravia.com>>
> Date: Fri, Apr 3, 2015 at 5:03 PM
> Subject: RE: [Moses-support] Server development
> To: "ugermann@inf.ed.ac.uk <mailto:ugermann@inf.ed.ac.uk>"
> <ugermann@inf.ed.ac.uk <mailto: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
> <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
> <mailto: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?s( Fulajt?r*|Researcher
> *T:* +420-545-552-340 <tel:%2B420-545-552-340>
> tomasfu@moravia.com <mailto:tomasfu@moravia.com>|moravia.com
> <http://www.moravia.com/>|*Skype:*tomasfulajtar
>
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu <mailto: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
>
> _______________________________________________
> 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
> 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/20150505/28f5c5d9/attachment.htm
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: not available
Url: http://mailman.mit.edu/mailman/private/moses-support/attachments/20150505/28f5c5d9/attachment.bat
------------------------------
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support
End of Moses-support Digest, Vol 103, Issue 14
**********************************************
Subscribe to:
Post Comments (Atom)
0 Response to "Moses-support Digest, Vol 103, Issue 14"
Post a Comment