The default option, 'conformal', implies that the meshes produced by HOMARD will be conformal, as expected in the finite element method. This is a classical choice for most of the simulation software with the finite element method.
-Nevertheless, if the computation is available with non conformal meshes, 3 possibilities are available:
-
+The treatment of non conformal meshes is possible.
.. image:: images/create_case_4.png
:align: center
-* 1 node per element: an element must not have more than one hanging node with its neighbours.
-* 1 node per edge: every single edge of an element ban be split once while its neighbour is not.
-* free: no limit for the number of hanging node.
+Some extra options can be given by the advanced options.
.. index:: single: boundary
Two situations:
-* 1D curve: this curve may be defined into a plane, for example for a 2D calculation. It can also be defined into the 3D space, for example to describe the intersection of two surfaces. Such a line is defined with a discrete desription.
-* a surface: such a surface is defined with an analytical description.
+- CAO: the CAO of the domain is available. The computtion will rely on it to project the nodes.
+- No CAO: if no CAO is available, an approximative approach is possible:
+
+ * 1D curve: this curve may be defined into a plane, for example for a 2D calculation. It can also be defined into the 3D space, for example to describe the intersection of two surfaces. Such a line is defined with a discrete desription.
+ * a surface: such a surface is defined with an analytical description.
Check the button:
-.. image:: images/create_case_5.png
+.. image:: images/create_boundary_1.png
:align: center
-The definition of the boundaries is described in :ref:`gui_create_boundary`.
+The definition of the boundaries is described in :doc:`gui_create_boundary`.
.. index:: single: pyramid
Advanced options
****************
-Default: no advanced option.
+Default: no advanced option. Nevertheless, some advanced options can be defined :
+
+The pyramids
+============
-Nevertheless, some advanced options can be defined :
+The first option is about the pyramids.
.. image:: images/create_case_7.png
:align: center
- segment
- triangle
- quadrangle
- - tetraedron
- - hexaedron
+ - tetrahedron
+ - hexahedron
- prism
If pyramids are present into the initial mesh, HOMARD stops with an error. However, if no refinement will be in contact with any edge of those pyramids, the "Authorized pyramids" whould be checked. The adaptation will go on and the pyramids will be back as they are into the initial mesh.
+Nevertheless, if the computation is available with non conformal meshes, 3 possibilities are available:
+
+Which conformity?
+=================
+
+With a conformal refinement, the choice is given between the standard conformal refinement, default option, and a refinement into boxes, e.g. without any staircases.
+
+.. image:: images/create_case_8.png
+ :align: center
+
+Which non conformity?
+=====================
+
+With a non conformal refinement, 4 choices are available:
+
+* standard non conformal refinement, default option
+* refinement into boxes, e.g. without any staircases
+* 1 node per edge: every single edge of an element ban be split once while its neighbour is not.
+* free: no limit for the number of hanging node.
+
+.. image:: images/create_case_9.png
+ :align: center
+
+The external format
+===================
+.. index:: single: MED
+.. index:: single: Saturne
+
+By default, the external format is MED. When coupled with Saturne 2D, it is necessary to precise it to correctly deal with the pseudo 2D situation.
+
+.. image:: ../images/create_case_1.png
+ :align: center
The pursuit of a case
*********************
.. index:: single: pursuit
-.. index:: single: yacs
+.. index:: single: YACS
The pursuit of a case is interesting in the following situation. A list of adaptations was done for a case and, at the end, SALOME is closed. The directories for these iterations are kept. Then, the user wants to go on these iterations from the final point of the previous list. This function is useful with a schema YACS if a long list of adaptations is cut into small parts.
Corresponding python functions
******************************
-Look :ref:`tui_create_case`
+Look :doc:`tui_create_case`
