LIST(APPEND CMAKE_MODULE_PATH "${KERNEL_ROOT_DIR}/salome_adm/cmake_files")
INCLUDE(SalomeMacros)
FIND_PACKAGE(SalomeKERNEL REQUIRED)
- KERNEL_WITH_CORBA() # check whether KERNEL builded with CORBA
+ KERNEL_WITH_CORBA() # check whether KERNEL built with CORBA
ELSE(EXISTS ${KERNEL_ROOT_DIR})
MESSAGE(FATAL_ERROR "We absolutely need a Salome KERNEL, please define KERNEL_ROOT_DIR")
ENDIF(EXISTS ${KERNEL_ROOT_DIR})
IF(EXISTS ${GUI_ROOT_DIR})
LIST(APPEND CMAKE_MODULE_PATH "${GUI_ROOT_DIR}/adm_local/cmake_files")
FIND_PACKAGE(SalomeGUI)
- SALOME_GUI_WITH_CORBA() # check whether GUI builded with CORBA
+ SALOME_GUI_WITH_CORBA() # check whether GUI built with CORBA
ADD_DEFINITIONS(${GUI_DEFINITIONS})
INCLUDE_DIRECTORIES(${GUI_INCLUDE_DIRS})
ELSE(EXISTS ${GUI_ROOT_DIR})
About SALOME GMSH plug-in
*************************
-\b GMSHPLUGIN plugin provides an integration of certain functionnalities of the
+\b GMSHPLUGIN plugin provides an integration of certain functionalities of the
well known <a href="http://www.geuz.org/gmsh/"><b>Gmsh three-dimensional finite
element mesh generator</b></a>.
-It is capable to to mesh 2D and 3D geometric entities. The plugin was especialy
-developped to integrate the Gmsh compound functionnality.
+It is capable of meshing 2D and 3D geometric entities. The plugin was especially
+developed to integrate the Gmsh compound functionality.
For more information please visit the SALOME platform web site:
Pre-requisites
--------------
-SALOME platform relies on a set of third-party softwares; some of them are needed
-at build time only, while other ones are needed in runtime also.
+SALOME platform relies on a set of third-party software; some of them are needed
+at build time only, while other ones are needed at runtime as well.
For more information about the pre-requisites please visit SALOME platform web
site:
------------------
The build procedure of the SALOME platform is implemented with CMake.
-In order to build the plug-in you have to do the following actions:
+In order to build the plug-in you have to do the following actions:
1. Set up environment for pre-requisites (see "Pre-requisites" section above).
where
- <mode> is either Release or Debug (default: Release);
- <installation_directory> is a destination folder to install SALOME GMSH
- plug-in (default: /usr);
+ plug-in (default: /usr);
- <path_to_src_dir> is a path to the SALOME GMSH plug-in sources directory.
Note: by default (if CMAKE_INSTALL_PREFIX option is not given), SALOME GMSH
# - Config file for the @PROJECT_NAME@ package
# It defines the following variables.
-# Specific to the pacakge @PROJECT_NAME@ itself:
+# Specific to the package @PROJECT_NAME@ itself:
# @PROJECT_NAME_UC@_ROOT_DIR_EXP - the root path of the installation providing this CMake file
#
The <b>Arguments tab</b> of the dialog boxes is very similar to the original <a href="http://www.geuz.org/gmsh/"> <b> Gmsh </b></a>
GUI general mesh option tab.
One familiar with the original interface can refer to the <a href="http://www.geuz.org/gmsh/doc/texinfo/gmsh.html">
-<b> Gmsh documentation </b></a> for more informations.
+<b> Gmsh documentation </b></a> for more information.
We briefly describe each argument of the <b>Arguments tab</b> and give the original corresponding Gmsh keyword
-(refering to <a href="http://www.geuz.org/gmsh/doc/texinfo/gmsh.html#Mesh-options-list"> <b> Gmsh Mesh options list</b></a>):
+(refer
ring to <a href="http://www.geuz.org/gmsh/doc/texinfo/gmsh.html#Mesh-options-list"> <b> Gmsh Mesh options list</b></a>):
- <b>Name</b> - allows to define the name for the algorithm ("Gmsh Parameters" by default).
- <b>2D algorithm</b> - allows to choose the Gmsh 2D algorithm for both 2D and 3D meshes.
Original corresponding Gmsh keyword is <b>"Mesh.Algorithm"</b>.
which actually will become quadratic.
Original corresponding Gmsh keyword is <b>"Mesh.ElementOrder"</b> (set to 2 if the box is checked in, else 1).
- <b>Use incomplete elements</b> - if this box is checked in (default), quadratic elements will be incomplete.
-For example a quadrangle will have 8 nodes if incomplete, 9 nodes if complete. See
-<a href="http://www.geuz.org/gmsh/doc/texinfo/gmsh.html#Node-ordering"> <b> Node ordering </b></a> for more informations.
-Be carefull with the case of pyramides. Complete pyramides will have 14 nodes but there is no pyra14 available in smesh.
+For example a quadrangle will have 8 nodes if incomplete, 9 nodes if complete. See
+<a href="http://www.geuz.org/gmsh/doc/texinfo/gmsh.html#Node-ordering"> <b> Node ordering </b></a> for more information.
+Be careful with the case of pyramids. Complete pyramids will have 14 nodes but there is no pyra14 available in smesh.
The last node created by Gmsh will then be ignored and using complete element can lead to orphelin nodes.
Original corresponding Gmsh keyword is <b>"Mesh.SecondOrderIncomplete"</b> (set to 1 if the box is checked in, else 0).
<br>
-\image html Compounds.png Coumpounds tab of the dialog boxe.
+\image html Compounds.png Compounds tab of the dialog boxes.
In the Compounds tab of the dialog boxes, it is possible to choose the following arguments:
- <b>Add</b> - allows to add geometrical defined groups of edges or groups of faces as compounds.
- <b>Remove</b> - deletes selected rows from the table.
*/
-
-
\mainpage Introduction to GMSHPLUGIN
-\b GMSHPLUGIN plugin provide an integration of certain functionnalities of the well known
+\b GMSHPLUGIN plugin provides an integration of certain functionalities of the well known
<a href="http://www.geuz.org/gmsh/"> <b>Gmsh three-dimensional finite element mesh generator</b></a>.
-It is possible to mesh 2D and 3D geometric entities. The plugin was especialy developped to
-integrate the Gmsh coumpound functionnality.
+It is possible to mesh 2D and 3D geometric entities. The plugin was especially developed to
+integrate the Gmsh compound functionality.
To manage parameters of the GMSHPLUGIN use \subpage gmsh_2d_3d_hypo_page.
e->getVertices(verts);
ASSERT(verts.size()==1);
//SMDS_Mesh0DElement* zeroDElement = 0;
- // WE DONT ADD 0D ELEMENTS because it does not follow the salome meshers philosophy
+ // WE DON'T ADD 0D ELEMENTS because it does not follow the salome meshers philosophy
//zeroDElement = meshDS->Add0DElementWithID(verts[0]->getNum(),e->getNum());
//meshDS->SetMeshElementOnShape(zeroDElement, topoVertex);
}
