Hi,
Thank you for your help and suggestions. I tested the new commit and there
is no segfault anymore, but the output is a blank line indeed. I will try
to pinpoint the cause of this behavior in the code and hopefully fix it,
even though, if I understand well, the fact that the phrase-table
*Good news* - i've fixed the segfault
https://github.com/moses-smt/mosesdecoder/commit/a4e951e581b6b3ed2a9c1057f0997739897bd267
*Bad news* - the server doesn't give the right output (it just produces a
blank line), even without XML tags. Did you look at the output when you
were trying it?
The
I have managed to track more precisely where the segfault occurs but I did
not understand why yet. It happens at some point during the for loop in the
function
void ChartHypothesis::GetOutputPhrase(Phrase ) const
in the file moses/ChartHypothesis.cpp
Strangely, if the decoder is called in
Thank you, I changed [inputtype] in the moses.ini from 3 --> 0 and now the
command
echo 'the' | bin/moses -f moses.ini
-xml-input inclusive -placeholder-factor 1
works fine but in server mode
bin/mosesserver -f moses.ini -xml-input inclusive -placeholder-factor 1
still yields a segfault at a
it doesn't need to be tree input, just normal strings is fine for hiero
models. Change [inputtype] in the moses.ini file from 3 -> 0.
if that doesn't work, let me know and i'll debug it
On 24/06/2016 11:31, Vito Mandorino wrote:
Hi,
I am trying to debug by running the decoder with high
it doesn't need to be tree input, just normal strings is fine for hiero
models. Change [inputtype] in the moses.ini file from 3 -> 0.
On 24/06/2016 11:31, Vito Mandorino wrote:
Hi,
I am trying to debug by running the decoder with high verbosity.
I have found that the segfault happens in the
Hi,
I am trying to debug by running the decoder with high verbosity.
I have found that the segfault happens in the function
TreeInput::ProcessAndStripXMLTags in the file TreeInput.cpp, and more
precisely at the line
Phrase sourcePhrase = this->GetSubString(Range(startPos,endPos-1));
The
it's very easy, i had thought i done it already but maybe it's dropped out.
The placeholder feature just tacks the translation on at the very end, just
before outputting the translation.
Run it in a debugger to see where it segfault and change that part of the
code
Hieu Hoang
Dear all,
to add up to the previous messages, I have tried the current version of
Moses from Github and found that hierarchical models do work fine with
mosesserver now. Placeholders are still an issue though: the commands
/bin/mosesserver -f moses.ini -xml-input inclusive -placeholder-factor 1
Hi Hieu,
There is also the mosesserver issue so I cannot say that's the only
difficulty from using tree-based models. If you can have a look it would be
great anyway. Speed is also an issue even though much less for hierarchical
than syntactic models in our tests.
Thank you and best regards,
I believe placeholders can be used but no-one has really tried. If thats
the only thing holding you back from using hiero/syntax models, I can look
into it for you.
However, there's likely to be other issues, such as speed and memory
consumption which may make these models unsuitable for
Dear all,
I am exploring hierarchical and syntactic models and I have two questions:
1. Is it possible to decode using mosesserver instead of moses_chart ?
According to " /mosesdecoder/bin/mosesserver --help " one can choose
different --search-algorithm values. I tried for instance, for a
12 matches
Mail list logo
