[louisgag]

Hi everyone,
I'm creating a mesh using snappyHexMesh and one of the stl files I use to define the refinement levels should not create a patch (but rather only be used to refine the region). Is that possible?
I tried various approaches, and also stitchMesh/mergeMesh and deleting the patch from the boundary file, but nothing does it. At best my refinement region gets totally ignored.
Regards,
-Louis

[mwaqas]

Hello Louis,
There are couple of things you can do.
It is strange that your refinement region gets ignored. Double check, the coordinates of your refinement region and also have a look on example tutorial to use refinement region correctly. I used it many time and I don't see any reason for it getting ignored.
If you are using stl file to refine mesh, you can use createPatchDict to combine it with neighboring patch.

pointSync false;

// Patches to create.
patches
(
{
// Name of new patch
name solid_4_to_top_4;

// Dictionary to construct new patch from
patchInfo
{
type mappedWall; // can be wall or patch
neighbourPatch wall;
sampleMode nearestPatchFace;
sampleRegion top_4;
samplePatch top_4_to_solid_4;
offset (0.000001 0.000001 0.000001);

}

// How to construct: either from 'patches' or 'set'
constructFrom patches;

// If constructFrom = patches : names of patches. Wildcards allowed.
patches (patch1 patch2);

}
);

[louisgag]

Hi Muhammad,
Thank you for your reply.
I was not clear enough: my region gets refined without problem (with stl or boxes/cylinders/etc).
My issue is that it always creates a patch in correspondence to the stl file's geometry and I don't want that patch!
Kind regards,
-Louis

[mwaqas]

Hello Loius,


I understood what your concern is.


First of all, I never tried this approach (stl file only for refinement purpose without creating patch).

You can try by using same name of two stl patches that you want to combine (I am not sure about it as I never tried this). It might work.

geometry
{
patch1.stl { type triSurfaceMesh; name patch1; }

patch2.stl { type triSurfaceMesh; name patch1; }

patch3.stl { type triSurfaceMesh; name patch3; }

};

The best approach is to use single stl file for patches and use searchable region for refinement


Regards

[apostolos]

you probably figured it out by now, but the answer is that you should only use your .stl at the refinementRegion entrance and ignore the refinementSurface one

[louisgag]

thanks for the tip, but I am pretty certain that this method will only create a refinement region and no "snapped" surface. I wanted the snapped surface without a patch while I was comparing a case with AMI to one without.

[bennn]

Again, a little late to the party, but I'd say best practice in AMI case is to create two geometry files base on a common rotating boundary, then create two separate meshes, and eventually merge the two meshes into a single case.


I have never seen an AMI case where the meshing is done in a single step.

[wouterremmerie]

We tried something similar and in the end it worked by doing this:

At the beginning, when declaring the geometry:

object.stl
{
type triSurfaceMesh;
object;
}


Under surface refinement:

object
faceType internal;
faceZone object_zone;


It creates 2 complementary patches, but they are not seen as a real wall.
Not sure if the faces actually match. If that's required, you could consider using faceType baffle instead?

Hope it helps!