Moses-support Digest, Vol 111, Issue 11

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: EMS: add additional steps to a finished run (Philipp Koehn)
2. Re: EMS: add additional steps to a finished run (Nicholas Ruiz)
3. Re: EMS: add additional steps to a finished run (Matthias Huck)


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

Message: 1
Date: Fri, 8 Jan 2016 13:17:32 -0500
From: Philipp Koehn <phi@jhu.edu>
Subject: Re: [Moses-support] EMS: add additional steps to a finished
run
To: Matthias Huck <mhuck@inf.ed.ac.uk>
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CAAFADDCAcwxzL-6O2q0=ywX3hX10yRQkFKUKBW5yuB_4g-ALkQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi,

the command
experiment.perl -config config.1 -continue 1
actually is not defined.

If you want to continue an experiment, you have to run
experiment.perl -continue 1

If you just want to add an additional test set, you have to
edit steps/1/config.1 before you re-run the command.

Note that editing steps/1/config.1 is not recommended use
of experiment.perl (although I do it all the time), since it breaks
assumptions that the scheduler has about which steps need
to be run. If you aware of the implications, proceed with
caution.

In you case you also need to remove the steps/1/REPORTING_report.1*
step, so it is re-run.

-phi

On Fri, Jan 8, 2016 at 12:47 PM, Matthias Huck <mhuck@inf.ed.ac.uk> wrote:

> Hi Nick,
>
> What you're attempting to do should generally be no problem. There's
> most likely some issue with your EMS configuration file. Doesn't it tell
> you something like:
>
> BUGGY CONFIG LINE (474): wrapping-frame = $tokenized-input
>
> I get this when I put two spaces between "wrapping-frame" and "=".
>
> Also, is /path/to/test4.tok.$output-extension some pre-translated
> hypothesis? If it's the reference, you might have to specify it as
> "tokenized-reference" rather than as "tokenized-output".
>
> Cheers,
> Matthias
>
>
> On Fri, 2016-01-08 at 12:16 -0500, Nicholas Ruiz wrote:
> > Thanks, Tomasz. Unfortunately modifying the config file in the steps
> > directory didn't work for me. My block looks something like this:
> >
> > [EVALUATION:test4]
> >
> > tokenized-input = /path/to/test4.tok.$input-extension
> > tokenized-output = /path/to/test4.tok.$output-extension
> > wrapping-frame = $tokenized-input
> >
> > z?n? ???u
> >
> > On Fri, Jan 8, 2016 at 12:11 PM, Tomasz Dwojak <t.dwojak@amu.edu.pl>
> wrote:
> >
> > > Hi Nick,
> > >
> > > there is a way to do that.
> > >
> > > In your working directory is a "steps" directory, where the EMS writes
> > > outputs, etc... There is also the copy of the config file (e.g.
> > > steps/1/config.1). You have to edit this file and then run EMS once
> again.
> > >
> > > Shortly:
> > > 1. Edit steps/1/config.1
> > > 2. run experiment.perl -continue 1
> > >
> > > Best,
> > > Tomasz
> > >
> > > On 08.01.2016 17:45, Nicholas Ruiz wrote:
> > >
> > > Hi all,
> > >
> > > I have a few different experiments that have finished training. Let's
> say
> > > I have versions 0 1 2 3. I'd like to translate/evaluate an additional
> test
> > > set. I added another [EVALUATION:...] block to specify the paths of the
> > > eval data and now I'd like to run it with
> > >
> > > experiment.perl -config config.1 -continue 1
> > >
> > > However, the steps for evaluating the new test set aren't in the list
> of
> > > steps. What's the best way to run this test without having to create
> > > another experiment folder?
> > >
> > > Thanks,
> > > Nick
> > >
> > > z?n? ???u
> > >
> > >
> > > _______________________________________________
> > > Moses-support mailing listMoses-support@mit.eduhttp://
> mailman.mit.edu/mailman/listinfo/moses-support
> > >
> > >
> > >
> > _______________________________________________
> > Moses-support mailing list
> > Moses-support@mit.edu
> > http://mailman.mit.edu/mailman/listinfo/moses-support
>
>
>
> --
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
> _______________________________________________
> 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/20160108/3907bf84/attachment-0001.html

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

Message: 2
Date: Fri, 8 Jan 2016 13:20:54 -0500
From: Nicholas Ruiz <nicruiz@fbk.eu>
Subject: Re: [Moses-support] EMS: add additional steps to a finished
run
To: Philipp Koehn <phi@jhu.edu>
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CAKa+0YPCKvb9ODSkf3-P3r4E-ZfuUh5C5chx4NEeF_5=jZBQwg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Thanks everyone, it's working now.

z?n? ???u

On Fri, Jan 8, 2016 at 1:17 PM, Philipp Koehn <phi@jhu.edu> wrote:

