Moses-support Digest, Vol 121, Issue 18

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: error in mosesdecoder tuning (Tom Hoar)
2. SLATE 2017 Call for Papers (Mikel L. Forcada)
3. Re: moses server options different for moses vs. moses2
(Hieu Hoang)


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

Message: 1
Date: Thu, 3 Nov 2016 00:05:54 +0700
From: Tom Hoar <tahoar@pttools.net>
Subject: Re: [Moses-support] error in mosesdecoder tuning
To: moses-support@mit.edu
Message-ID: <d2deb6b5-d11e-974d-905b-152a1abfbadc@pttools.net>
Content-Type: text/plain; charset="windows-1252"

Without a start-to-finish log file, it's impossible to debug. Based on
your description, however, I'd say you probably (a) ran out of free hard
drive space for temp files somewhere during step 2, or your very large
corpus has invalid character. Both will cause empty GIZA++ alignment
files and empty phrase tables.

Have you ever create a smaller model to validate your corpus preparation?



On 11/2/2016 10:32 PM, moses-support-request@mit.edu wrote:
> Date: Wed, 2 Nov 2016 17:32:48 +0200
> From: Hasan Sait ARSLAN<hasan.sait.arslan@gmail.com>
> Subject: Re: [Moses-support] error in mosesdecoder tuning
> To: Barry Haddow<bhaddow@staffmail.ed.ac.uk>
> Cc: moses-support<moses-support@mit.edu>
> Message-ID:
> <CAJj7HD3zd_r1ZjbYj0ikNNYauxe1KFA2MV4Ft1PfQ5vKtK=bSQ@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Barry,
>
> I have rerun training starting from step 5, and I kept log file. I have
> checked log file, and it doesn't show any bug about creating phrase-table,
> but phrase-table is still not being created. I am attaching log file, could
> you please check it, and show me where is the problem?
>
> Thanks,?
> log.gz
> <https://drive.google.com/file/d/0BxvJK3H5ZKsnYzJiZmhjUWI0Qlk/view?usp=drive_web>
> ?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20161102/8fcbf4ee/attachment-0001.html

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

Message: 2
Date: Wed, 2 Nov 2016 17:51:06 +0000
From: "Mikel L. Forcada" <mlf@dlsi.ua.es>
Subject: [Moses-support] SLATE 2017 Call for Papers
To: moses-support@mit.edu
Message-ID: <eadf46c1-49e5-a267-af5a-8d3f115e9a2e@dlsi.ua.es>
Content-Type: text/plain; charset="utf-8"



SLATE 2017 - Symposium on Languages, Applications and Technologies
(http://www.slate-conf.org) 26th - 27th June 2017
Media Arts and Design Superior School ? Polytechnic Institute of
Porto (Portugal)

Important dates:

Full papers * Paper Submission: March 5, 2017
* Paper Authors' Notification: April 23, 2017
* Final Paper Submission: May 21, 2017

Short Papers * Paper Submission: April 30, 2017
* Paper Authors' Notification: May 14, 2017
* Final Paper Submission: May 21, 2017

Other Dates * Accepted Paper's Author's Registration Deadline: May 31,
2017
* Conference: June 26 and 27, 2017


We often use languages. First, to communicate between ourselves. Later,
to communicate with computers. And more recently, with the advent of
networks, we found a way to make computers communicate between
themselves. All these different forms of communication use languages,
different languages, but that still share many similarities. In SLATE we
are interested in discussing these languages.
Being languages such a broad subject, SLATE is organized in three main
tracks:

1) HCL Track: Processing Human-Computer Languages The HCL track is
where researchers, developers and educators exchange ideas and
information on the latest academic or industrial work on language
design, processing, assessment and applications.
2) CCL Track: Processing Computer-Computer Languages The CCL track
main goal is to provide a broad space for discussion about the XML
mark-up language: examples of usage and associated technologies.
3) HHL Track: Processing Human-Human Languages The HHL track is
dedicated to the discussion of research projects and ideas involving
natural language processing and their industrial application.

A detailed topic list for each one of these tracks is presented below.

HCL Track: Processing Human-Computer Languages
* Programming language concepts, methodologies and tools; * Language
and Grammars, design, formal specification and quality; * Design of
novel language constructs and their implementation; * Domain Specific
Languages design and implementation; * Programming, refactoring and
debugging environments; * Dynamic and static analysis: Program Slicing;
* Program Comprehension; * Compilation and interpretation techniques;
* Code generation and optimization; * Program visualization and
animation; * Programming languages teaching methods; * Languages for
modeling; * Dynamic languages; * Programmer profiling; *
Cross-fertilization of different technological spaces (modelware,
grammarware, ontologies, etc).

