[blockMesh] When should I use mergePatchPairs?

yadongh · April 5, 2016, 20:49

Dear friends,

I am quite new to OpenFoam, and self-training myself via the user guide templates.

In the first template example, the 'Lid driven cavity', there is a part on the 'Graded mesh', where the the domain is divided into four block with different grading in each block. I can understand the 'blockMeshDict' file well except the last part, which is the 'mergePatchPairs'.

Why is this part blank? According to the later part of the manual, since we have four blocks, shouldn't the mergePatchPairs be used to deal with the connections between blocks? Or this means under some circumstances, this is not necessary?

Thanks a lot for any help!

Yadong

aow · May 31, 2018, 22:58

I'm assuming by now you figured it out, but for anyone else running across this post I'll give a short explanation.

The mergePatchPairs option is an alternative to the default method of "face matching" where nodes and mesh cells line up exactly (i.e. the numbers of cells in x and y directions on each face that is touching are the same for both faces and the corner nodes are the same too). In such a circumstance, you don't need to specify any additional face merging. This means you only need to use the mergePatchPairs when either the cell numbers don't match or the nodes aren't the same from one block (or hex as they're called in blockMeshDict) to another.

April 5, 2016, 20:49	When should I use mergePatchPairs?	#1
yadongh New Member Join Date: Apr 2016 Posts: 1 Rep Power: 0	Dear friends, I am quite new to OpenFoam, and self-training myself via the user guide templates. In the first template example, the 'Lid driven cavity', there is a part on the 'Graded mesh', where the the domain is divided into four block with different grading in each block. I can understand the 'blockMeshDict' file well except the last part, which is the 'mergePatchPairs'. Why is this part blank? According to the later part of the manual, since we have four blocks, shouldn't the mergePatchPairs be used to deal with the connections between blocks? Or this means under some circumstances, this is not necessary? Thanks a lot for any help! Yadong

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[blockMesh] mergePatchPairs problem when migrating from OFext1.6 to OFext3.1	ma-tri-x	OpenFOAM Meshing & Mesh Conversion	2	January 12, 2021 05:23
[blockMesh] mergePatchPairs reducing a face to less than 3 points	aow	OpenFOAM Meshing & Mesh Conversion	2	June 1, 2018 18:37
[mesh manipulation] mergePatchPairs with multiple areas	bjoern1	OpenFOAM Meshing & Mesh Conversion	1	October 1, 2015 08:07
[blockMesh] 2:1 refined 2D blockMeshDict with mergePatchPairs?	chrisb2244	OpenFOAM Meshing & Mesh Conversion	0	December 2, 2014 00:52
[blockMesh] mergePatchPairs vs stitchMesh	pg22	OpenFOAM Meshing & Mesh Conversion	1	March 10, 2010 06:50

May 31, 2018, 22:58		#2
aow Member Andrew O. Winter Join Date: Aug 2015 Location: Seattle, WA, USA Posts: 78 Rep Power: 11	I'm assuming by now you figured it out, but for anyone else running across this post I'll give a short explanation. The mergePatchPairs option is an alternative to the default method of "face matching" where nodes and mesh cells line up exactly (i.e. the numbers of cells in x and y directions on each face that is touching are the same for both faces and the corner nodes are the same too). In such a circumstance, you don't need to specify any additional face merging. This means you only need to use the mergePatchPairs when either the cell numbers don't match or the nodes aren't the same from one block (or hex as they're called in blockMeshDict) to another.