|
[Sponsors] |
|
January 13, 2012, 08:28 |
STL file
|
#1 |
Senior Member
stephane sanchi
Join Date: Mar 2009
Posts: 314
Rep Power: 18 |
Hi,
I have problem with newly created STL files. I use OF-2.1.x. I have created an STL file with ICEMCFD version 13. But SHM doesn't see any patch: Adding patches for surface regions ---------------------------------- Patch Type Region ----- ---- ------ Added patches in = 0 s Has someone encountered same kind of problem recently. Best regards, Stephane |
|
January 15, 2012, 08:53 |
|
#2 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,978
Blog Entries: 45
Rep Power: 128 |
Hi Stephane,
OK, there are several reasons why this might have happened:
Best regards, Bruno
__________________
|
|
January 16, 2012, 04:19 |
|
#3 |
Senior Member
stephane sanchi
Join Date: Mar 2009
Posts: 314
Rep Power: 18 |
Hi Bruno,
None of your proposals solve my problem. It is strange because when I use the surfaceFeatureExtract command to extract the edges sHM see the edges (and do the refinement). But sHM still doesn't any patch so it can't delete any cells inside or outside. Best regards, Stephane. |
|
January 16, 2012, 05:24 |
|
#4 |
Senior Member
stephane sanchi
Join Date: Mar 2009
Posts: 314
Rep Power: 18 |
Hi Bruno,
If I write as below sHM see the patch: geometry { flange.stl { type triSurfaceMesh; name flange; } }; But if I write as below sHM doesn't see any patch: geometry { flange.stl { type triSurfaceMesh; regions { FLANGE// Named region in the STL file { name flange;// User-defined patch name } } } }; Why ? Regards, Stephane. |
|
January 16, 2012, 15:14 |
|
#5 | |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,978
Blog Entries: 45
Rep Power: 128 |
Hi Stephane,
I thought it might be something like that. Older versions of OpenFOAM (<2.0.0) allowed that kind of renaming. But with >= 2.0.0, snappyHexMesh considers a more hierarchical name assignment. If I'm not mistaken, you should write "flange_FLANGE" or "flange.FLANGE". Let me check the examples... no, wait, that's only when the naming procedure is done automatically, as shown in the examples:
OK, the base example present in the source code at "applications/utilities/mesh/generation/snappyHexMesh/" clearly indicates: Code:
sphere.stl { type triSurfaceMesh; //tolerance 1E-5; // optional:non-default tolerance on intersections //maxTreeDepth 10; // optional:depth of octree. Decrease only in case // of memory limitations. // Per region the patchname. If not provided will be <name>_<region>. regions { secondSolid { name mySecondPatch; } } } Quote:
Best regards, Bruno
__________________
|
||
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
how to calculate mass flow rate on patches and summation of that during the run? | immortality | OpenFOAM Post-Processing | 104 | February 16, 2021 08:46 |
what is swap4foam ?? | AB08 | OpenFOAM | 28 | February 2, 2016 01:22 |
[foam-extend.org] problem when installing foam-extend-1.6 | Thomas pan | OpenFOAM Installation | 7 | September 9, 2015 21:53 |
[Other] Adding solvers from DensityBasedTurbo to foam-extend 3.0 | Seroga | OpenFOAM Community Contributions | 9 | June 12, 2015 17:18 |
OpenFOAM on MinGW crosscompiler hosted on Linux | allenzhao | OpenFOAM Installation | 127 | January 30, 2009 19:08 |