From: rnv <rnv@opencascade.com>
Date: Tue, 27 Mar 2012 12:52:59 +0000 (+0000)
Subject: 0021308: EDF 1923 SMESH: Remove hard-coded dependency of the external mesh plugins... 
X-Git-Tag: V6_5_0a1~14
X-Git-Url: http://git.salome-platform.org/gitweb/?p=modules%2Fsmesh.git;a=commitdiff_plain;h=d44f22428b2b8255f0481f9ff5c1c459b7d395b7;hp=da4fe2a060153eadccd50faeec22f80b0613fd80

0021308: EDF 1923 SMESH: Remove hard-coded dependency of the external mesh plugins from the SMESH module: Update documentation.
---

diff --git a/doc/salome/gui/SMESH/images/blsurf_attractors.png b/doc/salome/gui/SMESH/images/blsurf_attractors.png
deleted file mode 100644
index a0e0276c3..000000000
Binary files a/doc/salome/gui/SMESH/images/blsurf_attractors.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/blsurf_attractors2.png b/doc/salome/gui/SMESH/images/blsurf_attractors2.png
deleted file mode 100644
index 09dc1290d..000000000
Binary files a/doc/salome/gui/SMESH/images/blsurf_attractors2.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/blsurf_const_size_near_shape.png b/doc/salome/gui/SMESH/images/blsurf_const_size_near_shape.png
deleted file mode 100644
index 9e5ad6c0c..000000000
Binary files a/doc/salome/gui/SMESH/images/blsurf_const_size_near_shape.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/blsurf_const_size_near_shape2.png b/doc/salome/gui/SMESH/images/blsurf_const_size_near_shape2.png
deleted file mode 100644
index 68620f39e..000000000
Binary files a/doc/salome/gui/SMESH/images/blsurf_const_size_near_shape2.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/blsurf_parameters.png b/doc/salome/gui/SMESH/images/blsurf_parameters.png
deleted file mode 100644
index 4da8a9e3a..000000000
Binary files a/doc/salome/gui/SMESH/images/blsurf_parameters.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/blsurf_parameters_advanced.png b/doc/salome/gui/SMESH/images/blsurf_parameters_advanced.png
deleted file mode 100644
index 4fadb6b48..000000000
Binary files a/doc/salome/gui/SMESH/images/blsurf_parameters_advanced.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/blsurf_parameters_enforced_vertices.png b/doc/salome/gui/SMESH/images/blsurf_parameters_enforced_vertices.png
deleted file mode 100644
index b9a665afc..000000000
Binary files a/doc/salome/gui/SMESH/images/blsurf_parameters_enforced_vertices.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/blsurf_parameters_sizemap.png b/doc/salome/gui/SMESH/images/blsurf_parameters_sizemap.png
deleted file mode 100644
index 2b3819759..000000000
Binary files a/doc/salome/gui/SMESH/images/blsurf_parameters_sizemap.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/blsurf_parameters_sizemap1.png b/doc/salome/gui/SMESH/images/blsurf_parameters_sizemap1.png
deleted file mode 100644
index 4ae88c895..000000000
Binary files a/doc/salome/gui/SMESH/images/blsurf_parameters_sizemap1.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/blsurf_parameters_sizemap2.png b/doc/salome/gui/SMESH/images/blsurf_parameters_sizemap2.png
deleted file mode 100644
index e5e000d32..000000000
Binary files a/doc/salome/gui/SMESH/images/blsurf_parameters_sizemap2.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/ghs3d_enforced_meshes.png b/doc/salome/gui/SMESH/images/ghs3d_enforced_meshes.png
deleted file mode 100644
index 9ddc0127d..000000000
Binary files a/doc/salome/gui/SMESH/images/ghs3d_enforced_meshes.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/ghs3d_enforced_vertices.png b/doc/salome/gui/SMESH/images/ghs3d_enforced_vertices.png
deleted file mode 100644
index d3a4bbcfa..000000000
Binary files a/doc/salome/gui/SMESH/images/ghs3d_enforced_vertices.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/ghs3d_parameters_advanced.png b/doc/salome/gui/SMESH/images/ghs3d_parameters_advanced.png
deleted file mode 100644
index c254112a2..000000000
Binary files a/doc/salome/gui/SMESH/images/ghs3d_parameters_advanced.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/ghs3d_parameters_basic.png b/doc/salome/gui/SMESH/images/ghs3d_parameters_basic.png
deleted file mode 100644
index 9519c1461..000000000
Binary files a/doc/salome/gui/SMESH/images/ghs3d_parameters_basic.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/ghs3d_screenshot.png b/doc/salome/gui/SMESH/images/ghs3d_screenshot.png
deleted file mode 100644
index a9e7b972b..000000000
Binary files a/doc/salome/gui/SMESH/images/ghs3d_screenshot.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf1.png b/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf1.png
deleted file mode 100644
index 8923f007a..000000000
Binary files a/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf1.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf2.png b/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf2.png
deleted file mode 100644
index 5daf8a269..000000000
Binary files a/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf2.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf3.png b/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf3.png
deleted file mode 100644
index f6911ce0b..000000000
Binary files a/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf3.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf4.png b/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf4.png
deleted file mode 100644
index 46f12d83c..000000000
Binary files a/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf4.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf5.png b/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf5.png
deleted file mode 100644
index 531b8126d..000000000
Binary files a/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf5.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf6.png b/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf6.png
deleted file mode 100644
index 003f89f14..000000000
Binary files a/doc/salome/gui/SMESH/images/ghs3d_screenshot_enf6.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/hexotic_parameters.png b/doc/salome/gui/SMESH/images/hexotic_parameters.png
deleted file mode 100644
index 40abfedd3..000000000
Binary files a/doc/salome/gui/SMESH/images/hexotic_parameters.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/mesh_order_123_res.png b/doc/salome/gui/SMESH/images/mesh_order_123_res.png
index 7b7588c63..02208a052 100644
Binary files a/doc/salome/gui/SMESH/images/mesh_order_123_res.png and b/doc/salome/gui/SMESH/images/mesh_order_123_res.png differ
diff --git a/doc/salome/gui/SMESH/images/mesh_order_213_res.png b/doc/salome/gui/SMESH/images/mesh_order_213_res.png
index ca36759a9..8706fb45c 100644
Binary files a/doc/salome/gui/SMESH/images/mesh_order_213_res.png and b/doc/salome/gui/SMESH/images/mesh_order_213_res.png differ
diff --git a/doc/salome/gui/SMESH/images/mesh_order_321_res.png b/doc/salome/gui/SMESH/images/mesh_order_321_res.png
index 051447093..7a5f0172e 100644
Binary files a/doc/salome/gui/SMESH/images/mesh_order_321_res.png and b/doc/salome/gui/SMESH/images/mesh_order_321_res.png differ
diff --git a/doc/salome/gui/SMESH/images/netgen2d3d.png b/doc/salome/gui/SMESH/images/netgen2d3d.png
deleted file mode 100644
index 97b95486e..000000000
Binary files a/doc/salome/gui/SMESH/images/netgen2d3d.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/netgen2d3d_only.png b/doc/salome/gui/SMESH/images/netgen2d3d_only.png
deleted file mode 100644
index ece6fd1e8..000000000
Binary files a/doc/salome/gui/SMESH/images/netgen2d3d_only.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/netgen2d3d_simple.png b/doc/salome/gui/SMESH/images/netgen2d3d_simple.png
deleted file mode 100644
index f8d116610..000000000
Binary files a/doc/salome/gui/SMESH/images/netgen2d3d_simple.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/images/netgen3d_local_size.png b/doc/salome/gui/SMESH/images/netgen3d_local_size.png
deleted file mode 100644
index f7bcd18b9..000000000
Binary files a/doc/salome/gui/SMESH/images/netgen3d_local_size.png and /dev/null differ
diff --git a/doc/salome/gui/SMESH/input/about_hypo.doc b/doc/salome/gui/SMESH/input/about_hypo.doc
index f655e1a69..b17225d56 100644
--- a/doc/salome/gui/SMESH/input/about_hypo.doc
+++ b/doc/salome/gui/SMESH/input/about_hypo.doc
@@ -36,16 +36,6 @@ them, you operate numerical values):
 </ul>
 </ul>
 
-Some hypotheses are strictly combined with plug-in
-meshers and thus, work only with definite algorithms.
-<ul>
-<li>\subpage netgen_2d_3d_hypo_page</li> - work with NetGen algorithm.
-<li>\subpage ghs3d_hypo_page</li> - works with GHS3D algorithm.
-<li>\subpage ghs3dprl_hypo_page</li> - works with GHS3DPRL (tepal) algorithm.
-<li>\subpage blsurf_hypo_page</li> - works with BLSURF algorithm.
-<li>\subpage hexotic_hypo_page</li> - works with Hexotic algorithm.
-</ul>
-
 There also exist  
 \subpage additional_hypo_page "Additional Hypotheses" used together
 with other hypotheses:
diff --git a/doc/salome/gui/SMESH/input/additional_hypo.doc b/doc/salome/gui/SMESH/input/additional_hypo.doc
index 0ad738230..f0c623b1c 100644
--- a/doc/salome/gui/SMESH/input/additional_hypo.doc
+++ b/doc/salome/gui/SMESH/input/additional_hypo.doc
@@ -34,8 +34,8 @@ has been locally defined on the opposite edge.
 
 <h2>Quadrangle Preference</h2>
 
-This additional hypothesis can be used together with Netgen 2D algorithm.
-It allows Netgen 2D to build quadrangular meshes.
+This additional hypothesis can be used together with 2D triangulation algorithms.
+It allows 2D triangulation algorithms to build quadrangular meshes.
 
 <br>
 This hypothesis has one restriction on its work: the total quantity of
@@ -45,7 +45,7 @@ segments on all four sides of the face must be even (divisible by 2).
 <h2>Viscous Layers</h2>
 
 <b>Viscous Layers</b> additional hypothesis can be used together with
-several 3D algorithms: NETGEN 3D, GHS3D and Hexahedron(i,j,k). This
+3D algorithms, Hexahedron(i,j,k) for example. This
 hypothesis allows creation of layers of highly stretched prisms near
 mesh boundary, which is beneficial for high quality viscous
 computations. The prisms constructed on the quadrangular mesh faces are
diff --git a/doc/salome/gui/SMESH/input/basic_meshing_algos.doc b/doc/salome/gui/SMESH/input/basic_meshing_algos.doc
index 828561875..9532e2a91 100644
--- a/doc/salome/gui/SMESH/input/basic_meshing_algos.doc
+++ b/doc/salome/gui/SMESH/input/basic_meshing_algos.doc
@@ -21,7 +21,7 @@ shape of a mesh.</li>
 <li>For meshing of 2D entities (<b>faces</b>):</li>
 
 <ul>
-<li>Triangle meshing algorithms (Mefisto, Netgen 1D-2D and BLSUFR ) - Faces
+<li>Triangle meshing algorithms (Mefisto) - Faces
 are split into triangular elements.</li>
 <li>Quadrangle meshing algorithm (Mapping) - quadrilateral Faces are split into
 quadrangular elements.</li>
@@ -36,8 +36,6 @@ quadrangular elements.</li>
 <ul>
 <li>Hexahedron meshing algorithm (i,j,k) - 6-sided Volumes are split into
 hexahedral (cubic) elements.</li>
-<li>Tetrahedron (Netgen and GHS3D) meshing algorithms - Volumes are split into
-tetrahedral (pyramidal) elements.</li>
 <li>\subpage cartesian_algo_page</li>
 internal parts of Volumes are split into hexahedral elements forming a
 Cartesian grid; polyhedra and other types of elements are generated
@@ -53,14 +51,8 @@ Some of 3D meshing algorithms also can generate 3D meshes from 2D meshes, workin
 geometrical objects. Such algorithms are
 <ul>
 <li>Hexahedron meshing algorithm (i,j,k),</li>
-<li>Tetrahedron (Netgen and GHS3D) meshing algorithms,</li>
-<li>Hexotic.</li>
 </ul>
 
-
-\note BLSURF and GHS3D are commercial meshers and require a
-license to be used within the Mesh module.
-
 There is also a number of more specific algorithms:
 <ul>
 <li>\subpage projection_algos_page "for meshing by projection of another mesh"</li>
