View Revisions: Issue #3494

Summary 0003494: Wrong displacement accumulation in motionSolverList
Revision 2020-05-12 17:45 by henry
Steps To Reproduce Applying two or more different solvers in dynamicMeshDict with non-zero displacement components may already cause the issue. The attatched example case illustrates the displacement miscalculation, and can be run by tiping:

1. blockMesh
2. moveDynamicMesh
3. paraFoam

In the attatched file case, which presents constant mesh movement speed for both x and y axis, points in the mesh should be moved 0.2 m in both x and y directions for every 1 s time step. Instead, the mesh is moved in the expected direction and with desired displacement variation, but only in alternated time steps. During the other time steps, the mesh is kept almost unchanged, hence halving the expected total displacement for a larger number of time steps. In more complex movement cases, the mesh is moved in more unpredictable ways.
Revision 2020-05-12 03:16 by rmoreira
Steps To Reproduce Applying two or more different solvers in dynamicMeshDict with non-zero displacement components may already cause the issue. The attatched example case illustrates the displacement miscalculation, and can be run by tiping:

1. blockMesh
2. moveDynamicMesh
3. paraFoam

In the attatched file case, which presents constant mesh movement speed for both x and y axis, points in the mesh should be moved 0.2 m in both x and y directions for every 1 s time step. Instead, the mesh is moved in the expected direction and with desired displacement variation, but only in alternated time steps. During the other time steps, the mesh is kept almost unchanged, hence halving the expected total displacement for a larger number of time steps. In more complex movement cases, the mesh is moved in more unpredictable ways.