X-Git-Url: http://git.salome-platform.org/gitweb/?a=blobdiff_plain;f=doc%2Fsalome%2Fgui%2FSMESH%2Finput%2Fconstructing_meshes.rst;h=05c4c0d39d08b42f9f1fb22f033f8577bc8ca75b;hb=d245f797f1b69aca678fa372391275d7042faa10;hp=d26102f43049ac47f650011b1a9ad51a4ed9c41d;hpb=8d297d6698f361d4f2dde723050bcfbaea050920;p=modules%2Fsmesh.git diff --git a/doc/salome/gui/SMESH/input/constructing_meshes.rst b/doc/salome/gui/SMESH/input/constructing_meshes.rst index d26102f43..05c4c0d39 100644 --- a/doc/salome/gui/SMESH/input/constructing_meshes.rst +++ b/doc/salome/gui/SMESH/input/constructing_meshes.rst @@ -160,7 +160,6 @@ To construct a mesh: List of sets of hypotheses. Tag *[custom]* is automatically added to the sets defined by the user. .. note:: - * *"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. @@ -217,7 +216,11 @@ These elements can be kept in the mesh. Changing sub-mesh priority ########################## -If the mesh contains concurrent :ref:`sub-meshes `, it is possible to change the priority of their computation, i.e. to change the priority of applying algorithms to the shared sub-shapes of the Mesh shape. +If the mesh contains concurrent :ref:`sub-meshes `, it is possible to change their :ref:`default priority `. Changing priority works in two ways: + +* For sub-meshes with assigned algorithms of same dimension generating mesh of *several dimensions*, it sets the order in which the sub-meshes are computed. +* For the rest sub-meshes, it sets the order in which the sub-meshes are checked when looking for meshing parameters to apply to a sub-shape. Examples below present this way. To impose the order in which sub-meshes with uni-dimensional algorithms are computed, invoke **Compute Sub-mesh** command on sub-meshes in a desired order. + *To change sub-mesh priority:*