$$$$ LIRE NOTICE JC220346 14/02/19 21:15:03 7971 DATE 14/02/19 1. Directive LIRE Voir aussi : SORT -------------- LIRE | (GEO1) | ; | 'MED' FIC1 (MOT1) | ; | 'PROC' FIC1 (MOT1) | ; 2. Operateur LIRE -------------- TAB1 = LIRE | 'AVS' | ; | 'UNV' MOT1 | | 'FEM' FIC1 | Description : ____________ 1. Directive LIRE -------------- 1. The LIRE instruction reads a mesh on the logical unit file N1 defined by the OPTION instruction: OPTION LECT N1; (N1 = 4 by default) All the subobjects in the file are read too. If the name GEO1 of the mesh is provided, it is checked that it indeed does exist in the file. 1.2. The LIRE instruction reads the MED object familly named MOT1 in the file FIC1. If MOT1 is not given, the LIRE instruction prints the names of all the famillies saved in FIC1. 1.3. The LIRE instruction creates one or several PROCEDUR objects based on the content of the file FIC1. Two options are available : a) The syntax of the file FIC1 is the same as the one used to load procedures from UTILPROC (see the manual of UTIL) : - Each procedure is encapsulated in a block opened by DEBP and closed by FINP - Each of these blocks is preceded by a line beginning by "$$$$ xxxxxxxx" where the word xxxxxxxx must be a valid GIBIANE name, identical to the one specified after the associated DEBP instruction (case insensitive) If MOT1 is given, then only the procedure with such a name will be loaded from FIC1 (if it ever exists). b) The file is a batch of GIBIANE instructions. In this case, an object of type PROCEDUR is created and the content of FIC1 is loaded in it. Therefore, the instruction DEBP must not appear anywhere in the file. 2. Operateur LIRE -------------- 2.1 When the 'AVS' keyword is present LIRE becomes an operator. It reads the file of logical unit number N1, N1 being defined by the directive OPTION : OPTION LECT N1; (N1 = 4 by default) It is supposed that the file has the AVS UCD (Unstructured Cell Data) ASCII format. The objects found in the file are put to the TAB1 array (of type TABLE). The contents of this array are following (all the indices are of MOT (i.e. word) type) : -------------------------------------------------------------------- Index | Contents -------------------------------------------------------------------- MAILSUPP | A mesh (MAILLAGE type) composed of points (POI1) and | containing all the nodes in the file. It serves as the | support of the nodal field (CHPOINT type) if the latter | is present. It is always created. It may be used as a | background to find out the positions of different parts | in the whole mesh. -------------------------------------------------------------------- LEMAILLA | The mesh (MAILLAGE type) containing all the elements | found in the AVS file. It is composed of elementary sub- | meshes. Every such a sub-mesh is composed of one type of | elements and all its elements have the same material | number. It is always created. -------------------------------------------------------------------- SOUMAILA | It is an array (TABLE type). This array contains all the | elementary sub-meshes, which are pointed by the integer | indexes ranging from 1 to the number of the sub-meshes. | It is always created. -------------------------------------------------------------------- LECHPOIN | Nodal field (CHPOINT type). It is created only when the | AVS file contains such a field. The MAILSUPP mesh is its | support. -------------------------------------------------------------------- LEMCHAML | Element type field (MCHAML). It is created only when the | AVS file contains such a field. It is composed of | elementary fields. The sub-meshes contained in SOUMAILLA | are the supports of these elementary fields. -------------------------------------------------------------------- anything | A real number. All components of the global field (if it else | exists) appear in the table with their name (truncated to | 4 caracters) as the index. -------------------------------------------------------------------- Several UCD structures may be read from the same file (ex. created with the SORT 'AVS' ... 'SUIT' directive) if the LIRE 'AVS' operator is used several times (see soravs.dgibi). 2.2 When the keyword 'UNV' is used, LIRE becomes an operator which is able to read an ASCII file whose name is FIC1 (MOT type) and whose format is UNV (stands for UNiVersal). The information read in the DATASET wichh have the key number 2411, 2412, 2470 and 2477 are stored as MAILLAGE type objects in the TABLE type objet named TAB1 and described below. The data contained in the DATASET whose key number are 151 and 164 are read and printed only for user information. The other DATASET key numbers are ignored when they are read. -------------------------------------------------------------------- Index | Contents (MOT type) | (MAILLAGE type) -------------------------------------------------------------------- 'NOEUDS' | The mesh (MAILLAGE type object) composed of points | (POI1) including all the read nodes (DATASET 2411) -------------------------------------------------------------------- 'MAILLAGE' | The mesh (MAILLAGE type object) containing all the | elements read from the UNV file (DATASET 2412) -------------------------------------------------------------------- '@elti' | The created mesh (MAILLAGE type object) correspond to | an elementarymesh constituted by all the elements | type '@elti' read in the UNV file (DATASET 2412). | (Example : '@SEG2', '@TRI3', '@CUB8', ...) | The mesh with the name 'MAILLAGE' is constituted by | the union of the elementary meshes saved into the | different indices '@elti'. -------------------------------------------------------------------- 'grelti' | The mesh (MAILLAGE type) read in the UNV file which | corresponds to the element set linked to the physical | properties whose name is 'grelti' (DATASET 2470) | Caution : The 'grelti' index is totally identical to | the read name as stored in the file. So it can | contains spaces and also lower and upper letters | that have to be considered different ! -------------------------------------------------------------------- 'permai' | The mesh (MAILLAGE type) read in the UNV file which | corresponds to the element set (permanent group) | whose name is 'permai' (DATASET 2477) | Caution : The 'permai' index is totally identical to | the read name as stored in the file. So it can | contains spaces and also lower and upper letters | that have to be considered different ! -------------------------------------------------------------------- 2.3 When the keyword 'FEM' is used, LIRE becomes an operator which read an ASCII FEM file named FIC1 (MOT type) (FEM is a format read an written in the OptiStruct Profile of HyperMesh distributed by ALTAIR http://www.altair.com). Each 'Components' named in HyperMesh are placed in a TABLE type object named TAB1. Each index of the TABLE TAB1 is a mesh (MAILLAGE type object). $$$$
© Cast3M 2003 - All rights reserved.
Disclaimer