> Hi,
>
> the command
> experiment.perl -config config.1 -continue 1
> actually is not defined.
>
> If you want to continue an experiment, you have to run
> experiment.perl -continue 1
>
> If you just want to add an additional test set, you have to
> edit steps/1/config.1 before you re-run the command.
>
> Note that editing steps/1/config.1 is not recommended use
> of experiment.perl (although I do it all the time), since it breaks
> assumptions that the scheduler has about which steps need
> to be run. If you aware of the implications, proceed with
> caution.
>
> In you case you also need to remove the steps/1/REPORTING_report.1*
> step, so it is re-run.
>
> -phi
>
> On Fri, Jan 8, 2016 at 12:47 PM, Matthias Huck <mhuck@inf.ed.ac.uk> wrote:
>
>> Hi Nick,
>>
>> What you're attempting to do should generally be no problem. There's
>> most likely some issue with your EMS configuration file. Doesn't it tell
>> you something like:
>>
>> BUGGY CONFIG LINE (474): wrapping-frame = $tokenized-input
>>
>> I get this when I put two spaces between "wrapping-frame" and "=".
>>
>> Also, is /path/to/test4.tok.$output-extension some pre-translated
>> hypothesis? If it's the reference, you might have to specify it as
>> "tokenized-reference" rather than as "tokenized-output".
>>
>> Cheers,
>> Matthias
>>
>>
>> On Fri, 2016-01-08 at 12:16 -0500, Nicholas Ruiz wrote:
>> > Thanks, Tomasz. Unfortunately modifying the config file in the steps
>> > directory didn't work for me. My block looks something like this:
>> >
>> > [EVALUATION:test4]
>> >
>> > tokenized-input = /path/to/test4.tok.$input-extension
>> > tokenized-output = /path/to/test4.tok.$output-extension
>> > wrapping-frame = $tokenized-input
>> >
>> > z?n? ???u
>> >
>> > On Fri, Jan 8, 2016 at 12:11 PM, Tomasz Dwojak <t.dwojak@amu.edu.pl>
>> wrote:
>> >
>> > > Hi Nick,
>> > >
>> > > there is a way to do that.
>> > >
>> > > In your working directory is a "steps" directory, where the EMS writes
>> > > outputs, etc... There is also the copy of the config file (e.g.
>> > > steps/1/config.1). You have to edit this file and then run EMS once
>> again.
>> > >
>> > > Shortly:
>> > > 1. Edit steps/1/config.1
>> > > 2. run experiment.perl -continue 1
>> > >
>> > > Best,
>> > > Tomasz
>> > >
>> > > On 08.01.2016 17:45, Nicholas Ruiz wrote:
>> > >
>> > > Hi all,
>> > >
>> > > I have a few different experiments that have finished training. Let's
>> say
>> > > I have versions 0 1 2 3. I'd like to translate/evaluate an additional
>> test
>> > > set. I added another [EVALUATION:...] block to specify the paths of
>> the
>> > > eval data and now I'd like to run it with
>> > >
>> > > experiment.perl -config config.1 -continue 1
>> > >
>> > > However, the steps for evaluating the new test set aren't in the list
>> of
>> > > steps. What's the best way to run this test without having to create
>> > > another experiment folder?
>> > >
>> > > Thanks,
>> > > Nick
>> > >
>> > > z?n? ???u
>> > >
>> > >
>> > > _______________________________________________
>> > > Moses-support mailing listMoses-support@mit.eduhttp://
>> mailman.mit.edu/mailman/listinfo/moses-support
>> > >
>> > >
>> > >
>> > _______________________________________________
>> > Moses-support mailing list
>> > Moses-support@mit.edu
>> > http://mailman.mit.edu/mailman/listinfo/moses-support
>>
>>
>>
>> --
>> The University of Edinburgh is a charitable body, registered in
>> Scotland, with registration number SC005336.
>>
>> _______________________________________________
>> 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/20160108/593efa9d/attachment-0001.html

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

Message: 3
Date: Fri, 08 Jan 2016 18:24:41 +0000
From: Matthias Huck <mhuck@inf.ed.ac.uk>
Subject: Re: [Moses-support] EMS: add additional steps to a finished
run
To: Philipp Koehn <phi@jhu.edu>
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID: <1452277481.2708.41.camel@portedgar>
Content-Type: text/plain; charset="UTF-8"

Hi Philipp,

On Fri, 2016-01-08 at 13:17 -0500, Philipp Koehn wrote:
> the command
> experiment.perl -config config.1 -continue 1
> actually is not defined.

Are you sure about this? I seem to be doing that kind of thing all the
time and never had any issues with it, as far as I can tell.
It won't replace an older steps/1/config.1 , but I typically don't mind.

Cheers,
Matthias





--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.



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

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


End of Moses-support Digest, Vol 111, Issue 11
**********************************************

Tweet