23427: [CEA 2073] No hypothesis "Viscous Layers" with Netgen 1D-2D-3D

[modules/smesh.git] / doc / salome / gui / SMESH / input / constructing_meshes.doc

diff --git a/doc/salome/gui/SMESH/input/constructing_meshes.doc b/doc/salome/gui/SMESH/input/constructing_meshes.doc
index 2ec8a49878fa121577843d32121c0b28324a3421..2481807fd0888fdda36ee1c0c880f28b4a8cb8c0 100644 (file)
--- a/doc/salome/gui/SMESH/input/constructing_meshes.doc
+++ b/doc/salome/gui/SMESH/input/constructing_meshes.doc
@@ -10,13 +10,16 @@ To create a mesh on geometry, it is necessary to create a mesh object by choosin
     taken into account by the chosen meshing algorithms.
 
 Then you can launch mesh generation by invoking \ref compute_anchor "Compute" command.
     taken into account by the chosen meshing algorithms.
 
 Then you can launch mesh generation by invoking \ref compute_anchor "Compute" command.

+The generated mesh will be automatically shown in the Viewer. You can
+switch off automatic visualization or limit mesh size until which it is
+automatically shown in \ref mesh_preferences_page (<em>Automatic update</em> entry).

 
 \note Sometimes \a hypotheses term is used to refer to both algorithms
 and hypotheses.
 
 Mesh generation on the geometry is performed in the bottom-up
 flow: nodes on vertices are created first, then edges are divided into
 
 \note Sometimes \a hypotheses term is used to refer to both algorithms
 and hypotheses.
 
 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 node of segments are then
+segments using nodes on vertices; the nodes 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.
 
 used to mesh faces; then the nodes of faces are used to mesh
 solids. This automatically assures the conformity of the mesh.
 


@@ -313,24 +316,24 @@ There is an example of sub-mesh order modifications taking a Mesh created on a B
 shape. The main Mesh object:
 <ul>
   <li><i>1D</i> <b>Wire discretisation</b> with <b>Number of Segments</b>=20</li>
 shape. The main Mesh object:
 <ul>
   <li><i>1D</i> <b>Wire discretisation</b> with <b>Number of Segments</b>=20</li>

-  <li><i>2D</i> <b>Triangle (Mefisto)</b> with Hypothesis<b>Max Element Area</b>
+  <li><i>2D</i> <b>Triangle: Mefisto</b> with Hypothesis<b>Max Element Area</b>

   </li>
 </ul>
 The first sub-mesh <b>Submesh_1</b> created on <b>Face_1</b> is:
 <ul>
   <li><i>1D</i> <b>Wire discretisation</b> with <b>Number of Segments</b>=4</li>
   </li>
 </ul>
 The first sub-mesh <b>Submesh_1</b> created on <b>Face_1</b> is:
 <ul>
   <li><i>1D</i> <b>Wire discretisation</b> with <b>Number of Segments</b>=4</li>

-  <li><i>2D</i> <b>Triangle (Mefisto)</b> with Hypothesis <b>MaxElementArea</b>=1200</li>
+  <li><i>2D</i> <b>Triangle: Mefisto</b> with Hypothesis <b>MaxElementArea</b>=1200</li>

 </ul>
 The second sub-mesh <b>Submesh_2</b> created on <b>Face_2</b> is:
 <ul>
   <li><i>1D</i> <b>Wire discretisation</b> with <b>Number of Segments</b>=8</li>
 </ul>
 The second sub-mesh <b>Submesh_2</b> created on <b>Face_2</b> is:
 <ul>
   <li><i>1D</i> <b>Wire discretisation</b> with <b>Number of Segments</b>=8</li>

-  <li><i>2D</i> <b>Triangle (Mefisto)</b> with Hypothesis <b>MaxElementArea</b>=1200</li>
+  <li><i>2D</i> <b>Triangle: Mefisto</b> with Hypothesis <b>MaxElementArea</b>=1200</li>

 </ul>
 
 And the last sub-mesh <b>Submesh_3</b> created on <b>Face_3</b> is:
 <ul>
   <li><i>1D</i> <b>Wire discretisation</b> with <b>Number of Segments</b>=12</li>
 </ul>
 
 And the last sub-mesh <b>Submesh_3</b> created on <b>Face_3</b> is:
 <ul>
   <li><i>1D</i> <b>Wire discretisation</b> with <b>Number of Segments</b>=12</li>

-  <li><i>2D</i> <b>Triangle (Mefisto)</b> with Hypothesis <b>MaxElementArea</b>=1200</li>
+  <li><i>2D</i> <b>Triangle: Mefisto</b> with Hypothesis <b>MaxElementArea</b>=1200</li>

 </ul>
 
 The sub-meshes become concurrent if they share sub-shapes that can be
 </ul>
 
 The sub-meshes become concurrent if they share sub-shapes that can be


@@ -401,6 +404,7 @@ 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). 
 
 with the same contents. (To fully re-compute the mesh, invoke 
 \ref clear_mesh_anchor "Clear Mesh Data" command before). 
 

+\anchor meshing_result_anchor

 If the mesh computation has been a success, the box shows information
 on the 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.
 


@@ -445,7 +449,7 @@ to facilitate their analysis.
 </center>
 
 \note Mesh Computation Information box does not appear if you set
 </center>
 
 \note Mesh Computation Information box does not appear if you set

-"Mesh computation/Show a computation result notification" preference 
+\ref show_comp_result_pref "Mesh computation/Show a computation result notification" preference 

 to the "Never" value. This option gives the possibility to control mesh
 computation reporting. There are the following possibilities: always
 show the information box, show only if an error occurs or never. 
 to the "Never" value. This option gives the possibility to control mesh
 computation reporting. There are the following possibilities: always
 show the information box, show only if an error occurs or never.