diff --git a/doc/salome/gui/SMESH/input/blsurf_hypo.doc b/doc/salome/gui/SMESH/input/blsurf_hypo.doc
deleted file mode 100644
index 7e7a4f45a..000000000
--- a/doc/salome/gui/SMESH/input/blsurf_hypo.doc
+++ /dev/null
@@ -1,448 +0,0 @@
-/*!
-
-\page blsurf_hypo_page BLSURF Parameters hypothesis
-
-\anchor blsurf_top
-\n BLSURF Parameters hypothesis works only with <b>BLSURF</b> 2d
-algorithm. This algorithm is a commercial software.
-\n To get a licence, visit http://www.distene.com/corp/eval-distene.html
-
-<ol>
-<li>\ref blsurf_general_parameters "General parameters"</li>
-<li>\ref blsurf_advanced_parameters "Advanced parameters"</li>
-<li>\ref blsurf_local_size "Local size"</li>
-<ol>
-<li type="a">\ref blsurf_sizemap_computation "Computation of the physical size"</li>
-<li type="a">\ref blsurf_attractor "Advanced maps"</li>
-<li type="a">\ref blsurf_attractor_computation "Computation of attractors"</li>
-</ol>
-<li>\ref blsurf_enforced_elements "Enforced vertices"</li>
-<li>\ref blsurf_limitations "Limitations"</li>
-</ol>
-
-\anchor blsurf_general_parameters
-<h1>General parameters</h1>
-
-\image html blsurf_parameters.png
-
-<ul>
-<li><b>Name</b> - allows defining the name of the hypothesis (BLSURF
-Parameters_n by default).</li>
-
-<li><b>Physical Mesh</b> - can be set to None, Custom or Size Map
- <ul>
-  <li>if set to "Custom", allows user input in the
-in <b>User size</b>, <b>Max Physical Size</b> and <b>Min Physical
-Size</b> fields.</li>
-  <li>if set to "Size Map", behaves like "Custom" mode and takes into account the custom elements sizes given in the Size Map tab.</li>
-</ul>
-</li>
-
-<li><b>User size</b> - defines the size of the generated mesh elements. </li>
-
-<li><b>Max Physical Size</b> - defines the upper limit of mesh element size. </li>
-
-<li><b>Min Physical Size</b> - defines the lower limit of mesh element size. </li>
-
-<li><b>Geometrical mesh</b> - if set to "Custom", allows user input in
- <b>Angle Mesh S</b>, <b>Angle Mesh C</b> and
-<b>Gradation</b> fields. These fields control
-computation of the element size, so called <i>geometrical size</i>, conform to
-the surface geometry considering local curvatures. \n
-If both the <b>User size</b> and the <i>geometrical size</i> are defined, the
- eventual element size correspond to the least of the two. </li>
-
-<li><b>Angle Mesh S</b> - maximum angle between the mesh face and the
-tangent to the geometrical surface at each mesh node, in degrees. </li>
-
-<li><b>Angle Mesh C</b> - maximum angle between the mesh edge and the
-tangent to the geometrical curve at each mesh node, in degrees. </li>
-
-<li><b>Max Geometrical Size</b> - defines the upper limit of the <i>geometrical size</i>.</li>
-
-<li><b>Min Geometrical Size</b> - defines the lower limit of the <i>geometrical size</i>.</li>
-
-<li><b>Gradation</b> - maximum ratio between the lengths of
-two adjacent edges. </li>
-
-<li><b>Allow Quadrangles</b> - if checked, allows the creation of quadrilateral elements.</li>
-
-<li><b>Patch independent</b> - if checked, geometrical
-edges are not respected and all geometrical faces are meshed as one
-hyper-face.</li>
-</ul>
-
-\ref blsurf_top "Back to top"
-
-\anchor blsurf_advanced_parameters
-<h1>Advanced parameters</h1>
-
-The notion of <i>diag</i> used in the descriptions means the diagonal of the bounding box of the 
-geometrical object to mesh.
-
-\image html blsurf_parameters_advanced.png
-
-<li><b>Verbosity level</b> - Defines the percentage of "verbosity" of
-BLSURF [0-100].</li>
-
-<li><b>Topology</b> - allows creation of a conform mesh on a shell of
-not sewed faces. 
-<ul>
-  <li>"From CAD" means that mesh conformity is assured by conformity
-  of a shape.</li>
-  <li>"Pre-process" and "Pre-process++" allow the BLSURF software to
-  pre-process the geometrical model to eventually produce a conform
-  mesh. </li>
-  <li>"PreCAD" is an auxiliary CAD pre-processing module which has 
-  two main goals:
-  <ul>
-    <li> Complete missing or inadequate CAD descriptions.</li>
-    <li> Perform topology reconstruction and specific geometry 
-    enhancement for mesh generation.</li>
-  </ul>
-  This module requires a specific licence.
-  \n
-  The following PreCAD options are the most significant and important ones:
-  <ul>
-  <li><b>Merge Edges</b> - allows PreCAD to optimize the geometry by merging some
-  edges. This option is 0 by default.</li>
-  <li><b>Remove nano edges</b> - allows PreCAD to optimize the geometry by removing 
-  the nano edges whenever possible. This option is 0 by default.</li>
-  <li><b>Nano edge length</b> - gives the length below which an edge is considered as nano 
-  for the topology processing. See also the \b remove_nano_edges option. If unset, PreCAD
-  default value is \f$\mathrm{diag} \times 10^{-5}\f$.</li>
-  <li><b>Discard input topology</b> - computes the CAD topology from scratch, 
-  without considering the toplogical information contained in the original CAD
-  (Useful for iges files). This option is 0 by default.</li>
-  </ul>
-  </li>
-</ul>
-
-<li><b>ExportGMF</b> - saves the computed mesh into a GMF file (.mesh or .meshb).</li>
-
-<li><b>Add option</b> - provides the choice of multiple PreCAD and BLSURF 
-advanced options, which appear, if selected, in a table where it is 
-possible to input the value of the option and to edit it later.</li>
-
-<li><b>Clear option</b> - removes the option selected in the table.</li>
-
-</ul>
-
-\n
-The following BLSURF options are commonly usable.
-
-<ul>
-<li>\b topo_eps1 (real) - is the tolerance level inside a CAD
-patch. By default is equal to \f$\mathrm{diag} \times 10^{-4}\f$. This tolerance is used to
-identify nodes to merge within one geometrical face when \b Topology
-option is to pre-process.</li>
-
-<li>\b topo_eps2 (real) - is the tolerance level between two CAD
-patches. By default is equal to \f$\mathrm{diag} \times 10^{-4}\f$. This tolerance is used to
-identify nodes to merge over different geometrical faces when
-\b Topology option is to pre-process.</li>
-
-<li>\b LSS (real) - is an abbreviation for "length of sub-segment". It is
-a maximal allowed length of a mesh edge. Default is \f$0.5\f$.</li>
-
-<li>\b frontal (integer)
-<ul>
-<li> 1 - the mesh generator inserts points with an advancing front method.</li>
-<li> 0 - it inserts them with an algebraic method (on internal edges). This method is
-slightly faster but generates less regular meshes. </li>
-</ul>
-Default is 0.</li>
-
-\anchor blsurf_hinterpol_flag
-<li>\b hinterpol_flag (integer) - determines the computation of an
-interpolated value <i>v</i> between two points <i>P1</i> and <i>P2</i> on a
-curve. Let <i>h1</i> be the value at point <i>P1,</i> <i>h2</i> be the value at point
-<i>P2,</i> and <i>t</i> be a parameter varying from 0 to 1 when moving from <i>P1
-to</i> <i>P2</i>.
-<ul>
-<li>0 - the interpolation is linear: \f$v = h1 + t (h2 - h1 )\f$</li>
-<li>1 - the interpolation is geometric: \f$v = h1 \times \left( \frac{h1}{h2} \right)^{t}\f$</li>
-<li>2 - the interpolation is sinusoidal: \f$v = \frac{h1+h2}{2} + \frac{h1-h2}{2 \cdot \cos(\pi \cdot t)}\f$</li>
-</ul>
-Default is 0.</li>
-
-\anchor blsurf_hmean_flag
-<li>\b hmean_flag (integer) - determines the computation of the average of several
-values:<ul>
-<li>-1 - the minimum is computed.</li>
-<li>0 or 2 - the arithmetic average is computed.
-<li>1 - the geometric average is computed.</li>
-</ul>
-Default is 0.</li>
-
-<li>\b CheckAdjacentEdges, \b CheckCloseEdges and \b CheckWellDefined
-(integers) - gives the number of calls of equally named subroutines the
-purpose of which is to improve the mesh of domains having narrow
-parts. At each iteration,\b CheckCloseEdges decreases the sizes of the
-edges when two boundary curves are neighboring,\b CheckAdjacentEdges
-balances the sizes of adjacent edges, and \b CheckWellDefined checks if
-the parametric domain is well defined. Default values are 0.</li>
-
-
-<li>\b CoefRectangle (real)- defines the relative thickness of the rectangles
-used by subroutine \b CheckCloseEdges (see above). Default is 0.25.</li>
-
-<li>\b eps_collapse (real) - if more than 0.0, BLSURF removes
-curves whose lengths are less than \b eps_collapse. To obtain an
-approximate value of the length of a curve, it is arbitrarily
-split into 20 edges. Default is 0.0.</li>
-
-<li>\b eps_ends (real) - is used to detect the curves whose lengths are very
-small, which sometimes constitutes an error. A message is printed
-if \f$\left|P2-P1\right| < eps\_ends\f$, where <i>P1</i> and <i>P2</i> are the
-extremities of a curve. Default is \f$\frac{\mathrm{diag}}{500.0}\f$.</li>
-
-<li>\b prefix (char) - is a prefix of the files generated by
-BLSURF. Default is "x".</li>
-
-<li>\b refs (integer) - reference of a surface, used when exporting
-files. Default is 1.</li>
-</ul>
-
-\n
-The following PreCAD options are commonly usable. 
-<ul>
-<li>\b closed_geometry (int) - describes whether the working geometry 
-should be closed or not. When activated, this option helps PreCAD to process 
-the dirtiest geometries. By default this option is 0.</li>
-<li>\b debug (int) - If debug = 1 PreCAD will be very verbose and will output 
-some intermediate files in the working directory. By default this
-option is 0.</li>
-<li>\b eps_nano_relative (real) -  the same as \b eps_nano, but relatively to 
-the diagonal of the box bounding the geometry. By default this option is \f$10^{-5}\f$.</li>
-<li>\b eps_sewing (real) - tolerance of the assembly. It rarely requires to be tuned. 
-By default this option is \f$\mathrm{diag} \times 5 \cdot 10^{-4}\f$.</li>
-<li>\b eps_sewing_relative (real) -  the same as \b eps_nano but relatively to 
-the diagonal of the box bounding the geometry. By default this option is \f$5 \cdot 10^{-4}\f$.</li>
-<li>\b manifold_geometry (int) - describes whether the working geometry should be manifold or not.
-When activated, this option helps PreCAD to process the dirtiest
-geometries. By default this option is 0.</li>
-<li>\b create_tag_collision (int) - creates new tags from original ones in case 
-of collision (entity merge or association for example). By default
-this option is 0.</li>
-<li>\b periodic_tolerance (real) - defines the maximum distance error accepted between 
-two sets of periodic entities. By default this option is \f$\mathrm{diag} \times 10^{-5}\f$.</li>
-<li>\b periodic_tolerance_relative (real) -  the same as \b
-periodic_tolerance but in a relative unit. Bu default this option is \f$10^{-5}\f$.</li>
-<li>\b periodic_split_tolerance (real) - This periodicity processing related option defines 
-the minimum distance between a CAD point and an imprinted point. It allows to indirectly 
-control the number of created points and small edges. By default this
-option is \f$\mathrm{diag} \times 10^{-4}\f$.</li>
-<li>\b periodic_split_tolerance_relative (real -  the same as \b
-periodic_split_tolerance but in a relative unit. By default this
-option is \f$10^{-4}\f$.</li>
-</ul>
-
-\n
-The following advanced options are not documented and you can use them
-at your own risk.
-\n\n Integer variables:
-<ul>
-<li>    addsurf_ivertex</li>
-<li>    anisotropic    </li>
-<li>    background     </li>
-<li>    coiter         </li>
-<li>    communication  </li>
-<li>    decim          </li>
-<li>    export_flag    </li>
-<li>    file_h         </li>
-<li>    gridnu         </li>
-<li>    gridnv         </li>
-<li>    intermedfile   </li>
-<li>    memory         </li>
-<li>    normals        </li>
-<li>    optim          </li>
-<li>    pardom_flag    </li>
-<li>    pinch          </li>
-<li>    rigid          </li>
-<li>    surforient     </li>
-<li>    tconf          </li>
-<li>    topo_collapse  </li>
-</ul>
-Real variables:
-<ul>
-<li>    addsurf_angle    </li>
-<li>    addsurf_R        </li>
-<li>    addsurf_H        </li>
-<li>    addsurf_FG       </li>
-<li>    addsurf_r        </li>
-<li>    addsurf_PA       </li>
-<li>    angle_compcurv   </li>
-<li>    angle_ridge      </li>
-<li>    anisotropic_ratio</li>
-<li>    eps_pardom       </li>
-</ul>
-String variables:
-<ul>
-<li>    export_format  </li>
-<li>    export_option  </li>
-<li>    import_option  </li>  
-</ul>
-
-\ref blsurf_top "Back to top"
-
-\anchor blsurf_local_size
-<h1>Local size</h1>
-
-Local sizes can be defined on faces, edges or vertices.
-<ul>
-<li>The faces, edges and vertices can belong to the meshed geometrical
-object or to its sub-shapes (created using <b>Explode</b> command).</li>
-<li>Groups of faces, edges and vertices are also handled.</li>
-<li>It is possible to attribute the same size to several geometries using multi-selection.</li>
-<li>The sizes are constant values or python functions.</li>
-<li>In case of a python function, the following rules must be respected:
-<ul>
-<li>The name of the function is f.</li>
-<li>If geometry is a face or a group of faces, the function is f(u,v).</li>
-<li>If geometry is an edge or a group of edges, the function is f(t).</li>
-<li>If geometry is a vertex or a group of vertices, the function is f().</li>
-<li>The function must return a double.</li>
-</ul></li>
-</ul>
-
-3 different types of size maps can be defined:
-<ol>
-<li type="a">\ref blsurf_sizemap_computation "Computation of the physical size"</li>
-<li type="a">\ref blsurf_attractor "Advanced maps"</li>
-<li type="a">\ref blsurf_attractor_computation "Computation of attractors"</li>
-</ol>
-
-\ref blsurf_top "Back to top"
-
-\anchor blsurf_sizemap_computation
-<h2>Computation of the physical size</h2>
-\image html blsurf_parameters_sizemap1.png 
-
-The physical size is obtained by querying sizemap functions associated to the input CAD object for surfaces, curves and points.
-Each function can either return a value h (which is then trimmed
-between the two bounds hphymin and hphymax), or "no answer" (by not
-assigning a value to h), thus providing great flexibility in the
-specification of the sizes. The computation depends on whether point P is internal to a surface, internal to a curve, or at the end of several curves:
-<ul>
-<li> If point P is internal to a surface, the CAD surface size function is queried. If no answer is returned, one interpolates with the values at the vertices of the discretized interface curves.</li>
-<li> If point P is internal to a curve, the CAD curve size function is queried first. If no answer is returned, the surface size function is queried for every adjacent surface and the mean value of the returned values is computed. If no answer is returned, sizes h1 and h2 at both ends of the curve are considered (see next item) and the interpolated value is computed.</li>
-<li> If point P is at the extremity of several curves, the CAD point size function is queried first. If no answer is returned, the curve size function is queried for every adjacent curve and the mean value of the returned values is computed. If no answer is returned, the surface size function is queried for every adjacent surface and the mean value of the returned values is computed. If there is still no answer returned, the default value hphydef is kept.</li>
-</ul>
-In order to compute the mean of several values, the arithmetic mean is used by default, but this can be modified by the parameter \ref blsurf_hmean_flag "hmean flag". In the same way, in order to interpolate two values, a linear interpolation is used by default, but this can be modified by \ref blsurf_hinterpol_flag "hinterpol flag".
-
-\ref blsurf_local_size "Back to \"Local size\"" \n
-\ref blsurf_top "Back to top"
-
-\anchor blsurf_attractor
-<h2>Advanced maps</h2>
-\n
-\image html blsurf_parameters_sizemap2.png 
-\n
-More specific size maps can be defined on faces. 
-
-<ul>
-<li> <i> Attractors </i> allow to define the size of the mesh elements
-on a face so that the mesh is the finest on the attractor shape and
-becomes coarser when getting far from this shape.
-<ul> 
-<li> The selected attractor can be a Vertex, an Edge, a Wire or a
-Compound mixing several entities of those types.</li>
-<li> The attractor doesn't have to be a sub-shape of the shape to mesh.</li>
-<li> The size will grow exponentially (see the formula below) but is
-bounded by gradation, \n so if you want the formula to be strictly
-respected, you should set the <i>gradation</i> 
-to its maximum (2.5) in the <i>arguments</i> tab. 
-</ul>
-\n
-<li> Furthermore you can choose to <i> keep the size constant </i>
-until a certain distance from a shape. This option can be combined or
-not with an <i>attractor</i> size map described above. 
-<ul>
-<li> If the two options are combined the size will remain constant
-until the distance specified in "constant over" and grow then as
-prescribed by the attractor function.</li>
-<li> Else the growing is only controled by the standard arguments of
-BLSURF (gradation ...).</li>
-</ul>
-</ul>
-
-\image html blsurf_const_size_near_shape2.png "Example of size map with constant size option, the size is kept constant on the left side of the surface until a certain distance"
-
-Remark : The validation of the hypothesis might take a few seconds if
-attractors are defined or the "constant size" option is used because a
-map of distances has to be built on the whole surface for each face
-where such a hypothesis has been defined.
-
-<br><b>See Also</b> a sample TUI Script of the \ref tui_blsurf "creation of a BLSurf hypothesis", including size map.
-
-\ref blsurf_local_size "Back to \"Local size\"" \n
-\ref blsurf_top "Back to top"
-
-\anchor blsurf_attractor_computation
-<h2>Computation of attractors</h2>
-\n
-The size grows exponentially following the equation : 
-\f$h(d) = \mathrm{User Size} + (\mathrm{h\_start} - \mathrm{User Size}) \times e ^ { - \left( \frac{d}{R} \right) ^ {2} }\f$
-\n
-Where :
-<ul>
-<li>h_start is the desired size on the given attractor shape</li>
-<li>d is the distance of the current point from the attractor
-shape. The distance is the geodesic distance (i.e. calculated by following the surface to be meshed) </li>
-<li>R is called the distance of influence and allows controlling the growth rate of the mesh </li>
-</ul>
-
-\image html blsurf_attractors2.png "Example of mesh created using attractors, the attractors here are the side edges and the size grows from the side of the surface towards the apex"
-
-\ref blsurf_local_size "Back to \"Local size\"" \n
-\ref blsurf_top "Back to top"
-
-\anchor blsurf_enforced_elements
-<h1>Enforced vertices</h1>
-
-\image html blsurf_parameters_enforced_vertices.png
-
-It is possible to define some enforced vertices to BLSurf algorithm.
-An enforced vertex is defined on a Face or a Compound by
-<ul>
-<li> selecting an existing Vertex or Compound,</li>
-<li> or creating a new vertex given its coordinates.</li>
-</ul>
-The enforced vertex is the projection of a point defined by its
-(x,y,z) coordinates on the selected face.
-<ul>
-<li>It is possible to define several enforced vertices on a face or a group of faces.</li>
-<li>If the projected point is on the boundary or outside of the face, it will be ignored.</li>
-<li>If a group name is specified, the enforced nodes will be added in the group. If the group does not exist it will be created.
-</ul>
-
-You can specify BLSURF to use the internal vertices of the faces as enforced vertices by checking <i>Use internal vertices of all faces</i>.
-If a group name is specified, the internal enforced nodes will be added in the group. If the group does not exist it will be created.
-
-<br><b>See Also</b> a sample TUI Script of the \ref tui_blsurf "creation of a BLSurf hypothesis", including enforced vertices.
-
-\ref blsurf_top "Back to top"
-
-\anchor blsurf_limitations
-<h1>Limitations</h1>
-
-Currently BLSURF plugin has the following limitations.
-<ul>
-  <li>BLSURF algorithm cannot be used as a local algorithm (on
-      sub-meshes) or as a provider of a low-level
-      mesh for some 3D algorithms, because the BLSURF mesher (and
-      consequently plugin) does not provide the information on node
-      parameters on edges (U) and faces (U,V). For example the
-      following combinations of algorithms are impossible:
-      <ul>
-        <li> global MEFISTO or Quadrangle(mapping) + local BLSURF;</li>
-        <li> BLSURF + Projection 2D from faces meshed by BLSURF;</li>
-        <li> local BLSURF + Extrusion 3D;</li>
-      </ul>
-  </li>
-</ul>
-
-\ref blsurf_top "Back to top"
-
-*/
diff --git a/doc/salome/gui/SMESH/input/constructing_meshes.doc b/doc/salome/gui/SMESH/input/constructing_meshes.doc
index fc818ab5b..cefbd8ac7 100644
--- a/doc/salome/gui/SMESH/input/constructing_meshes.doc
+++ b/doc/salome/gui/SMESH/input/constructing_meshes.doc
@@ -181,30 +181,30 @@ shows a list of submeshes in the order of their priority.
 There is an example of submesh order modifications of the Mesh created on a Box
 shape. The main Mesh object:
 <ul>
