Normally, contour results in the Mechanical application are displayed as averaged results. Some results can also display as unaveraged contours. Averaged contours distribute the average elemental nodal results across element and geometric discontinuities. A user option exists that allows you to control whether results are also averaged across body boundaries that contain a conformal mesh. The default setting does not calculate an average across bodies.
Using the Mechanical APDL application terminology, unaveraged contour results display as element nodal contours that vary discontinuously even across element boundaries. These contours are determined by linear interpolation within each element and are unaffected by surrounding elements (that is, no nodal averaging is performed). The discontinuity between contours of adjacent elements is an indication of the gradient across elements.
Results that include the unaveraged contour display option are most elemental quantities such as stress or strain. This option is not available for degree of freedom results such as displacements.
Nodal averaging of element quantities involves direct averaging of values at corner nodes. For higher-order elements, midside node results are then taken as the average of the corner nodes.
There are two distinct techniques for calculating averaged nodal results. The calculation for the first technique is as follows:
Average the component (X, Y, Z, XY, YZ, XZ) stress values from the elements at a common node.
Calculate the equivalent stresses from the averaged component values
The calculation for the second technique is as follows:
Calculate the equivalent stress values (from the six component strains) on a per element basis.
Average these values from the elements at a common node.
For equivalent stress, stress/strain intensity, max shear stress/strain, and principal stresses/strains, the first technique is used to calculate the results. For equivalent strains, which are calculated by the Mechanical APDL solver, the second technique is used. For random vibration analysis, equivalent stresses are calculated by the Mechanical APDL solver using the Segalman method, so the second technique is also used.
Note: If an elemental result is scoped to a surface body, then there may be two sets of results at each node (Top and Bottom) and sometimes a third set of results (Middle). At release 12.0, if the solver writes Middle results to the result file, then Mechanical displays these results if the Shell Face setting in the Details view equals Middle (Membrane). If the solver did not write Middle results to the result file, then Mechanical displays the average of Top and Bottom if the Shell Face setting in the Details View is Middle (Membrane). For a given node on the shell, the application will average Top results, separately average Bottom results, and separately average Middle results. When you export a result in the application that is set to Top/Bottom, you may note that a node number is repeated in the Excel file. This is because both the Top and Bottom stresses are listed.
Beginning at Release 16.0, Mechanical supports the // positions for layered solid bodies. Therefore, layered solid elements mimic expanded shell elements, which display as having a thickness between the face and face.
You can display contour results by setting the Display Option field to one of the following:
Unaveraged: Displays unaveraged results.
Averaged (default): Displays averaged results.
Nodal Difference: Computes the maximum difference between the unaveraged computed result (for example, total heat flux, equivalent stress) for all elements that share a particular node.
Nodal Fraction: Computes the ratio of the nodal difference and the nodal average.
Elemental Difference: Computes the maximum difference between the unaveraged computed result (for example, total heat flux, equivalent stress) for all nodes in an element, including midside nodes.
Elemental Fraction: Computes the ratio of the elemental difference and the elemental average.
Elemental Mean: Computes the elemental average from the averaged component results.
Characteristics of unaveraged contour displays:
Because of the added data involved in the processing of unaveraged contour results, these results take a longer time to display than averaged results.
Occasionally, unaveraged contour result displays tend to resemble a checkerboard pattern.
Capped Isosurface displays can have missing facets.
When you select Averaged as the Display Option, the Average Across Bodies property displays in the Integration Point Results category. Setting this property to (the default value is ) allows you to averages the results across separate bodies on your model. This post-processing feature is supported for most averaged element nodal contour results (like stress, strain, and thermal flux).
If a node belongs to two different bodies, its averaged stress value of one of the bodies is typically different from the stress value of the other body. Using the Average Across Bodies feature, the average value at this node is the sum of all of the stress values from all “scoped” elements that contain the node (divided by the number of elements). The feature graphically renders a smoother result contour at the interfaces of bodies. If bodies do not share any nodes, then the feature has no effect.
Calculation Conditions
Note the following conditions and characteristics for calculating averages across bodies:
Principal values themselves are averaged when averaging results across bodies for principal and vector sums. Calculated results, such as the types shown below, are averaged at the nodes at the interfaces of bodies. That is, they do not average the components (SX, SY, etc.) across bodies. For example, this feature averages equivalent stress (SEQV) values directly:
SEQV(node_1) + SEQV(node_2) + SEQV(node_N)/N
This differs from the usual method (except for equivalent strain) of averaging the components and then computing SEQV.
Principal Stresses (1, 2, 3)
Stress Intensity (INT)
Equivalent Stress (EQV)
Principal Strains (1, 2, 3)
Strain Intensity (INT)
Equivalent Strain (EQV)
Total Thermal Flux
The following result illustrations show the outcomes between not performing an average calculation, performing an average calculation but not across bodies, and performing an average calculation across bodies.
No Averaging Performed

