diff --git a/CMakeLists.txt b/CMakeLists.txt
index b308616a7..08f747133 100755
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -28,8 +28,8 @@ CMAKE_POLICY(SET CMP0003 NEW)
STRING(TOUPPER ${PROJECT_NAME} PROJECT_NAME_UC)
SET(${PROJECT_NAME_UC}_MAJOR_VERSION 7)
-SET(${PROJECT_NAME_UC}_MINOR_VERSION 6)
-SET(${PROJECT_NAME_UC}_PATCH_VERSION 0)
+SET(${PROJECT_NAME_UC}_MINOR_VERSION 7)
+SET(${PROJECT_NAME_UC}_PATCH_VERSION 1)
SET(${PROJECT_NAME_UC}_VERSION
${${PROJECT_NAME_UC}_MAJOR_VERSION}.${${PROJECT_NAME_UC}_MINOR_VERSION}.${${PROJECT_NAME_UC}_PATCH_VERSION})
SET(${PROJECT_NAME_UC}_VERSION_DEV 0)
@@ -121,7 +121,9 @@ IF(SALOME_BUILD_GUI)
IF(EXISTS ${GUI_ROOT_DIR})
LIST(APPEND CMAKE_MODULE_PATH "${GUI_ROOT_DIR}/adm_local/cmake_files")
FIND_PACKAGE(SalomeGUI)
- FULL_GUI(TRUE) #check whether GUI builded in full mode and with CORBA
+ SALOME_GUI_WITH_CORBA() #check whether GUI builded with CORBA
+ SALOME_GUI_MODE(SALOME_USE_VTKVIEWER SALOME_USE_SALOMEOBJECT
+ OPTIONAL SALOME_USE_PLOT2DVIEWER SALOME_USE_PYCONSOLE)
##
## Prerequisites From GUI:
##
diff --git a/doc/salome/examples/CMakeLists.txt b/doc/salome/examples/CMakeLists.txt
index 7ee8ff5fd..65d8e52e2 100644
--- a/doc/salome/examples/CMakeLists.txt
+++ b/doc/salome/examples/CMakeLists.txt
@@ -165,6 +165,7 @@ SET(GOOD_TESTS
transforming_meshes_ex13.py
use_existing_faces.py
viewing_meshes_ex02.py
+ split_biquad.py
)
SET(EXAMPLES_TESTS ${BAD_TESTS} ${GOOD_TESTS} testme.py)
diff --git a/doc/salome/examples/split_biquad.py b/doc/salome/examples/split_biquad.py
new file mode 100644
index 000000000..e53e7b0b1
--- /dev/null
+++ b/doc/salome/examples/split_biquad.py
@@ -0,0 +1,37 @@
+# Split bi-quadratic to linear
+
+import salome
+salome.salome_init()
+
+from salome.geom import geomBuilder
+geompy = geomBuilder.New(salome.myStudy)
+
+from salome.smesh import smeshBuilder
+smesh = smeshBuilder.New(salome.myStudy)
+
+# make a shape consisting of two quadranges
+OY = geompy.MakeVectorDXDYDZ(0, 1, 0)
+OY1 = geompy.MakeTranslation( OY, 1, 0, 0 )
+OY2 = geompy.MakeTranslation( OY, 2, 0, 0 )
+q1 = geompy.MakeQuad2Edges( OY, OY1 )
+q2 = geompy.MakeQuad2Edges( OY1, OY2 )
+
+shape = geompy.Partition( [q1,q2], theName='shape' )
+ff = geompy.SubShapeAll( shape, geompy.ShapeType["FACE"], theName="quad" )
+
+# mesh one quadrange with quadrangless and the other with triangles
+mesh = smesh.Mesh( shape )
+mesh.Segment().NumberOfSegments(1)
+mesh.Quadrangle()
+mesh.Triangle( ff[1] )
+mesh.Compute()
+
+# make group of quadrangles and extrude them into a hexahedron
+quadGroup = mesh.Group( ff[0], "quads")
+mesh.ExtrusionSweepObject2D( quadGroup, [0,0,1], 1 )
+
+# make the mesh bi-quadratic
+mesh.ConvertToQuadratic( theToBiQuad=True )
+
+# split all elements into linear ones
+mesh.SplitBiQuadraticIntoLinear()
diff --git a/doc/salome/examples/transforming_meshes_ex01.py b/doc/salome/examples/transforming_meshes_ex01.py
index dc61324ec..93f5196c0 100644
--- a/doc/salome/examples/transforming_meshes_ex01.py
+++ b/doc/salome/examples/transforming_meshes_ex01.py
@@ -1,16 +1,11 @@
# Translation
import SMESH_mechanic
-import SMESH
-smesh = SMESH_mechanic.smesh
mesh = SMESH_mechanic.mesh
# define translation vector
-point = SMESH.PointStruct(-150., -150., 0.)
-vector =SMESH.DirStruct(point)
+vector = [-150., -150., 0.]
-# translate a mesh
-doCopy = 1
-
-mesh.Translate([], vector, doCopy)
+# make a translated copy of all elements of the mesh
+mesh.TranslateObject(mesh, vector, Copy=True)
diff --git a/doc/salome/examples/transforming_meshes_ex05.py b/doc/salome/examples/transforming_meshes_ex05.py
index f99d50b6a..deba1c407 100644
--- a/doc/salome/examples/transforming_meshes_ex05.py
+++ b/doc/salome/examples/transforming_meshes_ex05.py
@@ -1,10 +1,14 @@
# Merging Nodes
-import SMESH_mechanic
+import SMESH_mechanic, SMESH
mesh = SMESH_mechanic.mesh
# merge nodes
-Tolerance = 25.0
+Tolerance = 4.0
+
+# prevent nodes located on geom edges from removal during merge:
+# create a group including all nodes on edges
+allSegs = mesh.MakeGroup( "all segments", SMESH.EDGE, SMESH.FT_ElemGeomType,'=', SMESH.Geom_EDGE )
GroupsOfNodes = mesh.FindCoincidentNodes(Tolerance)
-mesh.MergeNodes(GroupsOfNodes)
+mesh.MergeNodes(GroupsOfNodes, NodesToKeep=allSegs)
diff --git a/doc/salome/examples/transforming_meshes_ex09.py b/doc/salome/examples/transforming_meshes_ex09.py
index 62fea88d1..9264a5c4c 100644
--- a/doc/salome/examples/transforming_meshes_ex09.py
+++ b/doc/salome/examples/transforming_meshes_ex09.py
@@ -11,35 +11,40 @@ import SMESH, SALOMEDS
from salome.smesh import smeshBuilder
smesh = smeshBuilder.New(salome.myStudy)
-# create two faces of the box
-box1 = geompy.MakeBox(0., 0., 0., 20., 20., 15.)
-facesList1 = geompy.SubShapeAll(box1, geompy.ShapeType["FACE"])
-face1 = facesList1[2]
+# make two not sewed quadranges
+OY0 = geompy.MakeVectorDXDYDZ(0, 1, 0)
+OY1 = geompy.MakeTranslation( OY0, 1, 0, 0, theName="OY1" )
+OY2 = geompy.MakeTranslation( OY0, 1.01, 0, 0, theName="OY2" )
+OY3 = geompy.MakeTranslation( OY0, 2, 0, 0 )
+q1 = geompy.MakeQuad2Edges( OY0, OY1 )
+q2 = geompy.MakeQuad2Edges( OY2, OY3 )
-box2 = geompy.MakeBox(0., 5., 0., 20., 20., 15.)
-facesList2 = geompy.SubShapeAll(box2, geompy.ShapeType["FACE"])
-face2 = facesList2[1]
-
-edgesList = geompy.SubShapeAll(face2, geompy.ShapeType["EDGE"])
-edge1 = edgesList[2]
-
-aComp = geompy.MakeCompound([face1, face2])
-geompy.addToStudy(aComp, "Two faces")
-
-# create a mesh on two faces
-mesh = smesh.Mesh(aComp, "Two faces : quadrangle mesh")
-
-algo1D = mesh.Segment()
-algo1D.NumberOfSegments(4)
-algo2D = mesh.Quadrangle()
-
-algo_local = mesh.Segment(edge1)
-algo_local.Arithmetic1D(1, 4)
-algo_local.Propagation()
+shape = geompy.MakeCompound( [q1,q2], theName='shape' )
+# make a non-uniform quadrangle mesh on two faces
+mesh = smesh.Mesh(shape, "Two faces : quadrangle mesh")
+mesh.Segment().Arithmetic1D( 0.1, 0.4 )
+mesh.Segment(q1).NumberOfSegments( 5 )
+mesh.Quadrangle()
mesh.Compute()
# sew free borders
-# FirstNodeID1, SecondNodeID1, LastNodeID1,
-# FirstNodeID2, SecondNodeID2, LastNodeID2, CreatePolygons, CreatePolyedrs
-mesh.SewFreeBorders(6, 21, 5, 1, 12, 3, 0, 0)
+
+segs1 = mesh.GetSubMeshElementsId( OY1 ) # mesh segments generated on borders
+segs2 = mesh.GetSubMeshElementsId( OY2 )
+
+FirstNodeID1 = mesh.GetElemNode( segs1[0], 0 )
+SecondNodeID1 = mesh.GetElemNode( segs1[0], 1 )
+LastNodeID1 = mesh.GetElemNode( segs1[-1], 1 )
+FirstNodeID2 = mesh.GetElemNode( segs2[0], 0 )
+SecondNodeID2 = mesh.GetElemNode( segs2[0], 1 )
+LastNodeID2 = mesh.GetElemNode( segs2[-1], 1 )
+CreatePolygons = True
+CreatePolyedrs = False
+
+res = mesh.SewFreeBorders(FirstNodeID1, SecondNodeID1, LastNodeID1,
+ FirstNodeID2, SecondNodeID2, LastNodeID2,
+ CreatePolygons, CreatePolyedrs )
+print res
+print "nb polygons:", mesh.NbPolygons()
+
diff --git a/doc/salome/examples/transforming_meshes_ex10.py b/doc/salome/examples/transforming_meshes_ex10.py
index 426a011a6..e0120b481 100644
--- a/doc/salome/examples/transforming_meshes_ex10.py
+++ b/doc/salome/examples/transforming_meshes_ex10.py
@@ -20,7 +20,7 @@ aComp = geompy.MakeCompound([box1, box2])
geompy.addToStudy(aComp, "Two boxes")
# create a mesh on two boxes
-mesh = smesh.Mesh(aComp, "Two faces : quadrangle mesh")
+mesh = smesh.Mesh(aComp, "Sew Side Elements")
algo1D = mesh.Segment()
algo1D.NumberOfSegments(2)
@@ -33,6 +33,31 @@ algo_local.Propagation()
mesh.Compute()
# sew side elements
-# IDsOfSide1Elements, IDsOfSide2Elements,
-# NodeID1OfSide1ToMerge, NodeID1OfSide2ToMerge, NodeID2OfSide1ToMerge, NodeID2OfSide2ToMerge
-mesh.SewSideElements([69, 70, 71, 72], [91, 92, 89, 90], 8, 38, 23, 58)
+
+# find elements to sew
+face1 = geompy.GetFaceNearPoint( aComp, geompy.MakeVertex( 5, 10, 5 ))
+IDsOfSide1Elements = mesh.GetSubMeshElementsId( face1 )
+print "side faces 1:",IDsOfSide1Elements
+
+face1Translated = geompy.MakeTranslation( face1, 0,5,0 )
+faceFilter = smesh.GetFilter( SMESH.FACE, SMESH.FT_BelongToGeom,'=', face1Translated )
+IDsOfSide2Elements = mesh.GetIdsFromFilter( faceFilter )
+print "side faces 2:",IDsOfSide2Elements
+
+# find corresponding nodes on sides
+edge1 = geompy.GetEdgeNearPoint( aComp, geompy.MakeVertex( 0, 10, 5 ))
+segs1 = mesh.GetSubMeshElementsId( edge1 ) # mesh segments generated on edge1
+NodeID1OfSide1ToMerge = mesh.GetElemNode( segs1[0], 0 )
+NodeID2OfSide1ToMerge = mesh.GetElemNode( segs1[0], 1 )
+print "nodes of side1:", [NodeID1OfSide1ToMerge,NodeID2OfSide1ToMerge]
+
+edge2 = geompy.GetEdgeNearPoint( aComp, geompy.MakeVertex( 0, 15, 5 ))
+segs2 = mesh.GetSubMeshElementsId( edge2 ) # mesh segments generated on edge2
+NodeID1OfSide2ToMerge = mesh.GetElemNode( segs2[0], 0 )
+NodeID2OfSide2ToMerge = mesh.GetElemNode( segs2[0], 1 )
+print "nodes of side2:", [NodeID1OfSide2ToMerge,NodeID2OfSide2ToMerge]
+
+res = mesh.SewSideElements(IDsOfSide1Elements, IDsOfSide2Elements,
+ NodeID1OfSide1ToMerge, NodeID1OfSide2ToMerge,
+ NodeID2OfSide1ToMerge, NodeID2OfSide2ToMerge)
+print res
diff --git a/doc/salome/gui/SMESH/images/extru_rib_segs.png b/doc/salome/gui/SMESH/images/extru_rib_segs.png
new file mode 100644
index 000000000..24f04cf39
Binary files /dev/null and b/doc/salome/gui/SMESH/images/extru_rib_segs.png differ
diff --git a/doc/salome/gui/SMESH/images/extrusionalongaline2.png b/doc/salome/gui/SMESH/images/extrusionalongaline2.png
index 32ea34f4a..f0e6d9e93 100644
Binary files a/doc/salome/gui/SMESH/images/extrusionalongaline2.png and b/doc/salome/gui/SMESH/images/extrusionalongaline2.png differ
diff --git a/doc/salome/gui/SMESH/images/extrusionalongaline3.png b/doc/salome/gui/SMESH/images/extrusionalongaline3.png
index a75601c01..75c359b07 100644
Binary files a/doc/salome/gui/SMESH/images/extrusionalongaline3.png and b/doc/salome/gui/SMESH/images/extrusionalongaline3.png differ
diff --git a/doc/salome/gui/SMESH/images/free_borders1.png b/doc/salome/gui/SMESH/images/free_borders1.png
old mode 100755
new mode 100644
index 6e73c9329..871beba86
Binary files a/doc/salome/gui/SMESH/images/free_borders1.png and b/doc/salome/gui/SMESH/images/free_borders1.png differ
diff --git a/doc/salome/gui/SMESH/images/hexa_ijk_mesh.png b/doc/salome/gui/SMESH/images/hexa_ijk_mesh.png
new file mode 100644
index 000000000..577ee8ec6
Binary files /dev/null and b/doc/salome/gui/SMESH/images/hexa_ijk_mesh.png differ
diff --git a/doc/salome/gui/SMESH/images/image152.png b/doc/salome/gui/SMESH/images/image152.png
old mode 100755
new mode 100644
index 604a15063..d30ae67dc
Binary files a/doc/salome/gui/SMESH/images/image152.png and b/doc/salome/gui/SMESH/images/image152.png differ
diff --git a/doc/salome/gui/SMESH/images/image88.jpg b/doc/salome/gui/SMESH/images/image88.jpg
old mode 100755
new mode 100644
index 3b2a9739c..9499ab219
Binary files a/doc/salome/gui/SMESH/images/image88.jpg and b/doc/salome/gui/SMESH/images/image88.jpg differ
diff --git a/doc/salome/gui/SMESH/images/mergeelems.png b/doc/salome/gui/SMESH/images/mergeelems.png
old mode 100755
new mode 100644
index 3f59269a6..40d614f5e
Binary files a/doc/salome/gui/SMESH/images/mergeelems.png and b/doc/salome/gui/SMESH/images/mergeelems.png differ
diff --git a/doc/salome/gui/SMESH/images/mergeelems_auto.png b/doc/salome/gui/SMESH/images/mergeelems_auto.png
index 904d23463..6e2b30697 100644
Binary files a/doc/salome/gui/SMESH/images/mergeelems_auto.png and b/doc/salome/gui/SMESH/images/mergeelems_auto.png differ
diff --git a/doc/salome/gui/SMESH/images/mergenodes.png b/doc/salome/gui/SMESH/images/mergenodes.png
old mode 100755
new mode 100644
index 05286a56e..5b34361cb
Binary files a/doc/salome/gui/SMESH/images/mergenodes.png and b/doc/salome/gui/SMESH/images/mergenodes.png differ
diff --git a/doc/salome/gui/SMESH/images/mergenodes_auto.png b/doc/salome/gui/SMESH/images/mergenodes_auto.png
index 6a2a92830..4f177f605 100644
Binary files a/doc/salome/gui/SMESH/images/mergenodes_auto.png and b/doc/salome/gui/SMESH/images/mergenodes_auto.png differ
diff --git a/doc/salome/gui/SMESH/images/merging_nodes1.png b/doc/salome/gui/SMESH/images/merging_nodes1.png
old mode 100755
new mode 100644
index f64bdcbe2..05c817537
Binary files a/doc/salome/gui/SMESH/images/merging_nodes1.png and b/doc/salome/gui/SMESH/images/merging_nodes1.png differ
diff --git a/doc/salome/gui/SMESH/images/merging_nodes2.png b/doc/salome/gui/SMESH/images/merging_nodes2.png
old mode 100755
new mode 100644
index 8d7cfdd09..862ed1723
Binary files a/doc/salome/gui/SMESH/images/merging_nodes2.png and b/doc/salome/gui/SMESH/images/merging_nodes2.png differ
diff --git a/doc/salome/gui/SMESH/images/preview_tmp_data.png b/doc/salome/gui/SMESH/images/preview_tmp_data.png
index be1a12515..6f9fb31b3 100644
Binary files a/doc/salome/gui/SMESH/images/preview_tmp_data.png and b/doc/salome/gui/SMESH/images/preview_tmp_data.png differ
diff --git a/doc/salome/gui/SMESH/images/revolutionsn1.png b/doc/salome/gui/SMESH/images/revolutionsn1.png
index 6564c7fc6..3e7a7a1aa 100644
Binary files a/doc/salome/gui/SMESH/images/revolutionsn1.png and b/doc/salome/gui/SMESH/images/revolutionsn1.png differ
diff --git a/doc/salome/gui/SMESH/images/revolutionsn2.png b/doc/salome/gui/SMESH/images/revolutionsn2.png
index 67a673144..064dd6c2d 100644
Binary files a/doc/salome/gui/SMESH/images/revolutionsn2.png and b/doc/salome/gui/SMESH/images/revolutionsn2.png differ
diff --git a/doc/salome/gui/SMESH/images/sew_after_merge.png b/doc/salome/gui/SMESH/images/sew_after_merge.png
new file mode 100644
index 000000000..43d6869f7
Binary files /dev/null and b/doc/salome/gui/SMESH/images/sew_after_merge.png differ
diff --git a/doc/salome/gui/SMESH/images/sew_using_merge.png b/doc/salome/gui/SMESH/images/sew_using_merge.png
new file mode 100644
index 000000000..80cc44c67
Binary files /dev/null and b/doc/salome/gui/SMESH/images/sew_using_merge.png differ
diff --git a/doc/salome/gui/SMESH/images/sewing1.png b/doc/salome/gui/SMESH/images/sewing1.png
old mode 100755
new mode 100644
index daef959ff..55e0d8334
Binary files a/doc/salome/gui/SMESH/images/sewing1.png and b/doc/salome/gui/SMESH/images/sewing1.png differ
diff --git a/doc/salome/gui/SMESH/images/sewing2.png b/doc/salome/gui/SMESH/images/sewing2.png
old mode 100755
new mode 100644
index b7563f97a..2ba3e4365
Binary files a/doc/salome/gui/SMESH/images/sewing2.png and b/doc/salome/gui/SMESH/images/sewing2.png differ
diff --git a/doc/salome/gui/SMESH/images/sewing3.png b/doc/salome/gui/SMESH/images/sewing3.png
old mode 100755
new mode 100644
index da2972fc4..d2d97d509
Binary files a/doc/salome/gui/SMESH/images/sewing3.png and b/doc/salome/gui/SMESH/images/sewing3.png differ
diff --git a/doc/salome/gui/SMESH/images/sewing4.png b/doc/salome/gui/SMESH/images/sewing4.png
old mode 100755
new mode 100644
index 748237c49..ad66682a7
Binary files a/doc/salome/gui/SMESH/images/sewing4.png and b/doc/salome/gui/SMESH/images/sewing4.png differ
diff --git a/doc/salome/gui/SMESH/images/sewing_auto.png b/doc/salome/gui/SMESH/images/sewing_auto.png
new file mode 100644
index 000000000..f81cfe277
Binary files /dev/null and b/doc/salome/gui/SMESH/images/sewing_auto.png differ
diff --git a/doc/salome/gui/SMESH/images/sewing_manual.png b/doc/salome/gui/SMESH/images/sewing_manual.png
new file mode 100644
index 000000000..ff125bc1a
Binary files /dev/null and b/doc/salome/gui/SMESH/images/sewing_manual.png differ
diff --git a/doc/salome/gui/SMESH/images/split_biquad_to_linear_dlg.png b/doc/salome/gui/SMESH/images/split_biquad_to_linear_dlg.png
new file mode 100644
index 000000000..c3df00902
Binary files /dev/null and b/doc/salome/gui/SMESH/images/split_biquad_to_linear_dlg.png differ
diff --git a/doc/salome/gui/SMESH/images/split_biquad_to_linear_icon.png b/doc/salome/gui/SMESH/images/split_biquad_to_linear_icon.png
new file mode 100644
index 000000000..0b9b7a038
Binary files /dev/null and b/doc/salome/gui/SMESH/images/split_biquad_to_linear_icon.png differ
diff --git a/doc/salome/gui/SMESH/images/split_biquad_to_linear_mesh.png b/doc/salome/gui/SMESH/images/split_biquad_to_linear_mesh.png
new file mode 100644
index 000000000..4a25e8f32
Binary files /dev/null and b/doc/salome/gui/SMESH/images/split_biquad_to_linear_mesh.png differ
diff --git a/doc/salome/gui/SMESH/images/swap.png b/doc/salome/gui/SMESH/images/swap.png
new file mode 100644
index 000000000..6470710aa
Binary files /dev/null and b/doc/salome/gui/SMESH/images/swap.png differ
diff --git a/doc/salome/gui/SMESH/input/1d_meshing_hypo.doc b/doc/salome/gui/SMESH/input/1d_meshing_hypo.doc
index 87c20b74f..a5b54c82c 100644
--- a/doc/salome/gui/SMESH/input/1d_meshing_hypo.doc
+++ b/doc/salome/gui/SMESH/input/1d_meshing_hypo.doc
@@ -5,31 +5,31 @@
Basic 1D hypothesis specifies:
how \ref a1d_algos_anchor "Wire Discretization" should divide the edge;
-
how \ref a1d_algos_anchor "Composite Side Discretization" should divide the group of C1-continues edges.
+
how \ref a1d_algos_anchor "Composite Side Discretization" should divide the group of C1-continuous edges.
-By type of nodes distribution the 1D hypotheses can be categorized as follows:
+1D hypotheses can be categorized by type of nodes distribution as follows:
-
Uniform distribution
+
Uniform distribution:
\ref average_length_anchor "Local Length"
\ref max_length_anchor "Max Size"
\ref number_of_segments_anchor "Number of segments" with Equidistant distribution
\ref automatic_length_anchor "Automatic Length"
-
Constantly increasing or decreasing length of segments
+
Constantly increasing or decreasing length of segments:
\ref arithmetic_1d_anchor "Arithmetic 1D"
\ref geometric_1d_anchor "Geometric Progression"
\ref start_and_end_length_anchor "Start and end length"
\ref number_of_segments_anchor "Number of segments" with Scale distribution
-
Distribution depending on curvature
+
Distribution depending on curvature:
\ref adaptive_1d_anchor "Adaptive"
\ref deflection_1d_anchor "Deflection 1D"
-
Arbitrary distribution
+
Arbitrary distribution:
\ref fixed_points_1d_anchor "Fixed points 1D"
\ref number_of_segments_anchor "Number of segments" with
@@ -144,12 +144,17 @@ composing your geometrical object. Definition of this hypothesis
consists of setting the \b length of segments, which will approximate these
edges, and the \b precision of rounding.
-The \b precision parameter is used to round a number of segments,
-calculated by dividing the edge length by the specified \b length of
-segment, to the higher integer if the remainder exceeds the precision
-and to the lower integer otherwise. Use value 0.5 to provide rounding
-to the nearest integer, 1.0 for the lower integer, 0.0 for the higher
-integer. Default value is 1e-07.
+The \b precision parameter is used to round a number of segments,
+calculated by dividing the edge length by the specified \b length of
+segment, to the higher integer if the \a remainder exceeds the \b precision
+and to the lower integer otherwise.
+Use value 0.5 to provide rounding to the nearest integer, 1.0 for the lower integer, 0.0 for the higher integer. Default value is 1e-07.
+
+For example: if edge length is 10.0 and the segment \b length
+is 3.0 then their division gives 10./3. = 3.33(3) and the \a remainder is 0.33(3).
+If \b precision is less than 0.33(3) then the edge is divided into 3 segments.
+If \b precision is more than 0.33(3) then the edge is divided into 4 segments.
+
\image html image41.gif
@@ -245,6 +250,7 @@ negative.
\ref tui_deflection_1d "Defining Number of Segments" hypothesis
operation.
+\note The plot functionality is available only if GUI module is builded with Plot 2D Viewer (set option SALOME_USE_PLOT2DVIEWER to ON when building GUI module).
\anchor start_and_end_length_anchor
@@ -316,7 +322,7 @@ possible to select the edges to be reversed either directly picking them in
the 3D viewer or selecting the edges or groups of edges in the
Object Browser.
-\ref reversed_edges_helper_anchor "Helper" group assists you in
+\ref reversed_edges_helper_anchor "Helper" group assists in
defining Reversed Edges parameter.
@@ -330,23 +336,23 @@ defining Reversed Edges parameter.
\image html rev_edges_helper_dlg.png
-\b Helper group assists you in defining Reversed Edges
+\b Helper group assists in defining Reversed Edges
parameter of the hypotheses depending on edge direction.
-Show whole geometry check-box lets you see the whole
-geometrical model in the 3D Viewer. This can help you to understand
-location within the model of a set of edges shown in the Viewer.
+Show whole geometry check-box allows seeing the whole
+geometrical model in the 3D Viewer, which can help to understand the
+location of a set of edges within the model.
-Propagation chains group helps you to define
-Reversed Edges so that opposite edges of quadrilateral faces
-will be split in the logically same direction. When this group is
+Propagation chains group allows defining Reversed Edges
+for splitting opposite edges of quadrilateral faces
+in a logically uniform direction. When this group is
activated, the list is filled with propagation chains found within the
-model. When you select a chain in the list, edges of the chain are
-shown in the Viewer with arrows so that you can chose a common
-direction for all chain edges. \b Reverse button inverses the common
-direction of chain edges. If \b Add button is active, this means that some
-edges of a chain have different direction and you can click \b Add
-button to add such edges to Reversed Edges list.
+model. When a chain is selected in the list its edges are
+shown in the Viewer with arrows, which enables choosing a common
+direction for all chain edges. \b Reverse button inverts the common
+direction of chain edges. If \b Add button is active, some
+edges of a chain have a different direction, so you can click \b Add
+button to add them to Reversed Edges list.
\image html propagation_chain.png "The whole geometry and a propagation chain"
diff --git a/doc/salome/gui/SMESH/input/2d_meshing_hypo.doc b/doc/salome/gui/SMESH/input/2d_meshing_hypo.doc
index 234ffd11b..308a6899a 100644
--- a/doc/salome/gui/SMESH/input/2d_meshing_hypo.doc
+++ b/doc/salome/gui/SMESH/input/2d_meshing_hypo.doc
@@ -26,9 +26,9 @@ which will compose the mesh of these faces.
\anchor length_from_edges_anchor
Length from Edges
-Length from edges hypothesis defines maximum linear size of
-mesh faces as an average length of mesh edges approximating a boundary
-of a face being meshed.
+Length from edges hypothesis defines the maximum linear size of
+mesh faces as an average length of mesh edges approximating
+the meshed face boundary.
See Also a sample TUI Script of a
\ref tui_length_from_edges "Length from Edges" hypothesis operation.
@@ -38,7 +38,7 @@ of a face being meshed.
\image html hypo_quad_params_dialog.png "Quadrangle parameters: Transition"
-Quadrangle parameters is a hypothesis for Quadrangle (Mapping) algorithm.
+Quadrangle parameters is a hypothesis for \ref quad_ijk_algo_page.
Transition tab is used to define the algorithm of transition
between opposite sides of the face with a different number of
@@ -113,7 +113,7 @@ of the enforced nodes.
projected to the meshed face and located close enough to the
meshed face will be used to create the enforced nodes.
-\note Enforced nodes can't be created at \b Reduced transition type.
+\note Enforced nodes cannot be created at \b Reduced transition type.
Let us see how the algorithm works:
diff --git a/doc/salome/gui/SMESH/input/about_filters.doc b/doc/salome/gui/SMESH/input/about_filters.doc
index bbd596023..f331fa4be 100644
--- a/doc/salome/gui/SMESH/input/about_filters.doc
+++ b/doc/salome/gui/SMESH/input/about_filters.doc
@@ -26,7 +26,7 @@ about selection filters and their usage in GUI.
- In Python scripts, filters can be used to choose only some mesh
entities (nodes or elements) for the operations, which require the
list of entities as input parameter (create/modify group, remove
- nodes/elements, etc) and for the operations, which accept objects as
+ nodes/elements, etc) and for the operations, which accept objects
as input parameter. The page \ref tui_filters_page provides
examples of the filters usage in Python scripts.
*/
diff --git a/doc/salome/gui/SMESH/input/about_hypo.doc b/doc/salome/gui/SMESH/input/about_hypo.doc
index b2dab5dbf..12f5c02e1 100644
--- a/doc/salome/gui/SMESH/input/about_hypo.doc
+++ b/doc/salome/gui/SMESH/input/about_hypo.doc
@@ -14,17 +14,16 @@ The choice of a hypothesis depends on the selected algorithm.
Hypotheses are created during creation and edition of
\ref constructing_meshes_page "meshes" and
-\ref constructing_submeshes_page "sub-mesh".
-Once created a hypotheses can be reused during creation and
-edition of other meshes and sub-meshes. All created hypotheses and
-algorithms are present in the Object Browser in \a Hypotheses and
-\a Algorithms folders correspondingly. From the context menu of the
-hypothesis you can invoke a dialog for modification of its parameters,
-and \b Unassign command that will unassign the hypothesis from all
-the meshes and sub-meshes using it.
-Modification of any hypothesis parameter and unassignment of a
-hypothesis leads to automatic removal of elements generated with use
-of this hypothesis.
+\ref constructing_submeshes_page "sub-meshes".
+Once created a hypotheses can be reused during creation and edition of
+other meshes and sub-meshes. All created hypotheses and algorithms are
+present in the Object Browser in \a Hypotheses and \a Algorithms
+folders correspondingly. It is possible to open a dialog to modify the
+parameters of a hypothesis from its context menu. This menu also
+provides \b Unassign command that will unassign the hypothesis from
+all meshes and sub-meshes using it. Modification of any parameter of a
+hypothesis and its unassignment leads to automatic removal of elements
+generated using it.
In \b MESH there are the following Basic Hypotheses:
diff --git a/doc/salome/gui/SMESH/input/about_meshes.doc b/doc/salome/gui/SMESH/input/about_meshes.doc
index 470cb854d..7550e8934 100644
--- a/doc/salome/gui/SMESH/input/about_meshes.doc
+++ b/doc/salome/gui/SMESH/input/about_meshes.doc
@@ -19,31 +19,31 @@ Mesh module provides several ways to create the mesh:
Construction of \subpage constructing_submeshes_page "sub-meshes"
allows to discretize some sub-shapes of the main shape, for example a face,
- using different meshing parameters than other sub-shapes.
+ using the meshing parameters that differ from those for other sub-shapes.
Meshing parameters of meshes and sub-meshes can be
\subpage editing_meshes_page "edited". (Upon edition only mesh entities
generated using changed meshing parameters are removed and will be
re-computed).
- \note Algorithms and hypotheses used at mesh level are referred as
- \a global ones and those used at sub-mesh level are referred as \a
+ \note Algorithms and hypotheses used at mesh level are referred to as
+ \a global ones and those used at sub-mesh level are referred to as \a
local ones.
Bottom-up way, using \ref modifying_meshes_page "mesh modification"
operations, especially \ref extrusion_page "extrusion" and \ref
- revolution_page "revolution". To create an empty mesh not based on
+ revolution_page "revolution". To create an empty mesh not based on a
geometry, use the same dialog as to \ref constructing_meshes_page
- "construct the mesh on geometry" but do not specify any geometry
- nor meshing algorithm.
+ "construct the mesh on geometry" but do not specify a geometry
+ or a meshing algorithm.
-
The mesh can be \ref importing_exporting_meshes_page "imported" from
+
The mesh can be \subpage importing_exporting_meshes_page "imported" from
(and exported to) the file in MED, UNV, STL, CGNS, DAT, GMF and
SAUVE formats.
The 3D mesh can be generated from the 2D mesh, \ref
importing_exporting_meshes_page "imported" or manually created. To
- setup the meshing parameters of a mesh not based on geometry, just
+ setup the meshing parameters of a mesh not based on a geometry, just
invoke \ref editing_meshes_page "Edit mesh / sub-mesh" command on
- your 3D mesh.
+ your 2D mesh.
Several meshes can be \subpage building_compounds_page "combined"
into a new mesh.
@@ -66,29 +66,29 @@ Attractive meshing capabilities include:
sub-meshes.
The \b structure of a SALOME mesh is described by nodes and elements based on
-these nodes. Geometry of the element is defined by the sequence of
+these nodes. The geometry of an element is defined by the sequence of
nodes constituting it and
the
connectivity convention (adopted from MED library). Definition of
-the element basing on elements of lower dimension is NOT supported.
+the element basing on the elements of a lower dimension is NOT supported.
\anchor mesh_entities
The mesh can include the following entities:
-
\b Node — an entity of a mesh defining a position in 3D
+
\b Node — a mesh entity defining a position in 3D
space with coordinates (x, y, z).
-
\b Edge (or segment) — 1D element of a mesh linking two nodes.
-
\b Face — 2D element of a mesh representing a part of
+
\b Edge (or segment) — 1D mesh element linking two nodes.
+
\b Face — 2D mesh element representing a part of
surface bound by links between face nodes. A face can be a
triangle, quadrangle or polygon.
-
\b Volume — 3D element of a mesh representing a part of 3D
+
\b Volume — 3D mesh element representing a part of 3D
space bound by volume facets. Nodes of a volume describing each
facet are defined by
the
MED connectivity convention. A volume can be a tetrahedron, hexahedron,
pentahedron, pyramid, hexagonal prism or polyhedron.
-
\b 0D element — element of a mesh defined by one node.
-
\b Ball element — discrete element of a mesh defined by a
+
\b 0D element — mesh element defined by one node.
+
\b Ball element — discrete mesh element defined by a
node and a diameter.
@@ -97,10 +97,14 @@ generated on (if any). The node generated on the geometrical edge or
surface in addition stores its position in parametric space of the
associated geometrical entity.
-SALOME supports elements of second order, without central node
-(quadratic triangle, quadrangle, tetrahedron, hexahedron, pentahedron
-and pyramid) and with central nodes (bi-quadratic triangle and
-quadrangle and tri-quadratic hexahedron).
+Mesh entities are identified by integer IDs starting from 1.
+Nodes and elements are countered separately, i.e. there can be a node
+and element with the same ID.
+
+SALOME supports elements of second order, without a central node
+(quadratic triangle, quadrangle, polygon, tetrahedron, hexahedron,
+pentahedron and pyramid) and with central nodes (bi-quadratic triangle
+and quadrangle and tri-quadratic hexahedron).
Quadratic mesh can be obtained in two ways:
- Using a global \ref quadratic_mesh_anchor "Quadratic Mesh"
hypothesis. (Elements with the central node are not generated in this way).
diff --git a/doc/salome/gui/SMESH/input/about_quality_controls.doc b/doc/salome/gui/SMESH/input/about_quality_controls.doc
index 1e170e440..9dbb5c992 100644
--- a/doc/salome/gui/SMESH/input/about_quality_controls.doc
+++ b/doc/salome/gui/SMESH/input/about_quality_controls.doc
@@ -24,7 +24,6 @@ Node quality controls:
Edge quality controls:
-
\subpage free_edges_page "Free edges"
\subpage free_borders_page "Free borders"
\subpage length_page "Length"
\subpage borders_at_multi_connection_page "Borders at multi-connection"
@@ -33,6 +32,7 @@ Edge quality controls:
Face quality controls:
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 e46385b2d..855b7e5ea 100644
--- a/doc/salome/gui/SMESH/input/adding_nodes_and_elements.doc
+++ b/doc/salome/gui/SMESH/input/adding_nodes_and_elements.doc
@@ -32,7 +32,7 @@ nodal connectivity of elements in the documentation on MED library or
From the \b Modification menu choose the \b Add item, the
following associated sub-menu will appear:
- \image html image146.png
+ \image html image152.png
From this sub-menu select the type of element which you would like to add to your mesh.
@@ -47,10 +47,13 @@ existing groups of the corresponding type becomes available. By
default, no group is selected. In this case, when the user presses
Apply or Apply & Close button, the warning message box
informs the user about the necessity to input new group name. The
-combo box lists both \ref standalone_group "standalone groups"
-and \ref group_on_geom "groups on geometry". If the user chooses a
-group on geometry, he is warned and proposed to
-\ref convert_to_standalone "convert this group to standalone".
+combo box lists groups of all the
+\ref grouping_elements_page "three types": both
+\ref standalone_group "standalone groups",
+\ref group_on_filter "groups on filter", and
+\ref group_on_geom "groups on geometry". If the user chooses a
+group on geometry or on filter, he is warned and proposed to
+convert this group to standalone.
If the user rejects conversion operation, it is cancelled and
a new node/element is not created!
@@ -87,29 +90,35 @@ selecting them in the 3D viewer and click the \b Apply or
\anchor adding_0delems_on_all_nodes_anchor
Making 0D elements on Element Nodes
-There is another way to create 0D elements. It is possible to create
+There is another way to create 0D elements. It is possible to create
0D elements on all nodes of the selected mesh, sub-mesh, or a group of elements or nodes.
\image html dlg_0D_on_all_nodes.png
-In this dialog
+In this dialog
The radio-buttons allow choosing the type of object to create 0D elements on.
-
Mesh, sub-mesh, group - this button allows selecting
- a mesh, a sub-mesh or a group to create 0D elements on the nodes of its
+
Mesh, sub-mesh, group - this button allows selecting
+ a mesh, a sub-mesh or a group to create 0D elements on the nodes of its
elements. The name of the selected object is shown in the dialog.
Elements - this button allows selecting elements in the
VTK viewer or typing their IDs in the dialog.
Nodes - this button allows selecting nodes to create
0D elements on in the VTK viewer or typing their IDs in the dialog.
-
Set Filter button allows selecting elements or nodes
-by filtering mesh elements or nodes with different criteria
-(see \ref filtering_elements "Filter usage").
-
Switching on Add to group check-box allows specifying the
- name of the group to which all created or found 0D elements will be added. You can either select an existing group from
- a drop-down list, or enter the name of the group to be created.
+
Set Filter button allows selecting elements or nodes
+ by filtering mesh elements or nodes with different criteria
+ (see \ref filtering_elements "Filter usage").
+
Switching on Add to group check-box allows specifying the
+ name of the group to which all created or found (existing) 0D elements will
+ be added. You can either select an existing group from a drop-down
+ list, or enter the name of the group to be created. If a selected
+ existing \ref grouping_elements_page "group" is not Standalone
+ (Group On Geometry or Group On Filter) it will be converted to
+ Standalone.
+ \warning If Add to group is activated it has to be filled in.
+
@@ -121,7 +130,7 @@ by filtering mesh elements or nodes with different criteria
In this dialog box specify the nodes, which will form your ball elements,
either by selecting them in the 3D viewer or by manually entering their IDs,
specify the ball diameter and click the \b Apply or Apply and
-Close button.
+ Close button.
\image html add_ball.png
diff --git a/doc/salome/gui/SMESH/input/adding_quadratic_elements.doc b/doc/salome/gui/SMESH/input/adding_quadratic_elements.doc
index 6a9527b5d..2fd906baf 100644
--- a/doc/salome/gui/SMESH/input/adding_quadratic_elements.doc
+++ b/doc/salome/gui/SMESH/input/adding_quadratic_elements.doc
@@ -36,7 +36,7 @@ one of the following:
\image html image152.png
-\note All dialogs for quadratic element adding to the mesh
+\note All dialogs for adding quadratic element to the mesh
provide the possibility to automatically add an element
to the specified group or to create the group anew using
Add to group box, that allows choosing an existing group for
@@ -47,23 +47,29 @@ existing groups of the corresponding type becomes available. By
default, no group is selected. In this case, when the user presses
Apply or Apply & Close button, the warning message box
informs the user about the necessity to input a new group name. The
-combo box lists both \ref standalone_group "standalone groups"
-and \ref group_on_geom "groups on geometry". If the user chooses a
-group on geometry, he is warned and proposed to
-\ref convert_to_standalone "convert this group to standalone".
+combo box lists groups of all the
+\ref grouping_elements_page "three types": both
+\ref standalone_group "standalone groups",
+\ref group_on_filter "groups on filter", and
+\ref group_on_geom "groups on geometry". If the user chooses a
+group on geometry or on filter, he is warned and proposed to
+convert this group to standalone.
If the user rejects conversion operation, it is cancelled and
a new quadratic element is not created.
-To create any Quadratic Element specify the nodes which will form your
-element by selecting them in the 3D viewer with pressed Shift
-button. Their numbers will appear in the dialog box as Corner Nodes
-(alternatively you can just input numbers in this field without
-selection). The edges formed by the corner nodes will appear in the
-table. To define the middle nodes for each edge, double-click on the
-respective field and input the number of the node (or pick the node in
-the viewer). For bi-quadratic and tri-quadratic elements, your also
-need to specify central nodes.
+To create any Quadratic Element specify the nodes which will
+form your element by selecting them in the 3D viewer with pressed
+Shift button and click \a Selection button to the right of
+Corner Nodes label. Their numbers will appear in the dialog box
+as Corner Nodes (alternatively you can just input numbers in
+this field without selection; note that to use this way the mesh
+should be selected before invoking this operation). The edges formed
+by the corner nodes will appear in the table. To define the middle
+nodes for each edge, double-click on the respective field and input
+the number of the node (or pick the node in the viewer). For
+bi-quadratic and tri-quadratic elements, your also need to specify
+central nodes.
As soon as all needed nodes are specified, a preview of a new
quadratic element will be displayed in the 3D viewer. Then
you will be able to click \b Apply or Apply and Close button to
diff --git a/doc/salome/gui/SMESH/input/additional_hypo.doc b/doc/salome/gui/SMESH/input/additional_hypo.doc
index 9bade2149..5904e87d4 100644
--- a/doc/salome/gui/SMESH/input/additional_hypo.doc
+++ b/doc/salome/gui/SMESH/input/additional_hypo.doc
@@ -31,12 +31,13 @@ The following additional hypothesis are available:
Propagation of 1D Hypothesis on opposite edges
Propagation of 1D Hypothesis on opposite edges allows to mesh
-opposite sides of a quadrangle face, and of other adjacent quadrangles,
-using the same hypothesis assigned to one edge only.
-Thus you define a sub-mesh on an edge where you define 1D meshing
-parameters and a \b Propagation hypothesis. These local meshing
+opposite sides of a quadrangle face and other adjacent quadrangles,
+using the same hypothesis assigned to only one edge.
+Thus you define a sub-mesh on the edge where you define 1D meshing
+parameters and the \b Propagation hypothesis. These local meshing
parameters will be propagated via opposite sides of quadrangles to the
-whole geometry, or till an edge with other local meshing parameters.
+whole geometry, and this propagation stops at an edge with other local
+meshing parameters.
This hypothesis can be taken into account by
\ref a1d_algos_anchor "Wire Discretization" and
@@ -84,17 +85,17 @@ computations.
Stretch factor - defines the growth factor of element height
from the mesh boundary inwards.
Extrusion method (available in 3D only) - defines how
- position of nodes are found during prism construction and how
- creation of distorted and intersecting prisms is prevented.
-
Surface offset + smooth method extrudes nodes along normal
- to underlying geometrical surface. Smoothing of internal surface of
+ positions of nodes are found during prism construction and how
+ the creation of distorted and intersecting prisms is prevented.
+
Surface offset + smooth method extrudes nodes along the normal
+ to the underlying geometrical surface. Smoothing of the internal surface of
element layers is possible to avoid creation of invalid prisms.
-
Face offset method extrudes nodes along average normal of
- surrounding mesh faces till intersection with a neighbor mesh face
- translated along its own normal by the layers thickness. Thickness
+
Face offset method extrudes nodes along the average normal of
+ surrounding mesh faces to the intersection with a neighbor mesh face
+ translated along its own normal by the thickness of layers. The thickness
of layers can be limited to avoid creation of invalid prisms.
-
Node offset method extrudes nodes along average normal of
- surrounding mesh faces by the layers thickness. Thickness of
+
Node offset method extrudes nodes along the average normal of
+ surrounding mesh faces by the thickness of layers. The thickness of
layers can be limited to avoid creation of invalid prisms.
\image html viscous_layers_extrusion_method.png "Prisms created by the tree extrusion methods at the same other parameters"
@@ -107,9 +108,9 @@ computations.
Faces (or edges) can be selected either in the Object Browser or in
the VTK Viewer.
\note A mesh shown in the 3D Viewer can prevent selection of faces
- and edges, just hide the mesh to avoid this. Sometimes a face to
- select is hidden by other faces, in this case consider creating a
- group of faces you want to select in the Geometry module.
+ and edges, just hide the mesh to avoid this. If a face, which should be
+ selected, is hidden by other faces, consider creating a
+ group of faces to be selected in the Geometry module.
To avoid a long wait when a
geometry with many faces (or edges) is displayed, the number of faces
(edges) shown at a time is limited by the value of "Sub-shapes
@@ -150,12 +151,12 @@ computations.
Quadratic Mesh hypothesis allows to build a quadratic mesh (in which
links between element nodes are not straight but curved lines due to
-presence of an additional midside node).
+presence of an additional mid-side node).
This 1D hypothesis can be taken into account by
\ref a1d_algos_anchor "Wire Discretization" and
\ref a1d_algos_anchor "Composite Side Discretization" algorithms. To
-make a quadratic mesh assign this hypothesis at
+create a quadratic mesh assign this hypothesis at
\ref constructing_meshes_page "mesh construction".
See \ref adding_quadratic_elements_page
@@ -168,9 +169,13 @@ for more information about quadratic meshes.
This additional hypothesis can be used together with 2D triangulation algorithms.
It allows 2D triangulation algorithms to build quadrangular meshes.
-When used with "Quadrangle (Mapping)" meshing algorithm, that is obsolete
- since introducing \ref hypo_quad_params_anchor "Quadrangle parameters"
-hypothesis, this hypothesis has one restriction on its work: the total quantity of
-segments on all four sides of the face must be even (divisible by 2).
-
+Usage of this hypothesis with "Quadrangle (Mapping)" meshing algorithm
+is obsolete since introducing
+\ref hypo_quad_params_anchor "Quadrangle parameters" hypothesis.
+Usage of this hypothesis with "Quadrangle (Mapping)" meshing algorithm
+corresponds to specifying "Quadrangle Preference" transition type of
+\ref hypo_quad_params_anchor "Quadrangle parameters" hypothesis.
+\note "Quadrangle Preference" transition type can be used only if the
+total quantity of segments on all sides of the face is even (divisible
+by 2), else "Standard" transition type is used.
*/
diff --git a/doc/salome/gui/SMESH/input/basic_meshing_algos.doc b/doc/salome/gui/SMESH/input/basic_meshing_algos.doc
index b82b67f89..080727462 100644
--- a/doc/salome/gui/SMESH/input/basic_meshing_algos.doc
+++ b/doc/salome/gui/SMESH/input/basic_meshing_algos.doc
@@ -7,26 +7,26 @@ used for meshing entities (1D, 2D, 3D sub-shapes) composing
geometrical objects.
An algorithm represents either an implementation of a certain meshing
-technique or a interface to a whole meshing program generating elements
+technique or an interface to the whole meshing program generating elements
of several dimensions.
For meshing of 1D entities (edges):
\anchor a1d_algos_anchor
-
Wire Discretization meshing algorithm - splits an edge into a
+
Wire Discretization meshing algorithm - splits an edge into a
number of mesh segments following an 1D hypothesis.
-
Composite Side Discretization algorithm - allows to apply an 1D
+
Composite Side Discretization algorithm - allows to apply a 1D
hypothesis to a whole side of a geometrical face even if it is
- composed of several edges provided that they form C1 curve and form
- one side in all faces of the main shape.
+ composed of several edges provided that they form C1 curve in all
+ faces of the main shape.
@@ -39,8 +39,15 @@ number of mesh segments following an 1D hypothesis.
For meshing of 3D entities (solid objects):
-
Hexahedron (i,j,k)meshing algorithm - 6-sided solids are
- split into hexahedral (cuboid) elements.
+
Hexahedron (i,j,k) meshing algorithm - solids are
+ split into hexahedral elements thus forming a structured 3D
+ mesh. The algorithm requires that 2D mesh generated on a solid could
+ be considered as a mesh of a box, i.e. there should be eight nodes
+ shared by three quadrangles and the rest nodes should be shared by
+ four quadrangles.
+\image html hexa_ijk_mesh.png "Structured mesh generated by Hexahedron (i,j,k) on a solid bound by 16 faces"
+
+
\subpage cartesian_algo_page "Body Fitting" meshing
algorithm - solids are split into hexahedral elements forming
a Cartesian grid; polyhedra and other types of elements are generated
@@ -52,22 +59,25 @@ number of mesh segments following an 1D hypothesis.
\image html image126.gif "Example of a hexahedral 3D mesh"
-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.
+Some 3D meshing algorithms, such as Hexahedron(i,j,k) also can
+generate 3D meshes from 2D meshes, working without geometrical
+objects.
There is also a number of more specific algorithms:
-
\subpage prism_3d_algo_page "for meshing prismatic 3D shapes"
-
\subpage quad_from_ma_algo_page "for meshing faces with sinuous borders"
+
\subpage prism_3d_algo_page "for meshing prismatic 3D shapes with hexahedra and prisms"
+
\subpage quad_from_ma_algo_page "for quadrangle meshing of faces with sinuous borders"
+
Polygon per Face meshing algorithm - generates one mesh
+ face (either a triangle, a quadrangle or a polygon) per a geometrical
+ face using all nodes from the face boundary.
\subpage projection_algos_page "for meshing by projection of another mesh"
\subpage import_algos_page "for meshing by importing elements from another mesh"
-
\subpage radial_prism_algo_page "for meshing geometrical objects with cavities"
-
\subpage radial_quadrangle_1D2D_algo_page "for meshing special 2d faces (circles and part of circles)"
+
\subpage radial_prism_algo_page "for meshing 3D geometrical objects with cavities with hexahedra and prisms"
+
\subpage radial_quadrangle_1D2D_algo_page "for quadrangle meshing of disks and parts of disks"
\subpage use_existing_page "Use Edges to be Created Manually" and
-\ref use_existing_page "Use Faces to be Created Manually" algorithms can be
-used to create a 1D or a 2D mesh in a python script.
-
\subpage segments_around_vertex_algo_page "for defining the local size of elements around a certain node"
+ \ref use_existing_page "Use Faces to be Created Manually" algorithms can be
+ used to create a 1D or a 2D mesh in a python script.
+
\subpage segments_around_vertex_algo_page "for defining the length of mesh segments around certain vertices"
\ref constructing_meshes_page "Constructing meshes" page describes in
diff --git a/doc/salome/gui/SMESH/input/borders_at_multi_connection.doc b/doc/salome/gui/SMESH/input/borders_at_multi_connection.doc
index b4f14481f..46fbc6047 100644
--- a/doc/salome/gui/SMESH/input/borders_at_multi_connection.doc
+++ b/doc/salome/gui/SMESH/input/borders_at_multi_connection.doc
@@ -2,8 +2,8 @@
\page borders_at_multi_connection_page Borders at multi-connection
-\n This mesh quality control highlights segments according to number
-of elements, faces and volumes, the segment belongs to.
+\n This mesh quality control highlights segments according to the number
+of elements, faces and volumes, to which the segment belongs.
\image html image151.gif
diff --git a/doc/salome/gui/SMESH/input/borders_at_multi_connection_2d.doc b/doc/salome/gui/SMESH/input/borders_at_multi_connection_2d.doc
index e0e78959b..77a439130 100644
--- a/doc/salome/gui/SMESH/input/borders_at_multi_connection_2d.doc
+++ b/doc/salome/gui/SMESH/input/borders_at_multi_connection_2d.doc
@@ -3,7 +3,7 @@
\page borders_at_multi_connection_2d_page Borders at multi-connection 2D
\n This mesh quality control highlights borders of faces (links
-between nodes) according to number of faces the link belongs to.
+between nodes) according to the number of faces, to which the link belongs.
\image html image127.gif
diff --git a/doc/salome/gui/SMESH/input/building_compounds.doc b/doc/salome/gui/SMESH/input/building_compounds.doc
index fb48fdb26..ce5f3ce50 100644
--- a/doc/salome/gui/SMESH/input/building_compounds.doc
+++ b/doc/salome/gui/SMESH/input/building_compounds.doc
@@ -4,10 +4,10 @@
\n Compound Mesh is a combination of several meshes. All elements and
groups present in input meshes are present in the compound
-mesh. Neither geometry nor hypotheses of initial meshes are used by
-the compound mesh. No link between input meshes and a compound mesh is
-supported, so that modification of an input mesh does not lead to
-update of the compound mesh.
+mesh. However, it does not use geometry or hypotheses of the initial meshes.
+The links between the input meshes and the compound mesh are not
+supported, consequently the modification of an input mesh does not lead to
+the update of the compound mesh.
To Build a compound mesh:
@@ -27,15 +27,16 @@ The following dialog box will appear:
\b Name - allows selecting the name of the resulting \b Compound mesh.
Meshes, sub-meshes, groups - allows selecting the meshes,
- sub-meshes and groups which will be concatenated. They can be
+ sub-meshes and groups to be concatenated. They can be
chosen in the Object Browser while holding \b Ctrl button.
Processing identical groups - allows selecting the method
of processing the namesake groups existing in the input meshes.
They can be either
-
\b United - all elements of Group1 of Mesh_1 and Group1 of Mesh_2
- become the elements of Group1 of the Compound_Mesh, or
-
\b Renamed - Group1 of Mesh_1 becomes Group1_1 and Group1 of Mesh_2
- becomes Group1_2.
+
\b United - all elements of \em Group1 of \em Mesh_1 and \em
+ Group1 of \em Mesh_2 become the elements of \em Group1 of the
+ \em Compound_Mesh, or
+
\b Renamed - \em Group1 of \em Mesh_1 becomes \em Group1_1
+ and \em Group1 of \em Mesh_2 becomes \em Group1_2.
See \ref grouping_elements_page "Creating Groups" for more information
about groups.
diff --git a/doc/salome/gui/SMESH/input/cartesian_algo.doc b/doc/salome/gui/SMESH/input/cartesian_algo.doc
index 4d00c577f..63b81ffc4 100644
--- a/doc/salome/gui/SMESH/input/cartesian_algo.doc
+++ b/doc/salome/gui/SMESH/input/cartesian_algo.doc
@@ -41,11 +41,9 @@ To apply this algorithm when you define your mesh, select Body
This dialog allows to define
\b Name of the algorithm.
-
Minimal size of a cell truncated by the geometry boundary. If the
size of a truncated grid cell is \b Threshold times less than a
initial cell size, then a mesh element is not created.
-
Implement Edges check-box activates incorporation of
geometrical edges in the mesh.
@@ -64,9 +62,10 @@ This dialog allows to define
System.
You can define the \b Spacing of a grid as an algebraic formula
f(t) where \a t is a position along a grid axis
- normalized at [0.0,1.0]. The whole range of geometry can be
- divided into sub-ranges with their own spacing formulas to apply;
- \a t varies between 0.0 and 1.0 within each sub-range. \b Insert button
+ normalized at [0.0,1.0]. f(t) must be non-negative
+ at 0. <= \a t <= 1. The whole extent of geometry can be
+ divided into ranges with their own spacing formulas to apply;
+ \a t varies between 0.0 and 1.0 within each \b Range. \b Insert button
divides a selected range into two. \b Delete button adds the
selected sub-range to the previous one. Double click on a range in
the list enables edition of its right boundary. Double click on a
diff --git a/doc/salome/gui/SMESH/input/changing_orientation_of_elements.doc b/doc/salome/gui/SMESH/input/changing_orientation_of_elements.doc
index 673e43fda..7253782c1 100644
--- a/doc/salome/gui/SMESH/input/changing_orientation_of_elements.doc
+++ b/doc/salome/gui/SMESH/input/changing_orientation_of_elements.doc
@@ -28,12 +28,12 @@
element will be added to the list. To remove a selected element or
elements from the list click the \b Remove button. The \b Sort button
allows to sort the list of elements IDs. The Set filter button
- allows to apply a definite \ref filtering_elements "filter" to
+ allows to apply a definite \ref filtering_elements "filter" to the
selection of elements.
Apply to all radio button allows to modify the orientation
of all elements of the selected mesh.
Select from set of fields allows to choose a sub-mesh or an
- existing group whose elements then can be added to the list.
+ existing group whose elements can be added to the list.
diff --git a/doc/salome/gui/SMESH/input/constructing_meshes.doc b/doc/salome/gui/SMESH/input/constructing_meshes.doc
index 66941609e..2ec8a4987 100644
--- a/doc/salome/gui/SMESH/input/constructing_meshes.doc
+++ b/doc/salome/gui/SMESH/input/constructing_meshes.doc
@@ -2,55 +2,54 @@
\page constructing_meshes_page Constructing meshes
-To create a mesh on geometry, at first you create a mesh object by choosing
+To create a mesh on geometry, it is necessary to create a mesh object by choosing
- a geometrical shape produced in the Geometry module (main shape);
- meshing parameters, including
- \ref basic_meshing_algos_page "meshing algorithms" and
- \ref about_hypo_page "hypotheses" specifying constraints to be
- taken into account by chosen meshing algorithms.
+ taken into account by the chosen meshing algorithms.
-Then you already can launch mesh generation by invoking \ref
-compute_anchor "Compute" command.
+Then you can launch mesh generation by invoking \ref compute_anchor "Compute" command.
\note Sometimes \a hypotheses term is used to refer to both algorithms
and hypotheses.
-Generation of the mesh on the geometry is performed in the bottom-up
+Mesh generation on the geometry is performed in the bottom-up
flow: nodes on vertices are created first, then edges are divided into
-segments using nodes on vertices; the segments of the edges is then
-used while meshing faces; then the mesh of the faces is used while meshing
+segments using nodes on vertices; the node of segments are then
+used to mesh faces; then the nodes of faces are used to mesh
solids. This automatically assures the conformity of the mesh.
-You are to choose a meshing algorithm for every dimension of
-sub-shapes up to the highest dimension you desire to generate. Note
-that some algorithms generate elements of several dimensions while
-others, of only one. But it's not necessary to define meshing
+It is required to choose a meshing algorithm for every dimension of
+sub-shapes up to the highest dimension to be generated. Note
+that some algorithms generate elements of several dimensions, and
+others of only one. It is not necessary to define meshing
parameters for all dimensions at once; you can start from 1D
meshing parameters only, compute the 1D mesh, then define 2D meshing
-parameters and compute the 2D mesh (note that 1D mesh won't be
+parameters and compute the 2D mesh (note that 1D mesh will not be
re-computed).
An algorithm of a certain dimension chosen at mesh creation is applied
-to discretize every sub-shape of this dimension. But you can
+to discretize every sub-shape of this dimension. It is possible to
specify a different algorithm or hypothesis to be applied to one or
a group of sub-shapes by creating a \ref constructing_submeshes_page
"sub-mesh". You can specify no algorithms at all at mesh object
creation and specify the meshing parameters on sub-meshes only; then
-only sub-shapes for which you defined an algorithm and a needed
-hypothesis (if any) will be discretized.
+only the sub-shapes, for which an algorithm and a hypothesis (if any)
+have been defined will be discretized.
-\n Construction of a mesh on some geometry includes at least two (mesh
-creation and computing) of the following steps:
+\n Construction of a mesh on a geometry includes at least two
+(\ref create_mesh_anchor "mesh creation" and
+\ref compute_anchor "computing") of the following steps:
-
\ref create_mesh_anchor "Creation of a mesh object" where you
+
\ref create_mesh_anchor "Creation of a mesh object", where you
can specify meshing parameters to apply to all sub-shapes of the
main shape.
-
\ref constructing_submeshes_page "Creation of sub-meshes"
- (optional) where you can specify meshing parameters to apply to
+
\ref constructing_submeshes_page "Creation of sub-meshes",
+ (optional) where you can specify meshing parameters to apply to the
selected sub-shapes.
\ref evaluate_anchor "Evaluating mesh size" (optional) can be
- used to know approximate number of elements before actual generation
- of them.
+ used to know an approximate number of elements before their actual generation.
\ref preview_anchor "Previewing the mesh" (optional) can be
used to generate mesh of only lower dimension(s) in order to
visually estimate it before full mesh generation, which can be much
@@ -61,8 +60,8 @@ creation and computing) of the following steps:
\ref compute_anchor "Computing the mesh" uses defined meshing
parameters to generate mesh elements.
\ref edit_anchor "Editing the mesh" (optional) can be used to
- \ref modifying_meshes_page "modify" mesh of lower dimension before
- \ref compute_anchor "computing" elements of upper dimension.
+ \ref modifying_meshes_page "modify" the mesh of a lower dimension before
+ \ref compute_anchor "computing" elements of an upper dimension.
\anchor create_mesh_anchor
@@ -103,10 +102,10 @@ creation and computing) of the following steps:
3D sub-shapes (solids) and generate 3D mesh elements
(tetrahedra, hexahedra etc.)
- As soon as you have selected an algorithm, you can create (or
- select already created) a hypothesis. A set of accessible
- hypotheses includes only hypotheses the selected algorithm can take
- into account.
+ As soon as you have selected an algorithm, you can create a
+ hypothesis (or select an already created one). A set of accessible
+ hypotheses includes only the hypotheses that can be used by the
+ selected algorithm.
\note
- Some page(s) can be disabled if the geometrical
@@ -115,10 +114,10 @@ creation and computing) of the following steps:
\b 3D page is disabled.
- Some algorithms affect the geometry of several dimensions,
i.e. 1D+2D or 1D+2D+3D. If such an algorithm is selected, the
- dialog box pages related to the corresponding lower dimensions are
+ dialog pages related to the corresponding lower dimensions are
disabled.
- - \b 0D page does not refer to the 0D elements, but to 0D
- geometry (vertices). Mesh module does not provide algorithms that
+ - \b 0D page refers to 0D geometry (vertices) rather than
+ to 0D elements. Mesh module does not provide algorithms that
produce 0D elements. Currently \b 0D page provides only one
algorithm "Segments around vertex" that allows specifying the required
size of mesh edges about the selected vertex (or vertices).
@@ -126,9 +125,9 @@ creation and computing) of the following steps:
For example, you need to mesh a 3D object.
First, you can change a default name of your mesh in the \b Name
- box. Then check that a selected geometrical object, whose name is
- shown in \b Geometry field, is that you wish to mesh; if not, click
- the right object in the Object Browser. Click "Select" button
+ box. Then check that the selected geometrical object indicated in
+ \b Geometry field, is what you wish to mesh; if not, select
+ the correct object in the Object Browser. Click "Select" button
near \b Geometry field if the name of the object has not yet
appeared in \b Geometry field.
@@ -189,13 +188,9 @@ creation and computing) of the following steps:
which is a 2D object, you do not need to define a 3D Algorithm and
Hypotheses.
- In the Object Browser the structure of the new mesh will be
+ In the Object Browser the structure of the new mesh is
displayed as follows:
-
-
\image html image88.jpg
-
-
It contains:
a mesh name (Mesh_mechanic);
@@ -205,6 +200,13 @@ creation and computing) of the following steps:
to the hypotheses chosen at the construction of the mesh;
Applied algorithms folder containing the references
to the algorithms chosen at the construction of the mesh.
+
SubMeshes on Face folder containing the sub-meshes
+ defined on geometrical faces. There also can be folders for
+ sub-meshes on vertices, edges, wires, shells, solids and
+ compounds.
+
Groups of Faces folder containing the groups of mesh
+ faces. There also can be folders for groups of nodes, edges,
+ volumes 0D elements and balls.
There is an alternative way to assign Algorithms and Hypotheses by
@@ -214,21 +216,32 @@ creation and computing) of the following steps:
CustomMeshers.xml file located in the home directory. CustomMeshers.xml
file must describe sets of hypotheses in the
same way as ${SMESH_ROOT_DIR}/share/salome/resources/smesh/StdMeshers.xml
- file does (sets of hypotheses are enclosed between
- tags).
-
-
+ file does (sets of hypotheses are enclosed between \
+ tags). For example:
+~~~~~~{.xml}
+
+
+
+
+
+
+
+~~~~~~
+ If the file contents are incorrect, there can be an error at
+ activation of Mesh module: "fatal parsing error: error
+ triggered by consumer in line ..."
+
+
\image html hypo_sets.png
List of sets of hypotheses. Tag [custom] is
automatically added to the sets defined by the user.
-
-
+
\note
- - \a "Automatic" in the names of predefined sets of
- hypotheses came from previous versions of SALOME where
- \ref automatic_length_anchor "Automatic Length" hypothesis
- was included in these sets, and not that these sets are suitable for
- meshing any geometry.
+ - \a "Automatic" in the names of predefined sets of hypotheses
+ does not actually mean that they are suitable for meshing any
+ geometry.
- The list of sets of hypotheses can be shorter than in the
above image depending on the geometry dimension.
@@ -253,7 +266,9 @@ information box:
Previewing the mesh
Before \ref compute_anchor "the mesh computation", it is also possible
-to see the mesh preview.
+to see the mesh preview. This operation allows to incrementally
+compute the mesh, dimension by dimension, and to discard an
+unsatisfactory mesh.
For this, select the mesh in the Object Browser. From the \b Mesh menu
select \b Preview or click "Preview" button in the toolbar or activate
@@ -371,8 +386,8 @@ will see the following information.
It is equally possible to skip \ref evaluate_anchor "the Evaluation"
and \ref preview_anchor "the Preview" and to \b Compute the mesh after
the hypotheses are assigned. For this, select your mesh in
-the Object Browser. From the \b Mesh menu select \b Compute or
-click "Compute" button of the toolbar.
+the Object Browser. From the \b Mesh menu or the context menu
+select \b Compute or click \a "Compute" button of the toolbar.
\image html image28.png
@@ -381,24 +396,25 @@ click "Compute" button of the toolbar.
After the mesh computation finishes, the Mesh Computation information
box appears. If you close this box and click "Compute" button again,
-without previously changing meshing parameters, the mesh is
-NOT re-computed and the Mesh Computation information box with
-the same contents is shown. (To fully re-compute the mesh, invoke \ref
-clear_mesh_anchor "Clear Mesh Data" command before).
+without previously changing meshing parameters, the mesh will NOT be
+re-computed and the Mesh Computation information box will be shown
+with the same contents. (To fully re-compute the mesh, invoke
+\ref clear_mesh_anchor "Clear Mesh Data" command before).
-In case of a success, the box shows information on number of entities
-of different types in the mesh.
+If the mesh computation has been a success, the box shows information
+on the number of entities of different types in the mesh.
\image html meshcomputationsucceed.png
\anchor meshing_failed_anchor
-If the mesh computation failed, the information about the cause of the
+If the mesh computation has failed, the information about the cause of the
failure is provided in \b Errors table.
\image html meshcomputationfail.png
-After you select an error, Show Sub-shape button allows
-visualizing in magenta the geometrical entity that causes the error.
+After you select an error in \b Errors table, Show Sub-shape button allows
+visualizing in magenta the geometrical entity meshing of which failed
+(Name of this entity or its ID and type is shown in \a Sub-shape column).
\image html failed_computation.png
@@ -439,12 +455,12 @@ By default, the information box is always shown after mesh computation operation
\anchor edit_anchor
Editing the mesh
-It is possible to \ref modifying_meshes_page "edit the mesh" of
-lower dimension before generation of mesh of higher dimension.
+It is possible to \ref modifying_meshes_page "edit the mesh" of a
+lower dimension before generation of the mesh of a higher dimension.
-For example you can generate 2D mesh, modify it using e.g.
-\ref pattern_mapping_page, and then generate 3D mesh basing on the
-modified 2D mesh. The workflow is following:
+For example you can generate a 2D mesh, modify it using e.g.
+\ref pattern_mapping_page, and then generate a 3D mesh basing on the
+modified 2D mesh. The workflow is as follows:
- Define 1D and 2D meshing algorithms.
- Compute the mesh. 2D mesh is generated.
- Apply \ref pattern_mapping_page.
@@ -453,9 +469,9 @@ and hypotheses.
- Compute the mesh. 3D mesh is generated.
\note Nodes and elements added \ref adding_nodes_and_elements_page
-"manually" can't be used in this workflow because the manually created
-entities are not attached to any geometry and thus (usually) can't be
-found by a mesher paving some geometry.
+"manually" cannot be used in this workflow because the manually created
+entities are not attached to any geometry and thus (usually) cannot be
+found by the mesher paving a geometry.
See Also a sample TUI Script demonstrates the possibility of
\ref tui_editing_while_meshing "Intermediate edition while meshing"
diff --git a/doc/salome/gui/SMESH/input/constructing_submeshes.doc b/doc/salome/gui/SMESH/input/constructing_submeshes.doc
index 9da2e4f7f..43f99e5c5 100644
--- a/doc/salome/gui/SMESH/input/constructing_submeshes.doc
+++ b/doc/salome/gui/SMESH/input/constructing_submeshes.doc
@@ -11,8 +11,8 @@ and/or hypotheses than those used to generate the mesh on other
sub-shapes.
Creation of a sub-mesh allows to control individually meshing of a
-certain sub-shape, thus allowing to get mesh locally coarser or finer, to get
-elements of different types in the same mesh etc.
+certain sub-shape, thus to get a locally coarser or finer mesh, to get
+elements of different types in the same mesh, etc.
A sub-shape to create a sub-mesh on should be retrieved from the main shape
in one of the following ways:
@@ -33,7 +33,7 @@ compound of solids, starts from searching an algorithm, 1D as for the
edge. The following sub-shapes are sequentially checked for presence
of a sub-mesh where 1D algorithm is assigned:
-
the \b edge it-self
+
the \b edge itself
groups of edges containing the edge, if any
\b wires sharing the edge
\b faces sharing the edge
@@ -43,29 +43,28 @@ of a sub-mesh where 1D algorithm is assigned:
groups of solids sharing the edge, if any
the main shape
-(This sequence of sub-shapes defines priority of sub-meshes. Thus more
+(This sequence of sub-shapes defines the priority of sub-meshes. Thus more
local, i.e. assigned to sub-shape of lower dimension, algorithms and
hypotheses have higher priority during the search of hypotheses to
apply.)
-As soon as an 1D algorithm is found the search stops and the same
-sequence of sub-shapes is checked to find a main and additional 1D
-hypotheses the found 1D algorithm can take into account.
+As soon as a 1D algorithm is found, the search stops and the same
+sequence of sub-shapes is checked to find the main and additional 1D
+hypotheses, which can be taken into account by the found 1D algorithm.
-The multi-dimensional algorithms have higher priority than
-uni-dimensional algorithms if they are assigned to sub-meshes of the
+The multi-dimensional algorithms have a higher priority than
+uni-dimensional ones if they are assigned to sub-meshes of the
same priority.
If meshing parameters are defined on sub-meshes of the same priority,
-for example different 1D hypotheses are assigned to two faces sharing
+for example, different 1D hypotheses are assigned to two faces sharing
an edge, the hypothesis assigned to a sub-shape with a lower ID will
be used for meshing. You can \ref submesh_order_anchor "change" mutual
priority of such concurrent sub-meshes.
-
\n Construction of a sub-mesh consists of:
-
Selecting a mesh which will encapsulate your sub-mesh
+
Selecting a mesh which will encapsulate the sub-mesh
Selecting a sub-shape for meshing
Applying one or several
\ref about_hypo_page "hypotheses" and
@@ -94,7 +93,7 @@ Geometry (e.g. a face if the parent mesh has been built on box) of the
sub-mesh. You can define meshing algorithms and hypotheses in the same way as
in \ref constructing_meshes_page "Create mesh" dialog.
-Later you can change applied hypotheses or their parameters in
+Later you can change the applied hypotheses or their parameters in
\ref editing_meshes_page "Edit mesh/sub-mesh" dialog. Mesh entities
generated using changed hypotheses are automatically removed.
diff --git a/doc/salome/gui/SMESH/input/convert_to_from_quadratic_mesh.doc b/doc/salome/gui/SMESH/input/convert_to_from_quadratic_mesh.doc
index a8ad620b5..a253c0523 100644
--- a/doc/salome/gui/SMESH/input/convert_to_from_quadratic_mesh.doc
+++ b/doc/salome/gui/SMESH/input/convert_to_from_quadratic_mesh.doc
@@ -51,7 +51,7 @@ The following dialog box will appear:
Quadratic mesh
-
Click the \b Apply or \b OK button.
+
Click the \b Apply or Apply and Close button.
See Also a sample TUI Script of a \ref tui_quadratic "Convert to/from quadratic" operation.
diff --git a/doc/salome/gui/SMESH/input/create_groups_from_geometry.doc b/doc/salome/gui/SMESH/input/create_groups_from_geometry.doc
index 34a09a449..009866e47 100644
--- a/doc/salome/gui/SMESH/input/create_groups_from_geometry.doc
+++ b/doc/salome/gui/SMESH/input/create_groups_from_geometry.doc
@@ -14,9 +14,9 @@ menu in the Object browser Create Groups from Geometry item.
\image html create_groups_from_geometry.png
-In this dialog \b Elements group contains a list of shapes to create
-groups of elements on them; \b Nodes group contains a list of shapes
-to create groups of node on them.
+In this dialog \b Elements group contains a list of shapes, on which
+groups of elements will be created; \b Nodes group contains a list of shapes,
+on which groups of nodes will be created.
*/
diff --git a/doc/salome/gui/SMESH/input/creating_groups.doc b/doc/salome/gui/SMESH/input/creating_groups.doc
index 796353528..da12c8337 100644
--- a/doc/salome/gui/SMESH/input/creating_groups.doc
+++ b/doc/salome/gui/SMESH/input/creating_groups.doc
@@ -23,7 +23,9 @@ elements which will form your group:
Name field allows to enter the name of your new group.
Color - allows to assign to the group a certain color. The
- chosen color is used to display the elements of the group.
+ chosen color is used to display the elements of the group.
+ Activation of Auto Color item in mesh context menu
+ switches on a random choice of a color for a new group.
Mesh module distinguishes between the three Group types:
Standalone Group, Group on Geometry and Group on Filter.
@@ -98,11 +100,11 @@ of a certain type generated on the selected geometrical object. Group
contents are dynamically updated if the mesh is modified. The group on
geometry can be created only if the mesh is based on geometry.
-To define a group, click a \a Selection button and chose
+To define a group, click the \a Selection button and choose
- Direct geometry selection to select a shape in the Object
Browser or in the Viewer;
- Find geometry by mesh element selection to activate a
- dialog which retrieves a shape by a selected element generated on
+ dialog which retrieves a shape by the selected element generated on
this shape.
Note that this choice is available only if the mesh elements are
@@ -130,8 +132,8 @@ of a certain type satisfying the defined filter. Group contents are
dynamically updated if the mesh is modified.
To define a group, click the Set filter button and define
-criteria of the filter in the opened dialog. After confirmation of the
-operation a new group of mesh elements will be created. See more about
+criteria of the filter in the opened dialog. After the
+operation is confirmed, a new group of mesh elements will be created. See more about
filters on the
\ref selection_filter_library_page "Selection filter library" page.
diff --git a/doc/salome/gui/SMESH/input/diagonal_inversion_of_elements.doc b/doc/salome/gui/SMESH/input/diagonal_inversion_of_elements.doc
index 1bc75ef20..c97663de2 100644
--- a/doc/salome/gui/SMESH/input/diagonal_inversion_of_elements.doc
+++ b/doc/salome/gui/SMESH/input/diagonal_inversion_of_elements.doc
@@ -18,7 +18,8 @@ The following dialog box shall appear:
\image html diagonalinversion.png
-
Enter IDs of nodes forming the required edge in the \b Edge field (the node IDs must be separated by a dash) or select
+
Enter IDs of nodes forming the required edge in the \b Edge field
+(the node IDs must be separated by dashes) or select
this edge in the 3D viewer.
Click the \b Apply or Apply and Close button.
diff --git a/doc/salome/gui/SMESH/input/extrusion.doc b/doc/salome/gui/SMESH/input/extrusion.doc
index 6337e5a0e..56cb32f4c 100644
--- a/doc/salome/gui/SMESH/input/extrusion.doc
+++ b/doc/salome/gui/SMESH/input/extrusion.doc
@@ -8,7 +8,7 @@ mesh of plus one dimension are additionally created. All created
elements can be automatically grouped. Extrusion can be used to create
a \ref extrusion_struct "structured mesh from scratch".
-\image html extrusion_box.png "If you extrude several quadrangles, you get exactly same mesh as if you meshed a geometrical box (except that the initial quadrangles can be incorrectly oriented): quadrangles and segments on boundary of generated mesh are created"
+\image html extrusion_box.png "If you extrude several quadrangles, you get exactly the same mesh as if you meshed a geometrical box (except for that the initial quadrangles can be incorrectly oriented): quadrangles and segments are created on the boundary of the generated mesh"
Any node, segment or 2D element can be extruded. Each type of
elements is extruded into a corresponding type of result elements:
@@ -22,6 +22,14 @@ elements is extruded into a corresponding type of result elements:
Hexagonal polygon
Hexagonal prism
+When 2D elements are extruded, in addition to 3D elements segments are
+created on ribs of the result 3D mesh. Free edges of input 2D elements
+generate logically horizontal rib segments. Logically vertical rib
+segments are generated from nodes belonging to a sole input 2D element
+(a figure below illustrates this rule).
+
+\image html extru_rib_segs.png "Two triangles extruded: no vertical rib segments generated from nodes #2 and #3 as they are shared by both triangles"
+
To use extrusion:
From the \b Modification menu choose the \b Extrusion item or click
@@ -32,24 +40,24 @@ elements is extruded into a corresponding type of result elements:
"Extrusion" button
-The following dialog, looking different depending on selected options,
-will appear:
+The following dialog will appear:
\image html extrusionalongaline1.png
-\image html extrusionalongaline2.png
-
-\image html extrusionalongaline3.png
-
In this dialog:
+
Use \a Selection button to specify what you are going to
+ select at a given moment, \b Nodes, \b Edges or \b Faces.
+ \image html image120.png
+
"Selection" button
+
Specify \b Nodes, \b Edges and \b Faces, which will be extruded, by one
of following means:
-
Select the whole mesh, sub-mesh or group activating this
- checkbox.
+
Select the whole mesh, sub-mesh or group activating the
+ corresponding check-box.
Choose mesh elements with the mouse in the 3D Viewer. It is
possible to select a whole area with a mouse frame.
Input the element IDs directly in Node IDs, Edge
@@ -63,7 +71,11 @@ will appear:
If the Extrusion to Distance radio button is selected
- specify the translation vector by which the elements will be extruded.
-
If the Extrusion Along Vector radio button is selected
+
+
+\image html extrusionalongaline2.png
+
+
If the Extrusion Along Vector radio button is selected
specify the coordinates of the \b Vector along which the elements
will be extruded, either directly or by selecting the mesh face (the
@@ -72,19 +84,23 @@ will appear:
be negative).
+
+
+\image html extrusionalongaline3.png
+
If the Extrusion By Normal radio button is selected,
- every node of selected faces is extruded along the \a average
+ every node of the selected faces is extruded along the \a average
of the \a normal vectors to the faces sharing the node. (Nodes and
- edges can't be extruded in this mode.)
+ edges cannot be extruded in this mode.)
Specify the \b Distance of extrusion (it can be negative),
Use Along average normal check-box to specify along
- what vector the distance is measured.
+ which vector the distance is measured.
If it is \a activated the distance is measured along the
average normal mentioned above.
If it is \a deactivated every node is extruded along the
- average normal till its intersection with the virtual plane got
+ average normal till its intersection with a virtual plane obtained
by translation of the face sharing the node along its own normal
by the \b Distance.
@@ -95,8 +111,8 @@ will appear:
\image html extrusionbynormal_alongavgnorm.png "'Along average normal' activated (to the left) and deactivated (to the right)"
-
Using Use only input elements check-box specify what
- elements to use to compute the average normal.
+
Use only input elements check-box specifies what
+ elements will be used to compute the average normal.
If it is \a activated only selected faces, among faces
sharing the node, are used to compute the average normal at
the node.
diff --git a/doc/salome/gui/SMESH/input/free_borders.doc b/doc/salome/gui/SMESH/input/free_borders.doc
index 86e5e2a37..3a8497c30 100644
--- a/doc/salome/gui/SMESH/input/free_borders.doc
+++ b/doc/salome/gui/SMESH/input/free_borders.doc
@@ -2,14 +2,16 @@
\page free_borders_page Free borders
-\n This mesh quality control highlights borders of faces consisting of
-1D elements (segments) belonging to one face only.
+\n This mesh quality control highlights 1D elements (segments)
+belonging to one element (face or volume) only.
\image html free_borders1.png
-In this picture the free borders are displayed in white.
+In this picture the free borders are displayed in red. (Faces are
+explicitly shown via Display Entity menu as all elements but
+segments are hidden upon this control activation).
See Also a sample TUI Script of a
\ref tui_free_borders "Free Borders quality control" operation.
-*/
\ No newline at end of file
+*/
diff --git a/doc/salome/gui/SMESH/input/free_edges.doc b/doc/salome/gui/SMESH/input/free_edges.doc
index 1a5720ee2..2e9d4a6ec 100644
--- a/doc/salome/gui/SMESH/input/free_edges.doc
+++ b/doc/salome/gui/SMESH/input/free_edges.doc
@@ -3,7 +3,7 @@
\page free_edges_page Free edges
\n This mesh quality control highlights borders of faces
-consisting of node links belonging to one face only.
+(links between nodes, not mesh segments) belonging to one face only.
\image html free_edges.png
In this picture some elements of mesh have been deleted and
diff --git a/doc/salome/gui/SMESH/input/group_of_underlying_elements.doc b/doc/salome/gui/SMESH/input/group_of_underlying_elements.doc
index e24cebd3e..7d31f7350 100755
--- a/doc/salome/gui/SMESH/input/group_of_underlying_elements.doc
+++ b/doc/salome/gui/SMESH/input/group_of_underlying_elements.doc
@@ -19,12 +19,12 @@ In this dialog box specify
\b All - include if all nodes are common;
\b Main - include if all corner nodes are common (meaningful for
a quadratic mesh)
-
At least one - include if one or more node is common
-
\b Majority - include if half of nodes or more is common
+
At least one - include if one or more nodes are common
+
\b Majority - include if half or more nodes are common
select reference groups,
-
Include underlying entities only option if activated
- allows inclusion of an entity provided that it is based on nodes of
+
If Include underlying entities only option is activated
+ an entity can be included if it is based on nodes of
one element of a reference group.
diff --git a/doc/salome/gui/SMESH/input/grouping_elements.doc b/doc/salome/gui/SMESH/input/grouping_elements.doc
index b0b4ab065..9548913da 100644
--- a/doc/salome/gui/SMESH/input/grouping_elements.doc
+++ b/doc/salome/gui/SMESH/input/grouping_elements.doc
@@ -12,35 +12,36 @@ visualization only and is not exported.
There are three types of groups different by their internal
organization:
Standalone group is a static set of mesh entities. Its
- contents can be explicitely controlled by the user. Upon removal of
+ contents can be explicitly controlled by the user. Upon removal of
the entities included into the group, the group becomes empty and
- the user is to pay efforts to restore its contents. Hence it is
- resonable to create standalone groups when the mesh generation is
+ its content can be restored only manually. Hence it is
+ reasonable to create standalone groups when the mesh generation is
finished and mesh quality is verified.
\warning Creation and edition of large standalone groups in
\ref creating_groups_page "Create group" dialog using manual edition
is problematic due to poor performance of the dialog.
-
Group on geomerty is associated to one or a group of
+
+
Group on geometry is associated to a sub-shape or a group of
sub-shapes of the main shape and includes mesh entities generated on
- this geometrical entities. The association to geometry is
- established at group construction and can't be changed. The group
- contents is always up-to-date without user's efforts, hence the
+ these geometrical entities. The association to a geometry is
+ established at group construction and cannot be changed. The group
+ contents are always updated automatically, hence the
group can be created even before mesh elements generation.
-
Group on filter encapsulates a filter which is used to
+
Group on filter encapsulates a filter, which is used to
select mesh entities composing the group from the whole
mesh. Criteria of the filter can be changed at any time. The
- group contents is always up-to-date without user's efforts, hence
+ group contents are always updated automatically, hence
the group can be created even before mesh elements generation.
The group on geometry and group on filter can be converted to
-the standalone group.
+a standalone group.
\image html groups_in_OB.png "Groups of different types look differently in the Object Browser"
The following ways of group creation are possible:
- \subpage creating_groups_page "Create group" dialog allows creation of
- a group of any of all the three types:
+ a group of any type:
\ref standalone_group "Standalone group",
\ref group_on_geom "Group on geometry" and
\ref group_on_filter "Group on filter" using dedicated tabs.
@@ -49,7 +50,7 @@ The following ways of group creation are possible:
- Standalone groups of all nodes and elements of the chosen sub-mesh
(type of elements depends on dimension of sub-mesh geometry) can
be created using Mesh -> Construct Group menu item (available
- in context menu as well).
+ from the context menu as well).
- Standalone groups of any element type can be created basing on nodes
of other groups - using \subpage group_of_underlying_elements_page
"Group based on nodes of other groups" dialog.
@@ -69,10 +70,9 @@ The created groups can be later:
- \ref importing_exporting_meshes_page "Exported" into a file as a
whole mesh.
-In the Object Browser, if groups container item includes more
-than one group, it is possible to sort the groups by name in
-ascending order. For this, select the groups container in the Object
-Browser and choose Sort children context menu item.
+In the Object Browser, if an item contains more than one child group,
+it is possible to sort the groups by name in ascending order
+using Sort children context menu item.
\image html smesh_sort_groups.png "Sorting groups"
diff --git a/doc/salome/gui/SMESH/input/importing_exporting_meshes.doc b/doc/salome/gui/SMESH/input/importing_exporting_meshes.doc
index 516981cd9..b8951f00a 100644
--- a/doc/salome/gui/SMESH/input/importing_exporting_meshes.doc
+++ b/doc/salome/gui/SMESH/input/importing_exporting_meshes.doc
@@ -4,8 +4,8 @@
\n In MESH there is a functionality allowing import/export
of meshes from/to \b MED, \b UNV (I-DEAS 10), \b DAT (simple ascii format), \b STL,
-\b GMF (internal format of DISTENE products, namely BLSurf, GHS3D and
-Hexotic algorithms) and \b CGNS format files. You can also export a
+\b GMF (internal format of DISTENE products, namely MG-CADSurf, MG-Tetra and
+MG-Hexa algorithms) and \b CGNS format files. You can also export a
group as a whole mesh.
diff --git a/doc/salome/gui/SMESH/input/index.doc b/doc/salome/gui/SMESH/input/index.doc
index 48047a296..9ecb7c5f0 100644
--- a/doc/salome/gui/SMESH/input/index.doc
+++ b/doc/salome/gui/SMESH/input/index.doc
@@ -16,25 +16,31 @@
either \ref importing_exporting_meshes_page "imported" or manually
created);
-
\ref importing_exporting_meshes_page "import and export of meshes in various formats";
+
\ref importing_exporting_meshes_page "importing and exporting meshes"
+ in various formats;
\subpage modifying_meshes_page "modifying meshes" with a vast
array of dedicated operations;
-
\subpage grouping_elements_page "creating groups of mesh elements";
+
\subpage grouping_elements_page "creating groups" of mesh
+ elements;
filtering mesh entities (nodes or elements) using
\subpage filters_page "Filters" functionality for \ref
grouping_elements_page "creating groups" and applying \ref
modifying_meshes_page "mesh modifications";
\subpage viewing_meshes_overview_page "viewing meshes" in
- the VTK viewer;
+ the VTK viewer and \ref mesh_infos_page "getting info" on mesh
+ and its sub-objects;
applying to meshes \subpage quality_page "Quality Controls",
- allowing to highlight important elements;
-
various \subpage measurements_page "measurements" of the mesh objects.
+ allowing to highlight important elements;
+
taking various \subpage measurements_page "measurements" of the
+ mesh objects.
-When setting parameters of operations, it is possible to use the variables predefined in
-\subpage using_notebook_mesh_page "Salome notebook".
+It is possible to use the variables predefined in
+\subpage using_notebook_mesh_page "Salome notebook" to set parameters
+of operations.
-Mesh module preferences are described in the \subpage mesh_preferences_page section of SALOME Mesh Help.
+Mesh module preferences are described in the \subpage mesh_preferences_page
+section of SALOME Mesh Help.
Almost all mesh module functionalities are accessible via
\subpage smeshpy_interface_page "Mesh module Python interface".
diff --git a/doc/salome/gui/SMESH/input/merging_elements.doc b/doc/salome/gui/SMESH/input/merging_elements.doc
index 9cde2b0ce..6236ad02b 100644
--- a/doc/salome/gui/SMESH/input/merging_elements.doc
+++ b/doc/salome/gui/SMESH/input/merging_elements.doc
@@ -2,68 +2,62 @@
\page merging_elements_page Merging Elements
-\n This functionality allows to merge coincident elements of a mesh
-object selectable in the dialog box. Two elements are considered coincident if they are based on the same set of nodes.
+\n This functionality allows to merge coincident elements of a
+mesh. Two elements are considered coincident if they are based on the
+same set of nodes.
\image html mergeelems_ico.png "Merge elements menu button"
-
-
Choose in the main menu \b Modification -> \b Transformation
- -> Merge elements item. The following dialog box shall
- appear:
+To merge elements choose in the main menu \b Modification -> \b Transformation
+-> Merge elements item. The following dialog box shall
+appear:
\image html mergeelems_auto.png
-
-
-
\b Name is the name of the mesh object whose elements will be
- merged.
-
\b Automatic or \b Manual Mode allows choosing how the elements
- are processed.
-
-
Automatic mode:
+In this dialog:
-
In the \b Automatic Mode the elements created on the same nodes
- will be merged.
-
-
+
\b Name is the name of the mesh object whose elements will be
+ merged.
+
\b Automatic or \b Manual Mode allows choosing how the elements
+ are processed. In the \b Automatic Mode all elements created on
+ the same nodes will be merged. In \b Manual mode you can adjust
+ groups of coincident elements detected by the program.
-
If the \b Manual Mode is selected, additional controls are
- available:
+ If the \b Manual Mode is selected, additional controls are
+ available:
\image html mergeelems.png
-
\b Detect button generates the list of coincident elements found
- in the selected object.
-
Coincident elements is a list of groups of elements for
- merging. As result of the operation all elements of each group will
- be replaced by the firts element of the group.
-
-
\b Remove button deletes the selected group from the list.
-
\b Add button adds to the list a group of elements selected in the
- viewer with pressed "Shift" key.
-
Select all checkbox selects all groups.
-
Show double elements IDs checkbox shows/hides identifiers of
- elements of selected groups in the 3D viewer.
-
-
Edit selected group list allows editing the selected group:
-
-\image html add.png
-
adds to the group the elements selected in the viewer.
-
-\image html remove.png
-
removes from the group the selected elements.
-
-\image html sort.png
-
moves the selected element to the first position in the
- group. This means that all other elements of the group will be
- replaced by this one.
-
-
-
To confirm your choice click \b Apply or Apply and Close button.
+
\b Detect button generates the list of coincident elements found
+ in the selected object.
+
Coincident elements is a list of groups of elements for
+ merging. After the operation all elements of each group will
+ be united into one element. The first element of a group is kept and
+ the others are removed.
+
\b Remove button deletes the selected group from the list.
+
\b Add button adds to the list a group of elements selected in the
+ viewer with pressed "Shift" key.
+
Select all check-box selects all groups.
+
Show double elements IDs check-box shows/hides identifiers of
+ elements of the selected groups in the 3D viewer.
+
Edit selected group of coincident elements list allows
+ editing the selected group:
+
+ \image html add.png
+
adds to the group the elements selected in the viewer.
+
+ \image html remove.png
+
removes the selected elements from the group.
+
+ \image html sort.png
+
moves the selected element to the first position in the
+ group in order to keep it in the mesh.
+
+
+
+
To confirm your choice click \b Apply or Apply and Close button.
-
In this picture you see a triangle which coincides with one of the
elements of the mesh. After we apply Merge Elements functionality, the
diff --git a/doc/salome/gui/SMESH/input/merging_nodes.doc b/doc/salome/gui/SMESH/input/merging_nodes.doc
index 76692add1..8aff9aa09 100644
--- a/doc/salome/gui/SMESH/input/merging_nodes.doc
+++ b/doc/salome/gui/SMESH/input/merging_nodes.doc
@@ -18,35 +18,59 @@ then converted to the single node.
\b Name is the name of the mesh whose nodes will be merged.
\b Automatic or \b Manual mode allows choosing how the nodes are
-processed.
+ processed. In \b Manual mode you can adjust groups of coincident nodes
+ detected by the program and/or select any nodes to be merged.
\b Tolerance is a maximum distance between nodes sufficient for
merging.
-
Exclude Groups group box allows to ignore the nodes which
-belong to the specified mesh groups.
+
Activation of No merge of corner and medium nodes of quadratic
+ cells check-box prevents merging medium nodes of quadratic
+ elements with corner nodes. This check-box is enabled provided
+ that the selected mesh includes quadratic elements.
+
Exclude groups from detection group allows to ignore the
+ nodes which belong to the specified mesh groups. This control is
+ active provided that the mesh includes groups.
+
Nodes to keep during the merge group allows to specify
+ nodes to keep in the mesh. (By default a node being the first in a
+ group of coincident nodes is kept.) It is possible to either select
+ nodes in the Viewer or select groups of any element type whose nodes
+ will be kept.
+
+
\a Selection button activates selection of nodes to keep.
+
Nodes button activates selection of nodes in the
+ Viewer.
+
Groups and sub-meshes button activates selection of
+ groups and sub-meshes.
+
\b Add button adds selected nodes or groups to the list.
+
Nodes or groups selected in the list can be removed using \b
+ Remove button.
+
+
Automatic mode:
-
In the \b Automatic Mode all Nodes within the indicated tolerance
-will be merged. The nodes which belong to the groups specified in the
-Exclude Groups will be not taken into account.
+
In the \b Automatic Mode all nodes within the indicated tolerance
+will be merged. The nodes which belong to the groups specified in
+Exclude groups from detection will NOT be taken into account.
The \b Manual mode gives you full control of what the operation will do.
In this mode additional controls are available:
-
\b Detect button generates the list of coincident nodes for the given
-\b Tolerance.
-
Coincident nodes is a list of groups of nodes for
- merging. As result of the operation all nodes of each group will be
- replaces by the firts node of the group.
+
\b Detect button generates the list of coincident nodes for the given
+ \b Tolerance.
+
Coincident nodes is a list of groups of nodes for
+ merging. Upon \b Apply all nodes of each group will
+ be united into one node. The first node of a group is kept and
+ the others are removed. By default the first node has a lowest ID
+ within the group.
\b Remove button deletes the selected group from the list.
\b Add button adds to the list a group of nodes selected in the
-viewer with pressed "Shift" key.
-
Select all checkbox selects all groups.
-
Show double nodes IDs checkbox shows/hides identifiers of
+viewer.
+
Select all check-box selects all groups.
+
Show double nodes IDs check-box shows/hides identifiers of
nodes of selected groups in the 3D viewer.
@@ -54,28 +78,32 @@ nodes of selected groups in the 3D viewer.
\image html mergenodes.png
-
Edit selected group list allows editing the selected
- group:
-
- \image html add.png
-
adds to the group the nodes selected in the viewer.
-
- \image html remove.png
-
removes from the group the selected nodes.
-
- \image html sort.png
-
moves the selected node to the first position in the
- group. This means that all other nodes of the group will be
- replaced by this one.
-
+
Edit selected group of coincident nodes list allows
+ editing the selected group:
+
+ \image html add.png
+
adds to the group the nodes selected in the viewer.
+
+ \image html remove.png
+
removes from the group the selected nodes.
+
+ \image html sort.png
+
moves the selected node to the first position in the
+ group in order to keep it in the mesh.
+
To confirm your choice click \b Apply or Apply and Close button.
-\image html merging_nodes1.png "The initial obgect"
-
-\image html merging_nodes2.png "The object has been merged with a very big tolerance"
+\image html merging_nodes1.png
+
The initial object. Nodes 25, 26 and 5 are added to Nodes
+ to keep during the merge group.
+
+
+\image html merging_nodes2.png
+
The object has been merged
+
See Also a sample TUI Script of a
\ref tui_merging_nodes "Merge Nodes" operation.
diff --git a/doc/salome/gui/SMESH/input/mesh_infos.doc b/doc/salome/gui/SMESH/input/mesh_infos.doc
index 8ead995f0..2013cd426 100644
--- a/doc/salome/gui/SMESH/input/mesh_infos.doc
+++ b/doc/salome/gui/SMESH/input/mesh_infos.doc
@@ -14,14 +14,16 @@ in the toolbar.
"Mesh Information" button
The Mesh Information dialog box provides three tab pages:
-- \ref advanced_mesh_infos_anchor "Base Info" - to show base
-information about the selected mesh object.
+- \ref advanced_mesh_infos_anchor "Base Info" - to show
+ base and quantitative information about the selected mesh object.
- \ref mesh_element_info_anchor "Element Info" - to show
-detailed information about the selected mesh node or element.
-- \ref mesh_addition_info_anchor "Additional Info" - to show additional information available
-for the selected mesh, sub-mesh or group object.
+ detailed information about the selected mesh nodes or elements.
+- \ref mesh_addition_info_anchor "Additional Info" - to show
+ additional information available for the selected mesh, sub-mesh or
+ group object.
- \ref mesh_quality_info_anchor "Quality Info" - to show
-overall quality information about the selected mesh, sub-mesh or group object.
+ overall quality information about the selected mesh, sub-mesh or group
+ object.
\anchor advanced_mesh_infos_anchor
Base Information
@@ -43,7 +45,8 @@ information about the selected mesh node(s) or element(s), namely:
- For a node:
- Node ID;
- Coordinates (X, Y, Z);
- - Connectivity information (connected elements);
+ - Connectivity information (connected elements); double click in
+ this line makes the dialog show information of these elements;
- Position on a shape (for meshes built on a geometry);
- Groups information (names of groups the node belongs to).
@@ -55,7 +58,8 @@ information about the selected mesh node(s) or element(s), namely:
- Element ID;
- Type (triangle, quadrangle, etc.);
- Gravity center (X, Y, Z coordinates);
- - Connectivity information (connected nodes);
+ - Connectivity information (connected nodes); double click in
+ a line of a node makes the dialog show information of this node;
- Quality controls (area, aspect ration, volume, etc.);
- Position on a shape (for meshes built on a geometry);
- Groups information (names of groups the element belongs to).
@@ -63,7 +67,7 @@ information about the selected mesh node(s) or element(s), namely:
\image html eleminfo2.png
"Element Info" page, element information
-The use can either input the ID of a node or element he wants to
+The user can either input the ID of a node or element he wants to
analyze directly in the dialog box or select the node(s) or element(s) in
the 3D viewer.
@@ -152,6 +156,8 @@ button. Also, values are automatically computed if the number of
nodes / elements does not exceed the "Automatic controls compute limit" set
via the "Mesh information" preferences (zero value means that there is no limit).
+\note The plot functionality is available only if GUI module is builded with Plot 2D Viewer (set option SALOME_USE_PLOT2DVIEWER to ON when building GUI module).
+
The button \b "Dump" allows printing the information displayed in the
dialog box to a .txt file.
diff --git a/doc/salome/gui/SMESH/input/mesh_preferences.doc b/doc/salome/gui/SMESH/input/mesh_preferences.doc
index 7c47c1fa2..26efbe272 100644
--- a/doc/salome/gui/SMESH/input/mesh_preferences.doc
+++ b/doc/salome/gui/SMESH/input/mesh_preferences.doc
@@ -44,17 +44,17 @@ or in later sessions with this module according to the preferences.
presentation mode as default.
- Representation of the 2D quadratic elements
- - Default mode of the 2D quadratic elements combobox - allows
+ - Default mode of the 2D quadratic elements combo-box - allows
to select lines or arcs for representation of quadratic elements as default.
- Maximum Angle - maximum deviation angle used by the
application to build arcs.
- Mesh export
- - If you toggle Automatically create groups for MED export checkbox,
+ - If you toggle Automatically create groups for MED export check-box,
this operation will be carried out automatically.
- Mesh computation
- - Show a computation result notification combobox allows to
+ - Show a computation result notification combo-box allows to
select the notification mode about a mesh computation result.
There are 3 possible modes:
- Never - do not show the result dialog at all;
@@ -132,16 +132,16 @@ or in later sessions with this module according to the preferences.
\image html pref22.png
- Nodes allows to define default parameters for nodes, which will be applied
- for a new created mesh only. Customization of already created meshes can be done using
- \ref colors_size_page "Properties dialog box" that is called by click on popup menu of mesh.
+ for a newly created mesh only. Existing meshes can be customized using
+ \ref colors_size_page "Properties dialog box" available from the context menu of a mesh.
- Color - allows to select the color of nodes. Click on the
colored line to access to the Select Color dialog box.
- Type of marker - allows to define the shape of nodes.
- Scale of marker - allows to define the size of nodes.
- Elements allows to define default parameters for different elements, which will be applied
- for a new created mesh only. Customization of already created meshes can be done using
- \ref colors_size_page "Properties dialog box" that is called by click on popup menu of mesh.
+ for a newly created mesh only. Existing meshes can be customized using
+ \ref colors_size_page "Properties dialog box" available from the context menu of a mesh.
- Surface color - allows to select the surface color of 2D elements
(seen in Shading mode). Click on the colored line to access to the
Select Color dialog box.
@@ -175,21 +175,21 @@ or in later sessions with this module according to the preferences.
- Groups
- Names color - specifies color of group names to be used in
3D viewer.
- - Default color - specifies default group color, which is used
- when creating new mesh group (see \ref creating_groups_page "Create Group dialog box").
+ - Default color - specifies the default group color, which is used
+ to create a new mesh group (see \ref creating_groups_page "Create Group dialog box").
- Numbering allows to define properties of numbering functionality:
- Nodes - specifies text properties of nodes numbering
(font family, size, attributes, color).
- Elements - same for elements.
-- Orientation of Faces - allows to define the behavior of
- Orientation of faces functionality, which will be applied
- for a new created mesh only. Customization of already created meshes can be done using
- \ref colors_size_page "Properties dialog box" that is called by click on popup menu of mesh.
- - \b Color - allows to define the color of orientation vertors;
+- Orientation of Faces - allows to define default properties of orientation vectors.
+ These preferences will be applied to the newly created meshes only; properties of existing meshes
+ can be customized using \ref colors_size_page "Properties dialog box"
+ available from the context menu of a mesh.
+ - \b Color - allows to define the color of orientation vectors;
- \b Scale - allows to define the size of orientation vectors;
- - 3D Vector checkbox allows to choose between 2D planar
+ - 3D Vector check-box allows to choose between 2D planar
and 3D vectors.
Selection Preferences
@@ -220,9 +220,9 @@ or in later sessions with this module according to the preferences.
\image html pref24.png
\note The following settings are default and will be applied for
-a new created mesh only. Customization of already created meshes
-can be done using local \ref scalar_bar_dlg "Scalar Bar Properties dialog box"
-that is called by click on popup menu of mesh.
+a newly created mesh only. Existing meshes
+can be customized using local \ref scalar_bar_dlg "Scalar Bar Properties dialog box"
+available from the context menu of a mesh.
- Font - in this menu you can set type, face and color for
the font of Title and Labels.
diff --git a/doc/salome/gui/SMESH/input/modifying_meshes.doc b/doc/salome/gui/SMESH/input/modifying_meshes.doc
index 8aa6503ba..3490916bc 100644
--- a/doc/salome/gui/SMESH/input/modifying_meshes.doc
+++ b/doc/salome/gui/SMESH/input/modifying_meshes.doc
@@ -43,6 +43,8 @@ transformation operations, giving the possibility to:
triangles.
\subpage split_to_tetra_page "Split" volumic elements into
tetrahedra or prisms.
+
\subpage split_biquad_to_linear_page "Split bi-quadratic" elements
+ into linear ones without creation of additional nodes.
\subpage smoothing_page "Smooth" elements, reducung distortions in
them by adjusting the locations of nodes.
Create an \subpage extrusion_page "extrusion" along a vector or by
@@ -58,8 +60,8 @@ transformation operations, giving the possibility to:
\subpage cut_mesh_by_plane_page "Cut a tetrahedron mesh by a plane".
-It is possible to \ref edit_anchor "modify the mesh" of lower
-dimension before generation of mesh of higher dimension.
+\note It is possible to \ref edit_anchor "modify the mesh" of a lower
+dimension before generation of the mesh of a higher dimension.
diff --git a/doc/salome/gui/SMESH/input/pattern_mapping.doc b/doc/salome/gui/SMESH/input/pattern_mapping.doc
index 0fee46ccc..b42795e5d 100644
--- a/doc/salome/gui/SMESH/input/pattern_mapping.doc
+++ b/doc/salome/gui/SMESH/input/pattern_mapping.doc
@@ -149,7 +149,7 @@ Alternatively, it is possible to select Refine selected mesh elements
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.
+
and select two \b Nodes instead of vertices.
Additionally it is possible to:
diff --git a/doc/salome/gui/SMESH/input/quad_from_ma_algo.doc b/doc/salome/gui/SMESH/input/quad_from_ma_algo.doc
index 976783d40..6a90f376e 100644
--- a/doc/salome/gui/SMESH/input/quad_from_ma_algo.doc
+++ b/doc/salome/gui/SMESH/input/quad_from_ma_algo.doc
@@ -5,15 +5,20 @@
Medial Axis Projection algorithm can be used for meshing faces with
sinuous borders and having channel-like shape, for which is it
difficult to define 1D hypotheses so that generated quadrangles to be
-of good shape.
+of good shape. The algorithm can be also applied to faces with ring
+topology, which can be viewed as a closed 'channel'. In the latter
+case radial discretization of a ring can be specified by
+using Number of Layers or Distribution of Layers
+hypothesis.
-\image html quad_from_ma_mesh.png "A mesh of a river model"
+\image html quad_from_ma_mesh.png "A mesh of a river model to the left and of a ring-face to the right"
The algorithm assures good shape of quadrangles by constructing Medial
Axis between sinuous borders of the face and using it to
-discretize the borders.
+discretize the borders. (Shape of quadrangles can be not perfect at
+locations where opposite sides of a 'channel' are far from being parallel.)
-\image html quad_from_ma_medial_axis.png "Media Axis between two blue sinuous borders"
+\image html quad_from_ma_medial_axis.png "Medial Axis between two blue sinuous borders"
The Medial Axis is used in two ways:
@@ -22,9 +27,9 @@ The Medial Axis is used in two ways:
Axis.
If there is no sub-meshes on the sinuous borders, then a part of
the Medial Axis that can be mapped to both borders is discretized
- using a hypothesis assigned to the face or its ancestor shapes,
+ using a 1D hypothesis assigned to the face or its ancestor shapes,
and the division points are mapped from the Medial Axis to the both
- borders.
+ borders to find positions of nodes.
*/
diff --git a/doc/salome/gui/SMESH/input/quad_ijk_algo.doc b/doc/salome/gui/SMESH/input/quad_ijk_algo.doc
index dfdb2d5cb..1ba49dd83 100644
--- a/doc/salome/gui/SMESH/input/quad_ijk_algo.doc
+++ b/doc/salome/gui/SMESH/input/quad_ijk_algo.doc
@@ -3,20 +3,20 @@
\page quad_ijk_algo_page Quadrangle (Mapping) meshing algorithm
Quadrangle (Mapping) meshing algorithm is intended for creating
-all-quadrangle and quad-dominant meshes on faces with no holes and
+all-quadrangle and quad-dominant meshes on faces without holes and
bound by at least three edges.
-The algorithm can create mesh on any face but mesh quality and
-validity depends on two factors:
-- face shape (number of edges and concavity of boundary);
+The algorithm can create mesh on any face but its quality and
+validity depend on two factors:
+- face shape (number of edges and boundary concavity);
- discretization of edges.
\image html quad_mesh_invalid.png "Invalid mesh on quadrilateral concave faces"
-The algorithm uses Transfinite Interpolation technic in
+The algorithm uses Transfinite Interpolation technique in the
parametric space of a face to locate nodes inside the face.
-The algorithm treats any face as a quadrangle. If a face is bound by
+The algorithm treats any face as quadrangle. If a face is bound by
more than four edges, four most sharp vertices are considered as
corners of the quadrangle and all edges between these vertices are
treated as quadrangle sides. In the case of three edges, the vertex
@@ -26,24 +26,24 @@ quadrangle.
\image html quad_meshes.png "Algorithm generates a structured mesh on complex faces provided that edges are properly discretized"
To get an all-quadrangle mesh you have to carefully define 1D
-hypotheses on edges of a face. To get a \b structured mesh you have to assure
+hypotheses on edges of a face. To get a \b structured mesh you have to provide
equal number of segments on opposite sides of the quadrangle. If this
-condition is not respected, the algorithm by default (with no
-hypothesis) creates \b quad-dominant mesh with triangles located near a
-side with maximal number of segments. But you can get an
+condition is not respected, the algorithm by default (without a
+hypothesis) creates a \b quad-dominant mesh with triangles located near the
+side with the maximal number of segments. However, you can get an
\b all-quadrangle mesh in this case by using
\ref hypo_quad_params_anchor "Quadrangle Parameters"
hypothesis to specify how to make transition mesh between opposite
sides with different number of segments, provided that certain
-conditions are respected. In any case total number of segments must be
-even. To use \a Reduced transition method there must be equal number
+conditions are respected. In any case the total number of segments must be
+even. To use \a Reduced transition method, there must be an equal number
of segments on one pair of opposite sides.
-The following hypotheses help in creation of quadrangle meshes.
+The following hypotheses help to create quadrangle meshes.
- \ref propagation_anchor "Propagation" additional 1D hypotheses
- help to get equal number of segments on opposite sides of the
+ help to get an equal number of segments on the opposite sides of a
quadrilateral face.
- \ref a1d_algos_anchor "Composite Side Discretization" algorithm is useful
- to discretize several C1 continues edges as one quadrangle side.
+ to discretize several C1 continuous edges as one quadrangle side.
*/
diff --git a/doc/salome/gui/SMESH/input/reorient_faces.doc b/doc/salome/gui/SMESH/input/reorient_faces.doc
index f2581bb89..96072cf43 100644
--- a/doc/salome/gui/SMESH/input/reorient_faces.doc
+++ b/doc/salome/gui/SMESH/input/reorient_faces.doc
@@ -5,8 +5,8 @@
\n This operation allows fixing the orientation of a set of faces in
the following ways:
-
The desired orientation of a set of neighboring faces can be defined
- by a vector giving a desired direction of a normal of a certain face.
+
The required orientation of a set of neighboring faces can be defined
+ by a vector giving the direction of a normal to a certain face.
Since the direction of face normals in the set can be even opposite,
it is necessary to specify a \a control face, the normal to which
will be compared with the vector. This face can be either:
@@ -41,7 +41,7 @@ The orientation of a face is changed by reverting the order of its nodes.
To reorient by direction of the face normal:
Specify the coordinates of the \b Point by which the control face
- will be found. You can specify the \b Point by either picking a
+ will be found. You can specify the \b Point by picking a
node in the 3D Viewer or selecting a vertex in the Object
Browser.
Set up the \b Direction vector to be compared with the normal of the
@@ -61,7 +61,7 @@ The orientation of a face is changed by reverting the order of its nodes.
-
In the second mode it is possible to either pick the \b Face by mouse in the 3D Viewer or directly input the \b Face ID in the corresponding field.
+
In the second mode it is possible to pick the \b Face by mouse in the 3D Viewer or directly input the \b Face ID in the corresponding field.
\image html reorient_2d_face.png "The orientation of adjacent faces is chosen according to a vector. The control face is explicitly given."
@@ -81,7 +81,7 @@ The orientation of a face is changed by reverting the order of its nodes.
-\image html reorient_2d_volume.png "The orientation of faces is chosen with relation to adjacent volumes."
+\image html reorient_2d_volume.png "The orientation of faces is chosen relatively to adjacent volumes."
diff --git a/doc/salome/gui/SMESH/input/revolution.doc b/doc/salome/gui/SMESH/input/revolution.doc
index fdc4f9544..f0d4194df 100644
--- a/doc/salome/gui/SMESH/input/revolution.doc
+++ b/doc/salome/gui/SMESH/input/revolution.doc
@@ -6,7 +6,9 @@
dimension than the input ones. Boundary elements around generated
mesh of plus one dimension are additionally created. All created
elements can be automatically grouped. Revolution can be used to create
-a \ref extrusion_struct "structured mesh from scratch".
+a \ref extrusion_struct "structured mesh from scratch".
+See \ref extrusion_page page for general information on Revolution
+which can be viewed as extrusion along a circular path.
To apply revolution:
@@ -33,7 +35,7 @@ The following dialog will appear:
of following means:
Select the whole mesh, sub-mesh or group activating this
- checkbox.
+ check-box.
Choose mesh elements with the mouse in the 3D Viewer. It is
possible to select a whole area with a mouse frame.
Input the element IDs directly in Node IDs, Edge
@@ -46,14 +48,14 @@ The following dialog will appear:
Specify the \b Axis of revolution:
-
Specify the cooordinates of the start \b Point of the
+
Specify the coordinates of the start \b Point of the
axis of revolution; either directly or by picking a node
in the Viewer (selection of nodes is activated as you click
the \a Selection button).
Specify the \b Vector of the axis in either of three ways:
directly adjust vector components;
-
click \a Selection button, chose From Origin to
+
click \a Selection button, choose From Origin to
selected Point in the opened menu and pick a node
in the Viewer;
click \a Selection button, chose Normal to
@@ -66,16 +68,16 @@ The following dialog will appear:
Angle by Step - the elements are revolved by the
specified angle at each step (i.e. for Angle=30 and Number of
- Steps=2, the elements will be extruded by 30 degrees twice for a
- total of 30*2=60)
-\image html revolutionsn2.png "Example of Revolution with Angle by Step"
+ Steps=3, the elements will be extruded by 30 degrees twice for a
+ total of 30*3=90)
+\image html revolutionsn2.png "Example of Revolution with Angle by Step. Angle=30 and Number of Steps=3"
Total Angle - the elements are revolved by the
specified angle only once and the number of steps defines the
- number of iterations (i.e. for Angle=30 and Number of Steps=2,
- the elements will be revolved by 30/2=15 degrees twice for a
+ number of iterations (i.e. for Angle=30 and Number of Steps=3,
+ the elements will be revolved by 30/3=10 degrees twice for a
total of 30).
-\image html revolutionsn1.png "Example of Revolution with Total Angle"
+\image html revolutionsn1.png "Example of Revolution with Total Angle. Angle=30 and Number of Steps=3"
diff --git a/doc/salome/gui/SMESH/input/segments_around_vertex_algo.doc b/doc/salome/gui/SMESH/input/segments_around_vertex_algo.doc
index f6250d2e5..ecd2e8aa9 100644
--- a/doc/salome/gui/SMESH/input/segments_around_vertex_algo.doc
+++ b/doc/salome/gui/SMESH/input/segments_around_vertex_algo.doc
@@ -3,15 +3,20 @@
\page segments_around_vertex_algo_page Segments around Vertex
\n Segments around Vertex algorithm is considered to be a 0D meshing
-algorithm, but, of course, it doesn't mesh nodes. It allows to define
-the local size of the elements in the neighborhood of a certain
-node. If we choose an object of higher dimension, it applies to all
-its tops, i.e. corners of a box. The 0D algorithm combines with the
-algorithms of higher dimensions, but it is not necessarily required
-for their successful implementation.
+algorithm, but, of course, it doesn't mesh vertices. It allows to define
+the local size of the segments in the neighborhood of a certain
+vertex. If we assign this algorithm to a geometrical object of higher
+dimension, it applies to all its vertices.
-This algorithm allows only one hypothesis.
+Length of segments near vertex is defined by Length Near
+ Vertex hypothesis.
+This hypothesis is used by \ref a1d_algos_anchor "Wire Discretization" or
+\ref a1d_algos_anchor "Composite Side Discretization" algorithms as
+follows: a geometrical edge is discretized according to a 1D
+ hypotheses and then nodes near vertices are modified to assure the
+ segment length required by Length Near Vertex hypothesis.
\image html lengthnearvertex.png
-*/
\ No newline at end of file
+
+*/
diff --git a/doc/salome/gui/SMESH/input/selection_filter_library.doc b/doc/salome/gui/SMESH/input/selection_filter_library.doc
index 94ba01319..308706075 100644
--- a/doc/salome/gui/SMESH/input/selection_filter_library.doc
+++ b/doc/salome/gui/SMESH/input/selection_filter_library.doc
@@ -2,9 +2,11 @@
\page selection_filter_library_page Selection filter library
-\n Selection filter library is a powerful tool enabling to create
-filters to be used on meshes. You can access to it from the Main Menu
-via Tools / Selection filter library.
+\n Selection filter library allows creating and storing in files
+filters that can be later loaded and used for operations on meshes. You can
+access to it from the Main Menu via Tools / Selection filter library.
+It is also possible to save any filter by invoking the filter library
+from \a Filter dialog launched from any mesh operation.
\image html selectionfilterlibrary.png
@@ -20,21 +22,23 @@ filter. By default it is prefixed with the corresponding entity type.
When we use filters during a group creation or another operation (by
clicking Set Filter button in the corresponding dialog), the
-menu for setting filters looks as shown below.
+dialog for setting filters looks as shown below.
+
+\image html a-filteronfaces.png
The \b Add button creates a new criterion at the end of the list of
criteria. The \b Insert button creates a new criterion before the
selected criterion. The \b Remove button deletes the selected
criterion. The \b Clear button deletes all criteria.
\n Each Entity type has its specific list of criteria, however all
-filters have common syntax. For each criterion you should specify the
-Threshold Value and for numerical criteria whether we search
-for the elements that should be \b More, \b Less or \b Equal to this
+filters have common syntax. The Threshold Value should be specified
+for most criteria. For numerical criteria it is necessary to indicate if
+the found elements should be \b More, \b Less or \b Equal to this
\b Value. You can also reverse the sense of a criterion using \b Unary
operator \a Not and you should specify logical relations between
criteria using \b Binary operators \a Or and \a And.
\n Some criteria have the additional parameter of \b Tolerance.
-Switching on Insert filter in viewer checkbox limits
+Switching on Insert filter in viewer check-box limits
selection of elements in the Viewer to the current filter.
In the \b Source field you choose if the filter will be applied to
@@ -56,8 +60,6 @@ in the Library.
is no selected mesh in the Object Browser and the filter can not be
created. You have to select the mesh and the button will be enabled.
-\image html a-filteronfaces.png
-
Some criteria are applicable to all Entity types:
Belong to Geom selects entities whose all nodes lie on the
@@ -72,7 +74,7 @@ algorithm works faster, if this is any other
shape, the algorithm works slower.
Belong to Mesh Group selects entities included into the mesh group
-defined by Threshold Value.
+defined by the Threshold Value.
Range of IDs allows selection of entities with the specified
IDs.
@@ -102,7 +104,7 @@ defined by the Threshold Value. The list of available geometric
types depends on the current entity type.
Entity type allows selection of elements by their type defined
-as combination of geometry type + number of nodes.
+as a combination of geometry type and the number of nodes.
@@ -133,7 +135,7 @@ See also \ref tui_double_nodes_control "Double Nodes quality control".
The following criteria allow selecting mesh Edges:
Free Borders selects free 1D mesh elements, i.e. edges belonging to
-one face only. See also a
+one element (face or volume) only. See also a
\ref free_borders_page "Free Borders quality control".
Double edges selects 1D mesh elements basing on the same set of nodes.
@@ -177,8 +179,8 @@ The following criteria allow selecting mesh Faces:
\ref area_page "Area quality control"), which is more, less or equal (within a given
Tolerance) to the predefined Threshold Value.
-Free edges selects 2D mesh elements consisting of edges belonging to
-one element of mesh only. See also a
+Free edges selects 2D mesh elements having at least one of its
+edges not shared with other faces. See also a
\ref free_edges_page "Free Edges quality control".
Free faces selects 2D mesh elements, which belong to less than two volumes.
diff --git a/doc/salome/gui/SMESH/input/sewing_meshes.doc b/doc/salome/gui/SMESH/input/sewing_meshes.doc
index 88edc1e62..8697b36f4 100644
--- a/doc/salome/gui/SMESH/input/sewing_meshes.doc
+++ b/doc/salome/gui/SMESH/input/sewing_meshes.doc
@@ -20,19 +20,82 @@ and from its sub-menu select the \b Sewing item.
Check in the dialog box one of the radio buttons corresponding to
the type of sewing operation you would like to perform.
Fill the other fields available in the dialog box.
-
Click the \b Apply or Apply and Close button to perform the operation of sewing.
+
Click the \b Apply or Apply and Close button to perform the
+ operation of sewing.
+
\anchor free_borders_anchor
Sew free borders
-This functionality allows you to unite two free borders of a 2D mesh.
+This functionality allows you to unite free borders of a 2D mesh.
+
+There are two working modes: \a Automatic and \a Manual. In the \b
+Automatic mode, the program finds free borders coincident within a
+specified tolerance and sews them. Optionally it is possible to
+visually check and correct is necessary the found free borders before
+sewing.
+In the \b Manual mode you are to define borders to sew by picking
+three nodes of each of two borders.
\image html sewing1.png
+
Default mode is \a Automatic
-For sewing free borders you should define three points on each border:
-first, second and the last node:
+To use \b Automatic sewing:
+
+
Specify a mesh you want to sew by selecting it or any its part
+ (group or sub-mesh) in the Object Browser or in the VTK Viewer.
+
Specify the \b Tolerance within which free borders are considered
+ coincident. At the default zero \b Tolerance, the tolerance used by
+ the search algorithm is defined as one tenth of an average size of
+ elements adjacent to free borders being compared.
+
To visually check the coincident free borders found by the
+ algorithm, switch off Auto Sewing check-box. Then controls
+ to adjust groups of coincident free borders will become available in
+ the dialog.
+
+\image html sewing_auto.png
+
Controls to adjust groups of coincident free borders
+
+
\b Detect button launches the algorithm of search of coincident
+ free borders.
+
The found groups of Coincident Free Borders are shown in a
+ list, a group per a line. Each group has its own color which is used
+ to display the borders of the group in the VTK Viewer. A free border
+ within a group is designated by IDs of its first, second and last
+ nodes within parenthesis. All borders present in the list will be
+ sewn upon \b Apply.
+
\b Remove button removes selected groups from the list.
+
Select All check-box selects all groups in the list.
+
When a group is selected, its borders appear in Edit Selected
+ Group list that allows you to change this group.
+
+\image html sort.png
+Set First button moves the selected border to the
+ first position in the group, as a result other borders will be moved
+ to this border during sewing.
+
+\image html remove.png
+Remove Border button removes selected borders from the
+ group. It is active if there are more than two borders in the group.
+
+
Selection of a border in the list allows to change its first and
+ last nodes whose IDs appear in two fields below the list. \a Arrow
+ buttons near each field move the corresponding end node by
+ number of nodes defined by \b Step field.
+
+\image html swap.png
+Swap button swaps the first and last nodes of a
+ selected border.
+
+
+
+For sewing free borders manually you should switch the \b Mode to \b
+Manual and define three points on each border: first, second and the
+last node:
+
+\image html sewing_manual.png
the first node specifies beginning of the border;
the second node specifies the part of the border which should be
@@ -50,6 +113,16 @@ corresponding end nodes of two borders will be merged. Intermediate
nodes of two borders will be either merged or inserted into faces of
the opposite border.
+In practice the borders to sew often coincide and in this case it is
+difficult to specify the first and the last nodes of a border since
+they coincide with the first and the last nodes of the other
+border. To cope with this,
+\ref merging_nodes_page "merge" coincident nodes into one
+beforehand. Two figures below illustrate this approach.
+\image html sew_using_merge.png "Merge coincident nodes which are difficult to distinguish"
+
+\image html sew_after_merge.png "After merging nodes it is easy to specify border nodes"
+
The sewing algorithm is as follows:
The parameter (U) of each node within a border is computed. So
diff --git a/doc/salome/gui/SMESH/input/smoothing.doc b/doc/salome/gui/SMESH/input/smoothing.doc
index eb74611cf..801b1c9d8 100644
--- a/doc/salome/gui/SMESH/input/smoothing.doc
+++ b/doc/salome/gui/SMESH/input/smoothing.doc
@@ -3,8 +3,11 @@
\page smoothing_page Smoothing
\n Smoothing is used to improve quality of 2D mesh by adjusting the
-locations of element corners (nodes). \note Depending on smoothing
-method and mesh geometry smoothing can decrease quality of elements.
+locations of element corners (nodes).
+
+\note Depending on the chosen method and mesh geometry
+the smoothing can actually decrease the quality of elements and even
+make some elements inverted.
To apply smoothing to the elements of your mesh:
diff --git a/doc/salome/gui/SMESH/input/split_biquad_to_linear.doc b/doc/salome/gui/SMESH/input/split_biquad_to_linear.doc
new file mode 100644
index 000000000..ea4ac7228
--- /dev/null
+++ b/doc/salome/gui/SMESH/input/split_biquad_to_linear.doc
@@ -0,0 +1,37 @@
+/*!
+
+\page split_biquad_to_linear_page Split bi-quadratic into linear
+
+\n This functionality allows to split bi-quadratic elements into
+linear ones without creation of additional nodes.
+
+So that
+- bi-quadratic triangle will be split into 3 linear quadrangles;
+- bi-quadratic quadrangle will be split into 4 linear quadrangles;
+- tri-quadratic hexahedron will be split into 8 linear hexahedra;
+- quadratic segments adjacent to the split bi-quadratic element will
+ be split into 2 liner segments.
+
+\image html split_biquad_to_linear_mesh.png "Mesh before and after splitting"
+
+To split bi-quadratic elements into linear:
+
+
From the \b Modification menu choose the Split bi-quadratic into linear item or
+click "Split bi-quadratic into linear" button in the toolbar.
+
+\image html split_biquad_to_linear_icon.png
+
"Split bi-quadratic into linear" button
+
+The following dialog box shall appear:
+
+\image html split_biquad_to_linear_dlg.png
+
+
+
Select a mesh, groups or sub-meshes in the Object Browser or in the
+ Viewer.
+
Click the \b Apply or Apply and Close button.
+
+
+ See Also a sample TUI Script of a \ref tui_split_biquad "Split bi-quadratic into linear" operation.
+
+*/
diff --git a/doc/salome/gui/SMESH/input/split_to_tetra.doc b/doc/salome/gui/SMESH/input/split_to_tetra.doc
index fb5c4e165..b6ee36e93 100644
--- a/doc/salome/gui/SMESH/input/split_to_tetra.doc
+++ b/doc/salome/gui/SMESH/input/split_to_tetra.doc
@@ -7,7 +7,7 @@ tetrahedra or hexahedra into prisms. 2D mesh is modified accordingly.
To split volumes:
-
Display a mesh, a sub-mesh or a group in the 3D viewer.
+
Select a mesh, a sub-mesh or a group.
In the \b Modification menu select the Split Volumes item or
click "Split Volumes" button in the toolbar.
diff --git a/doc/salome/gui/SMESH/input/symmetry.doc b/doc/salome/gui/SMESH/input/symmetry.doc
index 9c0b43263..4641ffe31 100644
--- a/doc/salome/gui/SMESH/input/symmetry.doc
+++ b/doc/salome/gui/SMESH/input/symmetry.doc
@@ -64,21 +64,21 @@ possible to select a whole area with a mouse frame; or
specify the conditions of symmetry operation:
-
activate Move elements radio button to change location of
+
activate Move elements radio button to change the location of
the selected elements within the current mesh;
activate Copy elements radio button to duplicate the
selected elements at the new location within the current mesh;
-
activate Create as new mesh radio button to create new
+
activate Create as new mesh radio button to create a new
element in a new mesh; the new mesh appears in the Object Browser
- with the default name MeshName_mirrored (it is possible to change
+ with the default name \a MeshName_mirrored (it is possible to change
this name in the adjacent box);
-
activate Copy groups checkbox to put new mesh enities
- into new groups if source entities belongs to some groups. New
+
activate Copy groups check-box to put new mesh entities
+ into new groups if source entities belong to some groups. New
groups are named by pattern "_mirrored".
-
activate Preview checkbox to show the result of
+
activate Preview check-box to show the result of
transformation in the viewer;
click \b Apply or Apply and Close button to confirm the
operation.
+\tui_script{split_biquad.py}
+
*/
diff --git a/doc/salome/gui/SMESH/input/uniting_set_of_triangles.doc b/doc/salome/gui/SMESH/input/uniting_set_of_triangles.doc
index 6397bd401..b9704a41a 100644
--- a/doc/salome/gui/SMESH/input/uniting_set_of_triangles.doc
+++ b/doc/salome/gui/SMESH/input/uniting_set_of_triangles.doc
@@ -2,7 +2,7 @@
\page uniting_set_of_triangles_page Uniting a set of triangles
-\n In MESH you can union many neighboring triangles (cells) into
+\n It is possible to unite many neighboring triangles into
quadrangles by deletion of the common edge.
To union several triangles:
@@ -10,7 +10,7 @@ quadrangles by deletion of the common edge.
Select a mesh (and display it in the 3D Viewer if you are going to
pick elements by mouse).
In the \b Modification menu select the Union of triangles
- item or click "Union of triangles" button in the toolbar.
+ item or click "Union of triangles" button in the tool-bar.
\image html image80.png
"Union of triangles" button
diff --git a/doc/salome/gui/SMESH/input/uniting_two_triangles.doc b/doc/salome/gui/SMESH/input/uniting_two_triangles.doc
index 39a61bbb2..f965a015f 100644
--- a/doc/salome/gui/SMESH/input/uniting_two_triangles.doc
+++ b/doc/salome/gui/SMESH/input/uniting_two_triangles.doc
@@ -2,14 +2,14 @@
\page uniting_two_triangles_page Uniting two triangles
-\n In MESH you can union two neighboring triangles (cells) by deletion
+\n In MESH you can union two neighboring triangles by deletion
of the common edge.
To unite two triangles:
From the \b Modification menu choose the Union of two
triangles item or click "Union of two triangles" button
-in the toolbar.
+in the tool-bar.
\image html image71.png
"Union of two triangles" button
@@ -20,7 +20,7 @@ The following dialog box shall appear:
Enter IDs of nodes forming the required edge in the \b Edge field
- (the node IDs must be separated by a dash) or select this edge in
+ (a couple of node IDs separated by a dash) or select this edge in
the 3D viewer.
Click the \b Apply or Apply and Close button.
diff --git a/doc/salome/gui/SMESH/input/viewing_meshes_overview.doc b/doc/salome/gui/SMESH/input/viewing_meshes_overview.doc
index 248685579..2472c24fa 100644
--- a/doc/salome/gui/SMESH/input/viewing_meshes_overview.doc
+++ b/doc/salome/gui/SMESH/input/viewing_meshes_overview.doc
@@ -26,8 +26,11 @@ information about the mesh.
\subpage find_element_by_point_page "Find Element by Point" -
allows to find all mesh elements, to which belongs a point with the
given coordinates.
-
Auto Color - switch on / off auto-assigning colors for the groups.
-
\subpage numbering_page "Numbering" - allows to display the ID
+
Auto Color - switch on / off auto-assigning colors for the
+ groups. If switched on, a default color of a new group in
+ \ref creating_groups_page "Create Group" dialog is chosen
+ randomly.
+
\subpage numbering_page "Numbering" - allows to display the ID
numbers of all meshing elements or nodes composing your mesh in the
viewer.