CCL Track: Processing Computer-Computer Languages
* IoT data protocols; * Semantic data description frameworks; *
Semantic Web languages; * Ontology engineering; * XML Databases and
Big Data; * Publishing and document storage formats; * HTML5 and web
formatting; * Industry specific XML based standards; * Web APIs and
service marketplaces; * Service Oriented Architectures; * E-learning
systems, standards and interoperability; * Data and graph visualization
languages.

HHL Track: Processing Human-Human Languages
* Computational morphology, syntax and semantics; * Machine
translation and tools for computer assisted translation; *
Computational terminology and lexicography; * Speech synthesis and
understanding; * Information retrieval, extraction and automatic
question answering; * Corpora linguistics; * NLP system and resource
evaluation; * Public tools and resources for NLP; * Ontologies and
knowledge representation; * Statistical Methods applied to NLP; *
Language teaching support tools.


SLATE Publication Policy

Paper types:
* Full papers - 8 to 14 pages, presented in 20+5 minutes, complete
work, including a validation or discussion;
* Short papers - 6 to 8 pages, presented in 10+5 minutes, ongoing
work, well anchored in the literature, but not yet fully validated;
* Lightning talks - no publication, presented in 3 to 5 minutes,
research ideas or work that has just started.

All accepted papers will be published in the conference proceedings,
under an ISBN reference, on paper and digital support. They will also
integrate the OASIcs series:
http://www.dagstuhl.de/publikationen/oasics/. In addition, we are
currently envisioning several publication follow-ups for SLATE?17 (more
information will be posted later on the conference website).
Papers should be written using the OASIcs LaTeX template, using the
English language. Please refer to our website
(http://slate-conf.org/2017/submissions) for details about the document
preparation.


Committees
Symposium Chairs
* Ricardo Queir?s (Instituto Polit?cnico do Porto, Portugal) * M?rio
Pinto (Instituto Polit?cnico do Porto, Portugal)

Track chairs
* Alberto Sim?es (Universidade do Minho, Portugal - HHL Track)
* Jos? Paulo Leal (Universidade do Porto, Portugal - CCL Track)
* Maria Jo?o Varanda (Instituto Polit?cnico de Bragan?a, Portugal ?
HCL Track)

Organization Committee
* Alberto Sim?es (Universidade do Minho, Portugal)
* Jos? Paulo Leal (Universidade do Porto, Portugal)
* Maria Jo?o Varanda (Instituto Polit?cnico de Bragan?a, Portugal)
* M?rio Pinto (Instituto Polit?cnico do Porto, Portugal)
* Pedro Rangel Henriques (Universidade do Minho, Portugal)
* Ricardo Queir?s (Instituto Polit?cnico do Porto, Portugal)

For the full Program Committes please look at the conference homepage.

Updates are regularly posted in the symposium webpage and notified
through different social networks (e.g., @slateorg at Twitter; check the
symposium webpage for details); Organizers can be contacted using
slate2017@easychair.org.


--
Mikel L. Forcada http://www.dlsi.ua.es/~mlf/
Departament de Llenguatges i Sistemes Inform?tics
Universitat d'Alacant
E-03690 Sant Vicent del Raspeig
Spain
Office: +34 96 590 9776

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20161102/265af9d2/attachment-0001.html

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

Message: 3
Date: Wed, 2 Nov 2016 14:32:04 -0500
From: Hieu Hoang <hieuhoang@gmail.com>
Subject: Re: [Moses-support] moses server options different for moses
vs. moses2
To: Martin Baumg?rtner <martin.baumgaertner@star-group.net>
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID: <e0280950-47f4-f7a4-a12f-46ce8a6db43d@gmail.com>
Content-Type: text/plain; charset="utf-8"

added:

https://github.com/moses-smt/mosesdecoder/commit/d49170de3dce41b52e4ddacf0b8f82cadb0919ef

it was actually already ported from Moses but the params weren't set up.

Also note that not all the params listed by Moses2 have been
implemented. If they are not implemented, Moses2 will just silently
ignore it.

Will try and make this clearer in the near future

On 02/11/2016 08:43, Martin Baumg?rtner wrote:
> Hi Hieu,
>
> especially the following params, all related to Abyss server
> functionality, with decreasing priority:
>
> --server-maxconn
> --server-maxconn-backlog
> --server-keepalive-maxconn
> --server-keepalive-timeout
> --server-timeout
>
> Currently the default of these params is ok for me, but there had been
> issues in the past that made it necessary to tweak.
>
> Cheers,
> Martin
>
> Am 02.11.2016 um 14:17 schrieb Hieu Hoang:
>> In general, I've added options that I understand and can test. Which
>> specific option are you after?
>>
>> Hieu Hoang
>> http://www.hoang.co.uk/hieu
>>
>> On 2 November 2016 at 06:04, Martin Baumg?rtner
>> <martin.baumgaertner@star-group.net
>> <mailto:martin.baumgaertner@star-group.net>> wrote:
>>
>> Hi all,
>>
>> I've seen that there's a difference between moses and moses2
>> concerning server options, especially missing the "Abyss stuff":
>>
>> moses:
>> ========
>>
>> Moses Server Options:
>> --server Run moses as a translation server.
>> --daemon Run moses as a translation server in
>> the background.
>> --server-port Port for moses server
>> --server-log Log destination for moses server
>> --serial Run server in serial mode, processing
>> only one request at a time.
>> --server-maxconn Max. No of simultaneous HTTP
>> transactions allowed by the server.
>> --server-maxconn-backlog Max. No. of requests the OS
>> will queue
>> if the server is busy.
>> --server-keepalive-maxconn Max. No. of requests the
>> server will
>> accept on a single TCP connection.
>> --server-keepalive-timeout Max. number of seconds the
>> server will
>> keep a persistent connection alive.
>> --server-timeout Max. number of seconds the server will
>> wait for a client to submit a request
>> once a connection has been established.
>> --session-timeout Timeout for sessions, e.g. '2h30m' or
>> 1d (=24h)
>> --session-cache-size Max. number of sessions cached.Least
>> recently used session is dumped first.
>>
>> moses2:
>> ========
>> Moses Server Options:
>> --server Run moses as a translation server.
>> --server-port Port for moses server
>> --server-log Log destination for moses server
>> --session-timeout Timeout for sessions, e.g. '2h30m' or
>> 1d (=24h)
>> --session-cache-size Max. number of sessions cached.Least
>> recently used session is dumped first.
>> --serial Run server in serial mode, processing
>> only one request at a time.
>>
>>
>> Is this feature or just being forgotten ;-)
>>
>> Cheers,
>> Martin
>>
>> --
>>
>> *STAR Group* <http://www.star-group.net>
>> <http://www.star-group.net/>
>>
>> *Martin Baumg?rtner*
>>
>> STAR Language Technology & Solutions GmbH
>> Umberto-Nobile-Stra?e 19 | 71063 Sindelfingen | Germany
>> Tel. +49 70 31-4 10 92-0 martin.baumgaertner@star-group.net
>> <mailto:martin.baumgaertner@star-group.net>
>> Fax +49 70 31-4 10 92-70 www.star-group.net
>> <http://www.star-group.net/>
>> Gesch?ftsf?hrer: Oliver Rau, Bernd Barth
>> Handelsregister Stuttgart HRB 245654 | St.-Nr. 56098/11677
>>
>>
>> _______________________________________________
>> Moses-support mailing list
>> Moses-support@mit.edu <mailto:Moses-support@mit.edu>
>> http://mailman.mit.edu/mailman/listinfo/moses-support
>> <http://mailman.mit.edu/mailman/listinfo/moses-support>
>>
>>
>
> --
>
> *STAR Group* <http://www.star-group.net>
> <http://www.star-group.net/>
>
> *Martin Baumg?rtner*
>
> STAR Language Technology & Solutions GmbH
> Umberto-Nobile-Stra?e 19 | 71063 Sindelfingen | Germany
> Tel. +49 70 31-4 10 92-0 martin.baumgaertner@star-group.net
> <mailto:martin.baumgaertner@star-group.net>
> Fax +49 70 31-4 10 92-70 www.star-group.net <http://www.star-group.net/>
> Gesch?ftsf?hrer: Oliver Rau, Bernd Barth
> Handelsregister Stuttgart HRB 245654 | St.-Nr. 56098/11677
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20161102/a540a4a5/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 8030 bytes
Desc: not available
Url : http://mailman.mit.edu/mailman/private/moses-support/attachments/20161102/a540a4a5/attachment.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 8030 bytes
Desc: not available
Url : http://mailman.mit.edu/mailman/private/moses-support/attachments/20161102/a540a4a5/attachment-0001.gif

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

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


End of Moses-support Digest, Vol 121, Issue 18
**********************************************

Tweet