ForkMaster/smesh
1
0
Fork 0
mirror of https://git.salome-platform.org/gitpub/modules/smesh.git synced 2025-01-13 02:00:34 +05:00
Code Issues Packages Projects Releases Wiki Activity

Some improvements

Browse Source
This commit is contained in:
eap 2013-05-29 13:36:40 +00:00
parent e9f23d7589
commit 6609664fc3
3 changed files with 8 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/salome/gui/SMESH/input/about_hypo.doc
View File

@ -5,13 +5,12 @@
\b Hypotheses represent boundary conditions which will be taken into \b Hypotheses represent boundary conditions which will be taken into
account at calculations of meshes or sub-meshes basing on geometrical account at calculations of meshes or sub-meshes basing on geometrical
objects. These hypotheses allow you to manage the level of detail of objects. These hypotheses allow you to manage the level of detail of
the resulting meshes or submeshes: when applying different hypotheses the resulting meshes or sub-meshes: when applying different hypotheses
with different parameters you can preset the quantity of meshing with different parameters you can preset the quantity or size of
elements which will compose your mesh. So, it will be possible to elements which will compose your mesh. So, it will be possible to
generate a coarse or a more refined mesh or sub-mesh. generate a coarse or a more refined mesh or sub-mesh.
In \b MESH there are the following Basic Hypotheses (to introduce In \b MESH there are the following Basic Hypotheses:
them, you operate numerical values):
<ul> <ul>
<li>\subpage a1d_meshing_hypo_page "1D Hypotheses" (for meshing of <li>\subpage a1d_meshing_hypo_page "1D Hypotheses" (for meshing of
<b>edges</b>):</li> <b>edges</b>):</li>
@ -49,9 +48,8 @@ with other hypotheses:
The choice of a hypothesis depends on: The choice of a hypothesis depends on:
<ul> <ul>
<li>the geometrical object (shape) which will be meshed</li>
<li>the algorithm, which will be selected for meshing of this geometrical object (shape)</li> <li>the algorithm, which will be selected for meshing of this geometrical object (shape)</li>
<li>the geometrical object (shape) which will be meshed</li>
</ul> </ul>
*/ */

6
doc/salome/gui/SMESH/input/basic_meshing_algos.doc
View File

@ -30,13 +30,13 @@ quadrangular elements.</li>
\image html image124.gif "Example of a quadrangular 2D mesh" \image html image124.gif "Example of a quadrangular 2D mesh"
<li>For meshing of 3D entities (<b>volume objects</b>):</li> <li>For meshing of 3D entities (<b>solid objects</b>):</li>
<ul> <ul>
<li>Hexahedron meshing algorithm (i,j,k) - 6-sided Volumes are split into <li>Hexahedron meshing algorithm (i,j,k) - 6-sided Solids are split into
hexahedral (cubic) elements.</li> hexahedral (cubic) elements.</li>
<li>\subpage cartesian_algo_page</li> <li>\subpage cartesian_algo_page</li>
- internal parts of Volumes are split into hexahedral elements forming a - internal parts of Solids are split into hexahedral elements forming a
Cartesian grid; polyhedra and other types of elements are generated Cartesian grid; polyhedra and other types of elements are generated
where the geometrical boundary intersects Cartesian cells.</li> where the geometrical boundary intersects Cartesian cells.</li>
</ul> </ul>

2
doc/salome/gui/SMESH/input/constructing_meshes.doc
View File

@ -251,7 +251,7 @@ And the last mesh computation is made with:
<em>"Result mesh with order SubMesh_3, SubMesh_2, SubMesh_1 "</em></center> <em>"Result mesh with order SubMesh_3, SubMesh_2, SubMesh_1 "</em></center>
As we can see, each mesh computation has a different number of result As we can see, each mesh computation has a different number of result
elements and a different mesh discretisation on the shared edges (the edges elements and a different mesh discretization on the shared edges (the edges
that are shared between <b>Face_1</b>, <b>Face_2</b> and <b>Face_3</b>) that are shared between <b>Face_1</b>, <b>Face_2</b> and <b>Face_3</b>)
Additionally, submesh priority (the order of applied algorithms) can Additionally, submesh priority (the order of applied algorithms) can