From 1ea8c2828e8ebcfcff032c29aae4fbcc2ad42693 Mon Sep 17 00:00:00 2001 From: eap Date: Mon, 14 Jul 2014 14:20:18 +0400 Subject: [PATCH] About KEEP_NETGEN_OUTPUT env --- .../NETGENPLUGIN/input/additional_hypo.doc | 16 ++++----- doc/salome/gui/NETGENPLUGIN/input/index.doc | 14 ++++++-- .../NETGENPLUGIN/input/netgen_2d_3d_hypo.doc | 33 +++++++++---------- 3 files changed, 34 insertions(+), 29 deletions(-) diff --git a/doc/salome/gui/NETGENPLUGIN/input/additional_hypo.doc b/doc/salome/gui/NETGENPLUGIN/input/additional_hypo.doc index 44766e8..dfc1fce 100644 --- a/doc/salome/gui/NETGENPLUGIN/input/additional_hypo.doc +++ b/doc/salome/gui/NETGENPLUGIN/input/additional_hypo.doc @@ -2,19 +2,12 @@ \page additional_hypo_page Additional Hypotheses -\n Additional Hypotheses can be applied as a supplement to the -main hypotheses, introducing additional concepts to mesh creation. +\n Additional Hypotheses can be applied as a supplement to +introducing additional concepts to mesh creation. Following additional hypotheses can be used together with NETGEN algoritm: +
  • Quadrangle Preference - This additional hypothesis can be + used together with Netgen 2D algorithm. +It allows Netgen 2D to build quad-dominant meshes.
  • +
    + For more detailed description of the described above hypothesis please refer SALOME Mesh User's Guide. */ diff --git a/doc/salome/gui/NETGENPLUGIN/input/index.doc b/doc/salome/gui/NETGENPLUGIN/input/index.doc index 074ce48..dff87a6 100644 --- a/doc/salome/gui/NETGENPLUGIN/input/index.doc +++ b/doc/salome/gui/NETGENPLUGIN/input/index.doc @@ -4,11 +4,19 @@ \b NETGENPLUGIN plugin is destined for: - Meshing 1D, 2D and 3D geometric entities. - - Faces are split into triangular elements. - - Volumes are split into tetrahedral (pyramidal) elements. + - Faces are split into triangular elements. Quad-dominant mesh is + also possible. + - Solids are split into tetrahedral elements. Pyramids are + constructed as a transition from quadrangles to tetrahedra. - Generating 3D meshes from 2D meshes, working without geometrical objects. -To manage parameters of the NETGENPLUGIN use \subpage netgen_2d_3d_hypo_page and \subpage additional_hypo_page. +To manage parameters of the NETGENPLUGIN use \subpage +netgen_2d_3d_hypo_page and \subpage additional_hypo_page. + +Native Netgen mesher usually prints a lot of trace output to the terminal +window. This output is redirected to some log file by the Plugin. It +is possible to switch off this redirection by setting up +KEEP_NETGEN_OUTPUT environment variable. Also all NETGENPLUGIN functionalities are accessible via \subpage netgenplugin_python_interface_page "NETGENPLUGIN Python interface". diff --git a/doc/salome/gui/NETGENPLUGIN/input/netgen_2d_3d_hypo.doc b/doc/salome/gui/NETGENPLUGIN/input/netgen_2d_3d_hypo.doc index d80dff0..cf9c245 100644 --- a/doc/salome/gui/NETGENPLUGIN/input/netgen_2d_3d_hypo.doc +++ b/doc/salome/gui/NETGENPLUGIN/input/netgen_2d_3d_hypo.doc @@ -11,12 +11,12 @@ meshing 2D objects). \image html netgen2d3d.png
    Hypothesis dialog boxes of Netgen 1D-2D and Netgen -1D-2D-3D algorithms are same
    + 1D-2D-3D algorithms are same
    \image html netgen2d3d_only.png
    Dialog boxes of Netgen 2D and Netgen 3D -algorithms
    + algorithms - Name - allows to define the name for the algorithm (Netgen 2D (or 3D) Parameters by default). @@ -25,19 +25,20 @@ algorithms ignored if it is more than Max Size. - Second Order - if this box is checked in, the algorithm will create second order mesh. -- Fineness - ranging from Very Coarse to Very Fine +- Fineness - ranging from Very Coarse to Very Fine allows to set the level of meshing detalization using the three parameters below. You can select \a Custom to define them manually. - Growth rate - allows to define how much the linear dimensions of -two adjacent cells can differ (i.e. 0.3 means 30%). +two adjacent cells can differ (e.g. 0.3 means 30%). - Nb. Segs per Edge - allows to define the minimum number of mesh segments in which edges will be split. This parameter is used only if Limit Size by Surface Curvature is checked. - Nb Segs per Radius - allows to define the size of mesh segments and mesh faces in which curved edges and surfaces will -be split. This parameter is used only if Limit Size by Surface -Curvature is checked. -- Limit Size by Surface Curvature - if this box is checked in, +be split. This value divided by a radius of curvature gives an element +size at a given point. This parameter is used only if Limit Size by + Surface Curvature is checked. +- Limit Size by Surface Curvature - if this box is checked in, then size of mesh segments and mesh faces on curved edges and surfaces is defined using value of Nb Segs per Radius parameter, and number of segments on straight edges is defined by values of @@ -74,13 +75,11 @@ dimension. \b 1D group allows defining the size of 1D elements in either of two ways: - Number of Segments allows specifying number of segments, that will split each edge, with equidistant distribution. -- Local Length can be applied for meshing of edges -composing geometrical object. Definition of this hypothesis -consists of setting required \b length of segments. +- Local Length defines length of segments. \b 2D group allows defining the size of 2D elements -- Length from edges if checked in, hypothesis forces building of -2D mesh elements having a length calculated as an average edge length +- Length from edges if checked in, size of +2D mesh elements is defined as an average mesh segment length for a given wire, else - Max. Element Area specifies expected maximum element area for each 2d element. @@ -91,15 +90,15 @@ wherever possible. - Length from faces if checked in, the area of sides of volumic elements will be equal to an average area of 2D elements, else - Max. Element Volume specifies expected maximum element volume -of each 3d element. +of 3d elements. \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 does not actually use Number of Segments 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 +close edges influence each other. - NETGEN additionally restricts the element size according to edge curvature. - The local size of segments influences the size of close triangles. - The order of elements and their size in the 1D mesh generated by