we should sort out the tuneable/activate feature issue when you get to
Edinburgh. They seem to overlap and cause problems if we don't sort it out
it may be that we should delete 1 of these options and depend wholly on the
other
On 26 February 2014 08:17, Rico Sennrich wrote:
> On 26.02.2014 0
On 26.02.2014 07:24, moses-support-requ...@mit.edu wrote:
> Hi Hieu, Rico,
> this does not seem to be an issue with the ini-file. It actually works
> as well with stand-alone moses. The issue seems to be the mert-moses.pl
> script which switches off features that are not returned by the decoder
> b
Hi Hieu, Rico,
this does not seem to be an issue with the ini-file. It actually works
as well with stand-alone moses. The issue seems to be the mert-moses.pl
script which switches off features that are not returned by the decoder
because they are set to tuneable=false.
In the function "run_deco
Can you please send me your ini file where you set tuneable = false.
This param has to work, the unknown word penalty depends on it
Sent while bumping into things
> On 23 Feb 2014, at 12:13 am, Marcin Junczys-Dowmunt
> wrote:
>
> And with "tuneable=false" it seems the features are being igno
Marcin Junczys-Dowmunt writes:
>
> And with "tuneable=false" it seems the features are being ignored during
> decoding, I understand this should not be happening. I get much worse
> translation results with an ini-file that has "tuneable=false" for all
> features than with the same ini withou
And with "tuneable=false" it seems the features are being ignored during
decoding, I understand this should not be happening. I get much worse
translation results with an ini-file that has "tuneable=false" for all
features than with the same ini without the option. The translation is
also much
BTW. "tuneable=false" seems to be ignored by Kenlm, works with other
features though.
W dniu 10.02.2014 21:15, Rico Sennrich pisze:
> Marcin Junczys-Dowmunt writes:
>
>> Hi,
>> it seems --activate-features=STRING is not working in mert-moses.perl.
>> The script prints a message that the ignored
You CAN remove Distortion from the ini file, there will be no distortion
score. There may still be reordering, this is controlled by the section
[distortion-limit].
Or you can do what Rico suggested:
[feature]
Distortion tuneable=false
[weight]
Distortion0= 0
fyi - the only obl
Marcin Junczys-Dowmunt writes:
>
> Hi,
> it seems --activate-features=STRING is not working in mert-moses.perl.
> The script prints a message that the ignored features are not being
> used, but then optimizes them anyway. I can see that the "enabled"
> information in the feature data structur
W dniu 10.02.2014 20:46, Barry Haddow pisze:
Ah, by the way, is removing the Distortion feature from the ini file and
setting the limit to 1 a safe way to actually disable distortion? Moses
does not complain (I always thought it is required.)
Best,
Marcin
> Hi Marcin
>
> I had some fun with --ac
Hi Marcin
I had some fun with --activate-features in the past - I think the syntax
was rather strange. If it is not working now, it may have got dropped by
the recent refactoring
My advice would be to use kbmira (or pro), since they are regularised
they don't go crazy when there is an uninform
Hi,
it seems --activate-features=STRING is not working in mert-moses.perl.
The script prints a message that the ignored features are not being
used, but then optimizes them anyway. I can see that the "enabled"
information in the feature data structure is not being used anywhere in
the script on
12 matches
Mail list logo
