Incompatible Kinematic Conditions

Radioss Starter will issue the following warning each time two nodal constraints are applied to the same set of nodes.

WARNING ID: 147
*** WARNING: INCOMPATIBLE KINEMATIC CONDITIONS
2 KINEMATIC CONDITIONS ON NODE xxxxxx,
IN DIRECTION TRANSLATION X, FOR:
- Nodal constraint 1 (e.g. BOUNDARY CONDITION)
- Nodal constraint 2 (e.g. RIGID WALL)

Radioss Starter does not check if the kinematic conditions are really incompatible. If they are strictly orthogonal, or if they are not applied simultaneously, just ignore the warning. Figure 1 illustrates two cases: in the first case, a node is secondary on a rigid wall and has a boundary condition in a non-orthogonal direction. If the rigid wall is fixed, there are no possible incompatible conditions (the node cannot impact on the wall). If the wall is moving, it is impossible after impact to respect both conditions. Therefore, the boundary condition is not applied and the reaction forces on the wall are incorrect. In the second case, a node is defined as a secondary for two parallel walls. If the two rigid walls are fixed, there are no possible incompatible conditions, as the node cannot impact the two walls at the same time. If one wall is moving, that results no problem, as long the moving wall is not crossing the fixed wall.

On a multi-processor Radioss version, a run executed twice can give different results if some kinematic conditions are incompatible. This is still true if option /PARITH/ON is being used. For example, if a secondary node impacting on two non-orthogonal rigid walls, as shown in Figure 2, the results obtained on a multi-processor can be arbitrary. If rigid wall 1 is computed before rigid wall 2, velocity V0 is replaced with velocity V12. If rigid wall 2 is computed before rigid wall 1, velocity V0 becomes V21. On multi-processor computers, the order in which rigid walls and other kinematic conditions are applied is arbitrary and can be changed from one cycle to the next and from one run to another.