I think it's
FeatureFunction::GetScoreProducerDescription()
On 12/02/16 23:56, Jasneet Sabharwal wrote:
Thanks, will give that a try.
Also, is it possible to get the value of feature name inside the
feature function. I’m specifically talking about “name” parameter in
moses.ini. I’m running
Thanks, will give that a try.
Also, is it possible to get the value of feature name inside the feature
function. I’m specifically talking about “name” parameter in moses.ini. I’m
running multiple copies of my feature function with different parameter as
follows:
CoarseBiLM name=CoarseBiLM tgtW
you can run the decoder
./moses -v 3
however, you should put debugging messages in your feature functions to
find out where the problem is. It looks like its in the Load() method so
add lots of debugging message in there and all functions it calls
On 12/02/16 23:34, Jasneet Sabharwal wrote:
Thanks Hieu for your reply.
Is it possible to do a verbose output of what’s happening, so that I can
identify when it’s going out of memory? I’m only running it for 1928 sentences.
I have almost 170gb of free memory and additional 400gb memory in buffer.
Thanks,
Jasneet
> On Feb 12, 2016, at
oh, you mean English -> English? yes, of course. eg. the recaser
'translates'
lowercased english -> cased English
On 12/02/16 15:56, Vincent Nguyen wrote:
> Hey Hieu,
>
> This may sound crazy but do you know if someone has ever run a training
> and testing with same language for the pair ?
>
Indeed. Thank you very much, dear sir.
On 12.02.2016 23:47, Hieu Hoang wrote:
> i think this happens just before expansion, once all the translation
> options have been collected
>
> On 12/02/16 22:36, Marcin Junczys-Dowmunt wrote:
>> But this happens during hypothesis expansion? I think I need i
i think this happens just before expansion, once all the translation
options have been collected
On 12/02/16 22:36, Marcin Junczys-Dowmunt wrote:
> But this happens during hypothesis expansion? I think I need it before.
>
> I have a classifier for which I want to restrict softmaxing over all
> a
hmm. doubt it. The moses.ini file is parsed in
moses/Parameter.cpp
there's no calls to any OS functions that expands environment variables.
It would be useful
On 12/02/16 14:33, Jeremy Gwinnup wrote:
> Hi,
>
> Dumb question - can I reference environment variables in a moses.ini ?
>
> Thanks!
when you extract the rules during training, you must tell the extract
program that there is parse information on the target side
.../extract-rules --TargetSyntax
On 08/02/16 10:31, Khyati Gupta wrote:
Hi,
I have completed string to tree syntax based model. And have converted
the ou
But this happens during hypothesis expansion? I think I need it before.
I have a classifier for which I want to restrict softmaxing over all
available target words for the complete sentence instead over all known
vocabulary items.
I will take a look at your second suggestion.
On 12.02.2016 23:
looks like it's run out of memory.
On 11/02/16 23:23, Jasneet Sabharwal wrote:
Hi,
I was adding a new feature function in Moses
(https://github.com/KonceptGeek/mosesdecoder/blob/master/moses/FF/CoarseBiLM.cpp).
It works fine when I test it for 1-2 sentences, but when I’m trying to
tune my pa
sounds useful.There's
FeatureFunction::EvaluateTranslationOptionListWithSourceContext()
which is called for for every subphrase. It passes the feature function a
list of translation option for that subphrase. The method is called in
TranslationOptionCollection::EvaluateTranslationOptionListWith
Hi everybody,
Is there a nice way to access the complete set of translation options
for a sentence from within a feature function? I just need the bag of
possible words before any processing. Let's say from within
"EmptyHypothesisState", there is InputType, but I cannot really find any
hook to
Hi,
Dumb question - can I reference environment variables in a moses.ini ?
Thanks!
-Jeremy
___
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support
14 matches
Mail list logo