-<li><i>3D</i> <b>Tetrahedron (Netgen)</b> with Hypothesis<b>Max Element Volume</b></li>
+<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>
-<li><i>1D</i> <b>Wire discretisation</b> with <b>Number of Segments</b>=20</li>
 </ul>
 The first submesh object <b>Submesh_1</b> created on <b>Face_1</b>
 is:
 <ul>
-<li><i>2D</i> Netgen 1D-2D with Hypothesis <b>Netgen Simple parameters</b>
-(Number of Segments = 4)</li>
+<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>
 </ul>
 The second submesh object <b>Submesh_2</b> created on <b>Face_2</b>
 is:
 <ul>
-<li><i>2D</i> Netgen 1D-2D with Hypothesis <b>Netgen Simple parameters</b>
-(Number of Segments = 8)</li>
+<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>
 </ul>
 
 And the last submesh object <b>Submesh_3</b> created on <b>Face_3</b>
 is:
 <ul>
-<li><i>2D</i> Netgen 1D-2D with Hypothesis <b>Netgen Simple parameters</b>
-(Number of Segments = 12)</li>
+<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>
 </ul>
+
 The submeshes become concurrent if they share sub-shapes that can be meshed 
 with different algorithms (or different hypothesises).
 In the example, we have three submeshes with concurrent algorithms,
