Problem of creating only cellZone (no faceZone) using snappyHexMesh
 

Hi,

It seems that I can create a cellZone using something like this:

However, the problem is that snappyHexMesh creates also a new boundary called heater and heater_slave, which I don't want to.

Even I set faceType as internal, I cannot avoid this problem.

So how can I create only a cellZone without add new boundaries?

Hi,

Try to remove the surface from the features subdictionary.

Also try to create an empty createPatch dictionary to clean up the patches

Hi,
I'm having snapping issues when trying something similar.

I have several searchablePlanes (parallel to each other) across my domain. I want the mesh to snap on all of those planes, but I don't need boundaries to be created.
Once the mesh is finished, I then remove all cells located below a plane of my choice (without having to remesh each time I need to split the mesh at a different height).
The problem with faceType internal; is that the planes are not properly snap. While if I use faceType baffle; the snap is good but I end up with walls across my domain.

Anyone knows how to get as good snap with faceType internal; as with faceType baffle;?

I can provide a small test-case if needed!
Thanks,
Eloïse

Hello Eloise,

I ve the same issue, however, if you remove "face type internal/baffle" command,and probably increase the refinement level of your block mesh dict, it might snap, i tried that first and it worked, but decomposing after mesh was an issue. and now that i am testing the case with the baffle or internal face type, the cell zones don't get properly refined. i don't know why

Hi,
I gave up exploring this option. I decided to insert a single searchable plane of type baffle in my mesh, and use this baffle to then split my mesh and keep only the side I'm interested in. I repeat the process if I want to split along another plane.
Regards,
Eloïse

Hi,

interesting, i haven't tried that option actually. i would look into that now, so i am guessing for a 3D mesh, a searchable box of type baffle might be the case. i will give it a try and provide update.

cheers