dynamicMotionSolverFvMeshAMI with 6DoF motion

benchwell · March 4, 2022, 06:28

Dear Foamers,

in the past, I have successfully set up the sixDoFRigidBodyMotion solver with AMI patches to separate a rotating cell region from a static surrounding.

Now I wanted to make use of the improved numerics implemented in dynamicMotionSolverFvMeshAMI. Now when I use sixDoFRigidBodyMotion as motionSolver, nothing happens.

I traced this to this particular change:

dynamicMotionSolverFvMesh.C

Code:

fvMesh::movePoints(motionPtr_->newPoints());

dynamicMotionSolverFvMeshAMI.C

Code:

pointField newPoints(motionPtr_->curPoints());

if(changeRequired
{
    [...]
    polyTopo.movePoints(newPoints); 
}
else
{
    fvMesh::movePoints(newPoints);
}

Why would the field be called newPoints if it uses the current points? Is this meant to be that way or faulty? When I change the call to

dynamicMotionSolverFvMeshAMI.C

Code:

pointField newPoints(motionPtr_->newPoints());

It does use the sixDoFRigidBodyMotion as intended.

Maybe someone can elaborate on the improved numerics, too, as I don't really understand, what's happening there.

Kind regards,
Felix

quarkz · August 18, 2023, 03:23

Hi benchwell,

Did you manage to find your ans? I wonder if the reason the sixDOF did not work is because the new AMI with topological changes is not absorbed into the standard dynamicMotionSolverFvMesh model?

Btw, you mentioned that you change the dynamicMotionSolverFvMeshAMI.C.

So did you create a new dynamicMotionSolverFvMeshAMI model and re-compile it?

And the sixDOF worked w/o any problem after that?

Thanks.

March 4, 2022, 06:28	dynamicMotionSolverFvMeshAMI with 6DoF motion	#1
benchwell New Member Felix Weiler Join Date: Nov 2016 Location: Bremen Posts: 22 Rep Power: 9	Dear Foamers, in the past, I have successfully set up the sixDoFRigidBodyMotion solver with AMI patches to separate a rotating cell region from a static surrounding. Now I wanted to make use of the improved numerics implemented in dynamicMotionSolverFvMeshAMI. Now when I use sixDoFRigidBodyMotion as motionSolver, nothing happens. I traced this to this particular change: dynamicMotionSolverFvMesh.C Code: fvMesh::movePoints(motionPtr_->newPoints()); dynamicMotionSolverFvMeshAMI.C Code: pointField newPoints(motionPtr_->curPoints()); if(changeRequired { [...] polyTopo.movePoints(newPoints); } else { fvMesh::movePoints(newPoints); } Why would the field be called newPoints if it uses the current points? Is this meant to be that way or faulty? When I change the call to dynamicMotionSolverFvMeshAMI.C Code: pointField newPoints(motionPtr_->newPoints()); It does use the sixDoFRigidBodyMotion as intended. Maybe someone can elaborate on the improved numerics, too, as I don't really understand, what's happening there. Kind regards, Felix Last edited by benchwell; March 4, 2022 at 06:29. Reason: Added file names for clarity

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Use of a laplacian mesh motion solver with the 6DoF or rigidBodyMotion libraries	tecmul	OpenFOAM Running, Solving & CFD	8	February 11, 2022 10:59
6DOF for spring valve motion problem	ahehuhehuh	Fluent UDF and Scheme Programming	2	April 18, 2018 15:39
Error in flow driven motion using cyclicAMI and 6DoF	ashish.kumar	OpenFOAM Running, Solving & CFD	0	August 27, 2017 10:43
How to use "translation" in solidBodyMotionFunction in OpenFOAM	rupesh_w	OpenFOAM Running, Solving & CFD	5	August 16, 2016 04:27
External management of solid motion (using dynamicmesh)	maxou1993	Main CFD Forum	0	July 28, 2015 11:37

August 18, 2023, 03:23		#2
quarkz Senior Member TWB Join Date: Mar 2009 Posts: 403 Rep Power: 19	Hi benchwell, Did you manage to find your ans? I wonder if the reason the sixDOF did not work is because the new AMI with topological changes is not absorbed into the standard dynamicMotionSolverFvMesh model? Btw, you mentioned that you change the dynamicMotionSolverFvMeshAMI.C. So did you create a new dynamicMotionSolverFvMeshAMI model and re-compile it? And the sixDOF worked w/o any problem after that? Thanks.