Much of the v2 moses.ini looks self-explanatory, but I'd like to confirm my understanding.

The website (http://www.statmt.org/moses/?n=Moses.FeatureFunctions) defines three feature/functions without arguments. In the moses.ini files made by train-model.perl's step 9, there also appears to be a 4th that requires no argument. Can someone confirm this is the case? Are there others that could appear without arguments?

    [feature]
    UnknownWordPenalty
    WordPenalty
    Distortion
    PhrasePenalty * - not listed on the website (are there more)

Feature/functions in the [feature] section and items in the [weight] sections appear to be linked. The feature/functions without arguments have corresponding entries linked by the same option name with an appended zero in the [weight] section. Since these feature/functions have arguments, is it safe to say that they can appear only once in both the [feature] and [weight] sections?

    [weight]
    UnknownWordPenalty0= 1
    WordPenalty0= -1
    Distortion0= 0.3
    PhrasePenalty0= 0.2

The feature/functions arguments have corresponding entries liked by the "name=" argument as the option name in the [weight] section. Are there cases where there will be entries in the [feature] section without corresponding entries in the [weight] section or vice-versa?

    [feature]
    PhraseDictionaryMemory name=*TranslationModel0* num-features=4 ...
    KENLM name=*LM0* factor=0 ...

    [weight]
*TranslationModel0*= 0.2 0.2 0.2 0.2
*LM0*= 0.5

The sections other than [feature] and [weight], such as [input-factors] and [mapping], appear to preserve the v1 moses.ini format. Is this true?

The order of lines in the [feature] and [weight] sections is irrelevant (as many examples have them in different orders). Also, the order of the arguments on a feature/function line is irrelevant (examples show them in different orders).

Finally, is there a connection between the [input-factors] section's value and the input-factor argument value for PhraseDictionaryMemory and LexicalReordering feature/functions? Or, are the similar names and corresponding values only coincidental?

My intention is to build two scripts and contribute these scripts to the Moses project. One will convert the v2 moses.ini file to a standard form (not associated with the command line syntax) so people can easily edit the values. The other will convert the interim form back to the native v2 moses.ini format.
_______________________________________________
Moses-support mailing list
[email protected]
http://mailman.mit.edu/mailman/listinfo/moses-support

Reply via email to