|
|
Reporter | maHein | Assigned To | henry | |
---|
Priority | normal | Severity | minor | Reproducibility | always |
---|
Status | closed | Resolution | suspended | |
---|
Platform | GNU/Linux | OS | Other | OS Version | (please specify) |
---|
Product Version | 13 | |
---|
|
|
Summary | 0004267: meshToMesh: Using 'fixedValue' for pointMotion not mapped correctly |
---|
Description | When a motionSolver is used for mesh deformation, the displacement or velocity at the patches must be specified (for example via 'pointMotionU' file in 0 directory). However, when this functionality is used together with the meshToMesh topoChanger, the corresponding boundary values in 'pointMotionU' are not correctly mapped, if a fixedValue type boundary condition is used. In contrast, a uniformFixedValue boudary condition works flawless.
|
---|
Steps To Reproduce | Take the 'shockFluid/movingCone' tutorial case and change the boundary condition of 'pointMotionUx' for the patches 'movingWall' and 'farFieldMoving' from uniformFixedValue to fixedValue with the same value of now 'value uniform 150'. At first, the mesh moves correctly. However, as soon as the first meshToMesh interpolation takes place, the mesh movement stops. The reason is that the values for the boundaries in pointMotionUx are suddenly set to zero. |
---|
Tags | No tags attached. |
---|
|
|