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: Support for XML Markup with Confusion Network Input
(James H. Cross III)
2. Re: Support for XML Markup with Confusion Network Input
(Hieu Hoang)
3. Re: Support for XML Markup with Confusion Network Input
(James H. Cross III)
4. Re: Support for XML Markup with Confusion Network Input
(James H. Cross III)
5. Re: Support for XML Markup with Confusion Network Input
(Hieu Hoang)
----------------------------------------------------------------------
Message: 1
Date: Wed, 22 Jul 2015 11:20:23 -0700
From: "James H. Cross III" <james.henry.cross.iii@gmail.com>
Subject: Re: [Moses-support] Support for XML Markup with Confusion
Network Input
To: Hieu Hoang <hieuhoang@gmail.com>
Cc: moses-support@mit.edu
Message-ID:
<CACdKcAG9AB9rgNdv0E5g6DY-dQN3C72PVGh9Xos-Nq4GF2G7Rw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Hi Hieu:
Thanks for the response! I would like to look into adding this
functionality myself.
After a first pass, it looks like a good starting point would be
adding functionality for interpreting XML (e.g., where an input line
could contain a single XML tag rather than a word column) to the
ConfusionNet class, and then adding functionality to enforce the
decoding constraints to the TranslationOptionCollectionConfusionNet
class. Let me know if this impression seems correct to you.
Any other advice or caveats regarding this undertaking would also be
much appreciated!
Thanks,
James
On Wed, Jul 22, 2015 at 5:22 AM, Hieu Hoang <hieuhoang@gmail.com> wrote:
> i guess lack of interest. XML markup is usually used by more
> application-focused users who don't usually use complicated things like
> confusion networks, and confusion networks are used mainly by researchers
> who don't use xml markups
>
>
> On 18/07/2015 00:35, James H. Cross III wrote:
>>
>> Hi:
>>
>> Is it still the case that XML markup is not supported for confusion
>> network (or lattice) input? If not, are the reasons for not supporting
>> this feature because implementing it imposes particular difficulties
>> or simply due to lack of interest?
>>
>> Thanks,
>> James
>> _______________________________________________
>> Moses-support mailing list
>> Moses-support@mit.edu
>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>
>
> --
> Hieu Hoang
> Researcher
> New York University, Abu Dhabi
> http://www.hoang.co.uk/hieu
>
------------------------------
Message: 2
Date: Wed, 22 Jul 2015 22:46:13 +0400
From: Hieu Hoang <hieuhoang@gmail.com>
Subject: Re: [Moses-support] Support for XML Markup with Confusion
Network Input
To: "James H. Cross III" <james.henry.cross.iii@gmail.com>
Cc: moses-support@mit.edu
Message-ID: <55AFE4F5.3080801@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
sounds ok. the xml markup is used for a number of things (forced
translation, placeholders, constraint on reordering). Which
functionality do you want to implement?
On 22/07/2015 22:20, James H. Cross III wrote:
> Hi Hieu:
>
> Thanks for the response! I would like to look into adding this
> functionality myself.
>
> After a first pass, it looks like a good starting point would be
> adding functionality for interpreting XML (e.g., where an input line
> could contain a single XML tag rather than a word column) to the
> ConfusionNet class, and then adding functionality to enforce the
> decoding constraints to the TranslationOptionCollectionConfusionNet
> class. Let me know if this impression seems correct to you.
>
> Any other advice or caveats regarding this undertaking would also be
> much appreciated!
>
> Thanks,
> James
>
> On Wed, Jul 22, 2015 at 5:22 AM, Hieu Hoang <hieuhoang@gmail.com> wrote:
>> i guess lack of interest. XML markup is usually used by more
>> application-focused users who don't usually use complicated things like
>> confusion networks, and confusion networks are used mainly by researchers
>> who don't use xml markups
>>
>>
>> On 18/07/2015 00:35, James H. Cross III wrote:
>>> Hi:
>>>
>>> Is it still the case that XML markup is not supported for confusion
>>> network (or lattice) input? If not, are the reasons for not supporting
>>> this feature because implementing it imposes particular difficulties
>>> or simply due to lack of interest?
>>>
>>> Thanks,
>>> James
>>> _______________________________________________
>>> Moses-support mailing list
>>> Moses-support@mit.edu
>>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>>
>> --
>> Hieu Hoang
>> Researcher
>> New York University, Abu Dhabi
>> http://www.hoang.co.uk/hieu
>>
--
Hieu Hoang
Researcher
New York University, Abu Dhabi
http://www.hoang.co.uk/hieu
------------------------------
Message: 3
Date: Wed, 22 Jul 2015 12:22:21 -0700
From: "James H. Cross III" <james.henry.cross.iii@gmail.com>
Subject: Re: [Moses-support] Support for XML Markup with Confusion
Network Input
To: Hieu Hoang <hieuhoang@gmail.com>
Cc: moses-support@mit.edu
Message-ID:
<CACdKcAFoYqLMa-Xk75VSRXo-NaCa_qRmF79cgciNuOzyuK6cyw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Definitely at least placeholders and constraints on reordering.
On Wed, Jul 22, 2015 at 11:46 AM, Hieu Hoang <hieuhoang@gmail.com> wrote:
> sounds ok. the xml markup is used for a number of things (forced
> translation, placeholders, constraint on reordering). Which functionality do
> you want to implement?
>
> On 22/07/2015 22:20, James H. Cross III wrote:
>>
>> Hi Hieu:
>>
>> Thanks for the response! I would like to look into adding this
>> functionality myself.
>>
>> After a first pass, it looks like a good starting point would be
>> adding functionality for interpreting XML (e.g., where an input line
>> could contain a single XML tag rather than a word column) to the
>> ConfusionNet class, and then adding functionality to enforce the
>> decoding constraints to the TranslationOptionCollectionConfusionNet
>> class. Let me know if this impression seems correct to you.
>>
>> Any other advice or caveats regarding this undertaking would also be
>> much appreciated!
>>
>> Thanks,
>> James
>>
>> On Wed, Jul 22, 2015 at 5:22 AM, Hieu Hoang <hieuhoang@gmail.com> wrote:
>>>
>>> i guess lack of interest. XML markup is usually used by more
>>> application-focused users who don't usually use complicated things like
>>> confusion networks, and confusion networks are used mainly by researchers
>>> who don't use xml markups
>>>
>>>
>>> On 18/07/2015 00:35, James H. Cross III wrote:
>>>>
>>>> Hi:
>>>>
>>>> Is it still the case that XML markup is not supported for confusion
>>>> network (or lattice) input? If not, are the reasons for not supporting
>>>> this feature because implementing it imposes particular difficulties
>>>> or simply due to lack of interest?
>>>>
>>>> Thanks,
>>>> James
>>>> _______________________________________________
>>>> Moses-support mailing list
>>>> Moses-support@mit.edu
>>>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>>>
>>> --
>>> Hieu Hoang
>>> Researcher
>>> New York University, Abu Dhabi
>>> http://www.hoang.co.uk/hieu
>>>
>
> --
> Hieu Hoang
> Researcher
> New York University, Abu Dhabi
> http://www.hoang.co.uk/hieu
>
------------------------------
Message: 4
Date: Wed, 22 Jul 2015 13:26:56 -0700
From: "James H. Cross III" <james.henry.cross.iii@gmail.com>
Subject: Re: [Moses-support] Support for XML Markup with Confusion
Network Input
To: Hieu Hoang <hieuhoang@gmail.com>
Cc: moses-support@mit.edu
Message-ID:
<CACdKcAG3F9LBSog_-7twpv=G24hoiK17dLvVSZBukL6TXtO+4A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Hi:
I also noticed that decoding with lattice input is not known to be
thread safe ( http://www.statmt.org/moses/?n=Moses.Optimize ). Does
this concern also extend to confusion network input?
Thanks again,
James
On Wed, Jul 22, 2015 at 12:22 PM, James H. Cross III
<james.henry.cross.iii@gmail.com> wrote:
> Definitely at least placeholders and constraints on reordering.
>
> On Wed, Jul 22, 2015 at 11:46 AM, Hieu Hoang <hieuhoang@gmail.com> wrote:
>> sounds ok. the xml markup is used for a number of things (forced
>> translation, placeholders, constraint on reordering). Which functionality do
>> you want to implement?
>>
>> On 22/07/2015 22:20, James H. Cross III wrote:
>>>
>>> Hi Hieu:
>>>
>>> Thanks for the response! I would like to look into adding this
>>> functionality myself.
>>>
>>> After a first pass, it looks like a good starting point would be
>>> adding functionality for interpreting XML (e.g., where an input line
>>> could contain a single XML tag rather than a word column) to the
>>> ConfusionNet class, and then adding functionality to enforce the
>>> decoding constraints to the TranslationOptionCollectionConfusionNet
>>> class. Let me know if this impression seems correct to you.
>>>
>>> Any other advice or caveats regarding this undertaking would also be
>>> much appreciated!
>>>
>>> Thanks,
>>> James
>>>
>>> On Wed, Jul 22, 2015 at 5:22 AM, Hieu Hoang <hieuhoang@gmail.com> wrote:
>>>>
>>>> i guess lack of interest. XML markup is usually used by more
>>>> application-focused users who don't usually use complicated things like
>>>> confusion networks, and confusion networks are used mainly by researchers
>>>> who don't use xml markups
>>>>
>>>>
>>>> On 18/07/2015 00:35, James H. Cross III wrote:
>>>>>
>>>>> Hi:
>>>>>
>>>>> Is it still the case that XML markup is not supported for confusion
>>>>> network (or lattice) input? If not, are the reasons for not supporting
>>>>> this feature because implementing it imposes particular difficulties
>>>>> or simply due to lack of interest?
>>>>>
>>>>> Thanks,
>>>>> James
>>>>> _______________________________________________
>>>>> Moses-support mailing list
>>>>> Moses-support@mit.edu
>>>>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>>>>
>>>> --
>>>> Hieu Hoang
>>>> Researcher
>>>> New York University, Abu Dhabi
>>>> http://www.hoang.co.uk/hieu
>>>>
>>
>> --
>> Hieu Hoang
>> Researcher
>> New York University, Abu Dhabi
>> http://www.hoang.co.uk/hieu
>>
------------------------------
Message: 5
Date: Thu, 23 Jul 2015 00:46:17 +0400
From: Hieu Hoang <hieuhoang@gmail.com>
Subject: Re: [Moses-support] Support for XML Markup with Confusion
Network Input
To: "James H. Cross III" <james.henry.cross.iii@gmail.com>
Cc: moses-support@mit.edu
Message-ID: <55B00119.6090400@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
it should be threadsafe these days. if you find out otherwise, i'll do
my best to fix it
Don't use IRSTLM or the old binary phrase-table.
On 23/07/2015 00:26, James H. Cross III wrote:
> Hi:
>
> I also noticed that decoding with lattice input is not known to be
> thread safe ( http://www.statmt.org/moses/?n=Moses.Optimize ). Does
> this concern also extend to confusion network input?
>
> Thanks again,
> James
>
>
> On Wed, Jul 22, 2015 at 12:22 PM, James H. Cross III
> <james.henry.cross.iii@gmail.com> wrote:
>> Definitely at least placeholders and constraints on reordering.
>>
>> On Wed, Jul 22, 2015 at 11:46 AM, Hieu Hoang <hieuhoang@gmail.com> wrote:
>>> sounds ok. the xml markup is used for a number of things (forced
>>> translation, placeholders, constraint on reordering). Which functionality do
>>> you want to implement?
>>>
>>> On 22/07/2015 22:20, James H. Cross III wrote:
>>>> Hi Hieu:
>>>>
>>>> Thanks for the response! I would like to look into adding this
>>>> functionality myself.
>>>>
>>>> After a first pass, it looks like a good starting point would be
>>>> adding functionality for interpreting XML (e.g., where an input line
>>>> could contain a single XML tag rather than a word column) to the
>>>> ConfusionNet class, and then adding functionality to enforce the
>>>> decoding constraints to the TranslationOptionCollectionConfusionNet
>>>> class. Let me know if this impression seems correct to you.
>>>>
>>>> Any other advice or caveats regarding this undertaking would also be
>>>> much appreciated!
>>>>
>>>> Thanks,
>>>> James
>>>>
>>>> On Wed, Jul 22, 2015 at 5:22 AM, Hieu Hoang <hieuhoang@gmail.com> wrote:
>>>>> i guess lack of interest. XML markup is usually used by more
>>>>> application-focused users who don't usually use complicated things like
>>>>> confusion networks, and confusion networks are used mainly by researchers
>>>>> who don't use xml markups
>>>>>
>>>>>
>>>>> On 18/07/2015 00:35, James H. Cross III wrote:
>>>>>> Hi:
>>>>>>
>>>>>> Is it still the case that XML markup is not supported for confusion
>>>>>> network (or lattice) input? If not, are the reasons for not supporting
>>>>>> this feature because implementing it imposes particular difficulties
>>>>>> or simply due to lack of interest?
>>>>>>
>>>>>> Thanks,
>>>>>> James
>>>>>> _______________________________________________
>>>>>> Moses-support mailing list
>>>>>> Moses-support@mit.edu
>>>>>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>>>>>
>>>>> --
>>>>> Hieu Hoang
>>>>> Researcher
>>>>> New York University, Abu Dhabi
>>>>> http://www.hoang.co.uk/hieu
>>>>>
>>> --
>>> Hieu Hoang
>>> Researcher
>>> New York University, Abu Dhabi
>>> http://www.hoang.co.uk/hieu
>>>
--
Hieu Hoang
Researcher
New York University, Abu Dhabi
http://www.hoang.co.uk/hieu
------------------------------
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support
End of Moses-support Digest, Vol 105, Issue 47
**********************************************
Subscribe to:
Post Comments (Atom)
0 Response to "Moses-support Digest, Vol 105, Issue 47"
Post a Comment