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 (Nicholas Ruiz)
2. Re: EMS: add additional steps to a finished run (Philipp Koehn)
3. Re: EMS: add additional steps to a finished run (Philipp Koehn)
4. Re: EMS: add additional steps to a finished run (Matthias Huck)
----------------------------------------------------------------------
Message: 1
Date: Fri, 8 Jan 2016 15:10:43 -0500
From: Nicholas Ruiz <nicruiz@fbk.eu>
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>, Philipp Koehn
<phi@jhu.edu>
Message-ID:
<CAKa+0YMcKE1b=xotCrcM9U8TB_e0E29rPZi+ggRcO7fVPPGM_g@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Got it. You have to explicitly run the reporting step, after
removing steps/1/REPORTING_report.1* and evaluation/report.1
./experiment.perl -continue 1 -final-step REPORTING:report -exec
Although I'm not sure why this is different from the default case, which
should always run reporting...
z?n? ???u
On Fri, Jan 8, 2016 at 2:43 PM, Nicholas Ruiz <nicruiz@fbk.eu> wrote:
> Actually, I'm halfway to the solution. I did the steps below:
>
> #1: Make sure you get your variable names correct. EMS has a boatload of
> variables so it's hard to remember what's "output" and what's "reference"
>
> #2: Don't have a million config files in a directory. You might be
> executing the wrong config file. :) [still trying to figure out how not to
> have one-off configs everywhere]
>
> #3: Edit steps/x/config.x instead of editing the original config.
>
> #4: Thank the EMS developers for their hard work.
>
> However, there's one piece missing. Philipp said:
> "In you case you also need to remove the steps/1/REPORTING_report.1*
> step, so it is re-run."
>
> I tried deleting the files above, as well as deleting evaluation/report.1,
> but the reporting module isn't executing. No new steps/1/REPORTING_report.1*
> files are being generated, although the dependency list shows
> 0 REPORTING:report -> run
>
> z?n? ???u
>
> On Fri, Jan 8, 2016 at 1:26 PM, Matthias Huck <mhuck@inf.ed.ac.uk> wrote:
>
>> So, what has been the proper solution?
>>
>> On Fri, 2016-01-08 at 13:20 -0500, Nicholas Ruiz wrote:
>> > Thanks everyone, it's working now.
>> >
>> > z?n? ???u
>>
>>
>>
>>
>> --
>> The University of Edinburgh is a charitable body, registered in
>> Scotland, with registration number SC005336.
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20160108/1144603a/attachment-0001.html
------------------------------
Message: 2
Date: Fri, 8 Jan 2016 15:15:15 -0500
From: Philipp Koehn <phi@jhu.edu>
Subject: Re: [Moses-support] EMS: add additional steps to a finished
run
To: Nicholas Ruiz <nicruiz@fbk.eu>
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CAAFADDCuaNJppN3C1uA4A5wYRo6g5t_KWcc-=Op2zxvUbv+G7g@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
you should not have to do that...
What happens if you run
./experiment.perl -config steps/1/config.1
This will create a new run, but it is the cleanest way to run with a config
file.
-phi
On Fri, Jan 8, 2016 at 3:10 PM, Nicholas Ruiz <nicruiz@fbk.eu> wrote:
> Got it. You have to explicitly run the reporting step, after
> removing steps/1/REPORTING_report.1* and evaluation/report.1
>
> ./experiment.perl -continue 1 -final-step REPORTING:report -exec
>
> Although I'm not sure why this is different from the default case, which
> should always run reporting...
>
> z?n? ???u
>
> On Fri, Jan 8, 2016 at 2:43 PM, Nicholas Ruiz <nicruiz@fbk.eu> wrote:
>
>> Actually, I'm halfway to the solution. I did the steps below:
>>
>> #1: Make sure you get your variable names correct. EMS has a boatload of
>> variables so it's hard to remember what's "output" and what's "reference"
>>
>> #2: Don't have a million config files in a directory. You might be
>> executing the wrong config file. :) [still trying to figure out how not to
>> have one-off configs everywhere]
>>
>> #3: Edit steps/x/config.x instead of editing the original config.
>>
>> #4: Thank the EMS developers for their hard work.
>>
>> However, there's one piece missing. Philipp said:
>> "In you case you also need to remove the steps/1/REPORTING_report.1*
>> step, so it is re-run."
>>
>> I tried deleting the files above, as well as deleting
>> evaluation/report.1, but the reporting module isn't executing. No new steps/1/REPORTING_report.1*
>> files are being generated, although the dependency list shows
>> 0 REPORTING:report -> run
>>
>> z?n? ???u
>>
>> On Fri, Jan 8, 2016 at 1:26 PM, Matthias Huck <mhuck@inf.ed.ac.uk> wrote:
>>
>>> So, what has been the proper solution?
>>>
>>> On Fri, 2016-01-08 at 13:20 -0500, Nicholas Ruiz wrote:
>>> > Thanks everyone, it's working now.
>>> >
>>> > z?n? ???u
>>>
>>>
>>>
>>>
>>> --
>>> The University of Edinburgh is a charitable body, registered in
>>> Scotland, with registration number SC005336.
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20160108/d296e229/attachment-0001.html
------------------------------
Message: 3
Date: Fri, 8 Jan 2016 15:17:22 -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:
<CAAFADDB=Lq=vfwGW3dG2nhG+AtwreLL1ejB+_uJ1FNtPSCwPXg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
I looked at the code, and I was not happy with what I found, although I
apparently wrote it.
What do you expect
experiment.perl -config config.1 -continue 1
to do differently than
experiment.perl -continue 1
Currently it seems to run with the specified config file but not overwrite
steps/1/config.1 which may cause some unexpected behaviour down the road...
-phi
On Fri, Jan 8, 2016 at 1:24 PM, Matthias Huck <mhuck@inf.ed.ac.uk> wrote:
> 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.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20160108/671cae2d/attachment-0001.html
------------------------------
Message: 4
Date: Fri, 08 Jan 2016 20:56:34 +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: <1452286594.2708.59.camel@portedgar>
Content-Type: text/plain; charset="UTF-8"
Hi Philipp,
Usually I just keep track of the EMS config files in my base directory
and more or less ignore the steps/*/config.* copies.
I never mix
experiment.perl -config config.1 -continue 1
and
experiment.perl -continue 1
so I won't run into trouble.
This workflow was totally okay for me so far. I wouldn't be surprised if
many other users do the same.
I agree that it may "cause some unexpected behaviour down the road",
e.g. if the web interface is used in a collaborative environment for
keeping track of experiments. It's gonna display the config from the
steps/ directory, even though that one might have been superseded when
continuing the experiment.
Cheers,
Matthias
On Fri, 2016-01-08 at 15:17 -0500, Philipp Koehn wrote:
> Hi,
>
>
> I looked at the code, and I was not happy with what I found, although
> I apparently wrote it.
>
>
> What do you expect
> experiment.perl -config config.1 -continue 1
> to do differently than
> experiment.perl -continue 1
>
>
> Currently it seems to run with the specified config file but not
> overwrite steps/1/config.1 which may cause some unexpected behaviour
> down the road...
>
>
> -phi
>
> On Fri, Jan 8, 2016 at 1:24 PM, Matthias Huck <mhuck@inf.ed.ac.uk>
> wrote:
> 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.
>
>
>
>
>
--
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 13
**********************************************
Subscribe to:
Post Comments (Atom)
0 Response to "Moses-support Digest, Vol 111, Issue 13"
Post a Comment