diff --git a/doc/salome/gui/SMESH/input/ghs3d_hypo.doc b/doc/salome/gui/SMESH/input/ghs3d_hypo.doc
deleted file mode 100644
index dfd0041f5..000000000
--- a/doc/salome/gui/SMESH/input/ghs3d_hypo.doc
+++ /dev/null
@@ -1,186 +0,0 @@
-/*!
-
-\page ghs3d_hypo_page GHS3D Parameters hypothesis
-
-\anchor ghs3d_top
-\n GHS3D Parameters hypothesis works only with <b>Tetrahedron (GHS3D)</b> 
-algorithm. This algorithm is a commercial software.
-\n To get a licence, visit http://www.distene.com/corp/eval-distene.html
-
-<ol>
-<li>\ref ghs3d_general_parameters "General parameters"</li>
-<li>\ref ghs3d_advanced_parameters "Advanced parameters"</li>
-<li>\ref ghs3d_enforced_vertices "Enforced vertices"</li>
-<li>\ref ghs3d_enforced_meshes "Enforced meshes"</li>
-</ol>
-
-\anchor ghs3d_general_parameters
-<h1>General parameters</h1>
-
-\image html ghs3d_parameters_basic.png
-
-<ul>
-<li><b>Name</b> - allows to define the name of the hypothesis (GHS3D 
-Parameters by default).</li>
-
-<li><b>To mesh holes</b> - if checked, the algorithm will 
-create mesh in the holes inside a solid shape, else only the outermost
-shape will be meshed. Volumic elements created within holes are bound
-to the solid.</li>
-
-<li><b>Optimization level</b> - allows choosing the required
-optimization level: 
-<ul>
-<li>none,</li>
-<li>light,</li>
-<li>medium (standard),</li>
-<li>standard+,</li>
-<li>strong.</li>
-</ul>
-Higher level of
-optimisation provides better mesh, but can be time-consuming.
-</li>
-</ul>
-
-\ref ghs3d_top "Back to top"
-
-\anchor ghs3d_advanced_parameters
-<h1>Advanced parameters</h1>
-
-\image html ghs3d_parameters_advanced.png
-
-<li><b>Maximum memory size</b> - launches ghs3d software with
-work space limited to the specified amount of RAM, in Mbytes. If this option is
-checked off, the software will be launched with 7O% of the total RAM space. </li>
-
-<li><b>Initial memory size</b> - starts ghs3d software with
-the specified amount of work space, in Mbytes. If this option is checked off, the
-software will be started with 100 Megabytes of working space. </li>
-
-<li><b>Working directory</b> - allows defining the folder for input and output
-files of ghs3d software, which are the files starting with "GHS3D_" prefix. </li>
-
-<li><b>Keep working files</b> - allows checking input and output files
-of ghs3d software, while usually these files are removed after the
-launch of the mesher.</li>
-
-<li><b>Verbose level</b> - to choose verbosity level in the range from
-0 to 10.
-<ul> <li>0, no standard output,
-</li><li>2, prints the data, quality statistics of the skin and final
-meshes and indicates when the final mesh is being saved. In addition
-the software gives indication regarding the CPU time.
-</li><li>10, same as 2 plus the main steps in the computation, quality
-statistics histogram of the skin mesh, quality statistics histogram
-together with the characteristics of the final mesh.
-</li></ul></li>
-
-<li><b>To create new nodes</b> - if this option is checked off, ghs3d
-tries to create tetrahedrons using only the nodes of the 2D mesh.</li>
-
-<li><b>To remove the initial central point</b> TetMesh-GHS3D adds an internal point 
-at the gravity centre of the bounding box to speed up and to simplify 
-the meshing process. However, it is possible to refrain from creating 
-this point by using the command line option -no initial central point. This can be
-particularly useful to generate a volume mesh without internal points at all and in some rare cases
-at the boundary regeneration phase when it is impossible to proceed
-with the standard options
-(for example, when one dimension of the domain is more than 20 times greater than the other two).
-Use this option if the boundary regeneration has failed with the standard parameters and before using
-the recovery version (command line option -C).
-Note: when using this option, the speed of the meshing process may
-decrease, and the quality may change.
-Note: the boundary regeneration may fail with this option, in some rare cases.</li>
-
-<li><b>To use boundary recovery version</b> - enables using a
-boundary recovery module which tries to
-create volume meshes starting from very poor quality surface meshes
-(almost flat triangles on the surface, high density propagation,
-extreme aspect ratios, etc.) which fails with the standard version. The
-resulting volume mesh will however most likely have a very poor
-quality (poor aspect ratio of elements, tetrahedra with a very small
-positive volume).</li>
-
-<li><b>To use FEM correction</b> - Applies finite-element correction by 
-replacing overconstrained elements where it is possible. At first the process 
-slices the overconstrained edges and at second the overconstrained 
-facets. This ensures that there are no edges with two boundary
-vertices and that there are no facets with three boundary vertices. TetMesh-GHS3D gives the initial 
-and final overconstrained edges and facets. It also gives the facets
-which have three edges on the boundary.
-Note: when using this option, the speed of the meshing process may 
-decrease, quality may change, and the smallest volume may be smaller.
-By default, the FEM correction is not used.</li>
-
-<li><b>Option as text</b> - allows to input in the command line any text
-for ghs3d, for example, advanced options. </li>
-
-</ul>
-
-\ref ghs3d_top "Back to top"
-
-\anchor ghs3d_enforced_vertices
-<h1>Enforced vertices</h1>
-
-\note This feature is currently available only on meshes with no
-geometry attached. Such meshes can be obtained by
-<ul>
-<li>Copying an existing mesh</li>
-<li>Importing a mesh from file</li>
-<li>Applying a transformation to a mesh a get result in a new mesh</li>
-</ul>
-
-\image html ghs3d_enforced_vertices.png
-
-GHS3D algorithm can locally make the mesh finer. It is possible to
-define enforced vertices in the volume where the mesh will be detailed.
-A node will be created at the enforced vertex coordinates.
-
-An enforced vertex is defined by:
-<ul>
-<li>A vertex</li>
-<ul>
-<li>from GEOM (Vertex, Compound)</li>
-<li>or from (x,y,z) cartesian coordinates</li>
-</ul>
-<li>A constant physical size</li>
-<li>If a group name is given, the created node will be added to the
-group. If the group does not exist, it is created.</li>
-</ul>
-\ref ghs3d_top "Back to top"
-
-\anchor ghs3d_enforced_meshes
-<h1>Enforced Meshes</h1>
-
-\note This feature is currently only available on meshes with no
-geometry attached. Such meshes can be obtained by
-<ul>
-<li>Copying an existing mesh</li>
-<li>Importing a mesh from file</li>
-<li>Applying a transformation to a mesh a get result in a new mesh</li>
-</ul>
-
-\image html ghs3d_enforced_meshes.png
-
-GHS3D algorithm can be forced by other meshes, sub-meshes or
-groups. The constraint elements should be contained
-entirely into the solid mesh.
-<ul>
-<li>The constraint element types are:
-<ul>
-<li>NODE</li>
-<li>EDGE</li>
-<li>FACE</li>
-</ul></li>
-<li>If a size is given, the mesh will be refined around the enforced
-elements given the size</li>
-<li>If a group name is given, the enforced elements will be added to
-the group. If the group does not exist, it is created.</li>
-</ul>
-
-<br><b>See Also</b> a sample TUI Script of the \ref tui_ghs3d "creation of a Ghs3D hypothesis", including enforced vertices.
-
-\ref ghs3d_top "Back to top"
-
-
-*/
diff --git a/doc/salome/gui/SMESH/input/ghs3dprl_hypo.doc b/doc/salome/gui/SMESH/input/ghs3dprl_hypo.doc
deleted file mode 100644
index a7f69dfc8..000000000
--- a/doc/salome/gui/SMESH/input/ghs3dprl_hypo.doc
+++ /dev/null
@@ -1,471 +0,0 @@
-/*!
-
-\page ghs3dprl_hypo_page GHS3DPRL Parameters hypothesis
-
-\n GHS3DPRL Parameters hypothesis works only with <b>Tetrahedron (Tepal with TetMesh-GHS3D)</b> algorithm. 
-This algorithm is a commercial software, its use requires a licence (http://www.distene.com/fr/build/offer.html).
-\n Tepal_V1.4 gives the possibility to generate a partitioned
-mesh with 200 million tetrahedrons on a computer with average memory size
-(2Go RAM) in about 50 hours on one CPU (Xeon, 2008).
-\n New Tepal_V2.0 gives the possibility to generate a partitioned mesh with (for the moment) no more than 100 million 
-tetrahedrons on computers using MPI, (Total 16 Go RAM) 
-in about 900 seconds (!yes! : !seconds!) on 2 octo processors (Xeon, 2009).
-The launch of this beta-version is described below.
-\n This is a serious alternative to GHS3D, which requires a much less common
-configuration with 64Go RAM to only try to make a partition of a mesh with
-200 million tetrahedrons, no result guaranteed.
-\n
-\note The Plugin doesn't load in the Memory the supposedly large resulting meshes. 
-The meshes are saved in MED files and can be imported in the user-defined location via menu File-Import-MED Files.
-\n Pay attention, that Salome GUI needs 2Go RAM to load a MED
-file with 5 million tetrahedrons.
-
-\image html ghs3dprl_parameters_basic.png
-
-<ul>
-<li>
-<b>Name</b> - allows to define the name of the hypothesis (GHS3DPRL Parameters by default).
-</li>
-<li>
-<b>MED_Name</b> - allows to define the path and the prefix of the 
-resulting MED files ("DOMAIN" by default). 
-If the path is not defined, the environment variable $SALOME_TMP_DIR
-is used. If $SALOME_TMP_DIR is not defined as well, the environment
-variable $TMP is used.
-</li>
-<li>
-<b>Nb_Part</b> - allows to define the number of generated MED files.
-The initial skin (triangles) will be meshed (tetrahedrons) and partitioned 
-in Nb_Part by the elementary algorithm implemented in Tepal.<br>
-</li>
-<li>
-<b>Keep_Files</b> - if this box is checked, input files of Tepal 
-(GHS3DPRL.points and GHS3DPRL.faces) are not deleted after use (...if the
-background mode was not used).
-</li>
-<li>
-<b>Tepal_in_Background</b> - if this box is checked, Tepal execution
-and MED file generation are launched in background mode and the user
-can even exit Salome. Pay attention that in this case Tepal algorithm works
-independently of "killSalome.py", and sometimes on another host.
-</li>
-<li>
-<b>To_Mesh_Holes</b> - if this box is checked, the parameter component 
-of tetmesh-ghs3d will mesh holes.
-</li>
-
-<h1>Modifying GHS3DPRL Advanced Parameters</h1><br>
-GHS3DPRL Plugin launches a standalone binary executable tepal2med.<br>
-tepal2med launches tepal, waits for the end of computation, and
-converts the resulting output tepal files into MED files.<br>
-Some advanced optional parameters are accessible as arguments.<br>
-
-If keep_files option is checked, it is possible to re-launch tepal2med
-or tepal in the Terminal as a command with custom parameters.<br>
-
-<li>
-<b>Advanced tepal2med Parameters</b> - type "tepal2med --help" in the Terminal. <p>
-
-\verbatim
-myname@myhost > /export/home/myname/salome_5/GHS3DPRLPLUGIN_5/bin/salome/tepal2med --help
-Available options:
-   --help         : produces this help message
-   --casename     : path and name of input tepal2med files which are
-                       - output files of tepal .msg .noboite .faces .points .glo
-                       - output file of GHS3DPRL_Plugin casename_skin.med (optional)
-                         with initial skin and its initial groups
-   --number       : number of partitions
-   --medname      : path and name of output MED files
-   --limitswap    : max size of working cpu memory (Mo) (before swapping on .temp files)
-   --verbose      : trace of execution (0->6)
-   --test         : more tests about joints, before generation of output files
-   --menu         : a GUI menu for option number
-   --launchtepal  : also launch tepal on files casename.faces and casename.points and option number
-   --meshholes    : force parameter component of tetmesh-ghs3d to mesh holes
-   --background   : force background mode from launch tepal and generation of final MED files (big meshes)
-   --deletegroups : regular expression (see QRegExp) which matches unwanted groups in final MED files
-                    (try --deletegroups="(\bAll_Nodes|\bAll_Faces)"
-                    (try --deletegroups="((\bAll_|\bNew_)(N|F|T))"
-example:
-   tepal2med --casename=/tmp/GHS3DPRL --number=2 --medname=DOMAIN --limitswap=1000 
-             --verbose=0 --test=yes --menu=no --launchtepal=no
-
-\endverbatim
-\n
-</li>
-<li>
-<b>Advanced Tepal_V1.4 Parameters</b> <p>
-
-\verbatim
-
-USAGE : tepal options
-
-With options :
-     --filename name (-f name) :
-          Prefix of the input case (MANDATORY)
-
-     --ndom n (-n n) :
-          Number of subdomains to make (MANDATORY)
-
-     --ghs3d ghs3d options (-g ghs3d options) :
-          Runs temesh ghs3d on a previously generated subdomain. (ghs3d options must be "quoted")
-
-     --memory m (-m m) :
-          Max amount of memory (megabytes) allowed for ghs in the cutting process. (default is 0 : unlimited)
-
-     --mesh_only  (-Z ) :
-          Only (re)meshes all subdomains and updates communications messages
-
-     --mesh_call command (-c command) :
-          Calls the user specified command for meshing all the
-          subomains after their skin has been generated
-
-     --stats_only  (-S ) :
-          Only computes and shows some statistics on subdomains
-
-     --rebuild  (-r ) :
-          Merges final subdomains skins
-
-     --rebuild_tetra  (-R ) :
-          Merges final subdomains skins and tetraedra
-
-     --rebuild_iface  (-i ) :
-          Includes interfaces in final subdomains merge
-
-     --rebuild_retag  (-t ) :
-          Tags vertices, faces (and tetra if selected) with their
-          subdomain number in the final merge of subdomains (keeps the lowest tag for shared elements)
-
-     --rebuild_ensight_parts  (-e ) :
-          Builds ensight geom file with parts
-
-     --tetmesh_args str (-G str) :
-          Arguments to pass to Tetmesh during cutting process
-
-\endverbatim
-\n
-</li>
-<li>
-<b>Advanced ghs3d Parameters (through Tepal_V1.4's --tetmesh_args)</b> - type "ghs3d -h" in a Terminal. <p>
-
-\verbatim
-myname@myhost > ghs3d -h
-
-USE
-    /export/home/myname/ghs3d-4.0/DISTENE/Tools/TetMesh-GHS3D4.0/bin/Linux/ghs3dV4.0
-    [-u] [-m memory>] [-M MEMORY] [-f prefix] [-v verbose]
-    [-c component] [-p0] [-C] [-E count] [-t] [-o level]
-    [-I filetype] [-a/-b] [-O n m]
-
-DESCRIPTION
-
- -u (-h)        : prints this message.
-
- -m memory      : launches the software with memory in Megabytes.
-                  The default value of this parameter is 64 Megabytes and its
-                  minimum value is 10 Megabytes.
-                  It is also possible to set this parameter with the
-                  environment variable GHS3D_MEMORY by means of an operation
-                  equivalent to:
-                           setenv GHS3D_MEMORY memory,
-                  the value specified in the command line has the priority on
-                  the environment variable.
-
- -M MEMORY      : provides the automatic memory adjustment feature.
-                  If MEMORY (in Megabytes) is equal to zero, the size of the work space is
-                  calculated from the input. If MEMORY is not equal to
-                  zero, the software starts with MEMORY amount of work space.
-                  The software reallocates memory as necessary.
-                  The start value of  MEMORY can range from 0 to 64 Megabytes,
-                  the maximum depends on -m option and the actual memory available.
-
- -f prefix      : defines the generic prefix of the files.
-
- -v verbose     : sets the output level parameter (the verbose parameter
-                  must be in the range 0 to 10).
-
- -c component   : chooses the meshed component. If the parameter is
-                      0, all components will be meshed, if
-                      1, only the main (outermost) component will be meshed
-
- -p0            : disables creation of internal points.
-
- -C             : uses an alternative boundary recovery mechanism. It should be used only
-                  when the standard boundary recovery fails.
-
- -E count       : sets the extended output for error messages. If -E is used,
-                  the error messages will be printed, it is possible
-                  to indicate the maximum number of printed messages between 1 and 100.
-
- -t             : generates an error file prefix.Log
-
- -o level       : sets the required optimisation level.
-                  Valid optimisation levels are:
-                  none, light, standard or strong,
-                  with increase of "quality vs speed" ratio.
-
- -I filetype    : defines the input mesh format as follows:
-                    -IP input files are ascii files, named prefix.points
-                     and prefix.faces - this is the default type of files
-                    -IPb input files are binary files, named prefix.pointsb
-                     and prefix.facesb
-                    -IM input file is ascii file, named prefix.mesh
-                  where prefix is defined with -f option
-
- -a/-b          : selects the output file type:
-                    -a for ascii (the default) and
-                    -b for binary.
-
- -On            : saves a NOPO file in addition. NOPO is the mesh data
-                  structure of the Simail and Modulef software packages.
- -Om            : saves a mesh file in addition.
- -Omn           : saves both NOPO and mesh files.
-
- ==============================================================================
-                   TETMESH-GHS3D SOFTWARE 4.0-3 (December, 2006)
-                                 END OF SESSION
-                COPYRIGHT (C)1989-2006 INRIA ALL RIGHTS RESERVED
- ==============================================================================
-      ( Distene SAS
-        Phone: +33(0)1-69-26-62-10   Fax: +33(0)1-69-26-90-33
-        EMail: support@distene.com )
-
-\endverbatim
-\n
-</li>
-<h1>Saving user's preferred GHS3DPRL Advanced Parameters</h1><br>
-GHS3DPRL Plugin launches standalone binary executable tepal2med.<br>
-You may rename file tepal2med as tepal2med.exe for example, and replace
-tepal2med by a shell script at your convenience to overriding parameters.
-<br>... or else $PATH modification... .<br>Idem for file tepal.<br><br>
-<li>
-<b>Advanced tepal2med Parameters</b> - overriding parameter deletegroups<p>
-You may rename tepal2med as tepal2med.exe for example.
-
-\code
-#!/bin/bash
-#script tepal2med overriding parameter deletegroups
-#we have renamed binary executable tepal2med as tepal2med.exe
-#echo tepal2med initial parameters are $1 $2 $3 $4 ... or $*
-#$0 is ignored
-
-tepal2med.exe $* --deletegroups="(\bAll_Nodes|\bAll_Faces)"
-
-\endcode
-\n
-</li>
-<li>
-<b>Advanced Tepal_V1.4 Parameters</b> - overriding parameter component of ghs3d (to mesh holes). <p>
-You may rename tepal as tepal.exe for example.
-
-\code
-#!/bin/bash
-#script tepal overriding parameter component of tetmesh-ghs3d
-#we have renamed binary executable tepal as tepal.exe
-
-#optionnaly we could set licence only for us
-DISTENE_LICENSE_FILE="Use global envvar: DLIM8VAR"
-DLIM8VAR="dlim8 1:1:29030@is142356/0016175ef08c::a1ba1...etc...e19"
-SIMULOGD_LICENSE_FILE=29029@is142356
-
-tepal.exe $* --tetmesh_args "-c 0"
-
-\endcode
-\n
-</li>
-<li>
-<b>Advanced tepal Parameters</b> - overriding launching tepal on other host. <p>
-You may rename tepal as tepal.exe for example.
-
-\code
-#!/bin/bash
-#script tepal overriding launching tepal on other host (tepal run 64 bits only)
-#we have renamed binary executable tepal as tepal.exe
-#common file system (same path) otherwise scp... on input or result files
-#ssh -keygen -t rsa done and files id_rsa et id-rsa.pub move in ~/.ssh
-
-#example of typical command
-#tepal -f /home/myname/tmp/GHS3DPRL -n 4 > /home/myname/tmp/tepal.log
-#echo parameters $1 $2 $3 $4 ... or $*
-
-#tepal licence ought to be known on otherhost
-ssh otherhost "tepal.exe $* > /home/myname/tmp/tepal.log"
-
-#or more and more
-#ssh otherhost "tepal.exe $* --tetmesh_args \"-c 0\"" > /home/myname/tmp/tepal.log
-
-\endcode
-\n
-</li>
-
-<h1>Tepal_V2.0 and MPI use.</h1><br>
-This all new beta-version needs MPI, (openmpi-1.3.1 was used). To use it you have to proceed 
-as done in "overriding parameter component of ghs3d".
-Advanced ghs3d Parameters (through Tepal_V1.4's --tetmesh_args) are not assumed yet.
-It meshes holes.
-\n You may rename tepal as tepal64_v2.exe for example, and replace tepal by a shell script like below.
-
-<li>
-<b>example tepal_v2_mpirun.</b><p>
-
-\code
-
-#!/bin/bash
-#script tepal overriding launching Tepal_V2.0 with MPI (tepal run 64 bits only).
-#we have renamed binary executable tepal as tepal64_v2.exe.
-#typical command to launch tepal v1 :
-#tepal -f /tmp/myname/GHS3DPRL -n 16 > /tmp/myname/tepal.log
-#this file is an exemple to transform this call for tepal v2.0, 
-#   (beta version using .mesh input file)
-#you have to adapt for your convenience.
-
-#first problem  is convert v1 input files GHS3DPRL.faces and GHS3DPRL.points 
-#               to v2 input file GHS3DPRL.mesh.
-#second problem is to launch on heterogeneous system linux cluster of 
-#               2 hosts (64 bits) of 8 nodes (by example)
-#               with different 2 executables codes linked on 2 different
-#               openmpi shared library codes.
-#third problem  is convert tepal v2 output files GHS3DPRL*.mesh
-#               to v1 input files GHS3DPRL*.faces an GHS3DPRL*.points.
-
-#you have to work on the same physical disk and same path input and ouput files : $SAME_DIR
-#you have to work on different physical disk but same path and name for executable files 
-#    (and shared libraries) : $DIFF_DIR
-
-echo "parameter 0="$0
-echo "parameter 1="$1
-echo "parameter 2="$2
-echo "parameter 3="$3
-echo "parameter 4="$4
-
-export SAME_DIR=/same_physical_disk_and_same path/tmp
-export DIFF_DIR=/different_physical_disk_but_same path/myname
-
-#copy input local files from local current directory (something like /tmp/myname)
-#in this case we need /tmp/myname and $SAME_DIR different
-cd $SAME_DIR
-rm *
-cp $2* .
-
-export IN_FILES=`basename $2`
-export IN_DIR=`dirname $2`
-#created .mesh from .faces et .points
-/through_salome_path/facespoints2mesh.py $IN_FILES
-
-#there are 2 executable openmpi and library through 2 physical DIFF_DIR
-export PATH=$DIFF_DIR/openmpi-1.3.1_install/bin:${PATH}
-export LD_LIBRARY_PATH=$DIFF_DIR/openmpi-1.3.1_install/lib:${LD_LIBRARY_PATH}
-
-#there are 2 executables tepal_v2 through 2 physical DIFF_DIR
-export LD_LIBRARY_PATH=$DIFF_DIR/tepal-2.0.0/bin/Linux_64:${LD_LIBRARY_PATH}
-export PATH=$DIFF_DIR/tepal-2.0.0/bin/Linux_64:$PATH
-
-#small test betweeen friends
-#rm hostnames.log
-#mpirun -n $4 hostname >> hostnames.log
-
-#there necessary set env licence file for tepal v2
-export DISTENE_LICENSE_FILE="Use global envvar: DLIM8VAR"
-export DLIM8VAR="dlim8 1:1:29030@is142356/0016175ef08c::a1ba...9e19"
-export SIMULOGD_LICENSE_FILE=29029@is142356 
-export LICENSE_FILE=/product/distene/dlim8.var.sh
-
-#mpirun with necessary set envenvironment
-export TMP_ENV="-x PATH -x LD_LIBRARY_PATH -x DISTENE_LICENSE_FILE -x DLIM8VAR \
-                -x SIMULOGD_LICENSE_FILE -x LICENSE_FILE"
-#mpirun $TMPENV -n $4 which tepal64_v2.exe >> hostnames.log
-
-#real mpirun uncomment after verify small test
-mpirun $TMPENV -n $4 tepal64_v2.exe --in $IN_FILES.mesh --out $IN_FILES.mesh --verbose 100
-
-#convert output files tepalv1 format
-/through_salome_path/mesh2facespoints.py $IN_FILES
-
-#copy ouputs files from $SAME_DIR to local current directory (something like /tmp/myname)
-cp -f hostnames.log $IN_DIR
-cp -f $IN_FILES* $IN_DIR
-
-#ls -al $SAME_DIR
-#cat $SAME_DIR/hostnames.log
-#cat /tmp/myname/tepal.log
-
-\endcode
-\n
-</li>
-
-<h1>TUI use.</h1><br>
-
-<li>
-<b>example ex30_tepal.py.</b><p>
-
-\code
-
-#!/bin/python
-import os
-
-import geompy
-import smesh
-
-# Parameters
-# ----------
-
-results = "/tmp/ZZ"
-
-radius =  50
-height = 200
-
-# Build a cylinder
-# ----------------
-
-base = geompy.MakeVertex(0, 0, 0)
-direction = geompy.MakeVectorDXDYDZ(0, 0, 1)
-
-cylinder = geompy.MakeCylinder(base, direction, radius, height)
-
-geompy.addToStudy(cylinder, "Cylinder")
-
-# Define a mesh on a geometry
-# ---------------------------
-
-m = smesh.Mesh(cylinder)
-
-# 2D mesh with BLSURF
-# -------------------
-
-algo2d = m.Triangle(smesh.BLSURF)
-
-algo2d.SetPhysicalMesh(1)
-algo2d.SetPhySize(5)
-
-algo2d.SetGeometricMesh(0)
-
-# 3D mesh with tepal
-# ------------------
-
-algo3d = m.Tetrahedron(smesh.GHS3DPRL)
-
-algo3d.SetMEDName(results)
-algo3d.SetNbPart(4)
-algo3d.SetBackground(False)
-algo3d.SetKeepFiles(False)
-algo3d.SetToMeshHoles(True)
-
-# Launch meshers
-# --------------
-
-status = m.Compute()
-
-# Test if ok
-# ----------
-
-if os.access(results+".xml", os.F_OK):
-    print "Ok: tepal"
-else:
-    print "KO: tepal"
-\endcode
-\n
-</li>
-</ul>
-
-
-*/
diff --git a/doc/salome/gui/SMESH/input/hexotic_hypo.doc b/doc/salome/gui/SMESH/input/hexotic_hypo.doc
deleted file mode 100644
index d42d1f827..000000000
--- a/doc/salome/gui/SMESH/input/hexotic_hypo.doc
+++ /dev/null
@@ -1,39 +0,0 @@
-/*!
-
-\page hexotic_hypo_page Hexotic Parameters hypothesis
-
-\n Hexotic Parameters hypothesis works only with <b>Hexotic</b> 
-algorithm. This algorithm is a commercial software.
-\n To get a licence, visit http://www.distene.com/corp/eval-distene.html
-
-\image html hexotic_parameters.png
-
-<ul>
-<li><b>Name</b> - allows to define the name of the hypothesis (Hexotic 
-Parameters by default).</li>
-
-<li><b>Nb. Hexes Min Level</b> - allows defining the minimal level of recursive partitioning on the initial octree cube.</li>
-
-<li><b>Nb. Hexes Max Level</b> - allows defining the maximal level of recursive partitioning on the initial octree cube.</li>
-
-<li><b>Salome Quadrangles</b> - not documented.</li>
-
-<li><b>Generate smooth meshes no ridges</b> - specifies that the mesher can ignore ridges. A ridge is a geometrical entity (a sharp edge). The resulting meshes will have better quality elements, at the price of "smoothing" out the geometry.
-</li>
-
-<li><b>Authorize invalid elements</b> - specifies that the mesher must conform as much as possible to the geometry (especially the sharp edges). The resulting meshes may contain invalid elements (but with positive volumes: for example, three vertices of an hexahedron on the same edge), for the benefit of better geometry accuracy.
-</li>
-
-<li><b>Sharp angle threshold in degrees</b> - specifies the angle between two triangles above which the hex mesher will consider the edge common to these two triangles as being a "ridge". A ridge is a geometrical entity (a sharp edge) which has to be kept as it is in the final hex mesh.The default value is 60 (degrees).<br>If you raise this value, the hex mesher will detect less ridges, and the final solid mesh will therefore be smoother. On the other hand, if you reduce this value, more ridges will be detected and the algorithm will face harder situations to conform to.
-</li>
-
-<li><b>Number of threads</b> - specifies the number of threads to be used (this should be the number of cores or processors of a shared memory parallel architecture).
-</li>
-
-<li><b>Working directory</b> - specifies the directory where the input/output files will be created.
-</li>
-</ul>
-
-\note If BLSURF is used as 2D algo, and if a GMF file is defined as output file (using SetGMFFile(my2Dmesh.mesh)), then Hexotic will use this file as input.
-This allows to avoid the reconstruction of the GMF file from the SMESH structure and can improve the global computation time.
-*/
diff --git a/doc/salome/gui/SMESH/input/netgen_2d_3d_hypo.doc b/doc/salome/gui/SMESH/input/netgen_2d_3d_hypo.doc
deleted file mode 100644
index 652b32919..000000000
--- a/doc/salome/gui/SMESH/input/netgen_2d_3d_hypo.doc
+++ /dev/null
@@ -1,98 +0,0 @@
-/*!
-
-\page netgen_2d_3d_hypo_page Netgen 2D and 3D hypotheses
-
-<b>Netgen 2D Parameters</b> and <b>Netgen 3D  Parameters</b> hypotheses work only with
-<b>Netgen 1D-2D</b>, <b>Netgen 2D</b>, <b>Netgen 1D-2D-3D</b> and
-<b>Netgen 3D</b> algorithms. <b>Netgen 1D-2D</b> and <b>Netgen
-1D-2D-3D</b>  algorithms do not require definition of lower-level
-hypotheses and algorithms (2D and 1D for meshing 3D objects and 1D for
-meshing 2D objects).
-
-\image html netgen2d3d.png
-<center><em>Dialog boxes of <b>Netgen 1D-2D</b> and <b>Netgen
-1D-2D-3D</b> algorithms </em></center>
-<br>
-
-\image html netgen2d3d_only.png
-<center><em>Dialog boxes of <b>Netgen 2D</b> and <b>Netgen 3D</b>
-algorithms </em></center>
-
-- <b>Name</b> - allows to define the name for the algorithm (Netgen
-2D (or 3D) Parameters by default).
-- <b>Max Size</b> - maximum linear dimensions for mesh cells.
-- <b>Min Size</b> - minimum linear dimensions for mesh cells. It is
-ignored if it is more than <b>Max Size</b>.
-- <b>Second Order</b> - if this box is checked in, the algorithm will
-create second order nodes on the mesh, which actually will become
-\ref adding_quadratic_elements_page "Quadratic".
-- <b>Fineness</b> - ranging from Very Coarse to Very Fine allows to set the
-level of meshing detalization using the three parameters below. You
-can select Custom to define them manually.
-- <b>Growth rate</b> - allows to define how much the linear dimensions of
-two adjacent cells can differ (i.e. 0.3 means 30%).
-- <b>Nb. Segs per Edge</b> and <b>Nb Segs per Radius</b> - allows to define the
-minimum number of mesh segments in which edges and radiuses will be
-split.
-- <b>Allow Quadrangles</b> - allows to use quadrangle elements in a
-triangle 2D mesh. This checkbox is not present in Netgen 3D parameters
-because currently building a tetrahedral mesh with quadrangle faces is
-not possible.
-- <b>Optimize</b> - if this box is checked in, the algorithm will try to
-create regular (possessing even sides) elements.
-
-\image html netgen3d_local_size.png
-
-- <b>Local sizes</b> - allows to define size of elements on and
-around specified geometrical edges and vertices. To define the local
-size it is necessary to select a geometrical edge or vertex in the
-object browser or in the viewer, and to click <b>On Edge</b> or <b>On
-Vertex</b> correspondingly. <b>Name</b> of the geometrical object and
-a default <b>Value</b> will be added in the table where the
-<b>Value</b> can be changed.
-- <b>Remove</b> - deletes a selected row from the table.
-
-\image html netgen2d3d_simple.png
-
-<b>Netgen 2D simple parameters</b> and <b>Netgen 3D simple
-parameters</b> allow defining the size of elements for each
-dimension.
-
-\b 1D group allows defining the size of 1D elements in either of two ways: 
-- <b>Number of Segments</b> has the same sense as \ref
-number_of_segments_anchor "Number of segments" hypothesis with
-equidistant distribution.
-- <b>Local Length</b> has the same sense as \ref 
-average_length_anchor "Local Length" hypothesis.
-
-\b 2D group allows defining the size of 2D elements 
-- <b>Length from edges</b> if checked in, acts like \ref
-length_from_edges_anchor "Length from Edges" hypothesis, else
-- <b>Max. Element Area</b> defines the maximum element area like \ref
-max_element_area_anchor "Max Element Area" hypothesis.
-- <b>Allow Quadrangles</b> - allows to use quadrangle elements in a
-triangle 2D mesh. This checkbox is not present in Netgen 3D simple parameters
-because currently building a tetrahedral mesh with quadrangle faces is
-not possible.
-
-\b 3D groups allows defining the size of 3D elements.
-- <b>Length from faces</b> if checked in, the area of sides of
-volumic elements will be equal to an average area of 2D elements, else
-- <b>Max. Element Volume</b> defines the maximum element volume like
-\ref max_element_volume_hypo_page "Max Element Volume"
-hypothesis.
-
-\note Netgen algorithm does not strictly follow the input
-parameters. The actual mesh can be more or less dense than
-required. There are several factors in it:
-- NETGEN does not actually use "NbOfSegments" parameter for discretization of
-edge. This parameter is used  only to define the local element size
-(size at the given point), so local sizes of adjacent edges influence
-each other.
-- NETGEN additionally restricts the element size according to edge curvature.
-- The local size of edges influences the size of close triangles.
-- The order of elements and their size in the 1D mesh generated by
-NETGEN differ from those in the 1D mesh generated by Regular_1D
-algorithm, resulting in different 2D and 3D meshes.
-
-*/
diff --git a/doc/salome/gui/SMESH/input/smeshpy_interface.doc b/doc/salome/gui/SMESH/input/smeshpy_interface.doc
index 6669892c0..e725ef99c 100644
--- a/doc/salome/gui/SMESH/input/smeshpy_interface.doc
+++ b/doc/salome/gui/SMESH/input/smeshpy_interface.doc
@@ -36,21 +36,13 @@ distribution are always available:
 - Hexa(3D)
 - etc...
 
