using blockMesh - defaultFaces
Hi to All!
could anybody support me to generate a hexmesh with blockMesh: channel with obstacle in the centre. http://up.picr.de/17331261jr.jpg I've created the mesh composing of 18 blocks. Result: 4 defaultFaces (faded in the picture --> redundant plane). Inlet is the leftmost plane, outlet rightmost plane, right wall is turned off in the pic, obstacle in the centre. How can I remove these defaultFaces? If I start the simulation converges very (too) fast, the result is wrong, the solver does not solve for Uz (but for Ux and Uy). The same case works perfectly if I disclaim the obstacle and create a very simple mesh (1 block) instead. Each time I create a mesh with blockMesh with undefined faces (wherever they come from) the simulation produces wrong results and paraFoam crashes if I try to view the mesh or the final reconstructed result from parallel run. Please advice! Aylalisa |
could you post your case along with the blockmesh dictionary please? Also, do you have any errosr/warnings when paraview crashes?
|
Hi,
defaultFaces is a patch where faces that do not belong to any patch go. I.e. to remove them you have to define these patches in boundary section of blockMeshDict and maybe then use mergePatchPairs to get rid of those additional patches. And yes, as pervious poster said it would be much easier to help you if you post your blockMeshDict. |
Hi Thangam, Hi alexeym,
with that case I wanted to test if it is possible to subdivide a domain with blockMesh in arbitrary number of blocks. Code:
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // Each time I unintentionally create default faces the solver only solves for certain components of u! In this case: Uz is omitted. Why? If the node coordinates are correctly defined there should not appear any default faces. Ayla |
Hi,
All faces that are not described in your boundary sub-dictionary of blockMeshDict go to defaultFaces. By default type of this boundary is empty, so there are no boundary conditions on the patch, and that is why you've got problems with velocities. In your case I've found duplicate vertices in blockMeshDict (43 and 48 for example, actually I've stopped after I found this pair, maybe there are more), so when you describe your blocks there appear two faces (though in paraview they look like one face) that can not be automatically merged by blockMesh (actually blockMesh thinks you've done this intentionally to have a wall inside domain). So they go to defaultFaces as you did not describe this faces in boundary sub-dictionary. I'd suggest Gmsh for the mesh as there it is easy to avoid this type of errors (and yes, it can build hexagonal meshes with transfinite algorithm). |
All times are GMT -4. The time now is 16:00. |