X-Git-Url: http://git.salome-platform.org/gitweb/?p=modules%2Fsmesh.git;a=blobdiff_plain;f=doc%2Fsalome%2Fgui%2FSMESH%2Finput%2Fprism_3d_algo.doc;h=5f98399c76ce6601f0b0b78cd5ff38b6b0738057;hp=71ba2a9125d6d26b4fbd0807a2597e8f8ecb2b38;hb=0f9ed6f02c1e57730c871370ee2ec04a1f417593;hpb=9b27b015d90bd12f9c8c7ea804bf69815e85491f;ds=sidebyside diff --git a/doc/salome/gui/SMESH/input/prism_3d_algo.doc b/doc/salome/gui/SMESH/input/prism_3d_algo.doc index 71ba2a912..5f98399c7 100644 --- a/doc/salome/gui/SMESH/input/prism_3d_algo.doc +++ b/doc/salome/gui/SMESH/input/prism_3d_algo.doc @@ -49,21 +49,35 @@ The \b Local algorithms and hypotheses to be chosen at \ref constructing_submeshes_page "Construction of sub-meshes" are:
• 1D and 2D algorithms and hypotheses that will be applied for - meshing the top and the base prism faces. These faces can be meshed + meshing the top and the base prism + \ref submesh_shape_section "faces". These faces can be meshed with any type of 2D elements: quadrangles, triangles, polygons or - their mix. It is enough to define a sub-mesh on either the top or the base - face. In the sample picture above, "NETGEN_1D2D" algorithm meshes - "bottom disk" face with triangles. (1D algorithm is not - assigned as "NETGEN_1D2D" does not require divided edges to create a 2D mesh.) + their mix. It is enough to define a sub-mesh on either the top or + the base face. In the sample picture above, "NETGEN_1D2D" + algorithm meshes "bottom disk" face with triangles. (1D algorithm + is not assigned as "NETGEN_1D2D" does not require divided edges to + create a 2D mesh.)
• -
• Optionally you can define a 1D sub-mesh on some vertical edges - of stacked prisms, which will override the global 1D hypothesis mentioned - above. In the Prism stacks picture, the - vertical division is not equidistant on the whole length because - a "Number Of Segments" hypothesis with Scale Factor=3 is assigned to - the highlighted edge. +
• Optionally you can define a 1D sub-mesh on some vertical + \ref submesh_shape_section "edges" of stacked prisms, which will + override the global 1D hypothesis mentioned above. In the Prism + stacks picture, the vertical division is not equidistant on + the whole length because a "Number Of Segments" hypothesis with + Scale Factor=3 is assigned to the highlighted edge.
+If 3D extrusion algorithm is assigned to a sub-mesh in a mesh +with multiple sub-meshes, the described above approach may not work as +expected. For example the bottom face may be meshed by other algorithm +before 3D extrusion have a chance to project a mesh from the +base face. This thing can happen with vertical edges as well. All +these can lead to either a meshing failure or to an incorrect meshing. + +In such a case, it's necessary to explicitly define algorithms +that 3D extrusion implicitly applies in a simple case: +- assign \ref projection_1D2D algorithm to the top face and +- assign a 1D algorithm to a group of all vertical edges. + \image html image157.gif "Prism with 3D extrusion meshing. Vertical division is different on neighbor edges because several local 1D hypotheses are assigned." \sa a sample TUI Script of