-There are also some algorithms, which can be installed optionally,
-some of them are based on open-source meshers:
-- NETGEN (1D-2D, 2D, 1D-2D-3D, 3D)
-
-... and others are based on commercial meshers:
-- GHS3D (3D)
-- BLSURF (2D)
-
 To add hypotheses, use the interfaces, provided by the assigned
 algorithms.
 
 Below you can see an example of usage of the package smesh for 3d mesh generation. 
 
 \anchor example_3d_mesh
-<h2>Example of 3d mesh generation with NETGEN:</h2>
+<h2>Example of 3d mesh generation:</h2>
 
 \code
 from geompy import * 
@@ -115,7 +107,7 @@ algo2d = tetra.Triangle()
 algo2d.LengthFromEdges() 
 
 # Define 3D hypothesis
-algo3d = tetra.Tetrahedron(smesh.NETGEN) 
+algo3d = tetra.Tetrahedron()
 algo3d.MaxElementVolume(100) 
 
 # Compute the mesh
diff --git a/doc/salome/gui/SMESH/input/tui_creating_meshes.doc b/doc/salome/gui/SMESH/input/tui_creating_meshes.doc
index 220e63c8a..24161d483 100644
--- a/doc/salome/gui/SMESH/input/tui_creating_meshes.doc
+++ b/doc/salome/gui/SMESH/input/tui_creating_meshes.doc
@@ -25,7 +25,7 @@ algo1D.NumberOfSegments(7)
 algo2D = tetra.Triangle()
 algo2D.MaxElementArea(800.)
 
