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_decoder" in mert-moses.perl there is this line:
$decoder_config = "-weight-overwrite '" . join(" ", values
%model_weights) ."'" unless $___USE_CONFIG_WEIGHTS_FIRST && $run==1;
And I suspect -weight-overwrite is with a truncated list of
model_weights is causing the issue.
Best,
Marcin
W dniu 24.02.2014 11:56, Hieu Hoang pisze:
> 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 <[email protected]>
>> wrote:
>>
>> 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 faster with the options specified, so something is clearly not
>> being evaluated.
>>
>> W dniu 23.02.2014 00:30, Marcin Junczys-Dowmunt pisze:
>>> 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 <junczys@...> 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 structure is not being used anywhere in
>>>>> the script once it has been set (apart from printing the message).
>>>> I don't know too much about the --activate-features option myself, but in
>>>> recent Moses versions, you can add the option 'tuneable=false' to a feature
>>>> function in the config. The effect is that the feature score(s) won't be
>>>> reported to the n-best list, and MERT/MIRA/PRO won't even know that the
>>>> feature exists. The weight from the original config will be used for all
>>>> tuning iterations, and copied to the final config. You can now also specify
>>>> the weight of sparse features in the config, and this will override the
>>>> weight set in the weights file.
>>>>
>>>> best wishes,
>>>> Rico
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>> _______________________________________________
>> 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
