[mesh manipulation] How to separate frontAndBack

xuegy · January 25, 2021, 23:20

Hello all,

I have a 2D mesh from fluent. When I run fluentMeshToFoam, it is automatically converted to a single layer 3D mesh. The front and back planes are combined in a single patch named "frontAndBackPlanes".
There is a tutorial that splits the boundary patch: patch splitting for different boundary conditions However, since "front" and "back" patches share the same cell, this trick doesn't work.
I know that the ultimate solution is to make a single-layer 3D mesh in fluent but is there any workaround to do it within OpenFOAM?

Thanks!

simrego · January 26, 2021, 09:51

Hi!

Maybe it is a silly question, but why do you need to split it? 2D mesh -> front and back are empty, and you will need the same BCs there.
Also you shouldn't evaluate anything there so I think there is no reason for that.

BTW: check the topoSet and createPatch utlities.

xuegy · January 26, 2021, 10:42

Quote:

Originally Posted by simrego

Hi!

Maybe it is a silly question, but why do you need to split it? 2D mesh -> front and back are empty, and you will need the same BCs there.
Also you shouldn't evaluate anything there so I think there is no reason for that.

BTW: check the topoSet and createPatch utlities.

I need to use extrudeMesh to generate a 3D pipe from the cross-section. That’s why I want a separate face.
Or is there anyway to get a 2D face patch from Fluent directly?

simrego · January 26, 2021, 10:53

Well. Then it would be nicer to do it with blockMesh.
As I know you can't do it. So it this case I would go with topoSet+createPatch and extrude that patch.
Or simply do it in fluent which is the easiest way.

And as you originally asked:
"is there any workaround to do it within OpenFOAM?"
Yes, there is a workaround for nearly everything in OpenFOAM, but in the worst case you have to code a little.

January 25, 2021, 23:20	How to separate frontAndBack	#1
xuegy Member Join Date: Jun 2016 Posts: 97 Rep Power: 8	Hello all, I have a 2D mesh from fluent. When I run fluentMeshToFoam, it is automatically converted to a single layer 3D mesh. The front and back planes are combined in a single patch named "frontAndBackPlanes". There is a tutorial that splits the boundary patch: patch splitting for different boundary conditions However, since "front" and "back" patches share the same cell, this trick doesn't work. I know that the ultimate solution is to make a single-layer 3D mesh in fluent but is there any workaround to do it within OpenFOAM? Thanks!

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Running multiple separate Serial runs on separate cores	FlyBoy38L	SU2	0	July 1, 2019 13:48
Separate cells by IsoSurface?	vidyadhar	FLUENT	1	June 18, 2019 08:15
Two-sided Wall Heat Transfer BC - No Separate Solid Mesh and No Heat Transfer Coeff	swahono	OpenFOAM Running, Solving & CFD	10	October 15, 2018 05:43
[DesignModeler] Creating Two Separate Bodies in Design Modeller	ashtonJ	ANSYS Meshing & Geometry	39	June 6, 2018 17:31
[Commercial meshers] import two separate gambit mesh file for solid and fluid regions	rapierrz	OpenFOAM Meshing & Mesh Conversion	0	December 31, 2015 10:26

January 26, 2021, 09:51		#2
simrego Senior Member anonymous Join Date: Jan 2016 Posts: 416 Rep Power: 13	Hi! Maybe it is a silly question, but why do you need to split it? 2D mesh -> front and back are empty, and you will need the same BCs there. Also you shouldn't evaluate anything there so I think there is no reason for that. BTW: check the topoSet and createPatch utlities.

January 26, 2021, 10:53		#4
simrego Senior Member anonymous Join Date: Jan 2016 Posts: 416 Rep Power: 13	Well. Then it would be nicer to do it with blockMesh. As I know you can't do it. So it this case I would go with topoSet+createPatch and extrude that patch. Or simply do it in fluent which is the easiest way. And as you originally asked: "is there any workaround to do it within OpenFOAM?" Yes, there is a workaround for nearly everything in OpenFOAM, but in the worst case you have to code a little.