KNOWN ISSUE: Monitored torques may be incorrect on the first timestep or iteration after a restart (Class 3 Error)


SYMPTOM:
If a case which includes a monitor of torque is restarted, then the monitored values of torque are calculated incorrectly the first time that the monitor is evaluated, if the torque is calculated in any coordinate frame other than the global one (Coord 0). For steady state runs this implies that the monitored value of torque will be incorrect in the first iteration after the restart. For transient runs with the default monitoring settings, this implies that the monitored value of torque will be incorrect at the end of the first timestep after the restart. However, for transient runs where the monitoring settings enable "Monitor Coefficient Loop Convergence", then the monitored value of torque will be incorrect only at the end of the first coefficient loop and correct again by the end of the timestep, assuming that the timestep does more than one coefficient loop and is properly converged.

PROBLEM:
The CFX-Solver needs to evaluate the force in order to transform the torque into the specified coordinate frame, and the force calculation is not being updated correctly when it is only triggered by the torque evaluation.

WORKAROUND:
No workaround is currently available.

FIXED IN:
ANSYS CFX Release 13.0. A custom executable for ANSYS CFX Release 12.1 is available on request.





Show Form
No comments yet. Be the first to add a comment!