From 49b6af44ca356a3a9abf5db67ac315410ee0b3e4 Mon Sep 17 00:00:00 2001 From: =?utf8?q?G=C3=A9rald=20NICOLAS?= Date: Tue, 15 Dec 2015 15:24:24 +0100 Subject: [PATCH] =?utf8?q?Documentation=20des=20options=20avanc=C3=A9es=20?= =?utf8?q?en=20GUI?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit --- doc/en/gui_create_case.rst | 50 ++++++++++++++++++++++++++++------ doc/en/intro.rst | 12 ++++---- doc/fr/gui_create_case.rst | 42 ++++++++++++++++++++++++---- src/HOMARDGUI/CreateCase.h | 4 +-- src/HOMARDGUI/CreateCase.ui | 2 +- src/HOMARDGUI/HOMARD_msg_fr.ts | 4 +++ src/HOMARDGUI/HOMARD_msg_ja.ts | 4 +++ 7 files changed, 94 insertions(+), 24 deletions(-) diff --git a/doc/en/gui_create_case.rst b/doc/en/gui_create_case.rst index 4dbd1ea5..43c6fa36 100644 --- a/doc/en/gui_create_case.rst +++ b/doc/en/gui_create_case.rst @@ -53,15 +53,12 @@ The future iterations for this case must respect the the same behaviour regardin 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 @@ -85,9 +82,12 @@ The definition of the boundaries is described in :doc:`gui_create_boundary`. 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 @@ -97,11 +97,43 @@ HOMARD is able to work with 2D or 3D meshes as well, including the following ele - 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 ********************* diff --git a/doc/en/intro.rst b/doc/en/intro.rst index 260e7928..9d2a8fd3 100644 --- a/doc/en/intro.rst +++ b/doc/en/intro.rst @@ -121,7 +121,7 @@ This, in turn, creates 4 new tetrahedrons. It should be noted that they are simi :width: 229 :height: 116 -Hexaedrons are split in eight. Each of the quadrangular faces is split into 4 quadrangular faces. Edges are created connecting each centre of opposite faces. This generates a new point located at the centre of the hexaedron. +Hexaedrons are split in eight. Each of the quadrangular faces is split into 4 quadrangular faces. Edges are created connecting each centre of opposite faces. This generates a new point located at the centre of the hexahedron. .. image:: ../images/dec_hex.png :align: center @@ -192,9 +192,9 @@ For a tetrahedron with one split edge, the middle of the split edge is joined to :width: 116 :height: 116 -The conformal strategy for the hexaedrons is based on tetraedrons and pyramids. The situation depends on the number of non conformities, following the rules for the quadrangles. Here is some examples from the 66 possible situations. +The conformal strategy for the hexahedrons is based on tetrahedrons and pyramids. The situation depends on the number of non conformities, following the rules for the quadrangles. Here is some examples from the 66 possible situations. -For an hexaedron with one face cut, we create 4 edges, 4 tetraedrons and 5 pyramids. +For an hexahedron with one face cut, we create 4 edges, 4 tetrahedrons and 5 pyramids. .. image:: ../images/hexaface.png :align: center @@ -202,7 +202,7 @@ For an hexaedron with one face cut, we create 4 edges, 4 tetraedrons and 5 pyram :width: 384 :height: 101 -For an hexaedron with only one edge cut, we create deux internal edges and four pyramids. +For an hexahedron with only one edge cut, we create deux internal edges and four pyramids. .. image:: ../images/hexa1arete.png :align: center @@ -210,7 +210,7 @@ For an hexaedron with only one edge cut, we create deux internal edges and four :width: 384 :height: 101 -For an hexaedron with two edges cut, we create one central point 10 edges, 12 tetraedrons and 2 pyramids. +For an hexahedron with two edges cut, we create one central point 10 edges, 12 tetrahedrons and 2 pyramids. .. image:: ../images/hexa2aretes.png :align: center @@ -218,7 +218,7 @@ For an hexaedron with two edges cut, we create one central point 10 edges, 12 te :width: 384 :height: 101 -For an hexaedron with three edges cut, we create one central point, 11 edges and 18 tetraedrons. +For an hexahedron with three edges cut, we create one central point, 11 edges and 18 tetrahedrons. .. image:: ../images/hexa3aretes.png :align: center diff --git a/doc/fr/gui_create_case.rst b/doc/fr/gui_create_case.rst index d8c3c7d1..0e41fc22 100644 --- a/doc/fr/gui_create_case.rst +++ b/doc/fr/gui_create_case.rst @@ -51,14 +51,12 @@ Les itérations qui seront calculées pour ce cas devront toutes respecter le m L'option par défaut, 'conforme', implique que les maillages produits par HOMARD seront conformes au sens des éléments finis. C'est le choix classique de la plupart des logiciels de simulation par éléments finis. -Néanmoins, si le calcul est possible avec des maillages non conformes, on a le choix entre 3 possibilités : +Il est possible également de traiter des maillages non conformes. .. image:: images/create_case_4.png :align: center -* 1 noeud par maille : une maille ne peut posséder qu'un seul noeud de non conformité avec ses voisines. -* 1 noeud par arête : chaque arête d'une maille peut être découpée sans que la maille voisine par cette arête ne le soit. -* quelconque : aucune limitation sur les raccords de conformité d'une maille à l'autre. +Des variantes peuvent être obtenues avec les options avancées. .. index:: single: frontière @@ -84,9 +82,12 @@ La définition des frontières est décrite dans :doc:`gui_create_boundary`. Les options avancées ******************** -Par défaut, aucune option avancée n'est active. +Par défaut, aucune option avancée n'est active. Néanmoins, on peut définir quelques options avancées. + +Les pyramides +============= -Néanmoins, on peut définir une option avancée : +La première concerne la gestion des mailles pyramidales. .. image:: images/create_case_7.png :align: center @@ -102,6 +103,35 @@ Par défaut, HOMARD sait traiter des maillages en 2 ou 3 dimensions et comportan Si le maillage initial comporte des pyramides, il y a arrêt en erreur. Toutefois, si on est certain que les raffinements ultérieurs ne toucheront aucune des arêtes des pyramides, on cochera la case "Pyramides autorisées". Les adaptations se dérouleront normalement et les pyramides seront restituées telles quelles dans le maillage final. +Quelle conformité ? +=================== + +Pour un raffinement conforme, on a le choix entre le raffinement conforme standard, option par défaut, ou un raffinement par boîte, c'est-à-dire interdisant le raffinement en escalier. + +.. image:: images/create_case_8.png + :align: center + +Quelle non-conformité ? +======================= + +Pour un raffinement non conforme, on a le choix entre 4 possibilités : +* raffinement conforme standard, option par défaut +* raffinement par boîte, c'est-à-dire interdisant le raffinement en escalier +* 1 noeud par arête : chaque arête d'une maille peut être découpée sans que la maille voisine par cette arête ne le soit. +* quelconque : aucune limitation sur les raccords de conformité d'une maille à l'autre. + +.. image:: images/create_case_9.png + :align: center + +Le format externe +================= +.. index:: single: MED +.. index:: single: Saturne + +Par défaut le format des mailles externes est le format MED. Dans le cas d'un calcul Saturne 2D, on doit le préciser ici pour gérer correctement le caractère pseudo-2D du maillage. + +.. image:: ../images/create_case_1.png + :align: center La poursuite d'un cas ********************* diff --git a/src/HOMARDGUI/CreateCase.h b/src/HOMARDGUI/CreateCase.h index c2483658..adc14078 100644 --- a/src/HOMARDGUI/CreateCase.h +++ b/src/HOMARDGUI/CreateCase.h @@ -1,7 +1,7 @@ /******************************************************************************** ** Form generated from reading UI file 'CreateCase.ui' ** -** Created: Mon Dec 14 17:01:30 2015 +** Created: Tue Dec 15 14:39:25 2015 ** by: Qt User Interface Compiler version 4.6.3 ** ** WARNING! All changes made in this file will be lost when recompiling UI file! @@ -521,7 +521,7 @@ public: CBAdvanced->setText(QApplication::translate("CreateCase", "Advanced options", 0, QApplication::UnicodeUTF8)); GBAdvancedOptions->setTitle(QApplication::translate("CreateCase", "Advanced options", 0, QApplication::UnicodeUTF8)); CBPyramid->setText(QApplication::translate("CreateCase", "Authorized pyramids", 0, QApplication::UnicodeUTF8)); - GBConforme->setTitle(QApplication::translate("CreateCase", "Conformit\303\251", 0, QApplication::UnicodeUTF8)); + GBConforme->setTitle(QApplication::translate("CreateCase", "Conformity +", 0, QApplication::UnicodeUTF8)); RBStandard->setText(QApplication::translate("CreateCase", "Standard", 0, QApplication::UnicodeUTF8)); RBBox->setText(QApplication::translate("CreateCase", "Box", 0, QApplication::UnicodeUTF8)); RBNC1NpA->setText(QApplication::translate("CreateCase", "1 node per edge", 0, QApplication::UnicodeUTF8)); diff --git a/src/HOMARDGUI/CreateCase.ui b/src/HOMARDGUI/CreateCase.ui index 75419364..7db2cd1a 100644 --- a/src/HOMARDGUI/CreateCase.ui +++ b/src/HOMARDGUI/CreateCase.ui @@ -441,7 +441,7 @@ - Conformité + Conformity + diff --git a/src/HOMARDGUI/HOMARD_msg_fr.ts b/src/HOMARDGUI/HOMARD_msg_fr.ts index 3216f739..0a6750d9 100644 --- a/src/HOMARDGUI/HOMARD_msg_fr.ts +++ b/src/HOMARDGUI/HOMARD_msg_fr.ts @@ -387,6 +387,10 @@ Non conformal option Option de non conformité + + Conformity + + Conformité + + Free Libre diff --git a/src/HOMARDGUI/HOMARD_msg_ja.ts b/src/HOMARDGUI/HOMARD_msg_ja.ts index deffcdad..ceda46c4 100644 --- a/src/HOMARDGUI/HOMARD_msg_ja.ts +++ b/src/HOMARDGUI/HOMARD_msg_ja.ts @@ -388,6 +388,10 @@ Non conformal option 非共形オプション + + Conformity type + 適合タイプ + Free Free -- 2.39.2