|
[Sponsors] |
[mesh manipulation] Problem with mesh quality after using mergeMesh and stitchMesh |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
May 19, 2014, 06:52 |
Problem with mesh quality after using mergeMesh and stitchMesh
|
#1 |
New Member
Join Date: Mar 2014
Posts: 11
Rep Power: 12 |
Hey there,
for improving my IC engine simulations I want to connect a block structured cylinder mesh with a cylinderhead mesh created by snappy. My situation is the following: So far I'm doing my simulation with a mesh created by snappy and the deforming strategy for piston and valve motion. The problem is that the mesh quality decreases fast and I have to create a lot of meshes which needs a lot of computing time. My idea to improve this is to combine a block structured cylinder mesh with the cylinderhead mesh createdy with snappy. This approach would be only suitable for closed valves but it would decrease my computing time significantly beacause I could use the layer addition and removal strategy for the piston motion. What I've done so far: I created my meshes. The block structured cylinder with a patch for merging and the snapped cylinderhead mesh with the corresponding patch for merging. (screenshots) I merged these meshes with mergeMesh and stitched them with stitchMesh. For using stitchMesh I've tried several options. Default, -partial, -perfect, -toleranceDict and different values in the toleranceDict. But no matter which options I used the result contained some bad cells according to checkMesh ( non-Ortho, skewness). So I'm looking for a method to connect these two meshes without changing any of their vertices. Anyone got some idea for that? I dont know much about sliding interfaces or GGI I just heard about them. Would be one of them a possibility to solve my problem? Thanks in advance! With best regards Julian CylHead.jpg liner.jpg Last edited by julianschl; May 19, 2014 at 18:13. |
|
May 20, 2014, 03:28 |
|
#2 |
Senior Member
Hrvoje Jasak
Join Date: Mar 2009
Location: London, England
Posts: 1,907
Rep Power: 33 |
mergeMesh basically catenates all points, faces, cells from two pieces to make a single mesh. If yo built your mesh in pieces, this is the first step.
stitchMesh will connect all non-matching interfaces using the sliding interface, just like you need it. Non-orthogonality and mesh quality loss is minimal: in your case, cell size across the interface is very similar. I am happily running 50:1 cell interfaces and it works just fine. Enjoy, Hrv
__________________
Hrvoje Jasak Providing commercial FOAM/OpenFOAM and CFD Consulting: http://wikki.co.uk |
|
May 20, 2014, 06:07 |
|
#3 |
New Member
Join Date: Mar 2014
Posts: 11
Rep Power: 12 |
Thanks for your reply.
Thats what I've done it so far. I used mergeMeshes liner_case cylinderhead_cyse and stitchMesh -overwrite -partial masterpatch_liner slavepatch_cylhead It works without any error! However checkMesh shows an increased number of highly skew faces (20 to be exactly) and in paraview the mesh doesnt look like I expect it to be. I attached two screenshots. One with activated decompose polyhedra option in paraview and one without decomposing. It looks like the vertices are stitched which is what I expect that stitchMesh does. But I dont want it to stitch the vertices. Do I have to set really low tolerance values in a toleranceDict to solve my problem? /edit: The default tolerance values: pointMergeTol : 0.05 edgeMergeTol : 0.01 nFacesPerSlaveEdge : 5 edgeFaceEscapeLimit : 10 integralAdjTol : 0.05 edgeMasterCatchFraction : 0.4 edgeCoPlanarTol : 0.8 edgeEndCutoffTol : 0.0001 I'm getting errors when I try to use low values for point- and edgeMergeTol with the other values as default. Stitched1.jpgStitched2.jpg |
|
May 20, 2014, 23:55 |
|
#4 | |
New Member
Josh
Join Date: Jun 2013
Posts: 19
Rep Power: 13 |
Quote:
|
||
May 28, 2014, 11:50 |
|
#5 |
New Member
Join Date: Mar 2014
Posts: 11
Rep Power: 12 |
I managed to solve my problem.
It seems that the patch of the slave mesh has to be within the patch of the master mesh. As you can see in the screenshots above the Cylinderhead (slave mesh) had a slightly bigger diameter than my liner mesh (the master mesh). Changing this solved my problem. No more skew faces created by stitchMesh. |
|
June 2, 2014, 02:59 |
|
#6 |
New Member
Join Date: Mar 2014
Posts: 11
Rep Power: 12 |
Seems like I should have had a closer look inside my mesh before reporting about a success..
enginetopomesher aborted with thousands of skew and non-ortho faces in the last part of the deforming phase. It looks like stitchMesh still connects some of the verties inside my mesh like the screenshot shows. Any idea which tolerance values help me avoiding this? Stitched3.jpg |
|
September 16, 2014, 11:22 |
|
#7 |
Member
Pratik Nanavati
Join Date: May 2014
Location: Munich, Germany
Posts: 40
Rep Power: 12 |
||
May 23, 2015, 13:42 |
|
#8 |
Senior Member
Dongyue Li
Join Date: Jun 2012
Location: Beijing, China
Posts: 849
Rep Power: 18 |
lamo,
usually I feel monotonous, tedious when I read some threads with no feelings. Then u made me spray rice out of my month into the screen. I really need to simulate how to spray those tiny rices elegantly. |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
MergeMesh and stitchMesh | lr103476 | OpenFOAM Running, Solving & CFD | 42 | September 10, 2020 08:31 |
[mesh manipulation] stitchMesh -perfect - tolerance error of 2 identical faces | Hanno | OpenFOAM Meshing & Mesh Conversion | 1 | November 21, 2013 06:41 |
[mesh manipulation] stitchMesh problems along patch edges | ribe | OpenFOAM Meshing & Mesh Conversion | 2 | March 5, 2013 16:25 |
[mesh manipulation] Mesh Manipulation Issues | vishalsacharya | OpenFOAM Meshing & Mesh Conversion | 2 | November 24, 2012 00:36 |