HOMARD : Control data |
![]() |
HOMARD is available on various computers. For example, PC-LINUX, workstations SUN, Compaq, ... It can be used with any other finite element software than Code_Aster®. To achieve mesh adaptation, some information have to be given to HOMARD :
To use HOMARD, control data must be provided ; they include the definition of all files involved as well as control options.
Rules which govern this file are the following :
# # Calculation mesh # NumeIter 1 CCNoMN__ M_1 CCMaiN__ $HOME/Rotor_study/cas_1/mesh.1.med CCNoMNP1 M_2 CCMaiNP1 $HOME/Rotor_study/cas_1/mesh.2.med # # Options for adaptation # CCNoChaI ERREST RESU_1__ERRE_ELEM_NORE__________ CCNumOrI 10 CCNumPTI 10 CCIndica $HOME/Rotor_study/cas_1/mesh.1.med TypeRaff free SeuilHPE 3. TypeDera free SeuilBPE 25. # # Fields to be updated # CCChaNom 1 RESU_1__TEMP____________________ CCChaNuO 1 9 CCChaPdT 1 9 CCChaNom 2 RESU_1__DEPL____________________ CCChaNuO 2 10 CCChaPdT 2 10 CCSolN__ $HOME/Rotor_study/cas_1/mesh.1.med CCSolNP1 $HOME/Rotor_study/cas_1/mesh.2.med # # Temporary HOMARD files # HOMaiN__ Mai1 /tmp/mesh.1.hom HOMaiNP1 Mai2 /tmp/mesh.2.hom # # Standard output # ListeStd $HOME/Rotor_study/cas_1/output.1.to.2
Some comments about theses intructions.
The initial point is a mesh which was obtained after 1 adaptation iteration. Its name is M_1 and it is in file $HOME/Rotor_study/cas_1/mesh.1.med. After adaptation, the name of the new mesh will be M_2 and it will be written down in file $HOME/Rotor_study/cas_1/mesh.2.med.
Adapation will be governed by component ERREST of field RESU_1__ERRE_ELEM_NORE__________, at order number and time step 10. This error indicator is in file $HOME/Rotor_study/cas_1/mesh.1.med. Refinement is asked over the worst 3% of elements. Unrefinement is asked for the 25% elements with the lowest error.
Field RESU_1__TEMP____________________, at order number and time step 9, and field RESU_1__DEPL____________________, at order number and time step 10, will be updated. They are taken from file $HOME/Rotor_study/cas_1/mesh.1.med, then written in file $HOME/Rotor_study/cas_1/mesh.2.med.
Temporary files /tmp/mesh.1.hom and /tmp/mesh.2.hom contains relationships between meshes from iterations 1 and 2. These relationships are named Mai1 and Mai2.
Last, messages from HOMARD will be written down in file $HOME/Rotor_study/cas_1/output.1.to.2.
Here is the list of keywords. When a default value exists, it is written with blue.
Input and output meshses :
NumeIter | Iteration rank for the mesh to be adapted. |
CCMaiN__ | Name of the file MED with the mesh to be adapted. |
CCNoMN__ | Name of the mesh to be adapted in the file. |
CCMaiNP1 | Name of the file MED which will include the new mesh. |
CCNoMNP1 | Name of the adapted mesh. |
The error indicator :
CCIndica | Name of the file MED with error indicator. |
CCNoChaI | Name of component to be used followed by the name of field of error indicator in the file. |
CCNumOrI | Selected order number. If not, HOMARD assumes that the filed was written without any number. |
CCNumPTI | Selected time step. If not, HOMARD assumes that the filed was written without any time step. |
Fields to be updated :
CCSolN__ | Name of the MED file MED which contains old fields. |
CCSolNP1 | Name of the MED file MED which contains new fields. |
CCChaNom | Rank of field | Name of the field to be updated. |
CCChaNuO | Rank of field | Order number of the field to be updated. |
CCChaPdT | Rank of field | Time step of the field to be updated. |
Adaptation strategy. There is a choice between various refinement and unrefinement types :
TypeRaff | free | Refinement based on an error threshold. |
hanging_nodes | Non-conforming elements, with 1 hanging node maximum. | |
hanging_nodes_indicator | Non-conforming elements, direct from the indicator. | |
uniform | All the elements are split. | |
no | No refinement. | |
TypeDera | free | Unrefinement based on an error threshold. |
uniform | All the elements are grouped. | |
no | No unrefinement. |
Specific options for refinement :
NiveauMa | Maximal level for refinement. |
SeuilHau | Absolute error threshold. Every element with higher error is split. |
SeuilHRe | Relative error threshold. The same, but the threshold is a fraction of the difference of error maxi/mini. The threshold is given with %, between 0 and 100. |
SeuilHPE | Fraction of elements with the highest error. The threshold is given with %, between 0 and 100. |
Specific options for unrefinement :
NiveauMi | Minimal level for unrefinement. |
SeuilBas | Absolute error threshold. Every element with lower error is unrefined. |
SeuilBRe | Relative error threshold. The same, but the threshold is a fraction of the difference of error maxi/mini. The threshold is given with %, between 0 and 100. |
SeuilBPE | Fraction of elements with the lowest error. The threshold is given with %, between 0 and 100. |
More options :
ListeStd | Name of the file for the standard output. |
Boundary fitting (2D adaptation only) :
The boundary fitting is made by connecting elements whihc belong to groups with the same name in the calculation mesh and in the boundary mesh. If no specific information is given, every element group in the boundary mesh is involved. The boundary fitting can be reserved for a group list, giving them by a line by group. That is the only exception to the rule of the last line :
SuivFron | no | No boundar fitting. |
yes | Boundary fitting is active. | |
CCFronti | Name of the MED file which contains the boundary mesh. | |
CCNoMFro | Name of the boundary mesh. | |
CCGroFro | Name of the group to be taken. |
Here are the miscellaneous options ::
Langue | French | Messages are written in french. |
English | Messages are in... English ! | |
TypeBila | 0 | No report on mesh. If not, it results from a product of the following choices. |
2 | Number of entities from the point of view of HOMARD. | |
3 | Element interpenetration. Caution : this could be rather costly with 3D mesh ! | |
5 | Quality of the elements. | |
7 | Number of entities from the point of view of the coupled software. | |
11 | Analysis of the connexity. | |
13 | Size of sub-domains. | |
PPBasFic | A prefix for the files which contain the information produced by HOMARD. If absent, these information are written down in standard output. | |
ModeHOMA | 1 | HOMARD is used to adapt a mesh. |
2 | HOMARD is used to get information about a mesh. | |
TypeElem | all | All the element types which HOMARD can split are allowed : bars, triangles, quadrangles, tetraedra. |
mixte | Adaptation is made over possible zones, but zones with hexaedra or pentaedra can pass, provided that they are not contaminated by refinement. | |
simplexe | Only simplexes (bars, triangles, tetraedra) are allowed. | |
CCAssoci | med | Calculation software is connected with MED files. |
HOMARD | HOMARD format is used. |
[ Top | How to do ? | Control data | Rules | Back ]