mirror of
https://git.salome-platform.org/gitpub/modules/smesh.git
synced 2025-03-03 17:55:37 +05:00
Correction after the proof reading
This commit is contained in:
parent
d8a4fd0b8c
commit
49ab78a64a
@ -19,8 +19,9 @@
|
||||
<li>\ref adding_polyhedrons_anchor "Polyhedrons"</li>
|
||||
</ul>
|
||||
|
||||
SALOME uses the convention of nodal connectivity of MED library elements. You
|
||||
can consult the description of nodal connectivity of elements in the documentation on MED library or
|
||||
The convention of nodal connectivity of elements used in SALOME is
|
||||
the MED library convention. You can consult the description of
|
||||
nodal connectivity of elements in the documentation on MED library or
|
||||
<a href="http://www.code-aster.org/outils/med/html/connectivites.html">
|
||||
here </a>.
|
||||
|
||||
|
@ -11,11 +11,12 @@ located between the corner nodes on element sides.
|
||||
If a quadratic quadrilateral element has an additional node at the
|
||||
element center, it is a bi-quadratic element (or
|
||||
QUAD9). If a quadratic hexahedral element has 7 additional nodes:
|
||||
at the element center and at the center of each side it is a
|
||||
at the element center and at the center of each side, it is a
|
||||
tri-quadratic element (or HEXA27).
|
||||
|
||||
SALOME uses the convention of nodal connectivity of MED library elements. You
|
||||
can consult the description of nodal connectivity of elements in the documentation on MED library or
|
||||
The convention of nodal connectivity of elements used in SALOME is
|
||||
the MED library convention. You can consult the description of nodal
|
||||
connectivity of elements in the documentation on MED library or
|
||||
<a href="http://www.code-aster.org/outils/med/html/connectivites.html">
|
||||
here </a>.
|
||||
|
||||
|
@ -46,7 +46,8 @@ where the geometrical boundary intersects Cartesian cells.</li>
|
||||
\image html image126.gif "Example of a hexahedral 3D mesh"
|
||||
</ul>
|
||||
|
||||
Some 3D meshing algorithms, such as Hexahedron(i,j,k) and GHS3D (commercial), also can generate 3D meshes from 2D meshes, working without
|
||||
Some 3D meshing algorithms, such as Hexahedron(i,j,k) and some
|
||||
commercial ones, also can generate 3D meshes from 2D meshes, working without
|
||||
geometrical objects.
|
||||
|
||||
There is also a number of more specific algorithms:
|
||||
|
@ -63,7 +63,7 @@ The \b Local algorithms and hypotheses to be chosen at
|
||||
the highlighted edge.
|
||||
</li></ul>
|
||||
|
||||
\image html image157.gif "Prism with 3D extrusion meshing. Vertical division is different on neighbor edges because a local 1D hypotheses is assigned."
|
||||
\image html image157.gif "Prism with 3D extrusion meshing. Vertical division is different on neighbor edges because several local 1D hypotheses are assigned."
|
||||
|
||||
\sa a sample TUI Script of
|
||||
\ref tui_prism_3d_algo "Use 3D extrusion meshing algorithm".
|
||||
|
@ -60,7 +60,9 @@ In this dialog you can define
|
||||
face being meshed.</li>
|
||||
</ul>
|
||||
|
||||
The groups of faces are suitable for this algorithm only if they contain an equal number of faces and form topologically equal structures.
|
||||
The groups of faces are suitable for this algorithm only if they
|
||||
contain an equal number of faces and form topologically equal
|
||||
structures.
|
||||
|
||||
\n <b>Projection 1D-2D</b> algorithm differs from <b>Projection 2D</b>
|
||||
algorithm in one aspect: it generates mesh segments on edges of
|
||||
|
@ -38,7 +38,7 @@ smesh = smeshBuilder.New(salome.myStudy)
|
||||
<b> Of course, <em>from smesh import *</em> is no more possible.</b>
|
||||
\n You have to explicitely write <em>smesh.some_method()</em>.
|
||||
|
||||
<b>Some algorithms have been transferred from the namespace <em>smesh</em> to the namespace <em>smeshBuilder</em>.</b>
|
||||
<b>All algorithms have been transferred from the namespace <em>smesh</em> to the namespace <em>smeshBuilder</em>.</b>
|
||||
\n For instance:
|
||||
\code
|
||||
MEFISTO_2D_1 = Mesh_1.Triangle(algo=smesh.MEFISTO,geom=Face_1)
|
||||
|
Loading…
Reference in New Issue
Block a user