From 49ab78a64a4f5a65535ebf87b081f77eafd065b6 Mon Sep 17 00:00:00 2001 From: eap Date: Thu, 18 Apr 2013 07:58:41 +0000 Subject: [PATCH] Correction after the proof reading --- doc/salome/gui/SMESH/input/adding_nodes_and_elements.doc | 5 +++-- doc/salome/gui/SMESH/input/adding_quadratic_elements.doc | 7 ++++--- doc/salome/gui/SMESH/input/basic_meshing_algos.doc | 3 ++- doc/salome/gui/SMESH/input/prism_3d_algo.doc | 2 +- doc/salome/gui/SMESH/input/projection_algos.doc | 4 +++- doc/salome/gui/SMESH/input/smesh_migration.doc | 2 +- 6 files changed, 14 insertions(+), 9 deletions(-) diff --git a/doc/salome/gui/SMESH/input/adding_nodes_and_elements.doc b/doc/salome/gui/SMESH/input/adding_nodes_and_elements.doc index b91324b85..e46385b2d 100644 --- a/doc/salome/gui/SMESH/input/adding_nodes_and_elements.doc +++ b/doc/salome/gui/SMESH/input/adding_nodes_and_elements.doc @@ -19,8 +19,9 @@
  • \ref adding_polyhedrons_anchor "Polyhedrons"
    • -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 here . diff --git a/doc/salome/gui/SMESH/input/adding_quadratic_elements.doc b/doc/salome/gui/SMESH/input/adding_quadratic_elements.doc index aaa797812..11b7931d8 100644 --- a/doc/salome/gui/SMESH/input/adding_quadratic_elements.doc +++ b/doc/salome/gui/SMESH/input/adding_quadratic_elements.doc @@ -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 here . diff --git a/doc/salome/gui/SMESH/input/basic_meshing_algos.doc b/doc/salome/gui/SMESH/input/basic_meshing_algos.doc index eca53a6b3..5aed468f1 100644 --- a/doc/salome/gui/SMESH/input/basic_meshing_algos.doc +++ b/doc/salome/gui/SMESH/input/basic_meshing_algos.doc @@ -46,7 +46,8 @@ where the geometrical boundary intersects Cartesian cells. \image html image126.gif "Example of a hexahedral 3D mesh" -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: diff --git a/doc/salome/gui/SMESH/input/prism_3d_algo.doc b/doc/salome/gui/SMESH/input/prism_3d_algo.doc index 5f6c57cc5..d377b549f 100644 --- a/doc/salome/gui/SMESH/input/prism_3d_algo.doc +++ b/doc/salome/gui/SMESH/input/prism_3d_algo.doc @@ -63,7 +63,7 @@ The \b Local algorithms and hypotheses to be chosen at the highlighted edge. -\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". diff --git a/doc/salome/gui/SMESH/input/projection_algos.doc b/doc/salome/gui/SMESH/input/projection_algos.doc index e2f68a897..4e5b6e90d 100644 --- a/doc/salome/gui/SMESH/input/projection_algos.doc +++ b/doc/salome/gui/SMESH/input/projection_algos.doc @@ -60,7 +60,9 @@ In this dialog you can define face being meshed. -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 Projection 1D-2D algorithm differs from Projection 2D algorithm in one aspect: it generates mesh segments on edges of diff --git a/doc/salome/gui/SMESH/input/smesh_migration.doc b/doc/salome/gui/SMESH/input/smesh_migration.doc index 055723dd7..e14640e8b 100644 --- a/doc/salome/gui/SMESH/input/smesh_migration.doc +++ b/doc/salome/gui/SMESH/input/smesh_migration.doc @@ -38,7 +38,7 @@ smesh = smeshBuilder.New(salome.myStudy) Of course, from smesh import * is no more possible. \n You have to explicitely write smesh.some_method(). -Some algorithms have been transferred from the namespace smesh to the namespace smeshBuilder. +All algorithms have been transferred from the namespace smesh to the namespace smeshBuilder. \n For instance: \code MEFISTO_2D_1 = Mesh_1.Triangle(algo=smesh.MEFISTO,geom=Face_1) -- 2.39.2