X-Git-Url: http://git.salome-platform.org/gitweb/?a=blobdiff_plain;f=doc%2Fsalome%2Fgui%2FSMESH%2Finput%2Fpattern_mapping.doc;fp=doc%2Fsalome%2Fgui%2FSMESH%2Finput%2Fpattern_mapping.doc;h=0fee46ccc870ebd42ea98aebc82fb54ac10f40f4;hb=e7f4c012fbf331df02bbde719b6e49cce95d202a;hp=969b9fc5e066a39b75acea62020432974a51864c;hpb=df9cc07c95bbe75654ed43634939a133ccebe2f6;p=modules%2Fsmesh.git
diff --git a/doc/salome/gui/SMESH/input/pattern_mapping.doc b/doc/salome/gui/SMESH/input/pattern_mapping.doc
index 969b9fc5e..0fee46ccc 100644
--- a/doc/salome/gui/SMESH/input/pattern_mapping.doc
+++ b/doc/salome/gui/SMESH/input/pattern_mapping.doc
@@ -14,17 +14,19 @@ The smp file contains 4 sections:
-# The first line indicates the total number of pattern nodes (N).
-# The next N lines describe nodes coordinates. Each line contains 2
-node coordinates for a 2D pattern or 3 node coordinates for a 3D pattern.
-Note, that node coordinates of a 3D pattern can be defined only by relative values in range [0;1].
+ node coordinates for a 2D pattern or 3 node coordinates for a 3D pattern.
+ Note, that node coordinates of a 3D pattern can be defined only by
+ relative values in range [0;1].
-# The key-points line contains the indices of the nodes to be mapped on geometrical
-vertices (for a 2D pattern only). Index n refers to the node described
-on the n-th line of section 2. The index of the first node zero. For a 3D pattern the key points are not specified.
+ vertices (for a 2D pattern only). Index n refers to the node described
+ on the n-th line of section 2. The index of the first node is
+ zero. For a 3D pattern the key points are not specified.
-# The remaining lines describe nodal connectivity of elements, one line
-for each element. Each line holds indices of nodes forming an element.
-Index n refers to the node described on the n-th line of section 2.
-The first node index is zero. There must be 3 or 4 indices on each
-line for a 2D pattern (only 2d elements are allowed) and 4, 5, 6 or 8
-indices for a 3D pattern (only 3d elements are allowed).
+ for each element. Each line holds indices of nodes forming an element.
+ Index n refers to the node described on the n-th line of section 2.
+ The first node index is zero. There must be 3 or 4 indices on each
+ line for a 2D pattern (only liner 2d elements are allowed) and 4, 5, 6 or 8
+ indices for a 3D pattern (only linear 3d elements are allowed).
A 2D pattern must contain at least one element and at least one
key-point. All key-points must lie on boundaries.
@@ -107,21 +109,24 @@ In this dialog you should specify:
- \b Pattern, which can be loaded from .smp pattern file previously
-created manually or generated automatically from an existing mesh or submesh.
+ created manually or generated automatically from an existing mesh or
+ sub-mesh.
- \b Face with the number of vertices equal to the number of
- key-points in the pattern; the number of key-points on internal
- boundaries of the pattern must also be equal to the number of vertices
- on internal boundaries of the face;
+ key-points in the pattern; the number of key-points on internal
+ boundaries of the pattern must also be equal to the number of vertices
+ on internal boundaries of the face;
- \b Vertex to which the first key-point should be mapped;
+
Alternatively, it is possible to select Refine selected mesh elements
check-box and apply the pattern to
-- Mesh Face instead of a geometric Face
-- and select \b Node instead of vertex.
+ - Mesh Face instead of a geometric Face
+ - and select \b Node instead of vertex.
+
Additionally it is possible to:
- Reverse the order of key-points. By default, the vertices of
- a face are ordered counterclockwise.
+ a face are ordered counterclockwise.
- Enable to Create polygons near boundary
- and Create polyhedrons near boundary
@@ -133,17 +138,18 @@ Additionally it is possible to:
In this dialog you should specify:
- \b Pattern, which can be loaded from .smp pattern file previously
-created manually or generated automatically from an existing mesh or submesh.
+ created manually or generated automatically from an existing mesh or
+ sub-mesh.
- A 3D block (Solid) object.
- Two vertices that specify the order of nodes in the resulting
mesh.
+
Alternatively, it is possible to select Refine selected mesh elements
-checkbox and apply the pattern to
+check-box and apply the pattern to
-- One or several Mesh volumes instead of a geometric 3D
-object
-- and select two /b Nodes instead of vertices.
+ - One or several Mesh volumes instead of a geometric 3D object
+ - and select two /b Nodes instead of vertices.
Additionally it is possible to:
@@ -152,7 +158,7 @@ Additionally it is possible to:
- Automatic Generation
+ Automatic Pattern Generation
To generate a pattern automatically from an existing mesh or sub-mesh,
click \b New button.
@@ -164,8 +170,8 @@ The following dialog box will appear:
In this dialog you should specify:
-- Mesh or Submesh, which is a meshed geometrical face (for a
-2D pattern) or a meshed solid (for a 3D pattern). Mesh nodes lying on
+
- Mesh or Sub-mesh, which is a meshed geometrical face (for a
+2D pattern) or a meshed solid block (for a 3D pattern). Mesh nodes lying on
the face vertices become key-points of the pattern.
- A custom Pattern Name
- Additionally, for a 2D pattern you may choose to
@@ -204,17 +210,17 @@ The mapping algorithm for a 2D case is as follows:
vertices. The node position on the edge depends on its distance from the
key-points.
\image html image96.gif
-- The cordinates of a non-boundary node in the parametric space of the face
- are defined in the following way. In the parametric space of the
+- The coordinates of a non-boundary node in the parametric space of the face
+ are defined in the following way. In the parametric space of the
pattern, the node lies at the intersection of two iso-lines. Both
of them intersect the pattern boundary at two
points at least. If the mapped positions of boundary nodes are known, it is
- possible to find, where the points at the intersection of isolines
+ possible to find, where the points at the intersection of iso-lines
and boundaries are mapped. Then it is possible to find
- the direction of mapped isolinesection and, filally, the poitions of
+ the direction of mapped iso-line section and, finally, the positions of
two nodes on two mapped isolines. The eventual mapped
- position of the node is found as an average of the positions on mapped
- isolines.
+ position of the node is found as an average of the positions on mapped
+ iso-lines.
\image html image97.gif
The 3D algorithm is similar.