-algo3D = tetra.Tetrahedron(smesh.NETGEN)
+algo3D = tetra.Tetrahedron()
 algo3D.MaxElementVolume(900.)
 
 # compute the mesh
@@ -103,31 +103,32 @@ Nb_Segments_1 = Regular_1D.NumberOfSegments(20)
 Nb_Segments_1.SetDistrType( 0 )
 MEFISTO_2D = Mesh_1.Triangle()
 Max_Element_Area_1 = MEFISTO_2D.MaxElementArea(1200)
-Tetrahedron_Netgen = Mesh_1.Tetrahedron(algo=smesh.NETGEN)
-Max_Element_Volume_1 = Tetrahedron_Netgen.MaxElementVolume(40000)
+Tetrahedron = Mesh_1.Tetrahedron()
+Max_Element_Volume_1 = Tetrahedron.MaxElementVolume(40000)
 
 # create submesh and assign algorithms on Face_1
-Netgen_1D_2D = Mesh_1.Triangle(algo=smesh.NETGEN,geom=Face_1)
-SubMesh_1 = Netgen_1D_2D.GetSubMesh()
-NETGEN_2D_Simple_Parameters_1 = Netgen_1D_2D.Parameters(which=smesh.SIMPLE)
-NETGEN_2D_Simple_Parameters_1.SetNumberOfSegments( 4 )
-NETGEN_2D_Simple_Parameters_1.LengthFromEdges()
+Regular_1D_1 = Mesh_1.Segment(geom=Face_1)
+Nb_Segments_2 = Regular_1D_1.NumberOfSegments(4)
+Nb_Segments_2.SetDistrType( 0 )
+MEFISTO_2D_1 = Mesh_1.Triangle(algo=smesh.MEFISTO,geom=Face_1)
+Length_From_Edges_2D = MEFISTO_2D_1.LengthFromEdges()
+SubMesh_1 = MEFISTO_2D_1.GetSubMesh()
 
 # create submesh and assign algorithms on Face_2
-Netgen_1D_2D_1 = Mesh_1.Triangle(algo=smesh.NETGEN,geom=Face_2)
-SubMesh_2 = Netgen_1D_2D_1.GetSubMesh()
-NETGEN_2D_Simple_Parameters_2 = Netgen_1D_2D_1.Parameters(which=smesh.SIMPLE)
-NETGEN_2D_Simple_Parameters_2.SetNumberOfSegments( 8 )
-NETGEN_2D_Simple_Parameters_2.LengthFromEdges()
-smeshObj_1 = smesh.CreateHypothesis('NETGEN_SimpleParameters_2D',
-'NETGENEngine')
+Regular_1D_2 = Mesh_1.Segment(geom=Face_2)
+Nb_Segments_3 = Regular_1D_2.NumberOfSegments(8)
+Nb_Segments_3.SetDistrType( 0 )
+MEFISTO_2D_2 = Mesh_1.Triangle(algo=smesh.MEFISTO,geom=Face_2)
+Length_From_Edges_2D_1 = MEFISTO_2D_2.LengthFromEdges()
+SubMesh_2 = MEFISTO_2D_2.GetSubMesh()
 
 # create submesh and assign algorithms on Face_3
-Netgen_1D_2D_2 = Mesh_1.Triangle(algo=smesh.NETGEN,geom=Face_3)
-SubMesh_3 = Netgen_1D_2D_2.GetSubMesh()
-NETGEN_2D_Simple_Parameters_3 = Netgen_1D_2D_2.Parameters(which=smesh.SIMPLE)
-NETGEN_2D_Simple_Parameters_3.SetNumberOfSegments( 12 )
-NETGEN_2D_Simple_Parameters_3.LengthFromEdges()
+Regular_1D_3 = Mesh_1.Segment(geom=Face_3)
+Nb_Segments_4 = Regular_1D_3.NumberOfSegments(12)
+Nb_Segments_4.SetDistrType( 0 )
+MEFISTO_2D_3 = Mesh_1.Triangle(algo=smesh.MEFISTO,geom=Face_3)
+Length_From_Edges_2D_2 = MEFISTO_2D_3.LengthFromEdges()
+SubMesh_3 = MEFISTO_2D_3.GetSubMesh()
 
 # check exisiting submesh priority order
 [ [ SubMesh_1, SubMesh_3, SubMesh_2 ] ] = Mesh_1.GetMeshOrder()
@@ -223,7 +224,7 @@ algo1D.NumberOfSegments(7)
 algo2D = tetra.Triangle()
 algo2D.MaxElementArea(800.)
 
-algo3D = tetra.Tetrahedron(smesh.NETGEN)
+algo3D = tetra.Tetrahedron()
 algo3D.MaxElementVolume(900.)
 
 # compute the mesh
