Mapping Specification

A mapping specification allows you to change the mapper search criteria, the integration algorithm, and how missing members are treated.

This page discusses:

The field mapping is discussed in Mapper. By default, the most appropriate mapping algorithm is selected based on the source and target fields. In certain cases, you can change the neighborhood search criteria and the transfer operation (for example, the mapping integration method and how missing members are handled).

Mapping Specification

Use the <mappingSpecifications> wrapper element to specify one or more mapping specifications.

Use the <mapSpec> element to provide a mapping specification. The name attribute is an internal reference name, used to assign a mapping specification to a connector definition.

Search Criteria

Use the <search> element to control the neighborhood search.

By default, search tolerances are relative to the characteristic element size of the source and target meshes. In some cases, it might be more appropriate to specify absolute distances.

Set the isAbsolute attribute to true if search tolerances are provided in units of length. If the source and target meshes have different unit systems, use meters (SI units) for the absolute tolerances in the search criteria.

Use the <normal> and <tangential> elements to define search tolerances in the normal and tangential directions, respectively. Only members that fall within this search distance are considered. If any target member could not find a source member within the given search tolerance, it is marked as a missing member.

For surface facets, the search is performed in the opposing normal direction to distinguish between the top and bottom faces of membrane and shell elements. You can apply search tolerances in the outward direction, the inward direction, or both directions as defined in Table 1.

Table 1. Normal search parameters.
Element Description
<outward> Search tolerance on a surface facet in the outward normal direction.
<inward> Search tolerance on a surface facet in the inward normal direction.
<bidirectional> Search tolerances for volumetric elements.

Example

The following example illustrates how to specify search tolerances:

<mappingSpecifications>
      <mapSpec name="MapSpec-1"”>
         <search isAbsolute=”false”>
            <normal>
               <bidirectional>0.05</bidirectional>
               <outward>0.05</outward>
               <inward>0.05</inward>
            </normal>
            <tangential>0.05</tangential>
         </search>
      </mapSpec>
           :
 </mappingSpecifications>

Transfer

The transfer specification allows you to change the mapping algorithm's conservation principle and to specify how missing members are treated.

Use the <transfer> element to modify the default settings.

Use the <flux> element to specify the conservation algorithm. By default, a subelement algorithm is employed. The subelement algorithm provides conservative mapping with a smooth distribution. Alternatively, you can select a global conservation algorithm where global conservation of the quantity is ensured, potentially at the expense of the smoothness of the distribution. To select the global conservation method, set the <globalConservation> element to true.

Missing members are nodes or elements where the search algorithm failed to find a corresponding member. Use this capability with caution; it is intended when there are a few failures due to complicated geometry. Use the <orphanTreatment> element, and specify a treatment listed in Table 2.

Table 2. Transfer settings.
Entity Description
<nearestNeighbor> Computes the missing member value based on the nearest neighbor value.
<constantValue> Lets you specify a constant value to be used for missing members (for example, a zero flux or ambient temperature value).

Example

The following example illustrates how to select the nearest neighbor treatment.

<mappingSpecifications>
      <mapSpec name="defaultMapSpec">
               :
         <transfer>
            <orphanTreatment>
               <nearestNeighbor></nearestNeighbor>
            </orphanTreatment>
         </transfer>
      </mapSpec>
 </mappingSpecifications>