|
[Sponsors] |
Is there a conflict between DEFINE_PROFILE and DEFINE_GRID_MOTION? |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
November 14, 2019, 07:37 |
Is there a conflict between DEFINE_PROFILE and DEFINE_GRID_MOTION?
|
#1 |
New Member
You Wu
Join Date: Nov 2018
Posts: 16
Rep Power: 8 |
Hi,
I am writing a UDF with DEFINE_GRID_MOTION macro, and trying to update the boundary velocity every time step with DEFINE_PROFILE. What I do is define the moving boundary as moving wall in "boundary condition", and the motion is defined by components where l could use DEFINE_PROFILE. And then in "dynamic mesh" I choose "user-defined" type for the moving boundary. However, when I run calculation, no mesh motion is observed from both the animation and the displacement monitor. So I feel very confused. Here I have 3 questions: 1\Is there a conflict between DEFINE_PROFILE and DEFINE_GRID_MOTION? For instance when I'm using DEFINE_PROFILE,DEFINE_GRID_MOTION will not update the grid. 2\Whether DEFINE_GRID_MOTION itself can update the boundary velocity condition in each time step? If so, which boundary condition I should use on the moving boundary? And how can I monitor the boundary velocity in each time step? 3\If DEFINE_GRID_MOTION can not update the boundary velocity and I can't use DEFINE_PROFILE to update it either, does it have a great influence on the aerodynamic calculation results? I mean if I just use stationary wall type on a moving boundary, and DEFINE_GRID_MOTION for dynamic mesh, I do see the grid moving, but I doubt the accuracy of the result. Can anyone help me? Thank you in advance! Youwu |
|
Tags |
dynamic mesh |
|
|