TRALE-EXTENSION:TGC Error and Warning Messages

Ambiguous field name(s) FieldNames in R1 and R2

R1 and R2 share the field(s) in the list FieldNames

Argument of compacts/2 not a list in compacts(Phi)

The argument a global compacts/1 constraint, Phi is not a list.

covered_by illigally used in rule Rule

A covered_by/2 constraint has been used locally in rule Rule.

Disjoined field names in conditional matches/2 for Phi matches Field

Field in a conditional matches/2 constraint is a disjunction of field names.

Inconsistent linking rules for F and R

Linking rules -»/2 and «-/2 for field F and region R violate the universal quantification condition of the rules.

Index not in range in Constraint constraint in Rule

The index used in Constraint in tecto-rule Rule is not in the valid range.

Index not integer in Constraint constraint in Rule

The index used in Constraint in tecto-rule Rule is not an integer.

Matched_by illigally used in rule Rule

A matched_by/2 constraint has been used locally in rule Rule.

Matrix not maximal in F -->> R

The linkage rule F -» R renders matrix non-maximal.

Matrix not maximal in R <<-- F

The linkage rule R «- F renders matrix non-maximal.

Multiple Constraint declarations for X

More than one global constraint Constraint has been found for X. Only the last instance is considered.

No fields specified in topo rule: R topo []

The right-hand side of a topo rule for R is an empty list.

No linking rules in pheno-grammar

No linking rules («-/2 or -»/2) were found in the grammar.

No matched_by rules. The parser will not tecto-parse.

The matched_by rules are responsible for predicting tectogrammatical categories. Without them tecto-parsing is not possible.

Unary-branching topo rule: TopoRule

All topo rules must be at least binary branching. Use linkage rules instead.