diff --git a/doc/salome/gui/SMESH/input/tui_defining_blsurf_hypotheses.doc b/doc/salome/gui/SMESH/input/tui_defining_blsurf_hypotheses.doc
deleted file mode 100644
index 71c2b7f6e..000000000
--- a/doc/salome/gui/SMESH/input/tui_defining_blsurf_hypotheses.doc
+++ /dev/null
@@ -1,156 +0,0 @@
-/*!
-
-\page tui_defining_blsurf_hypotheses_page Defining Hypotheses for BLSurf Algorithm
-
-\anchor tui_blsurf
-<h2>Construction of Mesh using BLSurf algorithm</h2>
-<h3>Basic hypothesis</h3>
-\code
-import geompy
-import smesh
-import BLSURFPlugin
-
-# create a box
-box = geompy.MakeBoxDXDYDZ(200., 200., 200.)
-geompy.addToStudy(box, "box")
-
-# get sub-shapes
-Face_1   = geompy.SubShapeAllSorted(box, geompy.ShapeType["FACE"])[0]
-Edge_1   = geompy.SubShapeAllSorted(box, geompy.ShapeType["EDGE"])[0]
-Vertex_1 = geompy.SubShapeAllSorted(box, geompy.ShapeType["VERTEX"])[0]
-
-Face_2   = geompy.SubShapeAllSorted(box,    geompy.ShapeType["FACE"])[5]
-Wire_1   = geompy.SubShapeAllSorted(Face_2, geompy.ShapeType["WIRE"])[0]
-
-# Geom object with sizemaps can be unpublished in study.
-# They will then be automatically published.
-geompy.addToStudyInFather(box,Face_1, "Face_1")
-geompy.addToStudyInFather(box,Edge_1, "Edge_1")
-geompy.addToStudyInFather(box,Vertex_1, "Vertex_1")
-
-geompy.addToStudyInFather(box   ,Face_2, "Face_2")
-geompy.addToStudyInFather(Face_2,Wire_1, "Wire_1")
-
-# create a mesh on the box
-blsurfMesh = smesh.Mesh(box,"box: BLSurf mesh")
-
-# create a BLSurf algorithm for faces
-algo2d = blsurfMesh.Triangle(algo=smesh.BLSURF)
-
-# End of script
-\endcode
-
-<h3>Adding sizemaps</h3>
-\code
-# optional - set physical mesh to 2 = Size Map
-algo2d.SetPhysicalMesh( 2 )
-
-# optional - set global mesh size
-algo2d.SetPhySize( 34.641 )
-
-# set size on Face_1
-algo2d.SetSizeMap(Face_1, 'def f(u,v): return 10' )
-# set size on Edge_1
-algo2d.SetSizeMap(Edge_1, 'def f(t): return 5' )
-# set size on Vertex_1
-algo2d.SetSizeMap(Vertex_1, 'def f(): return 2' )
-
-# compute the mesh
-blsurfMesh.Compute()
-
-# End of script
-\endcode
-
-<h3>Adding enforced vertices</h3>
-\code
-
-# Add enforced vertex for Face_1 on (50, 50, 50)
-# The projection coordinates will be (50, 50, 0)
-algo2d.SetEnforcedVertex(Face_1, 50, 50, 50)
-
-# Add another enforced vertex on (150, 150, 150)
-algo2d.SetEnforcedVertex(Face_1, 150, 150, 150)
-
-# Retrieve and print the list of enforced vertices defines on Face_1
-enfList = algo2d.GetEnforcedVertices(Face_1)
-print "List of enforced vertices for Face_1: "
-print enfList
-
-# compute the mesh
-blsurfMesh.Compute()
-
-# Remove an enforced vertex and print the list
-algo2d.UnsetEnforcedVertex(Face_1, 50, 50, 50)
-enfList = algo2d.GetEnforcedVertices(Face_1)
-print "List of enforced vertices for Face_1: "
-print enfList
-
-# compute the mesh
-blsurfMesh.Compute()
-
-# Remove all enforced vertices defined on Face_1
-algo2d.UnsetEnforcedVertices(Face_1)
-
-# compute the mesh
-blsurfMesh.Compute()
-
-# End of script
-
-\endcode
-
-<h3>Adding an attractor</h3>
-\code
-
-# Add an attractor on Face_2, which shape is Wire_1
-
-# The size on Wire_1 is 1 and will grow until a maximum of 36.641 (physical size set above) 
-# The influence distance of the attractor is 20
-# The size is kept constant until a distance of 10
-algo2d.SetAttractorGeom(Face_2, Wire_1, 1, 36.641, 20, 10)
-
-# In order to let the attractor control the growing of the mesh let set
-# the gradation to its maximum
-algo2d.SetGradation( 2.5 )
-
-# compute the mesh
-blsurfMesh.Compute()
-
-# End of script
-
-\endcode
-
-<h3>Using internal vertices</h3>
-\code
-
-# Creating a geometry containing internal vertices
-Face_3 = geompy.MakeFaceHW(1, 1, 1)
-Vertex_2 = geompy.MakeVertex(0.2, 0.2, 0)
-Partition_1 = geompy.MakePartition([Face_3, Vertex_2], [], [], [], geompy.ShapeType["FACE"], 0, [], 0)
-OX = geompy.MakeVectorDXDYDZ(1, 0, 0)
-OY = geompy.MakeVectorDXDYDZ(0, 1, 0)
-Multi_Translation_1 = geompy.MakeMultiTranslation2D(Partition_1, OX, 1, 10, OY, 1, 10)
-geompy.addToStudy( Face_3, 'Face_3' )
-geompy.addToStudy( Vertex_2, 'Vertex_2' )
-geompy.addToStudy( Partition_1, 'Partition_1' )
-geompy.addToStudy( OX, 'OX' )
-geompy.addToStudy( OY, 'OY' )
-geompy.addToStudy( Multi_Translation_1, 'Multi-Translation_1' )
-
-# The mesh on the geometry with internal vertices
-blsurfMesh_internal = smesh.Mesh(Multi_Translation_1, "blsurfMesh_internal")
-algo2d = blsurfMesh_internal.Triangle(algo=smesh.BLSURF)
-algo2d.SetPhySize( 0.1 )
-
-# Allows BLSURF to take into account internal vertices
-algo2d.SetInternalEnforcedVertexAllFaces( True )
-
-# Add the created nodes into a group
-algo2d.SetInternalEnforcedVertexAllFacesGroup( "my group" )
-
-# compute the mesh
-blsurfMesh_internal.Compute()
-
-# End of script
-\endcode
-
-*/
diff --git a/doc/salome/gui/SMESH/input/tui_defining_ghs3d_hypotheses.doc b/doc/salome/gui/SMESH/input/tui_defining_ghs3d_hypotheses.doc
deleted file mode 100644
index 6623cb624..000000000
--- a/doc/salome/gui/SMESH/input/tui_defining_ghs3d_hypotheses.doc
+++ /dev/null
@@ -1,234 +0,0 @@
-/*!
-
-\page tui_defining_ghs3d_hypotheses_page Defining Hypotheses for Ghs3D Algorithm
-
-\anchor tui_ghs3d
-
-<ol>
-<li>\ref tui_ghs3d_basic "Construction of Mesh using Ghs3D algorithm"</li>
-<li>\ref tui_ghs3d_enforced_vertices "Adding enforced vertices"</li>
-<li>\ref tui_ghs3d_enforced_meshes "Adding enforced mesh"</li>
-</ol>
-
-\anchor tui_ghs3d_basic
-<h2>Construction of Mesh using Ghs3D algorithm</h2>
-
-\code
-import geompy
-import smesh
-import BLSURFPlugin
-import GHS3DPlugin
-
-# create a box
-box = geompy.MakeBoxDXDYDZ(200., 200., 200.)
-geompy.addToStudy(box, "box")
-
-# create a mesh on the box
-ghs3dMesh = smesh.Mesh(box,"box: Ghs3D and BLSurf mesh")
-
-# create a BLSurf algorithm for faces
-BLSURF = ghs3dMesh.Triangle(algo=smesh.BLSURF)
-GHS3D = ghs3dMesh.Tetrahedron(algo=smesh.GHS3D)
-
-# compute the mesh
-ghs3dMesh.Compute()
-
-# End of script
-\endcode
-
-\image html ghs3d_screenshot.png Ghs3d mesh withtout hypothesis
-
-\ref tui_ghs3d "Back to top"
-
-\anchor tui_ghs3d_enforced_vertices
-<h2>Adding enforced vertices</h2>
-
-\code
-
-# An enforced vertex can be added via:
-# - the coordinates x,y,z
-# - a GEOM vertex or compound (No geometry, TUI only)
-#
-# The created enforced nodes can also be stored in
-# a group.
-#
-# This feature is available only on meshes without geometry.
-
-# Ex1: Add one enforced vertex with coordinates (50,50,100) 
-#      and physical size 2.
-
-import geompy
-import smesh
-import BLSURFPlugin
-import GHS3DPlugin
-
-# create a box
-box = geompy.MakeBoxDXDYDZ(200., 200., 200.)
-geompy.addToStudy(box, "box")
-# create a mesh on the box
-ghs3dMesh = smesh.Mesh(box,"box: Ghs3D and BLSurf mesh")
-# create a BLSurf algorithm for faces
-ghs3dMesh.Triangle(algo=smesh.BLSURF)
-# compute the mesh
-ghs3dMesh.Compute()
-
-# Make a copy of the 2D mesh
-ghs3dMesh_wo_geometry = smesh.CopyMesh( ghs3dMesh, 'Ghs3D wo geometry', 0, 0)
-
-# create a Ghs3D algorithm and hypothesis and assign them to the mesh
-GHS3D = smesh.CreateHypothesis('GHS3D_3D', 'GHS3DEngine')
-GHS3D_Parameters = smesh.CreateHypothesis('GHS3D_Parameters', 'GHS3DEngine')
-ghs3dMesh.AddHypothesis( GHS3D )
-ghs3dMesh.AddHypothesis( GHS3D_Parameters )
-# Create the enforced vertex
-GHS3D_Parameters.SetEnforcedVertex( 50, 50, 100, 2) # no group
-# Compute the mesh
-ghs3dMesh.Compute()
-
-
-# Ex2: Add one vertex enforced by a GEOM vertex at (50,50,100) 
-#      with physical size 5 and add it to a group called "My special nodes"
-
-# Create another GHS3D hypothesis and assign it to the mesh without geometry
-GHS3D_Parameters_wo_geometry = smesh.CreateHypothesis('GHS3D_Parameters', 'GHS3DEngine')
-ghs3dMesh_wo_geometry.AddHypothesis( GHS3D )
-ghs3dMesh_wo_geometry.AddHypothesis( GHS3D_Parameters_wo_geometry )
-
-# Create the enforced vertex
-p1 = geompy.MakeVertex(150, 150, 100)
-geompy.addToStudy(p1, "p1")
-GHS3D_Parameters_wo_geometry.SetEnforcedVertexGeomWithGroup( p1, 5 , "My special nodes")
-#GHS3D_Parameters.SetEnforcedVertexGeom( p1, 5 ) # no group
-
-# compute the mesh
-ghs3dMesh_wo_geometry.Compute()
-
-# Erase all enforced vertices
-GHS3D_Parameters.ClearEnforcedVertices()
-
-# End of script
-
-\endcode
-
-\image html ghs3d_screenshot_enf1.png Ghs3d mesh with enforced vertex
-\image html ghs3d_screenshot_enf2.png Ghs3d mesh with enforced vertex from GEOM vertex
-
-\ref tui_ghs3d "Back to top"
-
-\anchor tui_ghs3d_enforced_meshes
-<h2>Adding enforced mesh</h2>
-
-\code
-
-# It is possible to constrain GHS3D with another mesh or group.
-# The constraint can refer to the nodes, edges or faces.
-# This feature is available only on meshes without geometry.
-# The constraining elements are called enforced elements for the mesh.
-# They can be recovered using groups if necessary.
-
-# In the following examples, a box and a cylinder are meshed.
-# The mesh of the cylinder will be used as a constraint for the 
-# 3D mesh of the box.
-
-import geompy
-import smesh
-import BLSURFPlugin
-import GHS3DPlugin
-
-box = geompy.MakeBoxDXDYDZ(200, 200, 200)
-geompy.addToStudy( box, "box" )
-cylindre = geompy.MakeCylinderRH(50, 50)
-geompy.TranslateDXDYDZ(cylindre, 100, 100, 30)
-face_cyl = geompy.ExtractShapes(cylindre, geompy.ShapeType["FACE"], True)[1]
-geompy.addToStudy( cylindre, 'cylindre' )
-geompy.addToStudyInFather( cylindre, face_cyl, 'face_cyl' )
-p1 = geompy.MakeVertex(20, 20, 20)
-p2 = geompy.MakeVertex(180, 180, 20)
-c = geompy.MakeCompound([p1,p2])
-geompy.addToStudy( p1, "p1" )
-geompy.addToStudy( p2, "p2" )
-geompy.addToStudy( c, "c" )
-
-# Create the 2D algorithm and hypothesis
-BLSURF = smesh.CreateHypothesis('BLSURF', 'BLSURFEngine')
-# For the box
-BLSURF_Parameters = smesh.CreateHypothesis('BLSURF_Parameters', 'BLSURFEngine')
-BLSURF_Parameters.SetPhysicalMesh( 1 )
-BLSURF_Parameters.SetPhySize( 200 )
-# For the cylinder
-BLSURF_Parameters2 = smesh.CreateHypothesis('BLSURF_Parameters', 'BLSURFEngine')
-BLSURF_Parameters2.SetGeometricMesh( 1 )
-
-# Create the 3D algorithm and hypothesis
-GHS3D = smesh.CreateHypothesis('GHS3D_3D', 'GHS3DEngine')
-GHS3D_Parameters_node = smesh.CreateHypothesis('GHS3D_Parameters', 'GHS3DEngine')
-#GHS3D_Parameters_node.SetToMeshHoles( 1 )
-GHS3D_Parameters_edge = smesh.CreateHypothesis('GHS3D_Parameters', 'GHS3DEngine')
-#GHS3D_Parameters_edge.SetToMeshHoles( 1 )
-GHS3D_Parameters_face = smesh.CreateHypothesis('GHS3D_Parameters', 'GHS3DEngine')
-GHS3D_Parameters_face.SetToMeshHoles( 1 ) # to mesh inside the cylinder
-GHS3D_Parameters_mesh = smesh.CreateHypothesis('GHS3D_Parameters', 'GHS3DEngine')
-GHS3D_Parameters_mesh.SetToMeshHoles( 1 ) # to mesh inside the cylinder
-
-# Create the mesh on the cylinder
-Mesh_cylindre = smesh.Mesh(cylindre)
-smesh.SetName(Mesh_cylindre,"Mesh_cylindre")
-Mesh_cylindre.AddHypothesis( BLSURF )
-Mesh_cylindre.AddHypothesis( BLSURF_Parameters2 )
-# Create some groups
-face_cyl_faces = Mesh_cylindre.GroupOnGeom(face_cyl,'group_face_cyl', smesh.FACE)
-face_cyl_edges = Mesh_cylindre.GroupOnGeom(face_cyl,'group_edge_cyl', smesh.EDGE)
-face_cyl_nodes = Mesh_cylindre.GroupOnGeom(face_cyl,'group_node_cyl', smesh.NODE)
-Mesh_cylindre.Compute()
-
-# Create the mesh on the cylinder
-Mesh_box_tri = smesh.Mesh(box)
-smesh.SetName(Mesh_box_tri,"Mesh_box_tri")
-Mesh_box_tri.AddHypothesis( BLSURF )
-Mesh_box_tri.AddHypothesis( BLSURF_Parameters )
-Mesh_box_tri.Compute()
-
-# Create 4 copies of the 2D mesh to test the 3 types of contraints (NODE, EDGE, FACE)
-# from the whole mesh and from groups of elements.
-# Then the 3D algo and hypothesis are assigned to them.
-
-mesh_mesh = smesh.CopyMesh( Mesh_box_tri, 'Enforced by faces of mesh', 0, 0)
-mesh_mesh.AddHypothesis( GHS3D )
-mesh_mesh.AddHypothesis( GHS3D_Parameters_mesh)
-
-mesh_node = smesh.CopyMesh( Mesh_box_tri, 'Enforced by group of nodes', 0, 0)
-mesh_node.AddHypothesis( GHS3D )
-mesh_node.AddHypothesis( GHS3D_Parameters_node)
-
-mesh_edge = smesh.CopyMesh( Mesh_box_tri, 'Enforced by group of edges', 0, 0)
-mesh_edge.AddHypothesis( GHS3D )
-mesh_edge.AddHypothesis( GHS3D_Parameters_edge)
-
-mesh_face = smesh.CopyMesh( Mesh_box_tri, 'Enforced by group of faces', 0, 0)
-mesh_face.AddHypothesis( GHS3D )
-mesh_face.AddHypothesis( GHS3D_Parameters_face)
-
-# Add the enforced elements
-GHS3D_Parameters_mesh.SetEnforcedMeshWithGroup(Mesh_cylindre.GetMesh(),smesh.FACE,"faces from cylinder")
-GHS3D_Parameters_node.SetEnforcedMeshWithGroup(face_cyl_nodes,smesh.NODE,"nodes from face_cyl_nodes")
-GHS3D_Parameters_edge.SetEnforcedMeshWithGroup(face_cyl_edges,smesh.EDGE,"edges from face_cyl_edges")
-GHS3D_Parameters_face.SetEnforcedMeshWithGroup(face_cyl_faces,smesh.FACE,"faces from face_cyl_faces")
-
-#Compute the meshes
-mesh_node.Compute()
-mesh_edge.Compute()
-mesh_face.Compute()
-mesh_mesh.Compute()
-
-# End of script
-
-\endcode
-
-\image html ghs3d_screenshot_enf3.png
-\image html ghs3d_screenshot_enf4.png
-\image html ghs3d_screenshot_enf5.png
-\image html ghs3d_screenshot_enf6.png
-
-\ref tui_ghs3d "Back to top"
-
-*/
diff --git a/doc/salome/gui/SMESH/input/tui_defining_hypotheses.doc b/doc/salome/gui/SMESH/input/tui_defining_hypotheses.doc
index 4ced1731a..e98eca6b4 100644
--- a/doc/salome/gui/SMESH/input/tui_defining_hypotheses.doc
+++ b/doc/salome/gui/SMESH/input/tui_defining_hypotheses.doc
@@ -231,7 +231,7 @@ tetra = smesh.Mesh(cyl, "Cylinder : tetrahedrical mesh")
 # assign algorithms
 algo1D = tetra.Segment()
 algo2D = tetra.Triangle()
-algo3D = tetra.Tetrahedron(smesh.NETGEN)
+algo3D = tetra.Tetrahedron()
 
 # assign 1D and 2D hypotheses
 algo1D.NumberOfSegments(7)
@@ -363,8 +363,8 @@ algo1D = tetra.Segment()
 # create a Mefisto 2D algorithm for faces
 algo2D = tetra.Triangle()
 
-# create a Netgen 3D algorithm for solids
-algo3D = tetra.Tetrahedron(smesh.NETGEN)
+# create a 3D algorithm for solids
+algo3D = tetra.Tetrahedron()
 
 # define hypotheses
 algo1D.Arithmetic1D(1, 4)
@@ -373,17 +373,6 @@ algo2D.LengthFromEdges()
 # compute the mesh
 tetra.Compute()
 
-# 3. Create a tetrahedral mesh on the box with NETGEN_2D3D algorithm
-tetraN = smesh.Mesh(box, "Box : tetrahedrical mesh by NETGEN_2D3D")
-
-# create a Netgen_2D3D algorithm for solids
-algo3D = tetraN.Tetrahedron(smesh.FULL_NETGEN) 
-
-# define hypotheses
-n23_params = algo3D.Parameters()
-
-# compute the mesh
-tetraN.Compute()
 \endcode
 
 <br>
