Prescribe mesh motion from 2-way FSI

Lance · June 28, 2010, 11:01

Hi,
I've successfully run a 2-way FSI simulation with a RANS model and now I want to run the same simulation with LES instead. I imagine that LES-FSI would take forever to simulate, so to save some time I was thinking of taking the mesh deformation from the RANS model and prescribe it in the LES model, i.e. doing LES with 1-way FSI (with the assumption that the mesh deformation does not change significantly with turbulence model).
The thing is that I dont really know how to implement it. I guess some user CEL or Fortran is needed...?

So, is is possible to extract each node location at every time step from the RANS and then set it using "Specified Location" for the LES model? If so, does the time step size need to be the same for both simulations, or is it possible to interpolate the mesh location between time steps?

Lance

stumpy · June 28, 2010, 14:36

LES-FSI does indeed take a while, but it may still be a good option depending on the nature of your case. Firstly, it you are looking at vortex induced vibrations, then you can't use the 1-way assumption in any case. If you run LES-FSI your timestep is likely going to be small already. This means you typically don't need very many stagger/coupling iterations to converge the interface quantities - perhaps 3 at the most, assuming the under-relaxtion factor is 1, as it should be. If your structural mesh is small, then you might be only be looking at a 2x "slow down" compared to the fluids-only LES run. You might also consider explicit coupling (i.e. 1 stagger/coupling iteration per timestep), then you hardly have any slow-down, but it may or may not be stable.
If you do decide to use the approach you describe, then you can export Total Mesh Displacement X|Y|Z from Post for each timestep on the boundary of interest (script this step). You can import those files into CFX-Pre as a Profile Boundary then set your Total Mesh Displacement X|Y|Z equal to the profile boundary functions. That works well for a single profile, but in your case you have one profile per timestep. So I think reading in the profiles via Fortran is the best option, but you can still use the general Profile Boundary mechanism to set the displacements. The other problem is your LES timestep will be less than your RANS timestep, so you won't have enough profiles for the LES run.

Lance · June 29, 2010, 10:56

Thanks Stumpy for your input. I will consider the 2-way approach if I cant get the Fortran to work. For the timestep issue, I'll guess I can interpolate between two RANS timesteps to get the coordinates for the LES timestep.

Seems like it's gonna be a couple of weeks of Fortran then...

ghorrocks · June 29, 2010, 19:45

I remember in CFX V11 the ball valve example used fortran to read in some meshes. That might be a good starting point for you. I think the example was replaced with a purely CEL example in V12 so you will need to get hold of the V11 examples to see it.

Lance · July 1, 2010, 04:06

Hi Glenn,
yeah, I also remembered that, and it seems to be a good example to start from. Thanks.

June 28, 2010, 11:01	Prescribe mesh motion from 2-way FSI	#1
Lance Senior Member Lance Join Date: Mar 2009 Posts: 669 Rep Power: 22	Hi, I've successfully run a 2-way FSI simulation with a RANS model and now I want to run the same simulation with LES instead. I imagine that LES-FSI would take forever to simulate, so to save some time I was thinking of taking the mesh deformation from the RANS model and prescribe it in the LES model, i.e. doing LES with 1-way FSI (with the assumption that the mesh deformation does not change significantly with turbulence model). The thing is that I dont really know how to implement it. I guess some user CEL or Fortran is needed...? So, is is possible to extract each node location at every time step from the RANS and then set it using "Specified Location" for the LES model? If so, does the time step size need to be the same for both simulations, or is it possible to interpolate the mesh location between time steps? Lance

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Moving mesh part 2	lr103476	OpenFOAM Running, Solving & CFD	49	December 14, 2010 07:20
[snappyHexMesh] external flow with snappyHexMesh	chelvistero	OpenFOAM Meshing & Mesh Conversion	11	January 15, 2010 20:43
FSI mesh stiffness help	realanony87	Main CFD Forum	2	June 21, 2009 16:29
how to extend FSI 2D codes to 3D, need advises	abouziar	Main CFD Forum	1	May 30, 2008 05:08
large scale mesh motion	sb	FLUENT	1	April 27, 2007 23:23

June 28, 2010, 14:36		#2
stumpy Senior Member Join Date: Apr 2009 Posts: 531 Rep Power: 21	LES-FSI does indeed take a while, but it may still be a good option depending on the nature of your case. Firstly, it you are looking at vortex induced vibrations, then you can't use the 1-way assumption in any case. If you run LES-FSI your timestep is likely going to be small already. This means you typically don't need very many stagger/coupling iterations to converge the interface quantities - perhaps 3 at the most, assuming the under-relaxtion factor is 1, as it should be. If your structural mesh is small, then you might be only be looking at a 2x "slow down" compared to the fluids-only LES run. You might also consider explicit coupling (i.e. 1 stagger/coupling iteration per timestep), then you hardly have any slow-down, but it may or may not be stable. If you do decide to use the approach you describe, then you can export Total Mesh Displacement X\|Y\|Z from Post for each timestep on the boundary of interest (script this step). You can import those files into CFX-Pre as a Profile Boundary then set your Total Mesh Displacement X\|Y\|Z equal to the profile boundary functions. That works well for a single profile, but in your case you have one profile per timestep. So I think reading in the profiles via Fortran is the best option, but you can still use the general Profile Boundary mechanism to set the displacements. The other problem is your LES timestep will be less than your RANS timestep, so you won't have enough profiles for the LES run.

June 29, 2010, 10:56		#3
Lance Senior Member Lance Join Date: Mar 2009 Posts: 669 Rep Power: 22	Thanks Stumpy for your input. I will consider the 2-way approach if I cant get the Fortran to work. For the timestep issue, I'll guess I can interpolate between two RANS timesteps to get the coordinates for the LES timestep. Seems like it's gonna be a couple of weeks of Fortran then...

June 29, 2010, 19:45		#4
ghorrocks Super Moderator Glenn Horrocks Join Date: Mar 2009 Location: Sydney, Australia Posts: 17,871 Rep Power: 144	I remember in CFX V11 the ball valve example used fortran to read in some meshes. That might be a good starting point for you. I think the example was replaced with a purely CEL example in V12 so you will need to get hold of the V11 examples to see it.

July 1, 2010, 04:06		#5
Lance Senior Member Lance Join Date: Mar 2009 Posts: 669 Rep Power: 22	Hi Glenn, yeah, I also remembered that, and it seems to be a good example to start from. Thanks.