[SD@TUB]

Dear FOAMers,

after searching the whole morning for an appropriate way to delete internal patches within this forum, i've decided to open a new thread according to this!
After chaining several grids together via mergeMeshes w/o stitchMesh, the associated interfaces will be left in the polyMesh description (e.g. boundary file). What would be the smartest procedure to remove them (just deleting the patches in the ./constant/polyMesh/boundary file isn't a good idea)? They aren't needed anymore, hence i don't want to specify a boundary condition for these internal patches!

Thanks in advance for helpful hints!
/Stefan

[stevenvanharen]

Just deleting is not a good idea. Just use stitchMesh.

After using stitchMesh you will see the boundaries are still present in the boundary file bu they will contain 0 faces. You can just delete them from this file in this case (don't forget to change the number of boundaries at the top of the boundary file).

[SD@TUB]

Thanks Steven,

but what about the following issue?
When joining two grids where the connecting interface is named equally, mergeMeshes will leave this interface in the boundary file. It is obvious that this patch will consist of several faces, points, etc. In this
case stitchMesh will not work, because the need of <masterPatch> and <slavePatch>. Selecting this interface for master and slave will cause an error:

--> FOAM FATAL ERROR:
Zero length edge detected. Probable projection error: slave patch probably does project onto master.

Is it possible to delete interfaces in the above-mentioned scenario?


/Stefan
BTW: I am using version 1.7.x !

[stevenvanharen]

I also had this problem.

I don't fully remember how I fixed it. I know I manually changed the names of the boundaries to not have two boundaries with the same name.

I think I did this before using mergeMeshes but I am not fully sure. But I suggest you try this.

[prashant.A]

Well, its possible.
I would prefer stitchMesh, just because of the fact that mergeMeshes would also make one zone out of two which is sometimes not desired..

Remember a few things:

1. Before you "stitchMesh", move all the *Zones files to bak
2. After you have done "stitchMesh" successfully, a faceZone should appear with a name combination of the parts you have stitched. However, these bounday names still exist in the "boundary" file which need to be removed manually.
2. A new cellZone will be created, which you can conveniently ignore. Move cellZones.bak to cellZones so that you still have the different zone info intact in your mesh.
4. Run "checkMesh" once to ascertain that you followed all the steps correct !

Write back if you still see any issues...I hope I haven't missed anything in this regard.

[SD@TUB]

Terminating, stitchMesh plus removing the empty patches afterwards in the boundary file by hand seems to be the only way at the very least. The connecting interfaces from different grids have to be named differently! Thats a bit inconvenient. Maybe in future mergeMeshes would get an additionally option that simplify merging several grids.

/Stefan

[prashant.A]

Okay, I understand your problem. You can rename these interfaces in the boundary file itself, i.e. you need not go back to the mesher to be changed in the native format.

[Rebecca513]

Hi Stefan,

I am also trying to use stitchMesh to remove internal faces. I used extrudeMesh first, then merged the extruded and original meshes. And now I need to remove the generated internal patches.

But I keep getting the error message saying that 'Duplicate point found in cut face'. I wonder how you used this utility.

Any comment and suggestion is appreciated.

Thank you!

Originally Posted by SD@TUB

Terminating, stitchMesh plus removing the empty patches afterwards in the boundary file by hand seems to be the only way at the very least. The connecting interfaces from different grids have to be named differently! Thats a bit inconvenient. Maybe in future mergeMeshes would get an additionally option that simplify merging several grids.

/Stefan

[SD@TUB]

Hi Rebecca,

Did you use stitchMesh -perfect flag? I guess not from your posted error message...
You can use attachMesh for deleting internal faces after stitching (see if a file meshModifiers exist within constant/polyMesh directory.

Hope that helps!


Stefan

[Rebecca513]

Hi Stefan,

Thank you for your reply. Yes I tried -perfect flag, then it works OK. Also, thank you for the suggestion on using attachMesh~But at this stage, it seems that after stitchMesh the faces become empty, and I could manually delete them.

Best,

[Attesz]

Hi all,

I've problems with stitchMesh. I have 3 domains, with duplicate interfaces but the mesh points are coincident. When I want to stitch the interfaces using the -perfect option, i'm getting the following error message:

--> FOAM FATAL ERROR:
Problem : Patch AMI_INROT1 starts at 33776699
Current face counter at 33704048
Are patches in incremental order?

From function polyTopoChange:olyTopoChange(const polyMesh& mesh, const bool strict)
in file polyTopoChange/polyTopoChange/polyTopoChange.C at line 2459.

FOAM aborting

If I renumber the faces as it is said by OF, it seems to be working but why is it occurs?

Best,
Attila

[ebah6]

Hello Attila,

I have a similar problem with pimpleDyMFoam.

-------------------------------------
--> FOAM FATAL ERROR:
Problem : Patch AMI1 starts at 1756182
Current face counter at 213326
Are patches in incremental order?

From function polyTopoChange:olyTopoChange(const polyMesh& mesh, const bool strict)
in file polyTopoChange/polyTopoChange/polyTopoChange.C at line 2459.

FOAM aborting
--------------------------

were you able to solve this problem?

Thanks for you help.

[ebah6]

Hello everyone,

I think my problem is coming from the fact that snappyHexMesh is creating patches with nFaces=0 as below:

-----------------
blenderBlades
{
type wall;
nFaces 0;
startFace 211046;
}
blenderAMI
{
type wall;
nFaces 0;
startFace 211046;
}
-----------------------------

can someone help with this issue?
Thank in advance; any help is greatly appreciated.

[Attesz]

Hi I generated the mesh in ICEM CFD, using 1 common face as internal patch. Then, I exported the stator and rotor parts separately. After that I used the fluent3DMeshToFoam app to convert it to OF format, and then I did mergeMeshes to put them together. Now it works fine. You need two patches at the same position, or you should cut your mesh there. Also it is possible for you to generate your mesh separately with snappy and then merge them.

[louisgag]

ebah6:

If you are running your case based on a modification of the propeller tutorial, you need to adjust the starting faces for both AMI faces of the boundary file prior to running createBaffles. This is mandatory and unfortunately not taken care of by the tutorial, which will thus only work for the specific mesh given.

You can automate this process by running a command right before changeDictionary. Or if you use snappyHexMesh in a similar fashion than in the tutorial, automate the process by modifying the Allrun.pre file as follows,

# - create the inlet/outlet patches

runApplication createPatch -overwrite

# - fix the startFace value in changeDictionaryDict

AMI_startFace=`cat log.snappyHexMesh|grep "Snapped mesh"|sed s/^.*faces://|sed s/"  points.*$"//`
sed -i s/"startFace       0;"/"startFace       $AMI_startFace;"/g system/changeDictionaryDict

# - create the AMI faces by creating baffles, and then splitting the mesh

runApplication changeDictionary

(Notice that my changeDictionaryDict file initially has both startValue = 0; I think this should be added to the tutorial...


-Louis

[ebah6]

Thanks Louis.

[anufagbemi]

Dear foamers,
I am performing a fluid structure interaction problem in a porous media from McT images which consists of both the solid and fluid domains. Where the solid is just an inversion of the fluid domain. I'm trying to mesh objects based on stl files by using snappyHexMesh as follows:

1. blockMesh operation
2. snappyHexMesh operation
3. SplitMeshRegions -cellZones -overwrite

Unfortunately some fragments form. I can't delete the fragments because they help ensure conformity at the interface. Otherwise I'll be having a "Master point Addressing" problem. You can find my preProcessing case file here https://yadi.sk/d/yXwpAv8_3Ry3W7
If you observe in the FLUID "boundary" file I'm supposed to just have the inlet, outlet, wall and interface conditions but there is an extra patch represents the fragments named "Out"

5
(
    Out
    {
        type            patch;
        nFaces          322;
        startFace       1101291;
    }
    inlet
    {
        type            patch;
        nFaces          8889;
        startFace       1101613;
    }
    outlet
    {
        type            wall;
        inGroups        1(wall);
        nFaces          6859;
        startFace       1110502;
    }
    wall
    {
        type            wall;
        inGroups        1(wall);
        nFaces          23046;
        startFace       1117361;
    }
    domain0_to_SOLID
    {
        type            mappedWall;
        inGroups        1(wall);
        nFaces          148834;
        startFace       1140407;
        sampleMode      nearestPatchFace;
        sampleRegion    SOLID;
        samplePatch     SOLID_to_domain0;
    }
)

And similar for the SOLID folder.

I've tried to stitch those fragments using both stitchMesh and stitchMesh -partial, but none seemed to be working.

Please can anyone help or show me another method to achieve this?

Thanks
Samuel

[VarunG]

Dear Attesz,



Can you please explain how did you renumber the faces ?




Thank you
Varun