@@ -700,10 +689,10 @@ mesh = Mesh(shape, "CFD")
 
 mesh.Segment().NumberOfSegments( 4 )
 
-mesh.Triangle(NETGEN_2D)
+mesh.Triangle()
 mesh.Quadrangle(face1)
 mesh.Compute()
-algo3D = mesh.Tetrahedron(NETGEN)
+algo3D = mesh.Tetrahedron()
 
 thickness = 20
 numberOfLayers = 10
@@ -718,10 +707,4 @@ mesh.MakeGroup("Prims",VOLUME,FT_ElemGeomType,"=",Geom_PENTA)
 
 \endcode
 
-\n Other meshing algorithms:
-
-<ul>
-<li>\subpage tui_defining_blsurf_hypotheses_page</li>
-<li>\subpage tui_defining_ghs3d_hypotheses_page</li>
-</ul>
 */
diff --git a/doc/salome/gui/SMESH/input/tui_filters.doc b/doc/salome/gui/SMESH/input/tui_filters.doc
index 6d51c0a10..0eb41dd28 100755
--- a/doc/salome/gui/SMESH/input/tui_filters.doc
+++ b/doc/salome/gui/SMESH/input/tui_filters.doc
@@ -48,7 +48,7 @@ Filter 3D mesh elements (volumes) according to the aspect ratio value:
 \code
 # create mesh with volumes
 from SMESH_mechanic import *
-mesh.Tetrahedron( algo=smesh.NETGEN )
+mesh.Tetrahedron()
 mesh.Compute()
 # get volumes with aspect ratio < 2.0
 filter = smesh.GetFilter(smesh.VOLUME, smesh.FT_AspectRatio3D, smesh.FT_LessThan, 2.0)
@@ -165,7 +165,7 @@ Filter 3D mesh elements (volumes) according to the volume value:
 \code
 # create mesh with volumes
 from SMESH_mechanic import *
-mesh.Tetrahedron( algo=smesh.NETGEN )
+mesh.Tetrahedron()
 mesh.Compute()
 # get volumes faces with volume > 100
 filter = smesh.GetFilter(smesh.VOLUME, smesh.FT_Volume3D, smesh.FT_MoreThan, 100)
@@ -480,7 +480,7 @@ value of its edges and diagonals:
 \code
 # create mesh with volumes
 from SMESH_mechanic import *
-mesh.Tetrahedron( algo=smesh.NETGEN )
+mesh.Tetrahedron()
 mesh.Compute()
 # get all volumes that have elements with length > 10
 filter = smesh.GetFilter(smesh.VOLUME, smesh.FT_MaxElementLength3D, smesh.FT_MoreThan, 10)
@@ -660,7 +660,7 @@ the point of view of MED convention.
 \code
 # create mesh with volumes
 from SMESH_mechanic import *
-mesh.Tetrahedron( algo=smesh.NETGEN )
+mesh.Tetrahedron()
 mesh.Compute()
 # get all badly oriented volumes
 filter = smesh.GetFilter(smesh.VOLUME, smesh.FT_BadOrientedVolume)
@@ -729,7 +729,7 @@ entity type.
 \code
 # create mesh with volumes
 from SMESH_mechanic import *
-mesh.Tetrahedron( algo=smesh.NETGEN )
+mesh.Tetrahedron()
 mesh.Compute()
 # get all triangles, quadrangles, tetrahedrons, pyramids
 filter_tri = smesh.GetFilter(smesh.FACE, smesh.FT_ElemGeomType, smesh.Geom_TRIANGLE)
diff --git a/doc/salome/gui/SMESH/input/tui_generate_flat_elements.doc b/doc/salome/gui/SMESH/input/tui_generate_flat_elements.doc
index 412691d8b..eaf544556 100644
--- a/doc/salome/gui/SMESH/input/tui_generate_flat_elements.doc
+++ b/doc/salome/gui/SMESH/input/tui_generate_flat_elements.doc
@@ -18,6 +18,9 @@ by flat elements.
 The big cylinder is defined by two geometric volumes.
 
 \code
+import geompy
+import smesh
+import SMESH
 # geometry 
 
 O = geompy.MakeVertex(0, 0, 0)
@@ -45,13 +48,11 @@ vec2 = geompy.MakeVector(Vertex_5, Vertex_6)
 # meshing (we have linear tetrahedrons here, but other elements are OK)
 
 Mesh_1 = smesh.Mesh(Partition_1)
-BLSURF = Mesh_1.Triangle(algo=smesh.BLSURF)
-BLSURF_Parameters = BLSURF.Parameters()
-BLSURF_Parameters.SetPhysicalMesh( 0 )
-BLSURF_Parameters.SetGeometricMesh( 1 )
-BLSURF_Parameters.SetAngleMeshS( 16 )
-BLSURF_Parameters.SetAngleMeshC( 16 )
-GHS3D_3D = Mesh_1.Tetrahedron(algo=smesh.GHS3D)
+Regular_1D = Mesh_1.Segment()
+Nb_Segments_1 = Regular_1D.NumberOfSegments(15)
+MEFISTO_2D = Mesh_1.Triangle(algo=smesh.MEFISTO)
+Length_From_Edges_2D = MEFISTO_2D.LengthFromEdges()
+ALGO3D = Mesh_1.Tetrahedron()
 isDone = Mesh_1.Compute()
 
 # relevant groups of volumes and faces
diff --git a/doc/salome/gui/SMESH/input/tui_modifying_meshes.doc b/doc/salome/gui/SMESH/input/tui_modifying_meshes.doc
index 1dd65bfa1..922d15969 100644
--- a/doc/salome/gui/SMESH/input/tui_modifying_meshes.doc
+++ b/doc/salome/gui/SMESH/input/tui_modifying_meshes.doc
@@ -936,7 +936,7 @@ Mesh = smesh.Mesh(Sphere)
 Regular_1D = Mesh.Segment()
 Nb_Segments = Regular_1D.NumberOfSegments(5)
 MEFISTO_2D = Mesh.Triangle()
-Tetrahedron_Netgen = Mesh.Tetrahedron(algo=smesh.NETGEN)
+Tetrahedron = Mesh.Tetrahedron()
 
 # compute mesh
 
diff --git a/doc/salome/gui/SMESH/input/tui_notebook_smesh.doc b/doc/salome/gui/SMESH/input/tui_notebook_smesh.doc
index 049409200..a300ee633 100644
--- a/doc/salome/gui/SMESH/input/tui_notebook_smesh.doc
+++ b/doc/salome/gui/SMESH/input/tui_notebook_smesh.doc
@@ -32,15 +32,15 @@ algo1D.NumberOfSegments("NbSegments")
 algo2D = tetra.Triangle()
 algo2D.MaxElementArea("MaxElementArea")
 
-algo3D = tetra.Tetrahedron(smesh.NETGEN)
+algo3D = tetra.Tetrahedron()
 algo3D.MaxElementVolume("MaxElementVolume")
 
 # compute the mesh
 ret = tetra.Compute()
 
 # translate the mesh
-point = smesh.PointStructStr("Offset", 0., 0.)
-vector = smesh.DirStructStr(point) 
+point = smesh.PointStruct("Offset", 0., 0.)
+vector = smesh.DirStruct(point) 
 tetra.TranslateObject(tetra, vector, 0)
 \endcode
 
diff --git a/doc/salome/gui/SMESH/input/tui_quality_controls.doc b/doc/salome/gui/SMESH/input/tui_quality_controls.doc
index 420e507e1..bc99172aa 100644
--- a/doc/salome/gui/SMESH/input/tui_quality_controls.doc
+++ b/doc/salome/gui/SMESH/input/tui_quality_controls.doc
@@ -268,13 +268,12 @@ geompy.addToStudy( Plane_2, "Plane_2" )
 import smesh
 
 import StdMeshers
-import NETGENPlugin
 
 Mesh_1 = smesh.Mesh(Partition_1)
 Regular_1D = Mesh_1.Segment()
 Max_Size_1 = Regular_1D.MaxSize(34.641)
 MEFISTO_2D = Mesh_1.Triangle()
-Tetrahedron_Netgen = Mesh_1.Tetrahedron(algo=smesh.NETGEN)
+Tetrahedronn = Mesh_1.Tetrahedron()
 isDone = Mesh_1.Compute()
 
 # create a group of free faces
@@ -285,11 +284,11 @@ aGroup = Mesh_1.CreateEmptyGroup(smesh.FACE, "Free_faces")
 aGroup.Add(aFaceIds)
 
 # print the result
-print "Criterion: Free nodes Nb = ", len(anNodeIds)
+print "Criterion: Free faces Nb = ", len(aFaceIds)
 j = 1
 for i in range(len(aFaceIds)):
   if j > 20: j = 1; print ""
-  print anNodeIds[i],
+  print aFaceIds[i],
   j = j + 1
   pass
 print ""
diff --git a/doc/salome/gui/SMESH/input/tui_viewing_meshes.doc b/doc/salome/gui/SMESH/input/tui_viewing_meshes.doc
index 6ef80bf1b..fc0094e4b 100644
--- a/doc/salome/gui/SMESH/input/tui_viewing_meshes.doc
+++ b/doc/salome/gui/SMESH/input/tui_viewing_meshes.doc
@@ -25,7 +25,7 @@ algo1D.NumberOfSegments(3)
 algo2D = tetra.Triangle()
 algo2D.MaxElementArea(10.)
 
-algo3D = tetra.Tetrahedron(smesh.NETGEN)
+algo3D = tetra.Tetrahedron()
 algo3D.MaxElementVolume(900.)
 
 # Creation of SubMesh
diff --git a/src/SMESHGUI/SMESHGUI_Hypotheses.cxx b/src/SMESHGUI/SMESHGUI_Hypotheses.cxx
index f94f39785..2832c7afd 100644
--- a/src/SMESHGUI/SMESHGUI_Hypotheses.cxx
+++ b/src/SMESHGUI/SMESHGUI_Hypotheses.cxx
@@ -649,8 +649,17 @@ void SMESHGUI_HypothesisDlg::onHelp()
 {
   LightApp_Application* app = (LightApp_Application*)(SUIT_Session::session()->activeApplication());
   if (app) {
-    SMESHGUI* aSMESHGUI = dynamic_cast<SMESHGUI*>( app->activeModule() );
-    app->onHelpContextModule(aSMESHGUI ? app->moduleName(aSMESHGUI->moduleName()) : QString(""), myHelpFileName);
+    QString name = "SMESH";
+    if(myCreator) {
+      QVariant pluginName = myCreator->property( PLUGIN_NAME );
+      if( pluginName.isValid() ) {
+	QString rootDir = pluginName.toString() + "PLUGIN_ROOT_DIR";
+	QString varValue = QString( getenv(rootDir.toLatin1().constData()));
+	if(!varValue.isEmpty())
+	  name = pluginName.toString() + "PLUGIN";
+      }
+    }    
+    app->onHelpContextModule(name, myHelpFileName);
   }
   else {
     QString platform;
diff --git a/src/SMESHGUI/SMESHGUI_HypothesesUtils.cxx b/src/SMESHGUI/SMESHGUI_HypothesesUtils.cxx
index 623f0dbd2..da8e162c4 100644
--- a/src/SMESHGUI/SMESHGUI_HypothesesUtils.cxx
+++ b/src/SMESHGUI/SMESHGUI_HypothesesUtils.cxx
@@ -451,6 +451,12 @@ namespace SMESH
               // map hypothesis creator to a hypothesis name
               // BUG 0020378
               //myHypCreatorMap[aHypType] = aCreator;
+
+	      //rnv : This dynamic property of the QObject stores the name of the plugin.
+	      //      It is used to obtain plugin root dir environment variable
+              //      in the SMESHGUI_HypothesisDlg class. Plugin root dir environment 
+	      //      variable is used to display documentation.
+	      aCreator->setProperty(PLUGIN_NAME,aHypData->PluginName);
             }
           }
         }
diff --git a/src/SMESHGUI/SMESHGUI_HypothesesUtils.h b/src/SMESHGUI/SMESHGUI_HypothesesUtils.h
index 101c6b276..c003212fb 100644
--- a/src/SMESHGUI/SMESHGUI_HypothesesUtils.h
+++ b/src/SMESHGUI/SMESHGUI_HypothesesUtils.h
@@ -57,6 +57,9 @@ class SMESHGUI_GenericHypothesisCreator;
 class SALOMEDSClient_SObject;
 class algo_error_array;
 
+
+#define PLUGIN_NAME "PLUGIN_NAME"
+
 namespace SMESH
 {
   SMESHGUI_EXPORT
diff --git a/src/SMESH_SWIG/smeshDC.py b/src/SMESH_SWIG/smeshDC.py
index bd67a223b..3c36b1be6 100644
--- a/src/SMESH_SWIG/smeshDC.py
+++ b/src/SMESH_SWIG/smeshDC.py
@@ -44,10 +44,6 @@
 ##     @defgroup l3_hypos_1dhyps 1D Meshing Hypotheses
 ##     @defgroup l3_hypos_2dhyps 2D Meshing Hypotheses
 ##     @defgroup l3_hypos_maxvol Max Element Volume hypothesis
-##     @defgroup l3_hypos_netgen Netgen 2D and 3D hypotheses
-##     @defgroup l3_hypos_ghs3dh GHS3D Parameters hypothesis
-##     @defgroup l3_hypos_blsurf BLSURF Parameters hypothesis
-##     @defgroup l3_hypos_hexotic Hexotic Parameters hypothesis
 ##     @defgroup l3_hypos_quad Quadrangle Parameters hypothesis
 ##     @defgroup l3_hypos_additi Additional Hypotheses