Class 3 Error
SYMPTOM:
Using a global range on a plot showing "Total Mesh Displacement" in CFX-Post shows correct results. However, if one of the components of Total Mesh Displacement is plotted instead (e.g. "Total Mesh Displacement X") on a transient run, then the global range shown is actually only the range for the last timestep, rather than the range for all timesteps. This can be misleading because this incorrect global range does not update if the timestep is changed, and it may not be clear that the range has been truncated.
For example, if Total Mesh Displacement X varies between 0 and 5 [m] on timestep 3, and varies between 0 and 3 [m] on the last timestep, then the global range will be shown in CFX-Post as 0 to 3 [m] rather than 0 to 5 [m]. If you change timestep to timestep 3, the global range will remain set to 0 to 3 [m], and any part of the plot where Total Mesh Displacement X takes a value above 3 [m] will be coloured as if it has a value of 3 [m].
A similar problem exists for components of any other vector variable (such as Velocity or any gradient vector), but only if Conservative boundary data is used for the plot. Since Hybrid boundary data is plotted by default, this will be seen less commonly. (Note that for Total Mesh Displacement the problem applies to both Conservative and Hybrid value plots.)
PROBLEM:
The CFX-Solver is not recording the correct global ranges for conservative values of any vector quantity. Total Mesh Displacement does not have any Hybrid data, so the Conservative data is used for all plots of t
|
WORKAROUND: Avoid using the Global range for any affected plot of a vector component, by using a Local range or User Specified range instead. FIXED IN: ANSYS CFX Release 12.0. |
||
|