there should be no problem. I ran it all the way through yesterday. I've
checked my example config file into github:

https://github.com/moses-smt/mosesdecoder/commit/9cbfa50102b3a08fd934de97da9c1b90c143ba04

can you please send me your config file and tell me the EXACT command you
ran and the error you get


On 11 October 2013 11:48, 서원영 <[email protected]> wrote:

>  Hi,
> I'm taking same problem of crash with Lane.
> If I need to fix this problem, where I can fix this settings? In a ems
> config file or another configuration file?
>
>
>
> ------- *Original Message* -------
>
> *Sender* : Philipp Koehn<[email protected]>
>
> *Date* : 2013-10-11 09:54 (GMT+09:00)
>
> *Title* : Re: [Moses-support] Hiero ems should die on decode error, but
> doesn't
>
>
> Hi,
>
> In lines 1351ff of experiment.perl, a number of patterns are define,
> which detect
> crashes of steps:
>
>         foreach my $pattern (@{$ERROR{&defined_step_id($i)}},
>                              'error','killed','core dumped','can\'t read',
>                              'no such file or directory','unknown option',
>                              'died at','exit code','permission denied',
>            'segmentation fault','abort',
>            'no space left on device',
>            'can\'t locate', 'unrecognized option') {
>
> If you want to define additional detector patterns for a specific step,
> you can
> add these in experiment.meta:
>
> See for instance in LM:factorize
>
> factorize
>         in: tokenized-corpus
>         out: factorized-corpus
>         rerun-on-change: TRAINING:output-factors
>         default-name: lm/factored
>         pass-unless: factors
>         parallelizable: yes
>         error: can't open
>         error: incompatible number of words in factor
>
> To your question about this particular crash of Moses: you seem to have
> defined
> TranslationModel with num-features=1, but the phrase pairs in the table
> actually
> do not have any feature values.
>
> -phi
>
> On Thu, Oct 10, 2013 at 6:13 PM, Lane Schwartz **wrote:
> > I've been toying around again with ems. I know this should be easy,
> > but for some reason I'm really having trouble getting the toy config
> > changed to successfully run with a hiero model.
> >
> > I started out with scripts/ems/example/config.toy, and attempted to
> > apply the changes described here:
> > http://www.statmt.org/moses/?n=FactoredTraining.EMS#ntoc7. The
> > resulting setup runs, but dies at the final REPORTING stage.
> >
> > I looked through the output for various steps, and it appears that the
> > EVALUATION:decode step is dying with error message "Feature function
> > TranslationModel1 specified 1 dense scores or weights. Actually has
> > 0." As a result, the decoder failed to translate the requested
> > sentences.
> >
> > I'm not an expert on ems, but I would have expected EMS to die at the
> > EVALUATION:decode if that's where the first critical error occurs.
> >
> > That aside, I'd appreciate any thoughts on why ems might be dying. I'd
> > like to try running some hiero experiments with ems. FWIW, running the
> > config.toy phrase-based model works fine.
> >
> > Thanks,
> > Lane
> > _______________________________________________
> > 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
>
>
>
>
> *Engineer
> Wonyoung Seo
>  *
>
> Web Platform Lab / Software R&D Center / *SAMSUNG ELECTRONICS CO,. LTD*
> *TEL/Mobile* : +82-10-9626-3686 / *E-mail* : [email protected]
>
>
>
>
> _______________________________________________
> Moses-support mailing list
> [email protected]
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
>


-- 
Hieu Hoang
Research Associate
University of Edinburgh
http://www.hoang.co.uk/hieu

<<201310112048033_BEI0XT4N.gif>>

_______________________________________________
Moses-support mailing list
[email protected]
http://mailman.mit.edu/mailman/listinfo/moses-support

Reply via email to