CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > OpenFOAM > OpenFOAM Meshing & Mesh Conversion

[mesh manipulation] Create patches from a very complex geometry

Register Blogs Members List Search Today's Posts Mark Forums Read

Like Tree1Likes
  • 1 Post By fabian_roesler

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   January 8, 2015, 06:56
Post Create patches from a very complex geometry
  #1
New Member
 
Julie Correncon
Join Date: Oct 2014
Posts: 7
Rep Power: 11
CoSponge is on a distinguished road
Hello everybody,

I am wondering if it is possible to create patches and different region automatically from a .stl file.

For a simple geometry I tried to isolate the faces belonged to the different regions I'd like to have in the .stl file manually. It works perfectly
But now I have a very complex geometry, isolating the region is impossible by hand.

AutoPatch doesn't work, because it isolates some single points as a region (the mesh is not perfect) or the whole geometry, depending on the angle.

I know I could do it with the tool createPatches or making different blockMesh regions for each patch.

Does anyone knows the best option??

Thanks in avdance for the help,

Julie

Last edited by CoSponge; January 8, 2015 at 08:38.
CoSponge is offline   Reply With Quote

Old   January 9, 2015, 02:46
Default surfaceToPatch
  #2
Senior Member
 
Fabian Roesler
Join Date: Mar 2009
Location: Germany
Posts: 213
Rep Power: 18
fabian_roesler is on a distinguished road
Have you tried surfaceToPatch? With this tool you can identify faces close to a stl surface and automatically create a path out of them.

Cheers

Fabian
fumiya likes this.
fabian_roesler is offline   Reply With Quote

Old   January 12, 2015, 05:23
Default Error
  #3
New Member
 
Julie Correncon
Join Date: Oct 2014
Posts: 7
Rep Power: 11
CoSponge is on a distinguished road
Hey Fabian,

thank you a lot for your reply

I've tried, but I got this error:


// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Create polyMesh for time = 0

Reading surface from "pipe.stl" ...
Patching all boundary faces according to nearest surface triangle ...
All boundary faces further away than 0.001 of mesh bounding box (-0.04 -0.2 -0.15) (0.04 0.04 0.2) will keep their patch label ...
Before patching:
patch size
defaultFaces 34385



--> FOAM FATAL ERROR:
Cannnot read "pipe.stl"

From function triSurface::read(const fileName&, const word&, const bool)
in file triSurface/triSurface.C at line 369.

FOAM exiting

I should apply surfaceToPatch after snappyHexMesh, right?

Thanks in advance for the help,
greetings

Julie
CoSponge is offline   Reply With Quote

Old   January 13, 2015, 03:32
Default check the tutorials
  #4
Senior Member
 
Fabian Roesler
Join Date: Mar 2009
Location: Germany
Posts: 213
Rep Power: 18
fabian_roesler is on a distinguished road
When you're using snappy you can follow the chtMultiRegionFoam tutorials. They describe how to produce a multi region mesh with snappy. The basic work flow is the following:
  1. Create a single region mesh with cellZone for each region you want to create
  2. Run splitMeshRegions on the mesh (this will create the multi region mesh)
  3. Run changeDictionary to set the initial and boundary conditions for the regions
  4. Run the case
Cheers


Fabian
fabian_roesler is offline   Reply With Quote

Old   October 9, 2015, 13:32
Default splitMeshRegions patch naming convention
  #5
New Member
 
Gianluca
Join Date: Sep 2011
Location: Firenze, Italy
Posts: 11
Rep Power: 14
ninoleum is on a distinguished road
Hi foamers,
I don't know if the following is offtopic in this thread. If it is, I hope the moderator will move my post in a more suitable place.

I'm trying to set up a case similar to snappyMultiregionHeater. In my case there are three physical regions called "aria", "acqua" and "tubo_alettato" like in the attached pictures.
Similarly to the tutorial case the regions are coming from cellZones previously defined in SHMdict file.
When it comes the turn of "splitMeshRegions -cellZones" I got this a different behaviour in the interface patches naming scheme compared to the log of splitMeshRegions in snappyMultiregionHeater:

Code:
Adding patches

For interface between region domain0 and acqua added patches
    29	domain0_to_acqua
    30	acqua_to_domain0
For interface between region domain0 and aria added patches
    31	domain0_to_aria
    32	aria_to_domain0
For interface between region tubo_alettato and acqua added patches
    17	tubo_alettato_to_acqua
    18	tubo_alettato_to_acqua_slave
For interface between region aria and tubo_alettato added patches
    1	aria_to_tubo_alettato
    2	aria_to_tubo_alettato_slave
For interface between region domain0 and tubo_alettato added patches
    33	domain0_to_tubo_alettato
    34	tubo_alettato_to_domain0
i.e.: sometimes the rule patch1_to_patch2 in region "A" does not become patch2_to_patch1 in region B. Instead it becomes patch1_to_patch2_slave.
This would be an irrelevant matter if I had not already set up many other dictionaries following the scheme of mesh splitting snappyMultiregionHeater case.

Does anybody have an idea of the above behavior?
Thanks to every reader.

Gianluca
Attached Images
File Type: jpg aria_and_acqua.jpg (185.4 KB, 47 views)
File Type: jpg tubo_alettato.jpg (151.5 KB, 42 views)
ninoleum is offline   Reply With Quote

Reply

Tags
complex geometry, patches, regions, stl file

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
how to set periodic boundary conditions Ganesh FLUENT 15 November 18, 2020 07:09
Cyclic boundaries in OF 21x morard OpenFOAM 25 May 13, 2013 23:35
[ICEM] How to deal with a really complex geometry mountaineer ANSYS Meshing & Geometry 1 February 21, 2012 12:57
Actuator disk model audrich FLUENT 0 September 21, 2009 08:06
Where's the singularity/mesh flaw? audrich FLUENT 3 August 4, 2009 02:07


All times are GMT -4. The time now is 09:57.