HOMARD : Control data

French version
 
 

Red ball How to do ?

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 :


The first information is an interaction with the calculation software. The transmission of mesh, error indicator and fields is made via a MED file format, which has been developped in the SALOME project. Releases V8.x and after use release 2.3.1 for MED.
Relationships between old and new meshes are stored in a file which is automatically produced by HOMARD. For adaptation input, the file which was produced at the end of the previous iteration has to be given. At the very first iteration, nothing is given.
Last information on control dat is passed to HOMARD via an ASCII file. This file can be written by an automatic procedure. Code_Aster or Code_Saturne do it.

 

Red ball Control data

Balle jaune Rules

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 :

  • File name is "HOMARD.Configuration" ; it is to be located in the working directory
  • The length of a line is lower than 200 characters.
  • Each line contains one information.
  • A white line is ignored.
  • A line which begins with a # is ignored ; comments can be written down after this #.
  • The order of lines does not matter ; if the same information appears twice or more, only the last one will be kept.
  • A line is made up with a keyword, followed by one or two data.
  • The keyword and data are splitted by at least one blank ; the other blanks are ignored.
  • Environnement variables, such as $HOME, are interpreted while HOMARD is running.


    • Balle jaune Example 

    #
# 1. Standard output
#
ListeStd   $HOME/Rotor_study/cas_1/List.01.to.02
Langue english
#
# 2. General
#
Action   homa
NumeIter   1
CCAssoci med
#
# 3. Links withs computation code
#
CCNoMN__   M_1
CCMaiN__   $HOME/Rotor_study/cas_1/mesh.01.med
CCSolN__   $HOME/Rotor_study/cas_1/mesh.01.med
#
CCNoMNP1   M_2
CCMaiNP1   $HOME/Rotor_study/cas_1/mesh.02.med
CCSolNP1   $HOME/Rotor_study/cas_1/mesh.02.med
#
# 4. Options for adaptation
#
CCNoChaI ERREST RESU_1__ERRE_ELEM_NORE__________
CCNumOrI 10
CCNumPTI 10
CCIndica   $HOME/Rotor_study/cas_1/mesh.01.med
TypeRaff   free
SeuilHPE   3.
TypeDera   free
SeuilBPE   25.
#
# 5. 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.01.med
CCSolNP1   $HOME/Rotor_study/cas_1/mesh.02.med
#
# 6. Temporary HOMARD files
#
HOMaiN__   Mai1   /tmp/mesh.01.hom
HOMaiNP1   Mai2   /tmp/mesh.02.hom

    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.01.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.02.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.01.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.01.med, then written in file $HOME/Rotor_study/cas_1/mesh.02.med.
    Temporary files /tmp/mesh.01.hom and /tmp/mesh.02.hom contains relationships between meshes from iterations 1 and 2. These relationships are named Mai1 and Mai2.
    Last, english messages from HOMARD will be written down in file $HOME/Rotor_study/cas_1/List.01.to.02.

    Balle jaune Keyword list

    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 may have few components. If few has to be taken into account one has to indicate which ones and how to (L2 norm or absolute value ... ). If this is not done, HOMARD take the Euclidean norm of all components  :

    CCIndica Name of the file MED with error indicator.
    *CCNoChaI Name of the field in the file to be used as an error indicator.
    CCCoChaI Name of component to be used.
    CCUsCmpIWay to calculate the indicator -1 :
    • 0 L2 norm,
    • 1 infinite norm,
    • 2 relative value. (only if only one component is indicated.
    CCModeFIWay to calculate the indicator -2 :
    • 0 : The value of the indicator is used on each mesh.
    • 1 : We use the jump of the indicator between two meshes.
    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.

    Then, for every field to be updated, the following will be found :

    CCChaNom Rank Name of the field.
    CCChaNuO Rank Order number.
    CCChaPdT Rank Time step.
    CCChaIns Rank Instant.
    CCChaCaS Rank Characteristics of field support : 'standard' or 'aux_noeuds_par_element'.
    CCChaNCN Rank For a field over points of Gauss, rank of the associated field over nodes per element.'.

    The rank of field is an integer between 1 and the total number of fiels to be updated. Lines can be placed in any order provided that the numeration is full.


    Refinement according area. A choice among different kinds of area is given by a number:

    ZoRaType area number 1 Rectangular area. 5 Cylindrical area
    2 Parallepipedic area 6 Drilled disc
    3 Disc 7 Pipe
    4 Spherical area.


    When an area is 2D, it means that Z is constant and omitted


    Parallepipedic or rectangular area ZoRaXmin Area number Xmin of the box ZoRaXmax Area number Xmax of the box
    ZoRaYmin Area number Ymin of the box ZoRaYmax Area number Ymax of the box
    ZoRaZmin Area number Zmin of the box ZoRaZmax Area number Zmax of the box


    Spherical or discal area ZoRaXCen Area number X center of the sphere
    ZoRaYCen Area number Y center of the sphere
    ZoRaZCen Area number Z center of the sphere
    ZoRaRayo Area number Radius of the sphere


    cylindrical area ZoRaXBas Area number X center of the basis
    ZoRaYBas Area number Y center of the basis
    ZoRaZBas Area number Z center of the basis
    ZoRaRayo Area number Radius of cylindre
    ZoRaXAxe Area number X vector Axe
    ZoRaYAxe Area number Y vector Axe
    ZoRaZAxe Area number Z vector Axe
    ZoRaHaut Area number Height


    Pipe ZoRaXBas Area number X center of the basis
    ZoRaYBas Area number Y center of the basis
    ZoRaZBas Area number Z center of the basis
    ZoRaXAxe Area number X vector Axe
    ZoRaYAxe Area number Y vector Axe
    ZoRaZAxe Area number Z vector Axe
    ZoRaHaut Area number Height
    ZoRaRayI Area number Internal Radius of the pipe
    ZoRaRayE Area number External Radius of the pipe

    Adaptation strategy. There is a choice between various refinement and unrefinement types :

    TypeRaff free Conforming refinement.
    hanging_nodes_1_node Non-conforming elements, with 1 hanging node maximum per edge.
    hanging_nodes_1_edge Non-conforming elements, with 1 hanging edge maximum per element.
    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 information per mesh.
    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 | With Code_Aster® ]

    Logo droit [ Home page | Presentation | Images | User Guide | Documentation | Contact ] Logo gauche

    © EDF Electricité de France 1996, 1997, 2010. All rights reserved.