Class 3 Error

SYMPTOM:
If a callback (for example torque) is used in a part of the set-up of a problem where a local coordinate frame is in use, then the callback is evaluated in global coordinates.

PROBLEM:
This is a problem of software design as this behaviour was always intended and is documented, but is non-intuitive


WORKAROUND:
The user needs to modify settings to allow for this behaviour.

FIXED IN:
Release 11.0. In this release, torque_xyz(), area_xyz() and force_xyz() are now evaluated in the local coordinate frame of where they are used (Boundary Condition, Subdomain, Monitor Point, etc.).





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