Post-Processing Considerations with Metrics-Based Interfaces

Although metrics-based connectivity provides a faster computation of the interface intersection, this calculation method has an impact on the usability of certain post-processing features.

Metrics-based interfaces have no vertices, therefore they cannot provide any vertex data. Hence:

• Boundaries associated with a metrics-based interface have the following limitations:
  • They are not available as inputs for any derived part or as part seeds for streamlines.
  • They do not report any data in tables with the Data on Vertices property activated. This is also true for the plots that use those tables in data sets.
  • In scalar displayers, the automatic Contour Style setting for these boundaries is always equivalent to Filled (cell-based).

    When the setting is changed to Smooth Filled, these boundaries appear as gray surfaces.

  • In vector displayers that use these boundaries, line integral convolution only shows the surface.
• Solution histories are affected as follows:
  • Standalone boundary export is not available for these boundaries.
  • Regions containing these boundaries only export their original faces.

  • The above limitations become evident through differences in field function filling:

    Volume/surface representation	Corresponding solution history representation

    The volume/surface representation shows a higher mesh resolution because it includes the reconstructed geometry of an interface boundary. The solution history representation does not include that interface boundary because the associated interface, being metrics-based, has no vertices and therefore could not have its geometry exported to the solution history. Instead, what you see with the solution history representation is the original faces of this boundary before the creation of the interface.

• Smooth computation of reports is not available for the following objects:
  • Metrics-based interface boundaries, and part surfaces associated with those interface boundaries
  • Regions that include metrics-based interface boundaries
  • Geometry parts with a metrics-based interface