A Pair Feature (

) is a special feature that defines conditions on pairs. A pair has a source and a destination side, and a pair condition typically connects the dependent variables between them using pointwise constraints.
For pair features, there are two extra options in the Selection list of the
Selection section;
Source and
Destination. With these options you can specify to use the source or destination boundaries in the condition of a pair feature; see
Specifying Selections for more information.
See Selection Settings for
Generic Feature. For a pair feature, you do not have to specify the geometric entity level, because it is always boundary level. The same is true for the domain type setting, because all pairs belong to a special domain type, called
Pair. Ordinary features that support this domain type also appear in a pair version among the physics interface’s pair conditions.
Select the Only use explicit pair looping over pairs check box to turn off the automatic looping over pairs, so no individual pair access is supported for the nodes under the pair feature and for links to normal components. Any pair looping then have to use an explicit pair looping with a component (see the
Loop list in
Component).
Select the Singleton feature check box if the physics interface only allows a single instance of the feature.
For features under a physics interface there is an Add as default feature check box. Select this check box if you want the feature to be a default feature. When you specify default features, specify the geometric entity level in the
Default geometric entity level list. Newly created interfaces then add the feature on this level. The
Default entity types specifies the entity types the default feature is added on.
In the Advanced preferences table, you can specify special options for the default feature. By default, default features have a selection over all domains (it cannot be changed), and you can neither remove or disable the feature. Select the check box columns —
Unlock selection,
Clear selection,
Deactivable, and
Removable — to alter this default behavior. The last column,
Lists order weight, is a preference to control the order of the default features. The standard order is domain features first, then boundary features, and so on until the point features followed by the global features. The automatically added initial value features always show up last in the list. The program uses a integer when sorting the default features. The integer depends on the geometric entity dimension and the list order weight using the following formula: