About parser parameters

It is recommended that you review the following table before you Edit parser parameters.

Change XAmple Parser Parameters (Default Parser)

Parameter

Default value

Description

MaxNulls

1

The maximum number of null allomorphs that may appear in a single well-formed word.

You want this to be as small as possible to make parsing efficient.

MaxPrefixes

5

The maximum number of prefixes and proclitics that may appear in a single well-formed word.

Note that it is the sum of the maximum number of prefixes plus the maximum number of proclitics. You want this to be as small as possible to make parsing efficient.

MaxInfixes

0

The maximum number of infixes that may appear in a single well-formed word.

If you have at least one infix, this number will automatically be set to 1.

You will only need to change it if you can have two or more infixes in a single well-formed word. You want this to be as small as possible to make parsing efficient.

MaxRoots

1 or 2

The maximum number of roots that may appear in a single well-formed word.

Any lexical entry with a morpheme type of root, bound root, stem or bound stem is considered to be a root as far as this parameter is concerned.

If you have at least one compound rule, this number will automatically be set to 2. Otherwise, it defaults to 1.

You will only need to change it if you can have three or more roots that can compound in a single well-formed word. You want this to be as small as possible to make parsing efficient.

MaxSuffixes

5

The maximum number of suffixes and enclitics that may appear in a single well-formed word.

Note that it is the sum of the maximum number of suffixes plus the maximum number of enclitics. You want this to be as small as possible to make parsing efficient.

MaxInterfixes

0 or 1

The maximum number of interfixes that may appear in a single well-formed word.

If you have at least one interfix, this number will automatically be set to 1.

You will only need to change it if you can have two or more interfixes in a single well-formed word.

You want this to be as small as possible to make parsing efficient. (Interfixes are affixes (prefixes, infixes, or suffixes) which can appear between roots in compounds.)

MaxAnalyses

See description

The maximum number of analyses (i.e. parses) the parser will return.

If this is set to -1 (or less), the parser returns all the analyses/parses it discovers. (Depending on your implementation, this could be quite large or rather small.) This value was probably set to 10 when you created your language project. You want this parameter to be large enough to see the parses being produced, but not so large that the parsing process becomes inefficient. You can try setting it to a value of 10, say, and then, if you have wordforms with 10 parser-generated analyses, be aware that the parser might actually be producing more than 10 parses. You would need to increase this parameter to see if that is the case or not.

Change HC Parser Parameters (Phonological Rules-based Parser)

Parameter

Default value

Description

DelReapps

0

Normally, deletion rules only apply once. If you find that you need a deletion rule to apply more than once, you will need to set this parameter to greater than zero. You want this to be as small as possible to make parsing efficient.

NotOnClitics

means the set of phonological rules will not be applied to clitics.

 means the set of phonological rules will be applied to clitics.

NoDefaultCompounding

 means the parser will use default compound rules if you have not defined overt compound rules.

means no default compounding rules will be used.

AcceptUnspecifiedGraphemes

 means the HC parser requires every Unicode character that occurs in the Lexeme Form field of any entry in the Lexicon to be included in the Grapheme field of one of the Phonemes in the project. If not, an error message appears indicating a character is not recognized and any entry that has that character will be ignored by the parser.

 means the HC parser is more lenient:

  • It will attempt to parser wordforms that contain undefined characters, but the results may be meaningless.

  • It will not display error messages about unrecognized characters.

Tip

  •   is not recommended as a long-term strategy, but it may be helpful in the short-term under certain circumstances. The primary advantage is to prevent error messages from appearing in Try a Word that can make it difficult to scroll down quickly to the details about the attempted parse.

  • If you are not ready to fix the errors and when the errors are not relevant to the wordform being parsed, debugging might be easier when this parameter selected ().

GuessRoots

 means that for words that do not have any analyses, the HC parser will attempt to guess which portion of the word is the root, based on the current setup of the parser.

In order to guess roots, you need to create one or more pattern-matching entries in the Lexicon. For the Lexeme Form, create a pattern from the natural classes that have been defined.

The resulting guesses will be presented as possible analyses. The user can approve one to indicate which one is correct. The guessed root must be manually added to the Lexicon by means of the New Entry dialog box.

   

Note

  • If you have no Lexeme Forms that are pattern-matching entries, then root guessing will not happen even when GuessRoots is selected.

  • When the HC parser does the unapplication process on a word with no analyses, it will take all of the constraints of the pattern-matching entry into account as it tries to determine what affixes are on this word, and what the remaining root is.

  • Recommendation: select  NoDefaultCompounding to reduce the number of unhelpful guesses.

 Tip

Related Topics

Parser menu overview

Parsing words overview