I don't know which limitations Tomas is referring to, but when was the last time you've used multi-threaded moses with IRSTLM?
- Uli On Tue, May 5, 2015 at 6:27 PM, Hieu Hoang <[email protected]> wrote: > What limitations are you referring to? > ---------- Forwarded message ---------- > From: "Ulrich Germann" <[email protected]> > Date: 5 May 2015 19:49 > Subject: [Moses-support] Fwd: Server development > To: "[email protected]" <[email protected]> > Cc: > > This response was meant to go to moses-support as well Tomas. > > ---------- Forwarded message ---------- > From: Tomas Fulajtar <[email protected]> > Date: Fri, Apr 3, 2015 at 5:03 PM > Subject: RE: [Moses-support] Server development > To: "[email protected]" <[email protected]> > > > 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:[email protected]] > *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 <[email protected]> > 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 > [email protected] | moravia.com <http://www.moravia.com/> | *Skype:* > tomasfulajtar > > > > > _______________________________________________ > Moses-support mailing list > [email protected] > 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 > [email protected] > http://mailman.mit.edu/mailman/listinfo/moses-support > > > _______________________________________________ > Moses-support mailing list > [email protected] > http://mailman.mit.edu/mailman/listinfo/moses-support > > -- Ulrich Germann Senior Researcher School of Informatics University of Edinburgh
_______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