No Averaging Across Bodies Performed

Averaging Across Bodies Performed

If the associated bodies have different material properties, such as Poisson's ratios, then, because this feature averages quantities like equivalent elastic strain at common nodes, you may see unexpected results at the interfaces. The Poisson Ratio employed to calculate elastic equivalent in one body may be significantly different from the Poisson Ratio employed to calculate elastic equivalent in a different body. Therefore, in this scenario, averaging across bodies at the interface is not recommended.
If you choose to compare this feature against Mechanical APDL PowerGraphics with AVRES,1,FULL in effect, PowerGraphics employs the effective Poisson's ratio in the AVPRIN,KEY,EFFNU command. The EFFNU value may not match the Poisson's ratios in all bodies. PowerGraphics also calculates equivalent strain from the average component strains if KEY (in the AVPRIN command) is set to ZERO. As a result, there may be differences between this feature and PowerGraphics when the AVRES,1,FULL command is employed.
Support Limitations
The following results features are not supported:
Probe results
Results in cyclic symmetry analyses
Results on line bodies
For most element nodal results (like stresses and strains), the Mechanical solvers write only the unaveraged corner node values to the result file. No element nodal results are written for mid-side nodes. This difference is of critical importance.
To derive the value at a mid-side node, the Mechanical post processor must employ the values at the corner nodes. There are three distinct techniques for this process:
For line elements, such as unexpanded beam and pipe stress, Mechanical calculates the average of the unaveraged values of those corner nodes which share an edge with the mid-side node - corner nodes, node I and node J. See Case 1 below.
For solid elements (i.e. shell, hexahedron, tetrahedron, wedge, and pyramid elements), the technique calculates the mid-side node results from the averaged corner nodes. See Case 2 below.
For contact elements, the technique calculates the mid-side node results by averaging the un-averaged values of adjacent corner nodes. Note: A result max may be at a mid-side node. See Case 3 below.
Consider the following example consisting solely of high order line elements, where:
Element 1 contains nodes 1, 2, and 12.
Element 2 contains nodes 2, 3, and 23.
Element 3 contains nodes 3, 4, and 34.
Nodes 12, 23, and 34 are mid-side nodes.

If:
The element nodal solution for element 1 is 0.0 and 0.0 for nodes 1 and 2.
The element nodal solution for element 2 is 100 and 80 for nodes 2 and 3.
The element nodal solution for element 3 is 3 and 0.0 for nodes 3 and 4.
The unaveraged solution is then:
The value at node 12 is the average of the values at the associated element's end points, namely 0.0.
The value at node 23 is the average of the values at the associated element's end points, namely 90.
The value at node 34 is the average of the values at the associated element's end points, namely 1.5.

For the averaged solution of nodes 2 and 3:
The value at node 2 is 50.
The value at node 3 is 41.5.

Note that the value at the mid-side node 23 (90) exceeds the values at the end points.
Result averaging for solids: mid-side node results are the average of the averaged corner node values.
| Raw Data | Averaged Corner Nodes |
|
![]()
|
![]()
|
| Mid-Side Nodes Calculated from Averaged Corner Nodes | |
|
![]()
| |
Result averaging for contacts: calculate the final mid-side node results by averaging intermediate mid-side values.
| Raw Data | Averaged Corner Nodes |
|
![]()
|
![]()
|
| Mid-Side Nodes Calculated from Averaged Corner Nodes | |
|
![]()
| |
Note: Result maximum in this case may be at a mid-side node.