From e1c0323a8ce59520dbb46223112583a3fb6afc36 Mon Sep 17 00:00:00 2001 From: rnv Date: Tue, 23 Jan 2018 12:23:21 +0300 Subject: [PATCH] Update SMESH documentation: final cleanup and some corrections. --- doc/salome/gui/SMESH/doxyfile.in | 88 ---- doc/salome/gui/SMESH/doxyfile_py.in | 173 ------- .../gui/SMESH/input/1d_meshing_hypo.doc | 370 -------------- .../gui/SMESH/input/2d_meshing_hypo.doc | 146 ------ doc/salome/gui/SMESH/input/about_filters.doc | 35 -- doc/salome/gui/SMESH/input/about_hypo.doc | 66 --- doc/salome/gui/SMESH/input/about_meshes.doc | 118 ----- doc/salome/gui/SMESH/input/about_meshes.rst | 4 +- .../SMESH/input/about_quality_controls.doc | 78 --- .../SMESH/input/adding_nodes_and_elements.doc | 243 --------- .../SMESH/input/adding_quadratic_elements.doc | 85 --- .../gui/SMESH/input/additional_hypo.doc | 182 ------- doc/salome/gui/SMESH/input/area.doc | 28 - doc/salome/gui/SMESH/input/aspect_ratio.doc | 45 -- .../gui/SMESH/input/aspect_ratio_3d.doc | 40 -- .../gui/SMESH/input/bare_border_face.doc | 15 - .../gui/SMESH/input/bare_border_volumes.doc | 15 - .../gui/SMESH/input/basic_meshing_algos.doc | 87 ---- .../input/borders_at_multi_connection.doc | 15 - .../input/borders_at_multi_connection_2d.doc | 13 - .../gui/SMESH/input/building_compounds.doc | 60 --- doc/salome/gui/SMESH/input/cartesian_algo.doc | 113 ---- .../changing_orientation_of_elements.doc | 46 -- doc/salome/gui/SMESH/input/clipping.doc | 62 --- doc/salome/gui/SMESH/input/colors_size.doc | 52 -- doc/salome/gui/SMESH/input/connectivity.doc | 45 -- .../gui/SMESH/input/constructing_meshes.doc | 483 ------------------ .../SMESH/input/constructing_submeshes.doc | 159 ------ .../input/convert_to_from_quadratic_mesh.doc | 59 --- doc/salome/gui/SMESH/input/copy_mesh.doc | 54 -- .../input/create_groups_from_geometry.doc | 26 - .../gui/SMESH/input/creating_groups.doc | 145 ------ .../gui/SMESH/input/cut_mesh_by_plane.doc | 55 -- .../gui/SMESH/input/cutting_quadrangles.doc | 51 -- .../gui/SMESH/input/define_mesh_by_script.doc | 33 -- doc/salome/gui/SMESH/input/deflection_2d.doc | 25 - .../gui/SMESH/input/deleting_groups.doc | 22 - .../input/diagonal_inversion_of_elements.doc | 34 -- doc/salome/gui/SMESH/input/display_entity.doc | 23 - doc/salome/gui/SMESH/input/display_mode.doc | 23 - .../SMESH/input/double_elements_control.doc | 14 - .../gui/SMESH/input/double_nodes_control.doc | 17 - .../gui/SMESH/input/double_nodes_page.doc | 164 ------ doc/salome/gui/SMESH/input/editing_groups.doc | 49 -- doc/salome/gui/SMESH/input/editing_meshes.doc | 32 -- doc/salome/gui/SMESH/input/extrusion.doc | 181 ------- .../gui/SMESH/input/extrusion_along_path.doc | 176 ------- .../gui/SMESH/input/find_element_by_point.doc | 41 -- doc/salome/gui/SMESH/input/free_borders.doc | 17 - doc/salome/gui/SMESH/input/free_edges.doc | 15 - doc/salome/gui/SMESH/input/free_faces.doc | 18 - doc/salome/gui/SMESH/input/free_nodes.doc | 16 - .../SMESH/input/generate_flat_elements.doc | 12 - .../input/group_of_underlying_elements.doc | 51 -- .../gui/SMESH/input/grouping_elements.doc | 83 --- .../input/importing_exporting_meshes.doc | 71 --- doc/salome/gui/SMESH/input/index.doc | 52 -- doc/salome/gui/SMESH/input/introduction.rst | 2 +- doc/salome/gui/SMESH/input/length.doc | 13 - doc/salome/gui/SMESH/input/length_2d.doc | 28 - .../gui/SMESH/input/make_2dmesh_from_3d.doc | 55 -- .../gui/SMESH/input/max_element_length_2d.doc | 29 -- .../gui/SMESH/input/max_element_length_3d.doc | 29 -- .../SMESH/input/max_element_volume_hypo.doc | 16 - doc/salome/gui/SMESH/input/measurements.doc | 89 ---- .../gui/SMESH/input/merging_elements.doc | 71 --- doc/salome/gui/SMESH/input/merging_nodes.doc | 114 ----- doc/salome/gui/SMESH/input/mesh_infos.doc | 183 ------- .../gui/SMESH/input/mesh_preferences.doc | 294 ----------- .../gui/SMESH/input/mesh_through_point.doc | 47 -- doc/salome/gui/SMESH/input/minimum_angle.doc | 29 -- .../gui/SMESH/input/modifying_meshes.doc | 71 --- doc/salome/gui/SMESH/input/numbering.doc | 34 -- .../SMESH/input/over_constrained_faces.doc | 20 - .../SMESH/input/over_constrained_volumes.doc | 18 - .../gui/SMESH/input/pattern_mapping.doc | 231 --------- doc/salome/gui/SMESH/input/point_marker.doc | 53 -- doc/salome/gui/SMESH/input/prism_3d_algo.doc | 88 ---- .../gui/SMESH/input/projection_algos.doc | 116 ----- .../gui/SMESH/input/quad_from_ma_algo.doc | 36 -- doc/salome/gui/SMESH/input/quad_ijk_algo.doc | 49 -- .../gui/SMESH/input/radial_prism_algo.doc | 26 - .../input/radial_quadrangle_1D2D_algo.doc | 36 -- .../input/removing_nodes_and_elements.doc | 140 ----- doc/salome/gui/SMESH/input/reorient_faces.doc | 96 ---- doc/salome/gui/SMESH/input/revolution.doc | 112 ---- doc/salome/gui/SMESH/input/rotation.doc | 78 --- doc/salome/gui/SMESH/input/scalar_bar.doc | 44 -- doc/salome/gui/SMESH/input/scale.doc | 134 ----- .../input/segments_around_vertex_algo.doc | 22 - .../SMESH/input/selection_filter_library.doc | 281 ---------- doc/salome/gui/SMESH/input/sewing_meshes.doc | 234 --------- doc/salome/gui/SMESH/input/skew.doc | 33 -- .../gui/SMESH/input/smesh_migration.doc | 100 ---- .../gui/SMESH/input/smeshpy_interface.doc | 97 ---- doc/salome/gui/SMESH/input/smoothing.doc | 89 ---- .../SMESH/input/split_biquad_to_linear.doc | 37 -- doc/salome/gui/SMESH/input/split_to_tetra.doc | 68 --- doc/salome/gui/SMESH/input/symmetry.doc | 92 ---- doc/salome/gui/SMESH/input/taper.doc | 32 -- doc/salome/gui/SMESH/input/tools.doc | 16 - doc/salome/gui/SMESH/input/translation.doc | 74 --- doc/salome/gui/SMESH/input/transparency.doc | 11 - .../gui/SMESH/input/tui_cartesian_algo.doc | 6 - .../gui/SMESH/input/tui_creating_meshes.doc | 51 -- .../SMESH/input/tui_defining_hypotheses.doc | 134 ----- doc/salome/gui/SMESH/input/tui_filters.doc | 470 ----------------- .../input/tui_generate_flat_elements.doc | 35 -- .../gui/SMESH/input/tui_grouping_elements.doc | 55 -- .../gui/SMESH/input/tui_measurements.doc | 14 - .../gui/SMESH/input/tui_modifying_meshes.doc | 130 ----- .../gui/SMESH/input/tui_notebook_smesh.doc | 8 - .../gui/SMESH/input/tui_prism_3d_algo.doc | 9 - .../gui/SMESH/input/tui_quality_controls.doc | 76 --- .../SMESH/input/tui_transforming_meshes.doc | 59 --- .../SMESH/input/tui_use_existing_faces.doc | 14 - .../gui/SMESH/input/tui_viewing_meshes.doc | 15 - .../input/tui_work_on_objects_from_gui.doc | 34 -- .../SMESH/input/uniting_set_of_triangles.doc | 54 -- .../gui/SMESH/input/uniting_two_triangles.doc | 35 -- .../gui/SMESH/input/use_existing_algos.doc | 71 --- .../SMESH/input/using_notebook_smesh_page.doc | 42 -- .../input/using_operations_on_groups.doc | 123 ----- .../SMESH/input/viewing_meshes_overview.doc | 82 --- doc/salome/gui/SMESH/input/volume.doc | 28 - doc/salome/gui/SMESH/input/warping.doc | 43 -- doc/salome/gui/SMESH/static/footer.html | 14 - doc/salome/gui/SMESH/static/header.html.in | 23 - doc/salome/gui/SMESH/static/header_py.html.in | 24 - doc/salome/gui/SMESH/static/salome_extra.css | 29 -- doc/salome/gui/SMESH/static/switchers.js | 8 +- resources/SalomeApp.xml.in | 2 +- src/SMESH_SWIG/smeshBuilder.py | 15 +- 133 files changed, 16 insertions(+), 9679 deletions(-) delete mode 100755 doc/salome/gui/SMESH/doxyfile.in delete mode 100755 doc/salome/gui/SMESH/doxyfile_py.in delete mode 100644 doc/salome/gui/SMESH/input/1d_meshing_hypo.doc delete mode 100644 doc/salome/gui/SMESH/input/2d_meshing_hypo.doc delete mode 100644 doc/salome/gui/SMESH/input/about_filters.doc delete mode 100644 doc/salome/gui/SMESH/input/about_hypo.doc delete mode 100644 doc/salome/gui/SMESH/input/about_meshes.doc delete mode 100644 doc/salome/gui/SMESH/input/about_quality_controls.doc delete mode 100644 doc/salome/gui/SMESH/input/adding_nodes_and_elements.doc delete mode 100644 doc/salome/gui/SMESH/input/adding_quadratic_elements.doc delete mode 100644 doc/salome/gui/SMESH/input/additional_hypo.doc delete mode 100644 doc/salome/gui/SMESH/input/area.doc delete mode 100644 doc/salome/gui/SMESH/input/aspect_ratio.doc delete mode 100644 doc/salome/gui/SMESH/input/aspect_ratio_3d.doc delete mode 100644 doc/salome/gui/SMESH/input/bare_border_face.doc delete mode 100644 doc/salome/gui/SMESH/input/bare_border_volumes.doc delete mode 100644 doc/salome/gui/SMESH/input/basic_meshing_algos.doc delete mode 100644 doc/salome/gui/SMESH/input/borders_at_multi_connection.doc delete mode 100644 doc/salome/gui/SMESH/input/borders_at_multi_connection_2d.doc delete mode 100644 doc/salome/gui/SMESH/input/building_compounds.doc delete mode 100644 doc/salome/gui/SMESH/input/cartesian_algo.doc delete mode 100644 doc/salome/gui/SMESH/input/changing_orientation_of_elements.doc delete mode 100644 doc/salome/gui/SMESH/input/clipping.doc delete mode 100644 doc/salome/gui/SMESH/input/colors_size.doc delete mode 100644 doc/salome/gui/SMESH/input/connectivity.doc delete mode 100644 doc/salome/gui/SMESH/input/constructing_meshes.doc delete mode 100644 doc/salome/gui/SMESH/input/constructing_submeshes.doc delete mode 100644 doc/salome/gui/SMESH/input/convert_to_from_quadratic_mesh.doc delete mode 100644 doc/salome/gui/SMESH/input/copy_mesh.doc delete mode 100644 doc/salome/gui/SMESH/input/create_groups_from_geometry.doc delete mode 100644 doc/salome/gui/SMESH/input/creating_groups.doc delete mode 100644 doc/salome/gui/SMESH/input/cut_mesh_by_plane.doc delete mode 100644 doc/salome/gui/SMESH/input/cutting_quadrangles.doc delete mode 100644 doc/salome/gui/SMESH/input/define_mesh_by_script.doc delete mode 100644 doc/salome/gui/SMESH/input/deflection_2d.doc delete mode 100644 doc/salome/gui/SMESH/input/deleting_groups.doc delete mode 100644 doc/salome/gui/SMESH/input/diagonal_inversion_of_elements.doc delete mode 100644 doc/salome/gui/SMESH/input/display_entity.doc delete mode 100644 doc/salome/gui/SMESH/input/display_mode.doc delete mode 100644 doc/salome/gui/SMESH/input/double_elements_control.doc delete mode 100644 doc/salome/gui/SMESH/input/double_nodes_control.doc delete mode 100644 doc/salome/gui/SMESH/input/double_nodes_page.doc delete mode 100644 doc/salome/gui/SMESH/input/editing_groups.doc delete mode 100644 doc/salome/gui/SMESH/input/editing_meshes.doc delete mode 100644 doc/salome/gui/SMESH/input/extrusion.doc delete mode 100644 doc/salome/gui/SMESH/input/extrusion_along_path.doc delete mode 100644 doc/salome/gui/SMESH/input/find_element_by_point.doc delete mode 100644 doc/salome/gui/SMESH/input/free_borders.doc delete mode 100644 doc/salome/gui/SMESH/input/free_edges.doc delete mode 100644 doc/salome/gui/SMESH/input/free_faces.doc delete mode 100644 doc/salome/gui/SMESH/input/free_nodes.doc delete mode 100644 doc/salome/gui/SMESH/input/generate_flat_elements.doc delete mode 100755 doc/salome/gui/SMESH/input/group_of_underlying_elements.doc delete mode 100644 doc/salome/gui/SMESH/input/grouping_elements.doc delete mode 100644 doc/salome/gui/SMESH/input/importing_exporting_meshes.doc delete mode 100644 doc/salome/gui/SMESH/input/index.doc delete mode 100644 doc/salome/gui/SMESH/input/length.doc delete mode 100644 doc/salome/gui/SMESH/input/length_2d.doc delete mode 100644 doc/salome/gui/SMESH/input/make_2dmesh_from_3d.doc delete mode 100644 doc/salome/gui/SMESH/input/max_element_length_2d.doc delete mode 100644 doc/salome/gui/SMESH/input/max_element_length_3d.doc delete mode 100644 doc/salome/gui/SMESH/input/max_element_volume_hypo.doc delete mode 100644 doc/salome/gui/SMESH/input/measurements.doc delete mode 100644 doc/salome/gui/SMESH/input/merging_elements.doc delete mode 100644 doc/salome/gui/SMESH/input/merging_nodes.doc delete mode 100644 doc/salome/gui/SMESH/input/mesh_infos.doc delete mode 100644 doc/salome/gui/SMESH/input/mesh_preferences.doc delete mode 100644 doc/salome/gui/SMESH/input/mesh_through_point.doc delete mode 100644 doc/salome/gui/SMESH/input/minimum_angle.doc delete mode 100644 doc/salome/gui/SMESH/input/modifying_meshes.doc delete mode 100644 doc/salome/gui/SMESH/input/numbering.doc delete mode 100644 doc/salome/gui/SMESH/input/over_constrained_faces.doc delete mode 100644 doc/salome/gui/SMESH/input/over_constrained_volumes.doc delete mode 100644 doc/salome/gui/SMESH/input/pattern_mapping.doc delete mode 100644 doc/salome/gui/SMESH/input/point_marker.doc delete mode 100644 doc/salome/gui/SMESH/input/prism_3d_algo.doc delete mode 100644 doc/salome/gui/SMESH/input/projection_algos.doc delete mode 100644 doc/salome/gui/SMESH/input/quad_from_ma_algo.doc delete mode 100644 doc/salome/gui/SMESH/input/quad_ijk_algo.doc delete mode 100644 doc/salome/gui/SMESH/input/radial_prism_algo.doc delete mode 100644 doc/salome/gui/SMESH/input/radial_quadrangle_1D2D_algo.doc delete mode 100644 doc/salome/gui/SMESH/input/removing_nodes_and_elements.doc delete mode 100644 doc/salome/gui/SMESH/input/reorient_faces.doc delete mode 100644 doc/salome/gui/SMESH/input/revolution.doc delete mode 100644 doc/salome/gui/SMESH/input/rotation.doc delete mode 100755 doc/salome/gui/SMESH/input/scalar_bar.doc delete mode 100644 doc/salome/gui/SMESH/input/scale.doc delete mode 100644 doc/salome/gui/SMESH/input/segments_around_vertex_algo.doc delete mode 100644 doc/salome/gui/SMESH/input/selection_filter_library.doc delete mode 100644 doc/salome/gui/SMESH/input/sewing_meshes.doc delete mode 100644 doc/salome/gui/SMESH/input/skew.doc delete mode 100644 doc/salome/gui/SMESH/input/smesh_migration.doc delete mode 100644 doc/salome/gui/SMESH/input/smeshpy_interface.doc delete mode 100644 doc/salome/gui/SMESH/input/smoothing.doc delete mode 100644 doc/salome/gui/SMESH/input/split_biquad_to_linear.doc delete mode 100644 doc/salome/gui/SMESH/input/split_to_tetra.doc delete mode 100644 doc/salome/gui/SMESH/input/symmetry.doc delete mode 100644 doc/salome/gui/SMESH/input/taper.doc delete mode 100644 doc/salome/gui/SMESH/input/tools.doc delete mode 100644 doc/salome/gui/SMESH/input/translation.doc delete mode 100644 doc/salome/gui/SMESH/input/transparency.doc delete mode 100644 doc/salome/gui/SMESH/input/tui_cartesian_algo.doc delete mode 100644 doc/salome/gui/SMESH/input/tui_creating_meshes.doc delete mode 100644 doc/salome/gui/SMESH/input/tui_defining_hypotheses.doc delete mode 100755 doc/salome/gui/SMESH/input/tui_filters.doc delete mode 100644 doc/salome/gui/SMESH/input/tui_generate_flat_elements.doc delete mode 100644 doc/salome/gui/SMESH/input/tui_grouping_elements.doc delete mode 100644 doc/salome/gui/SMESH/input/tui_measurements.doc delete mode 100644 doc/salome/gui/SMESH/input/tui_modifying_meshes.doc delete mode 100644 doc/salome/gui/SMESH/input/tui_notebook_smesh.doc delete mode 100644 doc/salome/gui/SMESH/input/tui_prism_3d_algo.doc delete mode 100644 doc/salome/gui/SMESH/input/tui_quality_controls.doc delete mode 100644 doc/salome/gui/SMESH/input/tui_transforming_meshes.doc delete mode 100644 doc/salome/gui/SMESH/input/tui_use_existing_faces.doc delete mode 100644 doc/salome/gui/SMESH/input/tui_viewing_meshes.doc delete mode 100644 doc/salome/gui/SMESH/input/tui_work_on_objects_from_gui.doc delete mode 100644 doc/salome/gui/SMESH/input/uniting_set_of_triangles.doc delete mode 100644 doc/salome/gui/SMESH/input/uniting_two_triangles.doc delete mode 100644 doc/salome/gui/SMESH/input/use_existing_algos.doc delete mode 100644 doc/salome/gui/SMESH/input/using_notebook_smesh_page.doc delete mode 100644 doc/salome/gui/SMESH/input/using_operations_on_groups.doc delete mode 100644 doc/salome/gui/SMESH/input/viewing_meshes_overview.doc delete mode 100644 doc/salome/gui/SMESH/input/volume.doc delete mode 100644 doc/salome/gui/SMESH/input/warping.doc delete mode 100755 doc/salome/gui/SMESH/static/footer.html delete mode 100755 doc/salome/gui/SMESH/static/header.html.in delete mode 100644 doc/salome/gui/SMESH/static/header_py.html.in delete mode 100644 doc/salome/gui/SMESH/static/salome_extra.css diff --git a/doc/salome/gui/SMESH/doxyfile.in b/doc/salome/gui/SMESH/doxyfile.in deleted file mode 100755 index 2b716b2c0..000000000 --- a/doc/salome/gui/SMESH/doxyfile.in +++ /dev/null @@ -1,88 +0,0 @@ -# Copyright (C) 2007-2016 CEA/DEN, EDF R&D, OPEN CASCADE -# -# Copyright (C) 2003-2007 OPEN CASCADE, EADS/CCR, LIP6, CEA/DEN, -# CEDRAT, EDF R&D, LEG, PRINCIPIA R&D, BUREAU VERITAS -# -# This library is free software; you can redistribute it and/or -# modify it under the terms of the GNU Lesser General Public -# License as published by the Free Software Foundation; either -# version 2.1 of the License, or (at your option) any later version. -# -# This library is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -# Lesser General Public License for more details. -# -# You should have received a copy of the GNU Lesser General Public -# License along with this library; if not, write to the Free Software -# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA -# -# See http://www.salome-platform.org/ or email : webmaster.salome@opencascade.com -# - -#--------------------------------------------------------------------------- -# Project related configuration options -#--------------------------------------------------------------------------- -PROJECT_NAME = "SALOME Mesh User's Guide" -OUTPUT_DIRECTORY = SMESH -CREATE_SUBDIRS = NO -OUTPUT_LANGUAGE = English -TAB_SIZE = 5 - -#--------------------------------------------------------------------------- -# configuration options related to warning and progress messages -#--------------------------------------------------------------------------- -QUIET = NO -WARNINGS = YES - -#--------------------------------------------------------------------------- -#Input related options -#--------------------------------------------------------------------------- -INPUT = @CMAKE_CURRENT_SOURCE_DIR@/input $(GEOM_ROOT_DIR)/share/doc/salome/gui/GEOM/input -FILE_PATTERNS = *.doc -EXCLUDE = -EXCLUDE_PATTERNS = tui_*.doc -IMAGE_PATH = $(GEOM_ROOT_DIR)/share/doc/salome/gui/GEOM @CMAKE_CURRENT_SOURCE_DIR@/images -EXAMPLE_PATH = @CMAKE_SOURCE_DIR@/doc/salome/examples @CMAKE_SOURCE_DIR@/src/SMESH_SWIG - -#--------------------------------------------------------------------------- -#HTML related options -#--------------------------------------------------------------------------- -GENERATE_HTML = YES -HTML_OUTPUT = . -HTML_HEADER = @CMAKE_CURRENT_BINARY_DIR@/static/header.html -HTML_FOOTER = @CMAKE_CURRENT_SOURCE_DIR@/static/footer.html -HTML_EXTRA_STYLESHEET = @CMAKE_CURRENT_SOURCE_DIR@/static/salome_extra.css -TOC_EXPAND = YES -DISABLE_INDEX = NO -GENERATE_TREEVIEW = YES -TREEVIEW_WIDTH = 300 - -#--------------------------------------------------------------------------- -#SORT related options -#--------------------------------------------------------------------------- -SORT_GROUP_NAMES = NO - - -#--------------------------------------------------------------------------- -#LaTeX related option -#--------------------------------------------------------------------------- -GENERATE_LATEX = NO -EXTRA_PACKAGES = amsmath - -#--------------------------------------------------------------------------- -#RTF related options -#--------------------------------------------------------------------------- -GENERATE_RTF = NO - -#--------------------------------------------------------------------------- -#External reference options -#--------------------------------------------------------------------------- -TAGFILES = smeshpy_doc.tag=../SMESH/smeshpy_doc #rnv: 07.04.2011 Workaround for the doxygen 1.7.3: - #because it wrongly defines location of the html files for search. -SEARCHENGINE = YES - -#--------------------------------------------------------------------------- -#Custom commands -#--------------------------------------------------------------------------- -ALIASES += tui_script{1}="\include \1 Download this script" diff --git a/doc/salome/gui/SMESH/doxyfile_py.in b/doc/salome/gui/SMESH/doxyfile_py.in deleted file mode 100755 index 50b8dbe3e..000000000 --- a/doc/salome/gui/SMESH/doxyfile_py.in +++ /dev/null @@ -1,173 +0,0 @@ -# Copyright (C) 2007-2016 CEA/DEN, EDF R&D, OPEN CASCADE -# -# Copyright (C) 2003-2007 OPEN CASCADE, EADS/CCR, LIP6, CEA/DEN, -# CEDRAT, EDF R&D, LEG, PRINCIPIA R&D, BUREAU VERITAS -# -# This library is free software; you can redistribute it and/or -# modify it under the terms of the GNU Lesser General Public -# License as published by the Free Software Foundation; either -# version 2.1 of the License, or (at your option) any later version. -# -# This library is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -# Lesser General Public License for more details. -# -# You should have received a copy of the GNU Lesser General Public -# License along with this library; if not, write to the Free Software -# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA -# -# See http://www.salome-platform.org/ or email : webmaster.salome@opencascade.com -# - -#--------------------------------------------------------------------------- -# Project related configuration options -#--------------------------------------------------------------------------- -PROJECT_NAME = "SALOME Mesh User's Guide" -OUTPUT_DIRECTORY = SMESH -CREATE_SUBDIRS = NO -OUTPUT_LANGUAGE = English -USE_WINDOWS_ENCODING = NO -BRIEF_MEMBER_DESC = YES -REPEAT_BRIEF = YES -ALWAYS_DETAILED_SEC = YES -INLINE_INHERITED_MEMB = YES -FULL_PATH_NAMES = NO -SHORT_NAMES = NO -JAVADOC_AUTOBRIEF = YES -MULTILINE_CPP_IS_BRIEF = NO -DETAILS_AT_TOP = NO -INHERIT_DOCS = YES -SEPARATE_MEMBER_PAGES = NO -TAB_SIZE = 5 -OPTIMIZE_OUTPUT_FOR_C = YES -OPTIMIZE_OUTPUT_JAVA = YES -BUILTIN_STL_SUPPORT = NO -DISTRIBUTE_GROUP_DOC = NO -SUBGROUPING = YES - -#--------------------------------------------------------------------------- -# Build related options -#--------------------------------------------------------------------------- -EXTRACT_ALL = YES -EXTRACT_PRIVATE = YES -EXTRACT_STATIC = NO -EXTRACT_LOCAL_CLASSES = YES -EXTRACT_LOCAL_METHODS = NO -HIDE_UNDOC_MEMBERS = NO -HIDE_UNDOC_CLASSES = NO -HIDE_FRIEND_COMPOUNDS = NO -HIDE_IN_BODY_DOCS = NO -INTERNAL_DOCS = YES -CASE_SENSE_NAMES = YES -HIDE_SCOPE_NAMES = YES -SHOW_INCLUDE_FILES = YES -INLINE_INFO = YES -SORT_MEMBER_DOCS = NO -SORT_BRIEF_DOCS = NO -SORT_BY_SCOPE_NAME = NO -GENERATE_TODOLIST = YES -GENERATE_TESTLIST = YES -GENERATE_BUGLIST = YES -GENERATE_DEPRECATEDLIST= YES -MAX_INITIALIZER_LINES = 25 -SHOW_USED_FILES = NO -SHOW_DIRECTORIES = NO - -#--------------------------------------------------------------------------- -# configuration options related to source browsing -#--------------------------------------------------------------------------- -SOURCE_BROWSER = NO -INLINE_SOURCES = NO -STRIP_CODE_COMMENTS = YES -REFERENCED_BY_RELATION = NO -REFERENCES_RELATION = YES -USE_HTAGS = NO -VERBATIM_HEADERS = YES - -#--------------------------------------------------------------------------- -# configuration options related to warning and progress messages -#--------------------------------------------------------------------------- -QUIET = NO -WARNINGS = YES -WARN_IF_UNDOCUMENTED = YES -WARN_IF_DOC_ERROR = YES -WARN_NO_PARAMDOC = NO -EXCLUDE_SYMLINKS = NO -EXAMPLE_RECURSIVE = NO - -#--------------------------------------------------------------------------- -#Input related options -#--------------------------------------------------------------------------- -INPUT = tmp2/smeshBuilder.py \ - tmp2/smesh_algorithm.py \ - tmp2/StdMeshersBuilder.py \ - tmp2/smeshstudytools.py \ - tmp1/smeshBuilder.py \ - @CMAKE_CURRENT_SOURCE_DIR@/input -FILE_PATTERNS = tui_*.doc -IMAGE_PATH = @CMAKE_CURRENT_SOURCE_DIR@/images -RECURSIVE = NO -EXAMPLE_PATH = @CMAKE_SOURCE_DIR@/src/SMESH_SWIG @CMAKE_SOURCE_DIR@/doc/salome/examples - -#--------------------------------------------------------------------------- -#HTML related options -#--------------------------------------------------------------------------- -GENERATE_HTML = YES -HTML_OUTPUT = smeshpy_doc -HTML_HEADER = @CMAKE_CURRENT_BINARY_DIR@/static/header_py.html -HTML_FOOTER = @CMAKE_CURRENT_SOURCE_DIR@/static/footer.html -HTML_EXTRA_STYLESHEET = @CMAKE_CURRENT_SOURCE_DIR@/static/salome_extra.css -TOC_EXPAND = YES -DISABLE_INDEX = NO -GENERATE_TREEVIEW = YES -TREEVIEW_WIDTH = 300 - -#--------------------------------------------------------------------------- -#LaTeX related option -#--------------------------------------------------------------------------- -GENERATE_LATEX = NO - -#--------------------------------------------------------------------------- -#RTF related options -#--------------------------------------------------------------------------- -GENERATE_RTF = NO - -#--------------------------------------------------------------------------- -# Configuration options related to the dot tool -#--------------------------------------------------------------------------- -CLASS_DIAGRAMS = NO -HIDE_UNDOC_RELATIONS = NO -HAVE_DOT = YES -CLASS_GRAPH = YES -COLLABORATION_GRAPH = NO -GROUP_GRAPHS = NO -UML_LOOK = NO -TEMPLATE_RELATIONS = YES -INCLUDE_GRAPH = YES -INCLUDED_BY_GRAPH = YES -CALL_GRAPH = NO -GRAPHICAL_HIERARCHY = YES -DIRECTORY_GRAPH = YES -DOT_IMAGE_FORMAT = png -DOT_FONTNAME = Arial -DOT_PATH = -DOTFILE_DIRS = -MAX_DOT_GRAPH_WIDTH = 1024 -MAX_DOT_GRAPH_HEIGHT = 1024 -MAX_DOT_GRAPH_DEPTH = 1000 -DOT_TRANSPARENT = NO -DOT_MULTI_TARGETS = NO -GENERATE_LEGEND = NO -DOT_CLEANUP = YES - -#--------------------------------------------------------------------------- -#External reference options -#--------------------------------------------------------------------------- -GENERATE_TAGFILE = smeshpy_doc.tag -SEARCHENGINE = YES - -#--------------------------------------------------------------------------- -#Custom commands -#--------------------------------------------------------------------------- -ALIASES += tui_script{1}="\include \1 Download this script" diff --git a/doc/salome/gui/SMESH/input/1d_meshing_hypo.doc b/doc/salome/gui/SMESH/input/1d_meshing_hypo.doc deleted file mode 100644 index c4de6317c..000000000 --- a/doc/salome/gui/SMESH/input/1d_meshing_hypo.doc +++ /dev/null @@ -1,370 +0,0 @@ -/*! - -\page a1d_meshing_hypo_page 1D Meshing Hypotheses - -Basic 1D hypothesis specifies: - - -1D hypotheses can be categorized by type of nodes distribution as follows: - - -
-\anchor adaptive_1d_anchor -

Adaptive hypothesis

- -Adaptive hypothesis allows to split edges into segments with a -length that depends on the curvature of edges and faces and is limited by Min. Size -and Max Size. The length of a segment also depends on the lengths -of adjacent segments (that can't differ more than twice) and on the -distance to close geometrical entities (edges and faces) to avoid -creation of narrow 2D elements. - -\image html adaptive1d.png - -- Min size parameter limits the minimal segment size. -- Max size parameter defines the length of segments on straight edges. -- \b Deflection parameter gives maximal distance of a segment from a curved edge. - -\image html adaptive1d_sample_mesh.png "Adaptive hypothesis and NETGEN 2D algorithm - the size of mesh segments reflects the size of geometrical features" - -See Also a \ref tui_1d_adaptive "sample TUI Script" that uses Adaptive hypothesis. - -
-\anchor arithmetic_1d_anchor -

Arithmetic Progression hypothesis

- -Arithmetic Progression hypothesis allows to split edges into segments with a -length that changes in arithmetic progression (Lk = Lk-1 + d) -beginning from a given starting length and up to a given end length. - -The splitting direction is defined by the orientation of the -underlying geometrical edge. -Reverse Edges list box allows specifying the edges, for which -the splitting should be made in the direction opposite to their -orientation. This list box is usable only if a geometry object is -selected for meshing. In this case it is possible to select edges to -be reversed either directly picking them in the 3D viewer or by -selecting the edges or groups of edges in the Object Browser. Use \b -Add button to add the selected edges to the list. - -\ref reversed_edges_helper_anchor "Helper" group assists you in -defining Reversed Edges parameter. - - -\image html a-arithmetic1d.png - -\image html b-ithmetic1d.png "Arithmetic Progression hypothesis - the size of mesh elements gradually increases" - -See Also a sample TUI Script of a -\ref tui_1d_arithmetic "Defining Arithmetic Progression and Geometric Progression hypothesis" operation. - -
-\anchor geometric_1d_anchor -

Geometric Progression hypothesis

- -Geometric Progression hypothesis allows splitting edges into -segments with a length that changes in geometric progression (Lk = -Lk-1 * d) starting from a given Start Length and with a given -Common Ratio. - -The splitting direction is defined by the orientation of the -underlying geometrical edge. -Reverse Edges list box allows specifying the edges, for which -the splitting should be made in the direction opposite to their -orientation. This list box is usable only if a geometry object is -selected for meshing. In this case it is possible to select edges to -be reversed either directly picking them in the 3D viewer or by -selecting the edges or groups of edges in the Object Browser. Use \b -Add button to add the selected edges to the list. - -\ref reversed_edges_helper_anchor "Helper" group assists you in -defining Reversed Edges parameter. - -\image html a-geometric1d.png - -See Also a sample TUI Script of a -\ref tui_1d_arithmetic "Defining Arithmetic Progression and Geometric Progression hypothesis" operation. - -
-\anchor deflection_1d_anchor -

Deflection hypothesis

- -Deflection hypothesis can be applied for meshing curvilinear edges -composing your geometrical object. It defines only one parameter: the -value of deflection (or chord error). - -A geometrical edge is divided into segments of length depending on -edge curvature. The more curved the edge, the shorter the -segment. Nodes on the edge are placed so that the maximum distance -between the edge and a segment approximating a part of edge between -two nodes should not exceed the value of deflection. - -\image html a-deflection1d.png - -\image html b-flection1d.png "Deflection hypothesis - useful for meshing curvilinear edges" - -See Also a sample TUI Script of a -\ref tui_deflection_1d "Defining Deflection hypothesis" operation. - -
-\anchor average_length_anchor -

Local Length hypothesis

- -Local Length hypothesis can be applied for meshing of edges -composing your geometrical object. Definition of this hypothesis -consists of setting the \b length of segments, which will approximate these -edges, and the \b precision of rounding. - -The \b precision parameter is used to round a number of segments, -calculated by dividing the edge length by the specified \b length of -segment, to the higher integer if the \a remainder exceeds the \b precision -and to the lower integer otherwise.
-Use value 0.5 to provide rounding to the nearest integer, 1.0 for the lower integer, 0.0 for the higher integer. Default value is 1e-07. - -For example: if edge length is 10.0 and the segment \b length -is 3.0 then their division gives 10./3. = 3.33(3) and the \a remainder is 0.33(3). -If \b precision is less than 0.33(3) then the edge is divided into 3 segments. -If \b precision is more than 0.33(3) then the edge is divided into 4 segments. - - -\image html image41.gif - -\image html a-averagelength.png - -\image html b-erage_length.png "Local Length hypothesis - all 1D mesh segments are equal" - -See Also a sample TUI Script of a -\ref tui_average_length "Defining Local Length" hypothesis -operation. - -
\anchor max_length_anchor -

Max Size

-Max Size hypothesis allows splitting geometrical edges into -segments not longer than the given length. Definition of this hypothesis -consists of setting the maximal allowed \b length of segments. -Use preestimated length check box lets you use \b length -automatically calculated basing on size of your geometrical object, -namely as diagonal of bounding box divided by ten. The divider can be -changed via \ref diagonal_size_ratio_pref "Ratio Bounding Box Diagonal / Max Size" -preference parameter. -Use preestimated length check box is enabled only if the -geometrical object has been selected before hypothesis definition. - -\image html a-maxsize1d.png - -
-\anchor number_of_segments_anchor -

Number of Segments hypothesis

- -Number of Segments hypothesis can be applied for approximating -edges by a definite number of mesh segments with length depending on -the selected type of distribution of nodes. The default number of -segments can be set via -\ref nb_segments_pref "Automatic Parameters / Default Number of Segments" -preference parameter. - -The direction of the splitting is defined by the orientation of the -underlying geometrical edge. Reverse Edges list box allows to -specify the edges for which the splitting should be made in the -direction opposing to their orientation. This list box is enabled only -if the geometry object is selected for the meshing. In this case it is -possible to select edges to be reversed either by directly picking them -in the 3D viewer or by selecting the edges or groups of edges in the -Object Browser. - -\ref reversed_edges_helper_anchor "Helper" group assists you in -defining Reversed Edges parameter. - -You can set the type of node distribution for this hypothesis in the -Hypothesis Construction dialog bog : - -\image html a-nbsegments1.png - -
Equidistant Distribution - all segments will have the same -length, you define only the Number of Segments. - -
Scale Distribution - length of segments gradually changes -depending on the Scale Factor, which is a ratio of the first -segment length to the last segment length.
-Length of segments changes in geometric progression with the common -ratio (A) depending on the Scale Factor (S) and Number of -Segments (N) as follows: A = S**(1/(N-1)). For an -edge of length L, length of the first segment is -L * (1 - A)/(1 - A**N). - - -\image html a-nbsegments2.png - -
Distribution with Analytic Density - you input the formula, -which will rule the change of length of segments and the module shows -in the plot the density function curve in red and the node -distribution as blue crosses. - -\image html distributionwithanalyticdensity.png - -
-\anchor analyticdensity_anchor -The node distribution is computed so that to have the density function -integral on the range between two nodes equal for all segments. -\image html analyticdensity.png - -
Distribution with Table Density - you input a number of -pairs t - F(t), where \b t ranges from 0 to 1, and the module computes the -formula, which will rule the change of length of segments and shows -in the plot the density function curve in red and the node -distribution as blue crosses. The node distribution is computed in the -same way as for -\ref analyticdensity_anchor "Distribution with Analytic Density". You -can select the Conversion mode from \b Exponent and Cut -negative. - -\image html distributionwithtabledensity.png - -See Also a sample TUI Script of a -\ref tui_deflection_1d "Defining Number of Segments" hypothesis -operation. - -\note The plot functionality is available only if GUI module is built with Plot 2D Viewer (option SALOME_USE_PLOT2DVIEWER is ON when building GUI module). - -
-\anchor start_and_end_length_anchor -

Start and End Length hypothesis

- -Start and End Length hypothesis allows to divide a geometrical edge -into segments so that the first and the last segments have a specified -length. The length of medium segments changes with automatically chosen -geometric progression. - -The direction of the splitting is defined by the orientation of the -underlying geometrical edge. Reverse Edges list box allows to -specify the edges, for which the splitting should be made in the -direction opposing to their orientation. This list box is enabled only -if the geometry object is selected for the meshing. In this case it is -possible to select edges to be reversed either by directly picking them -in the 3D viewer or by selecting the edges or groups of edges in the -Object Browser. - -\ref reversed_edges_helper_anchor "Helper" group assists you in -defining Reversed Edges parameter. - - -\image html a-startendlength.png - -\image html b-art_end_length.png "The lengths of the first and the last segment are strictly defined" - -See Also a sample TUI Script of a -\ref tui_start_and_end_length "Defining Start and End Length" -hypothesis operation. - -
-\anchor automatic_length_anchor -

Automatic Length

- -The dialog box prompts you to define the quality of the future mesh by -only one parameter, which is \b Fineness, ranging from 0 (coarse mesh, -low number of segments) to 1 (extremely fine mesh, great number of -segments). - -\image html automaticlength.png - -Compare one and the same object (sphere) meshed with -minimum and maximum value of this parameter. - -\image html image147.gif "Example of a rough mesh at Automatic Length Fineness of 0." - -\image html image148.gif "Example of a fine mesh at Automatic Length Fineness of 1." - -
-\anchor fixed_points_1d_anchor -

Fixed Points hypothesis

- -Fixed Points hypothesis allows splitting edges through a -set of points parametrized on the edge (from 1 to 0) and a number of -segments for each interval limited by the points. - -\image html hypo_fixedpnt_dlg.png - -It is possible to check in Same Nb. Segments for all intervals -option and to define one value for all intervals. - -The splitting direction is defined by the orientation of the -underlying geometrical edge. Reverse Edges list box allows to -specify the edges for which the splitting should be made in the -direction opposite to their orientation. This list box is enabled only -if the geometrical object is selected for meshing. In this case it is -possible to select the edges to be reversed either directly picking them in -the 3D viewer or selecting the edges or groups of edges in the -Object Browser. - -\ref reversed_edges_helper_anchor "Helper" group assists in -defining Reversed Edges parameter. - - -\image html mesh_fixedpnt.png "Example of a sub-mesh on the edge built using Fixed Points hypothesis" - -See Also a sample TUI Script of a -\ref tui_fixed_points "Defining Fixed Points" hypothesis operation. - -\anchor reversed_edges_helper_anchor -

Reversed Edges Helper

- -\image html rev_edges_helper_dlg.png - -\b Helper group assists in defining Reversed Edges -parameter of the hypotheses depending on edge direction. - -Show whole geometry check-box allows seeing the whole -geometrical model in the 3D Viewer, which can help to understand the -location of a set of edges within the model. - -Propagation chains group allows defining Reversed Edges -for splitting opposite edges of quadrilateral faces in a logically -uniform direction. When this group is activated, the list is filled -with propagation chains found within the shape on which a hypothesis -is assigned. When a chain is selected in the list its edges are shown -in the Viewer with arrows, which enables choosing a common direction -for all chain edges. \b Reverse button inverts the common direction of -chain edges. \b Add button is active if some edges of a chain have a -different direction, so you can click \b Add button to add them -to Reversed Edges list. - -\image html propagation_chain.png "The whole geometry and a propagation chain" - -\note Alternatively, uniform direction of edges of one propagation -chain can be achieved by -\ref constructing_submeshes_page "definition of a sub-mesh" on one -edge of the chain and assigning a -\ref propagation_anchor "Propagation" additional hypothesis. -Orientation of this edge (and hence of all the rest edges of the chain) can be -controlled by using Reversed Edges field. - -*/ diff --git a/doc/salome/gui/SMESH/input/2d_meshing_hypo.doc b/doc/salome/gui/SMESH/input/2d_meshing_hypo.doc deleted file mode 100644 index 2005ad8d7..000000000 --- a/doc/salome/gui/SMESH/input/2d_meshing_hypo.doc +++ /dev/null @@ -1,146 +0,0 @@ -/*! - -\page a2d_meshing_hypo_page 2D Meshing Hypotheses - -- \ref max_element_area_anchor "Max Element Area" -- \ref length_from_edges_anchor "Length from Edges" -- \ref hypo_quad_params_anchor "Quadrangle parameters" - -\anchor max_element_area_anchor -

Max Element Area

- -Max Element Area hypothesis is applied for meshing of faces -composing your geometrical object. Definition of this hypothesis -consists of setting the maximum area of mesh faces, -which will compose the mesh of these faces. - -\image html a-maxelarea.png - -\n - -\image html max_el_area.png "In this example, Max. element area is very small compared to the 1D hypothesis" - -See Also a sample TUI Script of a -\ref tui_max_element_area "Maximum Element Area" hypothesis operation. - -\anchor length_from_edges_anchor -

Length from Edges

- -Length from edges hypothesis defines the maximum linear size of -mesh faces as an average length of mesh edges approximating -the meshed face boundary. - -See Also a sample TUI Script of a -\ref tui_length_from_edges "Length from Edges" hypothesis operation. - -\anchor hypo_quad_params_anchor -

Quadrangle parameters

- -\image html hypo_quad_params_dialog.png "Quadrangle parameters: Transition" - -Quadrangle parameters is a hypothesis for \ref quad_ijk_algo_page. - -Transition tab is used to define the algorithm of transition -between opposite sides of the face with a different number of -segments on them. The following types of transition -algorithms are available: - -- Standard is the default case, when both triangles and quadrangles - are possible in the transition area along the finer meshed sides. -- Triangle preference forces building only triangles in the - transition area along the finer meshed sides. - \note This type corresponds to Triangle Preference additional hypothesis, - which is obsolete now. -- Quadrangle preference forces building only quadrangles in the - transition area along the finer meshed sides. This hypothesis has a - restriction: the total quantity of segments on all - four face sides must be even (divisible by 2). - \note This type corresponds to Quadrangle Preference additional hypothesis, - which is obsolete now. -- Quadrangle preference (reversed) works in the same way and - with the same restriction as Quadrangle preference, but - the transition area is located along the coarser meshed sides. -- Reduced type forces building only quadrangles and the transition - between the sides is made gradually, layer by layer. This type has - a limitation on the number of segments: one pair of opposite sides must have - the same number of segments, the other pair must have an even total - number of segments. In addition, the number of rows - between sides with different discretization - should be enough for the transition. Following the fastest transition - pattern, three segments become one (see the image below), hence - the least number of face rows needed to reduce from Nmax segments - to Nmin segments is log3( Nmax / Nmin ). The number of - face rows is equal to the number of segments on each of equally - discretized sides. - -\image html reduce_three_to_one.png "The fastest transition pattern: 3 to 1" - -Base vertex tab allows using Quadrangle: Mapping -algorithm for meshing of trilateral faces. In this case it is -necessary to select the vertex, which will be used as the forth -degenerated side of quadrangle. - -\image html hypo_quad_params_dialog_vert.png "Quadrangle parameters: Base Vertex" - -\image html hypo_quad_params_1.png "A face built from 3 edges" - -\image html hypo_quad_params_res.png "The resulting mesh" - -This parameter can be also used to mesh a segment of a circular face. -Please, consider that there is a limitation on the selection of the -vertex for the faces built with the angle > 180 degrees (see the picture). - -\image html hypo_quad_params_2.png "3/4 of a circular face" - -In this case, selection of a wrong vertex for the Base vertex -parameter will generate a wrong mesh. The picture below -shows the good (left) and the bad (right) results of meshing. - -\image html hypo_quad_params_res_2.png "The resulting meshes" - -\image html hypo_quad_params_dialog_enf.png "Quadrangle parameters: Enforced nodes" - -Enforced nodes tab allows defining points, where the -algorithm should create nodes. There are two ways to define positions -of the enforced nodes. - -\note Enforced nodes cannot be created at \b Reduced transition type. - -Let us see how the algorithm works: - -If there are several enforced vertices, the algorithm is applied -recursively to the formed sub-domains. - -See Also a sample TUI Script of a -\ref tui_quadrangle_parameters "Quadrangle Parameters" hypothesis. - -
-*/ diff --git a/doc/salome/gui/SMESH/input/about_filters.doc b/doc/salome/gui/SMESH/input/about_filters.doc deleted file mode 100644 index 0519da4f5..000000000 --- a/doc/salome/gui/SMESH/input/about_filters.doc +++ /dev/null @@ -1,35 +0,0 @@ -/*! - -\page filters_page About filters - -\b Filters allow picking only the mesh elements satisfying to a -specific condition or a set of conditions. Filters can be used to create -or edit mesh groups, remove elements from the mesh, control -mesh quality by different parameters, etc. - -Several \ref filtering_criteria "filtering criteria" can be combined -together by using logical operators \a AND and \a OR. In addition, a -filter criterion can be reverted using logical operator \a NOT. - -Some filtering criteria use the functionality of \ref quality_page -"mesh quality controls" to filter mesh nodes / elements by specific -characteristic (Area, Length, etc). - -The functinality of mesh filters is available in both GUI and TUI -modes: - -- In GUI, filters are available in some dialog boxes via "Set Filters" -button, clicking on which opens the \ref filtering_elements "dialog box" -allowing to specify the list of filter criteria to be applied to the -current selection. See \subpage selection_filter_library_page page to -learn more about selection filters and their usage in GUI. - -- In Python scripts, filters can be used to choose only some mesh - entities (nodes or elements) for the operations, which require the - list of entities as input parameter (create/modify group, remove - nodes/elements, etc) and for the operations, which accept objects - (groups, sub-meshes) as input parameter. The page \ref - tui_filters_page provides examples of the filters usage in Python - scripts. - -*/ diff --git a/doc/salome/gui/SMESH/input/about_hypo.doc b/doc/salome/gui/SMESH/input/about_hypo.doc deleted file mode 100644 index f40555940..000000000 --- a/doc/salome/gui/SMESH/input/about_hypo.doc +++ /dev/null @@ -1,66 +0,0 @@ -/*! - -\page about_hypo_page About Hypotheses - -\b Hypotheses represent boundary conditions which will be taken into -account by meshing algorithms. -The hypotheses allow you to manage the level of detail of -the resulting mesh: when applying different hypotheses -with different parameters you can preset the quantity or size of -elements which will compose your mesh. So, it will be possible to -generate a coarse or a more refined mesh. - -The choice of a hypothesis depends on the selected algorithm. - -Hypotheses are created during creation and edition of -\ref constructing_meshes_page "meshes" and -\ref constructing_submeshes_page "sub-meshes". -Once created a hypotheses can be reused during creation and edition of -other meshes and sub-meshes. All created hypotheses and algorithms are -present in the Object Browser in \a Hypotheses and \a Algorithms -folders correspondingly. It is possible to open a dialog to modify the -parameters of a hypothesis from its context menu. This menu also -provides \b Unassign command that will unassign the hypothesis from -all meshes and sub-meshes using it. Modification of any parameter of a -hypothesis and its unassignment leads to automatic removal of elements -generated using it. - -In \b MESH there are the following Basic Hypotheses: - - -There also exist -\subpage additional_hypo_page "Additional Hypotheses": - - -*/ diff --git a/doc/salome/gui/SMESH/input/about_meshes.doc b/doc/salome/gui/SMESH/input/about_meshes.doc deleted file mode 100644 index be900bc1d..000000000 --- a/doc/salome/gui/SMESH/input/about_meshes.doc +++ /dev/null @@ -1,118 +0,0 @@ -/*! - -\page about_meshes_page About meshes - -\n \b MESH represents a discrete approximation of a subset of the -three-dimensional space by \ref mesh_entities "elementary geometrical elements". - -A SALOME study can contain multiple meshes, but they do not -implicitly compose one super-mesh, and finally each of them -can be used (e.g. exported) only individually. - -Mesh module provides several ways to create the mesh: - - -Meshes can be edited using the MESH functions destined for -\ref modifying_meshes_page "modification" of meshes. - -Attractive meshing capabilities include: -- 3D and 2D \ref viscous_layers_anchor "Viscous Layers" (boundary - layers of highly stretched elements beneficial for high quality - viscous computations); -- automatic conformal transition between tetrahedral and hexahedral - sub-meshes. - -The \b structure of a SALOME mesh is described by nodes and elements based on -these nodes. The geometry of an element is defined by the sequence of -nodes constituting it and the \ref connectivity_page "connectivity convention" -(adopted from MED library). Definition of the element basing on the elements -of a lower dimension is NOT supported. - -\anchor mesh_entities -The mesh can include the following entities: - - -Every mesh entity has an attribute associating it to a sub-shape it is -generated on (if any). The node generated on the geometrical edge or -surface in addition stores its position in parametric space of the -associated geometrical entity. This attribute is set up by meshing -algorithms generating elements and nodes. - -Mesh entities are identified by integer IDs starting from 1. -Nodes and elements are counted separately, i.e. there can be a node -and element with the same ID. - -SALOME supports elements of second order, without a central node -(quadratic triangle, quadrangle, polygon, tetrahedron, hexahedron, -pentahedron and pyramid) and with central nodes (bi-quadratic triangle -and quadrangle and tri-quadratic hexahedron).
-Quadratic mesh can be obtained in three ways: -- Using a global \ref quadratic_mesh_anchor "Quadratic Mesh" -hypothesis. (Elements with the central node are not generated in this way). -- Using \ref convert_to_from_quadratic_mesh_page operation. -- Using an appropriate option of some meshing algorithms, which -generate elements of several dimensions starting from mesh segments. -*/ diff --git a/doc/salome/gui/SMESH/input/about_meshes.rst b/doc/salome/gui/SMESH/input/about_meshes.rst index bdbbbeb4b..8b80a9ef0 100644 --- a/doc/salome/gui/SMESH/input/about_meshes.rst +++ b/doc/salome/gui/SMESH/input/about_meshes.rst @@ -4,7 +4,7 @@ About meshes ************ -**MESH** represents a discrete approximation of a subset of the three-dimensional space by `mesh_entities`_. +**MESH** represents a discrete approximation of a subset of the three-dimensional space by `elementary geometrical elements`_. A SALOME study can contain multiple meshes, but they do not implicitly compose one super-mesh, and finally each of them can be used (e.g. exported) only individually. @@ -43,7 +43,7 @@ Attractive meshing capabilities include: The **structure** of a SALOME mesh is described by nodes and elements based on these nodes. The geometry of an element is defined by the sequence of nodes constituting it and the :ref:`connectivity_page` (adopted from MED library). Definition of the element basing on the elements of a lower dimension is NOT supported. -.. _mesh_entities: +.. _elementary geometrical elements: The mesh can include the following entities: diff --git a/doc/salome/gui/SMESH/input/about_quality_controls.doc b/doc/salome/gui/SMESH/input/about_quality_controls.doc deleted file mode 100644 index 84bcf0d4d..000000000 --- a/doc/salome/gui/SMESH/input/about_quality_controls.doc +++ /dev/null @@ -1,78 +0,0 @@ -/*! - -\page quality_page About quality controls - -\n Mesh quality control in MESH is destined for visual control of the generated mesh. - -Application of a definite quality control consists of usage of the -corresponding algorithm, which calculates a value of a definite -geometric characteristic (Area, Length of edges, etc) for all meshing -elements, composing your mesh. Then all meshing elements are colored -according the calculated values. The reference between the coloring of -the meshing elements and these calculated values is shown with the -help of a scalar bar, which is displayed near the presentation of your -mesh. - -There are four types of quality controls, corresponding to node, edge, -face and volume entity type. - -Node quality controls: - - -Edge quality controls: - - -Face quality controls: - - -Volume quality controls: - - -To manage the quality controls call pop-up in the VTK viewer and select "Controls" sub-menu -\image html controls_popup.png - - - - -*/ diff --git a/doc/salome/gui/SMESH/input/adding_nodes_and_elements.doc b/doc/salome/gui/SMESH/input/adding_nodes_and_elements.doc deleted file mode 100644 index 793525c02..000000000 --- a/doc/salome/gui/SMESH/input/adding_nodes_and_elements.doc +++ /dev/null @@ -1,243 +0,0 @@ -/*! - -\page adding_nodes_and_elements_page Adding nodes and elements - -\n In MESH you can add to your mesh different elements such as: - - - -The convention of nodal connectivity of elements used in SALOME is -the MED library convention. You can consult the description of -nodal connectivity of elements in the documentation on MED library or -\ref connectivity_page "here". - -To add a node or an element to your mesh: -
    -
  1. Select your mesh in the Object Browser or in the 3D viewer.
    2. - -
  2. From the \b Modification menu choose the \b Add item, the - following associated sub-menu will appear:
    3. - - \image html image152.png - -From this sub-menu select the type of element which you would like to add to your mesh. - -\note All dialogs for new node or element adding to the mesh provide -the possibility to automatically add -a node or element to the specified group or to create it anew using -Add to group box, that allows choosing an existing group for -the created node or element or giving the name to a new group. By -default, the Add to group check box is switched off. If the user -switches this check box on, the combo box listing all currently -existing groups of the corresponding type becomes available. By -default, no group is selected. In this case, when the user presses -Apply or Apply & Close button, the warning message box -informs the user about the necessity to input new group name. The -combo box lists groups of all the -\ref grouping_elements_page "three types": both -\ref standalone_group "standalone groups", -\ref group_on_filter "groups on filter", and -\ref group_on_geom "groups on geometry". If the user chooses a -group on geometry or on filter, he is warned and proposed to -convert this group to standalone. -If the user rejects conversion operation, it is cancelled and -a new node/element is not created! - -
- -See Also sample TUI Scripts of -\ref tui_adding_nodes_and_elements "Adding Nodes and Elements" -operations. - -
-\anchor adding_nodes_anchor -

Adding nodes

- -\image html addnode.png - -In this dialog box set coordinates for your node in the \b Coordinates -set of fields and click the \b Apply or Apply and Close button. Your node will be -created: - -\image html add_node.png - -
-\anchor adding_0delems_anchor -

Adding 0D elements

- -\image html add0delement.png - -In this dialog box specify nodes which will form your 0D elements by -selecting them in the 3D viewer. Activate Allow duplicate - elements to get several 0D elements on a node. Click the \b Apply or -Apply and Close button. Your 0D elements will be created: - -\image html add_0delement.png - -\anchor adding_0delems_on_all_nodes_anchor -

Making 0D elements on Element Nodes

- -There is another way to create 0D elements. It is possible to create -0D elements on all nodes of the selected mesh, sub-mesh, or a group of elements or nodes. - -\image html dlg_0D_on_all_nodes.png - -In this dialog - - - -\anchor adding_balls_anchor -

Adding ball elements

- -\image html addball.png - -In this dialog box specify the nodes, which will form your ball elements, -either by selecting them in the 3D viewer or by manually entering their IDs, -specify the ball diameter and click the \b Apply or Apply and - Close button. - -\image html add_ball.png - -
-\anchor adding_edges_anchor -

Adding edges

- -\image html addedge.png - -In this dialog box specify the nodes which will form your edge by -selecting them in the 3D viewer with pressed Shift button and click -the \b Apply or Apply and Close button. Your edge will be created: - -\image html add_edge.png - -
-\anchor adding_triangles_anchor -

Adding triangles

- -\image html addtriangle.png - -In this dialog box specify the nodes which will form your triangle by -selecting them in the 3D viewer with pressed Shift button and click -the \b Apply or Apply and Close button. Your triangle will be created: - -\image html add_triangle.png - -
-\anchor adding_quadrangles_anchor -

Adding quadrangles

- -\image html addquadrangle.png - -In this dialog box specify the nodes which will form your quadrangle -by selecting them in the 3D viewer with pressed Shift button and click -the \b Apply or Apply and Close button. Your quadrangle will be created: - -\image html add_quadrangle.png - -
-\anchor adding_polygons_anchor -

Adding polygons

- -\image html addpolygon.png - -In this dialog box specify the nodes which will form your polygon by -selecting them in the 3D viewer with pressed Shift button and click -the \b Apply or Apply and Close button. - -\image html add_polygone.png - -
-\anchor adding_tetrahedrons_anchor -

Adding tetrahedrons

- -\image html addtetrahedron.png - -In this dialog box specify the nodes which will form your tetrahedron -by selecting them in the 3D viewer with pressed Shift button and click -the \b Apply or Apply and Close button. Your tetrahedron will be created: - -\image html image70.jpg - -
-\anchor adding_hexahedrons_anchor -

Adding hexahedrons

- -\image html addhexahedron.png - -In this dialog box specify the nodes which will form your hexahedron -by selecting them in the 3D viewer with pressed Shift button and click -the \b Apply or Apply and Close button. Your hexahedron will be created: - -\image html image71.jpg - -
-\anchor adding_octahedrons_anchor -

Adding hexagonal prism

- -In the Add Hexagonal Prism dialog box specify the nodes which will -form your hexagonal prism by selecting them in the 3D viewer with pressed Shift button and click -the \b Apply or Apply and Close button. Your hexagonal prism will be created: - -\image html image_octa12.png - -
-\anchor adding_polyhedrons_anchor -

Adding polyhedrons

- -\image html a-createpolyhedralvolume.png - -There are two different ways to add polyhedral volumes. -\n If you select \b Node as Elements Type you will specify the -nodes which will form the faces of your polyhedron by selecting the -nodes in the 3D viewer with pressed Shift button and clicking the \b -Add button to add the face in the list of Faces by Nodes, which will -form your polyhedron. Note, that it could be very useful to toggle -Polyhedron Preview checkbox to see the results of your selection. -\n The second way is somewhat simpler, however, there are cases when -it does not provide you with the necessary level of precision. If you -select \b Face as Elements Type, you will be able to select the faces -which will form your polyhedron in the 3D viewer with pressed Shift -button. If you've managed to obtain the necessary result, click the -\b Apply or Apply and Close button. Your polyhedron will be created: - -\image html add_polyhedron.png - -*/ diff --git a/doc/salome/gui/SMESH/input/adding_quadratic_elements.doc b/doc/salome/gui/SMESH/input/adding_quadratic_elements.doc deleted file mode 100644 index 222774cb9..000000000 --- a/doc/salome/gui/SMESH/input/adding_quadratic_elements.doc +++ /dev/null @@ -1,85 +0,0 @@ -/*! - -\page adding_quadratic_elements_page Adding Quadratic Elements - -\n MESH module allows you to work with Quadratic Elements. - -Quadratic elements are defined by the same corner nodes as the -corresponding linear ones, but in addition they have \a midside nodes -located between the corner nodes on element sides. - -If a quadratic 2D element has an additional node at the -element center, it is a bi-quadratic element (both TRIA7 and -QUAD9 elements are supported). If a quadratic hexahedral element has 7 -additional nodes: at the element center and at the center of each -side, it is a tri-quadratic element (or HEXA27). - -The convention of nodal connectivity of elements used in SALOME is -the MED library convention. You can consult the description of nodal -connectivity of elements in the documentation on MED library or -\ref connectivity_page "here". - -There are several ways to create quadratic elements in your mesh: -- manually (this way is described below); -- use \ref quadratic_mesh_anchor "Quadratic Mesh" hypothesis to -generate a quadratic mesh on your geometry; -- convert an existing linear mesh to a quadratic one -(see \ref convert_to_from_quadratic_mesh_page). - -To add a quadratic element to your mesh: -
    -
  1. Select your mesh in the Object Browser or in the 3D viewer.
    2. - -
  2. From the \b Modification menu choose the \b Add item and select -one of the following: - -\image html image152.png - -\note All dialogs for adding quadratic element to the mesh -provide the possibility to automatically add an element -to the specified group or to create the group anew using -Add to group box, that allows choosing an existing group for -the created node or element or giving the name to a new group. By -default, the Add to group check box is switched off. If the user -switches this check box on, the combo box listing all currently -existing groups of the corresponding type becomes available. By -default, no group is selected. In this case, when the user presses -Apply or Apply & Close button, the warning message box -informs the user about the necessity to input a new group name. The -combo box lists groups of all the -\ref grouping_elements_page "three types": both -\ref standalone_group "standalone groups", -\ref group_on_filter "groups on filter", and -\ref group_on_geom "groups on geometry". If the user chooses a -group on geometry or on filter, he is warned and proposed to -convert this group to standalone. -If the user rejects conversion operation, it is cancelled and -a new quadratic element is not created. - - -To create any Quadratic Element specify the nodes which will -form your element by selecting them in the 3D viewer with pressed -Shift button and click \a Selection button to the right of -Corner Nodes label. Their numbers will appear in the dialog box -as Corner Nodes (alternatively you can just input numbers in -this field without selection; note that to use this way the mesh -should be selected before invoking this operation). The edges formed -by the corner nodes will appear in the table. To define the middle -nodes for each edge, double-click on the respective field and input -the number of the node (or pick the node in the viewer). For -bi-quadratic and tri-quadratic elements, your also need to specify -central nodes. -As soon as all needed nodes are specified, a preview of a new -quadratic element will be displayed in the 3D viewer. Then -you will be able to click \b Apply or Apply and Close button to -add the element to the mesh. - -\image html aqt.png - -\b Reverse button reverses the element. -
    3. -
- - - -*/ diff --git a/doc/salome/gui/SMESH/input/additional_hypo.doc b/doc/salome/gui/SMESH/input/additional_hypo.doc deleted file mode 100644 index a41cbb40b..000000000 --- a/doc/salome/gui/SMESH/input/additional_hypo.doc +++ /dev/null @@ -1,182 +0,0 @@ -/*! - -\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. - -An Additional Hypothesis can be defined in the same way as any -main hypothesis in \ref create_mesh_anchor "Create Mesh" or -\ref constructing_submeshes_page "Create Sub-Mesh" dialog. - -The following additional hypothesis are available: - - - -\anchor propagation_anchor -

Propagation of 1D Hypothesis on opposite edges

- -Propagation of 1D Hypothesis on opposite edges allows to mesh -opposite sides of a quadrangle face and other adjacent quadrangles, -using the same hypothesis assigned to only one edge.
-Thus you define a sub-mesh on the edge where you define 1D meshing -parameters and the \b Propagation hypothesis. These local meshing -parameters will be propagated via opposite sides of quadrangles to the -whole geometry, and this propagation stops at an edge with other local -meshing parameters. - -This hypothesis can be taken into account by -\ref a1d_algos_anchor "Wire Discretization" and -\ref a1d_algos_anchor "Composite Side Discretization" algorithms. - -See Also a sample TUI Script of a -\ref tui_propagation "Propagation hypothesis" operation - -\anchor propagofdistribution_anchor -

Propagation of Node Distribution on Opposite Edges

- -Propagation of Node Distribution on Opposite Edges allows to propagate -distribution of nodes onto an opposite edge. If a local hypothesis and -propagation are defined on an edge of a quadrangular face, the -opposite edge will have the same number of nodes and the same -relations between segment lengths, unless another hypothesis -has been locally defined on the opposite edge. - -This hypothesis can be taken into account by -\ref a1d_algos_anchor "Wire Discretization" and -\ref a1d_algos_anchor "Composite Side Discretization" algorithms. - -See Also a sample TUI Script of a -\ref tui_propagation "Propagation hypothesis" operation - -\anchor viscous_layers_anchor -

Viscous Layers and Viscous Layers 2D

- -Viscous Layers and Viscous Layers 2D additional -hypotheses can be used by several 3D algorithms, for example -Hexahedron(i,j,k), or 2D algorithms, for example Triangle -(MEFISTO), correspondingly. These hypotheses allow creation of layers -of highly stretched elements, prisms in 3D and quadrilaterals in 2D, -near mesh boundary, which is beneficial for high quality viscous -computations. - -\image html viscous_layers_hyp.png - -\image html viscous_layers_2d_hyp.png - - - -\image html viscous_layers_mesh.png A group containing viscous layer prisms. - -
See also a sample TUI script of a \ref tui_viscous_layers -"Viscous layers construction". - - -\anchor quadratic_mesh_anchor -

Quadratic Mesh

- -Quadratic Mesh hypothesis allows to build a quadratic mesh (in which -links between element nodes are not straight but curved lines due to -presence of an additional mid-side node). - -This 1D hypothesis can be taken into account by -\ref a1d_algos_anchor "Wire Discretization" and -\ref a1d_algos_anchor "Composite Side Discretization" algorithms. To -create a quadratic mesh assign this hypothesis at -\ref constructing_meshes_page "mesh construction". - -See \ref adding_quadratic_elements_page -for more information about quadratic meshes. - - -\anchor quadrangle_preference_anchor -

Quadrangle Preference

- -This additional hypothesis can be used together with 2D triangulation algorithms. -It allows 2D triangulation algorithms to build quadrangular meshes. - -Usage of this hypothesis with "Quadrangle: Mapping" meshing algorithm -is obsolete since introducing -\ref hypo_quad_params_anchor "Quadrangle parameters" hypothesis. -Usage of this hypothesis with "Quadrangle: Mapping" meshing algorithm -corresponds to specifying "Quadrangle Preference" transition type of -\ref hypo_quad_params_anchor "Quadrangle parameters" hypothesis. -\note "Quadrangle Preference" transition type can be used only if the -total quantity of segments on all sides of the face is even (divisible -by 2), else "Standard" transition type is used. -*/ diff --git a/doc/salome/gui/SMESH/input/area.doc b/doc/salome/gui/SMESH/input/area.doc deleted file mode 100644 index 765d4d4f4..000000000 --- a/doc/salome/gui/SMESH/input/area.doc +++ /dev/null @@ -1,28 +0,0 @@ -/*! - -\page area_page Area - -\n \b Area mesh quality control is based on the algorithm of area -calculation of mesh faces. - -To apply the Area quality control to your mesh: -
    -
  1. Display your mesh in the viewer.
    2. - -
  2. Choose Controls > Face Controls > Area or click -"Area" button. - -\image html image35.png -
    "Area" button
    - -Your mesh will be displayed in the viewer with its faces colored -according to the applied mesh quality control criterion: - -\image html image5.jpg -
    3. -
- -
See Also a sample TUI Script of an -\ref tui_area "Area quality control" operation. - -*/ \ No newline at end of file diff --git a/doc/salome/gui/SMESH/input/aspect_ratio.doc b/doc/salome/gui/SMESH/input/aspect_ratio.doc deleted file mode 100644 index af1057ddd..000000000 --- a/doc/salome/gui/SMESH/input/aspect_ratio.doc +++ /dev/null @@ -1,45 +0,0 @@ -/*! - -\page aspect_ratio_page Aspect Ratio - -\n The Aspect Ratio quality criterion for mesh elements reveals -the degree of conformity of a mesh element to the regular element of -its type (with all edges having the same length). - - - -- The Aspect Ratio of a \b triangle 2D element consisting of 3 -nodes is calculated by the formula: - -\image html formula4.png - -- The Aspect Ratio of a \b quadrangle 2D element consisting of 4 -nodes is calculated using The Verdict Geometric Quality Library -available within VTK. The calculation formula is: - -\image html formula5.png - -To apply the Aspect Ratio quality criterion to your mesh: -
    -
  1. Display your mesh in the viewer.
    2. - -
  2. Choose Controls > Face Controls > Aspect Ratio or click -"Aspect Ratio" button in the toolbar. - -
    -\image html image37.png -"Aspect Ratio" button -
    - -Your mesh will be displayed in the viewer with its elements colored -according to the applied mesh quality control criterion: - -\image html image94.jpg -
    3. -
- -
See Also a sample TUI Script of an -\ref tui_aspect_ratio "Aspect Ratio quality control" operation. - -*/ - diff --git a/doc/salome/gui/SMESH/input/aspect_ratio_3d.doc b/doc/salome/gui/SMESH/input/aspect_ratio_3d.doc deleted file mode 100644 index 2ea62f1f8..000000000 --- a/doc/salome/gui/SMESH/input/aspect_ratio_3d.doc +++ /dev/null @@ -1,40 +0,0 @@ -/*! - -\page aspect_ratio_3d_page Aspect ratio 3D - -\n The Aspect Ratio 3D mesh quality criterion calculates the same -parameter as the \ref aspect_ratio_page "Aspect ratio" criterion, but -it is applied to 3D mesh elements: tetrahedrons, pentahedrons, -hexahedrons, etc. - -- The Aspect Ratio of a \b tetrahedron 3D element defined by -vertices {a,b,c,d } is calculated by the formula: - -\image html formula1.png - -- Other element types like polyhedron, pentahedron and hexahedron use - the following formula: - -\image html formula2.png - -To apply the Aspect Ratio 3D quality criterion to your mesh: -
    -
  1. Display your mesh in the viewer.
    2. - -
  2. Choose Controls > Volume Controls > Aspect Ratio 3D or click -"Aspect Ratio 3D" button of the toolbar. - -\image html image144.png -
    "Aspect Ratio 3D" button
    - -Your mesh will be displayed in the viewer with its elements colored -according to the applied mesh quality control criterion: - -\image html image86.jpg -
    3. -
- -
See Also a sample TUI Script of a -\ref tui_aspect_ratio_3d "Aspect Ratio 3D quality control" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/bare_border_face.doc b/doc/salome/gui/SMESH/input/bare_border_face.doc deleted file mode 100644 index 2115d3249..000000000 --- a/doc/salome/gui/SMESH/input/bare_border_face.doc +++ /dev/null @@ -1,15 +0,0 @@ -/*! - -\page bare_border_faces_page Bare border faces - -This mesh quality control highlights the faces having the border not -shared with other faces (free border) and missing an edge based on -nodes of the free border. The faces with bare border are shown with a -color different from the color of shared faces. - -\image html bare_border_faces_smpl.png - -\sa A sample TUI Script making a group of faces highlighted in the -picture is \ref tui_bare_border_faces "Bare border faces Control". - -*/ diff --git a/doc/salome/gui/SMESH/input/bare_border_volumes.doc b/doc/salome/gui/SMESH/input/bare_border_volumes.doc deleted file mode 100644 index d0dd894ba..000000000 --- a/doc/salome/gui/SMESH/input/bare_border_volumes.doc +++ /dev/null @@ -1,15 +0,0 @@ -/*! - -\page bare_border_volumes_page Bare border volumes - -This mesh quality control highlights the volumes having the border not -shared with other volumes (free border) and missing a face based on -nodes of the free border. The volumes with bare border are shown with a -color different from the color of shared volumes. - -\image html bare_border_volumes_smpl.png - -\sa A sample TUI Script making a group of volumes highlighted in the -picture is \ref tui_bare_border_volumes "Bare border volumes Control". - -*/ diff --git a/doc/salome/gui/SMESH/input/basic_meshing_algos.doc b/doc/salome/gui/SMESH/input/basic_meshing_algos.doc deleted file mode 100644 index 08841b063..000000000 --- a/doc/salome/gui/SMESH/input/basic_meshing_algos.doc +++ /dev/null @@ -1,87 +0,0 @@ -/*! - -\page basic_meshing_algos_page Basic meshing algorithms - -\n The MESH module contains a set of meshing algorithms, which are -used for meshing entities (1D, 2D, 3D sub-shapes) composing -geometrical objects. - -An algorithm represents either an implementation of a certain meshing -technique or an interface to the whole meshing program generating elements -of several dimensions. - - - -Some 3D meshing algorithms, such as Hexahedron(i,j,k) also can -generate 3D meshes from 2D meshes, working without geometrical -objects. - -There is also a number of more specific algorithms: - - -\ref constructing_meshes_page "Constructing meshes" page describes in -detail how to apply meshing algorithms. - -
See Also a sample TUI Script of a -\ref tui_defining_meshing_algos "Define Meshing Algorithm" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/borders_at_multi_connection.doc b/doc/salome/gui/SMESH/input/borders_at_multi_connection.doc deleted file mode 100644 index 46fbc6047..000000000 --- a/doc/salome/gui/SMESH/input/borders_at_multi_connection.doc +++ /dev/null @@ -1,15 +0,0 @@ -/*! - -\page borders_at_multi_connection_page Borders at multi-connection - -\n This mesh quality control highlights segments according to the number -of elements, faces and volumes, to which the segment belongs. - -\image html image151.gif - -In this picture the borders at multi-connection are displayed in blue. - -
See Also a sample TUI Script of a -\ref tui_borders_at_multiconnection "Borders at Multi-Connection quality control" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/borders_at_multi_connection_2d.doc b/doc/salome/gui/SMESH/input/borders_at_multi_connection_2d.doc deleted file mode 100644 index 77a439130..000000000 --- a/doc/salome/gui/SMESH/input/borders_at_multi_connection_2d.doc +++ /dev/null @@ -1,13 +0,0 @@ -/*! - -\page borders_at_multi_connection_2d_page Borders at multi-connection 2D - -\n This mesh quality control highlights borders of faces (links -between nodes) according to the number of faces, to which the link belongs. - -\image html image127.gif - -
See Also a sample TUI Script of a -\ref tui_borders_at_multiconnection_2d "Borders at Multi-Connection quality control" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/building_compounds.doc b/doc/salome/gui/SMESH/input/building_compounds.doc deleted file mode 100644 index ce5f3ce50..000000000 --- a/doc/salome/gui/SMESH/input/building_compounds.doc +++ /dev/null @@ -1,60 +0,0 @@ -/*! - -\page building_compounds_page Building Compound Meshes - -\n Compound Mesh is a combination of several meshes. All elements and -groups present in input meshes are present in the compound -mesh. However, it does not use geometry or hypotheses of the initial meshes. -The links between the input meshes and the compound mesh are not -supported, consequently the modification of an input mesh does not lead to -the update of the compound mesh. - -To Build a compound mesh: - -\par -From the \b Mesh menu select Build Compound or click "Build - Compound Mesh" button in the toolbar. - -\image html image161.png -
"Build Compound Mesh" button
- -\par -The following dialog box will appear: - -\image html buildcompound.png - -\par - - -\image html image160.gif "Example of a compound of two meshed cubes" - -See Also a sample -\ref tui_building_compound "TUI Example of building compounds." -*/ diff --git a/doc/salome/gui/SMESH/input/cartesian_algo.doc b/doc/salome/gui/SMESH/input/cartesian_algo.doc deleted file mode 100644 index 63b81ffc4..000000000 --- a/doc/salome/gui/SMESH/input/cartesian_algo.doc +++ /dev/null @@ -1,113 +0,0 @@ -/*! - -\page cartesian_algo_page Body Fitting 3D meshing algorithm - -Body Fitting algorithm generates hexahedrons of a Cartesian grid in -the internal part of geometry and polyhedrons and other types of -elements at the intersection of Cartesian cells with the geometrical -boundary. - -\image html cartesian3D_sphere.png "A sphere meshed by Body Fitting algorithm" - -The meshing algorithm is as follows. -
    -
  1. Lines of a Cartesian structured grid defined by -\ref cartesian_hyp_anchor "Body Fitting Parameters" hypothesis are -intersected with the geometry boundary, thus nodes lying on the -boundary are found. This step also allows finding out for each node of -the Cartesian grid if it is inside or outside the geometry.
    2. -
  2. For each cell of the grid, check how many of its nodes are outside -of the geometry boundary. Depending on a result of this check -
      -
    • skip a cell, if all its nodes are outside
      • -
    • skip a cell, if it is too small according to Size - Threshold parameter
      • -
    • add a hexahedron in the mesh, if all nodes are inside
      • -
    • add a polyhedron or another cell type in the mesh, if some -nodes are inside and some outside.
      • -
    -
    3. -
-To apply this algorithm when you define your mesh, select Body - Fitting in the list of 3D algorithms and add Body Fitting - Parameters hypothesis. The following dialog will appear: - -
-\anchor cartesian_hyp_anchor -

Body Fitting Parameters hypothesis

- -\image html cartesian3D_hyp.png "Body Fitting Parameters hypothesis dialog" - -This dialog allows to define - - -
-See Also a sample TUI Script of a -\ref tui_cartesian_algo "Usage of Body Fitting algorithm". - -*/ diff --git a/doc/salome/gui/SMESH/input/changing_orientation_of_elements.doc b/doc/salome/gui/SMESH/input/changing_orientation_of_elements.doc deleted file mode 100644 index 7253782c1..000000000 --- a/doc/salome/gui/SMESH/input/changing_orientation_of_elements.doc +++ /dev/null @@ -1,46 +0,0 @@ -/*! - -\page changing_orientation_of_elements_page Changing orientation of elements - -\n Orientation of an element is changed by changing the order of its nodes. - -To change orientation of elements: -
    -
  1. Select a mesh (and display it in the 3D Viewer if you are going to pick elements by mouse).
    2. -
  2. In the \b Modification menu select the \b Orientation item or click - Orientation button in the toolbar. - -
    -\image html image79.png -"Orientation" button -
    - - The following dialog box will appear: - -
    -\image html orientaation1.png -
    -
      -
    • Select type of elements to reorient: \b Face or \b Volume.
      • -
    • The main list shall contain the elements which will be - reoriented. You can click on an element in the 3D viewer and it will - be highlighted. After that click the \b Add button and the ID of this - element will be added to the list. To remove a selected element or - elements from the list click the \b Remove button. The \b Sort button - allows to sort the list of elements IDs. The Set filter button - allows to apply a definite \ref filtering_elements "filter" to the - selection of elements.
      • -
    • Apply to all radio button allows to modify the orientation - of all elements of the selected mesh.
      • -
    • Select from set of fields allows to choose a sub-mesh or an - existing group whose elements can be added to the list.
      • -
    - -
    3. -
  3. Click the \b Apply or Apply and Close button to confirm the operation.
    4. -
- -
See Also a sample TUI Script of a -\ref tui_orientation "Change Orientation" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/clipping.doc b/doc/salome/gui/SMESH/input/clipping.doc deleted file mode 100644 index f28b88001..000000000 --- a/doc/salome/gui/SMESH/input/clipping.doc +++ /dev/null @@ -1,62 +0,0 @@ -/*! - -\page clipping_page Clipping - -\b Clipping allows creating cross-section views (clipping planes) -of your mesh. - -It is available as a sub-item in the context menu of an active mesh. - -To create a clipping plane, click on the \b New button in the dialog and choose how it is defined: by \b Absolute or \b Relative coordinates. - -Absolute Coordinates - -\image html Clipping_Absolute.png - -- Base point - allows defining the coordinates of the base - point for the clipping plane. - - - Reset - returns the base point to coordinate origin. - -- Direction - allows defining the orientation of the - clipping plane. - - - Invert - allows selecting, which part of the object will be - removed and which will remain after clipping. - -Relative mode - -\image html Clipping_Relative.png - -- \b Orientation ( ||X-Y, ||X-Z or ||Y-Z). - -- \b Distance between the opposite extremities of the boundary box of -selected objects, if it is set to 0.5 the boundary box is split in two halves. - -- \b Rotation (in angle degrees) around X (Y to Z) and around -Y (X to Z) (depending on the chosen Orientation) - -\image html before_clipping_preview.png "The preview plane and the cut object" - -The other parameters are available in both modes : - -- OpenGL clipping check-box allows choosing OpenGL native clipping, which clips the whole presentation. If it is unchecked, the clipping is done on the dataset i.e. only the visibility of separate mesh cells is changed (see the examples). -- The List contains Meshes, sub-meshes and groups to which the cross-section will be applied. -- Select all check-box allows to selecting and deselecting all available objects at once. -- Show preview check-box shows the clipping plane in the 3D Viewer. -- Auto Apply check-box shows button is on, you can preview the -cross-section in the 3D Viewer. - -It is also possible to interact with the clipping plane directly in 3D -view using the mouse. - -To get a new object from \b Clipping, click \b Apply. - -Examples: - -\image html dataset_clipping.png "The cross-section using dataset" - -\image html opengl_clipping.png "The OpenGL cross-section" - - -*/ diff --git a/doc/salome/gui/SMESH/input/colors_size.doc b/doc/salome/gui/SMESH/input/colors_size.doc deleted file mode 100644 index c8be2278e..000000000 --- a/doc/salome/gui/SMESH/input/colors_size.doc +++ /dev/null @@ -1,52 +0,0 @@ -/*! - -\page colors_size_page Properties - -\image html colors_size.png - -Using this dialog you can customize different properties of the mesh visualization -parameters. - -The GUI elements in the "Properties" dialog box are grouped according -to the entity types of mesh data. If some data entities are not -present in the mesh object, the corresponding GUI elements are not -shown. - -- \b Nodes: - - \b Color - color of nodes. - - \b Type and \b Scale - these options allow changing the nodes - representation (see \subpage point_marker_page "Point Marker" page - for more details). -- Edges / wireframe: - - \b Color - color of element borders in wireframe mode. - - \b Width - width of lines (edges and borders of elements - in wireframe mode). -- \b Faces: - - \b Front - surface color of face elements (seen in shading mode). - - \b Back - backside surface color of face elements. Use the slider to - select this color generated on the base of the \b Face color by - changing its brightness and saturation. -- \b Volumes: - - \b Normal - surface color of normal volume elements (seen in shading mode). - - \b Reversed - surface color of volume elements. Use the slider to - select this color generated on the base of the \b Normal color by - changing its brightness and saturation. -- \b Outlines: - - \b Color - color of element borders in shading mode. - - \b Width - width of outlines (borders of elements - in shading mode). -- 0D elements: - - \b Color - color of 0D elements. - - \b Size - size of 0D elements. -- \b Balls: - - \b Color - color of discrete ball elements. - - \b Size - size of discrete ball elements. - - \b Scale - scale factor of discrete ball elements. -- Orientation vectors: - - \b Color - color of orientation vectors. - - \b Scale - size of orientation vectors. - - 3D vectors - allows to choose between 2D planar and 3D vectors. -- Shrink coef. - relative space of elements compared to gaps between - them in shrink mode. - -*/ diff --git a/doc/salome/gui/SMESH/input/connectivity.doc b/doc/salome/gui/SMESH/input/connectivity.doc deleted file mode 100644 index 28c863ff5..000000000 --- a/doc/salome/gui/SMESH/input/connectivity.doc +++ /dev/null @@ -1,45 +0,0 @@ -/*! -\page connectivity_page Nodal connectivity of elements - -The following images show order of nodes in correctly defined elements. - - - - - - - - - - - - -
Edge (segment): linear and quadratic
- \image html connectivity_edge.png
Triangle: linear, quadratic and bi-quadratic
- \image html connectivity_tria.png
Quadrangle: linear, quadratic and bi-quadratic
- \image html connectivity_quad.png
Polygon: linear and quadratic
- \image html connectivity_polygon.png
Tetrahedron: linear and quadratic
- \image html connectivity_tetra.png
Hexahedron: linear, quadratic and tri-quadratic
- \image html connectivity_hexa.png
Pentahedron: linear and quadratic
- \image html connectivity_penta.png
Pyramid: linear and quadratic
- \image html connectivity_pyramid.png
Hexagonal prism
- \image html connectivity_hex_prism.png
Polyhedron is defined by
    -
  • a sequence of nodes defining all facets
    • -
  • a sequence of number of nodes per facet
    • -
- \b Nodes:
- Node1_of_Facet1, Node2_of_Facet1, ..., NodeN_of_Facet1,
- Node1_of_Facet2, Node2_of_Facet2, ..., NodeN_of_Facet2,
- Node1_of_FacetM, Node2_of_FacetM, ..., NodeN_of_FacetM
- \b Quantity of nodes per facet:
- NbNodes_in_Facet1, NbNodes_in_Facet2, ..., NbNodes_in_FacetM - - For example the polyhedron shown in the image below is defined by nodes
- [ 1,2,3, 1,4,5,2, 2,5,6,3, 3,6,4,1, 4,7,9,5, 5,9,8,6, 6,8,7,4, 7,8,9 ]
- and quantities [ 3, 4, 4, 4, 4, 4, 4, 3 ] - \image html connectivity_polyhedron.png - Order of nodes of a facet must assure outward direction of its normal. -
- - -*/ diff --git a/doc/salome/gui/SMESH/input/constructing_meshes.doc b/doc/salome/gui/SMESH/input/constructing_meshes.doc deleted file mode 100644 index 2481807fd..000000000 --- a/doc/salome/gui/SMESH/input/constructing_meshes.doc +++ /dev/null @@ -1,483 +0,0 @@ -/*! - -\page constructing_meshes_page Constructing meshes - -To create a mesh on geometry, it is necessary to create a mesh object by choosing -- a geometrical shape produced in the Geometry module (main shape); -- meshing parameters, including - - \ref basic_meshing_algos_page "meshing algorithms" and - - \ref about_hypo_page "hypotheses" specifying constraints to be - taken into account by the chosen meshing algorithms. - -Then you can launch mesh generation by invoking \ref compute_anchor "Compute" command. -The generated mesh will be automatically shown in the Viewer. You can -switch off automatic visualization or limit mesh size until which it is -automatically shown in \ref mesh_preferences_page (Automatic update entry). - -\note Sometimes \a hypotheses term is used to refer to both algorithms -and hypotheses. - -Mesh generation on the geometry is performed in the bottom-up -flow: nodes on vertices are created first, then edges are divided into -segments using nodes on vertices; the nodes of segments are then -used to mesh faces; then the nodes of faces are used to mesh -solids. This automatically assures the conformity of the mesh. - -It is required to choose a meshing algorithm for every dimension of -sub-shapes up to the highest dimension to be generated. Note -that some algorithms generate elements of several dimensions, and -others of only one. It is not necessary to define meshing -parameters for all dimensions at once; you can start from 1D -meshing parameters only, compute the 1D mesh, then define 2D meshing -parameters and compute the 2D mesh (note that 1D mesh will not be -re-computed). - -An algorithm of a certain dimension chosen at mesh creation is applied -to discretize every sub-shape of this dimension. It is possible to -specify a different algorithm or hypothesis to be applied to one or -a group of sub-shapes by creating a \ref constructing_submeshes_page -"sub-mesh". You can specify no algorithms at all at mesh object -creation and specify the meshing parameters on sub-meshes only; then -only the sub-shapes, for which an algorithm and a hypothesis (if any) -have been defined will be discretized. - -\n Construction of a mesh on a geometry includes at least two -(\ref create_mesh_anchor "mesh creation" and -\ref compute_anchor "computing") of the following steps: - - -\anchor create_mesh_anchor -

Creation of a mesh object

-To construct a mesh: -
    -
  1. Select a geometrical object for meshing.
    2. -
  2. In the \b Mesh menu select Create Mesh or click "Create - Mesh" button in the toolbar. - -
    - \image html image32.png - "Create Mesh" button -
    - - The following dialog box will appear: - - \image html createmesh-inv.png -
    -
    3. -
  3. To filter off irrelevant meshing algorithms, you can - select Mesh Type in the corresponding list from Any, - Hexahedral, Tetrahedral, Triangular and \b Quadrilateral (there - can be less items for the geometry of lower dimensions). - - Selection of a mesh type hides all meshing algorithms that cannot - generate elements of this type.
    4. - -
  4. Apply \subpage basic_meshing_algos_page "meshing algorithms" and - \subpage about_hypo_page "hypotheses" which will be used to compute - this mesh. - - "Create mesh" dialog box contains several tab pages titled \b 3D, - \b 2D, \b 1D and \b 0D. The title of each page reflects the - dimension of the sub-shapes the algorithms listed on - this page affect and the maximal dimension of elements the algorithms - generate. For example, \b 3D page lists the algorithms that affect - 3D sub-shapes (solids) and generate 3D mesh elements - (tetrahedra, hexahedra etc.) - - As soon as you have selected an algorithm, you can create a - hypothesis (or select an already created one). A set of accessible - hypotheses includes only the hypotheses that can be used by the - selected algorithm. - - \note - - Some page(s) can be disabled if the geometrical - object does not include shapes (sub-shapes) of the corresponding - dimension(s). For example, if the input object is a geometrical face, - \b 3D page is disabled. - - Some algorithms affect the geometry of several dimensions, - i.e. 1D+2D or 1D+2D+3D. If such an algorithm is selected, the - dialog pages related to the corresponding lower dimensions are - disabled. - - \b 0D page refers to 0D geometry (vertices) rather than - to 0D elements. Mesh module does not provide algorithms that - produce 0D elements. Currently \b 0D page provides only one - algorithm "Segments around vertex" that allows specifying the required - size of mesh edges about the selected vertex (or vertices). - - For example, you need to mesh a 3D object. - - First, you can change a default name of your mesh in the \b Name - box. Then check that the selected geometrical object indicated in - \b Geometry field, is what you wish to mesh; if not, select - the correct object in the Object Browser. Click "Select" button - near \b Geometry field if the name of the object has not yet - appeared in \b Geometry field. -
    - \image html image120.png - "Select" button -
    - - Now you can define 3D Algorithm and 3D Hypotheses, which will be - applied to discretize the solids of your geometrical object using - 3D elements. Click the "Add Hypothesis" button to create - and add a hypothesis. -
    - \image html image121.png - "Add Hypothesis" button -
    - Click the "Plus" button to enable adding more additional hypotheses. - - Click the "Edit Hypothesis" button to change the values for the - current hypothesis. -
    - \image html image122.png - "Edit Hypothesis" button -
    - - Most 2D and 3D algorithms can work without hypotheses using - default meshing parameters. Some algorithms do not require any - hypotheses. After selection of an algorithm "Hypothesis" field of - the dialog can contain: -
      -
    • \ if the algorithm can work using default - parameters.
      • -
    • \ if the algorithm requires a hypothesis defining - its parameters.
      • -
    • If the algorithm does not use hypotheses, this field is grayed.
      • -
    - After selection of an algorithm Add. Hypothesis field can contain: -
      -
    • \ if the algorithm can be tuned - using an additional hypothesis.
      • -
    • If the algorithm does not use additional hypotheses, this field is grayed.
      • -
    - - Proceed in the same way with 2D and 1D Algorithms and Hypotheses that - will be used to mesh faces and edges of your geometry. (Note - that any object has edges, even if their existence is not - apparent, for example, a sphere has 4 edges). Note that the - choice of hypotheses and lower dimension algorithms depends on - the higher dimension algorithm. - - If you wish you can select other algorithms and/or hypotheses - for meshing some sub-shapes of your CAD model by \ref constructing_submeshes_page. - - Some algorithms generate mesh of several dimensions, while others - produce mesh of only one dimension. In the latter case there must - be one Algorithm and zero or several - Hypotheses for each dimension of your object, otherwise you will - not get any mesh at all. Of course, if you wish to mesh a face, - which is a 2D object, you do not need to define a 3D Algorithm and - Hypotheses. - - In the Object Browser the structure of the new mesh is - displayed as follows: - \image html image88.jpg - It contains: -
      -
    • a mesh name (Mesh_mechanic); -
    • a reference to the geometrical object on the basis of - which the mesh has been constructed (\a mechanic);
      • -
    • Applied hypotheses folder containing the references - to the hypotheses chosen at the construction of the mesh;
      • -
    • Applied algorithms folder containing the references - to the algorithms chosen at the construction of the mesh.
      • -
    • SubMeshes on Face folder containing the sub-meshes - defined on geometrical faces. There also can be folders for - sub-meshes on vertices, edges, wires, shells, solids and - compounds.
      • -
    • Groups of Faces folder containing the groups of mesh - faces. There also can be folders for groups of nodes, edges, - volumes 0D elements and balls.
      • -
    - - There is an alternative way to assign Algorithms and Hypotheses by - clicking Assign a set of hypotheses button and selecting among - pre-defined sets of algorithms and hypotheses. In addition to the built-in - sets of hypotheses, it is possible to create custom sets by editing - CustomMeshers.xml file located in the home directory. CustomMeshers.xml - file must describe sets of hypotheses in the - same way as ${SMESH_ROOT_DIR}/share/salome/resources/smesh/StdMeshers.xml - file does (sets of hypotheses are enclosed between \ - tags). For example: -~~~~~~{.xml} - - - - - - - -~~~~~~ - If the file contents are incorrect, there can be an error at - activation of Mesh module: "fatal parsing error: error - triggered by consumer in line ..." -
    -
    - \image html hypo_sets.png - List of sets of hypotheses. Tag [custom] is - automatically added to the sets defined by the user. -
    - \note - - \a "Automatic" in the names of predefined sets of hypotheses - does not actually mean that they are suitable for meshing any - geometry. - - The list of sets of hypotheses can be shorter than in the - above image depending on the geometry dimension. -
    5. -
- -Consider trying a sample script for construction of a mesh from our -\ref tui_creating_meshes_page "TUI Scripts" section. - -\anchor evaluate_anchor -

Evaluating mesh size

- -After the mesh object is created and all hypotheses are assigned and -before \ref compute_anchor "Compute" operation, it is possible to -calculate the eventual mesh size. For this, select the mesh in -the Object Browser and from the \b Mesh menu select \b -Evaluate. The result of evaluation will be displayed in the following -information box: - -\image html mesh_evaluation_succeed.png - -\anchor preview_anchor -

Previewing the mesh

- -Before \ref compute_anchor "the mesh computation", it is also possible -to see the mesh preview. This operation allows to incrementally -compute the mesh, dimension by dimension, and to discard an -unsatisfactory mesh. - -For this, select the mesh in the Object Browser. From the \b Mesh menu -select \b Preview or click "Preview" button in the toolbar or activate -"Preview" item from the pop-up menu. - -
-\image html mesh_precompute.png -"Preview" button -
- -Select 1D mesh or 2D mesh preview mode in the Preview dialog. - -\image html preview_mesh_1D.png "1D mesh preview shows nodes computed on geometry edges" -
-\image html preview_mesh_2D.png "2D mesh preview shows edge mesh elements, computed on geometry faces" - -Compute button computes the whole mesh. - -When the Preview dialog is closed, the question about the storage of temporarily -created mesh elements appears: - -\image html preview_tmp_data.png - -These elements can be kept in the mesh. - - -\anchor submesh_order_anchor -

Changing sub-mesh priority

- -If the mesh contains concurrent \ref constructing_submeshes_page "sub-meshes", -it is possible to change the priority of their computation, i.e. to -change the priority of applying algorithms to the shared sub-shapes of -the Mesh shape. - -To change sub-mesh priority: - -Choose "Change sub-mesh priority" from the Mesh menu or a pop-up -menu. The opened dialog shows a list of sub-meshes in the order of -their priority. - -There is an example of sub-mesh order modifications taking a Mesh created on a Box -shape. The main Mesh object: - -The first sub-mesh Submesh_1 created on Face_1 is: - -The second sub-mesh Submesh_2 created on Face_2 is: - - -And the last sub-mesh Submesh_3 created on Face_3 is: - - -The sub-meshes become concurrent if they share sub-shapes that can be -meshed with different algorithms (or different hypotheses). In the -example, we have three sub-meshes with concurrent algorithms, because -they have different hypotheses. - -The first mesh computation is made with: -
-\image html mesh_order_123.png -"Mesh order SubMesh_1, SubMesh_2, SubMesh_3"
-
-\image html mesh_order_123_res.png -"Result mesh with order SubMesh_1, SubMesh_2, SubMesh_3 "
- -The next mesh computation is made with: -
-\image html mesh_order_213.png -"Mesh order SubMesh_2, SubMesh_1, SubMesh_3"
-
-\image html mesh_order_213_res.png -"Result mesh with order SubMesh_2, SubMesh_1, SubMesh_3 "
- -And the last mesh computation is made with: -
-\image html mesh_order_321.png -"Mesh order SubMesh_3, SubMesh_2, SubMesh_1"
-
\image html mesh_order_321_res.png -"Result mesh with order SubMesh_3, SubMesh_2, SubMesh_1 "
- -As we can see, each mesh computation has a different number of result -elements and a different mesh discretization on the shared edges (the edges -that are shared between Face_1, Face_2 and Face_3) - -Additionally, sub-mesh priority (the order of applied algorithms) can -be modified not only in a separate dialog box, but also in -the Preview. This helps to preview different mesh results, -modifying the order of sub-meshes. -
-\image html mesh_order_preview.png -"Preview with sub-mesh priority list box"
- -If there are no concurrent sub-meshes under the Mesh object, the user -will see the following information. -
-\image html mesh_order_no_concurrent.png -"No concurrent submeshes detected"
- - -\anchor compute_anchor -

Computing the mesh

- -It is equally possible to skip \ref evaluate_anchor "the Evaluation" -and \ref preview_anchor "the Preview" and to \b Compute the mesh after -the hypotheses are assigned. For this, select your mesh in -the Object Browser. From the \b Mesh menu or the context menu -select \b Compute or click \a "Compute" button of the toolbar. - -
-\image html image28.png -"Compute" button -
- -After the mesh computation finishes, the Mesh Computation information -box appears. If you close this box and click "Compute" button again, -without previously changing meshing parameters, the mesh will NOT be -re-computed and the Mesh Computation information box will be shown -with the same contents. (To fully re-compute the mesh, invoke -\ref clear_mesh_anchor "Clear Mesh Data" command before). - -\anchor meshing_result_anchor -If the mesh computation has been a success, the box shows information -on the number of entities of different types in the mesh. - -\image html meshcomputationsucceed.png - -\anchor meshing_failed_anchor -If the mesh computation has failed, the information about the cause of the -failure is provided in \b Errors table. - -\image html meshcomputationfail.png - -After you select an error in \b Errors table, Show Sub-shape button allows -visualizing in magenta the geometrical entity meshing of which failed -(Name of this entity or its ID and type is shown in \a Sub-shape column). - -
-\image html failed_computation.png -3D algorithm failed to compute mesh on a box shown using Show - Sub-shape button -
- -Publish Sub-shape button publishes the sub-shape, whose meshing -has failed, in the Geometry component as a child of the main shape, which -allows analyzing the problematic geometry and creating a sub-mesh on it in -order to locally tune the hypotheses. - -If the failure is caused by an invalid input mesh and the algorithm has -found which mesh entities are bad, Show bad Mesh -button appears in the dialog. Clicked, it shows the bad mesh entities in -the Viewer in magenta. Sometimes the shown mesh entities are too small -or/and hidden by other mesh elements. They can be seen after -switching the mesh to Wireframe visualization mode or switching off -the visualization of faces and volumes (if any). - -Bad Mesh to Group button creates groups of bad mesh entities -to facilitate their analysis. - -
-\image html show_bad_mesh.png -Edges bounding a hole in the surface are shown in magenta using Show - bad Mesh button -
- -\note Mesh Computation Information box does not appear if you set -\ref show_comp_result_pref "Mesh computation/Show a computation result notification" preference -to the "Never" value. This option gives the possibility to control mesh -computation reporting. There are the following possibilities: always -show the information box, show only if an error occurs or never. -By default, the information box is always shown after mesh computation operation. - -

-\anchor edit_anchor -

Editing the mesh

- -It is possible to \ref modifying_meshes_page "edit the mesh" of a -lower dimension before generation of the mesh of a higher dimension. - -For example you can generate a 2D mesh, modify it using e.g. -\ref pattern_mapping_page, and then generate a 3D mesh basing on the -modified 2D mesh. The workflow is as follows: -- Define 1D and 2D meshing algorithms. -- Compute the mesh. 2D mesh is generated. -- Apply \ref pattern_mapping_page. -- Define 3D meshing algorithms without modifying 1D and 2D algorithms -and hypotheses. -- Compute the mesh. 3D mesh is generated. - -\note Nodes and elements added \ref adding_nodes_and_elements_page -"manually" cannot be used in this workflow because the manually created -entities are not attached to any geometry and thus (usually) cannot be -found by the mesher paving a geometry. - -See Also a sample TUI Script demonstrates the possibility of -\ref tui_editing_while_meshing "Intermediate edition while meshing" - -*/ diff --git a/doc/salome/gui/SMESH/input/constructing_submeshes.doc b/doc/salome/gui/SMESH/input/constructing_submeshes.doc deleted file mode 100644 index b7fe2feee..000000000 --- a/doc/salome/gui/SMESH/input/constructing_submeshes.doc +++ /dev/null @@ -1,159 +0,0 @@ -/*! - -\page constructing_submeshes_page Constructing sub-meshes - -\tableofcontents - -By purpose, the sub-mesh is an object used to assign to a sub-shape -different meshing parameters than those assigned to the main shape. - -Structurally, the sub-mesh is a mesh on a certain sub-shape, or a group of -sub-shapes, possibly generated using different meshing algorithms -and/or hypotheses than those used to generate the mesh on other -sub-shapes. - -Creation of a sub-mesh allows to control individually meshing of a -certain sub-shape, thus to get a locally coarser or finer mesh, to get -elements of different types in the same mesh, etc. - -A sub-mesh can be meshed individually. To achieve this, select a -sub-mesh and either invoke Compute Sub-mesh vai the contextual -menu in the Object Browser or invoke Mesh > Compute menu. - -\section submesh_shape_section How to get a sub-shape for sub-mesh construction - -A sub-shape to create a sub-mesh on should be retrieved from the main shape -in one of the following ways: - -\section submesh_priority How hypotheses are selected among sub-meshes - -Internally, definition of meshing parameters to apply for -discretization of a certain sub-shape, for example an edge of a -compound of solids, starts from searching an algorithm, 1D as for the -edge. The following sub-shapes are sequentially checked for presence -of a sub-mesh where 1D algorithm is assigned: - -(This sequence of sub-shapes defines the priority of sub-meshes. Thus more -local, i.e. assigned to sub-shape of lower dimension, algorithms and -hypotheses have higher priority during the search of hypotheses to -apply.) - -As soon as a 1D algorithm is found, the search stops and the same -sequence of sub-shapes is checked to find the main and additional 1D -hypotheses, which can be taken into account by the found 1D algorithm. - -The multi-dimensional algorithms have a higher priority than -uni-dimensional ones if they are assigned to sub-meshes of the -same priority. - -If meshing parameters are defined on sub-meshes of the same priority, -for example, different 1D hypotheses are assigned to two faces sharing -an edge, the hypothesis assigned to a sub-shape with a lower ID will -be used for meshing. You can \ref submesh_order_anchor "change" mutual -priority of such concurrent sub-meshes. - -\section submesh_definition How to construct a sub-mesh - -\n Construction of a sub-mesh consists of: - - -
To construct a sub-mesh: -\par -From the \b Mesh menu select Create Sub-mesh or click "Create -Sum-mesh" button in the toolbar. - -
- \image html image33.gif - "Create Sub-mesh" button -
- -\par -The following dialog box will appear: - -\par -\image html createmesh-inv2.png - -It allows to define the \b Name, the parent \b Mesh and the \b -Geometry (e.g. a face if the parent mesh has been built on box) of the -sub-mesh. You can define meshing algorithms and hypotheses in the same way as -in \ref constructing_meshes_page "Create mesh" dialog. - -Later you can change the applied hypotheses or their parameters in -\ref editing_meshes_page "Edit mesh/sub-mesh" dialog. Mesh entities -generated using changed hypotheses are automatically removed. - -\anchor subshape_by_mesh_elem -If the parent mesh is already computed, then you can define the -\b Geometry by picking mesh elements computed on a sub-shape of interest -in the 3D Viewer, i.e. you do not have to extract this sub-shape -in Geometry module beforehand. To start element selection, press \a -Selection button to the right of \b Geometry label. If this button is -already down, then click it to release and then click it again. The -following pop-up menu allowing to choose a way of geometry definition will -appear. - -\image html choose_geom_selection_way.png - -Direct geometry selection enables selecting the sub-shape in the Object -Browser. -Find geometry by mesh element selection activates the following dialog. - -\image html find_geom_by_mesh_elem.png - -In this dialog, Element Type defines a kind of element to pick in the -Viewer. -Instead of picking an element in the Viewer, you can type its -ID in Element ID field. - Geometry name field allows defining a name of the sub-shape, -with which the sub-shape will appear in the Object Browser (if not yet -there). - -\section submesh_tree Sub-mesh in the Object Browser - -In the Object Browser the structure of the new sub-mesh will be -displayed as follows: - -\image html image10.jpg - -It contains: - - -
See Also a sample TUI Script of a -\ref tui_construction_submesh "Construct Sub-mesh" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/convert_to_from_quadratic_mesh.doc b/doc/salome/gui/SMESH/input/convert_to_from_quadratic_mesh.doc deleted file mode 100644 index a253c0523..000000000 --- a/doc/salome/gui/SMESH/input/convert_to_from_quadratic_mesh.doc +++ /dev/null @@ -1,59 +0,0 @@ -/*! - -\page convert_to_from_quadratic_mesh_page Convert to/from Quadratic Mesh - -\n This functionality allows transforming linear meshes (or -sub-meshes) to quadratic and vice versa. -Note that conversion of a sub-mesh most probably will produce a -non-conformal mesh. Elements on the boundary between quadratic and -linear sub-meshes become (or remain) quadratic. - -See \ref adding_quadratic_elements_page for more information about -quadratic meshes. - -To produce a conversion: -
    -
  1. Select a mesh or a sub-mesh in the Object Browser or in the - Viewer.
    2. -
  2. From the Modification menu or from the contextual menu in the - Object Browser choose Convert to/from Quadratic Mesh item, - or click "Convert to/from quadratic" button in the - toolbar. - -
    -\image html image154.png -"Convert to/from quadratic" button -
    - -The following dialog box will appear: - -\image html convert.png - -
    3. -
  3. In this dialog box specify: - -
      -
    • If it is necessary to convert a linear mesh to quadratic or a quadratic - mesh to linear. **Convert to bi-quadratic** creates some types of quadratic - elements with additional central nodes: TRIA7, QUAD9 and HEXA27 - elements instead of TRIA6, QUAD8, and HEXA20 elements - respectively.
      • -
    • If it is necessary to place **medium nodes** of the quadratic mesh **on the - geometry** (meshed shape). This option is relevant for conversion to - quadratic provided that the mesh is based on a geometry (not imported - from file).
      • -
    - -\image html image156.gif -
    Linear mesh (coarse mesh on a torus)
    - -\image html image155.gif -
    Quadratic mesh
    - -
    4. -
  4. Click the \b Apply or Apply and Close button.
    5. -
- -
See Also a sample TUI Script of a \ref tui_quadratic "Convert to/from quadratic" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/copy_mesh.doc b/doc/salome/gui/SMESH/input/copy_mesh.doc deleted file mode 100644 index 404359ce7..000000000 --- a/doc/salome/gui/SMESH/input/copy_mesh.doc +++ /dev/null @@ -1,54 +0,0 @@ -/*! - -\page copy_mesh_page Copy Mesh - -\n A mesh can be created by copying a part of or the whole other mesh. - -To make a copy of a mesh: - -\par -From the contextual menu in the Object Browser of from the \b Mesh -menu select Copy Mesh or click "Copy Mesh" button in -the toolbar. - -\image html copy_mesh_icon.png -
"Copy Mesh" button
- -\par -The following dialog box will appear: - -\image html copy_mesh_dlg.png - -\par -In the dialog: - - -See Also a sample -\ref tui_copy_mesh "TUI Example of mesh copying." -*/ diff --git a/doc/salome/gui/SMESH/input/create_groups_from_geometry.doc b/doc/salome/gui/SMESH/input/create_groups_from_geometry.doc deleted file mode 100644 index b8ee303f2..000000000 --- a/doc/salome/gui/SMESH/input/create_groups_from_geometry.doc +++ /dev/null @@ -1,26 +0,0 @@ -/*! - -\page create_groups_from_geometry_page Create Groups from Geometry - -This operation allows creating groups on geometry on all selected -shapes. Only the main shape of the mesh and its sub-shapes can be selected. - -The type of each new group is defined automatically by the nature of -the Geometry. -The group names will be the same as the names of geometrical objects. - -\warning It's impossible to create a group of 0D elements or ball -elements with this operation. For this, it is necessary to use -\ref creating_groups_page "Create Group" operation. - -To use this operation, select in the \b Mesh menu or in the contextual -menu in the Object browser Create Groups from Geometry item. - -\image html create_groups_from_geometry.png - -In this dialog \b Elements group contains a list of shapes, on which -groups of elements will be created; \b Nodes group contains a list of shapes, -on which groups of nodes will be created. - - -*/ diff --git a/doc/salome/gui/SMESH/input/creating_groups.doc b/doc/salome/gui/SMESH/input/creating_groups.doc deleted file mode 100644 index da12c8337..000000000 --- a/doc/salome/gui/SMESH/input/creating_groups.doc +++ /dev/null @@ -1,145 +0,0 @@ -/*! - -\page creating_groups_page Creating groups - -\n In MESH you can create a \ref grouping_elements_page "group" of -elements of a certain type. The main way to create a group, is to -select in the \b Mesh menu Create Group item (also available in -the context menu of the mesh).
-To create a group you should define the following: - -Mesh module distinguishes between the three Group types: -Standalone Group, Group on Geometry and Group on Filter. - -\anchor standalone_group

"Standalone Group"

- -Standalone Group contains a list of mesh elements, which you can define in -the following ways: - -In the manual edition mode you can - - -\image html creategroup.png - - -For example, to create a new group containing all faces of an -existing group and some other faces selected in the viewer: - - -Please note that the new group does not have references to the source -group. It contains only the list of face IDs. So if the source group -is changed, the new one is not updated accordingly. - - -\image html image130.gif -
In this picture the brown cells belong to a group defined - manually.
- -See Also a sample TUI Script of a -\ref tui_create_standalone_group "Create a Standalone Group" -operation. - - -\anchor group_on_geom

"Group on Geometry"

- -To create a group on geometry check Group on geometry in the \b -Group \b type field. The group on geometry contains the elements -of a certain type generated on the selected geometrical object. Group -contents are dynamically updated if the mesh is modified. The group on -geometry can be created only if the mesh is based on geometry. - -To define a group, click the \a Selection button and choose -- Direct geometry selection to select a shape in the Object - Browser or in the Viewer; -- Find geometry by mesh element selection to activate a - dialog which retrieves a shape by the selected element generated on - this shape. - -Note that this choice is available only if the mesh elements are -already generated. - -\image html a-creategroup.png - -After confirmation of the operation a new group of mesh elements will -be created. - -\image html image132.gif -
In this picture the cells which belong to a certain - geometrical face are selected in green.
- -See Also a sample TUI Script of a -\ref tui_create_group_on_geometry "Create a Group on Geometry" -operation. - - -\anchor group_on_filter

"Group on Filter"

- -To create a group on filter check Group on filter in the -Group type field. The group on filter contains the elements -of a certain type satisfying the defined filter. Group contents are -dynamically updated if the mesh is modified. - -To define a group, click the Set filter button and define -criteria of the filter in the opened dialog. After the -operation is confirmed, a new group of mesh elements will be created. See more about -filters on the -\ref selection_filter_library_page "Selection filter library" page. - -\image html creategroup_on_filter.png - -See Also a sample TUI Script of a -\ref tui_create_group_on_filter "Create a Group on Filter" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/cut_mesh_by_plane.doc b/doc/salome/gui/SMESH/input/cut_mesh_by_plane.doc deleted file mode 100644 index 9befdbbeb..000000000 --- a/doc/salome/gui/SMESH/input/cut_mesh_by_plane.doc +++ /dev/null @@ -1,55 +0,0 @@ -/*! - -\page cut_mesh_by_plane_page Cut a tetrahedron mesh by a plane - -\n MeshCut works only with MED files and produces MED files, and is a standalone program. -It can be used either directly from a command shell outside SALOME, or with a GUI interface in SMESH, -provided in a python plugin that needs to be installed in your SALOME application. - -\n MeshCut allows to cut a mesh constituted of linear tetrahedrons by a plane. -\n The tetrahedrons intersected by the plane are cut and replaced by elements of various types, -(tetrahedron, pyramid, pentahedron). - -
-\anchor meshcut_standalone -

Using MeshCut as a standalone program, outside SALOME

- -\n MeshCut is a standalone program, reading and producing med files. -\n -\n Syntax: -\code -MeshCut input.med output.med resuMeshName aboveGroup belowGroup nx ny nz px py pz T -\endcode - -\n -\n where: -\n input.med = name of the original mesh file in med format -\n output.med = name of the result mesh file in med format -\n resuMeshName = name of the result mesh -\n aboveGroup = name of the group of volumes above the cut plane -\n belowGroups = name of the group of volumes below the cut plane -\n nx ny nz = vector normal to the cut plane -\n px py pz = a point of the cut plane -\n T = 0 < T < 1 : vertices of a tetrahedron are considered as belonging to -\n the cut plane if their distance from the plane is inferior to L*T, -\n where L is the mean edge size of the tetrahedron - -
-\anchor meshcut_plugin -

Using MeshCut inside SALOME

- -When the MeshCut plugin is installed, it can be found in the Mesh menu, sub-menu SMESH_plugins. -\n If the plugin is not installed, the file meshcut_plugin.py is in -SMESH installation in subdirectory bin/salome/meshcut_plugin.py. - -\n If there are already plugins defined in a smesh_plugins.py file, - this file should be added at the end. - if not, copied as ${HOME}/Plugins/smesh_plugins.py or ${APPLI}/Plugins/smesh_plugins.py - or in ${PLUGINPATH} Directory. - -From the Mesh menu, sub-menu SMESH_plugins, choose "MeshCut" item -The following dialog box will appear: -\image html meshcut_plugin.png "MeshCut Plugin dialog box" - -See above for the meaning of the parameters. -*/ diff --git a/doc/salome/gui/SMESH/input/cutting_quadrangles.doc b/doc/salome/gui/SMESH/input/cutting_quadrangles.doc deleted file mode 100644 index 34f26a67d..000000000 --- a/doc/salome/gui/SMESH/input/cutting_quadrangles.doc +++ /dev/null @@ -1,51 +0,0 @@ -/*! - -\page cutting_quadrangles_page Cutting quadrangles - -This operation allows cutting one or several quadrangle elements into two or four triangles. - -To cut quadrangles: - -1) Select a mesh (and display it in the 3D Viewer if you are going to pick elements by mouse). - -2) In the \b Modification menu select the Cutting of quadrangles item or -click "Cutting of quadrangles" button in the toolbar. - -\image html image82.png -
"Cutting of quadrangles" button
- -The following dialog box will appear: - -\image html a-cuttingofquadrangles.png - - -- The main list contains the list of quadrangles selected for cutting. You can -click on a quadrangle in the 3D viewer and it will be highlighted (lock Shift -keyboard button to select several quadrangles): - - Click \b Add button and the ID of this quadrangle will be added to the list. - - To remove a selected element or elements from the list click \b Remove button. - - Sort list button allows sorting the list of IDs. - - \b Filter button allows applying a definite \ref filtering_elements "filter" - to the selection of quadrangles. -- Apply to all check box allows cutting all quadrangles of the selected mesh. -- \b Preview provides a preview of cutting in the viewer. It is disabled for Cut into 4 triangles as this cutting way implies no ambiguity. -- \b Criterion defines the way of cutting: - - Cut into 4 triangles allows cutting a quadrangle into four triangles by inserting a new node at the center of the quadrangle. The other options allow cutting a quadrangle into two triangles by connecting the nodes of a diagonal. - - Use diagonal 1-3 and Use diagonal 2-4 allow specifying the opposite corners, which will be connected to form two new triangles. - - Use numeric functor allows selecting in the field below a quality metric, which will be optimized when choosing a diagonal for cutting a quadrangle: - - Minimum diagonal cuts by the shortest diagonal. - - Aspect Ratio cuts by the diagonal splitting the quadrangle into triangles with \ref aspect_ratio_page "Aspect Ratio" closer to 1 - - Minimum Angle cuts by the diagonal splitting the quadrangle into triangles with \ref minimum_angle_page "Minimum Angle" closer to 60 degrees. - - Skew cuts by the diagonal splitting the quadrangle into triangles with \ref skew_page "Skew" closer to 0.0 degrees. -- Select from allows choosing a sub-mesh or an existing group, whose quadrangle elements then can be added to the main list. - -3) Click the \b Apply or Apply and Close button to confirm the operation. - -\image html image52.jpg "The chosen quadrangular element" - -\image html image51.jpg "Two resulting triangular elements" - -
See Also a sample TUI Script of a -\ref tui_cutting_quadrangles "Cutting Quadrangles" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/define_mesh_by_script.doc b/doc/salome/gui/SMESH/input/define_mesh_by_script.doc deleted file mode 100644 index 4b978245c..000000000 --- a/doc/salome/gui/SMESH/input/define_mesh_by_script.doc +++ /dev/null @@ -1,33 +0,0 @@ -/*! - -\page use_existing_page Use Edges/Faces to be Created Manually - -The algorithms Use Edges to be Created Manually and -Use Faces to be Created Manually allow creating a 1D or a 2D mesh -in a python script (using AddNode, AddEdge -and AddFace commands) and then using such sub-meshes in the -construction of a 2D or a 3D mesh. - -For example, you want to use standard algorithms to generate 1D and 3D -meshes and to create 2D mesh by your python code. For this, you -
    -
  1. create a mesh object, assign a 1D algorithm,
    2. -
  2. invoke \b Compute command, which computes a 1D mesh,
    3. -
  3. assign Use Faces to be Created Manually and a 3D algorithm,
    4. -
  4. run your python code, which creates a 2D mesh,
    5. -
  5. invoke \b Compute command, which computes a 3D mesh.
    6. -
- -\warning Use Edges to be Created Manually and Use Faces to -be Created Manually algorithms should be assigned _before_ -mesh generation by the Python code. - -Consider trying a sample script demonstrating the usage of -\ref tui_use_existing_faces "Use Faces to be Created Manually" -algorithm for construction of a 2D mesh using Python commands. - -\image html use_existing_face_sample_mesh.png - Mesh computed by \ref tui_use_existing_faces "the sample script" - shown in a Shrink mode. - -*/ diff --git a/doc/salome/gui/SMESH/input/deflection_2d.doc b/doc/salome/gui/SMESH/input/deflection_2d.doc deleted file mode 100644 index a9d38cde3..000000000 --- a/doc/salome/gui/SMESH/input/deflection_2d.doc +++ /dev/null @@ -1,25 +0,0 @@ -/*! - -\page deflection_2d_page Deflection 2D - -\n This quality control criterion consists of calculation of distance -between a mesh face gravity corner and the surface the face discretizes. - -To apply the Deflection 2D quality criterion to your mesh: -
    -
  1. Display your mesh in the viewer.
    2. - -
  2. Choose Controls > Face Controls > Deflection 2D or click -"Deflection 2D" button in the toolbar. - -Your mesh will be displayed in the viewer with faces colored according -to the applied mesh quality control criterion: - -\image html deflection_2d.png -
    3. -
- -
See Also a sample TUI Script of a -\ref tui_deflection_2d "Deflection 2D quality control" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/deleting_groups.doc b/doc/salome/gui/SMESH/input/deleting_groups.doc deleted file mode 100644 index 521b55282..000000000 --- a/doc/salome/gui/SMESH/input/deleting_groups.doc +++ /dev/null @@ -1,22 +0,0 @@ -/*! - -\page deleting_groups_page Deleting groups with content - -To delete groups and their content, in the menu select -Modification -> Remove -> Delete groups with Contents -and select one or several groups you wish to delete in the 3D viewer -or in the Object Browser. - -The selected groups will be listed in Delete groups with contents menu. -Then click Apply and Close button to remove the selected groups -and close the menu or \b Apply button to remove them and proceed with -the selection. - -\image html deletegroups.png - -\n Please, note that this operation removes groups with their - elements. To delete a group and leave its elements intact, right-click -on the group in the Object Browser and select \b Delete in the pop-up -menu or select the group and choose Edit -> Delete in the main menu. - -*/ diff --git a/doc/salome/gui/SMESH/input/diagonal_inversion_of_elements.doc b/doc/salome/gui/SMESH/input/diagonal_inversion_of_elements.doc deleted file mode 100644 index c97663de2..000000000 --- a/doc/salome/gui/SMESH/input/diagonal_inversion_of_elements.doc +++ /dev/null @@ -1,34 +0,0 @@ -/*! - -\page diagonal_inversion_of_elements_page Diagonal inversion of two triangles - -\n In MESH you can inverse the diagonal (edge) of a pseudo-quadrangle -formed by two neighboring triangles with one common edge. - -To inverse the diagonal: -
    -
  1. From the \b Modification menu choose the Diagonal inversion item or -click "Diagonal Inversion" button in the toolbar. - -\image html image70.png -
    "Diagonal Inversion" button
    - -The following dialog box shall appear: - -\image html diagonalinversion.png - -
    2. -
  2. Enter IDs of nodes forming the required edge in the \b Edge field -(the node IDs must be separated by dashes) or select -this edge in the 3D viewer.
    3. -
  3. Click the \b Apply or Apply and Close button.
    4. -
- -\image html image38.jpg "The selected edge" - -\image html image36.jpg "The inverted edge" - -
See Also a sample TUI Script of a -\ref tui_diagonal_inversion "Diagonal Inversion of Elements" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/display_entity.doc b/doc/salome/gui/SMESH/input/display_entity.doc deleted file mode 100644 index 13b11c38e..000000000 --- a/doc/salome/gui/SMESH/input/display_entity.doc +++ /dev/null @@ -1,23 +0,0 @@ -/*! - -\page display_entity_page Display Entity - -\n In this submenu you can choose to display only volumes, faces or -edges or combine them. - -\image html image56.jpg Only Faces - -\image html image58.png Only Edges - -\image html image59.png Edges + Faces - -If the mesh contains a lot of elements, select Choose... item, - -\image html display_entity_choose_item.png Item to call 'Display Entity' dialog box - -and Display Entity dialog box will provide a way to display only some entities at the first display instead of displaying all entities, which can take a long time. - -\image html display_entity_dlg.png 'Display Entity' dialog allows to select entities before displaying - -\note This menu item is available from the context menu in both Object browser and 3D viewer. -*/ \ No newline at end of file diff --git a/doc/salome/gui/SMESH/input/display_mode.doc b/doc/salome/gui/SMESH/input/display_mode.doc deleted file mode 100644 index adcd37615..000000000 --- a/doc/salome/gui/SMESH/input/display_mode.doc +++ /dev/null @@ -1,23 +0,0 @@ -/*! - -\page display_mode_page Display Mode - -\n By default your objects are represented as defined in -\ref mesh_tab_preferences "Preferences". -\n However, right-clicking on the mesh in the Object Browser, -and selecting Display Mode, you can display your mesh as: - -\image html image53.gif Wireframe - -\image html image37.jpg Shading - -\image html image56.gif Nodes - -\b Wireframe can combine with \b Nodes and \b Shading. - -\b Shading and \b Wireframe modes can combine with \b Shrink, however -\b Nodes can't. - -\image html image55.gif Shrink - -*/ diff --git a/doc/salome/gui/SMESH/input/double_elements_control.doc b/doc/salome/gui/SMESH/input/double_elements_control.doc deleted file mode 100644 index 63ee0e762..000000000 --- a/doc/salome/gui/SMESH/input/double_elements_control.doc +++ /dev/null @@ -1,14 +0,0 @@ -/*! - -\page double_elements_page Double edge, Double faces and Double volumes - -These mesh quality controls highlight the mesh elements basing on the same set of nodes. - -\image html double_faces.png - -In this picture some faces are coincident after copying all elements -with translation with subsequent Merge of nodes. - -\sa A sample TUI Script of a \ref filter_double_elements "Filters of Double Elements". - -*/ diff --git a/doc/salome/gui/SMESH/input/double_nodes_control.doc b/doc/salome/gui/SMESH/input/double_nodes_control.doc deleted file mode 100644 index 10fd49a41..000000000 --- a/doc/salome/gui/SMESH/input/double_nodes_control.doc +++ /dev/null @@ -1,17 +0,0 @@ -/*! - -\page double_nodes_control_page Double nodes - -This mesh quality control highlights the nodes which are coincident -with other nodes (within a given tolerance). Distance at which two -nodes are considered coincident is defined by -\ref dbl_nodes_tol_pref "Quality Controls/Double nodes tolerance" -preference. - -\image html double_nodes.png - -In this picture some nodes are coincident after copying all elements with translation. - -\sa A sample TUI Script of a \ref tui_double_nodes_control "Double Nodes" filter. - -*/ diff --git a/doc/salome/gui/SMESH/input/double_nodes_page.doc b/doc/salome/gui/SMESH/input/double_nodes_page.doc deleted file mode 100644 index 1d5a5ddd4..000000000 --- a/doc/salome/gui/SMESH/input/double_nodes_page.doc +++ /dev/null @@ -1,164 +0,0 @@ -/*! - -\page double_nodes_page Duplicate Nodes or/and Elements - -\n This operation allows duplicating mesh nodes or/and elements, which can be useful to emulate a crack in the model. - -Duplication consists in creation of mesh elements "equal" to existing ones. - -To duplicate nodes or/and elements: -
    -
  1. From the \b Modification menu choose \b Transformation -> Duplicate - Nodes or/and Elements item or click "Duplicate Nodes or/and - Elements" button in the toolbar. -
    -\image html duplicate_nodes.png "Duplicate Nodes or/and Elements button" -
    2. -
  2. Check in the dialog box one of four radio buttons corresponding to - the type of duplication operation you would like to perform.
    3. -
  3. Fill the other fields available in the dialog box (depending on - the chosen operation mode).
    4. -
  4. Click the \b Apply or Apply and Close button to perform the - operation of duplication.
    5. -
- -\n "Duplicate Nodes or/and Elements" dialog has four working modes: - - -
-\anchor mode_without_elem_anchor - -

Duplicate nodes only

- -\image html duplicate01.png - -Parameters to be defined in this mode: - -A schema below illustrates how the crack is emulated using the node duplication. -\image html crack_emulation_double_nodes.png "Crack emulation" -This schema shows a virtual crack in a 2D mesh created using this duplication -mode: -- Black balls are duplicated nodes. -- Red balls are new nodes. -- Elements to replace nodes with new ones are marked with green. - -Note that in the reality duplicated nodes coincide with new nodes. - -
-\anchor mode_with_elem_anchor - - -

Duplicate nodes and border elements

- -\image html duplicate02.png - -Parameters to be defined in this mode: - - -A schema below explains the crack emulation using the node duplication -with border elements. -\image html crack_emulation_double_nodes_with_elems.png "Crack emulation" -This schema shows a virtual crack in a 2D mesh created using this duplication -mode. In this schema: -- Black segments are duplicated elements (edges in 2D case). -- Black balls (except for the lowest one) are duplicated nodes of duplicated elements. -- The lowest black ball is the non-duplicated node. -- Red balls are newly created nodes. -- Red segments are created elements (edges). -- Elements to replace nodes with new ones are marked with green. - -Note that in the reality nodes to duplicate coincide with new nodes. -
-In a 3D case, where elements to duplicate are faces, the edges -located at the "crack" (if any) are cloned automatically. - -
-\anchor mode_elem_only_anchor -

Duplicate elements only

- -This mode duplicates the given elements, i.e. creates new elements with the same nodes as the given elements. -
- -\image html duplicate03.png - -Parameters to be defined in this mode: - - -
-\anchor mode_group_boundary_anchor -

Duplicate nodes on group boundaries

- -This mode duplicates nodes located on boundaries between given groups of volumes. - -
- -\image html duplicate04.png - -Parameters to be defined in this mode: - - -
See Also a sample TUI Script of a - \ref tui_duplicate_nodes "Duplicate nodes or/and elements" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/editing_groups.doc b/doc/salome/gui/SMESH/input/editing_groups.doc deleted file mode 100644 index a880b1cfb..000000000 --- a/doc/salome/gui/SMESH/input/editing_groups.doc +++ /dev/null @@ -1,49 +0,0 @@ -/*! - -\page editing_groups_page Editing groups - -To edit an existing group of elements: -
    -
  1. Select your group in the Object Browser and in the \b Mesh menu click -the Edit Group item or "Edit Group" button in the toolbar.
    2. - -\image html image74.gif -
    "Edit Group" button
    - -The following dialog box will appear (if the selected group -is standalone, else this dialog looks different): - -\image html editgroup.png - -In this dialog box you can modify the name and the color of your group -despite of its type. You can add or remove the elements composing a -standalone group. You can change criteria of the filter of -a group on filter. For more information see -\ref creating_groups_page "Creating Groups" page. - -
  2. Click the \b Apply or Apply and Close button to confirm -modification of the group.
    3. -
- -
-\anchor convert_to_standalone -To convert an existing group on geometry or a group on filer into -a standalone group and modify its contents: -
    -
  1. Select your group on geometry or on filter in the -Object Browser and in the \b Mesh menu click the Edit Group as -Standalone item.
    2. - -\image html image74.gif -
    "Edit Group as Standalone" button
    - -The selected group will be converted into a standalone group and -its contents can be modified. - -
  2. Click the \b Apply or Apply and Close button to confirm modification of the -group.
    3. -
- -\sa A sample TUI Script of an \ref tui_edit_group "Edit Group" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/editing_meshes.doc b/doc/salome/gui/SMESH/input/editing_meshes.doc deleted file mode 100644 index a4602e6c4..000000000 --- a/doc/salome/gui/SMESH/input/editing_meshes.doc +++ /dev/null @@ -1,32 +0,0 @@ -/*! - -\page editing_meshes_page Editing Meshes - -\n After you have created a mesh or sub-mesh with definite applied -meshing algorithms and hypotheses you can edit your mesh by \b assigning other -algorithms and/or hypotheses or \b unassigning the applied hypotheses and -algorithms. The editing proceeds in the same way as -\ref create_mesh_anchor "Mesh Creation". - -\image html createmesh-inv3.png - -You can also change values for the current hypothesis by clicking the -"Edit Hypothesis" button. - -\image html image122.png -
"Edit Hypothesis" button
- -Mesh entities generated before using changed hypotheses are automatically removed. - -See how the mesh constructed on a geometrical object -changes if we apply different meshing parameters to it. - -\image html edit_mesh1.png "Example of a mesh with Max. Element area 2D hypothesis roughly corresponding to 1D hypotheses on edges" -
- -\image html edit_mesh_change_value_hyp.png "And now the Max Element area is greatly reduced" - -
See Also a sample TUI Script of an -\ref tui_editing_mesh "Edit Mesh" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/extrusion.doc b/doc/salome/gui/SMESH/input/extrusion.doc deleted file mode 100644 index 96da45d43..000000000 --- a/doc/salome/gui/SMESH/input/extrusion.doc +++ /dev/null @@ -1,181 +0,0 @@ -/*! - -\page extrusion_page Extrusion - -\n Extrusion is used to build mesh elements of plus one -dimension than the input ones. Boundary elements around generated -mesh of plus one dimension are additionally created. All created -elements can be automatically grouped. Extrusion can be used to create -a \ref extrusion_struct "structured mesh from scratch". - -\image html extrusion_box.png "If you extrude several quadrangles, you get exactly the same mesh as if you meshed a geometrical box (except for that the initial quadrangles can be incorrectly oriented): quadrangles and segments are created on the boundary of the generated mesh" - -

Any node, segment or 2D element can be extruded. Each type of -elements is extruded into a corresponding type of result elements: - - - - - - - - -
Extruded element Result element
Node Segment
Segment Quadrilateral
Triangle Pentahedron
Quadrilateral Hexahedron
Polygon Polyhedron
Hexagonal polygon Hexagonal prism
- -When 2D elements are extruded, in addition to 3D elements segments are -created on the ribs of the resulting 3D mesh. Free edges of input 2D elements -generate logically horizontal rib segments. Logically vertical rib -segments are generated from the nodes belonging to a sole input 2D element -(the figure below illustrates this rule). - -\image html extru_rib_segs.png "Two triangles extruded: no vertical rib segments generated from nodes #2 and #3 as they are shared by both triangles" - -To use extrusion: -

    -
  1. From the \b Modification menu choose the \b Extrusion item or click -"Extrusion" button in the toolbar. - -
    -\image html image91.png -"Extrusion" button -
    - -The following dialog will appear: - -\image html extrusionalongaline1.png - -
    2. - -
  2. In this dialog: -
      -
    • Use \a Selection button to specify what you are going to - select at a given moment, \b Nodes, \b Edges or \b Faces. - \image html image120.png -
      "Selection" button
      -
      • -
    • Specify \b Nodes, \b Edges and \b Faces, which will be extruded, by one - of following means: -
        -
      • Select the whole mesh, sub-mesh or group activating the - corresponding check-box.
        • -
      • Choose mesh elements with the mouse in the 3D Viewer. It is - possible to select a whole area with a mouse frame.
        • -
      • Input the element IDs directly in Node IDs, Edge - IDs and Face IDs fields. The selected elements will - be highlighted in the viewer, if the mesh is shown there.
        • -
      • Apply Filters. Set filter button allows to apply a - filter to the selection of elements. See more about filters in - the \ref filtering_elements "Selection filters" page.
        • -
      -
      • - -
    • If the Extrusion to Distance radio button is selected -
        -
      • specify the translation vector by which the elements will - be extruded.
        • -
      -
      • - -
    • If the Extrusion Along Vector radio button is selected -\image html extrusionalongaline2.png -
        -
      • specify the components of the \b Vector along which the elements - will be extruded, either directly or by selecting the mesh face (the - normal to the face will define the vector),
        • -
      • specify the \b Distance of extrusion along the vector (it can - be negative).
        • -
      -
      • - -
    • If the Extrusion By Normal radio button is selected, - every node of the selected faces is extruded along the \a average - of the \a normal vectors to the faces sharing the node. (Nodes and - edges cannot be extruded in this mode.) -\image html extrusionalongaline3.png -
        -
      • Specify the \b Distance of extrusion (it can be negative),
        • -
      • Use Along average normal check-box to specify along - which vector the distance is measured. -
          -
        • If it is \a activated the distance is measured along the - average normal mentioned above.
          • -
        • If it is \a deactivated every node is extruded along the - average normal till its intersection with a virtual plane obtained - by translation of the face sharing the node along its own normal - by the \b Distance.
          • -
        - The picture below shows a cross-section of a 2D mesh extruded - with Along average normal activated (to the left) and - deactivated (to the right). - - \image html extrusionbynormal_alongavgnorm.png "'Along average normal' activated (to the left) and deactivated (to the right)" -

        • - -
      • Use only input elements check-box specifies what - elements will be used to compute the average normal.
          -
        • If it is \a activated only selected faces, among faces - sharing the node, are used to compute the average normal at - the node.
          • -
        • Else all faces sharing the node are used.
        - - The picture below shows a cross-section of a 2D mesh the upper - plane of which is extruded with Use only input elements - activated (to the left) and deactivated (to the right). - - \image html extrusionbynormal_useonly.png "'Use only input elements' activated (to the left) and deactivated (to the right)" -

        • - -
      - -
    • Specify the Number of steps.
      • - -
    • Optionally specify Scale Factors. Each scale factor in - the list is applied to nodes of a corresponding extrusion step - unless Linear Variation of Scale Factors is checked, is - which case the scale factors are spread over all extrusion steps.
      • -
        -
      • Scaling Center can be defined either using spin boxes - or by picking a node in the Viewer or by picking a geometrical - vertex in the Object Browser.
        • -
      • \b Add button adds a scale factor to the list. - \image html add.png -
        "Add" button
        -
        • -
      • \b Remove button removes selected scale factors from the list. - \image html remove.png -
        "Remove" button
        -
        • -
      - -
    • If you activate Generate Groups check-box, the result elements - created from selected elements contained in groups will be - included into new groups named by pattern "_extruded" and "_top". For example if a - selected quadrangle is included in \a g_Faces group (see figures - below) then result hexahedra will be included in \a - g_Faces_extruded group and a quadrangle created at the "top" of - extruded mesh will be included in \a g_Faces_top group.
      -\image html extrusion_groups.png -\image html extrusion_groups_res.png -

      This check-box is active only if there are some groups in the mesh. -

      • -
    - -
  3. Click \b Apply or Apply and Close button to confirm the operation.
    4. -
-

- -\anchor extrusion_struct -

Example: creation of a structured mesh from scratch

- -\image html image75.jpg "A node is extruded into a line of segments" -
-\image html image76.jpg "The line of segments is extruded into a quadrangle mesh" -
-\image html image77.jpg "The quadrangle mesh is revolved into a hexahedral mesh" - - -
See Also a sample TUI Script of an -\ref tui_extrusion "Extrusion" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/extrusion_along_path.doc b/doc/salome/gui/SMESH/input/extrusion_along_path.doc deleted file mode 100644 index ca782049a..000000000 --- a/doc/salome/gui/SMESH/input/extrusion_along_path.doc +++ /dev/null @@ -1,176 +0,0 @@ -/*! - -\page extrusion_along_path_page Extrusion along Path - -\n In principle, Extrusion along Path works in the same way -as \ref extrusion_page "Extrusion", the main difference is that we -define not a vector, but a path of extrusion which must be an 1D mesh -or 1D sub-mesh. -To get an idea of how this algorithm works, examine several examples, -starting from the most simple case of extrusion along a straight edge. -In the examples the sample mesh will be extruded along different -paths and with different parameters. -This 2D mesh has two quadrangle faces and seven edges. Look -at the picture, where white digits are the node numbers and green -are the element numbers: - -\image html mesh_for_extr_along_path.png - -

Extrusion along a straight edge

(not using base point -or angles)
- -\image html straight_before.png -
The image shows a 1D path mesh, built on a linear edge, and the initial 2D mesh.
- -\image html straight_after.png -
The image shows the result of extrusion of two edges -(#1 and #2) of the initial mesh along the path. \n Node #1 of path mesh -has been selected as Start node.
- -

Extrusion along a curvilinear edge

(with and -without angles)
- -\image html curvi_simple_before.png -
The image shows a 1D path mesh, built on curvilinear edge, and -the initial 2D mesh.
- -\image html curvi_simple_after.png -
The central image shows the result of extrusion of one edge -(#2) of the initial mesh along the path. \n Node #1 of path mesh has -been selected as Start node.
- -\image html curvi_angles_after.png -
The same, but using angles {45, 45, 45, 0, -45, -45, -45}
- -

Extrusion of a 2D face along a mesh built on a wire

- -In this example the path mesh has been built on a wire containing 3 -edges. Node 1 is a start node. Linear angle variation by 180 degrees -has also been applied. - -\image html extr_along_wire_before.png -
Meshed wire
- -\image html extr_along_wire_after.png -
The resulting extrusion
- -

Extrusion of 2d elements along a closed path

- -\image html circle_simple_before.png -
The image shows a path mesh built on a closed edge -(circle).
- -\image html circle_simple_after.png -
The central image shows the result of extrusion of both faces -of the initial mesh. \n Note, that no sewing has been done, so, there are -six coincident nodes and two coincident faces in the resulting -mesh.
- -\image html circle_angles_after.png -
The same, but using angles {45, -45, 45, -45, 45, -45, 45, -45} -
- -
To use Extrusion along Path: -
    -
  1. From the \b Modification menu choose the Extrusion along a -path item or click "Extrusion along a path" button in the toolbar. - -\image html image101.png -
    "Extrusion along a path" button
    - -The following dialog will appear: - -\image html extrusion_along_path_dlg.png -
    2. - -
  2. In this dialog: -
      -
    • Use \a Selection button to specify what you are going to - select at a given moment, \b Nodes, \b Edges or \b Faces. -\image html image120.png -
      "Selection" button
      -
      • -
    • Specify \b Nodes, \b Edges and \b Faces, which will be extruded, by one - of following means: -
        -
      • Select the whole mesh, sub-mesh or group activating this - check-box.
        • -
      • Choose mesh elements with the mouse in the 3D Viewer. It is - possible to select a whole area with a mouse frame.
        • -
      • Input the element IDs directly in Node IDs, Edge - IDs and Face IDs fields. The selected elements will - be highlighted in the viewer, if the mesh is shown there.
        • -
      • Apply Filters. Set filter button allows to apply a - filter to the selection of elements. See more about filters in - the \ref filtering_elements "Selection filters" page.
        • -
      -
      • -
    • Define the \b Path along which the elements will be extruded.
      - Path definition consists of several elements: -
        -
      • Mesh or sub-mesh - 1D mesh or sub-mesh, along which - proceeds the extrusion.
        • -
      • Start node - the start node of the Path. It is used - to define the direction of extrusion.
        • -
      -
      • -
    • If you activate Generate Groups check-box, the result elements - created from selected elements contained in groups will be - included into new groups named by pattern "_extruded" and "_top". For example if a - selected quadrangle is included in \a g_Faces group (see figures - below) then result hexahedra will be included in \a - g_Faces_extruded group and a quadrangle created at the "top" of - extruded mesh will be included in \a g_Faces_top group.
      -\image html extrusion_groups.png -\image html extrusion_groups_res.png -

      This check-box is active only if there are some groups in the mesh. -

      • -
    -
    3. - -
  3. There are two optional parameters, which can be very useful: -
      -
    • If the path of extrusion is curvilinear, at each iteration the - extruded elements are rotated to keep its initial angularity to the - curve. By default, the Base Point around which the elements - are rotated is the mass center of the elements (note that it can - differ from the gravity center computed by \a Geometry module for the - underlying shape), however, you can specify any point as the Base - Point and the elements will be rotated with respect to this - point.
      - Note that only the displacement of the Base Point exactly - equals to the path, and all other extruded elements simply keep - their position relatively to the Base Point at each - iteration.
      • -
    • The elements can also be rotated around the path to get the - resulting mesh in a helical fashion. You can set the values of - angles at the right, add them to the list of angles at the left by - pressing the "Add" button and remove them from the list by - pressing the "Remove" button. -\image html add.png -
      "Add" button
      -\image html remove.png -
      "Remove" button
      - -Linear variation of the angles option allows defining the angle -of gradual rotation for the whole path. At each step the elements will -be rotated by ( angle / nb. of steps ). -
      • -
    -
    4. - - -
  4. Click \b Apply or Apply and Close button to confirm the - operation. Mesh edges will be extruded into faces, faces into - volumes. The external surface of the resulting 3d mesh (if faces - have been extruded) is covered with faces, and corners with - edges. If the path is closed, the resulting mesh can contain - duplicated nodes and faces, because no sewing is done. -
    5. -
- -
See Also a sample TUI Script of an -\ref tui_extrusion_along_path "Extrusion along a Path" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/find_element_by_point.doc b/doc/salome/gui/SMESH/input/find_element_by_point.doc deleted file mode 100644 index 191aa4307..000000000 --- a/doc/salome/gui/SMESH/input/find_element_by_point.doc +++ /dev/null @@ -1,41 +0,0 @@ -/*! - -\page find_element_by_point_page Find Element by Point - -\n This functionality allows you to find all mesh elements to which -belongs a certain point. - -To find the elements: -
    -
  1. Select a mesh or a group
    2. -
  2. Select from the Mesh menu or from the context menu the Find -Element by Point item. - -\image html findelement3.png -
    "Find Element by Point" button
    - -The following dialog box will appear: - -\image html findelement2.png - -
    3. -
  3. In this dialog box you should select: - -
      -
    • the coordinates of the point;
      • -
    • the type of elements to be found; it is also possible to find elements -of all types related to the reference point. Choose type "All" to find -elements of any type except for nodes and 0D elements.
      • -
    - -
    4. -
  4. Click the \b Find button. -
- -\image html findelement1.png -
The reference point and the related elements.
- - -
See Also a sample TUI Script of a \ref tui_find_element_by_point "Find Element by Point" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/free_borders.doc b/doc/salome/gui/SMESH/input/free_borders.doc deleted file mode 100644 index 3a8497c30..000000000 --- a/doc/salome/gui/SMESH/input/free_borders.doc +++ /dev/null @@ -1,17 +0,0 @@ -/*! - -\page free_borders_page Free borders - -\n This mesh quality control highlights 1D elements (segments) -belonging to one element (face or volume) only. - -\image html free_borders1.png - -In this picture the free borders are displayed in red. (Faces are -explicitly shown via Display Entity menu as all elements but -segments are hidden upon this control activation). - -
See Also a sample TUI Script of a -\ref tui_free_borders "Free Borders quality control" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/free_edges.doc b/doc/salome/gui/SMESH/input/free_edges.doc deleted file mode 100644 index 2e9d4a6ec..000000000 --- a/doc/salome/gui/SMESH/input/free_edges.doc +++ /dev/null @@ -1,15 +0,0 @@ -/*! - -\page free_edges_page Free edges - -\n This mesh quality control highlights borders of faces -(links between nodes, not mesh segments) belonging to one face only. - -\image html free_edges.png -
In this picture some elements of mesh have been deleted and -the "holes" are outlined in red.
- -
See Also a sample TUI Script of a -\ref tui_free_edges "Free Edges quality control" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/free_faces.doc b/doc/salome/gui/SMESH/input/free_faces.doc deleted file mode 100644 index d35caa9ac..000000000 --- a/doc/salome/gui/SMESH/input/free_faces.doc +++ /dev/null @@ -1,18 +0,0 @@ -/*! - -\page free_faces_page Free faces - -This mesh quality control highlights the faces connected to -less than two mesh volume elements. The free faces are shown with a -color different from the color of shared faces. - -\image html free_faces.png - -In this picture some volume mesh elements have been removed, as -a result some faces became connected only to one -volume. i.e. became free. - -\sa A sample TUI Script of a \ref tui_free_faces "Free Faces quality control" -operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/free_nodes.doc b/doc/salome/gui/SMESH/input/free_nodes.doc deleted file mode 100644 index 8a06fe3de..000000000 --- a/doc/salome/gui/SMESH/input/free_nodes.doc +++ /dev/null @@ -1,16 +0,0 @@ -/*! - -\page free_nodes_page Free nodes - -This mesh quality control highlights the nodes which are not connected -to any mesh element. - -\image html free_nodes.png - -In this picture some nodes are not connected to any mesh -element after deleting some elements and adding several isolated nodes. - -\sa A sample TUI Script of a \ref tui_free_nodes "Free Nodes quality control" -operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/generate_flat_elements.doc b/doc/salome/gui/SMESH/input/generate_flat_elements.doc deleted file mode 100644 index 7cfdbf90b..000000000 --- a/doc/salome/gui/SMESH/input/generate_flat_elements.doc +++ /dev/null @@ -1,12 +0,0 @@ -/*! - -\page generate_flat_elements_page Generate flat elements on group boundaries or on faces - -\n These functionalities, used in some mechanics calculations, -allow to generate flat volume elements on the boundaries of a list -of groups of volumes, or on a list of groups of faces. -\n These functionalities are only available in python scripts. - -
See a sample TUI Script of \ref tui_double_nodes_on_group_boundaries "Generate flat elements" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/group_of_underlying_elements.doc b/doc/salome/gui/SMESH/input/group_of_underlying_elements.doc deleted file mode 100755 index 7d31f7350..000000000 --- a/doc/salome/gui/SMESH/input/group_of_underlying_elements.doc +++ /dev/null @@ -1,51 +0,0 @@ -/*! - -\page group_of_underlying_elements_page Group Based on Nodes of Other Groups - - -To create a standalone group of entities basing on nodes of existing -reference groups, in the \b Mesh menu select Group of underlying entities. - -The following dialog box will appear: - -\image html dimgroup_dlg.png - -In this dialog box specify - -In the figure below, there are two reference Volume groups: - -\image html dimgroup_src.png -
Reference groups
- -In this case the following results for Faces, Edges and Nodes are obtained: - -\image html dimgroup_2d.png -
Faces
- -\image html dimgroup_1d.png -
Edges
- -\image html dimgroup_0d.png -
Nodes
- -See Also a sample TUI Script of a -\ref tui_create_dim_group "Creating groups basing on nodes of other groups" -operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/grouping_elements.doc b/doc/salome/gui/SMESH/input/grouping_elements.doc deleted file mode 100644 index 7d738c8ee..000000000 --- a/doc/salome/gui/SMESH/input/grouping_elements.doc +++ /dev/null @@ -1,83 +0,0 @@ -/*! - -\page grouping_elements_page Grouping elements - -In Mesh module it is possible to create groups of mesh entities: -nodes, edges, faces, volumes, 0D elements or balls. One group contains -elements of only one type. Groups, unlike sub-meshes, are exported -along with mesh entities into the files of following formats: MED, UNV, -and CGNS. The group has a color attribute which is used for -visualization only and is not exported. - -There are three types of groups different by their internal -organization:
    -
  1. Standalone group is a static set of mesh entities. Its - contents can be explicitly controlled by the user. Upon removal of - the entities included into the group, e.g. due to modification of - meshing parameter, the group becomes empty and its content can be - restored only manually. Hence it is reasonable to create standalone - groups when the mesh generation is finished and mesh quality is - verified. - \warning Creation and edition of large standalone groups in - \ref creating_groups_page "Create group" dialog using manual edition - is problematic due to poor performance of the dialog.
    2. - -
  2. Group on geometry is associated to a sub-shape or a group of - sub-shapes of the main shape and includes mesh entities generated on - these geometrical entities. The association to a geometry is - established at group construction and cannot be changed. The group - contents are always updated automatically, hence the - group can be created even before mesh elements generation.
    3. -
  3. Group on filter encapsulates a \ref filters_page "filter", - which is used to select mesh entities composing the group from the - whole mesh. Criteria of the filter can be changed at any time. The - group contents are always updated automatically, hence the group can - be created even before mesh elements generation.
    4. -
-The group on geometry and group on filter can be converted to -a standalone group. - -\image html groups_in_OB.png "Groups of different types look differently in the Object Browser" - -The following ways of group creation are possible: - -- \subpage creating_groups_page "Create group" dialog allows creation of - a group of any type: - \ref standalone_group "Standalone group", - \ref group_on_geom "Group on geometry" and - \ref group_on_filter "Group on filter" using dedicated tabs. -- \subpage create_groups_from_geometry_page "Create Groups from Geometry" - dialog allows creation of several groups on geometry at once. -- Standalone groups of all nodes and elements of the chosen sub-mesh - (type of elements depends on dimension of sub-mesh geometry) can - be created using Mesh -> Construct Group menu item (available - from the context menu as well). -- Standalone groups of any element type can be created basing on nodes - of other groups - using \subpage group_of_underlying_elements_page - "Group based on nodes of other groups" dialog. -- Standalone groups can be created by applying - \subpage using_operations_on_groups_page "Boolean operations" to - other groups. -- Creation of standalone groups is an option of many - \ref modifying_meshes_page "mesh modification" operations. - -The created groups can be later: - -- \subpage editing_groups_page "Edited" -- \subpage deleting_groups_page "Deleted", either as an object or - together with contained elements. -- The group on geometry and group on filter can be - \ref convert_to_standalone "converted into the standalone" group. -- \ref importing_exporting_meshes_page "Exported" into a file as a - whole mesh. - -In the Object Browser, if an item contains more than one child group, -it is possible to sort the groups by name in ascending order -using Sort children context menu item. - -\image html smesh_sort_groups.png "Sorting groups" - -An important tool, providing filters for creation of standalone -groups and groups on filter is \ref selection_filter_library_page. - -*/ diff --git a/doc/salome/gui/SMESH/input/importing_exporting_meshes.doc b/doc/salome/gui/SMESH/input/importing_exporting_meshes.doc deleted file mode 100644 index a4a8d3ca2..000000000 --- a/doc/salome/gui/SMESH/input/importing_exporting_meshes.doc +++ /dev/null @@ -1,71 +0,0 @@ -/*! - -\page importing_exporting_meshes_page Importing and exporting meshes - -\n In MESH there is a functionality allowing import/export -of meshes from/to \b MED, \b UNV (I-DEAS 10), \b DAT (simple ascii format), \b STL, -\b GMF (internal format of DISTENE products, namely MG-CADSurf, MG-Tetra and -MG-Hexa algorithms) and \b CGNS format files. You can also export a -group as a whole mesh. - - -To import a mesh: - -
    -
  1. From the \b File menu choose the \b Import item, from its sub-menu - select the corresponding format (MED, UNV, STL, GMF and CGNS) of the - file containing your mesh.
    2. -
  2. In the standard Search File dialog box find the file for - import. It is possible to select multiple files to be imported all at - once.
    3. - -
  3. Click the \b OK button.
    4. -
- -\image html meshimportmesh.png - -To export a mesh or a group: - -
    -
  1. Select the object you wish to export.
    2. -
  2. From the \b File menu choose the \b Export item, from its sub-menu - select the format (MED, UNV, DAT, STL, GMF and CGNS) of the file which will - contain your exported mesh.
    3. -
  3. In the standard Search File select a location for the - exported file and enter its name.
    4. -
  4. Click the \b OK button.
    5. -
- -\image html meshexportmesh.png - - If you try to export a group, the warning will be shown: -\image html meshexportgroupwarning.png - - - There are additional parameters available at export to MED and SAUV format files. - -
See Also a sample TUI Script of an \ref tui_export_mesh "Export Mesh" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/index.doc b/doc/salome/gui/SMESH/input/index.doc deleted file mode 100644 index e2762515b..000000000 --- a/doc/salome/gui/SMESH/input/index.doc +++ /dev/null @@ -1,52 +0,0 @@ -/*! - -\mainpage Introduction to Mesh module - -\image html a-viewgeneral.png - -\n \b Mesh module of SALOME is destined for: - - -It is possible to use the variables predefined in -\subpage using_notebook_mesh_page "Salome notebook" to set parameters -of operations. - -Mesh module preferences are described in the \subpage mesh_preferences_page -section of SALOME Mesh Help. - -Almost all mesh module functionalities are accessible via -\subpage smeshpy_interface_page "Mesh module Python interface". - -There is a set of \subpage tools_page "tools" plugged-in the module to extend -the basic functionality listed above. - -\image html image7.jpg "Example of MESH module usage for engineering tasks" - -*/ diff --git a/doc/salome/gui/SMESH/input/introduction.rst b/doc/salome/gui/SMESH/input/introduction.rst index a5a9a1465..9d94c31f2 100644 --- a/doc/salome/gui/SMESH/input/introduction.rst +++ b/doc/salome/gui/SMESH/input/introduction.rst @@ -7,7 +7,7 @@ Introduction to Mesh module **Mesh** module of SALOME is destined for: -* :ref:`about_meshes_page` in different ways: +* :ref:`creating meshes ` in different ways: * by meshing geometrical models previously created or imported by the Geometry component; * bottom-up, using :ref:`modifying_meshes_page`, especially :ref:`extrusion_page` and :ref:`revolution_page`; * by generation of the 3D mesh from the 2D mesh not based on the geometry (:ref:`importing_exporting_meshes_page` for example); diff --git a/doc/salome/gui/SMESH/input/length.doc b/doc/salome/gui/SMESH/input/length.doc deleted file mode 100644 index e8210294d..000000000 --- a/doc/salome/gui/SMESH/input/length.doc +++ /dev/null @@ -1,13 +0,0 @@ -/*! - -\page length_page Length - -\n Length quality control criterion returns a value of length of -edge. - -\image html length-crit.png - -
See Also a sample TUI Script of a -\ref tui_length_1d "Length quality control" operation. - -*/ \ No newline at end of file diff --git a/doc/salome/gui/SMESH/input/length_2d.doc b/doc/salome/gui/SMESH/input/length_2d.doc deleted file mode 100644 index b3599ae29..000000000 --- a/doc/salome/gui/SMESH/input/length_2d.doc +++ /dev/null @@ -1,28 +0,0 @@ -/*! - -\page length_2d_page Length 2D - -\n This quality control criterion consists of calculation of length of -the links between corner nodes of mesh faces. - -To apply the Length 2D quality criterion to your mesh: -
    -
  1. Display your mesh in the viewer.
    2. - -
  2. Choose Controls > Face Controls > Length 2D or click -"Length 2D" button in the toolbar. - -\image html image34.png -
    "Length 2D" button
    - -Your mesh will be displayed in the viewer with links colored according -to the applied mesh quality control criterion: - -\image html length2d.png -
    3. -
- -
See Also a sample TUI Script of a -\ref tui_length_2d "Length 2D quality control" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/make_2dmesh_from_3d.doc b/doc/salome/gui/SMESH/input/make_2dmesh_from_3d.doc deleted file mode 100644 index 3dfec30d5..000000000 --- a/doc/salome/gui/SMESH/input/make_2dmesh_from_3d.doc +++ /dev/null @@ -1,55 +0,0 @@ -/*! - -\page make_2dmesh_from_3d_page Generate boundary elements - -\n This functionality allows to generate mesh elements on the borders of -elements of a higher dimension, for example, to create 2D elements -around a block of 3D elements as in the following figure. - -\image html 2d_from_3d_example.png "Missing 2D elements were generated" - -To generate border elements: -
    -
  1. Select a mesh or group in the Object Browser or in the 3D Viewer
    2. -
  2. From the Modification menu choose "Create boundary elements" -item, or click "Create boundary elements" button in the toolbar - -\image html 2d_from_3d_ico.png "Create boundary elements icon" - -The following dialog box will appear: -\image html 2d_from_3d_dlg.png "Create boundary elements dialog box". -
    3. -
  3. Check in the dialog box one of two radio buttons corresponding to -the type of operation you would like to perform.
    4. -
  4. Fill the other fields available in the dialog box.
    5. -
  5. Click the \b Apply or Apply and Close button to perform the operation.
    6. -
- -\n "Create boundary elements" dialog allows creation of boundary elements -of two types. - -Here a free facet means a facet shared by only one volume, a free edge -means an edge shared by only one mesh face. - -In this dialog: - -
See Also a sample TUI Script of a \ref tui_make_2dmesh_from_3d "Create boundary elements" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/max_element_length_2d.doc b/doc/salome/gui/SMESH/input/max_element_length_2d.doc deleted file mode 100644 index e4e2ce9a8..000000000 --- a/doc/salome/gui/SMESH/input/max_element_length_2d.doc +++ /dev/null @@ -1,29 +0,0 @@ -/*! - -\page max_element_length_2d_page Element Diameter 2D - -\n This quality control criterion consists in calculation of the maximal length of -edges and diagonals of 2D mesh elements (triangles and quadrangles). For polygons -the value is always zero. - -To apply the Element Diameter 2D quality criterion to your mesh: -
    -
  1. Display your mesh in the viewer.
    2. - -
  2. Choose Controls > Face Controls > Element Diameter 2D or click -"Element Diameter 2D" button in the toolbar. - -\image html image42.png -
    "Element Diameter 2D" button
    - -Your mesh will be displayed in the viewer with its elements colored according to the -applied mesh quality control criterion: - -\image html max_element_length_2d.png -
    3. -
- -
See Also a sample TUI Script of a -\ref tui_max_element_length_2d "Element Diameter 2D quality control" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/max_element_length_3d.doc b/doc/salome/gui/SMESH/input/max_element_length_3d.doc deleted file mode 100644 index 837f6aa6f..000000000 --- a/doc/salome/gui/SMESH/input/max_element_length_3d.doc +++ /dev/null @@ -1,29 +0,0 @@ -/*! - -\page max_element_length_3d_page Element Diameter 3D - -\n This quality control criterion consists in calculation of the maximal length of -edges and diagonals of 3D mesh elements (tetrahedrons, pyramids, etc). For polyhedra -the value is always zero. - -To apply the Element Diameter 3D quality criterion to your mesh: -
    -
  1. Display your mesh in the viewer.
    2. - -
  2. Choose Controls > Volume Controls > Element Diameter 3D or click -"Element Diameter 3D" button in the toolbar. - -\image html image43.png -
    "Element Diameter 3D" button
    - -Your mesh will be displayed in the viewer with its elements colored according to the -applied mesh quality control criterion: - -\image html max_element_length_3d.png -
    3. -
- -
See Also a sample TUI Script of a -\ref tui_max_element_length_3d "Element Diameter 3D quality control" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/max_element_volume_hypo.doc b/doc/salome/gui/SMESH/input/max_element_volume_hypo.doc deleted file mode 100644 index 1dd459161..000000000 --- a/doc/salome/gui/SMESH/input/max_element_volume_hypo.doc +++ /dev/null @@ -1,16 +0,0 @@ -/*! - -\page max_element_volume_hypo_page Max Element Volume hypothesis - -\n Max Element Volume hypothesis is applied for meshing of 3D objects -composing your geometrical object. Definition of this hypothesis -consists of setting the maximum volume of 3D meshing elements -(depending on the chosen meshing algorithm it can be \b hexahedrons or -\b tetrahedrons), which will compose the mesh of these 3D objects. - -\image html a-maxelvolume.png - -
See Also a sample TUI Script of a -\ref tui_max_element_volume "Maximum Element Volume hypothesis" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/measurements.doc b/doc/salome/gui/SMESH/input/measurements.doc deleted file mode 100644 index bfedbe0c8..000000000 --- a/doc/salome/gui/SMESH/input/measurements.doc +++ /dev/null @@ -1,89 +0,0 @@ -/*! - -\page measurements_page Measurements - -Mesh module provides the possibility to perform different measurements -of the selected mesh data. - -All measurement operations are available via \b Measurements -top-level menu. Access to the measurements operations is -implemented via a single dialog box, where each operation is represented -as a separate tab page. - -\section min_distance_anchor Minimum Distance - -This operation allows measuring the distance between two objects. -Currently only node-to-node and node-to-origin operations are -available, but this operation will be extended in the future to support -other mesh objects - elements, meshes, sub-meshes and groups. - -To start Minimum Distance operation, select Minimum Distance -tab in \b Measurements dialog. - -\image html min_distance.png - -Choose the first and the second target by -switching the corresponding radio buttons, then select the objects the distance -between which is to be calculated (or input their IDs directly -in case of nodes/elements) and press \b Compute button. - -The following targets are supported: -- \b Node: single mesh node; -- \b Element: single mesh element (not available in this version); -- \b Object: mesh, sub-mesh or group object (not available in this -version); -- \b Origin: origin of the global co-ordinate system. - -The result will be shown in the bottom area of the dialog. In addition, a simple -preview will be shown in the 3D viewer. - -\image html min_distance_preview.png - -\section bounding_box_anchor Bounding Box - -This operation allows calculating the bounding box of the selected -object(s). - -To start Bounding Box operation, select Bounding Box -tab in \b Measurements dialog. - -\image html bnd_box.png - -Choose the required type of the object by switching the corresponding radio button, select the object(s) and press \em Compute button. - -The following types of input are available: -- \b Objects: one or several mesh, sub-mesh or group objects; -- \b Nodes: a set of mesh nodes; -- \b Elements: a set of mesh elements. - -The result of calculation will be shown in the bottom area of the -dialog. In addition, a simple preview will be shown in the 3D viewer. - -\image html bnd_box_preview.png - -\section basic_properties_anchor Basic Properties - -This operation provides calculation of length, area or volume for the the selected object: -- \b Length is calculated as a sum of lengths of all 1D elements; -- \b Area is a sum of areas of all 2D elements -- \b Volume is a sum of volumes of all 3D elements. - -To start a Basic Properties calculation, select Length, Area or Volume item. - -\image html basic_props.png - -In the dialog box select the required type of calculation (length, area or volume) and the object (mesh, sub-mesh or group) and press \b Compute button. - -The result of calculation will be shown in the bottom area of the dialog. - -\note -- If the mesh consists of 3D elements only, its "length" and "area" will be 0. -- As calculation result is a sum of lengths, areas and volumes of all mesh elements, the - duplication is not taken into account; i.e. all duplicated elements - (elements built on the same set of nodes) will be included into the result. -- Similarly, intersection of elements is not taken into account. - -See Also a sample TUI Script of -\ref tui_measurements_page "Measurement operations". - -*/ diff --git a/doc/salome/gui/SMESH/input/merging_elements.doc b/doc/salome/gui/SMESH/input/merging_elements.doc deleted file mode 100644 index 6236ad02b..000000000 --- a/doc/salome/gui/SMESH/input/merging_elements.doc +++ /dev/null @@ -1,71 +0,0 @@ -/*! - -\page merging_elements_page Merging Elements - -\n This functionality allows to merge coincident elements of a -mesh. Two elements are considered coincident if they are based on the -same set of nodes. - -\image html mergeelems_ico.png "Merge elements menu button" - -To merge elements choose in the main menu \b Modification -> \b Transformation --> Merge elements item. The following dialog box shall -appear: - -\image html mergeelems_auto.png - -In this dialog: - - -In this picture you see a triangle which coincides with one of the -elements of the mesh. After we apply Merge Elements functionality, the -triangle will be completely merged with the mesh. - -\image html meshtrianglemergeelem1.png - -
See Also a sample TUI Script of a -\ref tui_merging_elements "Merge Elements" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/merging_nodes.doc b/doc/salome/gui/SMESH/input/merging_nodes.doc deleted file mode 100644 index 872f9eeed..000000000 --- a/doc/salome/gui/SMESH/input/merging_nodes.doc +++ /dev/null @@ -1,114 +0,0 @@ -/*! - -\page merging_nodes_page Merging nodes - -This functionality allows user to detect groups of coincident nodes -with specified tolerance; each group of the coincident nodes can be -then converted to the single node. - -\image html mergenodes_ico.png "Merge nodes menu button" - -To merge nodes of your mesh: -
    -
  1. Choose \b Modification -> \b Transformation -> Merge nodes - menu item. The following dialog box shall appear:
    2. -
    -\image html mergenodes_auto.png -
    -
      -
    • \b Name is the name of the mesh whose nodes will be merged.
      • -
    • \b Automatic or \b Manual mode allows choosing how the nodes are - processed. In \b Manual mode you can adjust groups of coincident nodes - detected by the program and/or select any nodes to be merged.
      • -
    • \b Tolerance is a maximum distance between nodes sufficient for -merging.
      • -
    • Activation of No merge of corner and medium nodes of quadratic - cells check-box prevents merging medium nodes of quadratic - elements with corner nodes. This check-box is enabled provided - that the selected mesh includes quadratic elements.
      • -
    • Activation of Avoid making holes check-box prevents merging - nodes that make elements invalid (but not degenerated) and hence - removed. Thus, no holes in place of removed elements appear.
      • -
    • Exclude groups from detection group allows to ignore the - nodes which belong to the specified mesh groups. This control is - active provided that the mesh includes groups.
      • -
    • Nodes to keep during the merge group allows to specify - nodes to keep in the mesh. (By default a node being the first in a - group of coincident nodes is kept.) It is possible to either select - nodes in the Viewer or select groups of any element type whose nodes - will be kept. -
        -
      • \a Selection button activates selection of nodes to keep.
        • -
      • Nodes button activates selection of nodes in the - Viewer.
        • -
      • Groups and sub-meshes button activates selection of - groups and sub-meshes.
        • -
      • \b Add button adds selected nodes or groups to the list.
        • -
      • Nodes or groups selected in the list can be removed using \b - Remove button.
        • -
      -
      • -
    - -
  2. Automatic mode: -
    -
      -
    • In the \b Automatic Mode all nodes within the indicated tolerance -will be merged. The nodes which belong to the groups specified in -Exclude groups from detection will NOT be taken into account.
      • -
    -

    3. -
  3. The \b Manual mode gives you full control of what the operation will do. -In this mode additional controls are available: -
      -
    • \b Detect button generates the list of coincident nodes for the given - \b Tolerance.
      • -
    • Coincident nodes is a list of groups of nodes for - merging. Upon \b Apply all nodes of each group will - be united into one node. The first node of a group is kept and - the others are removed. By default the first node has a lowest ID - within the group. -
        -
      • \b Remove button deletes the selected group from the list.
        • -
      • \b Add button adds to the list a group of nodes selected in the -viewer.
        • -
      • Select all check-box selects all groups.
        • -
      • Show double nodes IDs check-box shows/hides identifiers of -nodes of selected groups in the 3D viewer.
        • -
      - -
      -\image html mergenodes.png -
      -
      • -
    • Edit selected group of coincident nodes list allows - editing the selected group: -

      - \image html add.png -
      adds to the group the nodes selected in the viewer.
      -
      - \image html remove.png -
      removes from the group the selected nodes.
      -
      - \image html sort.png -
      moves the selected node to the first position in the - group in order to keep it in the mesh.

      -
      • -
    -
    4. -
  4. To confirm your choice click \b Apply or Apply and Close button.
    5. -
- -\image html merging_nodes1.png -
The initial object. Nodes 25, 26 and 5 are added to Nodes - to keep during the merge group. -
-
-\image html merging_nodes2.png -
The object has been merged -
- -
See Also a sample TUI Script of a -\ref tui_merging_nodes "Merge Nodes" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/mesh_infos.doc b/doc/salome/gui/SMESH/input/mesh_infos.doc deleted file mode 100644 index e20375251..000000000 --- a/doc/salome/gui/SMESH/input/mesh_infos.doc +++ /dev/null @@ -1,183 +0,0 @@ -/*! - -\page mesh_infos_page Mesh Information - -The user can obtain information about the selected mesh object -(mesh, sub-mesh or group) using Mesh Information dialog box. - -To view the Mesh Information, select your mesh, sub-mesh or -group in the Object Browser and invoke Mesh Information -item from the \b Mesh menu or from the context menu, or click "Mesh Information" button -in the toolbar. - -
\image html image49.png -"Mesh Information" button
- -The Mesh Information dialog box provides three tab pages: -- \ref advanced_mesh_infos_anchor "Base Info" - to show - base and quantitative information about the selected mesh object. -- \ref mesh_element_info_anchor "Element Info" - to show - detailed information about the selected mesh nodes or elements. -- \ref mesh_addition_info_anchor "Additional Info" - to show - additional information available for the selected mesh, sub-mesh or - group object. -- \ref mesh_quality_info_anchor "Quality Info" - to show - overall quality information about the selected mesh, sub-mesh or group - object. - -\anchor dump_mesh_infos -The button \b Dump allows printing the information displayed in the -dialog box to a .txt file. The dialog for choosing a file also allows -to select which tab pages to dump via four check-boxes. The default state -of the check-boxes can be changed via \ref mesh_information_pref "Mesh information" -preferences. - -\anchor advanced_mesh_infos_anchor -

Base Information

- -The Base Info tab page of the dialog box provides general -information on the selected object - mesh, sub-mesh or mesh group: -name, type, total number of nodes and elements separately for each -type: 0D elements, edges, faces, volumes, balls. - -
\image html advanced_mesh_infos.png -"Base Info" page
- -\anchor mesh_element_info_anchor -

Mesh Element Information

- -The Element Info tab page of the dialog box gives detailed -information about the selected mesh node(s) or element(s), namely: - -- For a node: - - Node ID; - - Coordinates (X, Y, Z); - - Connectivity information (connected elements); double click in - this line reveals information about these elements; - - Position on a shape (for meshes built on a geometry); - - Groups information (names of groups the node belongs to). - -
\image html eleminfo1.png -"Element Info" page, node information
-
- -- For an element: - - Element ID; - - Type (triangle, quadrangle, etc.); - - Gravity center (X, Y, Z coordinates); - - Connectivity information (connected nodes); double click in - a line of a node reveals the information about this node; - - Quality controls (area, aspect ratio, volume, etc.); - - Position on a shape (for meshes built on a geometry); - - Groups information (names of groups the element belongs to). - -
\image html eleminfo2.png -"Element Info" page, element information
- -The user can either input the ID of a node or element he wants to -analyze directly in the dialog box or select the node(s) or element(s) in -the 3D viewer. - -If Show IDs is activated, IDs of selected nodes or elements are -displayed in the 3D viewer. - -\note The information about the groups, to which the node or element belongs, -can be shown in a short or in a detailed form. By default, for performance -reasons, this information is shown in a short form (group names -only). The detailed information on groups can be switched on via -\ref group_detail_info_pref "Show details on groups in element information tab" -option of \ref mesh_preferences_page. - -\anchor mesh_addition_info_anchor -

Additional Information

- -The Additional Info tab page of the dialog box provides an -additional information on the selected object: mesh, sub-mesh or -group. - -For a mesh object, the following information is shown: -- Name -- Type: based on geomerty, imported, standalone -- Shape (if mesh is based on geometry) -- File (if mesh is imported from the file) -- Groups -- Sub-meshes - -
\image html addinfo_mesh.png -"Additional Info" page, mesh information
-
- -For a sub-mesh object, the following information is shown: -- Name -- Parent mesh -- Shape - -
\image html addinfo_submesh.png -"Additional Info" page, sub-mesh information
-
- -\anchor mesh_addition_info_group_anchor -For a group object, the following information is shown: -- Name -- Parent mesh -- Type: standalone, group on geometry, group on filter -- Entity type: node, edge, face, volume -- Size -- Color -- Number of underlying nodes (for non-nodal groups) - -
\image html addinfo_group.png -"Additional Info" page, group information
-
- -\note For the performance reasons, the number of underlying nodes is -computed only by demand. For this, the user should press the "Compute" -button (see picture). Also, the number of underlying nodes is -automatically calculated if the size of the group does not exceed -the \ref nb_nodes_limit_pref "Automatic nodes compute limit" -preference value (zero value means no limit). - -\anchor mesh_quality_info_anchor -

Quality Information

- -The Quality Info tab provides overall information about mesh quality controls on the selected object - mesh, sub-mesh or mesh group: -- Name; -- Nodes information: - - Number of free nodes; - - Maximal number of elements connected to a node; - - Number of double nodes; -- Edges information: - - Number of double edges; -- Faces information: - - Number of double faces; - - Number of over-constrained faces; - - Aspect Ratio histogram; -- Volume information: - - Number of double volumes; - - Number of over-constrained volumes; - - Aspect Ratio 3D histogram. - -
\image html ctrlinfo.png -"Quality Info" page
- -\note It is possible to change Double nodes tolerance, which -will be used upon consequent pressing \a Compute button. The default value -of the tolerance can be set via the -\ref dbl_nodes_tol_pref "Quality controls" preferences. - -\note For performance reasons, all quality control values for big -meshes are computed only by demand. For this, press the \a Compute -button. Also, values are automatically computed if the number of nodes -/ elements does not exceed the -\ref auto_control_limit_pref "Automatic controls compute limit" set -via the \ref mesh_information_pref "Mesh information" preferences -(zero value means that there is no limit). - -\note The plot functionality is available only if the GUI module is -built with Plot 2D Viewer (option SALOME_USE_PLOT2DVIEWER is ON when -building GUI module). - -See the \ref tui_viewing_mesh_infos "TUI Example". - -*/ - diff --git a/doc/salome/gui/SMESH/input/mesh_preferences.doc b/doc/salome/gui/SMESH/input/mesh_preferences.doc deleted file mode 100644 index ea83772f7..000000000 --- a/doc/salome/gui/SMESH/input/mesh_preferences.doc +++ /dev/null @@ -1,294 +0,0 @@ -/*! - -\page mesh_preferences_page Mesh preferences - -In the Mesh module you can set mesh preferences, which can be used right now -or in later sessions with this module according to the preferences. - -

General Preferences

- -\image html pref21.png - -\anchor automatic_update_pref -- Automatic Update - - Automatic Update - if activated, the mesh in your - viewer will be automatically updated after it's computation, depending on - values of additional preferences specified below. - - Size limit (elements) - allows specifying the maximum - number of elements in the resulting mesh for which the automatic updating - of the presentation is performed. This option affects only - \ref compute_anchor "Compute" operation. Zero value means "no - limit". Default value is 500 000 mesh elements. - - Incremental limit check - if activated, - the mesh size limit check is not applied to the total number of - elements in the resulting mesh, it is applied iteratively to each entity type - in the following order: 0D elements, edges, faces, volumes, balls. - At each step the number of entities of a certain type is added to the - total number of elements computed at the previous step - if the resulting - number of elements does not exceed the size limit, the entities of - this type are shown, otherwise the user is warned that some entities are not shown. - -\anchor display_mode_pref -- Display mode - - Default display mode - allows to set Wireframe, Shading, Nodes or Shrink - \ref display_mode_page "presentation mode" as default. - -\anchor quadratic_2d_mode_pref -- Representation of the 2D quadratic elements - - Default mode of the 2D quadratic elements - allows to - select either \a Lines or \a Arcs as a default - \ref quadratic_2d_mode "representation" of 1D and 2D - \ref adding_quadratic_elements_page "quadratic elements". - - Maximum Angle - maximum deviation angle used by the - application to build arcs. - -- Quality Controls - - Display entity - if activated, only currently - \ref quality_page "controlled" entities are displayed in the - viewer and other entities are temporarily hidden. For example if you - activate \ref length_page "Length" quality control, which controls - the length of mesh segments, then only mesh segments are - displayed and faces and volumes are hidden. - - Use precision - if activated, all quality controls - will be computed at precision defined by Number of digits after - point - as integers by default. -\anchor dbl_nodes_tol_pref - - Double nodes tolerance - defines the maximal distance between two - mesh nodes, at which they are considered coincident by - \ref double_nodes_control_page "Double nodes" quality control. - This value is also used in \ref mesh_quality_info_anchor "Quality Info" - tab page of \ref mesh_infos_page dialog. - -- Mesh export -\anchor export_auto_groups_pref - - Automatically create groups for MED export - defines a - default state of a corresponding check-box in \ref export_auto_groups - "MED Export" dialog. -\anchor group_export_warning_pref - - Show warning when exporting group - if activated, a warning is - displayed when exporting a group. - -\anchor show_comp_result_pref -- Mesh computation - - Show a computation result notification - allows to - select the notification mode about a \ref compute_anchor "mesh computation" result. - There are 3 possible modes: - - Never - not to show the \ref meshing_result_anchor "result dialog" at all; - - Errors only - the result dialog will be shown if there were - some errors during a mesh computation; - - Always - show the result dialog after each mesh - computation. This is a default mode. - -\anchor mesh_information_pref -- Mesh information - - Mesh element information - allows changing the way - \ref mesh_element_info_anchor "mesh element information" is shown: - - Simple - as a plain text - - Tree - in a tree-like form -\anchor nb_nodes_limit_pref - - Automatic nodes compute limit - allows defining the size limit for the - \ref mesh_addition_info_group_anchor "mesh groups" for which - the number of underlying nodes is calculated - automatically. If the group size exceeds the value set in the preferences, - the user will have to press \em Compute button explicitly. Zero value - means "no limit". By default the value is set to 100 000 mesh elements. -\anchor auto_control_limit_pref - - Automatic controls compute limit - allows defining a - maximal number of mesh elements for which the quality controls - in the \ref mesh_quality_info_anchor "Quality Information" - tab page are calculated automatically. If the number of mesh elements - exceeds the value set in the preferences, it is necessary to press - \b Compute button explicitly to calculate a quality measure. Zero value - means "no limit". By default the value is set to 3 000 mesh - elements. -\anchor group_detail_info_pref - - Show details on groups in element information tab - when - this option is switched off (default), only the names of groups, to which the node - or element belongs, are shown in the \ref mesh_element_info_anchor "Element Info" - tab of "Mesh Information" dialog box. If this option is - switched on, the detailed information on groups is shown. - - Dump base information - allows dumping base mesh information to the - file, see \ref dump_mesh_infos "Mesh Information". - - Dump element information - allows dumping element information to the - file, see \ref dump_mesh_infos "Mesh Information". - - Dump additional information - allows dumping additional mesh - information to the file, see \ref dump_mesh_infos "Mesh Information". - - Dump controls information - allows dumping quality mesh - information to the file, see \ref dump_mesh_infos "Mesh Information". - -- Automatic Parameters -\anchor diagonal_size_ratio_pref - - Ratio Bounding Box Diagonal / Max Size - defines the ratio - between the bounding box of the meshed object and the Max Size of - segments. It is used as a default value of \ref a1d_meshing_hypo_page - defining length of segments, especially by - \ref max_length_anchor "Max Size" hypothesis. -\anchor nb_segments_pref - - Default Number of Segments - defines the default number of - segments in \ref number_of_segments_anchor "Number of Segments" - hypothesis. - -- Mesh loading - - No mesh loading from study file at hypothesis modification - if - activated, the mesh data will not be loaded from the study file - when a hypothesis is modified. This allows saving time by omitting - loading data of a large mesh that is planned to be recomputed with other parameters. - -- Input fields precision - allows to adjust input precision of - different parameters. The semantics of the precision values is - described in detail in Using input widgets chapter of GUI - documentation (Introduction to Salome Platform / Introduction to GUI / - Using input widgets). In brief: \b positive precision value is the - maximum allowed number of digits after the decimal point in the - fixed-point format; \b nagative precision value is the maximum - allowed number of significant digits in mantissa in either the - fixed-point or scientific format. - - Length precision - allows to adjust input precision of coordinates and dimensions. - - Angular precision - allows to adjust input precision of angles. - - Length tolerance precision - allows to adjust input precision of tolerance of coordinates and dimensions. - - Parametric precision - allows to adjust input precision of parametric values. - - Area precision - allows to adjust input precision of mesh element area. - - Volume precision - allows to adjust input precision of mesh element volume. - -- Preview - - Sub-shapes preview chunk size - allows to limit the number - of previewed sub-shapes shown in the hypotheses creation dialog boxes, - for example "Reverse Edges" parameter of - \ref number_of_segments_anchor "Number of segments" hypothesis. - -- Python Dump - - Historical python dump - allows switching between - \a Historical and \a Snapshot dump mode: - - In \a Historical mode, Python Dump script includes all commands - performed by SMESH engine. - - In \a Snapshot mode, the commands relating to objects removed - from the Study as well as the commands not influencing the - current state of meshes are excluded from the script. - -\anchor mesh_tab_preferences -

Mesh Preferences

- -\b Mesh tab page contains parameters defining the way the mesh is -displayed in the 3D Viewer. - -\image html pref22.png - -- Nodes - allows to define default parameters for nodes, which will be applied - for a newly created mesh only. Existing meshes can be customized using - \ref colors_size_page "Properties dialog box" available from the context menu of a mesh. - - Color - allows to select the color of nodes. Click on the - downward arrow near the colored line to access to the Select Color dialog box. - - Type of marker - allows to define the shape of nodes. - - Scale of marker - allows to define the size of nodes. - -- Elements - allows to define default parameters for different - elements, which will be applied to a newly created mesh - only. Existing meshes can be customized using - \ref colors_size_page "Properties dialog box" available from the context menu of a mesh. - - Surface color - allows to select the surface color of 2D elements - (seen in Shading mode). Click on the downward arrow near the colored line to access to the - Select Color dialog box. - - Back surface color - allows to select the back surface color - of 2D elements. This is useful to differ 2d elements with - reversed orientation. Use the slider to select the color generated basing on - the Surface color by changing its brightness and saturation. - - Volume color - allows to select the surface color of 3D elements - (seen in Shading mode). - - Reversed volume color - allows to select the surface color - of reversed 3D elements. Use the slider to select the color generated basing on - the Volume color by changing its brightness and saturation. - - 0D element color - allows to choose color of 0D mesh elements. - - Ball color - allows to choose color of discrete mesh elements (balls). - - Outline color - allows to select the color of element borders. - - Wireframe color - allows to select the color of borders of - elements in the wireframe mode. - - Preview color - allows to select the preview color of the - elements, which is used while - \ref adding_nodes_and_elements_page "manual creation of elements". - - Size of 0D elements - specifies default size of 0D elements. - - Size of ball elements - specifies default size of discrete - elements (balls). - - Scale factor of ball elements - specifies default scale - factor of discrete elements (balls) allowing to adjust their size in the Viewer. - - Line width - allows to define the width of 1D elements (segments). - - Outline width - allows to define the width of borders of - 2D and 3D elements (shown in the Shading mode). - - Shrink coef. - allows to define relative size of a shrunk - element compared a non-shrunk element in percents in the shrink mode. - -- Groups - - Names color - specifies color of group names to be used in - the 3D viewer. - - Default color - specifies the default group color, which is used - to create a new mesh group (see \ref creating_groups_page "Create Group dialog box"). - -- Numbering allows to define properties of numbering functionality: - - Nodes - specifies text properties of nodes numbering - (font family, size, attributes, color). - - Elements - same for elements. - -- Orientation of Faces - allows to define default properties of - orientation vectors. These preferences will be applied to the newly - created meshes only; properties of existing meshes can be customized - using \ref colors_size_page "Properties dialog box" available from - the context menu of a mesh. - - \b Color - allows to define the color of orientation vectors; - - \b Scale - allows to define the size of orientation vectors; - - 3D Vector - allows to choose between 2D planar - and 3D vectors. - -

Selection Preferences

- -\image html pref23.png - -- Selection - performed with mouse-indexing (preselection) - and left-clicking on an object, whose appearance changes as defined in - the Preferences. - - Object color - allows to select the color of mesh (edges and - borders of meshes) of the selected entity. Click on the colored line - to access to the Select Color dialog box. - - Element color - allows to select the color of surface of selected - elements (seen in Shading mode). Click on the colored line to access - to the Select Color dialog box. - -- Preselection - performed with mouse-indexing on an object, - whose appearance changes as defined in the Preferences. - - Highlight color - allows to select the color of mesh (edges and - borders of meshes) of the entity. Click on the colored line to access - to the Select Color dialog box. - -- Precision - in this menu you can set the value of precision - used for Nodes, Elements and Objects. - -

Scalar Bar Preferences

- -\image html pref24.png - -\note The following settings are default and will be applied to -a newly created mesh only. Existing meshes can be customized using -local \ref scalar_bar_dlg "Scalar Bar Properties dialog box" available -from the context menu of a mesh. - -- Font - in this menu you can set type, face and color of - the font of Title and Labels. - -- Colors & Labels - in this menu you can set the number of - colors and the number of labels in use. - -- Orientation - here you can choose between vertical and - horizontal orientation of the Scalar Bar. - -- Origin & Size Vertical & Horizontal - allows to define - placement (X and Y) and lookout (Width and - Height) of Scalar Bars. - - X - abscissa of the point of origin (from the left side). - - Y - ordinate of the origin of the bar (from the bottom). - -- Distribution in this menu you can Show/Hide distribution - histogram of the values of the Scalar Bar and specify the - Coloring Type of the histogram: - - Multicolor - the histogram is colored as Scalar Bar. - - Monocolor - the histogram is colored as selected with - Distribution color selector. - -*/ diff --git a/doc/salome/gui/SMESH/input/mesh_through_point.doc b/doc/salome/gui/SMESH/input/mesh_through_point.doc deleted file mode 100644 index 1684404ab..000000000 --- a/doc/salome/gui/SMESH/input/mesh_through_point.doc +++ /dev/null @@ -1,47 +0,0 @@ -/*! - -\page mesh_through_point_page Moving nodes - -\n In mesh you can define a node at a certain point either -- by movement of the node closest to the point or -- by movement of a selected node to the point. - -To displace a node: -
    -
  1. From the \b Modification menu choose the Move node item or -click "Move Node" button in the toolbar. - -\image html image67.png -
    "Move Node" button
    - -The following dialog will appear: - -\image html meshtopass1.png "Manual node selection" -
    - -\image html meshtopass2.png "Automatic node selection" -
    - -
    2. -
  2. Specify the way of node selection: manually (the first radio - button) or automatically (the second radio button).
    3. -
  3. If the manual method is selected, select a node to move (X, Y, - Z fields show the original coordinates of the node) or type - the node ID.
    4. -
  4. Enter the coordinates of the destination point. You can - click Update Destination button to set the coordinates of the - destination point equal to the coordinates of the node to move.
    5. -
  5. Activate \b Preview check-box to show the result of move in the - viewer.
    6. -
  6. Click the \b Apply or Apply and Close button to confirm the - operation.
    7. -
- -\image html moving_nodes1.png "The initial mesh" - -\image html moving_nodes2.png "The modified mesh" - -
See Also a sample TUI Script of a -\ref tui_moving_nodes "Moving Nodes" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/minimum_angle.doc b/doc/salome/gui/SMESH/input/minimum_angle.doc deleted file mode 100644 index 4236d6562..000000000 --- a/doc/salome/gui/SMESH/input/minimum_angle.doc +++ /dev/null @@ -1,29 +0,0 @@ -/*! - -\page minimum_angle_page Minimum angle - -\n Minimum angle mesh quality criterion consists of calculation of the -minimum value of angle between two adjacent sides of a 2D meshing -element (triangle or quadrangle). - -To apply the Minimum angle quality criterion to your mesh: -
    -
  1. Display your mesh in the viewer.
    2. - -
  2. Choose Controls > Face Controls > Minimum angle or click -"Minimum Angle" button. - -\image html image38.png -
    "Minimum Angle" button
    - -Your mesh will be displayed in the viewer with its elements colored -according to the applied mesh quality control criterion: - -\image html image92.jpg -
    3. -
- -
See Also a sample TUI Script of a -\ref tui_minimum_angle "Minimum Angle quality control" operation. - -*/ \ No newline at end of file diff --git a/doc/salome/gui/SMESH/input/modifying_meshes.doc b/doc/salome/gui/SMESH/input/modifying_meshes.doc deleted file mode 100644 index 3490916bc..000000000 --- a/doc/salome/gui/SMESH/input/modifying_meshes.doc +++ /dev/null @@ -1,71 +0,0 @@ -/*! - -\page modifying_meshes_page Modifying meshes - -Salome provides a vast specter of mesh modification and -transformation operations, giving the possibility to: - - - -\note It is possible to \ref edit_anchor "modify the mesh" of a lower -dimension before generation of the mesh of a higher dimension. - -


- -\note It is possible to use the variables defined in the SALOME \b NoteBook - to specify the numerical parameters used for modification of any object. - -*/ diff --git a/doc/salome/gui/SMESH/input/numbering.doc b/doc/salome/gui/SMESH/input/numbering.doc deleted file mode 100644 index c68137390..000000000 --- a/doc/salome/gui/SMESH/input/numbering.doc +++ /dev/null @@ -1,34 +0,0 @@ -/*! - -\page numbering_page Numbering - -

Displaying node numbers

- -In MESH you can display the ID numbers of all nodes of your mesh in -the viewer. - -To display ID numbers of nodes: -
    -
  1. Display your mesh in the viewer
    2. -
  2. Right-click on the mesh in the 3D viewer and from the associated -pop-up menu choose Numbering > Display Nodes #.
    3. -
- -\image html image96.jpg "Displayed node numbers" - -

Displaying element numbers

- -In MESH you can display the ID numbers of all meshing elements -composing your mesh in the viewer. - -To display ID numbers of elements: -
    -
  1. Display your mesh in the viewer
    2. -
  2. Right-click on the mesh in the 3D viewer and from the associated -pop-up menu choose Numbering > Display Elements #.
    3. -
- -\image html image95.jpg "Displayed element numbers" - -*/ - diff --git a/doc/salome/gui/SMESH/input/over_constrained_faces.doc b/doc/salome/gui/SMESH/input/over_constrained_faces.doc deleted file mode 100644 index acd29bb5b..000000000 --- a/doc/salome/gui/SMESH/input/over_constrained_faces.doc +++ /dev/null @@ -1,20 +0,0 @@ -/*! - -\page over_constrained_faces_page Over-constrained faces - -\n This mesh quality control highlights faces sharing only one border -with other faces. In other words, the faces having all their nodes on -the free border of the 2D mesh are highlighted. - -\note The highlighted faces are actually over-constrained only if, at -the computation time, the boundary conditions on the borders where the -nodes are located are all Dirichlet boundary conditions. - -\image html over_constrained_faces.png - -In this picture the over-constrained face is displayed in red. - -
See Also a sample TUI Script of a -\ref tui_over_constrained_faces "Over-constrained faces" filter. - -*/ diff --git a/doc/salome/gui/SMESH/input/over_constrained_volumes.doc b/doc/salome/gui/SMESH/input/over_constrained_volumes.doc deleted file mode 100644 index 7f1ba280d..000000000 --- a/doc/salome/gui/SMESH/input/over_constrained_volumes.doc +++ /dev/null @@ -1,18 +0,0 @@ -/*! - -\page over_constrained_volumes_page Over-constrained volumes - -\n This mesh quality control highlights volumes sharing only one border with other volumes. -In other words, the volumes having all their nodes on the external border of the mesh are highlighted. - -\note The highlighted volumes are actually over-constrained only if, at the computation time, -the boundary conditions on the borders where the nodes are located are all Dirichlet boundary conditions. - -\image html over_constrained_volumes.png - -In this picture the over-constrained volume is displayed in red. - -
See Also a sample TUI Script of a -\ref tui_over_constrained_volumes "Over-constrained volumes" filter. - -*/ diff --git a/doc/salome/gui/SMESH/input/pattern_mapping.doc b/doc/salome/gui/SMESH/input/pattern_mapping.doc deleted file mode 100644 index b42795e5d..000000000 --- a/doc/salome/gui/SMESH/input/pattern_mapping.doc +++ /dev/null @@ -1,231 +0,0 @@ -/*! - -\page pattern_mapping_page Pattern mapping - -

About patterns

- -The pattern describes a mesh to generate: positions of nodes within a -geometrical domain and nodal connectivity of elements. A -pattern also specifies the so-called key-points, i.e. the nodes that will be -located at geometrical vertices. The pattern description is stored in -\.smp file. - -The smp file contains 4 sections: - --# The first line indicates the total number of pattern nodes (N). --# The next N lines describe nodes coordinates. Each line contains 2 - node coordinates for a 2D pattern or 3 node coordinates for a 3D pattern. - Note, that node coordinates of a 3D pattern can be defined only by - relative values in range [0;1]. --# The key-points line contains the indices of the nodes to be mapped on geometrical - vertices (for a 2D pattern only). Index n refers to the node described - on the n-th line of section 2. The index of the first node is - zero. For a 3D pattern the key points are not specified. --# The remaining lines describe nodal connectivity of elements, one line - for each element. Each line holds indices of nodes forming an element. - Index n refers to the node described on the n-th line of section 2. - The first node index is zero. There must be 3 or 4 indices on each - line for a 2D pattern (only liner 2d elements are allowed) and 4, 5, 6 or 8 - indices for a 3D pattern (only linear 3d elements are allowed). - -A 2D pattern must contain at least one element and at least one -key-point. All key-points must lie on boundaries. - -A 3D pattern must contain at least one element. - -An example of a simple 2D pattern smp file: - -\code -!!! SALOME 2D mesh pattern file -!!! -!!! Nb of points: -9 - 200 0 !- 0 - 100 0 !- 1 - 0 0 !- 2 - 0 -100 !- 3 - 0 -200 !- 4 - 100 -200 !- 5 - 200 -200 !- 6 - 200 -100 !- 7 - 100 -100 !- 8 -!!! Indices of 4 key-points - 2 0 4 6 -!!! Indices of points of 6 elements - 0 1 8 - 8 5 6 7 - 2 3 8 - 8 3 4 5 - 8 7 0 - 8 1 2 -\endcode - -The image below provides a preview of the above pattern: - -\image html pattern2d.png - -An example of a simple 3D pattern smp file: - -\code -!!! SALOME 3D mesh pattern file -!!! -!!! Nb of points: -9 - 0 0 0 !- 0 - 1 0 0 !- 1 - 0 1 0 !- 2 - 1 1 0 !- 3 - 0 0 1 !- 4 - 1 0 1 !- 5 - 0 1 1 !- 6 - 1 1 1 !- 7 - 0.5 0.5 0.5 !- 8 -!!! Indices of points of 6 elements: - 0 1 5 4 8 - 7 5 1 3 8 - 3 2 6 7 8 - 2 0 4 6 8 - 0 2 3 1 8 - 4 5 7 6 8 -\endcode - -

Application of pattern mapping

- -To apply pattern mapping to a geometrical object or mesh elements: - -From the \b Modification menu choose the Pattern Mapping item or click -"Pattern mapping" button in the toolbar. - -\image html image98.png -
"Pattern mapping" button
- -The following dialog box will appear: - -\n For a 2D pattern - -\image html patternmapping1.png - -In this dialog you should specify: - -
    -
  • \b Pattern, which can be loaded from .smp pattern file previously - created manually or generated automatically from an existing mesh or - sub-mesh.
    • -
  • \b Face with the number of vertices equal to the number of - key-points in the pattern; the number of key-points on internal - boundaries of the pattern must also be equal to the number of vertices - on internal boundaries of the face;
    • -
  • \b Vertex to which the first key-point should be mapped;
    • -
- -Alternatively, it is possible to select Refine selected mesh elements -check-box and apply the pattern to
    -
  • Mesh Face instead of a geometric Face
    • -
  • and select \b Node instead of vertex.
    • -
- -Additionally it is possible to:
    -
  • Reverse the order of key-points. By default, the vertices of - a face are ordered counterclockwise.
    • -
  • Enable to Create polygons near boundary
    • -
  • and Create polyhedrons near boundary
    • -
- -\n For a 3D pattern - -\image html patternmapping2.png - -In this dialog you should specify: -
    -
  • \b Pattern, which can be loaded from .smp pattern file previously - created manually or generated automatically from an existing mesh or - sub-mesh.
    • -
  • A 3D block (Solid) object.
    • -
  • Two vertices that specify the order of nodes in the resulting - mesh.
    • -
- -Alternatively, it is possible to select Refine selected mesh elements -check-box and apply the pattern to -
    -
  • One or several Mesh volumes instead of a geometric 3D object
    • -
  • and select two \b Nodes instead of vertices.
    • -
-Additionally it is possible to: -
    -
  • Enable to Create polygons near boundary
    • -
  • and Create polyhedrons near boundary
    • -
- -
-

Automatic Pattern Generation

- -To generate a pattern automatically from an existing mesh or sub-mesh, -click \b New button. - -The following dialog box will appear: - -\image html a-patterntype1.png - -In this dialog you should specify: - -
    -
  • Mesh or Sub-mesh, which is a meshed geometrical face (for a -2D pattern) or a meshed solid block (for a 3D pattern). Mesh nodes lying on -the face vertices become key-points of the pattern.
    • -
  • A custom Pattern Name
    • -
  • Additionally, for a 2D pattern you may choose to -Project nodes on the face to get node coordinates instead of using -"positions on face" generated by the mesher (if there is any). The faces -having a seam edge cannot be used for automatic pattern creation.
    • -
- -When a pattern is created from an existing mesh, two cases are possible: - -- A sub-mesh on a face/solid is selected. The pattern is created from the 2d/3d -elements bound to the face/solid by the mesher. For a 2D pattern, the node coordinates are either -"positions on face" computed by the mesher, or coordinates got by node -projection on a geometrical surface, according to the user choice. For -a 3D pattern, the node coordinates correspond to the nodes computed by -the mesher. -- A mesh, where the main shape is a face/solid, is selected. The pattern is -created from all 2d/3d elements in a mesh. In addition, if all mesh -elements of a 2D pattern are built by the mesher, the user can select -how to get node coordinates, otherwise all nodes are projected on -a face surface. - - -

Mapping algorithm

- -The mapping algorithm for a 2D case is as follows: - -- The key-points are set counterclockwise in the order corresponding - to their location on the pattern boundary. The first key-point is preserved. -- The geometrical vertices corresponding to the key-points are found - on face boundary. Here, "Reverse order of key-points" flag is set. -\image html image95.gif -- The boundary nodes of the pattern are mapped onto the edges of the face: a - node located between two key-points on the pattern boundary is - mapped on the geometrical edge limited by the corresponding geometrical - vertices. The node position on the edge depends on its distance from the - key-points. -\image html image96.gif -- The coordinates of a non-boundary node in the parametric space of the face - are defined in the following way. In the parametric space of the - pattern, the node lies at the intersection of two iso-lines. Both - of them intersect the pattern boundary at two - points at least. If the mapped positions of boundary nodes are known, it is - possible to find, where the points at the intersection of iso-lines - and boundaries are mapped. Then it is possible to find - the direction of mapped iso-line section and, finally, the positions of - two nodes on two mapped isolines. The eventual mapped - position of the node is found as an average of the positions on mapped - iso-lines. -\image html image97.gif - -The 3D algorithm is similar. - -See Also a sample TUI Script of a -\ref tui_pattern_mapping "Pattern Mapping" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/point_marker.doc b/doc/salome/gui/SMESH/input/point_marker.doc deleted file mode 100644 index 0a7b88e3b..000000000 --- a/doc/salome/gui/SMESH/input/point_marker.doc +++ /dev/null @@ -1,53 +0,0 @@ -/*! - -\page point_marker_page Point Marker - -\n You can change the representation of points in -the 3D viewer either by selecting one of the predefined -shapes or by loading a custom texture from an external file. - -- Standard point markers - -The Mesh module provides a set of predefined point marker shapes -which can be used to display points in the 3D viewer. -Each standard point marker has two attributes: type (defines shape -form) and scale factor (defines shape size). - -\image html point_marker_widget1.png - -
- -\image html std_point_marker.png "Mesh presentation with standard point markers" - -- Custom point markers - -It is also possible to load a point marker shape from an external file. -This file should provide a description of the point texture as a set -of lines; each line is represented as a sequence of "0" and "1" symbols, -where "1" symbol means an opaque pixel and "0" symbol means a -transparent pixel. The width of the texture corresponds to the length -of the longest line in the file, expanded to the nearest byte-aligned -value. The height of the texture is equal to the number of non-empty -lines in the file. Note that missing symbols are replaced by "0". - -Here is a texture file sample: - -
-11111111
-10000001
-10011001
-10111101
-10111101
-10011001
-10000001
-11111111
-
- -\image html point_marker_widget2.png - -
- -\image html custom_point_marker.png "Mesh presentation with custom point markers" - -*/ - diff --git a/doc/salome/gui/SMESH/input/prism_3d_algo.doc b/doc/salome/gui/SMESH/input/prism_3d_algo.doc deleted file mode 100644 index 6d4be7be8..000000000 --- a/doc/salome/gui/SMESH/input/prism_3d_algo.doc +++ /dev/null @@ -1,88 +0,0 @@ -/*! - -\page prism_3d_algo_page Extrusion 3D meshing algorithm - -Extrusion 3D algorithm can be used for meshing prisms, i.e. 3D shapes -defined by two opposing faces having the same number of vertices and -edges. These two faces should be connected by quadrangle "side" faces. - -\image html prism_mesh.png "Clipping view of a mesh of a prism with non-planar base and top faces" - -The prism is allowed to have sides composed of several faces. (A prism -side is a row of faces (or one face) connecting the corresponding edges of -the top and base faces). However, a prism -side can be split only vertically as indicated in the -picture below. - -\image html prism_ok_ko.png "A suitable and an unsuitable prism" -In this picture, the left prism is suitable for meshing with 3D -extrusion algorithm: it has six sides, two of which are split -vertically. The right prism cannot be meshed with this -algorithm because one of the prism sides is split horizontally (the -splitting edge is highlighted). - -The algorithm can propagate 2D mesh not only between horizontal -(i.e. base and top) faces of one prism but also between faces of prisms -organized in a stack and between stacks sharing prism sides. - -\image html prism_stack.png "Prism stacks" -This picture shows four neighboring prism stacks, each comprising two prisms. -The shown sub-mesh is used by the algorithm to mesh -all eight prisms in the stacks. - -To use Extrusion 3D algorithm you need to assign algorithms -and hypotheses of lower dimensions as follows. -(A sample picture below shows algorithms and hypotheses used to -mesh a cylinder with prismatic volumes). - -\image html prism_needs_hyps.png - -The \b Global algorithms and hypotheses to be chosen at -\ref create_mesh_anchor "Creation of a mesh object" are: -
    -
  • 1D algorithm and hypothesis that will be applied for meshing - (logically) vertical edges of the prism (which connect the top and the - base faces of the prism). In the sample picture above these are - "Regular_1D" algorithm and "Number of Segments" hypothesis named "Vertical - Nb. Segments".
    • -
- -The \b Local algorithms and hypotheses to be chosen at -\ref constructing_submeshes_page "Construction of sub-meshes" are: -
    -
  • 1D and 2D algorithms and hypotheses that will be applied for - meshing the top and the base prism - \ref submesh_shape_section "faces". These faces can be meshed - with any type of 2D elements: quadrangles, triangles, polygons or - their mix. It is enough to define a sub-mesh on either the top or - the base face. In the sample picture above, "NETGEN_1D2D" - algorithm meshes "bottom disk" face with triangles. (1D algorithm - is not assigned as "NETGEN_1D2D" does not require divided edges to - create a 2D mesh.) -
    • -
  • Optionally you can define a 1D sub-mesh on some vertical - \ref submesh_shape_section "edges" of stacked prisms, which will - override the global 1D hypothesis mentioned above. In the Prism - stacks picture, the vertical division is not equidistant on - the whole length because a "Number Of Segments" hypothesis with - Scale Factor=3 is assigned to the highlighted edge. -
- -If Extrusion 3D algorithm is assigned to a sub-mesh in a mesh -with multiple sub-meshes, the described above approach may not work as -expected. For example the bottom face may be meshed by other algorithm -before Extrusion 3D have a chance to project a mesh from the -base face. This thing can happen with vertical edges as well. All -these can lead to either a meshing failure or to an incorrect meshing. - -In such a case, it's necessary to explicitly define algorithms -that Extrusion 3D implicitly applies in a simple case: -- assign \ref projection_1D2D algorithm to the top face and -- assign a 1D algorithm to a group of all vertical edges. - -\image html image157.gif "Prism with Extrusion 3D meshing. Vertical division is different on neighbor edges because several local 1D hypotheses are assigned." - -\sa a sample TUI Script of -\ref tui_prism_3d_algo "Use Extrusion 3D meshing algorithm". - -*/ diff --git a/doc/salome/gui/SMESH/input/projection_algos.doc b/doc/salome/gui/SMESH/input/projection_algos.doc deleted file mode 100644 index de11a7ee0..000000000 --- a/doc/salome/gui/SMESH/input/projection_algos.doc +++ /dev/null @@ -1,116 +0,0 @@ -/*! - -\page projection_algos_page Projection Algorithms - -\tableofcontents - -Projection algorithms allow to define the mesh of a geometrical -object by the projection of another already meshed geometrical object. - -\note Source and target geometrical objects mush be topologically -equal, i.e. they must have same number of sub-shapes, connected to -corresponding counterparts. - -\image html topo_equality.png Topologically equal faces suitable for 2D projection. - - -\section projection_1D Projection 1D - -Projection 1D algorithm allows to define the mesh of an edge -(or group of edges) -by the projection of another already meshed edge (or group of edges). -\n To apply this algorithm select the edge to be meshed (indicated in -the field \b Geometry of Create mesh dialog box), -Projection1D in the list of 1D algorithms and click the -"Add Hypothesis" button. -The following dialog box will appear: - -\image html projection_1d.png - -In this dialog you can define -
    -
  • the \b Name of the algorithm,
    • -
  • the already meshed Source Edge and
    • -
  • the Source Mesh (It can be omitted only when projecting - a sub-mesh on another one of the same Mesh).
    • -
  • It could also be necessary to define the orientation of edges, - which is done by indicating the Source Vertex being the - first point of the Source Edge and the Target Vertex being - the first point of the edge being meshed.
    • -
-
-For a group of edges, Source and Target vertices should be -shared by only one edge of the group. If Source and Target -vertices are specified, the edges in the group must be connected. -The source and target groups must contain equal number of edges -and they must form topologically equal structures. - -\section projection_2D Projection 2D - -\n Projection 2D algorithm allows to define the mesh of a face -(or group of faces) by the projection of another already meshed face -(or group of faces). This algorithm works only if all edges of the -target face have been discretized into the same number of -segments as corresponding edges of the source face. - -To apply this algorithm select the face to be meshed (indicated in the -field \b Geometry of Create mesh dialog box), Projection -2D in the list of 2D algorithms and click the "Add -Hypothesis" button. The following dialog box will appear: - -\image html projection_2d.png - -In this dialog you can define -
    -
  • the \b Name of the algorithm,
    • -
  • the already meshed Source Face and
    • -
  • the Source Mesh (It can be omitted only when - projecting a submesh on another one of the same Mesh).
    • -
  • It could also be necessary to define the orientation of mesh on - the face, which is done by indicating two Source Vertices, - which belong to the same edge of the Source Face, and - two Target Vertices, which belong to the same edge of the - face being meshed.
    • -
- -The groups of faces are suitable for this algorithm only if they -contain an equal number of faces and form topologically equal -structures. - -\section projection_1D2D Projection 1D-2D - -\n Projection 1D-2D algorithm differs from -\ref projection_2D algorithm in one aspect: it generates mesh segments -on edges of the face according to the projected 2D elements; thus it -does not require the edges to be meshed by any other 1D algorithm; -moreover it does not allow to mesh edges of the face using another -algorithm via definition of sub-meshes. - -\section projection_3D Projection 3D - -\n Projection 3D algorithm allows to define the mesh of a shape by -the projection of another already meshed shape. This algorithm works -only if all faces and edges of the target shape have been meshed as 1D-2D -Projections of the faces and edges of the source shape. Another -limitation is that this algorithm currently works only on boxes. - -To apply this algorithm select the solid to be meshed (indicated in -the field \b Geometry of Create mesh dialog box), Projection -3D in the list of 3D algorithms and click the button. The -following dialog box will appear: - -\image html projection_3d.png - -In this menu you can define the \b Name of the algorithm, the already -meshed source 3D shape and the \b Mesh (It can be omitted only when -projecting a submesh on another one from the same global Mesh). -It could also be necessary to define the orientation of mesh on the shape, which is -done by indicating two Source Vertices, which belong to the same edge -of the source 3D Shape, and two Target Vertices, which belong to the -same edge of the source 3D Shape. - -
See Also a sample TUI Script of a -\ref tui_projection "Projection Algorithms". - -*/ - diff --git a/doc/salome/gui/SMESH/input/quad_from_ma_algo.doc b/doc/salome/gui/SMESH/input/quad_from_ma_algo.doc deleted file mode 100644 index f7312ee12..000000000 --- a/doc/salome/gui/SMESH/input/quad_from_ma_algo.doc +++ /dev/null @@ -1,36 +0,0 @@ -/*! - -\page quad_from_ma_algo_page Medial Axis Projection Quadrangle meshing algorithm - -Medial Axis Projection algorithm can be used for meshing faces with -sinuous borders and a channel-like shape, for which it can be -difficult to define 1D hypotheses such that to obtain a good shape of -resulting quadrangles. The algorithm can be also applied to faces with ring -topology, which can be viewed as a closed 'channel'. In the latter -case radial discretization of a ring can be specified by -using Number of Layers or Distribution of Layers -hypothesis. - -\image html quad_from_ma_mesh.png "A mesh of a river model to the left and of a ring-face to the right" - -The algorithm provides proper shape of quadrangles by constructing Medial -Axis between sinuous borders of the face and using it to -discretize the borders. (Shape of quadrangles can be not perfect at -locations where opposite sides of a 'channel' are far from being parallel.) - -\image html quad_from_ma_medial_axis.png "Medial Axis between two blue sinuous borders" - -The Medial Axis is used in two ways: -
    -
  1. If there is a sub-mesh on a sinuous border, then the nodes of - this border are mapped to the opposite border via the Medial - Axis.
    2. -
  2. If there are no sub-meshes on sinuous borders, then the part of - the Medial Axis that can be mapped to both borders is discretized - using a 1D hypothesis assigned to the face or its ancestor shapes, - and the division points are mapped from the Medial Axis to both - borders to find positions of nodes.
    3. -
- -\image html quad_from_ma_ring_mesh.png "Mesh depends on defined sub-meshes: to the left - sub-meshes on both wires, to the right - a sub-mesh on internal wire only" -*/ diff --git a/doc/salome/gui/SMESH/input/quad_ijk_algo.doc b/doc/salome/gui/SMESH/input/quad_ijk_algo.doc deleted file mode 100644 index 292a300e5..000000000 --- a/doc/salome/gui/SMESH/input/quad_ijk_algo.doc +++ /dev/null @@ -1,49 +0,0 @@ -/*! - -\page quad_ijk_algo_page Quadrangle: Mapping meshing algorithm - -Quadrangle: Mapping meshing algorithm is intended for creating -all-quadrangle and quad-dominant meshes on faces without holes and -bound by at least three edges. - -The algorithm can create mesh on any face but its quality and -validity depend on two factors: -- face shape (number of edges and boundary concavity); -- discretization of edges. - -\image html quad_mesh_invalid.png "Invalid mesh on quadrilateral concave faces" - -The algorithm uses Transfinite Interpolation technique in the -parametric space of a face to locate nodes inside the face. - -The algorithm treats any face as quadrangle. If a face is bound by -more than four edges, four most sharp vertices are considered as -corners of the quadrangle and all edges between these vertices are -treated as quadrangle sides. In the case of three edges, the vertex -specified by the user is considered as a fourth degenerated side of the -quadrangle. - -\image html quad_meshes.png "Algorithm generates a structured mesh on complex faces provided that edges are properly discretized" - -To get an all-quadrangle mesh you have to carefully define 1D -hypotheses on edges of a face. To get a \b structured mesh you have to provide -equal number of segments on opposite sides of the quadrangle. If this -condition is not respected, the algorithm by default (without a -hypothesis) creates a \b quad-dominant mesh with triangles located near the -side with the maximal number of segments. However, you can get an -\b all-quadrangle mesh in this case by using -\ref hypo_quad_params_anchor "Quadrangle Parameters" -hypothesis to specify how to make transition mesh between opposite -sides with different number of segments, provided that certain -conditions are respected. In any case the total number of segments must be -even. To use \a Reduced transition method, there must be an equal number -of segments on one pair of opposite sides. - -The following hypotheses help to create quadrangle meshes. -- \ref propagation_anchor "Propagation" additional 1D hypotheses - help to get an equal number of segments on the opposite sides of a - quadrilateral face. -- \ref a1d_algos_anchor "Composite Side Discretization" algorithm is useful - to discretize several C1 continuous edges as one quadrangle side. - -*/ diff --git a/doc/salome/gui/SMESH/input/radial_prism_algo.doc b/doc/salome/gui/SMESH/input/radial_prism_algo.doc deleted file mode 100644 index 8c3306857..000000000 --- a/doc/salome/gui/SMESH/input/radial_prism_algo.doc +++ /dev/null @@ -1,26 +0,0 @@ -/*! - -\page radial_prism_algo_page Radial Prism - -\n This algorithm applies to the meshing of a hollow 3D shape, -i.e. such shape should be composed of two meshed shells: an outer -shell and an internal shell without intersection with the outer -shell. One of the shells should be a 2D Projection of the other -shell. The meshes of the shells can consist both of triangles and -quadrangles. - -The Radial Prism algorithm would fill the space between the two shells -with prisms. - -\image html radial_prism_mesh.png "Cut-view of a hollow sphere meshed by Radial Prism algorithm" - -This algorithm also needs the information concerning the number and -distribution of mesh layers between the inner and the outer shapes. - -\image html number_of_layers.png - -Distribution of layers can be set with any of 1D Hypotheses. - -\image html distribution_of_layers.png - -*/ diff --git a/doc/salome/gui/SMESH/input/radial_quadrangle_1D2D_algo.doc b/doc/salome/gui/SMESH/input/radial_quadrangle_1D2D_algo.doc deleted file mode 100644 index 7e49a9a66..000000000 --- a/doc/salome/gui/SMESH/input/radial_quadrangle_1D2D_algo.doc +++ /dev/null @@ -1,36 +0,0 @@ -/*! - -\page radial_quadrangle_1D2D_algo_page Radial Quadrangle 1D-2D - -\n This algorithm applies to the meshing of 2D shapes under the -following conditions: the face must be a full ellipse or a part of ellipse -(i.e. the number of edges is less or equal to 3 and one of them is an ellipse curve). -The resulting mesh consists of triangles (near the center point) and -quadrangles. - -This algorithm is optionally parametrized by the hypothesis indicating -the number of mesh layers along the radius. The distribution of layers -can be set with any 1D Hypothesis. If the face boundary includes -radial edges, this distribution is applied to the longest radial -edge. If the face boundary does not include radial edges, this -distribution is applied to the longest virtual radial edge. The -distribution is applied to the longest radial edge starting from its -end lying on the elliptic curve. - - -If no own hypothesis of the algorithm is assigned, any local or global -hypothesis is used by the algorithm to discretize edges. - -If no 1D hypothesis is assigned to an edge, -\ref nb_segments_pref "Default Number of Segments" preferences -parameter is used to discretize the edge. - -\image html hypo_radquad_dlg.png - -\image html mesh_radquad_01.png "Radial Quadrangle 2D mesh on the top and the bottom faces of a cylinder" - -\image html mesh_radquad_02.png "Radial Quadrangle 2D mesh on a part of circle" - -\sa A sample \ref tui_radial_quadrangle "TUI Script". - -*/ diff --git a/doc/salome/gui/SMESH/input/removing_nodes_and_elements.doc b/doc/salome/gui/SMESH/input/removing_nodes_and_elements.doc deleted file mode 100644 index fd506d2b7..000000000 --- a/doc/salome/gui/SMESH/input/removing_nodes_and_elements.doc +++ /dev/null @@ -1,140 +0,0 @@ -/*! - -\page removing_nodes_and_elements_page Removing nodes and elements - -\n In MESH you can remove nodes and all types of cells of your mesh. - -
    -
  • \ref removing_nodes_anchor "Nodes"
    • -
  • \ref removing_orphan_nodes_anchor "Orphan Nodes"
    • -
  • \ref removing_elements_anchor "Elements"
    • -
  • \ref clear_mesh_anchor "Clear Mesh Data"
    • -
- -
-\anchor removing_nodes_anchor -

Removing nodes

- -To remove a node: -
    -
  1. Select your mesh in the Object Browser or in the 3D viewer.
    2. - -
  2. From the Modification menu choose Remove and from the associated -submenu select the Nodes, or just click "Remove nodes" -button in the toolbar. - -\image html remove_nodes_icon.png -
    "Remove nodes" button
    - -The following dialog box will appear: - -\image html removenodes.png - -In this dialog box you can specify one or several nodes: -
      -
    • choose mesh nodes with the mouse in the 3D Viewer. It is -possible to select a whole area with a mouse frame; or
      • -
    • input the node IDs directly in ID Elements field. The selected nodes will be highlighted in the -viewer; or
      • -
    • apply Filters. Set filter button allows to apply a filter to the selection of nodes. See more -about filters in the \ref selection_filter_library_page "Selection filter library" page.
      • -
    - - -
    3. -
- -\note Be careful while removing nodes because if you remove a definite -node of your mesh all adjacent elements will be also deleted. - -
-\anchor removing_orphan_nodes_anchor -

Removing orphan nodes

- -There is a quick way to remove all orphan (free) nodes. - -To remove orphan nodes: -
    -
  1. Select your mesh in the Object Browser or in the 3D viewer.
    2. - -
  2. From the Modification menu choose Remove and from the associated -submenu select Orphan Nodes, or just click "Remove orphan nodes" -button in the toolbar. - -\image html remove_orphan_nodes_icon.png -
    "Remove orphan nodes" button
    - -The following Warning message box will appear: - -\image html removeorphannodes.png - -Confirm nodes removal by pressing "Yes" button. -
- -
-\anchor removing_elements_anchor -

Removing elements

- -To remove an element: -
    -
  1. Select your mesh in the Object Browser or in the 3D viewer.
    2. - -
  2. From the Modification menu choose Remove and from the -associated submenu select the Elements, or just click -"Remove elements" button in the toolbar. - -\image html remove_elements_icon.png -
    "Remove elements" button
    - -The following dialog box will appear: - -\image html removeelements.png - -In this dialog box you can specify one or several elements -
      -
    • choose mesh elements with the mouse in the 3D Viewer. It is -possible to select a whole area with a mouse frame; or
      • -
    • input the element IDs directly in ID Elements field. The selected elements will be highlighted in the -viewer; or
      • -
    • apply Filters. Set filter button allows to apply a filter to the selection of elements. See more -about filters in the \ref selection_filter_library_page "Selection filter library" page.
      • -
    - -
    3. -
  3. Click \b Apply or Apply and Close to confirm deletion of the specified elements.
    4. -
- -\image html remove_nodes1.png "The initial mesh" - -\image html remove_nodes2.png "The mesh with some elements removed" - -
-\anchor clear_mesh_anchor -

Clearing Mesh Data

- -To remove all nodes and all types of cells in your mesh at once: -
    -
  1. Select your mesh in the Object Browser or in the 3D viewer.
    2. - -
  2. From the Modification menu choose Remove and from the associated -submenu select the Clear Mesh Data, or just click "Clear Mesh Data" -button in the toolbar. You can also right-click on the mesh in the -Object Browser and select Clear Mesh Data in the pop-up menu.
    3. -
- -
-\image html mesh_clear.png -"Clear Mesh Data" button
- -\note This command works in a different way in different situations:
    -
  • if the mesh is computed on a geometry, then "Clear Mesh Data" removes - all elements and nodes.
    • -
  • if the mesh is not based on a geometry (imported, compound, created from - scratch etc.), then "Clear Mesh Data" removes only the elements and - nodes computed by algorithms. If no such elements or nodes have been created, can remove nothing.
- -
See Also a sample TUI Script of a -\ref tui_removing_nodes_and_elements "Removing Nodes and Elements" operation. - -*/ - diff --git a/doc/salome/gui/SMESH/input/reorient_faces.doc b/doc/salome/gui/SMESH/input/reorient_faces.doc deleted file mode 100644 index 96072cf43..000000000 --- a/doc/salome/gui/SMESH/input/reorient_faces.doc +++ /dev/null @@ -1,96 +0,0 @@ -/*! - -\page reorient_faces_page Orient faces - -\n This operation allows fixing the orientation of a set of faces in -the following ways: -
    -
  • The required orientation of a set of neighboring faces can be defined - by a vector giving the direction of a normal to a certain face.
    - Since the direction of face normals in the set can be even opposite, - it is necessary to specify a \a control face, the normal to which - will be compared with the vector. This face can be either: -
      -
    • found by proximity to a given point, or
      • -
    • specified explicitly.
      • -
    -
    • -
  • Alternatively, the faces can be oriented relatively to the adjacent volumes.
    • -
- -The orientation of a face is changed by reverting the order of its nodes. - -To set orientation of faces: -
    -
  1. In the \b Modification menu select Reorient faces - item or click Reorient faces button in the toolbar. - -
    -\image html reorient_faces_face.png -"Reorient faces" button -
    -
    2. - -
  2. In the "Reorient faces" dialog box - -
      -
    • Select the \b Object (mesh, sub-mesh or group) - containing faces to reorient, in the Object Browser or in the 3D - Viewer.
      • - -
    • To reorient by direction of the face normal: -
        -
      • Specify the coordinates of the \b Point by which the control face - will be found. You can specify the \b Point by picking a - node in the 3D Viewer or selecting a vertex in the Object - Browser.
        • -
      • Set up the \b Direction vector to be compared with the normal of the - control face. There are following options:
          -
        • adjust vector components directly;
          • -
        • select a vertex in the Object Browser or a node in the 3D - Viewer; their coordinates will define vector components;
          • -
        • pick two nodes (holding Shift button), the \b Direction vector - will go from the first to the second node.
          • -
        -
      - -
      -
      -\image html reorient_2d_point.png "The orientation of adjacent faces is chosen according to a vector. The control face is found by point." -
      - -
      • - -
    • In the second mode it is possible to pick the \b Face by mouse in the 3D Viewer or directly input the \b Face ID in the corresponding field. - -
      -\image html reorient_2d_face.png "The orientation of adjacent faces is chosen according to a vector. The control face is explicitly given." -
      - -
      • - -
    • In the third mode, the faces can be reoriented according to volumes: -
        -
      • Select an object (mesh, sub-mesh or group) containing - reference \b Volumes, in the Object Browser or in the 3D - Viewer.
        • -
      • Specify whether face normals should point outside or inside - the reference volumes using Face normal outside volume - check-box.
        • -
      - -
      -
      -\image html reorient_2d_volume.png "The orientation of faces is chosen relatively to adjacent volumes." -
      - -
      • -
    - -
  3. Click the \b Apply or Apply and Close button to confirm the operation.
    4. -
- -
See Also a sample TUI Script of a -\ref tui_reorient_faces "Reorient faces" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/revolution.doc b/doc/salome/gui/SMESH/input/revolution.doc deleted file mode 100644 index 4b1d81240..000000000 --- a/doc/salome/gui/SMESH/input/revolution.doc +++ /dev/null @@ -1,112 +0,0 @@ -/*! - -\page revolution_page Revolution - -\n Revolution is used to build mesh elements of plus one -dimension than the input ones. Boundary elements around generated -mesh of plus one dimension are additionally created. All created -elements can be automatically grouped. Revolution can be used to create -a \ref extrusion_struct "structured mesh from scratch". -See \ref extrusion_page page for general information on Revolution, -which can be viewed as extrusion along a circular path. - -To apply revolution: -
    -
  1. From the \b Modification menu choose the \b Revolution item or click - "Revolution" button in the toolbar. - -\image html image92.png -
    "Revolution" button
    - -The following dialog will appear: - -\image html revolution1.png - -
    2. - -
  2. In this dialog: -
      -
    • Use \a Selection button to specify what you are going to - select at a given moment, \b Nodes, \b Edges or \b Faces. -\image html image120.png -
      "Selection" button
      -
      • -
    • Specify \b Nodes, \b Edges and \b Faces, which will be revolved, by one - of following means: -
        -
      • Select the whole mesh, sub-mesh or group activating this - check-box.
        • -
      • Choose mesh elements with the mouse in the 3D Viewer. It is - possible to select a whole area with a mouse frame.
        • -
      • Input the element IDs directly in Node IDs, Edge - IDs and Face IDs fields. The selected elements will - be highlighted in the viewer, if the mesh is shown there.
        • -
      • Apply Filters. Set filter button allows to apply a - filter to the selection of elements. See more about filters in - the \ref filtering_elements "Selection filters" page.
        • -
      -
      • -
    • Specify the \b Axis of revolution: -
        -
      • Specify the coordinates of the start \b Point of the - axis of revolution; either directly or by picking a node - in the Viewer (selection of nodes is activated as you click - the \a Selection button).
        • -
      • Specify the \b Vector of the axis in either of three ways: -
          -
        • directly adjust vector components;
          • -
        • click \a Selection button, choose From Origin to - selected Point in the opened menu and pick a node - in the Viewer;
          • -
        • click \a Selection button, chose Normal to - selected Face in the opened menu and pick a mesh - face in the Viewer.
          • -
      -
      • -
    • Specify the \b Angle of revolution and the Number of - steps of revolution, -
        -
      • Angle by Step - the elements are revolved by the - specified angle at each step (i.e. for Angle=30 and Number of - Steps=3, the elements will be extruded by 30 degrees twice for a - total of 30*3=90) -\image html revolutionsn2.png "Example of Revolution with Angle by Step. Angle=30 and Number of Steps=3" -
        • -
      • Total Angle - the elements are revolved by the - specified angle only once and the number of steps defines the - number of iterations (i.e. for Angle=30 and Number of Steps=3, - the elements will be revolved by 30/3=10 degrees twice for a - total of 30). -\image html revolutionsn1.png "Example of Revolution with Total Angle. Angle=30 and Number of Steps=3" -
        • -
      -
      • -
    • Specify the \b Tolerance, which is used to detect nodes lying - on the axis of revolution. -
      • -
    • Activate Preview check-box to see the result mesh in - the viewer. -
      • -
    • If you activate Generate Groups check-box, the result elements - created from selected elements contained in groups will be - included into new groups named by pattern "_rotated" and "_top". For example if a - selected quadrangle is included in \a g_Faces group (see figures - below) then result hexahedra will be included in \a - g_Faces_rotated group and a quadrangle created at the "top" of - revolved mesh will be included in \a g_Faces_top group.
      -\image html extrusion_groups.png -\image html extrusion_groups_res.png -

      This check-box is active only if there are some groups in the mesh. -

      • -
    -
    3. - -
  3. Click \b Apply or Apply and Close button to confirm the - operation.
    4. -
- -
See Also a sample TUI Script of a -\ref tui_revolution "Revolution" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/rotation.doc b/doc/salome/gui/SMESH/input/rotation.doc deleted file mode 100644 index cb46359fd..000000000 --- a/doc/salome/gui/SMESH/input/rotation.doc +++ /dev/null @@ -1,78 +0,0 @@ -/*! - -\page rotation_page Rotation - -\n This operation allows to rotate in space the mesh or -some of its elements. - -To rotate the mesh: - -
    -
  1. From the \b Modification menu choose \b Transformation -> \b Rotation item or click -"Rotation" button in the toolbar. - -\image html rotation_ico.png "Rotation button" - -The following dialog will appear: - -\image html rotation.png - -
    2. - -
  2. -In this dialog: -
      -
    • specify the IDs of the elements which will be rotated: - -
        -
      • Select the whole mesh, submesh or group activating this -checkbox; or
        • -
      • choose mesh elements with the mouse in the 3D Viewer. It is -possible to select a whole area with a mouse frame; or
        • -
      • input the element IDs directly in ID Elements field. The selected elements will be highlighted in the -viewer; or
        • -
      • apply Filters. Set filter button allows to apply a filter to the selection of elements. See more -about filters in the \ref selection_filter_library_page "Selection filter library" page.
        • -
      -
      • - -
    • specify the axis of rotation: -
        -
      • specify the cooordinates of the start \b Point of the vector of rotation;
        • -
      • specify the \b Vector of rotation through the coordinates of its -end point with respect to the coordinates of the start point;
        • -
      -
      • -
    • specify the \b Angle of rotation
      • - -
    • specify the conditions of rotation: -
        -
      • activate Move elements radio button to create the source -mesh (or elements) at the new location and erase it from the previous location;
        • -
      • activate Copy elements radio button to create the source -mesh (or elements) at the new location, but leave it at the previous -location, the source mesh will be considered one and single mesh with the result of the rotation;
        • -
      • activate Create as new mesh radio button to leave the -source mesh (or elements) at its previous location and create a new -mesh at the new location, the new mesh appears in the Object Browser -with the default name MeshName_rotated (it is possible to change this -name in the adjacent box);
        • -
      • activate Copy groups checkbox to copy the groups of elements of the source mesh to the newly created mesh.
        • -
      -
      • - -
    • activate Preview checkbox to show the result of transformation in the viewer
      • -
    • click \b Apply or Apply and Close button to confirm the -operation.
      • -
    -
- - -\image html rotation1.png "The initial mesh" - -\image html rotation2.png "The rotated mesh" - -
See Also a sample TUI Script of a -\ref tui_rotation "Rotation" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/scalar_bar.doc b/doc/salome/gui/SMESH/input/scalar_bar.doc deleted file mode 100755 index 9d36cd301..000000000 --- a/doc/salome/gui/SMESH/input/scalar_bar.doc +++ /dev/null @@ -1,44 +0,0 @@ -/*! - -\page scalar_bar_dlg Scalar Bar properties - -In this dialog you can specify the properties of the scalar bar - -\image html scalar_bar_dlg.png - -
    -
  • Scalar Range - in this menu you can specify -Min value and Max value of the Scalar Bar, and -turn on/off Logarithmic scaling of the scalar bar.
    • - -\note Logarithmic scale is not applicable in case of -negative and zero values in the range. In such cases it is disabled. - -
  • Font - in this menu you can set type, face and color for -the font of Title and Labels of the Scalar -Bar
    • - -
  • Colors & Labels - in this menu you can set the number of -colors and the number of labels of the Scalar -Bar
    • - -
  • Orientation - allows choosing between vertical and -horizontal orientation of the Scalar Bar
    • . - -
  • Origin & Size Vertical & Horizontal - allows defining the -location (X and Y) and size (Width and -Height) of Scalar Bar
    • -
      -
    • X: abscissa of the origin (from the left -side)
      • -
    • Y: ordinate of the origin (from the bottom)
      • -
    -
  • Distribution - in this menu you can Show/Hide distribution histogram of the values of the Scalar Bar and specify histogram properties
    • -
      -
    • Multicolor the histogram is colored as Scalar Bar
      • -
    • Monocolor the histogram is colored as selected with Distribution color selector
      • -
    -
- - -*/ diff --git a/doc/salome/gui/SMESH/input/scale.doc b/doc/salome/gui/SMESH/input/scale.doc deleted file mode 100644 index 57626fd78..000000000 --- a/doc/salome/gui/SMESH/input/scale.doc +++ /dev/null @@ -1,134 +0,0 @@ -/*! - -\page scale_page Scale - -\n This geometrical operation allows to scale in space your mesh -or some of its elements. - -To scale a mesh: - -
    -
  1. From the \b Modification menu choose \b Transformation -> \b Scale -\b Transform item. - -One of the following dialogs will appear: - -With one scale factor: -\image html scale01.png - -Or with different scale factors for axes: -\image html scale02.png - -
    2. - -
  2. -In the dialog: -
      -
    • specify the IDs of the translated elements: - -
        -
      • Select the whole mesh, submesh or group activating this -checkbox; or
        • -
      • choose mesh elements with the mouse in the 3D Viewer. It is -possible to select a whole area with a mouse frame; or
        • -
      • input the element IDs directly in ID Elements field. The selected elements will be highlighted in the -viewer; or
        • -
      • apply Filters. Set filter button allows to apply a filter to the selection of elements. See more -about filters in the \ref selection_filter_library_page "Selection filter library" page.
        • -
      -
      • - -
    • specify the base point for scale
      • - -
    • specify the scale factor
      • - -
    • specify the conditions of scale: -
        -
      • activate Move elements radio button to scale the selected -mesh (or elements) without creating a copy;
        • -
      • activate Copy elements radio button to duplicate the selected -mesh (or elements) and to apply scaling to the copy within the same mesh;
        • -
      • activate Create as new mesh radio button to leave the -selected mesh (or elements) at its previous location and create a new -mesh of the scaled copy of the selected elements; the new mesh appears in the Object Browser -with the default name MeshName_scaled (it is possible to change this -name in the adjacent box);
        • -
      • activate Copy groups checkbox to copy the groups of -elements existing in the source mesh to the newly created mesh.
        • -
      -
      • - - - -
    • activate Preview checkbox to show the result of transformation in the viewer
      • -
    • click \b Apply or Apply and Close button to confirm the operation.
      • -
    -
- - - -Example of using: - -1. Create quandrangle mesh 3x3 on a simple planar face (200x200) - -\image html scaleinit01.png - -and union 3 faces (along axis Z) to group "gr_faces" - -\image html scaleinit02.png - - - -2. Perform scale operation for the whole mesh and create a new mesh: - -\image html scale03.png - -result after operation: - -\image html scaleres03.png - - - -3. Perform scale operation for the whole mesh and copy elements: - -\image html scale04.png - -result after operation: - -\image html scaleres04.png - - - -4. Perform scale operation for a group of faces and copy elements: - -\image html scale06.png - -result after operation: - -\image html scaleres06.png - - - -5. Perform scale operation for two edges and move elements: - -\image html scale07.png - -result after operation: - -\image html scaleres07.png - - - -6. Perform scale operation for one face and move elements: - -\image html scale09.png - -result after operation: - -\image html scaleres09.png - - -
See Also a sample TUI Script of a \ref tui_scale "Scale" operation. - - -*/ diff --git a/doc/salome/gui/SMESH/input/segments_around_vertex_algo.doc b/doc/salome/gui/SMESH/input/segments_around_vertex_algo.doc deleted file mode 100644 index ecd2e8aa9..000000000 --- a/doc/salome/gui/SMESH/input/segments_around_vertex_algo.doc +++ /dev/null @@ -1,22 +0,0 @@ -/*! - -\page segments_around_vertex_algo_page Segments around Vertex - -\n Segments around Vertex algorithm is considered to be a 0D meshing -algorithm, but, of course, it doesn't mesh vertices. It allows to define -the local size of the segments in the neighborhood of a certain -vertex. If we assign this algorithm to a geometrical object of higher -dimension, it applies to all its vertices. - -Length of segments near vertex is defined by Length Near - Vertex hypothesis. -This hypothesis is used by \ref a1d_algos_anchor "Wire Discretization" or -\ref a1d_algos_anchor "Composite Side Discretization" algorithms as -follows: a geometrical edge is discretized according to a 1D - hypotheses and then nodes near vertices are modified to assure the - segment length required by Length Near Vertex hypothesis. - -\image html lengthnearvertex.png - - -*/ diff --git a/doc/salome/gui/SMESH/input/selection_filter_library.doc b/doc/salome/gui/SMESH/input/selection_filter_library.doc deleted file mode 100644 index 97d63ec02..000000000 --- a/doc/salome/gui/SMESH/input/selection_filter_library.doc +++ /dev/null @@ -1,281 +0,0 @@ -/*! - -\page selection_filter_library_page Selection filter library - -\tableofcontents - -\section selection_filter_library Filter library - -\n Selection filter library allows creating and storing in files -the filters that can be later reused for operations on meshes. You can -access it from the Main Menu via Tools / Selection filter library. -It is also possible to save/load a filter by invoking the filter library -from \ref filtering_elements "Filter dialog" launched from any mesh operation. - -\image html selectionfilterlibrary.png - -Library file name shows the path and the file name where your -filters will be stored. By clicking the Browse button you can -load an existing filter library. -\n Names of filters lists the filters created or uploaded for -the current study. You can \b Add or \b Delete filters. -\n In Filter name box you can specify the name for your -filter. By default it is prefixed with the corresponding entity type. - -\section filtering_elements Filter Dialog - -When we use filters during group creation or another operation (by -clicking Set Filter button in the corresponding dialog), the -dialog for setting filters looks as shown below. - -\image html a-filteronfaces.png - -The \b Add button creates a new criterion at the end of the list of -criteria. The \b Insert button creates a new criterion before the -selected criterion. The \b Remove button deletes the selected -criterion. The \b Clear button deletes all criteria.\n -If there is a choice of Entity type in the dialog, only -criteria of currently selected type are used to create or change a -filter, and criteria of hidden types (if were specified) are ignored. -\n Each Entity type has its specific list of criteria, however all -filters have common syntax. The Threshold Value should be specified -for most criteria. For numerical criteria it is necessary to indicate if -the found elements should be \b More, \b Less or \b Equal to this -\b Value. You can also reverse the sense of a criterion using \b Unary -operator \a Not and you should specify logical relations between -criteria using \b Binary operators \a Or and \a And. -\n Some criteria have the additional parameter of \b Tolerance.
-Switching on Insert filter in viewer check-box limits -selection of elements in the Viewer to the current filter. -
-In the \b Source field you choose if the filter will be applied to -the whole \b Mesh, the Initial Selection or the Current -Dialog. If \b Mesh is chosen, the elements satisfying the filter -will be selected in the 3D Viewer. If Initial Selection is -chosen, the filter will be applied to the selected elements and the -elements rejected by the filter will be deselected. If Current -Dialog is chosen, the filter will be applied to the list of -elements in the current dialog and the elements rejected -by the filter will be removed from the list. -
-Copy from... button gives you a possibility to load an -existing filter from Selection filter library and Add -to... button gives you a possibility to save your current filter -in the Library. -
-Note: If the button Apply and Close is disabled, there -is no selected mesh in the Object Browser and the filter can not be -created. You have to select the mesh and the button will be enabled. - -\section filtering_criteria Filtering Criteria - -Some criteria are applicable to all Entity types: -
  • -Belong to Geom selects entities whose all nodes lie on the -shape defined by Threshold Value. -If the threshold shape is a sub-shape of the main shape of the mesh, -the filtering algorithm works faster because node-to-shape association -is used instead of measuring distance between nodes and the shape, and -\b Tolerance is not used. If the threshold shape is any other shape, -the algorithm works slower because distance between nodes and the -shape is measured and is compared with \b Tolerance. The latter -approach (distance measurement) is also used if an element is not -associated to any shape. -
  • -Lying on Geom selects entities whose at least one node -lies on the shape defined by the Threshold Value. -If the threshold shape is a sub-shape of the main shape of the mesh, -the filtering algorithm works faster because node-to-shape association -is used instead of measuring distance between nodes and the shape, and -\b Tolerance is not used. If the threshold shape is any other shape, -the algorithm works slower because distance between nodes and the -shape is measured and is compared with \b Tolerance. The latter -approach (distance measurement) is also used if an element is not -associated to any shape. -
  • -Belong to Mesh Group selects entities included into the mesh group -defined by the Threshold Value. -
  • -Range of IDs allows selection of entities with the specified -IDs. -Threshold Value can be, for example: "1,2,3,50-60,63,67,70-78" -
  • -Color of Group allows selection of entities belonging to the Group with -the color defined by the Threshold Value. -
  • -Elements of a domain allows selection of entities belonging to -one domain of a mesh. The domain is mesh part not connected to -other parts. Threshold Value locating any element of the domain can be either -- node ID (that you can pick in the Viewer) or -- geometrical vertex (that you can pick either in the Viewer or in the - Object Browser) or -- 3 coordinates of a point (that you can enter in TUI mode only). - -
    • -
- -Some criteria are applicable to entities of dimension -more than zero, i.e. to \b Edges, \b Faces and \b Volumes: -
  • -Linear allows selection of Linear or Quadratic elements (if Unary is set to "Not") -
  • -Geometry type allows selection of elements by their geometric type -defined by the Threshold Value. The list of available geometric -types depends on the current entity type. -
  • -Entity type allows selection of elements by their type defined -as a combination of geometry type and the number of nodes. -
    • -
- -The following criteria are applicable to Entities of \b all types -except for \a Volumes: -
  • -Belong to Plane selects entities whose all nodes belong to a -specified plane within a given Tolerance. -
  • -Belong to Cylinder selects entities whose all nodes belong to a -specified cylinder within a given Tolerance. -
  • -Belong to Surface selects entities whose all nodes belong to a -specified arbitrary surface within a given Tolerance. -
    • -
- -The following criteria allow selecting mesh Nodes: -
  • -Free nodes selects nodes not belonging to any mesh element. -
  • -Double nodes selects a node coincident with other nodes -(within a given Tolerance). -See also \ref tui_double_nodes_control "Double Nodes quality control". -
  • -Connectivity number selects nodes with a number of connected -elements, which is more, less or equal to the predefined Threshold - Value. Elements of the highest dimension are countered only. -
    • -
- -The following criteria allow selecting mesh Edges: -
  • -Free Borders selects free 1D mesh elements, i.e. edges belonging to -one element (face or volume) only. See also a -\ref free_borders_page "Free Borders quality control". -
  • -Double edges selects 1D mesh elements basing on the same set of nodes. -See also \ref filter_double_elements "Double Elements quality control". -
  • -Borders at Multi-Connections selects edges belonging to several faces. -The number of faces should be more, less or equal (within a given Tolerance) -to the predefined Threshold Value. See also a -\ref borders_at_multi_connection_page "Borders at Multi-Connection quality control". -
  • -Length selects edges with a value of length, which is more, less or equal -(within a given Tolerance) to the predefined Threshold Value. -See also a -\ref length_page "Length quality control". -
    • -
- -The following criteria allow selecting mesh Faces: -
  • -Aspect ratio selects 2D mesh elements with an aspect ratio (see also an -\ref aspect_ratio_page "Aspect Ratio quality control"), which is more, less or equal -(within a given Tolerance) to the predefined Threshold Value. -
  • -Warping selects quadrangles with warping angle (see also a -\ref warping_page "Warping quality control"), which is more, less or equal -(within a given Tolerance) to the predefined Threshold Value. -
  • -Minimum angle selects triangles and quadrangles with minimum angle (see also a -\ref minimum_angle_page "Minimum angle quality control"), which is more, less or equal -(within a given Tolerance) to the predefined Threshold Value. -
  • -Taper selects quadrangles cells with taper value (see also a -\ref taper_page "Taper quality control"), which is more, less or equal (within a given -Tolerance) to the predefined Threshold Value. -
  • -Skew selects triangles and quadrangles with skew value (see also a -\ref skew_page "Skew quality control"), which is more, less or equal (within a given -Tolerance) to the predefined Threshold Value. -
  • -Area selects triangles and quadrangles with a value of area (see also an -\ref area_page "Area quality control"), which is more, less or equal (within a given -Tolerance) to the predefined Threshold Value. -
  • -Free edges selects 2D mesh elements having at least one -edge, which is not shared with other faces. See also a -\ref free_edges_page "Free Edges quality control". -
  • -Free faces selects 2D mesh elements, which belong to less than two volumes. -
  • -Double faces selects 2D mesh elements basing on the same set of nodes. -See also \ref filter_double_elements "Double Elements quality control". -
  • -Faces with bare border selects 2D mesh elements having a free border without an edge on it. -See also \ref bare_border_faces_page "Bare border faces quality control". -
  • -Over-constrained faces selects 2D mesh elements having only one border shared -with other 2D elements. -See also \ref over_constrained_faces_page "Over-constrained faces quality control". -
  • -Borders at Multi-Connections 2D selects cells consisting of edges belonging to -several elements of mesh. The number of mesh elements should be more, less or equal -(within a given Tolerance) to the predefined Threshold Value. -See also a -\ref borders_at_multi_connection_2d_page "Borders at Multi-Connection 2D quality control". -
  • -Length 2D selects triangles and quadrangles combining of the edges with a value of -length, which is more, less or equal (within a given Tolerance) to the predefined -Threshold Value. See also a -\ref length_2d_page "Length 2D quality control". -
  • -Coplanar faces selects mesh faces neighboring the one selected -by ID in Threshold Value field, if the angle between the -normal to the neighboring face and the normal to the selected face is less then the -angular tolerance (defined in degrees). Selection continues among all neighbor faces of already -selected ones.
    -
  • -Deflection 2D selects 2D mesh elements having distance between their gravity -centers and underlying surfaces, which is more, less or equal (within a given Tolerance) to the predefined Threshold Value. See also a -\ref deflection_2d_page "Deflection 2D quality control". -
  • -Element Diameter 2D selects triangles and quadrangles composed of the edges and -diagonals with a value of length, which is more, less or equal -(within a given Tolerance) to the predefined Threshold Value. See also a -\ref max_element_length_2d_page "Element Diameter 2D quality control". -
    • -
- -The following criteria allow selecting mesh Volumes: -
  • -Aspect ratio 3D selects 3D mesh elements with an aspect ratio (see also an -\ref aspect_ratio_3d_page "Aspect Ratio 3D quality control"), which is more, less or equal -(within a given Tolerance) to the predefined Threshold Value. -
  • -Volume selects 3D mesh elements with a value of volume (see also a -\ref volume_page "Volume quality control"), which is more, less or equal (within a given -Tolerance) to the predefined Threshold Value. -
  • -Element Diameter 3D selects 3D mesh elements composed of the edges and -diagonals with a value of length, which is more, less or equal -(within a given Tolerance) to the predefined Threshold Value. See also a -\ref max_element_length_3d_page "Element Diameter 3D quality control". -
  • -Double volumes selects 3D mesh elements basing on the same set of nodes. -See also \ref filter_double_elements "Double Elements quality control". -
  • -Bad oriented volume selects mesh volumes, which are incorrectly oriented from -the point of view of MED convention. -
  • -Over-constrained volumes selects mesh volumes having only one facet shared -with other volumes. -See also \ref over_constrained_volumes_page "Over-constrained volumes quality control". -
  • -Volumes with bare border selects 3D mesh elements having a free border without a face on it. -See also \ref bare_border_volumes_page "Bare border volumes quality control". -
    • -
- - -*/ diff --git a/doc/salome/gui/SMESH/input/sewing_meshes.doc b/doc/salome/gui/SMESH/input/sewing_meshes.doc deleted file mode 100644 index cfb6206dd..000000000 --- a/doc/salome/gui/SMESH/input/sewing_meshes.doc +++ /dev/null @@ -1,234 +0,0 @@ -/*! - -\page sewing_meshes_page Sewing meshes - -\n In SMESH you can sew elements of a mesh. The current -functionality allows you to sew: -
    -
  • \ref free_borders_anchor "Free borders"
    • -
  • \ref conform_free_borders_anchor "Conform free borders"
    • -
  • \ref border_to_side_anchor "Border to side"
    • -
  • \ref side_elements_anchor "Side elements"
    • -
- -\image html sewing.png "Sewing button" - -To sew elements of a mesh: -
    -
  1. From the \b Modification menu choose the \b Transformation item -and from its sub-menu select the \b Sewing item.
    2. -
  2. Check in the dialog box one of the radio buttons corresponding to -the type of sewing operation you would like to perform.
    3. -
  3. Fill the other fields available in the dialog box.
    4. -
  4. Click the \b Apply or Apply and Close button to perform the - operation of sewing.
    5. -
- - -
-\anchor free_borders_anchor -

Sew free borders

- -This functionality allows you to unite free borders of a 2D mesh. - -There are two working modes: \a Automatic and \a Manual. In the \b -Automatic mode, the program finds free borders coincident within the -specified tolerance and sews them. Optionally it is possible to -visually check and correct if necessary the found free borders before -sewing.
-In the \b Manual mode you are to define borders to sew by picking -three nodes of each of two borders. - -\image html sewing1.png -
Default mode is \a Automatic
- -To use \b Automatic sewing: -
    -
  • Specify the mesh you want to sew by selecting it or any its part - (group or sub-mesh) in the Object Browser or in the VTK Viewer.
    • -
  • Specify the \b Tolerance, within which free borders are considered - coincident. At the default zero \b Tolerance, the tolerance used by - the search algorithm is defined as one tenth of an average size of - elements adjacent to compared free borders.
    • -
  • To visually check the coincident free borders found by the - algorithm, switch off Auto Sewing check-box. The controls - to adjust groups of coincident free borders will become available in - the dialog.
    • - -\image html sewing_auto.png -
    Controls to adjust groups of coincident free borders
    - -
  • \b Detect button launches the algorithm of search of coincident - free borders.
    • -
  • The found groups of Coincident Free Borders are shown in the - list, one group per line. Each group has its own color, which is used - to display the group borders in the VTK Viewer. A free border - within a group is designated by the IDs of its first, second and - last nodes within parenthesis. All borders present in the list will - be sewn upon \b Apply.
    • -
  • \b Remove button removes the selected groups from the list.
    • -
  • Select All check-box selects all groups in the list.
    • -
  • When a group is selected, its borders appear in Edit Selected - Group list that allows you to change this group.
    • -
  • -\image html sort.png -Set First button moves the selected border to the - first position in the group, as a result other borders will be moved - to this border during sewing. -
  • -\image html remove.png -Remove Border button removes the selected borders from the - group. It is active if there are more than two borders in the group. -
    • -
  • Selection of a border in the list allows changing its first and - last nodes whose IDs appear in two fields below the list. \a Arrow - buttons near each field move the corresponding end node by the - number of nodes defined by \b Step field.
    • -
  • -\image html swap.png -Swap button swaps the first and last nodes of a - selected border. -
    • -
- -For sewing free borders manually you should switch the \b Mode to \b -Manual and define three points on each border: the first, the second and the -last node: - -\image html sewing_manual.png -
    -
  • the first node specifies beginning of the border;
    • -
  • the second node specifies the part of the border which should be -considered (as far as the free border usually forms a closed -contour);
    • -
  • the last node specifies the end of the border.
    • -
- -You can select these nodes in the 3D viewer or define by its id. - -The first and the second nodes should belong to the same link of a -face. The second and the last nodes of a border can be the same. The -first and the last nodes of two borders can be the same. The -corresponding end nodes of two borders will be merged. Intermediate -nodes of two borders will be either merged or inserted into faces of -the opposite border. - -In practice the borders to sew often coincide and in this case it is -difficult to specify the first and the last nodes of a border since -they coincide with the first and the last nodes of the other -border. To cope with this, -\ref merging_nodes_page "merge" coincident nodes into one -beforehand. Two figures below illustrate this approach. -\image html sew_using_merge.png "Merge coincident nodes, which are difficult to distinguish" -
-\image html sew_after_merge.png "After merging nodes it is easy to specify border nodes" - -The sewing algorithm is as follows: -
    -
  1. The parameter (U) of each node within a border is computed. So -that the first node has U=0.0, the last node has U=1.0, for the rest -nodes 0.0 < U < 1.0;
    2. -
  2. Compare node parameters of the two borders. If two nodes of the -opposite borders have close parameters, they are merged, i.e. a node -of the first border is replaced in all elements by a node of the -second border. If a node has no node with a close parameter in the -opposite border, it is inserted into an edge of element of the -opposite border, an element is split. Two nodes are considered close -enough to merge, if difference of their parameters is less than one -fifth of minimum length of adjacent face edges on the borders.
    3. -
- -\image html image22.jpg "Sewing free borders" - -See Also a sample TUI Script of a -\ref tui_sew_free_borders "Sew Free Borders" operation. - -
-\anchor conform_free_borders_anchor -

Sew conform free borders

- -This functionality can be used to unite two free borders of a 2D mesh. - -\image html sewing2.png - -The borders of meshes for sewing are defined as for "Sew free borders" -except that the second free border is not limited and can be defined -by the first and the second nodes only. The first nodes of two borders -can be the same. - -The algorithm is following: counting nodes starting at the first ones, -the n-th node of the first border is merged with the n-th node of the -other border, until the end of either of borders. Nodes of the first -border are replaced in all elements with corresponding nodes of the -second border. -\n For sewing conform free borders you should define three points on -the first border and two points on the second one. User can select -these nodes in 3D viewer or define node by its id. - -\image html image23.jpg "Sewing conform free borders" - -See Also a sample TUI Script of a -\ref tui_sew_conform_free_borders "Sew Conform Free Borders" -operation. - -
-\anchor border_to_side_anchor -

Sew border to side

- -"Sew border to side" is intended to sew a free border to a mesh -surface. -\n The free border is defined as for "Sewing of free borders". The -place where to sew the border is defined by two nodes, between which -the border faces are placed, so that the first border node is merged -with the first node on the side and the last node of the border is -merged with the second specified node on the side. - -\image html sewing3.png - -The algorithm is following. -
    -
  1. Find a sequence of linked nodes on the side such that the found -links to be most co-directed with the links of the free border.
    2. -
  2. Sew two sequences of nodes using algorithm of "Sewing of free berders". -\n For sewing border to side you should define three points on the -border and two points on the side. User can select these nodes in 3D -viewer or define node by its id.
    3. -
- -\image html image30.jpg "Sewing border to side" - -See Also a sample TUI Script of a -\ref tui_sew_meshes_border_to_side "Sew Border to Side" operation. - -
-\anchor side_elements_anchor -

Sew side elements

- -This operation is intended to unite two mesh surfaces. - -\image html sewing4.png - -Surfaces may be defined by either 2d or 3d elements. The number of -given elements of the sides must be the same. The sets of given -elements must be topologically equal, i.e. each node of one element -set must have a corresponding node in the other element set and -corresponding nodes must be equally linked. If there are 3d elements -in a set, only their free faces must obey to that rule. -\n Two corresponding nodes on each side must be specified. They must -belong to one element and must be located on an element set boundary. - -Sewing algorithm finds and merges the corresponding nodes starting -from the specified ones. - -\image html image31.jpg "Step-by-step sewing process" - -\image html image32.jpg "The result of side elements sewing" - -For sewing side elements you should define elements for sewing and two -nodes for merging on the each side. User can select these elements and -nodes in 3D viewer or define them by its id. - -See Also a sample TUI Script of a -\ref tui_sew_side_elements "Sew Side Elements" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/skew.doc b/doc/salome/gui/SMESH/input/skew.doc deleted file mode 100644 index 01f3c5fea..000000000 --- a/doc/salome/gui/SMESH/input/skew.doc +++ /dev/null @@ -1,33 +0,0 @@ -/*! - -\page skew_page Skew - -\n \b Skew mesh quality criterion reflects the angle between the lines -that join opposite sides of a quadrangle element or the greatest angle -between a median and a midline in a triangle element. This mesh quality -criterion can be applied to elements composed of 4 and 3 nodes -(quadrangles and triangles). - -\image html image27.jpg - -To apply the Skew quality criterion to your mesh: -
    -
  1. Display your mesh in the viewer.
    2. - -
  2. Choose Controls > Face Controls > Skew or click -"Skew" button of the toolbar. - -\image html image40.png -
    "Skew" button
    - -Your mesh will be displayed in the viewer with its elements colored -according to the applied mesh quality control criterion: - -\image html image93.jpg -
    3. -
- -
See Also a sample TUI Script of a -\ref tui_skew "Skew quality control" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/smesh_migration.doc b/doc/salome/gui/SMESH/input/smesh_migration.doc deleted file mode 100644 index 71c18b1e0..000000000 --- a/doc/salome/gui/SMESH/input/smesh_migration.doc +++ /dev/null @@ -1,100 +0,0 @@ -/*! - -\page smesh_migration_page Modifying Mesh Python scripts from SALOME 6 and before - -\n In SALOME 7.2, the Python interface for %Mesh has been slightly modified to offer new functionality: - -\n Scripts generated for SALOME 6 and older versions must be adapted to work in SALOME 7.2 with full functionality. -\n The compatibility mode allows old scripts to work in almost all cases, but with a warning. - -See also \subpage geompy_migration_page - -Salome initialisation must always be done as shown below -\n (salome_init() can be invoked safely several times): -\code -import salome -salome.salome_init() -\endcode - -smesh initialisation is modified. -\n the old mode (from dump): -\code -import smesh, SMESH, SALOMEDS -smesh.SetCurrentStudy(salome.myStudy) -\endcode -\n the new mode: -\code -import SMESH, SALOMEDS -from salome.smesh import smeshBuilder -smesh = smeshBuilder.New(salome.myStudy) -\endcode - - - Of course, from smesh import * is no more possible. -\n You have to explicitly write smesh.some_method(). - -All algorithms have been transferred from the namespace smesh to the namespace smeshBuilder. -\n For instance: -\code -MEFISTO_2D_1 = Mesh_1.Triangle(algo=smesh.MEFISTO,geom=Face_1) -\endcode -is replaced by: -\code -MEFISTO_2D_1 = Mesh_1.Triangle(algo=smeshBuilder.MEFISTO,geom=Face_1) -\endcode -\n StdMeshers algorithms concerned are REGULAR, PYTHON, COMPOSITE, MEFISTO, Hexa, QUADRANGLE, RADIAL_QUAD. -\n SMESH Plugins provide such algorithms as: NETGEN, NETGEN_FULL, FULL_NETGEN, NETGEN_1D2D3D, NETGEN_1D2D, NETGEN_2D, NETGEN_3D. -\n If you use DISTENE plugins, you also have BLSURF, GHS3D, GHS3DPRL, Hexotic. - -Some variables were available in both namespaces smesh and SMESH. -Now they are available only in namespace SMESH. -\n The dump function used only the namespace SMESH, -so, if your script was built with the help of the dump function, it should be already OK in this respect. - -The most used variables concerned are: -\n NODE, EDGE, FACE, VOLUME, ALL. -\n FT_xxx, geom_xxx, ADD_xxx... - -\n For instance: -\code -srcFaceGroup = srcMesh.GroupOnGeom( midFace0, "src faces", smesh.FACE ) -mesh.MakeGroup("Tetras",smesh.VOLUME,smesh.FT_ElemGeomType,"=",smesh.Geom_TETRA) -filter = smesh.GetFilter(smesh.FACE, smesh.FT_AspectRatio, smesh.FT_MoreThan, 6.5) -\endcode -is replaced by: -\code -srcFaceGroup = srcMesh.GroupOnGeom( midFace0, "src faces", SMESH.FACE ) -mesh.MakeGroup("Tetras",SMESH.VOLUME,SMESH.FT_ElemGeomType,"=",SMESH.Geom_TETRA) -filter = smesh.GetFilter(SMESH.FACE, SMESH.FT_AspectRatio, SMESH.FT_MoreThan, 6.5) -\endcode - - -The namespace smesh.smesh does not exist any more, use smesh instead. -\n For instance: -\code -Compound1 = smesh.smesh.Concatenate([Mesh_inf.GetMesh(), Mesh_sup.GetMesh()], 0, 1, 1e-05) -\endcode -is replaced by: -\code -Compound1 = smesh.Concatenate([Mesh_inf.GetMesh(), Mesh_sup.GetMesh()], 0, 1, 1e-05) -\endcode - -If you need to import a %SMESH Plugin explicitly, keep in mind that they are now located in separate namespaces. -\n For instance: -\code -import StdMeshers -import NETGENPlugin -import BLSURFPlugin -import GHS3DPlugin -import HexoticPLUGIN -\endcode -is replaced by: -\code -from salome.StdMeshers import StdMeshersBuilder -from salome.NETGENPlugin import NETGENPluginBuilder -from salome.BLSURFPlugin import BLSURFPluginBuilder -from salome.GHS3DPlugin import GHS3DPluginBuilder -from salome.HexoticPLUGIN import HexoticPLUGINBuilder -\endcode - -*/ diff --git a/doc/salome/gui/SMESH/input/smeshpy_interface.doc b/doc/salome/gui/SMESH/input/smeshpy_interface.doc deleted file mode 100644 index 524a4ceb0..000000000 --- a/doc/salome/gui/SMESH/input/smeshpy_interface.doc +++ /dev/null @@ -1,97 +0,0 @@ -/*! - -\page smeshpy_interface_page Python interface - -Python API of SALOME %Mesh module defines several classes that can -be used for easy mesh creation and edition. - -Documentation of SALOME %Mesh module Python API is available in two forms: -- Structured documentation, where all methods and -classes are grouped by their functionality. -- Linear documentation grouped only by classes, declared -in the \ref smeshBuilder and \ref StdMeshersBuilder Python packages. - -\n With SALOME 7.2, the Python interface for %Mesh has been slightly modified to offer new functionality. -\n You may have to modify your scripts generated with SALOME 6 or older versions. -\n Please see \subpage smesh_migration_page. - -Class \ref smeshBuilder.smeshBuilder "smeshBuilder" provides an interface to create and handle -meshes. It can be used to create an empty mesh or to import mesh from the data file. - -As soon as a mesh is created, it is possible to manage it via its own -methods, described in class \ref smeshBuilder.Mesh "Mesh" documentation. - -Class \ref smeshstudytools.SMeshStudyTools "SMeshStudyTools" provides several methods to manipulate mesh objects in Salome study. - -A usual workflow to generate a mesh on geometry is following: -
    -
  1. Create an instance of \ref smeshBuilder.smeshBuilder "smeshBuilder": - 
    -      from salome.smesh import smeshBuilder
-      smesh = smeshBuilder.New( salome.myStudy )
-
    2. -
  2. Create a \ref smeshBuilder.Mesh "mesh" object: - 
    -      mesh = \ref smeshBuilder.smeshBuilder.Mesh "smesh.Mesh( geometry )" 
-
    3. -
  3. Create and assign \ref basic_meshing_algos_page "algorithms" by - calling corresponding methods of the mesh. If a sub-shape is - provided as an argument, a \ref constructing_submeshes_page "sub-mesh" - is implicitly created on this sub-shape: - 
    -      regular1D = \ref smeshBuilder.Mesh.Segment "mesh.Segment"()
-      mefisto   = \ref smeshBuilder.Mesh.Triangle "mesh.Triangle"( smeshBuilder.MEFISTO )
-      # use other triangle algorithm on a face -- a sub-mesh appears in the mesh
-      netgen    = \ref smeshBuilder.Mesh.Triangle "mesh.Triangle"( smeshBuilder.NETGEN_1D2D, face )
-
    4. -
  4. Create and assign \ref about_hypo_page "hypotheses" by calling - corresponding methods of algorithms: - 
    -      segLen10 = \ref StdMeshersBuilder.StdMeshersBuilder_Segment.LocalLength "regular1D.LocalLength"( 10. )
-      maxArea  = \ref StdMeshersBuilder.StdMeshersBuilder_Segment.LocalLength "mefisto.MaxElementArea"( 100. )
-      netgen.SetMaxSize( 20. )
-      netgen.SetFineness( smeshBuilder.VeryCoarse )
-
    -
    5. -
  5. \ref compute_anchor "Compute" the mesh (generate mesh nodes and elements): - 
    -      \ref Mesh.Compute "mesh.Compute"()
-
    -
    6. -
- -An easiest way to start with Python scripting is to do something in -GUI and then to get a corresponding Python script via - File > Dump Study menu item. Don't forget that you can get -all methods of any object in hand (e.g. a mesh group or a hypothesis) -by calling \a dir() Python built-in function. - -All methods of the Mesh Group can be found in \ref tui_create_standalone_group sample script. - -An example below demonstrates usage of the Python API for 3d mesh -generation and for retrieving information on mesh nodes and elements. - -\anchor example_3d_mesh -

Example of 3d mesh generation:

-\tui_script{3dmesh.py} - -Examples of Python scripts for Mesh operations are available by -the following links: - -- \subpage tui_creating_meshes_page -- \subpage tui_defining_hypotheses_page -- \subpage tui_grouping_elements_page -- \subpage tui_filters_page -- \subpage tui_modifying_meshes_page -- \subpage tui_transforming_meshes_page -- \subpage tui_viewing_meshes_page -- \subpage tui_quality_controls_page -- \subpage tui_measurements_page -- \subpage tui_work_on_objects_from_gui -- \subpage tui_notebook_smesh_page -- \subpage tui_cartesian_algo -- \subpage tui_use_existing_faces -- \subpage tui_prism_3d_algo -- \subpage tui_generate_flat_elements_page - -*/ diff --git a/doc/salome/gui/SMESH/input/smoothing.doc b/doc/salome/gui/SMESH/input/smoothing.doc deleted file mode 100644 index 801b1c9d8..000000000 --- a/doc/salome/gui/SMESH/input/smoothing.doc +++ /dev/null @@ -1,89 +0,0 @@ -/*! - -\page smoothing_page Smoothing - -\n Smoothing is used to improve quality of 2D mesh by adjusting the -locations of element corners (nodes). - -\note Depending on the chosen method and mesh geometry -the smoothing can actually decrease the quality of elements and even -make some elements inverted. - -To apply smoothing to the elements of your mesh: -
    - -
  1. In the \b Modification menu select the \b Smoothing item or click -"Smoothing" button in the toolbar. - -\image html image84.png -
    "Smoothing" button
    - -The following dialog will appear: - -\image html smoothing.png -
    2. -
  2. In this dialog: - -
      -
    • specify the IDs of the elements which will be smoothed: -
        -
      • Select the whole mesh, sub-mesh or group activating this - check-box; or
        • -
      • choose mesh elements with the mouse in the 3D Viewer. It is - possible to select a whole area with a mouse frame; or
        • -
      • input the element IDs directly in ID Elements field. The - selected elements will be highlighted in the viewer; or
        • -
      • apply Filters. Set filters button allows to apply a filter - to the selection of elements. See more about filters in the - \ref filtering_elements "Selection filter library" page.
        • -
      -
      • - -
    • define the Fixed nodes ids that should remain at their - location during smoothing. If a mesh is built on a shape, the nodes - built on its geometric edges are always fixed. If the smoothing is - applied to a part of the mesh (a set of element), the nodes on - boundary of the element set are also fixed. It is possible to - additionally fix any other nodes. The fixed nodes can be selected - manually or by filters, just as the smoothed elements.
      • -
    • choose the Smoothing Method: -
        -
      • \b Laplacian smoothing pulls a node toward the center of -surrounding nodes directly connected to that node along an element -edge. -
      • \b Centroidal smoothing pulls a node toward the -element-area-weighted centroid of the surrounding elements.
        • - -Laplacian method will produce the mesh with the least element -edge length. It is also the fastest method. Centroidal smoothing -produces a mesh with more uniform element sizes. -
      - -\image html image83.gif - -
      • -
    • specify the Iteration limit. Both smoothing methods iterate - through a number of steps to produce the resulting smoothed mesh. At - each new step the smoothing is reevaluated with the updated nodal - locations. This process continues till the limit of iterations has - been exceeded, or till the aspect ratio of all element is less than - or equal to the specified one.
      • -
    • specify the Max. aspect ratio - the target mesh quality at - which the smoothing algorithm should stop the iterations.
      • -
    • activate in parametric space check-box if it is necessary to - improve the shape of faces in the parametric space of geometrical - surfaces on which they are generated, else the shape of faces in the - 3D space is improved that is suitable for planar meshes only.
      • -
    -
    3. -
  3. Click \b Apply or Apply and Close button to confirm the operation.
    4. -
- -\image html smoothing1.png "The initial mesh" - -\image html smoothing2.png "The smoothed mesh" - -
See Also a sample TUI Script of a -\ref tui_smoothing "Smoothing" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/split_biquad_to_linear.doc b/doc/salome/gui/SMESH/input/split_biquad_to_linear.doc deleted file mode 100644 index ea4ac7228..000000000 --- a/doc/salome/gui/SMESH/input/split_biquad_to_linear.doc +++ /dev/null @@ -1,37 +0,0 @@ -/*! - -\page split_biquad_to_linear_page Split bi-quadratic into linear - -\n This functionality allows to split bi-quadratic elements into -linear ones without creation of additional nodes. - -So that -- bi-quadratic triangle will be split into 3 linear quadrangles; -- bi-quadratic quadrangle will be split into 4 linear quadrangles; -- tri-quadratic hexahedron will be split into 8 linear hexahedra; -- quadratic segments adjacent to the split bi-quadratic element will - be split into 2 liner segments. - -\image html split_biquad_to_linear_mesh.png "Mesh before and after splitting" - -To split bi-quadratic elements into linear: -
    -
  1. From the \b Modification menu choose the Split bi-quadratic into linear item or -click "Split bi-quadratic into linear" button in the toolbar. - -\image html split_biquad_to_linear_icon.png -
    "Split bi-quadratic into linear" button
    - -The following dialog box shall appear: - -\image html split_biquad_to_linear_dlg.png - -
    2. -
  2. Select a mesh, groups or sub-meshes in the Object Browser or in the - Viewer.
    3. -
  3. Click the \b Apply or Apply and Close button.
    4. -
- -
See Also a sample TUI Script of a \ref tui_split_biquad "Split bi-quadratic into linear" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/split_to_tetra.doc b/doc/salome/gui/SMESH/input/split_to_tetra.doc deleted file mode 100644 index b6ee36e93..000000000 --- a/doc/salome/gui/SMESH/input/split_to_tetra.doc +++ /dev/null @@ -1,68 +0,0 @@ -/*! - -\page split_to_tetra_page Splitting volumes - -\n This operation allows to split either any volumic elements into -tetrahedra or hexahedra into prisms. 2D mesh is modified accordingly. - -To split volumes: -
    -
  1. Select a mesh, a sub-mesh or a group.
    2. -
  2. In the \b Modification menu select the Split Volumes item or -click "Split Volumes" button in the toolbar. - -\image html split_into_tetra_icon.png -
    "Split Volumes" button
    - -The following dialog box will appear: - -\image html split_into_tetra.png - -
    -First it is possible to select the type of operation: -- If \b Tetrahedron button is checked, the operation will split volumes of any type into tetrahedra. -- If \b Prism button is checked, the operation will split hexahedra into prisms. - -
      -
    • The main list contains the list of volumes to split. You can click on - a volume in the 3D viewer and it will be highlighted (lock Shift - keyboard button to select several volumes). Click \b Add button and - the ID of this volume will be added to the list. To remove the - selected element or elements from the list click \b Remove button. Sort - list button allows to sort the list of IDs. \b Filter button allows applying a filter to the selection of volumes. -
      Note: If you split not all adjacent non-tetrahedral - volumes, your mesh becomes non-conform.
      • - -
    • Apply to all radio button allows splitting all - volumes of the currently selected mesh.
      • - -
    • If \b Tetrahedron element type is selected, Split hexahedron group allows specifying the number of tetrahedra a hexahedron will be split into. If the chosen method does not allow to get a conform mesh, a generic solution is applied: an additional node is created at the gravity center of a hexahedron, serving an apex of tetrahedra, all quadrangle sides of the hexahedron are split into two triangles each serving a base of a new tetrahedron.
      • - -
    • If \b Prism element type is selected, the Split hexahedron group looks as follows: - -\image html split_into_prisms.png - -
        -
      • Into 2 (or 4) prisms allows to specify the number of prisms a hexahedron will be split into.
        • -
      • Facet to split group allows to specify the side (facet) of the hexahedron, which is split into triangles. This facet is defined by a point and a direction. The algorithm finds a hexahedron closest to the specified point and splits a facet whose normal is closest to the specified direction. Then the splitting is propagated from that hexahedron to all adjacent hexahedra. -The point and the direction by which the first split hexahedron is found can be specified: -
          -
        • by input of coordinates in Hexa location and Facet normal fields, or
          • -
        • by clicking Selection button and selecting in the viewer the element whose barycenter will be used as the start point and whose direction will be used as a normal to facet to split into triangles. Switch this button -off to return to selection of volumes to split.
          • -
        - -
      • If All domains option is off, the operation stops when all - hehexedra adjacent to the start hexahedron are split into - prisms. Else the operation tries to continue splitting starting from - another hexahedron closest to the Hexa location.
        • - -
      - -
    • Select from set of fields allows choosing a sub-mesh or an - existing group whose elements will be added to the list as you click \b Add button.
      • -
    - -
  3. Click \b Apply or Apply and Close button to confirm the operation.
    4. -
-*/ diff --git a/doc/salome/gui/SMESH/input/symmetry.doc b/doc/salome/gui/SMESH/input/symmetry.doc deleted file mode 100644 index 4641ffe31..000000000 --- a/doc/salome/gui/SMESH/input/symmetry.doc +++ /dev/null @@ -1,92 +0,0 @@ -/*! - -\page symmetry_page Symmetry - -\n This geometrical operation allows to perform a symmetrical copy of -your mesh or some of its elements. - -To create a symmetrical copy: - -
    -
  1. From the \b Modification menu choose \b Transformation -> \b Symmetry item or click -"Symmetry" button in the toolbar. - -\image html symmetry.png "Symmetry button" - -One of the following dialogs will appear: - -It is possible to mirror a mesh or some of its elements through: -\image html symmetry1.png "a point"
    -\image html symmetry2.png "an axis"
    -\image html symmetry3.png "a plane (defined by a point and a normal to the plane)" - -
    2. - -
  2. In the dialog: -
      -
    • specify the elements for the symmetry operation: - -
        -
      • Select the whole mesh, submesh or group activating this -checkbox; or
        • -
      • choose mesh elements with the mouse in the 3D Viewer. It is -possible to select a whole area with a mouse frame; or
        • -
      • input the element IDs directly in ID Elements field. The - selected elements will be highlighted in the viewer; or
        • -
      • apply Filters. Set Filter button allows to apply a - \ref filtering_elements "filter" to the selection of elements.
        • -
      -
      • - -
    • depending on the nature of the mirror object: -
        -
      • if the mesh is mirrored through a point, specify the coordinates - of the point, either directly or by picking a mesh node;
        • -
      • if the mesh is mirrored through an axis: -
          -
        • specify the coordinates of the start \b Point of the axis, either - directly or by picking a mesh node;
          • -
        • specify the components of axis \b Vector, either directly or by - picking a mesh node, in which case \b Vector is defined as a shift - between the \b Point and the node;
          • -
        -
        • - -
      • if the mesh is mirrored through a plane: -
          -
        • specify the cooordinates of the \b Point lying on the plane, - either directly or by picking a mesh node;
          • -
        • specify the components of plane \b Normal, either directly or by - picking a mesh node, in which case \b Normal is defined as a shift - between the \b Point and the node.
          • -
        -
        • - -
      • specify the conditions of symmetry operation: -
          -
        • activate Move elements radio button to change the location of - the selected elements within the current mesh;
          • -
        • activate Copy elements radio button to duplicate the - selected elements at the new location within the current mesh;
          • -
        • activate Create as new mesh radio button to create a new - element in a new mesh; the new mesh appears in the Object Browser - with the default name \a MeshName_mirrored (it is possible to change - this name in the adjacent box);
          • -
        • activate Copy groups check-box to put new mesh entities - into new groups if source entities belong to some groups. New - groups are named by pattern "_mirrored".
          • -
        -
        • -
      -
    • activate Preview check-box to show the result of - transformation in the viewer;
      • -
    • click \b Apply or Apply and Close button to confirm the - operation.
      • -
    - -
- -
See Also a sample TUI Script of a -\ref tui_symmetry "Symmetry" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/taper.doc b/doc/salome/gui/SMESH/input/taper.doc deleted file mode 100644 index da3ed83f6..000000000 --- a/doc/salome/gui/SMESH/input/taper.doc +++ /dev/null @@ -1,32 +0,0 @@ -/*! - -\page taper_page Taper - -\n \b Taper mesh quality criterion represents the ratio of the areas -of two triangles separated by a diagonal within a quadrilateral face. - -
JA = 0.25 * (A1 + A2 + A3 + A4) -
TAPER = MAX(|A1/JA - 1|, |A2/JA - 1|, |A3/JA - 1|, |A4/JA - 1|)
 - -
To apply the Taper quality criterion to your mesh: - -
    -
  1. Display your mesh in the viewer.
    2. - -
  2. Choose Controls > Face Controls > Taper or click -"Taper" button in the toolbar. - -\image html image36.png -
    "Taper" button
    - -Your mesh will be displayed in the viewer with its elements colored -according to the applied mesh quality control criterion: - -\image html image90.jpg -
    3. -
- -
See Also a sample TUI Script of a -\ref tui_taper "Taper quality control" operation. - -*/ \ No newline at end of file diff --git a/doc/salome/gui/SMESH/input/tools.doc b/doc/salome/gui/SMESH/input/tools.doc deleted file mode 100644 index 041a07385..000000000 --- a/doc/salome/gui/SMESH/input/tools.doc +++ /dev/null @@ -1,16 +0,0 @@ -/*! - -\page tools_page Plugins - -The following plugins are accessible via Mesh > SMESH pligins menu: - -- SpherePadder plugin -- MGSurfOpt plugin -- MGCleaner plugin -- Z-cracks plugin -- MacMesh plugin -- blocFissure plugin -- MeshCut plugin - allows to cut a mesh constituted of linear tetrahedrons by a plane. -- Get min or max value of control - a sample plugin whose sources are located in ${GUI_ROOT_DIR}/share/salome/plugins/gui/demo directory (files minmax_plugin.py, minmax_ui.py and smesh_plugins.py). You can find a detailed description of how to create your own plugin in documentation: Help > GUI module > User's Guide > How-To's and Best Practices > Extend SALOME gui functions using python plugins. - -*/ diff --git a/doc/salome/gui/SMESH/input/translation.doc b/doc/salome/gui/SMESH/input/translation.doc deleted file mode 100644 index 56c1dfb05..000000000 --- a/doc/salome/gui/SMESH/input/translation.doc +++ /dev/null @@ -1,74 +0,0 @@ -/*! - -\page translation_page Translation - -\n This geometrical operation allows to translate in space your mesh -or some of its elements. - -To translate a mesh: - -
    -
  1. From the \b Modification menu choose \b Transformation -> \b Translation item or click -"Translation" button in the toolbar. - -\image html translation.png "Translation button" - -One of the following dialogs will appear: - -It is possible to define the vector of thanslation: -\image html translation1.png "by two points" - -\image html translation2.png "by the vector from the origin of coordinates" - -
    2. - -
  2. -In the dialog: -
      -
    • specify the IDs of the translated elements: - -
        -
      • Select the whole mesh, submesh or group activating this -checkbox; or
        • -
      • choose mesh elements with the mouse in the 3D Viewer. It is -possible to select a whole area with a mouse frame; or
        • -
      • input the element IDs directly in ID Elements field. The selected elements will be highlighted in the -viewer; or
        • -
      • apply Filters. Set filter button allows to apply a filter to the selection of elements. See more -about filters in the \ref selection_filter_library_page "Selection filter library" page.
        • -
      -
      • - -
    • specify the vector of translation: -
        -
      • specify the cooordinates of the start and end \b Points of the -vector of translation; or
        • -
      • specify the end point of the \b Vector of rotation starting at the -origin of coordinates.
        • -
      -
      • - -
    • specify the conditions of translation: -
        -
      • activate Move elements radio button to create the source -mesh (or elements) at the new location and erase it from the previous location;
        • -
      • activate Copy elements radio button to create the source -mesh (or elements) at the new location, but leave it at the previous -location, the source mesh will be considered one and single mesh with the result of the rotation;
        • -
      • activate Create as new mesh radio button to leave the -source mesh (or elements) at its previous location and create a new -mesh at the new location, the new mesh appears in the Object Browser -with the default name MeshName_rotated (it is possible to change this -name in the adjacent box);
        • -
      • activate Copy groups checkbox to copy the groups of elements of the source mesh to the newly created mesh.
        • -
      -
      • - -
    • activate Preview checkbox to show the result of transformation in the viewer
      • -
    • click \b Apply or Apply and Close button to confirm the operation.
      • -
    -
- -
See Also a sample TUI Script of a \ref tui_translation "Translation" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/transparency.doc b/doc/salome/gui/SMESH/input/transparency.doc deleted file mode 100644 index 91734abf8..000000000 --- a/doc/salome/gui/SMESH/input/transparency.doc +++ /dev/null @@ -1,11 +0,0 @@ -/*! - -\page transparency_page Transparency - -\image html a-transparency.png - -Using this slider you can set the transparency of shading. Absolutely -transparent shading will be invisible. By default it is absolutely -opaque. - -*/ \ No newline at end of file diff --git a/doc/salome/gui/SMESH/input/tui_cartesian_algo.doc b/doc/salome/gui/SMESH/input/tui_cartesian_algo.doc deleted file mode 100644 index dccf68a5f..000000000 --- a/doc/salome/gui/SMESH/input/tui_cartesian_algo.doc +++ /dev/null @@ -1,6 +0,0 @@ -/*! - -\page tui_cartesian_algo Usage of Body Fitting algorithm -\tui_script{cartesian_algo.py} - -*/ diff --git a/doc/salome/gui/SMESH/input/tui_creating_meshes.doc b/doc/salome/gui/SMESH/input/tui_creating_meshes.doc deleted file mode 100644 index 53ad3f8a4..000000000 --- a/doc/salome/gui/SMESH/input/tui_creating_meshes.doc +++ /dev/null @@ -1,51 +0,0 @@ -/*! - -\page tui_creating_meshes_page Creating Meshes - -\tableofcontents - -\n First of all see \ref example_3d_mesh "Example of 3d mesh generation", - which is an example of good python script style for Mesh module. - -
-\section construction_of_a_mesh Construction of a mesh -\tui_script{creating_meshes_ex01.py} - -
-\section tui_construction_submesh Construction of a sub-mesh -\tui_script{creating_meshes_ex02.py} - -
-\section change_priority_of_submeshes_in_mesh Change priority of sub-meshes in mesh -\tui_script{creating_meshes_ex03.py} - -
-\section tui_editing_while_meshing Intermediate edition while meshing -\tui_script{a3DmeshOnModified2Dmesh.py} - -
-\section tui_editing_mesh Editing a mesh (i.e. changing hypotheses) -\tui_script{creating_meshes_ex04.py} - -
-\section tui_export_mesh Export of a Mesh -\tui_script{creating_meshes_ex05.py} - -
-\section how_to_mesh_a_cylinder_with_hexahedrons How to mesh a cylinder with hexahedrons? -Here you can see an example of python script, creating a hexahedral -mesh on a cylinder. A picture below the source code of the script -demonstrates the resulting mesh. -\tui_script{creating_meshes_ex06.py} - -\image html mesh_cylinder_hexa.png - -
-\section tui_building_compound Building a compound of meshes -\tui_script{creating_meshes_ex07.py} - -
-\section tui_copy_mesh Mesh Copying -\tui_script{creating_meshes_ex08.py} - -*/ diff --git a/doc/salome/gui/SMESH/input/tui_defining_hypotheses.doc b/doc/salome/gui/SMESH/input/tui_defining_hypotheses.doc deleted file mode 100644 index 85a3cdf92..000000000 --- a/doc/salome/gui/SMESH/input/tui_defining_hypotheses.doc +++ /dev/null @@ -1,134 +0,0 @@ -/*! - -\page tui_defining_hypotheses_page Defining Hypotheses and Algorithms - -This page provides example codes of \ref tui_defining_meshing_algos -"defining algorithms" and hypotheses. -
    -
  • Wire discretisation 1D algorithm -
      -
    • \ref tui_1d_adaptive "Adaptive 1D" hypothesis
      • -
    • \ref tui_1d_arithmetic "Arithmetic Progression" hypothesis
      • -
    • \ref tui_1d_arithmetic "Geometric Progression" hypothesis
      • -
    • \ref tui_deflection_1d "Deflection and Number of Segments" hypotheses
      • -
    • \ref tui_start_and_end_length "Start and End Length" hypotheses
      • -
    • \ref tui_average_length "Local Length"
      • -
    • \ref tui_propagation "Propagation" additional hypothesis
      • -
    • \ref tui_fixed_points "Fixed Points 1D" hypothesis
      • -
    -
    • -
  • Triangle: Mefisto 2D algorithm -
      -
    • \ref tui_max_element_area "Max Element Area" hypothesis
      • -
    • \ref tui_length_from_edges "Length from Edges" - hypothesis
      • -
    -
    • -
  • NETGEN 3D algorithm -
      -
    • \ref tui_max_element_volume "Max. Element Volume"hypothesis
      • -
    • \ref tui_viscous_layers "Viscous layers"
      • -
    -
    • -
  • \ref tui_projection "Projection Algorithms"
    • -
  • \ref tui_radial_quadrangle "Radial Quadrangle 1D-2D" algorithm
    • -
  • Quadrangle: Mapping 2D algorithm -
      -
    • \ref tui_quadrangle_parameters "Quadrangle Parameters" hypothesis
      • -
    -
    • -
  • \ref tui_import "Import 1D-2D Elements from Another Mesh" algorithm
    • -
-
- -

Defining 1D Hypotheses

- -
-\anchor tui_1d_arithmetic -

Arithmetic Progression and Geometric Progression

-\tui_script{defining_hypotheses_ex01.py} - -
-\anchor tui_1d_adaptive -

Adaptive

-\tui_script{defining_hypotheses_adaptive1d.py} - -
-\anchor tui_deflection_1d -

Deflection and Number of Segments

-\tui_script{defining_hypotheses_ex02.py} - -
-\anchor tui_start_and_end_length -

Start and End Length

-\tui_script{defining_hypotheses_ex03.py} - -
-\anchor tui_average_length -

Local Length

-\tui_script{defining_hypotheses_ex04.py} - -

Defining 2D and 3D hypotheses

- -
-\anchor tui_max_element_area -

Maximum Element Area

-\tui_script{defining_hypotheses_ex05.py} - -
-\anchor tui_max_element_volume -

Maximum Element Volume

-\tui_script{defining_hypotheses_ex06.py} - -
-\anchor tui_length_from_edges -

Length from Edges

-\tui_script{defining_hypotheses_ex07.py} - -

Defining Additional Hypotheses

- -
-\anchor tui_propagation -

Propagation

-\tui_script{defining_hypotheses_ex08.py} - -
-\anchor tui_defining_meshing_algos -

Defining Meshing Algorithms

-\tui_script{defining_hypotheses_ex09.py} - -
-\anchor tui_projection -

Projection Algorithms

-\tui_script{defining_hypotheses_ex10.py} - -

Projection 1D2D

-\tui_script{defining_hypotheses_ex11.py} - -
- -\anchor tui_fixed_points - -

1D Mesh with Fixed Points example

-\tui_script{defining_hypotheses_ex12.py} - -\anchor tui_radial_quadrangle -

Radial Quadrangle 1D-2D example

-\tui_script{defining_hypotheses_ex13.py} - -\anchor tui_quadrangle_parameters -

Quadrangle Parameters example 1 (meshing a face with 3 edges)

-\tui_script{defining_hypotheses_ex14.py} - -

Quadrangle Parameters example 2 (using different types)

-\tui_script{defining_hypotheses_ex15.py} - -\anchor tui_import -

"Import 1D-2D Elements from Another Mesh" example

-\tui_script{defining_hypotheses_ex16.py} - -\anchor tui_viscous_layers -

Viscous layers construction

-\tui_script{defining_hypotheses_ex17.py} - -*/ diff --git a/doc/salome/gui/SMESH/input/tui_filters.doc b/doc/salome/gui/SMESH/input/tui_filters.doc deleted file mode 100755 index d77c447e6..000000000 --- a/doc/salome/gui/SMESH/input/tui_filters.doc +++ /dev/null @@ -1,470 +0,0 @@ -/*! - -\page tui_filters_page Filters usage - -\tableofcontents - -Filters allow picking only the mesh elements satisfying to a -specific condition or a set of conditions. Filters can be used to create -or edit mesh groups, remove elements from the mesh, control -mesh quality by different parameters, etc. - -Several filtering criteria can be combined together by using logical -operators \a AND and \a OR. In addition, a filtering criterion can -be reverted using logical operator \a NOT. - -Mesh filters can use the functionality of mesh quality controls to filter -mesh nodes / elements by a specific characteristic (Area, Length, etc). - -This page provides a short description of the existing mesh filters, -describes required parameters and gives simple examples of usage in -Python scripts. - -\sa \ref tui_quality_controls_page - -\section filter_aspect_ratio Aspect ratio - -filters 2D mesh elements (faces) according to the aspect ratio value: -- element type should be \a SMESH.FACE -- functor type should be \a SMESH.FT_AspectRatio -- threshold is floating point value (aspect ratio) - -\tui_script{filters_ex01.py} - -\sa \ref tui_aspect_ratio - -\section filter_aspect_ratio_3d Aspect ratio 3D - -filters 3D mesh elements (volumes) according to the aspect ratio value: -- element type is \a SMESH.VOLUME -- functor type is \a SMESH.FT_AspectRatio3D -- threshold is floating point value (aspect ratio) - -\tui_script{filters_ex02.py} - -\sa \ref tui_aspect_ratio_3d - -\section filter_warping_angle Warping angle - -filters 2D mesh elements (faces) according to the warping angle value: -- element type is \a SMESH.FACE -- functor type is \a SMESH.FT_Warping -- threshold is floating point value (warping angle) - -\tui_script{filters_ex03.py} - -\sa \ref tui_warping - -\section filter_minimum_angle Minimum angle - -filters 2D mesh elements (faces) according to the minimum angle value: -- element type is \a SMESH.FACE -- functor type is \a SMESH.FT_MinimumAngle -- threshold is floating point value (minimum angle) - -\tui_script{filters_ex04.py} - -\sa \ref tui_minimum_angle - -\section filter_taper Taper - -filters 2D mesh elements (faces) according to the taper value: -- element type is \a SMESH.FACE -- functor type is \a SMESH.FT_Taper -- threshold is floating point value (taper) - -\tui_script{filters_ex05.py} - -\sa \ref tui_taper - -\section filter_skew Skew - -filters 2D mesh elements (faces) according to the skew value: -- element type is \a SMESH.FACE -- functor type is \a SMESH.FT_Skew -- threshold is floating point value (skew) - -\tui_script{filters_ex06.py} - -\sa \ref tui_skew - -\section filter_area Area - -filters 2D mesh elements (faces) according to the area value: -- element type is \a SMESH.FACE -- functor type is \a SMESH.FT_Area -- threshold is floating point value (area) - -\tui_script{filters_ex07.py} - -\sa \ref tui_area - -\section filter_volume Volume - -filters 3D mesh elements (volumes) according to the volume value: -- element type is \a SMESH.VOLUME -- functor type is \a SMESH.FT_Volume3D -- threshold is floating point value (volume) - -\tui_script{filters_ex08.py} - -\sa \ref tui_volume - -\section filter_free_borders Free borders - -filters 1D mesh elements (edges) which represent free borders of a mesh: -- element type is \a SMESH.EDGE -- functor type is \a SMESH.FT_FreeBorders -- threshold value is not required - -\tui_script{filters_ex09.py} - -\sa \ref tui_free_borders - -\section filter_free_edges Free edges - -filters 2D mesh elements (faces) having edges (i.e. links between -nodes, not mesh segments) belonging to one face of mesh only: -- element type is \a SMESH.FACE -- functor type is \a SMESH.FT_FreeEdges -- threshold value is not required - -\tui_script{filters_ex10.py} - -\sa \ref tui_free_edges - -\section filter_free_nodes Free nodes - -filters free nodes: -- element type is \a SMESH.NODE -- functor type is \a SMESH.FT_FreeNodes -- threshold value is not required - -\tui_script{filters_ex11.py} - -\sa \ref tui_free_nodes - -\section filter_free_faces Free faces - -filters free faces: -- element type is \a SMESH.FACE -- functor type is \a SMESH.FT_FreeFaces -- threshold value is not required - -\tui_script{filters_ex12.py} - -\sa \ref tui_free_faces - -\section filter_bare_border_faces Bare border faces - -filters faces with bare borders: -- element type is \a SMESH.FACE -- functor type is \a SMESH.FT_BareBorderFace -- threshold value is not required - -\tui_script{filters_ex13.py} - -\sa \ref tui_bare_border_faces - -\section filter_coplanar_faces Coplanar faces - -filters coplanar faces: -- element type is \a SMESH.FACE -- functor type is \a SMESH.FT_CoplanarFaces -- threshold value is the face ID -- tolerance is in degrees - -\tui_script{filters_ex14.py} - -\section filter_over_constrained_faces Over-constrained faces - -filters over-constrained faces: -- element type is \a SMESH.FACE -- functor type is \a SMESH.FT_OverConstrainedFace -- threshold value is not required - -\tui_script{filters_ex15.py} - -\sa \ref tui_over_constrained_faces - -\section filter_double_elements Double edges, Double faces, Double volumes - -filters mesh elements basing on the same set of nodes: -- element type is either \a SMESH.EDGE, \a SMESH.FACE or \a SMESH.VOLUME -- functor type is either \a SMESH.FT_EqualEdges, \a - SMESH.FT_EqualFaces or \a SMESH.FT_EqualVolumes, -- threshold value is not required - -\tui_script{filters_ex16.py} - - -\section tui_double_nodes_control Double nodes - -filters mesh nodes which are coincident with other nodes (within a given tolerance): -- element type is \a SMESH.NODE -- functor type is \a SMESH.FT_EqualNodes -- threshold value is not required -- default tolerance is 1.0e-7 - -\tui_script{filters_ex17.py} - - -\section filter_node_nb_conn Node connectivity number - -filters nodes according to a number of elements of highest dimension connected to a node: -- element type should be \a SMESH.NODE -- functor type should be \a SMESH.FT_NodeConnectivityNumber -- threshold is an integer value (number of elements) - -\tui_script{filters_node_nb_conn.py} - - -\section filter_borders_multiconnection Borders at multi-connection - -filters 1D mesh elements (segments) according to the specified number of -connections (faces and volumes on whose border the segment lies): -- element type is \a SMESH.EDGE -- functor type is \a SMESH.FT_MultiConnection -- threshold is integer value (number of connections) - -\tui_script{filters_ex18.py} - -\sa \ref tui_borders_at_multiconnection - -\section filter_borders_multiconnection_2d Borders at multi-connection 2D - -filters 2D mesh elements (faces) with the specified maximal number of -faces connected to a border (link between nodes, not mesh segment): -- element type is \a SMESH.FACE -- functor type is \a SMESH.FT_MultiConnection2D -- threshold is integer value (number of connections) - -\tui_script{filters_ex19.py} - -\sa \ref tui_borders_at_multiconnection_2d - -\section filter_length Length - -filters 1D mesh elements (edges) according to the edge length value: -- element type should be \a SMESH.EDGE -- functor type should be \a SMESH.FT_Length -- threshold is floating point value (length) - -\tui_script{filters_ex20.py} - -\sa \ref tui_length_1d - -\section filter_length_2d Length 2D - -filters 2D mesh elements (faces) according to the maximum length of its -edges (links between nodes): -- element type should be \a SMESH.FACE -- functor type should be \a SMESH.FT_Length2D -- threshold is floating point value (edge length) - -\tui_script{filters_ex21.py} - -\sa \ref tui_length_2d - -\section filter_max_element_length_2d Element Diameter 2D - -filters 2D mesh elements (faces) according to the maximum length -of its edges and diagonals: -- element type should be \a SMESH.FACE -- functor type should be \a SMESH.FT_MaxElementLength2D -- threshold is floating point value (length) - -\tui_script{filters_ex22.py} - -\sa \ref tui_max_element_length_2d - -\section filter_max_element_length_3d Element Diameter 3D - -filters 3D mesh elements (volumes) according to the maximum length -of its edges and diagonals: -- element type should be \a SMESH.VOLUME -- functor type should be \a SMESH.FT_MaxElementLength3D -- threshold is floating point value (edge/diagonal length) - -\tui_script{filters_ex23.py} - -\sa \ref tui_max_element_length_3d - -\section filter_bare_border_volumes Bare border volumes - -filters 3D mesh elements with bare borders, i.e. having a facet not -shared with other volumes and without a face on it: -- element type is \a SMESH.VOLUME -- functor type is \a SMESH.FT_BareBorderVolume -- threshold value is not required - -\tui_script{filters_ex24.py} - -\sa \ref tui_bare_border_volumes - -\section filter_over_constrained_volumes Over-constrained volumes - -filters over-constrained volumes, whose all nodes are on the mesh boundary: -- element type is \a SMESH.VOLUME -- functor type is \a SMESH.FT_OverConstrainedVolume -- threshold value is not required - -\tui_script{filters_ex25.py} - -\sa \ref tui_over_constrained_faces - -\section filter_belong_to_group Belong to Mesh Group - -filters mesh entities (nodes or elements) included in a mesh group -defined by threshold value: -- element type can be any, from \a SMESH.NODE to \a SMESH.BALL -- functor type should be \a SMESH.FT_BelongToMeshGroup -- threshold is mesh group object - -\tui_script{filters_belong2group.py} - -\section filter_belong_to_geom Belong to Geom - -filters mesh entities (nodes or elements) which all nodes lie on the -shape defined by threshold value: -- element type can be any, from \a SMESH.NODE to \a SMESH.BALL -- functor type should be \a SMESH.FT_BelongToGeom -- threshold is geometrical object -- tolerance is a distance between a node and the geometrical object; -it is used if an node is not associated to any geometry. - -\tui_script{filters_ex26.py} - -\section filter_lying_on_geom Lying on Geom - -filters mesh entities (nodes or elements) at least one node of which lies on the -shape defined by threshold value: -- element type can be any, from \a SMESH.NODE to \a SMESH.BALL -- functor type should be \a SMESH.FT_LyingOnGeom -- threshold is geometrical object -- tolerance is a distance between a node and the geometrical object; -it is used if an node is not associated to any geometry. - -\tui_script{filters_ex27.py} - -\section filter_belong_to_plane Belong to Plane - -filters mesh entities (nodes or elements) which all nodes belong to the -plane defined by threshold value with the given tolerance: -- element type can be any except \a SMESH.VOLUME -- functor type should be \a SMESH.FT_BelongToPlane -- threshold is geometrical object (plane) -- default tolerance is 1.0e-7 - -\tui_script{filters_ex28.py} - -\section filter_belong_to_cylinder Belong to Cylinder - -filters mesh entities (nodes or elements) which all nodes belong to the -cylindrical face defined by threshold value with the given tolerance: -- element type can be any except \a SMESH.VOLUME -- functor type should be \a SMESH.FT_BelongToCylinder -- threshold is geometrical object (cylindrical face) -- default tolerance is 1.0e-7 - -\tui_script{filters_ex29.py} - -\section filter_belong_to_surface Belong to Surface - -filters mesh entities (nodes or elements) which all nodes belong to the -arbitrary surface defined by threshold value with the given tolerance: -- element type can be any except \a SMESH.VOLUME -- functor type should be \a SMESH.FT_BelongToGenSurface -- threshold is geometrical object (arbitrary surface) -- default tolerance is 1.0e-7 - -\tui_script{filters_ex30.py} - -\section filter_range_of_ids Range of IDs - -filters mesh entities elements (nodes or elements) according to the -specified identifiers range: -- element type can be any, from \a SMESH.NODE to \a SMESH.BALL -- functor type is \a SMESH.FT_RangeOfIds -- threshold is string listing required IDs and/or ranges of IDs, e.g."1,2,3,50-60,63,67,70-78" - -\tui_script{filters_ex31.py} - -\section filter_bad_oriented_volume Badly oriented volume - -filters 3D mesh elements (volumes), which are incorrectly oriented from -the point of view of MED convention. -- element type should be \a SMESH.VOLUME -- functor type is \a SMESH.FT_BadOrientedVolume -- threshold is not required - -\tui_script{filters_ex32.py} - -\section filter_linear_or_quadratic Linear / quadratic - -filters linear / quadratic mesh elements: -- element type should be either \a SMESH.EDGE, \a SMESH.FACE or \a SMESH.VOLUME -- functor type is \a SMESH.FT_LinearOrQuadratic -- threshold is not required -- if unary operator is set to SMESH.FT_LogicalNOT, the quadratic -elements are selected, otherwise (by default) linear elements are selected - -\tui_script{filters_ex33.py} - -\section filter_group_color Group color - -filters mesh entities, belonging to the group with the color defined by the threshold value. -- element type can be any, from \a SMESH.NODE to \a SMESH.BALL -- functor type is \a SMESH.FT_GroupColor -- threshold should be of SALOMEDS.Color type - -\tui_script{filters_ex34.py} - -\section filter_geom_type Geometry type - -filters mesh elements by the geometric type defined with the threshold -value. The list of available geometric types depends on the element -entity type. -- element type can be any, e.g.: \a SMESH.EDGE, \a SMESH.FACE, \a SMESH.VOLUME, etc. -- functor type should be \a SMESH.FT_ElemGeomType -- threshold is either of smesh.GeometryType values. Type \a SMESH.GeometryType._items in the Python Console to see all geometric types. - -\tui_script{filters_ex35.py} - -\section filter_entity_type Entity type - -filters mesh elements by the geometric type and number of nodes. -- element type can be any, e.g.: \a SMESH.EDGE, \a SMESH.FACE, \a SMESH.VOLUME, etc. -- functor type should be \a SMESH.FT_EntityType -- threshold is either of SMESH.EntityType values. Type \a SMESH.EntityType._items in the Python Console to see all entity types. - -\tui_script{filters_ex37.py} - -\section filter_ball_diam Ball diameter - -filters ball elements by diameter. -- element type should be \a SMESH.BALL -- functor type should be \a SMESH.FT_BallDiameter -- threshold is floating point value (ball diameter) - -\tui_script{filters_ex38.py} - -\section filter_domain Elements of a domain - -filters elements of a specified domain. -- element type can be any, e.g.: \a SMESH.EDGE, \a SMESH.FACE, \a SMESH.VOLUME, etc. -- functor type should be \a SMESH.FT_ConnectedElements -- threshold is either (1) node ID or (2) geometrical vertex or (3) 3 coordinates of a point. - -\tui_script{filters_ex39.py} - -\section combining_filters How to combine several criteria into a filter? - -Several criteria can be combined into a filter. - -Example : - -\tui_script{filters_ex36.py} - - -*/ diff --git a/doc/salome/gui/SMESH/input/tui_generate_flat_elements.doc b/doc/salome/gui/SMESH/input/tui_generate_flat_elements.doc deleted file mode 100644 index 03f0141ed..000000000 --- a/doc/salome/gui/SMESH/input/tui_generate_flat_elements.doc +++ /dev/null @@ -1,35 +0,0 @@ -/*! - -\page tui_generate_flat_elements_page Generate flat elements - -
-\anchor tui_double_nodes_on_group_boundaries -

Double nodes on groups boundaries

- -\n Double nodes on shared faces between groups of volumes and create flat elements on demand. -\n The list of groups must contain at least two groups. The groups have to be disjoint: no common element into two different groups. -\n The nodes of the internal faces at the boundaries of the groups are doubled. Optionally, the internal faces are replaced -by flat elements. -\n Triangles are transformed into prisms, and quadrangles into hexahedrons. -\n The flat elements are stored in groups of volumes. -These groups are named according to the position of the group in the list: -the group j_n_p is the group of the flat elements that are built between the group \#n and the group \#p in the list. -If there is no shared faces between the group \#n and the group \#p in the list, the group j_n_p is not created. -All the flat elements are gathered into the group named "joints3D" (or "joints2D" in 2D situation). -The flat element of the multiple junctions between the simple junction are stored in a group named "jointsMultiples". - -\n -\n This example represents an iron cable (a thin cylinder) in a concrete bloc (a big cylinder). -The big cylinder is defined by two geometric volumes. - -\tui_script{generate_flat_elements.py} - -\n Here, the 4 groups of volumes [Solid_1_1, Solid_2_1, Solid_3_1, Solid_4_1] constitute a partition of the mesh. -The flat elements on group boundaries and on faces are built with the -2 last lines of the code above. -\n If the last argument (Boolean) in DoubleNodesOnGroupBoundaries is set to 1, -the flat elements are built, otherwise, there is only a duplication of the nodes. - -\n To observe flat element groups, save the resulting mesh on a MED file and reload it. - -*/ diff --git a/doc/salome/gui/SMESH/input/tui_grouping_elements.doc b/doc/salome/gui/SMESH/input/tui_grouping_elements.doc deleted file mode 100644 index 87a7073fb..000000000 --- a/doc/salome/gui/SMESH/input/tui_grouping_elements.doc +++ /dev/null @@ -1,55 +0,0 @@ -/*! - -\page tui_grouping_elements_page Grouping Elements - -\tableofcontents - -
-\section tui_create_standalone_group Create a Standalone Group -\tui_script{grouping_elements_ex01.py} - -\image html create_group.png - -
-\section tui_create_group_on_geometry Create a Group on Geometry -\tui_script{grouping_elements_ex02.py} - -
-\section tui_create_group_on_filter Create a Group on Filter -\tui_script{grouping_elements_ex03.py} - -
-\section tui_edit_group Edit a Group -\tui_script{grouping_elements_ex04.py} - -\image html editing_groups1.png - -
-\section tui_union_of_groups Union of groups -\tui_script{grouping_elements_ex05.py} - -\image html union_groups1.png - -
-\section tui_intersection_of_groups Intersection of groups -\tui_script{grouping_elements_ex06.py} - -\image html intersect_groups1.png - -
-\section tui_cut_of_groups Cut of groups -\tui_script{grouping_elements_ex07.py} - -\image html cut_groups1.png - -
-\section tui_create_dim_group Creating groups of entities basing on nodes of other groups -\tui_script{grouping_elements_ex08.py} - -\image html dimgroup_tui1.png - - - - - -*/ diff --git a/doc/salome/gui/SMESH/input/tui_measurements.doc b/doc/salome/gui/SMESH/input/tui_measurements.doc deleted file mode 100644 index 950cc2aba..000000000 --- a/doc/salome/gui/SMESH/input/tui_measurements.doc +++ /dev/null @@ -1,14 +0,0 @@ -/*! - -\page tui_measurements_page Measurements - -\section tui_min_distance Minimum Distance -\tui_script{measurements_ex01.py} - -\section tui_bounding_box Bounding Box -\tui_script{measurements_ex02.py} - -\section tui_bounding_box Basic Properties -\tui_script{measurements_ex03.py} - -*/ diff --git a/doc/salome/gui/SMESH/input/tui_modifying_meshes.doc b/doc/salome/gui/SMESH/input/tui_modifying_meshes.doc deleted file mode 100644 index a8ca5c941..000000000 --- a/doc/salome/gui/SMESH/input/tui_modifying_meshes.doc +++ /dev/null @@ -1,130 +0,0 @@ -/*! - -\page tui_modifying_meshes_page Modifying Meshes - -\tableofcontents - -
-\section tui_adding_nodes_and_elements Adding Nodes and Elements - -
-\anchor tui_add_node -

Add Node

-\tui_script{modifying_meshes_ex01.py} - -
-\anchor tui_add_0DElement -

Add 0D Element

-\tui_script{modifying_meshes_ex02.py} - -
-\anchor tui_add_0DElement_on_all_nodes -

Add 0D Element on Element Nodes

-\tui_script{modifying_meshes_ex03.py} - -
-\anchor tui_add_edge -

Add Edge

-\tui_script{modifying_meshes_ex04.py} - -
-\anchor tui_add_triangle -

Add Triangle

-\tui_script{modifying_meshes_ex05.py} - -
-\anchor tui_add_quadrangle -

Add Quadrangle

-\tui_script{modifying_meshes_ex06.py} - -
-\anchor tui_add_tetrahedron -

Add Tetrahedron

-\tui_script{modifying_meshes_ex07.py} - -
-\anchor tui_add_hexahedron -

Add Hexahedron

-\tui_script{modifying_meshes_ex08.py} - -
-\anchor tui_add_polygon -

Add Polygon

-\tui_script{modifying_meshes_ex09.py} - -
-\anchor tui_add_polyhedron -

Add Polyhedron

-\tui_script{modifying_meshes_ex10.py} - -
-\section tui_removing_nodes_and_elements Removing Nodes and Elements - -
-\anchor tui_removing_nodes -

Removing Nodes

-\tui_script{modifying_meshes_ex11.py} - -
-\anchor tui_removing_elements -

Removing Elements

-\tui_script{modifying_meshes_ex12.py} - -
-\anchor tui_removing_orphan_nodes -

Removing Orphan Nodes

-\tui_script{modifying_meshes_ex13.py} - -
-\section tui_moving_nodes Moving Nodes -\tui_script{modifying_meshes_ex15.py} - -
-\section tui_diagonal_inversion Diagonal Inversion -\tui_script{modifying_meshes_ex16.py} - -
-\section tui_uniting_two_triangles Uniting two Triangles -\tui_script{modifying_meshes_ex17.py} - -
-\section tui_uniting_set_of_triangles Uniting a Set of Triangles -\tui_script{modifying_meshes_ex18.py} - -
-\section tui_orientation Orientation -\tui_script{modifying_meshes_ex19.py} - -
-\section tui_cutting_quadrangles Cutting Quadrangles -\tui_script{modifying_meshes_ex20.py} - -
-\section tui_smoothing Smoothing -\tui_script{modifying_meshes_ex21.py} - -
-\section tui_extrusion Extrusion -\tui_script{modifying_meshes_ex22.py} - -
-\section tui_extrusion_along_path Extrusion along a Path -\tui_script{modifying_meshes_ex23.py} - -
-\section tui_revolution Revolution -\tui_script{modifying_meshes_ex24.py} - -
-\section tui_pattern_mapping Pattern Mapping -\tui_script{modifying_meshes_ex25.py} - -
-\section tui_quadratic Convert mesh to/from quadratic -\tui_script{modifying_meshes_ex26.py} - -
-\section tui_split_biquad Split bi-quadratic into linear -\tui_script{split_biquad.py} - -*/ diff --git a/doc/salome/gui/SMESH/input/tui_notebook_smesh.doc b/doc/salome/gui/SMESH/input/tui_notebook_smesh.doc deleted file mode 100644 index 7f34deca9..000000000 --- a/doc/salome/gui/SMESH/input/tui_notebook_smesh.doc +++ /dev/null @@ -1,8 +0,0 @@ -/*! - -\page tui_notebook_smesh_page Using SALOME NoteBook - -\anchor tui_notebook_smesh -\tui_script{notebook_smesh.py} - -*/ diff --git a/doc/salome/gui/SMESH/input/tui_prism_3d_algo.doc b/doc/salome/gui/SMESH/input/tui_prism_3d_algo.doc deleted file mode 100644 index 0bd16a9e3..000000000 --- a/doc/salome/gui/SMESH/input/tui_prism_3d_algo.doc +++ /dev/null @@ -1,9 +0,0 @@ -/*! - -\page tui_prism_3d_algo Use Extrusion 3D meshing algorithm -\tui_script{prism_3d_algo.py} - -The result geometry and mesh is shown below -\image html prism_tui_sample.png - -*/ diff --git a/doc/salome/gui/SMESH/input/tui_quality_controls.doc b/doc/salome/gui/SMESH/input/tui_quality_controls.doc deleted file mode 100644 index cb1632c1e..000000000 --- a/doc/salome/gui/SMESH/input/tui_quality_controls.doc +++ /dev/null @@ -1,76 +0,0 @@ -/*! - -\page tui_quality_controls_page Quality Controls - -\tableofcontents - -\section tui_free_borders Free Borders -\tui_script{quality_controls_ex01.py} - -\section tui_borders_at_multiconnection Borders at Multiconnection -\tui_script{quality_controls_ex02.py} - -\section tui_length_1d Length 1D -\tui_script{quality_controls_ex03.py} - -\section tui_free_edges Free Edges -\tui_script{quality_controls_ex04.py} - -\section tui_free_nodes Free Nodes -\tui_script{quality_controls_ex05.py} - -\section tui_free_faces Free Faces -\tui_script{quality_controls_ex06.py} - -\section tui_bare_border_faces Bare border faces -\tui_script{quality_controls_ex07.py} - -\section tui_bare_border_volumes Bare border volumes -\tui_script{quality_controls_ex08.py} - -\section tui_over_constrained_faces Over-constrained faces -\tui_script{quality_controls_ex09.py} - -\section tui_over_constrained_volumes Over-constrained volumes -\tui_script{quality_controls_ex10.py} - -\section tui_length_2d Length 2D -\tui_script{quality_controls_ex11.py} - -\section tui_deflection_2d Deflection 2D -\tui_script{quality_controls_defl.py} - -\section tui_borders_at_multiconnection_2d Borders at Multiconnection 2D -\tui_script{quality_controls_ex12.py} - -\section tui_area Area -\tui_script{quality_controls_ex13.py} - -\section tui_taper Taper -\tui_script{quality_controls_ex14.py} - -\section tui_aspect_ratio Aspect Ratio -\tui_script{quality_controls_ex15.py} - -\section tui_minimum_angle Minimum Angle -\tui_script{quality_controls_ex16.py} - -\section tui_warping Warping -\tui_script{quality_controls_ex17.py} - -\section tui_skew Skew -\tui_script{quality_controls_ex18.py} - -\section tui_max_element_length_2d Element Diameter 2D -\tui_script{quality_controls_ex19.py} - -\section tui_aspect_ratio_3d Aspect Ratio 3D -\tui_script{quality_controls_ex20.py} - -\section tui_volume Volume -\tui_script{quality_controls_ex21.py} - -\section tui_max_element_length_3d Element Diameter 3D -\tui_script{quality_controls_ex22.py} - -*/ diff --git a/doc/salome/gui/SMESH/input/tui_transforming_meshes.doc b/doc/salome/gui/SMESH/input/tui_transforming_meshes.doc deleted file mode 100644 index 9837176b6..000000000 --- a/doc/salome/gui/SMESH/input/tui_transforming_meshes.doc +++ /dev/null @@ -1,59 +0,0 @@ -/*! - -\page tui_transforming_meshes_page Transforming Meshes - -\tableofcontents - -
-\section tui_translation Translation -\tui_script{transforming_meshes_ex01.py} - -
-\section tui_rotation Rotation -\tui_script{transforming_meshes_ex02.py} - -
-\section tui_scale Scale -\tui_script{transforming_meshes_ex03.py} - -
-\section tui_symmetry Symmetry -\tui_script{transforming_meshes_ex04.py} - -
-\section tui_merging_nodes Merging Nodes -\tui_script{transforming_meshes_ex05.py} - -
-\section tui_merging_elements Merging Elements -\tui_script{transforming_meshes_ex06.py} - -
-\section tui_sew_meshes_border_to_side Sew Meshes Border to Side -\tui_script{transforming_meshes_ex07.py} - -
-\section tui_sew_conform_free_borders Sew Conform Free Borders -\tui_script{transforming_meshes_ex08.py} - -
-\section tui_sew_free_borders Sew Free Borders -\tui_script{transforming_meshes_ex09.py} - -
-\section tui_sew_side_elements Sew Side Elements -\tui_script{transforming_meshes_ex10.py} - -
-\section tui_duplicate_nodes Duplicate nodes or/and elements -\tui_script{transforming_meshes_ex11.py} - -
-\section tui_make_2dmesh_from_3d Create boundary elements -\tui_script{transforming_meshes_ex12.py} - -
-\section tui_reorient_faces Reorient faces -\tui_script{transforming_meshes_ex13.py} - -*/ diff --git a/doc/salome/gui/SMESH/input/tui_use_existing_faces.doc b/doc/salome/gui/SMESH/input/tui_use_existing_faces.doc deleted file mode 100644 index 03928c38b..000000000 --- a/doc/salome/gui/SMESH/input/tui_use_existing_faces.doc +++ /dev/null @@ -1,14 +0,0 @@ -/*! - -\page tui_use_existing_faces Usage of "Use Faces to be Created Manually" algorithm - -This sample demonstrates how to use Use Faces to be Created Manually algorithm, -which is actually just a stub allowing to use your own 2D algorithm -implemented in Python. - -\tui_script{use_existing_faces.py} - -Resulting mesh: -\image html use_existing_face_sample_mesh.png - -*/ diff --git a/doc/salome/gui/SMESH/input/tui_viewing_meshes.doc b/doc/salome/gui/SMESH/input/tui_viewing_meshes.doc deleted file mode 100644 index 2f3c4b404..000000000 --- a/doc/salome/gui/SMESH/input/tui_viewing_meshes.doc +++ /dev/null @@ -1,15 +0,0 @@ -/*! - -\page tui_viewing_meshes_page Viewing Meshes - -
-\anchor tui_viewing_mesh_infos -

Viewing Mesh Infos

-\tui_script{viewing_meshes_ex01.py} - -
-\anchor tui_find_element_by_point -

Find Element by Point

-\tui_script{viewing_meshes_ex02.py} - -*/ diff --git a/doc/salome/gui/SMESH/input/tui_work_on_objects_from_gui.doc b/doc/salome/gui/SMESH/input/tui_work_on_objects_from_gui.doc deleted file mode 100644 index ddd1658a7..000000000 --- a/doc/salome/gui/SMESH/input/tui_work_on_objects_from_gui.doc +++ /dev/null @@ -1,34 +0,0 @@ -/*! - -\page tui_work_on_objects_from_gui How to work with objects from the GUI ? - -It is sometimes useful to work alternatively in the GUI of SALOME and in the Python Console. To fetch an object from the TUI simply type: - -\code{.py} -myMesh_ref = salome.IDToObject( ID ) -# were ID is a string looking like "0:1:2:3" that appears in the Object Browser in the Entry column. -# ( If hidden, show it by right clicking and checking the checkbox Entry ) -myMesh = smesh.Mesh(myMesh_ref) -\endcode -or -\code{.py} -myMesh_ref = salome.myStudy.FindObjectByPath("/Mesh/myMesh").GetObject() -#'/Mesh/myMesh' is a path to the desired object in the Object Browser -myMesh = smesh.Mesh(myMesh_ref) -\endcode -or -\code{.py} -# get a selected mesh -from salome.gui import helper -myMesh_ref = helper.getSObjectSelected()[0].GetObject() -myMesh = smesh.Mesh(myMesh_ref) -\endcode - -All the methods documented in these pages can then be used on myMesh - -\note The first statement only gives you access to a reference to the object created via the GUI. -\n But the methods available on this reference are not exactly the same as those documented in these help pages. -This Python API is meant to be used on smesh.Mesh instances. -\n That's why you'll have to create such an instance with the second statement. - -*/ diff --git a/doc/salome/gui/SMESH/input/uniting_set_of_triangles.doc b/doc/salome/gui/SMESH/input/uniting_set_of_triangles.doc deleted file mode 100644 index b9704a41a..000000000 --- a/doc/salome/gui/SMESH/input/uniting_set_of_triangles.doc +++ /dev/null @@ -1,54 +0,0 @@ -/*! - -\page uniting_set_of_triangles_page Uniting a set of triangles - -\n It is possible to unite many neighboring triangles into -quadrangles by deletion of the common edge. - -To union several triangles: -
    -
  1. Select a mesh (and display it in the 3D Viewer if you are going to - pick elements by mouse).
    2. -
  2. In the \b Modification menu select the Union of triangles - item or click "Union of triangles" button in the tool-bar. - -\image html image80.png -
    "Union of triangles" button
    - -The following dialog box will appear: - -\image html a-unionoftriangles.png - -
      -
    • The main list shall contain the triangles which will be - united. You can click on a triangle in the 3D viewer and it will be - highlighted. After that click the \b Add button and the ID of this - triangle will be added to the list. To remove a selected element or - elements from the list click the \b Remove button. The \b Sort button allows - to sort the list of IDs. The Filter button allows to apply a - definite \ref filtering_elements "filter" to selection of triangles.
      • -
    • Apply to all radio button allows to apply the operation to - all triangles of the selected mesh.
      • -
    • Preview provides a preview in the viewer.
      • -
    • \b Criterion menu allows to choose a quality criterion, - which will be optimized to select triangles to unite.
      • -
    • Select from set of fields allows to choose a sub-mesh or an - existing group whose triangle elements then can be added to the - list.
      • -
    - -
    3. -
  3. Click the \b Apply or Apply and Close button to confirm the operation.
    4. -
- -If some selected triangle elements have no adjacent edges with one of -the others, the operation on these elements shall take no effect. - -\image html uniting_a_set_of_triangles1.png "The chosen triangles" - -\image html uniting_a_set_of_triangles2.png "The union of several triangles - several quadrangular cells are created" - -
See Also a sample TUI Script of a -\ref tui_uniting_set_of_triangles "Uniting a Set of Triangles" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/uniting_two_triangles.doc b/doc/salome/gui/SMESH/input/uniting_two_triangles.doc deleted file mode 100644 index f965a015f..000000000 --- a/doc/salome/gui/SMESH/input/uniting_two_triangles.doc +++ /dev/null @@ -1,35 +0,0 @@ -/*! - -\page uniting_two_triangles_page Uniting two triangles - -\n In MESH you can union two neighboring triangles by deletion -of the common edge. - -To unite two triangles: -
    -
  1. From the \b Modification menu choose the Union of two -triangles item or click "Union of two triangles" button -in the tool-bar. - -\image html image71.png -
    "Union of two triangles" button
    - -The following dialog box shall appear: - -\image html unionoftwotriangles.png - -
    2. -
  2. Enter IDs of nodes forming the required edge in the \b Edge field - (a couple of node IDs separated by a dash) or select this edge in - the 3D viewer.
    3. -
  3. Click the \b Apply or Apply and Close button.
    4. -
- -\image html uniting_two_triangles1.png "The selected triangles" - -\image html uniting_two_triangles2.png "The union of two triangles" - -
See Also a sample TUI Script of a -\ref tui_uniting_two_triangles "Uniting Two Triangles" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/use_existing_algos.doc b/doc/salome/gui/SMESH/input/use_existing_algos.doc deleted file mode 100644 index bdb4151a4..000000000 --- a/doc/salome/gui/SMESH/input/use_existing_algos.doc +++ /dev/null @@ -1,71 +0,0 @@ -/*! - -\page import_algos_page Import Elements from Another Mesh Algorithms - -\n Import Elements from Another Mesh algorithms allow to -define the mesh of a geometrical -object by importing suitably located mesh elements from another -mesh. The mesh elements to import from the other mesh should be contained in -groups. If several groups are used to mesh the same geometry, validity of -nodal connectivity of result mesh must be assured by connectivity of -the source mesh; no geometrical checks are performed to merge -different nodes at same locations. -
The source elements must totally cover the meshed geometry. -The source elements lying partially over the geometry will not be used. -
-These algorithms can be used to mesh a very complex geometry part by -part, by storing meshes of parts in files and then fusing them -together using these algorithms. -
- -Import 1D Elements from Another Mesh algorithm allows to define -the mesh of a geometrical edge (or group of edges) -by importing mesh edges contained in a group (or groups) from another mesh. -
-To apply this algorithm select the edge to be meshed (indicated in -the field \b Geometry of Create mesh dialog box), -Import 1D Elements from Another Mesh in the list of 1D -algorithms and click the "Add Hypothesis" button. -The following dialog box will appear: - -\image html hyp_source_edges.png - -In this dialog box you can define -
    -
  • The \b Name of the algorithm.
    • -
  • The Groups of Edges to import 1D elements from. -
  • To copy mesh checkbox allows to import not only the edges of -the selected Groups of Edges, but the whole source -mesh. In this case To copy groups checkbox allows to create -the same groups as in the imported source mesh.
    • -
- -Import 1D-2D Elements from Another Mesh algorithm allows to define -the mesh of a geometrical face (or group of faces) -by importing mesh faces contained in a group (or groups) from another -(or this) mesh. 1D elements on the boundary of the geometrical face -(if not yet present) are also created by the algorithm in conformity -with the created 2D elements.
-To apply this algorithm select the geometrical face to be meshed (indicated in -the field \b Geometry of Create mesh dialog box), -Import 1D-2D Elements from Another Mesh in the list of 2D -algorithms and click the "Add Hypothesis" button. -The following dialog box will appear: - -\image html hyp_source_faces.png - -In this dialog box you can define -
    -
  • The \b Name of the algorithm.
    • -
  • The Groups of Faces to import 2D elements from. -
  • To copy mesh checkbox allows to import not only the faces of -the selected Groups of Faces, but the whole source -mesh. In this case To copy groups checkbox allows to create -the same groups as in the imported source mesh.
    • -
- -
See Also a sample TUI Script of a -\ref tui_import "Import 2D Elements from Another Mesh". - -*/ - diff --git a/doc/salome/gui/SMESH/input/using_notebook_smesh_page.doc b/doc/salome/gui/SMESH/input/using_notebook_smesh_page.doc deleted file mode 100644 index aac0c9052..000000000 --- a/doc/salome/gui/SMESH/input/using_notebook_smesh_page.doc +++ /dev/null @@ -1,42 +0,0 @@ -/*! - -\page using_notebook_mesh_page Using SALOME NoteBook - -SALOME NoteBook allows defining variables to be used for -creation and modification of objects. - -\image html using_notebook_smesh.png "Setting of variables in SALOME NoteBook" - -\image html addnode_notebook.png "Use of variables to add a node in MESH module" - -The following limitations on the use of variables still exist: - -
    -
  • \ref radial_prism_algo_page "Distribution of Layers" hypothesis - - parametrical values are correctly applied, but they are not restored - after "Update study" operation. -
  • \ref a1d_meshing_hypo_page "Number of Segments" hypothesis, Distribution - with Table Density and Distribution with Analytic Density - parametrical - values are not applicable. -
  • \ref translation_page "Translation" dialog box, default mode - (translation by two points) - parametrical values are correctly applied, - but they are not restored after "Update study" operation. -
  • \ref merging_nodes_page "Merging nodes" dialog box - parametrical value - (tolerance of coincident nodes detection) is correctly applied, - but it is not restored after "Update study" operation. -
  • \ref revolution_page "Revolution" dialog box - it is impossible to - use the angle of revolution as "total angle" if it is defined as variable. -
  • \ref extrusion_along_path_page "Extrusion along a path" dialog box - it is - impossible to use "Linear variation of the angles" mode if at least one of - those angles is defined as variable. -
  • \ref pattern_mapping_page "Pattern mapping" dialog box - parametrical - values (indices of nodes) are correctly applied, but they are not restored - after "Update study" operation. -
  • \ref clipping_page "Clipping" dialog box. -
  • Properties dialog box. -
- -Our TUI Scripts provide you with useful examples of -\ref tui_notebook_smesh "Using SALOME NoteBook". - -*/ diff --git a/doc/salome/gui/SMESH/input/using_operations_on_groups.doc b/doc/salome/gui/SMESH/input/using_operations_on_groups.doc deleted file mode 100644 index a380581ab..000000000 --- a/doc/salome/gui/SMESH/input/using_operations_on_groups.doc +++ /dev/null @@ -1,123 +0,0 @@ -/*! - -\page using_operations_on_groups_page Boolean operations on groups - -\n In MESH you can perform some Boolean operations on groups, which -belong to one and the same mesh. -
    -
  • \ref union_anchor "Union"
    • -
  • \ref intersection_anchor "Intersection"
    • -
  • \ref cut_anchor "Cut"
    • -
- - -
-\anchor union_anchor -

Union of groups

- -This operation allows to create a new group in such a way that all -mesh elements that are present in the initial groups will be added to -the new one. - -To union groups: -
    -
  1. In the \b Mesh menu select the Union Groups item. The following -dialog box will appear: - -\image html uniongroups.png - -In this dialog box you should specify the name of the resulting group -and set of groups which will be united. - -For example, we have two groups Group1 and Group2. -\n The result of their \b Union will be Group12: - -\image html image133.gif -
    Group1
    - -\image html image134.gif -
    Group2
    - -\image html image135.gif -
    Group12
    -
    2. -
  2. Click the \b Apply or Apply and Close button to confirm creation of the group.
    3. -
- -See Also a sample TUI Script of a -\ref tui_union_of_groups "Union of Groups" operation. - -
-\anchor intersection_anchor -

Intersection of groups

- -This operation allows to create a new group in such a way that all -mesh elements that are present in all initial groups together are added to the -new one. - -To intersect groups: -
    -
  1. In the \b Mesh menu select the Intersect Groups item. The -following dialog box will appear: - -\image html intersectgroups.png - -In this dialog box you should specify the name of the resulting group -and set of groups which will be intersected. - -For example, we have two groups Group1 and Group2. -\n The result of their \b Intersection will be Group12a: - -\image html image133.gif -
    Group1
    - -\image html image134.gif -
    Group2
    - -\image html image136.gif -
    Group12a
    -
    2. -
  2. Click the \b Apply or Apply and Close button to confirm creation of the group.
    3. -
- -See Also a sample TUI Script of an -\ref tui_intersection_of_groups "Intersection of Groups" operation. - -
-\anchor cut_anchor -

Cut of groups

- -This operation allows to create a new group in such a way that all -mesh elements that are present in the main groups but are absent in the -tool groups are added to the new one. - -To cut groups: -
    -
  1. In the \b Mesh menu select the Cut Groups item. The -following dialog box will appear: - -\image html cutgroups.png - -In this dialog box you should specify the name of the resulting group -and groups which will be cut. - -For example, we have two groups Group1 and Group2. -\n The result of their \b Cut will be Group12b: - -\image html image133.gif -
    Group1
    - -\image html image134.gif -
    Group2
    - -\image html image137.gif -
    Group12b
    -
    2. -
  2. Click the \b Apply or Apply and Close button to confirm creation of the -group.
    3. -
- -See Also a sample TUI Script of a -\ref tui_cut_of_groups "Cut of Groups" operation. - -*/ diff --git a/doc/salome/gui/SMESH/input/viewing_meshes_overview.doc b/doc/salome/gui/SMESH/input/viewing_meshes_overview.doc deleted file mode 100644 index c4831c064..000000000 --- a/doc/salome/gui/SMESH/input/viewing_meshes_overview.doc +++ /dev/null @@ -1,82 +0,0 @@ -/*! - -\page viewing_meshes_overview_page Viewing meshes - -By default a just \ref compute_anchor "computed" mesh will be -automatically displayed in the VTK 3D Viewer. (You can switch -off \ref automatic_update_pref "Automatic Update" preference parameter -to prevent this.) -Click Display only to hide all other objects at the same time. - -VTK 3D Viewer is described in detail in the documentation on GUI module. - -Use the following \ref mesh_preferences_page "preference parameters" -to adjust how the mesh is displayed by default: -- \ref automatic_update_pref "Automatic Update" -- \ref display_mode_pref "Default display mode" -- \ref quadratic_2d_mode_pref "Representation of the 2D quadratic elements" -- All parameters of \ref mesh_tab_preferences "Mesh" tab page of the -Preferences dialog. - -After the mesh has appeared in the Viewer, you can select it with -left mouse click and get information about it, change its -presentation parameters and access to other useful options by -right-clicking on the selected mesh. - -\image html dialog.png - -
    -
  • Rename - allows to rename the object in the Object browser.
    • -
  • Hide all - allows to hide all objects in the viewer.
    • -
  • Update - refreshes the presentation of your mesh in the - Object Browser, applying all recent changes.
    • -
  • \subpage mesh_infos_page "Mesh Information" - provides - information about the mesh.
    • -
  • \subpage find_element_by_point_page "Find Element by Point" - - allows to find all mesh elements, to which belongs a point with the -given coordinates.
    • -
  • Auto Color - switch on / off auto-assigning colors for the - groups. If switched on, a default color of a new group in - \ref creating_groups_page "Create Group" dialog is chosen - randomly.
    • -
  • \subpage numbering_page "Numbering" - allows to display the ID - numbers of all meshing elements or nodes composing your mesh in the - viewer.
    • -
  • \subpage display_mode_page "Display Mode" - allows to select between - Wireframe, Shading and Nodes presentation.
    • -
  • \subpage display_entity_page "Display Entity" - allows to display - entities by types (Faces, Edges, Volumes etc.).
    • -\anchor quadratic_2d_mode -
  • 2D Quadratic - allows to select between the representation - of quadratic edges as broken \b lines or as \b arcs. A default - representation can be set in \ref quadratic_2d_mode_pref "Preferences". - Arc representation applies to 1D and 2D elements only. -
    • -
  • Orientation of faces - shows vectors of orientation of - faces of the selected mesh. The orientation vector is shown for each - 2D mesh element and for each free facet of a 3D mesh element. The - vector direction is calculated by the first three nodes of the face - produced by vectors n1-n2 and n1-n3.
    • -
  • \subpage colors_size_page "Properties" - allows to define several - visual properties, including color of elements, shrink size, ...
    • -
  • \subpage transparency_page "Transparency" - allows to change the - transparency of mesh elements.
    • -
  • \ref quality_page "Controls" - graphically presents various - information about the mesh.
    • -
  • Hide - allows to hide the selected mesh from the viewer.
    • -
  • Show Only - allows to display only the selected mesh, - hiding all others from the viewer.
    • -
  • \subpage clipping_page "Clipping" - allows to create - cross-sections of the displayed objects.
    • -
  • Dump view - exports an object from the viewer in bmp, png - or jpeg image format.
    • -
  • Change background - allows to redefine the background - color. By default it is black.
    • -
  • View Operations - allows to show/hide the - visualization toolbar in the Viewer window.
    • -
  • Recording Operations - allows to show/hide the recording - toolbar in the Viewer window.
    • -
- -*/ - diff --git a/doc/salome/gui/SMESH/input/volume.doc b/doc/salome/gui/SMESH/input/volume.doc deleted file mode 100644 index 4d74fcbf0..000000000 --- a/doc/salome/gui/SMESH/input/volume.doc +++ /dev/null @@ -1,28 +0,0 @@ -/*! - -\page volume_page Volume - -\n \b Volume mesh quality criterion reflects the volume of meshes of a -3D object. - -To apply the Volume quality criterion to your mesh: -
    -
  1. Display your mesh in the viewer.
    2. - -
  2. Choose Controls > Volume Controls > Volume or click -"Volume" button in the toolbar. - -\image html image145.png -
    "Volume" button
    - -Your mesh will be displayed in the viewer with its elements colored -according to the applied mesh quality control criterion: - -\image html image143.gif -
    3. -
- -
See Also a sample TUI Script of a -\ref tui_volume "Volume quality control" operation. - -*/ \ No newline at end of file diff --git a/doc/salome/gui/SMESH/input/warping.doc b/doc/salome/gui/SMESH/input/warping.doc deleted file mode 100644 index 86ba0c905..000000000 --- a/doc/salome/gui/SMESH/input/warping.doc +++ /dev/null @@ -1,43 +0,0 @@ -/*! - -\page warping_page Warping - -\image html image24.gif - -\n \b Warping indicates that a face is not planar and is applied only to -2D elements with 4 nodes. This quality control criterion is based on a -projection plane created by: -
    -
  1. bisecting the four element edges,
    2. -
  2. creating a point on the plane at the vector average of the -corners, where the x-axis extends from the point to the bisector on -edge 2.
    3. -
-The plane normal is in the direction of the cross product of the -x-axis and the vector from the origin to the bisector of edge 3. Every -corner of the quad will then be a distance ?h? from the plane. The -length of each half edge is measured and the shortest length is -assigned ?l?. The warp angle is the arcsine of the ratio of the -projection height ?h? to the half edge length ?l?. - -To apply the Warping quality criterion to your mesh: -
    -
  1. Display your mesh in the viewer.
    2. - -
  2. Choose Controls > Face Controls > Warping Angle or click -"Warping angle" button of the toolbar. - -\image html image39.png -
    "Warping angle" button
    - -Your mesh will be displayed in the viewer with its elements colored -according to the applied mesh quality control criterion: - -\image html image97.jpg -
    3. -
- -
See Also a sample TUI Script of a -\ref tui_warping "Warping quality control" operation. - -*/ diff --git a/doc/salome/gui/SMESH/static/footer.html b/doc/salome/gui/SMESH/static/footer.html deleted file mode 100755 index 7cf11feba..000000000 --- a/doc/salome/gui/SMESH/static/footer.html +++ /dev/null @@ -1,14 +0,0 @@ - - - - - - diff --git a/doc/salome/gui/SMESH/static/header.html.in b/doc/salome/gui/SMESH/static/header.html.in deleted file mode 100755 index 45674df6f..000000000 --- a/doc/salome/gui/SMESH/static/header.html.in +++ /dev/null @@ -1,23 +0,0 @@ - - - - - - - -$projectname: $title -$title - - - -$treeview -$search -$mathjax - -$extrastylesheet - - -
- -
Version: @SALOMESMESH_VERSION@
- diff --git a/doc/salome/gui/SMESH/static/header_py.html.in b/doc/salome/gui/SMESH/static/header_py.html.in deleted file mode 100644 index e937979f6..000000000 --- a/doc/salome/gui/SMESH/static/header_py.html.in +++ /dev/null @@ -1,24 +0,0 @@ - - - - - - - -$projectname: $title -$title - - - -$treeview -$search -$mathjax - -$extrastylesheet - - -
- -
Version: @SALOMESMESH_VERSION@
- - diff --git a/doc/salome/gui/SMESH/static/salome_extra.css b/doc/salome/gui/SMESH/static/salome_extra.css deleted file mode 100644 index 3e8b838a6..000000000 --- a/doc/salome/gui/SMESH/static/salome_extra.css +++ /dev/null @@ -1,29 +0,0 @@ -/* The extra CSS for doxygen 1.8.3.1 */ - -#titlearea { - background-image:url('head.png'); - background-color: #175783; - border: 1px solid; - height: 80px; - background-repeat: no-repeat; - padding: 0px; - margin: 0px; - width: 99.9%; - border-bottom: 1px solid #5373B4; -} - -div.version { - border:1px solid #0000FF; - color: #CCCCCC; - font-family: Arial, Helvetica, sans-serif; - font-size: 9pt; - text-align: center; - width:100px; - -moz-border-radius: 8px; - margin: 5px; -} - -.navpath li.footer { - line-height:15px; - text-align: right; -} \ No newline at end of file diff --git a/doc/salome/gui/SMESH/static/switchers.js b/doc/salome/gui/SMESH/static/switchers.js index d6fcd5534..a84e66536 100644 --- a/doc/salome/gui/SMESH/static/switchers.js +++ b/doc/salome/gui/SMESH/static/switchers.js @@ -25,7 +25,7 @@ function on_language_switch() { var selected_language = $(this).children('option:selected').attr('value') + '/'; var url = window.location.href; - + var current_language = language_segment_from_url(url); var current_suffix = ""; if (current_language != "") { @@ -33,17 +33,17 @@ } else { current_language = "/"; } - + var selected_suffix = "_"; if (selected_language == 'en/') { // Special 'default' case for english. selected_language = ''; selected_suffix = "/"; } - + var new_url = url.replace('/gui/SMESH' + current_suffix + current_language, '/gui/SMESH' + selected_suffix + selected_language); if (new_url != url) { - window.open(new_url); + window.location.href = new_url; } } diff --git a/resources/SalomeApp.xml.in b/resources/SalomeApp.xml.in index 1a507d04d..9c1b51daf 100644 --- a/resources/SalomeApp.xml.in +++ b/resources/SalomeApp.xml.in @@ -118,7 +118,7 @@
- + diff --git a/src/SMESH_SWIG/smeshBuilder.py b/src/SMESH_SWIG/smeshBuilder.py index 78f85f93c..febf232fe 100644 --- a/src/SMESH_SWIG/smeshBuilder.py +++ b/src/SMESH_SWIG/smeshBuilder.py @@ -1355,14 +1355,15 @@ class smeshBuilder(object, SMESH._objref_SMESH_Gen): return value def GetGravityCenter(self, obj): - """ - Get gravity center of all nodes of the mesh object. + """ + Get gravity center of all nodes of the mesh object. - Parameters: - obj: mesh, submesh or group - Returns: - Three components of the gravity center: x,y,z - """ + Parameters: + obj: mesh, submesh or group + + Returns: + Three components of the gravity center: x,y,z + """ if isinstance(obj, Mesh): obj = obj.mesh if isinstance(obj, Mesh_Algorithm): obj = obj.GetSubMesh() aMeasurements = self.CreateMeasurements() -- 2.39.2