3. Operands#
3.1. Operand MAILLAGE#
♦ MAILLAGE = my
The mesh type [mesh] to be analyzed. Attention, the analysis will only focus on nodes, stitches-points, segments, segments, triangles, quadrangles, tetrahedra, hexahedra or pentahedra. If a mesh containing other cells, for example pyramids, is provided, two scenarios are possible: either an erroneous stop, or information on the authorized zone, the rest of the mesh being ignored. The choice between these two modes of operation is made by the keyword ELEMENTS_NON_HOMARD.
The mesh is in degrees 1 or 2, but it is not possible to mix the two.
In all cases, the presence of HEXA27 enriched meshes is prohibited.
3.2. Operand NOMBRE#
◊ NOMBRE = /' OUI '[DEFAUT]
/” NON “
If the choice is” OUI “, a summary of the number of nodes and meshes is printed on the message file.
3.3. Operand QUALITE#
◊ QUALITE = /' OUI '[DEFAUT]
/” NON “
If the choice is” OUI “, a mesh quality report is printed on the message file.
The quality of a triangle is defined as the ratio between the length of the longest side and the radius of the inscribed circle.
The quality of a quadrangle is defined as the quotient of the product of the longest length and the averages on the sides and diagonals by the smallest of the areas of the triangles internal to the quadrangles.
Likewise, the quality of a tetrahedron is defined as the ratio between the length of the longest side and the radius of the inscribed sphere.
The quality of a hexahedron is defined as the worst of the qualities of the inscribed tetrahedra.
All of these quality measures are standardized to 1 in the case of an equilateral triangle, square, equilateral tetrahedron, or cube. For any non-equilateral mesh, the quality is greater than 1. See reference [bib1] for detailed explanations.
The result is presented in the form of tables, with the extreme values.
The interpretation of the values produced depends on the numerical method used for the calculation. Depending on whether the problem is isotropic or not, depending on the speed of spatial variation of the data, depending on the calculation technique, the same mesh can lead to a good Jacobian or not. The main thing at first is to spot the really bad stitches. If we observe that the maximum quality exceeds 100, even 1,000 or 100,000, we must be worried: one or more meshes are very deformed and the mesh must certainly be repeated. Secondly, this quality information should make it possible to compare two meshes that are a prima facie correct, without much value. If the problem is isotropic, it will be advantageous to use the mesh with the quality distribution closest to 1.
Illustrations of quality values for different meshes can be found in [Ref. 5].
3.4. Operand DIAMETRE#
◊ DIAMETRE = /' OUI '[DEFAUT]
/” NON “
If the choice is” OUI “, a summary of the mesh diameters is printed on the message file.
The diameter of a mesh is defined as the length of the largest segment that can be inserted into the mesh.
For a triangle or a tetrahedron, the diameter corresponds to the length of the longest side.
For a quadrangle, hexahedron, pentahedron, or pyramid, the diameter is the maximum between the length of the longest side and the length of the largest diagonal.
The result is presented in the form of tables, with the extreme values.
3.5. Operand CONNEXITE#
◊ CONNEXITE = /' OUI '[DEFAUT]
/” NON “
If the choice is” OUI “, a connectivity report is printed on the message file. We will then know if the segments, the 2D cells (triangles and quadrangles combined) or the 3D cells (tetrahedra, hexahedra, pentahedra and pyramids combined) are in one piece or divided into several blocks. We will also know the number of holes in the structure: the through holes or the internal holes.
3.6. Operand TAILLE#
◊ TAILLE = /' OUI '[DEFAUT]
/” NON “
If the choice is” OUI “, a summary of the sizes of the subdomains is printed on the message file. A subdomain is defined as a set of cells of the same size and belonging to the same groups.
3.7. Operand PROP_CALCUL#
◊ PROP_CALCUL = /' OUI '[DEFAUT]
/” NON “
If the choice is” OUI “, a diagnosis on the properties of the meshes as elements for calculation is printed on the message file. We count the number of overstressed elements: the elements where all the vertices are located on the edge. We count the volume cells (or surface cells) that touch the edge of the domain but that are not bordered by surface cells (or linear cells).
3.8. Operand INTERPENETRATION#
◊ INTERPENETRATION = /' OUI '
/” NON “[DEFAUT]
If the choice is” OUI “, we check that the mesh is correct from the point of view of coverage: no mesh has one of its vertices inside another mesh.
Warning: this operation can be expensive for large meshes, hence the choice “NON” by default.
3.9. Operand MAILLAGE_FRONTIERE#
◊ MAILLAGE_FRONTIERE =MAF
The choice of this option means that the segments forming the edge of the calculation mesh or an internal limit are attached to a fine description of this edge. This fine mesh is transmitted here. The link is made by belonging of the segments to the same groups.
3.10. Operand GROUP_MA_FRONT#
◊ GROUP_MA_FRONT =l_grma
If this option is absent, the link between the segments is made for all the groups present in the border mesh. If the link is only made for a few groups, they are designated here.
3.11. Operand ELEMENTS_ACCEPTES#
◊ ELEMENTS_ACCEPTES = /' HOMARD '[DEFAUT]
/” IGNORE_PYRA “
In its current version, HOMARD only refers to certain meshes: mesh-points, segments, triangles, quadrangles, tetrahedra, hexahedra, hexahedra, pentahedra in degrees 1 or 2.
By using the “HOMARD” option, the transmission of a mesh containing anything other than these types of meshes will cause an error to be stopped. It is the default option.
By choosing the “IGNORE_PYRA” option, you can analyze a mesh including pyramids. The information will only cover the areas authorized by HOMARD, the rest of the mesh will be ignored.
In all cases, the presence of HEXA27 enriched meshes is prohibited.
3.12. Operand VERSION_HOMARD#
◊ VERSION_HOMARD = /'V11_10' [DEFAUT]
/”V11_N” /”V11_N_ PERSO “
This operand allows you to select the version of HOMARD that is used for the adaptation. By default, HOMARD 11.10 is started. It is the reference version. Choosing “V11_N” activates version 11.n of HOMARD which is the development version. The “V11_N_ PERSO “choice activates a user-specific development version. This option allows the HOMARD development team to develop new features. It also allows the user to benefit from an innovation in HOMARD before commissioning in Code_Aster.
3.13. Operand LANGUE#
◊ LANGUE = /' FRANCAIS '[DEFAUT]
/” FRENCH “ /” ANGLAIS “ /” ENGLISH “
This operand specifies the language in which messages from HOMARD are printed.
3.14. Operand LOGICIEL#
◊ LOGICIEL = software [K]
This option suggests using another coupling interface between Code_Aster and HOMARD than the one provided by default in the directory of tools associated with Code_Aster. This option is in fact reserved for the HOMARD development team to develop new features. It allows you to test new features before modifying the control macro command.
3.15. Operand UNITE#
◊ UNITE = unit [I]
This option is only possible if you have activated the development version of HOMARD, 11.n. The data file transmitted by the user under this logical unit number will be directly transmitted as a complement to the HOMARD configuration file. This option is in fact reserved for the HOMARD development team to develop new features. It allows you to test new features before modifying the control macro command.
3.16. Operand INFO#
◊ INFO =/1
/2 /3 /4
If INFO is 1, the impressions are minimal; we only get those that were explicitly requested, the quality of the stitches for example, and any error messages.
If INFO is 2, we will get the messages sent by the commands underlying the macro-command: IMPR_RESU, LIRE_MAILLAGE, LIRE_RESU.
If INFO is 3, we will get the standard messages from HOMARD, summarizing the execution.
If INFO is 4, we will have all the messages sent by HOMARD, for debugging.