GiD The universal, adaptative and user friendly pre and postprocessing system for computer analysis in science and engineering Customization ManualTable of Contents Chapters 1 FEATURES: 2 INTRODUCTION 2 XML file 2.1 ValidatePassw ord node 4 PROBLEMTYPE SYSTEM 4.1 Structure of the problem type 4.2 Definitions 4.3 Data tree fields 4.3.1 PTdata 4.3.1.1 container 43.1.2 value 4.3.1.3 condition 4.3.1.3.1 symbol 4.3.1.4 blockdata 4.3.1.5 edit_command 4.3.1.6 dependencies 4.3.1.7 groups 4.3.1.8 groups_types 4.3.1.8.4 group_type 4.3.1.9 units 4.3.1.9.3 unit_magnitude 4.3.,9:2.4 unit 4.3.1.20 function 4.3.1.20.1 functionVariable 4.4 Units 4.5 Main procedures 4.6 Writing the input file for calculation 4:7 User preferences 4.8 Import export materials 4.9 About Customuib 4.10 CustornLiB extras 4.10.1 SPD_fields 4.10.4. include 4.10.2 Extra functions 5 EXECUTING AN EXTERNAL PROGRAM 5.1 Show ing feedback when running the solver 5.2 Commands accepted by the GiD command.exe 5.3 Managing errors 5.4 Examples 6 PREPROCESS DATA FILES 6.1 Geometry format: Modelname.geo 6.1.1 Geometry example 7 POSTPROCESS DATA FILES 7.4 Results format: Modall'ame,postres 7.1.4 Gauss Points 7.2.2 Result Range Table 7.2.2 Result 7.2.3.3 Results example 7.4.4 Result group 7.2 Mach format: ModelN'ame.post.msh 7.2.1 Mesh example 7.2.2 Group of meshes 7.3 List fle format: Modell ame. post lst Pag, 20 a 12 13 13 33 33 33 a4 a4 a4 a4 a4 35 29 39 22 23 23 24 24 24 24 27 27 2 32 33 35 35 38 43 43 44 48 49 st 34 36 39 39 62Table of Contents fi 7.4 Graphs file format: Modelltame.post. orf 63 8 TCL AND TK EXTENSION 65 8.1 Event procedures 6s 8.2 GiD_Process function n 8.3 GiD_Info function 3 8.3.1 automatictolerance 73 8.3.2 condtions 73 8.3.3 coordinates 74 8.3.4 check 74 8.3.5 events 74 8.3.6 gendata 8 8.3.7 geometry 5 8.3.8 gidbits 8 8.3.9 gidversion 76 8.3.10 graphcenter 76 8.2.12 intvdata 76 8.3.12 ispointinside 76 8.3.13 layers 76 8.3.14 listmassproperties ” 8.3.15 list_entities ” 8.3.16 localaxes 9 8.3.17 magnitudes 9 8.3.18 materials 9 8.3.19 mesh 9 8.3.20 meshauality 80 8.3.21 opengl 80 8.3.22 ortholimits 80 8.3.23 bounding_box 80 8.3.24 parametric et 8.3.25 perspectivefactor e1 8.3.26 postprocess et 8.3.27 problemtypepath 83 8.3.28 project 83 8.3.29 robdefauitbackground 83 8.3.30 unitssysters 34 8.3.91 variables 34 8.3.92 view 34 8.4 Special Tel commands 34 8.4.1. Geometry 84 8.4.2 Mesh 86 8.4.2.1 Preprocess mesh 86 8.4.2.2 Cartesian grid 97 8.4.2.3 Postprocess mesh 97 8.4.3 Groups 38 8.4.3.1 Definition 88 8.4.3.2 Entities 88 8.4.4 Data 89 8.4.5 Results 92 8.4.6 Sets 93 8.4.6.1 Definition 93 8.4.6.2 Entities 93 8.4.7 Graphs 94 8.4.8 GraphSets 95 8.4.9 OpenGL 95 8.4.10 Other 97 8.5 HTML help support 00 8.5.1 HelpDirs 00Table of Contents 8.5.2 Structure of the help content 8.5.3 TocPage 8.5.4 IndexPage 8.6 Managing menus 8.7 Custorn data window = 8.7.1 TeWidget 8.7.2 Data window s behavior 8.8 Interaction with themes 8.8.1 Asking for images 8.8.2 Forcing themes use 8.8.3 Creating new themes 8.9 GID version 8.10 Detailed example 9 PLUG-IN EXTENSIONS 9. Tel plugrin 9.2 GID dynamic library plug-in 9.2.1 Introduction 9.2.2 In GiD 9.2.3 Developing the plugin 9.2.4 Functions provided by iD 9.2.5 List of examples 410 APPENDIX A (PRACTICAL EXAMPLES) 41 APPENDIX B (classic problertype system) 11.4 PROBLEMTYPE ‘CLASSIC’ 11.4.1 CONFIGURATION FILES 11.1.2.1 Conditions file (.end) 41.4.4.4.1 Example: Creating the conditions file 11.1.2.2 Problem and intervals data file (.prb) 11.4.4.2.1 Example: Creating the PRA data file 11.2.4.3 Materials file (.mat) 411.2.4..1 Example: Creating the materials file 14.1.4.4 Special fields 11.1.4.5 Unit System file (.uni) 11.1.1.6 Conditions symbols file (sim) 11.1.1.6.1 Example: Creating the Symbols file 11.2.2 TEMPLATE FILES 11.1.2.1 Commands used in the .bas file 11.1.2.1.1 Single value return commands 11.1.2.1.2 Multiple values return commands 11.1.2.1.3 Specific commands 11.1.2.2 General description 1.1.2.3 Detailed example - Template file creation 11.4.2.3.1 Formatted nodes and coordinates listing 11.1.2.3.2 Elements, materials and connectivities listing 11.4.2.3.3 Nodes listing declaration 11.1.2.3.4 Elements listing declaration 11.4.2.3.5 Materials listing declaration 411.4.2.3.6 Nodes and its conditions listing declaration 100 aon aon on 104 104 06 107 107 109 109 120 aaa a3 a3 13 13 a3 a4 us us 9 aa aaa 322 322 12s 126 126 227 128 128 133 134 134 135 136 136 140 143 150 150 154 156 156 357 158 1591 FEATURES Gi offers the following custorrization features: + Complete menu's can be custorrised and created to suit the specific needs of the user's simulation softw are, * Simple interfaces can be developed bety een the data definition and the simulation softw are. * Simple interfaces based on scalar, vector and matrix quantities can be developed for the resuits visualisation. © Menus for the results visualisation can be customised and created according to the needs of the application or analysis, “The customization in GiD is done by creating a Problem Type,INTRODUCTION2 INTRODUCTION When GiO is to be used for 2 particular type of analysis, itis necessary to predefine all the information required from the User and to define the w ay the final information is given to the solver module, To do so, some files are used to describe conditions, materials, general data, units systems, symbols and the format of the input file for the solver. We give the name Problem Type to this collection of files used to configure GiD for a particular type of analysis. Not this tutorial is included mith the GiD package you have bought. You can also dovnload it from the GID support web page (http://w gidhome. corn/ support). + You can also learn how to configure GiD for a particular type of analysis by following the Problem Type Tutorial; GiD has been designed to be a general-purpose Pre- and Postprocessor: consequently, the configurations for different analyses rust be performed according to the particular specifications of each solver. It is therefore necessary to create specific data input files for every solver. How ever, GiD lets you perform this configuration process inside the program itself, without any change in the solver, and without having to program any independent utility. GiD Prone Pospecess C SOLVER C INPUT OUTPUT FILE FILE “To configure these files means defining the data that must be input by the user, aswell as the materials to be implemented and other geometrical and time-dependent conditions. It is also possible to add symbols or dravings to represent the defined conditions, GiD offers the opportunity to work with units when defining the properties of the data mentioned above, but there must be a configuration file where the definition of the units systems can be found. It is also necessary to define the way in which this data is to be written inside the file that will be the input file read by the corresponding solver From the 13th version of GiD, 2 nen system of problertye has been implemented (based in the CustomLIB library) [Although the ‘classic’ problem type system is stil supported by GiD, itis considered deprecated, as the new one offers clear advanteges in terms of usability, performance and integration cappabilities. Documentation about the deprecated classic problem type systern can be found in the annex of this manual ‘This new problem type definition uses a single .=pd file to describe general properties, materials, conditions and units (as a tree with xml syntax), All this data is show ed in a ‘ree view", and materials and conditions are associated to groups of enties. About writting the input fle, Tel commands are used to write the data in files (optionally aided with the special funcion GiD_WriteCaleulationFile for efficiency). “The new problem type creation system lean on a collection of tools, which facilitates the development of advanced problem types for customizing the personal pre and post processor system GID for computer simulation codes. It is based on a XML hierarchical structure and an automatic physical tree view.XML file3 XML file The file problem_type.xml declare information related to the configuration of the problem type, such name, version, file browser icon, passw ord validation or message catalog location, history news, etc. ‘The data included inside the xm file should observe the following structur “ifane XC/Hame> eer iene) Version By default GiD read this file when loading the problertype and provide its key-value pairs parsed in a Tel global array named 'problemtype_current (2.9. $1:problemtype_current{version) returns the version of the problerntype) Compulsory nodes: (the values of these nodes are just examples) + itane>emas7a_custonl ib to provide an identifier name for the problem type, + 1. 0¢/Version> dotted version number of the problem type. ‘The name and version of the problemtype is used to compare the version of the problemype used for a old model and do ‘an automatic transform if necessary to try to map the old and new data fields. ‘The ‘Internet retrieve! tool also uses Mame and Version to compare a local problemtype with the remote copy of the Internet repository, Optional node: © -ctiniman¢iDVersion>12.1.114¢/MiniamnGiDVersion> to state the minim GiD version required. Te the problempe iz loaded in a GID version lower than the one required a warning mevsage will he 2 cimagePil eBrowser>inages/ InageFileBrowser gifc/ ImageTileBrowser> icon image to be used in the file browser to show a project corresponding to this problem cype. The recommended dimensions for thiz + ctingeatReoe>scripes/nogs 2 pach, relative of absolute, indicating where the folder wich + .. 2 path, relative or absolute, indicating where to write the passn ord information see ValidstePacsy ord node -paq. 5). + WalidatePassword> provides a custom validation script in order to override the default GiD validation (see ValidatePassu ord node -pag. 5). + i This node must be defined only for ‘customLib like! problerrtypes, with values O (default) or 1 If true i alloys to do. automatic tasks to ure the library (otherwise the problemtype developer must write extra code to use the library, like load packages, initialize the library, etc.) + ic/ Custonk ibllativeccoups> This node must be defined only for ‘custorrLib like’ problemtypes, with values 0 (default) or 1, to specify that the library uses ‘native GID groups’ instead of ‘pseude-groups GiD conditions’ It is possible to set other non-standard nodes, to use 3.1 ValidatePassword node ‘The default action taken by GID when validating a problem type passw ord is verifying that it is nat empty. When a passu ord is considered as valid, this information is written in the fle ‘passw ord.tst’ which is lecated in the problem type directory. In order to override this behaviour, tv o nodes are provided in the .xmrl file * Passi ordPath: The value of this node specifies a relative or absolute path describing where to locate/create the file password.txt. If the value is a relative path itis taken with respect to the problem type path, Exarle: PasswordPath>.. * ValidatePassn ord: The value of this node is a Tel script which will be executed when a passw ord for this problem type needs to be validated. The script receives the parameters for validation in the following variables: key with the contents of the password typed, dir with the path of the problem type, and computer_name with the name of host machine Note: Its like this Tel procedure prototype: proc Passw ordPath { key dir computer_name} {... body... } ‘The script should return one of three possible codes:ValidatePassword node 6 On case of failure, Lin case of success 2 in case of success; the difference here is that the problem type has just saved the password. information so GID should not do it. Furthermore, we can provide a description of the status returned for GID to show to the user. If ancther status is returned, itis assumed to be 1 by default Below is an example of a node, Hvalidacion-exe simulates an external program to validade the key for chis conpucemnane Hinsvead an external program can be used a cel procedure Gf ( [catch (set rex [exec [£ile join fair validation.exe] fkey fcomputername]) megexe] ) ( zetumn (Lise 0 "Error fmagezs"] > switch “regexp -- res ( ‘eai1RB ( seturn (Lise 0 “you ask me co fail!) > ckandsaveRB ( proc save_pass (dir id pass) ( see date [clock format [clock second] “format "WY tm ta") Bee £a [open [4ile goin Faiz. "pasoword.cxe") “a"] pats $£a "Pid fpans # faace Password for Problem cype ‘Faiz! close #68 > pave_pass $4iz fcompucernane fey zenawe sate pass secur (Iise 2 "password fey saved by me" > oun seturn (Lise 1 "password fkey will be saved by gid") > default ( seturn (ise 0 "Ersoz: unexpected retusn value fzez"] > > 4 PROBLEMTYPE SYSTEM A problem type is a collection of utilities, which allows the user to interact easily with them by means of a Graphical User Interface (GUI), and facilitates the definition and introduction of all the data necessary for carrying out a particular calculation. In order for GID to prepare data for a specific analysis program, it is necessary to customize it. The customization is defined in GiD by means of a problem type. ‘The new system of problem types creation adds some additional capabilities compared with the classic one: © Ik takes advantage of the XML (Extensible Markup Language) format features and its hierarchical structure. It stores data more efficiently. The elements in a XML document form a tree-structure that starts at Dithe roctL] and branches to [ithe leaves(] with different relationships betw een the nested elements It permits to process automatically XML documents on 2 physical data tree view on the GID window for interfaces creation. + It facilitates the automatic creation of standard windows in the data tree to enter input dates. It couples geometry or mash entities with identical properties inta the called groups using these standard window s + It permits to couple entities with identical properties into groups. In this w ay, it couples geometry or mesh entities with Identical properties into the called groups using these standard window s + If allows to apply efficiently geometry properties and boundary conditions (je. constraints, loads, materials...) into ‘groups and to edit their properties easily. + In order to configure GiD for a specific type of analysis, itis possible to set the data tree hiding the required parts automatically «= Ik allows to fix the data tree hiding concrete parts if this is convenient, for a specific type of analysis. =f couples all the common features of the different problem types. 4.1 Structure of the problem type ‘The problem type is defined using a directory with the its name and a set of files, The directory with the problem type will be located in the problemtypes directory in the GiD distribution, or in a subdirectory of it, This set of files define the problertype and contain the full functionality for custorrizing the pre-process. The main files that configure the problem type are shown in the table below. * Main configuration file of the data tree, XML-based. ‘The main configuration file in XML format contains the definition of all the data (except the geometry) necessary to perform an analysis. It ie defined in XML format with the extension .=pd (specific problem type data) and contains all the definition ofall the data that defines the analysis like boundary conditions, loads, materials, loadcases, etc. ‘The syntax rules of the -spd file are very simple, logical, concise, easy to learn and to use. The file is human-legible, clear and easy to create. Moreover, the information is stored in plain text format. It can be viewed in all major of browsers, and itis designed to be self-descriptive ‘The elements in a XML document form a tree-structure that starts at "the root” and branches to "the leaves" with different relationships between the nested elements. It allows to aggregate efficiently elements. Customlib takes advantage of this hierarchical structure to convert automatically the main XML file to a physical tree on the GiD. window. The XML elements can have attributes, which provide additional information about elements. It is necessary to modify this XML document in order to add conditions, or general data to the problem type. + Main TCL fie, initialization ATCL initialization fle is used to create complex window s or menus. Contains the initialization routines + Output description to the file of analysis, ATCL file located in the folder determines the » ay in which the final information has to be written inside theStructure of the problem type 8 input files that will be read by the solver: * Conditions file File with extension .cnd is used but should not be modified by the problemtype creator. * Information for data input fle File .bas is not used it should be existing but void. + Several other TCL files 4.2 Definitions CustomLib defines its own XML tags, which clearly describes its content. For more information about this attribute, see the section| + 100N library ‘The {00M library is used by the Toolkit due to it combines high performance XML data processing with easy and pow erful Tel scripting functionality. 100M is one of the fastest w ays to manipulate XML and it uses very litle memory in the process of creating a DOM tree from a XML document. In TDOM terminology we call Yield to the ‘Element narne! and ‘parameter’ to the ‘attribute’ All data is stored in fields and parameters, where the parameters can contain a value, @ xpath expression or a [TCL command] + XPATH XPath is a language for addressing parts of an XML document using path notations. It is used for navigating through the hierarchical structure of a XML document to extract information. Ttis based on a tree of nodes representing the XML fle, It provides the ability to navigate around the tree, selecting nodes from it and computing string-values. xpath expression -> A search is performed and the result is substituted in the parameter when necessary. [TCL command] -> The command between brackets is executed when necessary and the return value is replaced inside the parameter, 4.3 Data tree fields “The fields and parameters of the main configuration file (.spd) of the data tree, are described below. 4.3.1 PT_data Main root field of the .spd file, It contains the version number and the name of the problem type. PT must be replaced by the problem type name, ‘version ~ Internal version number. 2.69, if the problertype is named ‘cmas2d_customlib’ the main node will be 4.3.1.1 container This is the simplest form to group the data for improving its visualization, (On the resulting window, in addition to the inputs there will be the following set of buttons: It can contain the following fields: , , , , The parameters are as follows, in - Name used to reference the field, especially when writing the .dat fle, pn = Label that will be visualized by the user. It can be translated. icon - It alloys to put an image in .png format in the data tree, The image should be stored inside the images folder of the problem type,container 9 help - 1t displays a pop-up wrindow of help information related to the task the user is performing. state - Specifies one of two states for the field: normal, or hidden. Note that hidden field can be used for storing hidden values, that you de not want to show in the user interface, It also permits to handle a Tel function, by means of square brackets. update_proc - It calls @ TCL procedure, when clicking on the ‘Ok’ button in the window. Square brackets are not supported. actualize_tree - Itupdates the information in the whole data tree, and automatically refresh data shown in the user interface. It is a boolean value as a 1 of 0 that indicates ft is activated or deactivated. Ifthe data source is changed, such 1s new fields have been added or data values and field have been modified, all the user interface will reflact those changes. Furthermore, all the TCL procedures defined in the data tree will be called and the whole data tree will be refreshed. “Therefore, this instruction must be carried out only when necessary. actualize - This only updates a specified field in data tree, Note that only this specified field will be refreshed in the user interface, and not the whole data tree, itis a boolean value as a 1 or O that indicates if is activated or deactivated del_cancel_button - It is a boolean value as 1 of 0 that indicates ifthe cancel button is removed (1) or not (0). On the resulting window there will be only the ‘OK’ button, 2s follow s, Example: selver'/> Stop tolerance! value='Le-8!/> 4.3.1.2 value It is the main field to store data, This field allows to define an entry, or a combobox in the window It can contain the follow ing fields: , , The parameters are as follows, in = Name used to reference the field, especially when writing the .dat fle, pn = Label that will be visualized by the user. It can be translated. \v-The value of default value for a 'value' field state - Specifies one of the four states for the entry: normal, disabled, hidden or readonly. Ifthe entry is readonly, then the value may not be changed using widget commands and ne insertion cursor will be displayed, even # the input focus is in the widget; the contents of the widget may stil be selected, Ifthe entry is disabled, the entry may not be changed, no insertion cursor will be displayed and the contents will nat be selectable. Note that hidden entry can be used for storing hidden values, It alzo permits to define a Tel function, by means of square brackets values_tree - Permits to define a TCL function, by means of square brackets, and returns a combobox with a list of strings values - Commarseparated list of strings For instance, value ‘mech.therm” dict - Comma-separated list of key,value. This operation places a mapping from the given key to the given value, which is shown in the GUL, Values can be translated. For instance, dict="mech Mechanical therm, Thermal" show s Mechanical and Thermal string_is - Tests the validity of various interpretations of a string, as follows, integer ~ To test ifa string is an integer value integer_or_void - To test if a string is an integer value, or empty (not-filled), double - To test if a string is a double value, double_or_void - To test if string is a double value, or empty (not-filed) 1% - To test if a string is a percentage (%4) list_of_double - To test f a string is a list of doubles, representing a data structure of doubles in Te. help = It displays a pop-up window of help information related to the task the user is performing. actualize_tree - Itupdates the information in the whole data tree, and automatically refresh data shown in the user interface. It is a boolean value as a 1 of 0 that indicates ft is activated or deactivated. Ifthe data source is changed, such 1s new fields have been added or data values and field have been modified, all the user interface will reflect those changes. Furthermore, all the TCL procedures defined in the data tree will be called and the whole data tree will be refreshed. “Therefore, this instruction must be carried out only when necessary.value 10 actualize - This only updates a specified field in data tree, Note that only this specified field will be refreshed in the user interface, and not the whole data tree, itis a boolean value ax a 1 or O that indicates if tis activated or deactivated update_proc - It cals a TCL procedure, when clicking on the ‘OF’ button in the window or when changing the value of the entry. Square brackets are not supported. menu_update - It allows to update the menus.Values can be yes of no. It is necessary to define a field, as follow s, ficldtype - Itcreates a box in the user interface in order to introduce a text. It can be: longtext - A text box is created editable - Its a boolean value as 2 1 or 0 that indicates if the entry could be changed or not. If itis activated (1) the entry may not be changed, no insertion cursor will be displayed and the contents will nt be selectable. uunit_magnitude - Physical quantity (ie. L, for Length). For more information about this attribute, see the sectionDescription of the units units - Unit of the physical quantity (i. units (General_Data'/value[@n='analysis_type']" att="menu_update” 1m). For more information about this attribute, see the sectionDescription of the function - Contains a Tel command, which is executed when is called, It permits to create or edit a function for a determined entry function_func - Perrrits to define a TCL function, values_check - It allow s to handle a Tel function, by means of square brackets, min_two_pnits - It is a boolean value as a1 or 0 and indicates that tvo points or more are required in a linear interpolation. uunit_definition - The fields used to choose the default units in the GUI are special, They contain the attribute called unit_definition= "magnitude" being magnitude the name 'n' to be used in that field. It is important to note that these bind of fields does not contain dependencies. Mass! wnit_definieion='M'/> Force! unit_definieion='F'/> unit_mesh_definition - The field used to choose the mesh unit is special, It has the attribute "and it does not contain any "v" attribute or dependencies. units_system_definition - The field used to choose the units system is special. It has the attribute ‘does not contain any "v" attribute, and it contains a unique dependency related to the units “Gdependencies nede="//“[@unis_definivion of @init nesh definivion='1']" acei='change_wnits_system* wen /> Civalue> 4.3.1.3 condition < It contains some inputs with values and can be applied to groups. For each applied group, a dependent set of values will be created that belong to that group, for this condition. |A group is a category that brings together selected entities (points, lines, surfaces and/or volumes) with identical properties. I should be noted that any entity can belong to more than one group (unlike the concept of layer, where any entity cannot belong to more than one layer) It can contain the follow ng fields: , , acondition a Button ‘Select’ enables to create a group and choose entities into it. ov, ovi, i=1,2 - Indicates to which entity types can a ‘condition’ be applied. Can be one of several of the following values: point, line, surface, surface_as_volume, volume, ov_default - Indicates the default entity type which a ‘condition’ can be applied. Can be one of the following values: point, line, surface, surface_as_volume, volume. ovm, ovmi, i=1,2 - Indicates to which entity can a condition’ be applied, It can be element, node, face_element or void. state - Specifies one of two states for the field: normal, or hidden. Note that hidden field can be used for storing hidden values, that you de not want to show in the user interface, It also permits to handle a Tel function, by means of square brackets. 4.3.1.3.1 symbol Every condition can have a symbol, that will be drawn when the user selects Draw symbols in the contextual menu that ‘appears on user interactions such as right-mouse click operation. ‘The symbol is defined by a field inside the condition, The available XML parameters are: © proci Includes the name of @ TCL proc to be defined in the TCL files of the problemtypes. In that prac, OpenGL is used to make the real drawing. ‘The procedure must return the id of a OpenGL draw ing list (created by GiD_OpenGL draw -gent ists 1), or a dict with some required keys depending on the orientation attribute value * orientation: can be global, local, localLA, section, shell_thickness, loads. * global means that the symbol defined in the proc will be drav with its axes corresponding to that of the global axes of the model. * local means that the symbol will be dravin related to a local axes systern dependent on the entity, For lines, this local axes system will have x’ axe parallel to the line, For surfaces, the 2’ axe will be parallel to the surface normal * local A is similar to local * section is similar to local, used to draw bar section profiles + shell_s In this case the proc must return a dict Tel object with a key named thickness witht the value of the thickness associated to the surface. kness to draw the surface with a thickness, * Toads to represent loads. In this case the proc must return a dict Tel object with @ key named load_type with possible values global, global projected, local “There are Tel predefined procedures to facilitate dran’ing with OpenGL: ‘To automatically import a GiD mech fleta be drawn with OpenGL. ~ ‘The filename to be read must be a GiD ASCII mesh of lines, triangles and quadrilaterals (with as feu: elements as as possible), This mesh could be exported from the menu Files->Export->GiD mech. The pracedure read the mesh and invoke 64_openct ara commands, ‘The mesh rust represent a normalized shape, centered at the origin and contained in a box of size 4 for every of its dimensions (a 2x2x2 cube) = gid_groups_conds:: arau_symbol_image Cimage> ‘To automatically import in image file to be drawn with OpenGL. The image must use some valid image format (png, if. 3p.) ‘The values_list argument is currently not used. + gid_groups_conds:: draw_symbol_cexe cvalues_Lise> To automatically print a text with OpenGL. ‘The values_list argument is currently not used. Note: The package gid_drav_openg| also contains some predefined interesting procedures. Example: wane eo apply'/>symbol 12 (mana: DrawSynbolWeigch" orientation "global "/> ‘And its Tel drawing procedure, assuring that the mesh file named weight problemtype: moh is located in the symbols folder or the proc (nance: -DeausyabolWeigch {values List > ¢ TE ( Hlindo exiata ~epengl_draw List(weighe)] ) ( Zee opengl dea 1ise (weight) (64D_opencL draw ~genl ists 1 Gin_Gpencu deaw cneel ne # opengl draw lise (weighs) compile pet filenane mesh [file join [Cnas2e -GetDiz] symbols weighe gid, groups conds: inpost gid mesh an_openGl #£ilename_nesh black blue > see weigeh_and.unie [Izange [lindex fvalues_1ise (1search ~index 0 fvalues_lise Weighel] 121 See weigh [1index fweigeh and unit 0] dee scale (expr (Gweigeh"0-1)1 dee transform matrix [1ise Fecale 0.00 0 facale 0000 fecate 0.000 11 See Lise sa (65D openGh dea ~genl ists 11 GiD_openGL draw Thewl ise $list sd compile GsD_opench draw “pushnaczix ~malematrie Feransform matzix GiD_opencL draw -eall ¢_opengl_draw1ise(weight) secusn Sine id > 4.3.1.4 blockdata < Represents a set of properties with some kind of relationship. A ‘blockdata' field can copy itself, to duplicate and create several sets, It can contain the following fields: , , , , , and other in - Name used to reference the field, especially hen writing the .dat fle, ame - Label that will be visualized by the user. It can be translated Sequence - It allow sa ‘blockdata' field to by duplicated and copied by the user in order to create several sets. Like several load cases with its ‘value’ and ‘condition’ included. If it has the ‘sequence’ parameter activated, itis possible for the user to create consecutive repetitions of the full block data in order to represent, for example, leadcases with all its conditions inside. sequence_type - It can be! any ~ The lst can be void (this is the default) rnon_void_disabled - At least there needs to be one element, It can be disabled. rnon_void_deactivated - At least there needs to be one element, It can be deactivated, editable_name - can be void " or ‘unique’. The ‘unique! means that itis not possible to use the same name (‘pn field), For two different ‘sequence! ‘blockdata’ morebutton - It is a boolean value az a1 of 0 to show a ‘More.’ button in fields of type ‘blockdata’. It ic activated by default. For more information about this attribute, see the section Import export materials can_delete_last_item - A single blockdata could be deleted. before_update_proc - It allows to call a TCL procedure, when choosing this field in data tree, Square brackets are not supported. update_proc - It calls 2 TCL procedure, when clicking on the ‘Ok’ button in the window. Square brackets are not supported. icon - If alloys to put an image in .png format in the data tree, The image should be stored inside the images folder of the problem type, help - It displays a pop-up wrindow of help information related to the task the user is performing. state - Specifies one of tio states for the field: normal, or hidden. Note that hidden field can be used for storing hidden values, that you de not want to show in the user interface, It also permits to handle a Tel function, by means of square brackets. allow_import - It is a boolean value ar a 1 or 0 that allows to add the ‘Import/export material’ item in the contextual menu for a specific ‘blockdata' field. tis deactivated by default. For more information about this attribute, see the section Import export materialsedit_command 13 4.3.1.5 edit_command < It adds 2 button in the window that allows to call a TCL procedure when necessary. The parameters are as follows, in = Name used to reference the field, especially hen writing the .dat fle, pn = Label that will be visualized by the user. It can be translated. icon - It alloys to put an image in .png format in the data tree, The image should be stored inside the images folder of the problem type, proc - Perrrits to define 2 TCL proc. The code will receive an implicit argument with name ‘domNode' that represents the TDOM node in the calling field context. Square brackets are not necessary in edit_command field help - It displays a pop-up wrindow of help information related to the task the user is performing. 4.3.1.6 dependencies When a field of type ‘value! changes its value 'v', the field allows to force a change in other values. The parameters are as follows, node - It is the xpath expression to the node that should be updated. value - Field allow s to define a condition to execute a dependence. att, atti, =1,2 - Indicates to which attributes of a node affect a change in one value, wyvi #=1,2 ~ Indicates the new value for atti, =1,2. It can be normal, hidden or disabled, default - Default value for the condition. It permits to execute a dependence. actualize - This only updates a spacified field in data tree, Note that only this specified field will be refreshed in the user interface, and not the whole data tree, itis a boolean value as a 1 or O that indicates if is activated or deactivated actualize_tree - Itupdates the information in the whole data tree, and automatically refresh data shown in the user interface. It is a boolean value as a 1 of 0 that indicates ft is activated or deactivated. Ifthe data source is changed, such 1s new fields have been added or data values and field have been modified, all the user interface will reflact those changes. Furthermore, all the TCL procedures defined in the data tree will be called and the whole data tree will be refreshed. “Therefore, this instruction must be carried out only when necessary. Example: when the user select ‘No! in the combo 'show_w eigth’ the itern value with name whan select "Yas! is show ed. igth’ will be hidden, and Note the use of a relative xpath nede="../value(@r='weight']" to specify the xml node to be changed by the dependency’ ‘“aependencies value: weighe'] Ve inozmal '/> Saependencies value” Jreaive (n= weight] ‘niaden'/> wane eo apply"/> 4.3.4.7 groups Initial groups field. tis aly ays an empty field in the .sp file 4.3.1.8 groups_types Represents the types of groups. It can contain the following fields: The parameters are as follows, editable - Its a boolean value as 2 1 or 0 that indicates if the entry could be changed or not. If itis activated (1) the entry may not be changed. 4.3.1.8.1 group_type Main configuration field of the group types. pn = Label that will be visualized by the user. It can be translated.group_type “4 default - itis a boolean value ar a 1 or 0 that indicates the default group type. auto_from_be - It is a boolean value as a 1 or 0 that indicates that the group type is a boundary condition (be). Example: 4.3.1.9 units Main unit field. It can contain the follow ing fields: 4.3.1.9.1 unit_magnitude - It is necessary to add a field of type unit_magnitude to change the priority ‘p' for a given unit, together with the values of the priorities, for each ‘unit ' considered. It can contain the following fields: The parameters are as follows, in - Name used to reference the field, especially when writing the .dat fle, pn - Label that will be visualized by the user. It can be translated. default - Default unit for a specific magnitude, ST_base -Unit based in the international system units for a specific magnitude. active - It is the default unit shown in the user interface, for a spacific magnitude, 43.1.9.1.1 unit in - Name used to reference the field, especially when writing the .dat fle, pn = Label that will be visualized by the user. It can be translated. P = Priority of the unit, itis regarded as more important than others units, The possible values for 'p' are 2, 2 and 3. For more information about this attribute, see the sactionDescription of the units factor - The conversion factor used to multiply a quantity »'hen converting from one system of units to another. For more information about this atribute, see the sectionDescription of the units help - To make easier to the user to identify the unit units_system - There are two systems used to define units, the possible values ar SI International system imperial - Imperial system addend - Conversion number, relation bet een two units. Example: In order to go from Celsius to Kelvin, 273.15 is added to the temperature in Celsius, Therefore, addend = 273.15. printable_name - Name used to print the unit. For instance, ‘oC’ could be the print name of °C. 4.3.1.10 function - Main function field, srhich contains a function variable field called , It permits to create or edit a function defined by points for a determined field. 2-9, for a property variable with the temperature. It can contain the following fields: 4.3.1.10.1 functionVariable - It allow s to define the default values of a function defined by xy points. The parameters are as follow s, in - Name used to reference the field, especially when writing the .dat fle, pn = Label that will be visualized by the user. It can be translated. ‘variable - Name of the variable shown in the GUL units - Its value is the default unit shown in the GUI, which could be changed, #f desired, Example:functionVariable 15 value netdens" pae'Density" min_eve_pnts="l" help="Density of Steel" unit_magnitude="W/L“2" sniesitkg/n°2" function" [density function)” function func" veHLO) eprecs>, ‘cprec n=!densicy function’ azgst!args!> erteDarat MyDensivyFunceion Gdonede Fars a> In this example the proc density_function referenced by the function’ attribute is implemented in the xml .spd file but itis very simple and only invokes anether procedure named MyDensityFunction adding some arguments. The body of the tel procedure could be implemented separatelly in a.tl file (sourced in the problemtype), this facilitate its edition and debug. proc MyDensityFunction ( donilede args} ( set result [join [list scalar [list incezpelatoz func = = Templ] +] secur Szemuie > “The proc referenced by the function’ must return as value something like this: where seataz is a keyword, interpolator_func is the same name used in in the *.spd file can be used to change some defaults or to add specialized units, which in principle are not supported, The structure and contents of this subtree requires to have the format ar further detailed in this document. The following attributes are available: * p= Priority of the unit, itis regarded as more important than others units, The possible values for ‘p' are 2, 2 and 3, as follow s, 1 It gives maximum priority, and therefore a unit with p="2" is the default unit in the GUL 2A unit mith p="2" is alu ays shown in the corrbobox of below to facilitate the selection of the most used units. 3- It gives low est priority, and therefore a unit with p in the combobox of below , which enables the user to choose the unit from a table. could only be chosen when clicking on ‘More units.’ option bs 1 Move > tite 1 Options fy Rogan 1o me arem(S) te pound 04539057 penal 5s oy Brogan ter ine sem (5) eaten 605 ne aes) ig Stage co) Int aptem (3) ap seagem oat ine em (3) 3 eaten tel5 intone (3) $3 femtagare seit ineaysem (3) @ * factor - The conversion factor used to multiply a quantity when converting from one system of units to another. It is the mathematical tool for converting beby een units of measurement [1 un#t=factor*unit(SI)]. Exarrple: Imm=10e- + help - To make easier to the user to identify the unit, Example of field: Species concentration and reference variable are not supported and therefore, both magnitudes are defined in the *.spd file, as follows, 10.001" helpriper-one-thowsand"/> reppes"/> conic iparto-perwill ion" p ‘parta-percmill fon'/> sparta-per-bill ion"/> sneshendeed"/> sne-thowsand"/> Units system definition ‘The field used to choose the units system is special. thas the attribute units_syster_definition="1", it does nat containUnits v7 any "v" attribute, and it contains a unique dependency related to the units fields. ‘The field used to choose the mash unit is also special. It has the attribute unit_mesh_definition="1", and it does not attribute or dependencies contain any ‘The fields used to choose the default units in the GUI are also special, They contain the attribute called Lnit_defiition="magnituda” being magnitude the name 'n' to be used in that field, It is important to note that these kind of fields does not contain dependencies Here's an example of node type “container” in the .spd file, which allows to choose the geometry units and the general Units, as follows, sexy units" wuit_nesh definieion="" iconstunies-16"/> Caependencies node="//*{unit_definicion oz Gunit_nesh_definieio change wnits_systen® vI="(@r)"/> Example of window to spect the International and Imperial systems ‘There are to primary systems used to define units: the international and imperial systems, as seen below. The international system of units is the modern standardized form of the metric system, It sets standard measurements and conversions, and is the mast commonly and universally accepted system of units. The imperial system, also known as Britich Imperial, is the system of units first defined in the British Weights and Measures Act of 1924, which was later refined and reduced, ‘The fields of type can contain the attribute called units_system, as follow s, + unite_system - There are tro systems used to define units, the possible values are: SI - International system imperial - Imperial systern Defining magnitudes and unitsUnits 18 “The attributes involved in any field of the .spd fle are ‘unit_magnitude! and ‘units. + unit_magnitude: Its value relates to the name 'n! used to reference the unit field. Please see the table below for a complete lst ofall the names available. © units: Its value is the defauit unit chown in the GUI, which could be changed, f desired. Some functions are useful for writing data with units defined into the calculation file, For more information about this issue, see the section called Writing the input file for calculation. Example: Note: For instance, itis convenient to change magnitudes like unit_magnitude="F/L“2" by unit_magnitude=' “The table below gives a summary of the names used forall units available, ee ult Length L m Mass ™ kg Time T . Temperature Temp, K Frequency Frequency He Force F " Pressure P Pa Energy Energy 3 Pow er Pow er w Angle Angle rad Solid_angle Solid_angle * Velocity Velocity m/s Acceleration Acceleration mis-2 Area Area m2 Volume Volurne m3 Density Density kglme3 Electric current Electric_current ‘Amount of substance Amount_of_substance mol Luminous intensity Luminous_intensity cd Electric charge Electric_charge c Electric potential Flectric_potential v Capacitance Capacitance F Electric resistance Electric_resistance > Electric conductance Electrie_conductance s Magnetic flux Magnetic_flux we Magnetic flux density Magnetic_flux_density T Inductance Inductance 4 Delta phi DeltaPhi ag Delta temperature DeltaTemp. ak Luminous flux Luminous flux Im. tlurninance Ilurninance x KinematicViscosity KinematicViscosity m/s Viscosity Viscosity Pats Permeability Permeability m2 “The magnitudes available to be used ith the problem type in XML format are also listed below “To change the priority 'p' for a given unit, itis necessary to add a field of type ‘unit_magritude’ in the node of the ‘spd file, together with the values of the priorities, for each ‘unit ' considered. Here is shown an example of node in the -spd file, where kl and MPa will be the units by default for the force and pressure respectively:Units 19 “The default magnitudes and conversion factors could be seen at the file 2¢#ipt=\ custonl ib\ custonb ib\wnits_sml 4.5 Main procedures PROBLEMTYPE ‘CUSTOMLIB'>Main procedures “The main procedures available to be used in the TCL files, are listed belo * gid_groups_conds::actualize_conditions_window ‘This procedure updates the information of the whole data tree, and automatically refresh data shown in the user Interface. If the data source is changed, such as nen fields have been added or data values and field have been. ‘modified, all the user interface will reflect those changes. Furthermore, all the TCL procedures defined in the data tree will be called and the whole data tree vill be refreshed, Note that this instruction must be carried out only when necessary. Ithas no arguments. * gid_groups_conds::begin_problemtype spd_file defaults fle " ‘This procedure allows to load the problem type and should be defined in the InitGIDProject procedure. The arguments are the following} spd fle - The directory of the main configuration file (.sp4)- defaults file - The directory of the preferences file. Ifthe directory of the preferences file does not already exist, it is created. * gid_groups_conds::SetProgramitame program_name ‘This procedure stores the program name in the preferences file and should be defined in the InitIDProject procedure ‘The argument is the follon ing} program_name - Name of the program. * gid_groups_conds:1end_problemtype defaults_file ‘This procedure will be called when the project is about to be closed, in the EndGlDProject procedure, It receives az argument: defaults_file - The directory of the preferences file, Ifthe directory of the preferences file does not already exist, it is created. * gid_groups_conds::give_data_version ‘This function returns the version number of the problem type, + gid_groups_conds::save_spd file spd file ‘This procedure saves the .spd file and should be defined in the SaveGIDProject procedure, Therefore, i will be called when the currently opened file is saved to disk. It receives az argument spd file: path of the file being saved * gid_groups_conds:import_export_materials widget xpath ‘This procedure allow s to open the ‘Import/export materials! window. It receives as arguments: widget - Parent widget: xpath - It is thexpath expression to the field ‘container’ of materials. 4.6 Writing the input file for calculation “The procedure called GID_WriteCalculationfile permits to create the output description to the file of analysis. GiD_WriteCalculationFile init| end |puts [coordinates all_connectivities |connectivities|nodes elements |has_ele ments?-elemtype ? ?-localaxes "2 ?-elements_faces _all|elements|faces? 2-number_ranges ? ?-unique? ?-multiple? 2-all_entities? ?-do_subst? ?-sorted? ?-count? 2-retum? 2-print_faces_conecs ? -connec_ordering? corner_face_corner_face Writing the input file for calculation 20 + GiD_WriteCalculationFile init ?-encoding extemal utf-#2 ‘To open for writting the calculation file (external default encoding). Before to print any information to the file it must be opened with this command. Exarle: GiD_NriveCaleulationFile init (c:/temp/my output ast) + GiD_WriteCalculationfile end To close the calculation file Exarle: * GiD_WriteCalculationFile puts ?-nonewline? Print the string in the calculation file and a carriage return + -nonewline avoid the carriage return, Exarele: * GiD_WriteCalculationFile coordinates ?-count? ?-retum? ?-factor ? ‘This command rust be used to print all nodes of the mesh, It prints for each node. must be a "C-like’ format for an integer an three doubles. ‘Are only printed the values with supplied format, e.g. if the format is "sed 96°" only the node number and its x will be printed. If 2 %.0s is specified then the corresponding value is not printed (trick to avoid print some values) + IF -count is specified then only return the number of entities, without print + If return is specified then return the string, without print + If factor is set the the coordinates will be scaled by the (that must be a real number, 1.0 by default), It i used ald to write the mesh based on the declared mesh unit and the current reference length unit. Example: see mumcoordinates [6iD_WriveCalculationFile coordinates “come "*] ;ffwith “cone the fommat GiD_WeiceCalculacionFile pues "mum coordinates: Fnum coordinates” see mesh unit [yid_groups_conds: :give_mesh_wnit] ict mesh factor [1index (gid groups_conds:7give wmit_facter L fmesh_unit] 0] Gip_NrieCalculationFile coordinates “factor fresh factor "Wd tg tg 8g) * GiD_WriteCalculationFile all_connectivities ?-elemtype ? ?-count? ?-return? ?-connec_ordering comers_faces|comer_face_comer_face? ‘This command must be used to print all elements of the mesh, It prints the element number and its connectivities for teach element of type of the mesh (sll types if -elemtype is not set) < must be an integer for the element id and as much integers ar connectivities to be printed. + can be: Linear|Triangle| Quadrilateral |Tetrahedra | Hexahedral Prism | Point| Pyramid | Sphere| Ci de + If -count is specified then only return the number of entities, without print. +f -returm is specified then return the corlete string, without print * for quadratic elements the order of nodes could be specified with -connec_ordering corners_faces|comer_face_comer_face by default the order is corners_faces (First are printed the corners and then the quadratic nodes) Exarele: * GiD_WriteCalculationFile connectivities |nodes|elements|has_elements ?-elemtype ? ?-localaxes ? ?-elements_faces all | elements | faces? ?-number_ranges ? ?-count? f repeated? ?-multiple? 2-all_entities? ?-print_faces_conecs? ?-sorted? ?-do_subst? 2ounique? ?-error_i ?-connec_ordering? ?-retum? ‘To get entities information related to groups: connectivities, nodes, elements of the group names specified in the dictionaryWriting the input file for calculation 21 is 2 dictionary (list of pairs key value), with key=group and value=format for connectivities it prints the element number and its connectivities for nedes it prints the node number for elements it prints the element number + -elemtype can be: Linear! Triangle| Quadrilateral |Tetrahedra|Hexahedra| Prism| Point] Pyramid] Sphere| Circle + & Jocalaxes can be set in order to write local coordinate axes, where is a dictionary (list of pairs key-value), with key equal to LA name and value equal to a format, which could be for instance ‘{9ed[euler_angles matris/matrixT "Seg%q%a%a%g%q%eG%a%G"T}. The euler_angles is a function and matrix or matrix its argument in order to remark that its rotation matrix or its transposed matrix should be written. A format equal to" should be specified at the end of the GiD_WriteCalculationfile function. The EAmat function permits to have more control about the rotation matrix related to the euler angles using for instance the format {(9ed[EAmat 1 1][EAMmat 2 1][EAmat 3 1][EAmst 1 2][EAmst 2 2I[EAmat 3 2][EAmat 1 3][EAmat 2 3][EAmat 3 3D} to write the directions of the local coordinate systems. The three angles giving the rotation matrix are called Euler angles: ‘A -do_subst flag should be required in order to replace the previous formulas in the GiD_WriteCalculationFile. is a dictionary (list of pairs key value) of local axes, with key=LA_name and value=format + Acelements_faces can be set to specify any type (all), body elements (elements) or face elements (faces). ‘Therefore, it considers element connectivities or face elements connectivities A cunique can be set to specify thet each entity should be written once, + -multiple can be used in order to consider a list of variables containing @ dictionary value (list of pairs key value). It is known that "dict set dictionary key valve” command takes the name of a variable containing a dictionary value and places an updated dictionary value in that variable, containing a mapping from the given key to the given value. It should be noted that when multiple keys are present, this operation creates or updates 1a chain of nested dictionaries and the GiD_WriteCalculationFile function requires -multiple flag. + A -all_entities can be set to specify that all entities should be considered. + A -do_subst can be set to replace formulas, + A -number_ranges can be set to group entities using a groups dictionary, + is a dictionary of number of ranges + A-sorted can be set to apply a string ordering. + A-print_faces_conecs can be set to print face element connectivities. A ~elements faces of face elements should be specified when 2 -print_faces_conecs is used. + A. -connec_ordering can be set to specify @ connectivities ordering as corner-middle _edge-comner (comer_face_comer_face), default is first all corner nodes (comners_faces) + IF -count is specified then only the number of entities is returned, without print. + If return is specified then the complete string is returned, without print. Example: to print the id and connectivities of the triangle elements of the groups named $group_a or $group_b see format_by_group [dice create fgroup_a "AD 44 ~ td 4d 4d" Ggroup_b "BR td td 8a ta") GiD_NriveCalcalacionFile connectivities “elemtype Triangle #fozmae_by_gzoup Example: to print the node id of the nodes belonging to $group_name and a text with the group name see format_by_group [dice create fyroup_nane "$d of group $group_nam Gid_NriveCalculavionTile nodes fEermat_ by group Functions to convert between different unit types ‘There are a couple of functions that are essential hen writing the input file for the calculation. These functions permit the treatment of the units, and facilitates the conversion from one measurement to anather. They are the follow ing + gid_groups_conds::give_mesh_unit ‘This function provides the mesh unit, + gid_groups_conds::set_mesh_unit unit “This function imposes a mesh unit, where the argument is as follows Unit - A text string, denoting the unit that you want to apply as mesh unit © gid_groups_conds::convert_value_to nodeObject to_unit ‘This function converts the value of a nodeObject from the current unit for the original number to another unit, where the arguments are as follows:Writing the input file for calculation 22 nodeObject - DOM node object chosen, to_unit - A text string, denoting the unit that you want to convert the original number to. © gid_groups_conds::convert_value_to_active nodeObject ‘This function converts the value of a nedeObject from the current unit type to the general active unit selected in the GUL The argument is as follons: nodeObject - DOM node object chosen, © gid_groups_conds::convert_unit_value magnitude value unit_frorn to_unit This function converts a number from one unit type to another unit type, for the same magnitude. It receives as arguments: ‘magnitude - Unit definition, itis the name 'n’ of the physical quantity (eg. "L" for Length) value - The number to be converted, unit_from ~ A text string, denoting the unit fr the original number ‘to_unit - A text string, denoting the unit that you want to convert the original number to. + gid_groups_conds::convert_value_to_printable_unit nodeObject ‘his function returns a text string, denoting the current unit of the node. It receives as argument: nodeObject - DOM node object chosen, * gid_groups_conds::give_unit_ factor magnitude unit ‘This function returns the conversion factor for the unit given. The arguments are as follows ‘magnitude ~ Unit definition, itis the name 'n’ of the physical quantity (eg. "L" fer Length) unit - A text string, denoting the unit chosen to obtain the conversion Factor, + b_write_cale_file::apply_unit_ factor magnitude value to_unit ‘his function returns the conversion factor, the numerical factor used to multiply a quantity when converting from one system of units to another, It is the mathematical tool for converting between units of measurement [1 Unit=factor*unit(S1)], Example: 1mm=10e-3 m The arguments are as follows: ‘magnitude ~ Unit definition, itis the name 'n’ of the physical quantity (eg. "L" for Length) value - The number to be converted, ‘to_unit ~ A text string, denoting the unit that you want to convert the original number to. * gid_groups_conds::convert_v_to_default value magnitude unit_from ‘This function converts a number from one unit type to the unit type by default, for the same magnitude, It receives az arguments value - The number to be converted, ‘magnitude - Unit definition, itis the name 'n' of the physical quantity (eg unit_from ~ A text string, denoting the unit fer the original number for Length) + gid_groups_conds::give_active_units_system This function returns a string list, where the first iter is the units system, + Gid_groups_conds::give_active_unit magnitude “This function returns the active unit for a given magnitude. It receives as argument: ‘magnitude - Unit definition, itis the name 'n’ of the physical quantity (eg. "L’ for Length) 4.7 User preferences User preferences of the problemtype will be automtically saved/read to/from disk in a xml file named ‘$problem_typefversion.ini, located in the same user folder as the GiD preferences, “To set/get user preferences variables these procedures must be used. + gid_groups_conds:iget_preference ‘This function returns the value of a preference, or the default value if the preference does nat already exist, It receives 2s arguments: name - Name of the preference value - Default value J groups_conds::set_preference User preferences 23 ‘This function imposes the value of a preference, It receives as arguments: name - Name of the preference value - Default value Example: get or set a user variable named 'verbosity_level’, with default value= set level (gid_groups_conds: -get_prefezence verbosity level 01 gid_groups_conds:: set preference verbosity level 2 4.8 Import export materials, Parameter called allow_import in fields of type allows to add the ‘Import/export materiale’ item in the contextual menu for a specific ‘blockdata' field A material is composed by a set of material properties, which can be applied to geometry entities, Import/export tool allows to handle material properties easily. This tool is located inside the right mouse menu when a particular material of a materials collection is selected in the data tree and allow_import parameter is activated, + In order to activate the Import/ export materials tool, itis necessary to call n="materials" to the global container in the spd, Moreover, although the intermediate containers could be defined using any attribute n, each final material blockdata has to be called n="material” © The “Import/export materials” window contains two different material data trees. At the left side there is the local materials list associated to the current model. At the right side there is 2 material data tree list, which could be imported or exported depending on the user interests. It is possible to import/export materials in four different w ays * Global databace active * Global databace inactive + Import from a file + Export to afi ‘The global database active is the database shovin in the data tree located at the left side of the GiD window when a new model is created, ‘The global database inactive is an internal database which does not affect the default data tree for nen models, It could be used to store odd materials in order to import them for a particular model The global database active also allows to import the original defauit materials clicking on the button located just at the Fight side of the "Import/export to" combo-box, which facilitates to recover easily the original input data for materials. It is also possible to import or export selected materials from particular XML-files without modifying the global database, It should be noted that the creation of nen materials can be done directly using the right mouse menu in the import/export materials window 4.9 About CustomLib Cirne's copyrighted CustomLib is developed between CIMNE and Compass Ingenieria y Sistemas, and it is the library included in GiD for creating advanced customized problerrtypes, ive. adaptations to third-party simulation codes or external programs. CustomLib terms of use are the same as the GiD ones. Compass offers the possibility of implementing advanced customizations of GiD, based on custornLib, adapted to the specific need of every spacific client. For more information about this service, please visit \/»\v.compassis.com.About CustomLib 24 © compass Ingenieria y Seen http://w w w.compassis.com info@compassis.com 4.10 CustomLIB extras For using this extra functionality, just activate the Custonl bAucomaeic field in the [RICHIE “paq Sor load it manually by requiring the package custom! Sh_exezar ‘The extra content on this package is © New fields added to the spd file 4.10.1 SPD_fields t's used to join diferent parts of the spd file. It must contain the follow ing attributes: 1 relative path, from the problemtype folder It can contain the following attributes: specifies if the part must be added in the final + active: Example: cimelude path=tenl /materials snl "/> 4.10.2 Extra functions “The main procedures available to be used in the TCL files, are listed below. All the usages and examples can be found on the 'cmas2d_customlib' problemtype. © customlibr:Pracessincludes directory ‘This procedure parses the active include nodes of the spd file, and replaces them for the node found in the path files. * customlibs PracessincludesRecurse filename bazedit This procedure parses the active include nodes of the specified file, and replaces them for the node found in the path files, Basediris the directory where the file specified by the path field is, + customlibs initWriteFile filename (Open the fle for nritting + customlibr:éndWriterile + custornlibs initMaterialslist_of_condition_names ‘The list_of_condition_names is the list of these conditions were we can find a material, so we can consider it as "used, asigning it a MID (Material Identifier) for further queries. + custornlbi:Writestring str Writes the content of str in the opened file + customnlbs: WriteConnectvities list_of_condition_names parameters Utlity to print elements and connectivities In the spd file, we can define condition tags to assign properties to a GiD group. The list_of_condition_names is the list of these conditions whose groups’ elements must be printed. parameters is a list of lists of 3 words, and defines the format and the information that we want to print. The first Word is al ays a format. The second w ord can be “element”, "material", "property" or string’, "element" is set to write clement information. "material" is set to print any material property. "string" is set to print a string. The third word depends on the second one. IF it's "element", the third can be: “id” or "connectivities". If it's “material”, the third one can be "MID", "Density" or any material property according to GetMaterials function. Obviously, to use ‘material’ data, ‘a material must be definad in the condition, Valid examples:Extra functions 25 + crnnoa’ + cena’ + cena’ + Coxaoa® “nacesiat (vio naeeriat 2a") (osioa" sproperey’ (vag ssering™ Exarle: see List_of condition panes (Lise "Shell s"] dee paraneers (Lise ("10a" “elemene™ id") ("¥204" “wrD) 1 cusconl ib: UriveConnectivicies $1ist_of condition names Sparaneters Jenene" “connectivicies") ("810a" ‘maverial™ # These instructions prine the following text = customlibr: Writeltodes lit_of_condition_names parameters lags? Uslity to print the nodes of the groups of the conditions specified at list_of_condition_names, and the infermation asigned to them. Exarle: set ist_of condition panes [Lise “Pine Weight") dee paranecers [Lise ('¥a" Yelemene” 'id") (412. Se" property” "Weighe"] Cuscoml ib: Wrivelodes flist_ef condition names Sparanctezs # cwepue + custornlb::GettlumberOfodes list_of_concition_names flags? Uslity to get the number of nodes of the groups of the conditions specified at list_of_condition_names. + customlibs: WiriteCoordinates formats Writes the coordinates of the nodes of the model. # cwepue: # cwepue: + custornlib::GetMaterials ?state? This procedure returns a nested dict, where the first kay is the name of 2 material, the second key is the name of the property state can be ‘used’, to return only the used materials, or ‘all to return all the materials. Example: set mat_dict [custornlib::GetMaterials used] set aluminium [dict get $mat_dict "Aluminiur") set density [dict get aluminium "Density"] + custornlb::GetMaterials 2otate? This procedure returns a nested dict, where the first kay is the name of 2 material, the second key is the name of the property state can be ‘used’, to return only the used materials, or ‘all to return all the materials. Exarle: see mat_dice (custom! ib: GetMaverials usedExtra functions 26 see aluminium (dict gee Snat_dice "ALuniniun") Bee densiey (dice gee Galuminiun "Densiey"] + custornlb::GettlumberOfMaterials 2state? state can be all’ of ‘used! Returns the number of materials in the database. If state is used, it returns the number of materials used in the model. © customlb::WriteMaterials parameters ?state? state can be''all’ of ‘used! Uslity to print the list of materials, and their properties defined in parameters. Exarele: set parameters (Lise (4d) MID") ("412_5e" Snaverial Casconl ib: Wrivelisterials Sparanccers used material Denssey")] # cwepue:5 EXECUTING AN EXTERNAL PROGRAM Once all the problem type files are finished (.end, .rnat, .prb, it directly from inside Gio. im, .bas files), you can run the solver. You may wish to run To do so, itis necessary to create the file Peoblem type_nane bat in the Problem Type directory. This must be a shell script that can contain any type of information and that will be different for every operating system, When yau select the Calculate option in GiD Preprocess this shell script is executed (see CALCULATE from Reference Manual). Because the .bat file will be different depending on the operating system, itis possible to create two files: one for Window = and another for Unix/Linux. The Windons file has to be called: problem type_nane.win.bat; the Unix/Linux file has to be called: problem eype_nane unix bat IEGID finds a -win.bat or -unix.bat file, the file Pe0bl em_eype_nane bat will be ignored. If 2 -b2° fle existe in the problem type directory when choosing Start in the calculations window, GiD will automatically write the analysis file inside the example directory assigning the name Project_nane. dat to this file (if there are more files, the names project_nane-1. dat ... are used), Next, this shell script will be executed, GiD will assign three arguments to this script + Ast argument: pr03¢ce_name (name of the current project): © and argument: «:\a\\c\pzo3ect_nane.gid (path of the current project); + ard argument: <:\2\b\<\pzobl en_eype_nane.gid (path of the problem type selected); ‘Among other utilities, this script can move of rename files and execute the process unti i finishes, Note 1: This file must have the executable flag set (see the UNIX command chmod +x) in UNIX systems. Note 2: GID sets as the current directory the model directory (example: ¢:\exanples\test1..gia) just before executing the .bat file. Therefore, the lines (cd #aizectozy) are not necessary in the scripts. Note 3: In UNIX platforms check you have installed the shell you are using in the .unix.bat script, there are more than one possibilities: bash, esh, tesh, “The first line of the script specify the shell to be used, for example Bi bin ob. Bi/binl bash In Window s platforms, the command.exe provided by GID is used instead the standard cmd.exe or command.com 5.1 Showing feedback when running the solver, ‘The information about what is displayed when Output view : is pressed is also given here. To determine what will be shown, the script must include a comment line in the following forrn: For Windows For Linux/Unix: B owepueFile: “fits” where "$i.log” means to display in that window a file whose name ist project_name.log. The name can also be an absolute name like output-dat. If this line is omitted, when you press Output view :, nothing will be displayed, 5.2 Commands accepted by the GID command.exe The keyu ords are as follos: * chasz (ca) + Rename (Ren, Move) ease (a)Commands accepted by the GiD command.exe 28 + Eeke (Gecko) Unknown instructions will be executed as from an external file, Not all the possible parameters and modifiers available in the operating system are implemented in the GiD executable command.exe, Note: At the moment, command.exe is only used in Window s operating systems as an alternative to command.com or cmd.exe. With the GID command.exe some of the disadvantages of Windows can be avoided (the limited length of parameters, temporary use of letters of virtual units that sometimes cannot be elirinated, flesting appearance of the console window , etc). If GID finds the file command.exe located next to gid.exe , it will be used to interpret the *.bat file of the problem type: ifthe file command.exe cannot be found, the *.bat file will be interpreted by the window = command.com. If conflicts appear by the use of some instruction still not implemented in the GID command.exe , itis possible to rename the corrmand.exe file, so that GiD does net find it, and the operating system cormand.com is used, % Returns the value of a variable, Senumber Soname% Parameters number “The number is the position (from 0 to 9) of one of the parameters w hich the *-bat fle receives. ‘The name of an environment variable, That variable has to be declared with the instruction "set Not GiD sends three parameters to the *.bat file: %1, 92, 963 961 is the name of the currant project (project_name) 962 is the path of the current project (c:\a\b\c\project_name.gid) 963 is path of the problem type (ct\a\b\c\problem_type_name.gid) For example, if GiD is installed in €:\gidwin, the "problemtyp inc:\temp (the project is a directory called ¢:\temp\test-gia with some files inside), parameters will have the following name is emas2a.gid and the project is test. gid, located cl\eenp\eere gid 82 ©: \gidwin\ prob] entypes\ cmas: Note: It is possible that the file and directory names of these parameters are in the short mode Windows format. So, parameter %3 would be: ¢:\ GIDUIIN\PROBLE~\cwAS2D. 61D Examples echo 42> s2\ az exe shift ‘The shift command changes the values of parameters 960 to %9 copying each parameter in the previous one, That is to say, value S61 is copied to %0, value %2 is copied to %1, etc. shift Parameter None, Not “The shift command can be used to create a batch program that accepts more than 10 parameters, If it specifiesCommands accepted by the GiD command.exe 29 more than 10 parameters in the command line, those that appear after tenth (%9) will move to parameter %9 one by one. Rem Rem is used to include comments in a *.bat file or in a configuration file, rem{comment] Parameter comment ‘Any character string, Note: Some comments are GiD commands. chair (ca) Changes to a different directory. chdir(drive:path] [-] cdfdrive:path] [..] Parameters Fative-path] Disk and path of the new directory. ba Goes back one directory. For example if you are within the C:\WINDOWS\COMMAND> directory this would take you to cAwmpows>. Note: When GiD calls the *.bat file, the path of the project is the current path, so itis not necessary to use ed 962 at the beginning of the *-bat file. Examples chdiz e:\emp cd Delete (Del, Erase) Command used to delete files permanently from the computer. delete[drive: path] filetlame [filetlame] Parameters Edrive: [path] filetlame [filetame] Parameters that specify the location and the name of the file that has to be erased from disk, Several file names can be given. Not Files will be eliminated although they have the hidden or read only flag. Use of wildcards is nat allow ed, For example del *.* is not valid. File names must be separated by spaces and if the path contains blank spaces, the path should be inside inverted commas (the short path without spaces can also be used). Examples delece 2\sa\ tile cat del C:\ewp\£a.dae Co \enp\ fb dae del "C:\Program files\eese Lexe" copy Copies one or more files to another location. copy source [+ source [+] destination Parameters source Specifies the file or files to be copied, destination Specifies the filename for the new file(s). “To append files, specify a single file for destination, but multiple files for source (using the filet + file2 + file3 Format) Not it File names must be separated by spaces. If the destination only contains the path but not the filename, the new name will If the destination file already exists, it will be overwritten without prometing whether or not you wish to overwriteCommands accepted by the GiD command.exe 30 be the same as the source filename. Examples copy fi-exe olen fem if dizectory e:\tmp exists, c:\emp\£l.txt will he created, if it dees not exist, file c:\emp will be Rename (Ren, Move) Used to rename files and directories from the original name to a new name, rename/drive:J[path] filellamet filellame2 Parameter [drive:][path] filel'amet Specifies the path and the name of the file hich is to be renamed. filel'ame? Specifies the new name file. Note: If the destination file already exists, it will be overwritten without prorreting whether or not you wish to overwrite it, Wildcards are nat accepted (*,?), s0 only one file can be renamed every time, Nate that you cannot specify a ne drive for your destination. A directory can be renamed in the same w ay as ifit was a file, Examples Rename "c:\Peogeam Files\fa.cxe" c:\emp\fa.cxe Rename c:\test.gid c:\test? gid Mlle (end) Allow s you to create your ov'n directories. micdir[drive:|pathmd [drive:]path Parameter drive: Specifies the drive where the new directory has to be created path Specifies the name and location of the new directory. The maximum length of the path is limited by the file system Not mkdir can be used to create a nen path with many new directories. Examples mediz e:\tm? pueaiz an\ar\aa set Displays, sets, or removes Window s environment variables. set variable=[string) Parameters variable Specifies the environment-variable name, string Specifies a series of characters to assign to the variable Note: The set command creates variables which can be used in the same way as the variables %0 to %9. Variables %0 to 969 can be assigned to new variables using the set command, To get the value of a variable, the variable has to be written inside tre % symbols. For example, if the environment-variable name is V1, its value is %6V1%, Variable names are not case-sensitive Examples Echo (@echo) Displays messages. echo [message]Commands accepted by the GiD command.exe 31. Parameters massage Specifies the text that will be displayed in the screen, Note: The message will not be visible because the console is not visible, since GID hides it-Therefore, this command is only useful the output is redirected to a file (using > or >>). The symbol > sends the text to a new file, and the symbol >> sends the text to afile ft already exists, The if and echo commands can be used in the same command line. Examples Echo tpacht >> one .exe 1 Wot Exist ¢2\¢1 post.xes Echo "Program Eailed" >> ¢2\¢L.ex= i Executes a conditional sentence. If the specified condition is true, the command which follows the condition will be executed; ifthe condition is false, the next line is ignored, * iffnot] exist fletame command + if [not] string! ==string2 command © iffnot] errorlevel number command Parameters not Spacifies that the command has to be executed only if the condition is false. exist file Returns true if file exists command Is the command that has to be executed i the condition returns true, string1==string2 Returns true if string and string2 are equal. It is possible to compare two strings, or variables (for example, %1). errorlevel number Returns true if the last program executed returned a code equal to or bigger than the number specified Note: Exist can also be used to check if a directory exists, Examples call Executes nev program. call[drive:]fpath] file [parameters] Parameter [dtiva:Ilpath] file Specifies the location and the name of the program that has to be executed parameters Parameters required by the program executed, Not ‘The program can be *.bat file, a *.exe file or a *.comfile. If the program does a recursive call, some condition has to be imposed to avoid an endless cul Examples Goto “The execution jumps to a line identified by a label. goto label Parameter label It specifies a line of the *.bat file where the execution will continue, That label must exist when the Goto command is executed, A label is aline of the *.bat file and starts mith (:). Goto is often used with the command if, in order to execute conditional operations. The Goto corrmand can be used with the label :E0F to make the execution jurrp to the end of the ‘bat file and finish, Not ‘The label can have more than eight characters and there cannot be spaces between them, The label name is not case-sensitiveCommands accepted by the GiD command.exe 32 Example Declares a label tlabelltame Parameter labelliame A string which identifies a line of the file, so that the Goto command can jump there, The label line will not be executed Note: The label can have more than eight characters and there cannot be spaces between them, The label name is not case-sensitive Examples Tye Displays the contents of text files type[drive:J[path] fileliame Parameters [dtiva:Ilpath] filetlame Specifies the location and the name of the file to be displayed. If the file name contains blank spaces it should be inside inverted commas ("file name"). Note: The text will not be visible because the console is not visible, since GID hides it Therefore, this command is only Useful if the output is redirected to a file (using > or >>). The symbol > sends the text to a new file, and the symbol >> sends the text to afile fit already exists. It is recommended to use the copy command instead of type. In general, the type command should net be used with binary files, Examples eype t2\tase > salar exe 5.3 Managing errors Aline of code like For Windows For Linux/UNIX B EecosPile: “fers included in the .bat file means that the given filename is the error file, At the end of the execution of the .bat file, if the errorfile does not exist or is zero, execution is considered to be successful, If not, an etror window appears and the contents of the error file are considered to be the error message, If this line exists, GiD will delete this file just before calculating to avoid errors with previous calculations. A comment line like B WaeningPile: “F1wen" included in the bat file means that the given filename is the waming file. This file stores the warnings that may appear during the execution of the -bat fle,Examples 5.4 Examples: 33 Here are two examples of easy scripts to do. One of them is for Unix/Linux machines and the other one is for MS-Dos or Window s + UNZX/Linux example: Bibi oh Dasenane = $2 aizectony = $2 PechlenDizectory = $2 # owepuerile: "flog" IT IS USED BY GiD B EeesPile. "flezs" 17 15 USED BY GiD im -£ "fhasenane post 243 "Probl enDixecvory/mprogran” “fhasenane! are "Phasenane result: + MS-D0S/Windows exampl em basenane=tl JUST INFORMATIVE rem dizectory=¥2 JUST INFORMATIVE sem ProblenDizectozy-2 JUST INFORMATIVE sem OuepucFile: Slog 71S USED BY GiD sem EnzosFile: tex: IT 15 USED BY GID S2\ayprogran 81PREPROCESS DATA FILES 3435 6 PREPROCESS DATA FILES 6.1 Geometry format: Modelname.geo DESCRIPTION OF THE FORMAT ‘There are two versions of the .geo GiD format: Binary (used by GiD by default) and ASCIL, This chapter describes the format of the geometry ASCII fie During the development of the program, the back ard compatibility has been tried to be guaranteed as much as possible, s0 that, in general, any GiD version is be able to read it (some very old version of GiD can ignore some neu entities) + The file "geo" is written using Export->SaveAsciProject, but by default the geometry will be saved in binary format In order to GiD to read the file, it should be placed inside a directory named "*.cid” Document natation: © By default all the variables are of type integer, the variables of type float will be written underlined, and those of type double with double underlined. (data types of the "C" language) + A carriage return is denoted for ‘The commas written to separate the variables should not be written in the fle, they only appear in this document to facilitate their reading, and the same applies for the white lines. “The file should contain the following fields, and in the described order dn enery for each meshing data (avoid if net exits) Mali entity (denoves end of mesh data) Mall entity (denoves end of geometric entities) Header RAMSAN-ASCII-gid-v7.6 (it is used to identify the file type and its version, in this case 7.6) Problem Type Problem type (variable of type string) IsQuadratic (0 for lineal elernents) (problem type name, UNKNOWN type for not loading none) Must Repair 0 (0 i itis not necessary to apply the "Repair" function after the reading, "Repait" corrects the value of some fields like the counter of the number of higher entities to those an entity is subordinated to) Layer Number of layer, Name (variable of type string), isfrozen (0 oF 1),ison (0 er 1), RGB_R, RGB_G, RGB_B (RGB color, values from 0 to 255) Null entity for end of entities) NoStructuredMeshData Entity code= -2, number 1D, NumOféntities (number of entities than point to it), elementtype, MustBeMashed (0 oF 2, default=0), size (edge element size), StructuredMeshData Entity Code= -2, number ID, NumOffntities, elementtype, MustBeMeshed, Size, StructuredWeightedMeshDataGeometry format: Modelname.geo 36 Entity Code= -3, number ID, NumOfEntities, elementtype, MustBeMeshed, Size (number of divisions), w eight (positive or negative value to a non uniform concentration of the elements) Where ElernType={Nolle=0, Linear=1, Triangle=2, Quadrilateral OnlyPoints=7} |» Tetrahedra=4, Hexahedr 1 Prism=6, Point Entity Code=1, number ID, label”, selection’, number of higher entities, conditions=0, materi data=0 xy 2 . number layer, mesh ‘The flag value label is only used by old GID versions (to set on/off the visualization of the entity label), current versions use only selection for both flags (frst bt for selection on/off and second bit for label on/off) Straight segment Entity Code=2, number GOES, labels, selection, number of higher entities, condition data=0 < CR> Number of intial point, number of final point , material=0, number layer, mesh fee Entity Code=3, number 1D, label, selection, number of higher entities, condition data=0, Number of initial point, number of final point, x center, y center, radius, intial angle, final angle ‘TransformationMatrix [0] [0]... TransformationMatrix [0] [3] ‘TransformationMatrix [3] [0]... TransformationMatrix [3] [3] “The transformation matrix maps the points from 2D to the final 30 location. Polyline Entity Code=4, number of 1D, label, selection, number of higher entities, conditions data=0, Number of initial point, number of final point, number of parts, length, UsePointsInMeshing=0, checknur sense[2] j.., sense[number parts] (gives the orientation of the sub line, possible values 0 or 4) length{2],...)ength{number parts] here the description for each one of then sub-curves is written, with the particularity that the number is set = -2 to all of them, to mark that they are not independent entities. number of layer, mesh NURBS curve Entity Code=11, number ID, label, selection, number of higher entities, conditions=0, mater data=0, , number layer, mesh Number of initial point, number of final point, number de polygon contrel points, degree, length xpoint{1], y point{2], z point{1] x point [number points], y point [nurrber points], z point [number points] Inots[2], ... » knots [number peints+degreeti], IsRational (0 or 4) Weight{2] ,.., Weight [number points ] (only if rational) “The length is ignored when reading, itis recalculated (it could be set to 0.0) Planar Surface Entity Code=5, number 1, label, selection, number of higher entities, condition data=0 0, material >» number layer, rmesh Number of boundary lines, number of curvel2], .. , number of curvefnumber of lines] (Note: if the curve is a part of a polyline it should be substituted “number of curvefi]" for "= number curvefi], relative position inside the poly-line”, Note the negative sign in the polyline number, and the position in the polyline will be Ot...) sense[2], ... sense[number of lines], (set the orientation of a segment, rust be 0 or 1) x center, y canter, 2 center, x normal, y normal, z normal, (vector normal to the plane)Geometry format: Modelname.geo 37. Coon Surfaces (defined by 4 sides, their interior is interpolated from the contour) Entity Code=6, number of ID, label, selection, number of higher entities, conditions data=0, number of layer, mesh Number of boundary lines=4, Number of curve[], ... , number of curve[4], (Note: if the curve is part of a polyline it should be substituted "number of curvefi]" for "= number of curve], relative location inside the polyline", note the negative sign in the polyline number, and the position in the polyline will be 0, sense[2]..., sense[4] (set the segment orientation, must be 0 or 1) xcenter, y canter, 2 center, ) x normal, y normal, z normal, (vector normal to the plane) NURES Surface Entity Code=14, number of 1D, label, selection, number of higher entities, concitions=0, material=0, number of layer, mesh data=0, Number of boundary lines Number of curve[], .«. , number of curve[4], sense[]..., sense[4] (set the segment orientation, must be 0 or 1) xcenter, y canter, z center, x normal, y normal, z normal, (vector normal to the plane) <> IsTrimmed, NU (number of control points in the U direction), NV, degreeU (polynomial degree), degree xpoint{1], y point{2], z point[1], x point{NUMNV], y pointINUMV J, z point{NUMIY J, knotsU[L], ... , knotsU [WUtdegreeU+4], knotsv[2}, ... , knotsV [NV+degreeV+4], IsRational (0 or 1) Weight{2],.., Weight [NU*NV] (only if rational) Volume Entity Code=9, number of 1D, label, selection, number of higher entities, conditions data=0 number of layer, mesh Number of boundary surfaces Number of surface[2],... , number of surface[number of surfaces], sense[2], .. sense [number of surfaces], (segment orientation, 0 or 1) xcenter, y canter, 2 center, Rules to follow: ‘There are four level types of geometrical entities: Point, Curves (straight segment, are, polyline, Nurbs), Surface (planar, Coon, Wurbs) and Volume. + Geometrical entities of the same type cannot have the same ID number associated (is not valid to have to curves with same 1D) + The numeration begins with 1 (not by 0 like in the “ entity is deleted). + The entities of a level are listed with increasing ID. style), and it could be jumps in the numeration (¢¢. when a ‘The center of the entities doesrit refer to the geometric center, itis simply an approximate center where its label will be drawn, + The higherentities number can be intialized to zero, and it will be corrected automatically if "Must Be repaired” flag was set to 2. In any case is recommended to set the righ value and avoid the reparation. + The lenght of NURBS curves could be set to zero, currant versions ignore this value and recalculate it, + Parametric curves are normalized to parameter space [0.0,4.0] + Parametric curve must have its initial point at parameter 0.0 and end point at parameter 1.0. A closed curve must share the same start and end point. + Parametric surfaces are normalized to parameter space [0.0,1.0]+{0.0,1.0] ‘The boundary curves of a surface define a outer loop and some possible inner loops. The outer loop is before outer loops. + The curves of a loop are ordered consecutivelly. A loop finish when the starting point of the first curve (taking into ‘account its sense for the surface) is equal to the last point of other curve.Geometry format: Modelname.geo ES + The ordering and orientation of the boundary curves must agree with the surface normal (Xu°Xy) (right-hand rule), ‘The outer loop must point to the same sense as the surface normal, and inner loops is any in the opposite sense, * Volumes are defined by a closed shell of surfaces: first surfaces must define the outer shell, and then the inner shells, + The order of surfaces on a ‘volume shell’ is not relevant, but the orientation must be 0 (SAME1ST) is the surface 6.1.1 Geometry example ‘This example consists on a simple cylinder, like the ene shown on the right It contains points, curves of type straight lines, circumference ares and curved NURBS with circumference shape, and surfaces of the types planar, ‘Coon and NURBS with cylindrical form, and there is a single volume. Note: This model could be found at: Examples\ Cylinder ASCIL.gidGeometry example 39Geometry example 40 This is the explanation of its content: RAMSAN-ASCII-gid-v7.6 UNKNOWN 0 ° “The GiD geometry ASCII file is wrote with rules of version 7.6, and without any problertype (UNKNOWN) “The model has two layers, created with: 1 Tops 0 100.255 2 Lateral 0.10255 255 ° “The layer number 1 is named Tops’, is net frozen, visible, and with RGB color The layer number 2 is named ‘Lateral, is not frozen, visible, and with RGB color Last 0 denotes the end of layers block ° ‘There is no meshing information attached to entities. “Then four points (code=1) are defined: 111230020 -1.65134 -1.60324 0 121230020 -1,65134 -1.60324 2.76945 131230020 -1,80449 -3.49553 0 141230020 -1,80449 -3.49553 2.76945 2.65134,-1.60324,0) 1,65134,-1,60324,3,76945) the meaning of rype_point 1=peint_id 1: layer ‘Lateral’ O=has_mesh_data 2=label_on_selection_off 3higherentities Jum_conditions O=id_material the point 1 belong to 3 curves (1, 3 and 5) then higherentities must be 3 211220020 12 221220020 34 ‘This define curves 1 and 2 that are straigth lines (type surfaces, then its higherentity counter is 2 .2), In this model that close a volume all curves belong to two “The curve 1 starts in the point 1 and end in the point 2 1131220020 135 22.98214 -1.65134 -1.603240 "2159749 -1.52666 0 "2167407 -2.47281 0 “2175064 -3.41896 0 “1180449 -3.49553 0 ooo0s05111 110.707107 10.707107 1 1141220020 2452 2.98214 "1.65134 -1.60324 2.76945 “2159749 -1.52666 2.76945 "2167407 -2.47281 3.76945Geometry example 41 “2.75064 -3.41896 3.76945 “110449 -3.49553 3.76945 ooo0s05111 41.0.707107 10.707107 1 1151220020 3.15 22,98213 “1.80449 -3.49553 0 58344 -3.57211 0 [781767 -2.62596 0 0519 -1.67981 0 71165134 -1.60324 0 0000505111 110.707107 10.707107 1 Previous text define curves 3, 4 and 5 that are NURBS (type==11) ig rational, weigehs= 1 0.707107 1 0.707107 1 jeguee 2. 902101ength 361220020 42 -0.315383 0.025526 0.949244 4.62163 7.77322 1000 o100 oo10 -1,41253 -2.57491 3.76945 1 And curve 6 is a circurference arc (type 11) angie (22a) ig 2 4x4 transformation matrix that moves the 2D arc to the final 3D location snd point (-0.215263 0.025526)=20 cencex 0.945244 1411210020 a 1423 oon “2.67407 -2.47281 1. 0.996741 -0.080672 0 02512 -1,65134 -1.60324 0 71165134 -1.60324 3.76945 "2159749 -1.52666 0 "2159749 -1.52666 3.76945 “2.67407 -2.472810 "2167407 -2.47281 3.76945 "2175064 -3.41896 0 "2175064 -3.41896 3.76945 “110449 -3.49553 0 “1180449 -3.49553 3.76945 oo oo00s505111 1.110.707 107 0.707107 1 10.707107 0.707107 11, 473 Surface 1 is a NURBS surface (type respectivelly Its approximated center is (-2.67407 -2.47281 3.98473) (0.996744 -0.080672 0) then are isted the control points, the Frets u=(0 0 42) andbnets va(0 000-8. 0-8 1 1a) and the weigths=(2 1 0.707107 0.707107 1 1 0.707307 9.707307 3 1) 14), it has 4 boundary lines: 1, 4, 2, 3, with orientations same, same, dif diffGeometry example 2 621210020 a 1526 1100 781767 -2.62596 1.88473 -10.6459 0.861634 -0 Surface 1 is a Coons surface (type==6), it has 4 boundary lines: 1, 5, 2, 6, with orientations dif, diff, same, same. Then is printed its approximated center and normal ‘The chape of kind of surface is defined only by its boundary. 1431210010 2 53 oo -1.72792 -2.54939 0 oor 12211 “2.7699 -1.5074 0 “217699 -3.59137 0 Surface 3 is like the 2. a NURBS surface (type 4), but in this case is trimming a planar squared shape. 541210010 2 64 an -1.41253 -2.57491 2.76945 oot Surface 4 is a planar surface (type=: ), that is defined by a canter an normal, and the trimming boundary lines. 911200020 4a 1243 ooo0 -1,72792 -2.54939 1.08473 ° This define the volume 1 (typs and approximated center=(-1.72792 -2.54939 1.88473) ) that is defined by 4 boundary surfaces: 1, 2, 4, 3 with orientations same, same, same, Last 0 is 2 NULL entity (type==0) that finish the definition of geometrical entities43 7 POSTPROCESS DATA FILES In GiD Postprocess you can study the results obtained from a solver program The solver and GiD Postprocess communicate through the transfer of files. The solver program has to urite the results to a file that must have the extension .post.res and its name must be the project name, ‘he solver program can also send the postprocess mesh to GID (though this is not mandatory), where it should have the extension .post.msh. IF this mech is nat provided by the solver program, GiD uses the preprocess mesh in Postprocess. ‘The extensions .msh and .res are also allow ed, but only files with the extensions .post.res ~ and potentially .post.msh - will automaticaly be read by GiD when postprocessing the GID project. Postprocessing data files are ASCII files, and can be separated into two categories: + Mech Data File: projece_nane.post.msh for volume and surface (3D oF 2D) mesh information, and = Results Data File; peeject_nane-post-res for results information 0 oe. post SOLVER, Proprosase GD rote epee Note:Projectitame.post.msh handles meshes of different element types: points, lines, triangles, quadhilaterals, tetrahedra and hexahedra, If a project is loaded into GiD, when changing to GiD Postprocess it will look for Projectitame,post.res. If a mesh information file with the name Proj ecttlame,post.msh is present, it ill also be read, regardless of the information available from GiD Prepracess, * ProjectName.postimsh: This fle should contain nodal coordinates of the mesh and its nodal connectivities as well as the material of each element. At the moment, only one set of nodal coordinates can be entered. Different kinds of elements can be used but separated into different sets, If no material is supplied, GiD takes the material number to be equal to zero. + ProjectName.postres: This second file must contain the nodal or gaussian variables, GID lets you define as many nodal variables as desired, as well as several steps and analysis cases (limited only by the memory of the machine). “The definitions af the Gauss points and the results defined on these points should also be written in ths file, ‘The files are created and read in the order that corresponds to the natural w ay of solving a finite element problem: mesh, surface definition and conditions and finally, evaluation of the results. The format of the read statements is normally free, ibe itis necessary only to separate them by spaces. “Thus, files can be modified with any format, leaving spaces betu een each field, and the resuits can also be written with as many decimal places as desired, Should there be an error, the program wars the user about the type of mistake found. GiD reads all the information directly from the preprocessing files whenever possible in order to gain efficiency. 7.1 Results format: ModelName.postresResults format: ModelName.post.res 44 Note: Code developers can dow nload the GiDpost tool from the GiD web page (http://w w..sidhome. comm gid-plus/tools/gi post!) this is a C/C++/Fortran library for creating pastprocess files for GiD in both ASCII and compressed binary format. ‘This is the ASCII format description: ‘The first line of the files with results written in this new postprocess format should be: where must be: 1.0 in general >=1:1 in case of binary compressed format >=1.2 in case of contain some OnllurbsSuzface result Comment lines are allo» ed and should begin with a'#", Blank lines are also allow ed. Results files can also be included with the keyw ord include, for instance: This is useful, for instance, for sharing several GaussPoints definitions and ResultRangeTable among different analyses. This ‘include’ should be outside the Blocks of information ‘There are several types of Blocks of information, all of them identified by a keyword = GaussPoints: Information about gauss peints: name, number of gauss points, natural coordinates, etc; * ResultRangesTable: Information for the resuit visualization type Contour Ranges: name, range limits and range + Result: Information about a result: name, analysis, analysis/time step, type of result, location, values: + ResultGroup: several results grouped in one block, These results share the same analysis, time step, and location (nodes or gauss points) 7.1.1 Gauss Points If Gauss points are to be included, they must be defined before the Result which uses them. Each Gauss points block is defined bety een the lines GaussPoints and End GaussPoints. ‘The structure is as follows, and should: * Begin with a header that follons this model GaussPoints "gauss_points_name" Elemtype my_type "mesh_name” where + GaussPoints, elemtype: are not case-sensitive; + sgauss_poines_name': is a name for the gauss points set, which will be used as reference by the results that are located on these gauss points: ma pme, decribes which element type these gauss points arefor, i.e, Mine, Tetangie, Guadsstatesal, + Smesh_name': is an optional field. If this field is missing, the gauss points are defined for all the elements of ‘type my_type. If a mesh name is given, the gauss points are only defined for this mesh. * Be follow ed by the gauss points properties: Number of Gauss Points: number_gauss_points_per_element Nodes included Nodes notincluded Natural Coordinates: Intemal Natural Coordinates: Given natural_coordinates_for_gauss_point_1... . natural_coordinates_for_gauss_point_n where + Number of Gauss Points: number_gauss_points_per_element: is not case-sensitive and is followed by the number of gauss points per element that defines this set. IF Natural Coordinates: is set to Internal, urber_gauss_points_per_element should be one of + 4, 3, 6for Triangles: + 4, 4, 9 for Quadiilaterals:Gauss Points 4s + 1, 4, 10 for Tetrahedra: + 1,8, 27 for Hexahedra; + 1, 6 for Prisms: #4, Sfor Pyramids; and + 2s. m points equally spaced over lines, For triangles and quadrilaterals the order of the gauss points with Internal natural coordinates will be this: y y 4 3 4 3 2 2 1 1 Internal coordinates: Internal coordinates: Internal coordinates: (0,0) 2£0.57735027 77459667 (ara) (ara) (2 3) (ara) (ara) (a, a) (0a) (2, 0) (a2) a.) (0, a) (2,0) (0, 0) ‘Gauss Points positions of the quadrature of Gauss-Legendre Quadilaterals Internal coordinates: Internal coordinates: Internal coordinates: 1/3 13=0.09157621 6=0.8168475 7 144594849 d=0,1081030 (aa) (2,0) (a, )(0, a) : (2,2) (ba) (26) (ed) (ee) (de) Gauss Points positions of the quadrature of Gauss for Triangles For tetrahedra the order of the Internal Gauss Points is this:Gauss Points Internal coordinates: 2=(5434sqrt(5))/20=0.585410198624968 b=(S-sart(S))/20 =0.138196601125020 (1b, b, b) ( a,b, b) ( b, a, b) (bb, a) For hexahedra the order of the Intemal Gauss Points is this: Internal coordinates: 2 0.577350269189626 (-ararca) (aaa) (a, aa) (-a, ara) (ara, a) (ara.a) (aaa) Ca, aa) For prisms the order of the Internal Gauss Points is this: 9.21324965405187 799675134594012 (a0 (bad (abe (aa) (bead) (abd) Internal coordinates: 9=0,108103018168070 b=0,445948490915965 =0.816847572980459, (aaa(caad(aca)(aad (by a, a) (by bs a) (a, by a) (a, a,b) (by a,b) (a,b, b) Internal coordinates: 9.774596669241483 a) ( a-aica) ( 2, aa) (-a, ara) (Cara, a) (ara, a) (a, 2,3) (-a, a a) (0-aa) ( a, 0.-a) (0, aa) (-a, 0.-a) (ara, 0) (ara, 0) (a, 2, 0) (-a, a, 0) (0a, a) (3,0, 2) (0, a, a) (-a, 0. a) (0, 0-3) (0a, 0) ( 3, 0, 0) (0, a, 0) (-a, 0, 0) (0,0, a) (0,0, 0) For pyramids the order of the Internal Gauss Points will be this:Gauss Points a7 Internal coordinates: (258.0 sqrt(2.0/15.0)/ 5.0 =0.584237394572177 b=-2/3 =-0.ss66sescee56665 /5 = 0.4 (-3;-2,b) (2,-2,b) (aab) (-3, a,b) (0.0, 0.0, ¢) ‘The given natural coordinates for Gauss Points should range: + betu een 0.0 and 1.0 for Triangles, Tetrahedra and Prisms, and for Quadrilaterals, Hexahedra and Pyrarrids. Note: If the natural coordinates used are the internal ones, almost all the Results visualization possibilities will have some limitations for tetrahedra and hexahedra with more than one gauss points. If the natural coordinates are given, these limitations are extended to those elements with number_gauss_points_per_element not included in the list written above. + Nodes Included / Nodes not Included: are not case-sensitive, and are only necessary for gauss points on Line elements which indicate whether or not the end nodes of the Line element are included in the urber_gauss_points_per_element count: ‘The default value is nodes not included Note: By now, Natural Coordinates for line elements cannot be "Given" + Natural Coordinates: Internal / Natural Coordinates: Given: are not case-sensitive, and indicate whether the natural coordinates are calculated internally by GiD, or are given in the following lines. The natural coordinates should be written for each line and gauss point. + End with this tall End GaussPoints where End GaussPoints: is not case-sensitive Here is an example of results on Gauss Points Internal Gauss pointsGauss Points 48 ‘The following Internal gauss points are automatically defined, Results can use this names without explicitly define them with a GaussPoints / End GaussPoints statement op_pONT_a GP_LINE2 GP_TRIANGLE_1 GP_TRIANGLE_3 GP_TRIANGLE_6 GP_QUADRILATERAL_1 GP_QUADRILATERAL. 4 GP_QUADRILATERAL 9 GP_TETRAHEDRA_1 GP_TETRAHEDRA_4 GP_TETRAHEDRA_10 GP_HEXAHEDRA_1 GP_HEXAHEDRA_@ GP_HEXAHEDRA_27 GP_PRISM_1 GP_PRISM_6 GP_PIRAMID_1 GP_PIRAMID_S GP_SPHERE_1 GP_CIRCLE_2 Is is possible to use also the generic name GP_ELEMENT_1 to mean all kind of elements with 1 gauss point (instead of the specific element GP_LINE_1, GP_TRIANGLE_t, etc. 7.1.2 Result Range Table If Result Range Table is to be included, it must be defined before the Resuit which uses it. Each Result Range Table is defined betw een the lines ResultRangesTable and End ResultRangesTable ‘The structure is as follows and should * Begin with a header that follows this model ResultRangesTable "ResultsRangeTablell ame” where ResultRangesTable: is not case-sensitive; "ResultsRangeTablellame": is a name for the Result Ranges Table, hich will be used as a reference by the results that use this Result Ranges Table, + Be follow ed by a lst of Ranges, each of them defined as follows Min_Value - Max_Values "Range Name” where + Min_value : is the rinimum value of the range, and may be void if the Max_value is given. If void, the minimum value of the result will be used; + Max_value + is the maximum value of the range, and may be void if the Min_value is given. If void, the maximum value of the result will be used: + "Range Name" : is the name of the range which will appear on legends and labels. © End with this tall End ResultRangesTable where End ResultRangesTable: is not case-sensitive. Here are several examples of results range table: + Ranges defined for the hole result: Ball the ranges are min <= rex < mar except # che ase range is min <= res * dust a couple of ranges: + OF using the maximum of the result:Result Range Table 49 7.1.3 Result Each Result block is identified by a Result header, follow ed by several optional properties: component names, ranges table, and the result values, defined by the lines Values and End Values. ‘The structure is as follows and should * Begin with a result header that follow s this model Result "resuit name" "analysis name" step_value resuit_type result_location "location name" where + Result is not case-sensitive; + vresule mane": ig a name for the Result, which will be used for menusi if the result name contains spaces it should be written betw ean "" or betw ean (}. "analysis name": is the name of the analysis of this Result, which will be used for menus; ifthe analysis name contains spaces it should be written betw een "or between {. + svep_valwe: is the value of the step inside the analysis "analysis name": + resule_cype: describes the type of the Result, It should be one of the follow ini + Seals: one component per result + Vector: ty, three or four components for result: x, y, 2 and ( signed) modulus Macrix: three components for 2D matrices, six components for 3D matrices PlainDefosmationtiaesix: four components: Six, Syy, Sx, SEZ Nainifacsix: the three main unitary eigen vectors vectors ( three components each) and three eigen values of the matrix + “Loeat Ares: three auler angles to specfy the local axis + ComplexSealar’ tio components to spacty a+b i + ComplexVecter: four components for 2D complex vectors, six or nine components for 3D vectors! FX ix r¥ iY £2 iZ [el lil [vector] ~-> to specify the vector (1X + ik, r¥ +i, 12 + 12) + zesult_location® is where the Result is located. It should be one of the following: Ifthe Result is onGaursPoines, g “Location nane" should be entered: is the name of the Gauss Points on which the Result is defined Note: Resuits can be visually grouped into ‘folders’ like in the following picture ts: sta . os seslFaceNUn FT % igiese Hts by just grouping of results using double slahes in the result names: Result "fechanical//Pressures//Watez pressure” "Time analysis" 60 Result "Physical//Sacuzation" "Time analysis” 60 Scalar Onllodes and £0 on. + Be follow ed (optionally) by result properties:Result 50 ResultRangesTable "Name of a result ranges table” ComponentNames "Name of Component 1", "Name of Component 2° + ResultRangesTable "Name of a result ranges table": (optional) is not case-sensitive, follow ed by the name of the previously defined Result Ranges Table, which will be used if the Contour Ranges result visualization is chosen (see Table pag 40); + Componentitames "Name of Component 1", "Name of Component 2": (optional) is not case-sensitive, follow ed by ‘the names of the components of the results which will be used in GiD. Missing components names will be Tezult Rani automatically generated, The number of Component Names are! * One for a Scalar Result + Three for a Vector Result © Six for a Matrix Result * Four for a PlainDeformationMatrix Result * ‘Six for a MainMatrix Result + Three for a Localaxes Result + Two for a ComplexScalar Result * Six or nine for ComplexSealar + Uniti the unit of the result. + End with the result values: Values End Values where * Values: is not case-sensitive, and indicates the beginning of the results values section; © The lines + node_or_eler_number component_1_value component_2_value + node_or_elern_number component_1_value component_2_value are the values of the result at the related 'node_or_elem_number’ ‘The number of results values are limited thus: *+ the Result is located Onttodes, they are limited to the number of nodes defined in Projectitame.post.rnsh, +f the Result is located OnGaussPoints "My GP", and if the Gauss Points "My GP" are defined for the mesh "My mesh’, the limit is the number of gauss points in "My GP" multiplied by the number of elements of the mesh “My mesh’ For results in gauss points, each element must have 'ngause' lines of results For example, ifthe number of gauss points is 3, then for an element, 3 lines of gauss point scalar result must appear. Holes are allowed in any result. The element nodes with no result defined will not be drawn, ie. they will appear transparent. Result location: OnNodes: results are defined on the nodes of the mesh. If nodes are shared betw een elements, as usual, then the result field is continous. OnGaussPoints: results are defined in some locations of the mesh elements. Usually solvers calculate values in some special locations named ‘gauss points’ for its numerical integration, then is natural to write the results on these locations. The resuits field is discontinuous between elements, then some options like calculate streamlines are not allow ed for this kind of result. Sometimes results are extrapolated and averaged on nodes providing a continuous andResult SL smoothed result. OnNurbsSurface: results are defined on the ‘control points’ of the NURBS surfaces. These surfaces by default are the ones of preprocess, but could be overriden by an optional file with the same format as the .geo preprocess file In this case the .post.geo fle must contain only surfaces of NURBS type, and any volume. Note: in case of have some result OnllurbsSurface the file header must be declared with version greater of equal to 12 ‘The values block of a result Onl\urbsSurface must have for each surface with results something like this Walwe()_sonponent_A ...valwe()_comonent_n value (num_contzel_poines_s)_component_1 -.. value(num_contzel_poines_u)_component_n value (num_contzol_poines_w x num_control_peints_v)_component_1... value(num_contzol_poinesy ol_posnes_v) companent_m where surface_nunber js the id of the surface (the same integer number that identify the surface in preprocess) value jg the real number of the result, It is compulsory to write the values for all control pointsof the surface, if some control point doesn't has result it must have a NR value to represent 'no result” This is tipical of trimmed NURBS surfaces, some control points far of trimmed part are not relevant and doest'n have any value, Ie the whole surface doesn't has OntlurbsSurface result, itis not nacesary to be written, ‘There is a model with isogeometric results OnllurbsSurface ati Examples\IGA_shell.gid\IGA_chell.postires ‘The number of components for each Result Value are: * for Scalar results: one component resuit_nurrber_| scalar_value * for Vector results: three components, with an optional fourth component for signed modules result_number_i xvalue y_value 2_value result_number_i x_value y_value 2 value signed_module_value + for Matrix results: three components (2D models) or six components (30 models)2D: _result_number_i Sxx_value Syy_value Sxy_value3D: result_ourrber_j Sxe_value * for PlainDeformationMatrix results: four components result_number_i Sxx_value Syy_value Sxy_value Sez_value + for MainMatrix result Sxx_value Syy_value Sez_value Sxy_value Syz_value prelve components result_number_i Si_value Sil_value Sill_value Vix_value Viy_value Vie_value Viix_value Viiy_value Viiz_value Vilix_value Vily_value Viiz_value * for Localxes results: three components describing the Euler angles result_number_i euler_ang_3_value ‘euler_ang_?_value euler_ang_3_value, Look for LocalAxesDef(EulerAngles) at Multiple values return commands for a more detailed explanation to calculate axis from euler angles and vice-versa + for ComplexScalar results: two components to specify a+b +i * for ComplexVector results: four components for 2D complex vectors, six or nine components for 3D vectors: CK FIV FZ [rf [i] [vector] => to specify the vector (1+ 1K, HY HY, FZ +12) * End Values: is not case-sensitive, and indicates the end of the results values section Not For Matrix and PlainDeformationMatrix resuits, the Si, Sii and Sili components are calculated by GiD, which represents the eigen values & vectors of the matrix results, and which are ordered according te the eigen value. 7.1.3.1 Results example Here is an example of results for the table in the previous example (see fish sxamaleResults exampleResults example 53Results example 54 7.1.4 Result group Results can be grouped into one block. These results belong to the same time step of the same analysis and are located in the same place. So all the results in the group are nodal results er are defined over the same gauss points set Each Result group Is identified by a ResultGroup header, followed by the results descriptions and its optional properties ~ such as corrponents names and ranges tables, and the results values - all bety een the lines Values and End values. ‘The structure is as follows and should * Begin with a header that follons this model ResultGroup "analysis name" step_value my_location " where + Resultsrou is not case-sensitive: + "analysis name’: is the name of the analysis of this ResultGraup, which will be used for menus: if the analysis name contains spaces it should be written between or between {). * step_value! is the value of the step inside the analysis “analysis name": + my_lecation: is where the ResultGroup is located, It should be one of the following: Onllodes, OnGaussPoints. If the ResultGroup is OnGaussPoints, a "lecation name" should be entered, location name": is the name of the Gauss Points on which the ResultGroup is defined. * Be follow ed by at least one of the resuits descriptions of the group ResultDescription "result name" my_result_type{:components_number] ResultRangesTable "Name of a result ranges table’ ComponentNames "lame of Component 1", "Name of Component 2" where + ResultDescription: is not case-sensitive: + "result name"! is a name for the Resuit, which will be used for menus; ifthe result name contains spaces it should or between {. + my_type: describes the type of the Result. It should be one of the following: Scalar, Vector, Matrix, PlainDeformationMatrix, MainMatrix, or LocalAxes. The number of components for each type is as follows be written bet een © One for a Scalar: the_scalar_value + Thres for a Vector: x, Y and Z + Six for a Matrix: Sxx, Syy, Szz, Sxy, Syz and Sxz * Four for a PlainDeformationMatrix: Sxx_value, Sy, Sxy and Sez + Twelve for a MainMatrix: Si, Si, Sil, VIX, Viv, VIZ, Vix, ViY, VIZ, ix, Vi and Viz + Three for a LocalAxes: euler_ang_1, euler_ang_? and euler_ang 3 Following the description of the type of the result, an optional modifier can be appended to specify the number of components separated by a colon, It only makes sense to indicate the number of components on vectors and matrices: © Vector:2, Vectori3 or Vector:4: which specify © Vector:2: x and ¥ x, ¥ and Z X,Y; Z and [Vector] (module of the vector, with sign for some tricks) ‘The default (Vector) is 3 components per vector. © Matrix: oF Matrixi6: which spect 3: Six, Sy and Sxy Sox, Sys $22, Sxy, Syz and Sxz ‘The default (Matrix) is 6 components for matrices: Here are some examples: ‘and w here (optional properties) * ResultRangesTable "Name of a result ranges table": (optional) is not case-sensitive, and is follow ed by the name of the previously defined Result Ranges Table which will be used if the Contour Ranges result visualization is chosenResult group 55 (see Result Range Table -pea. 48); CCommponentitames "Name of Component 1", "Name of Component 2": (optional) is not case-sensitive, and is follow ed by the names of the components of the results which will be used in GiD. The nurrber of Component Names are: * One for a Scalar Result + Three for a Vector Result © Six for a Matrix Result * Four for a PlainDeformationMatrix Result Six for a MainMatrix Result + Three for a Localaxes Result = End with the results values: Values End Values ~ ~ ~ where * Values: is not case-sensitive, and indicates the beginning of the results values section; + The lines * location_1. result_1_cormponent_1_value result_1_component_2_value result_1_cormponent_3_value result_2_component_2_value result_2_component_: 2 value result 2_component_3_value * locationn result_1_corponent__value result_1_component_: 2 value result_1_component_3_value result_2_compenent_2_value result_2_component_2_value result_2_component_3_value are the values of the various results described with ResultDescription for each location. All the results values for the lecation '' should be written in the same line". ‘The number of results values are limited thus: + the Result is located Onttodes, they are limited to the number of nodes defined in Projectitame-post.rnsh, If the Result is located OnGaussPoints "My GP", and if the Gauss Points "My GP" are defined for the mash "My mesh’, the limit is the number of gauss points in "My GP" multiplied by the number of elements of the mesh “My mest Holes are allow ed. The element nodes with no result defined will not be drav'n, ie, they will appear transparent: “The number of components for each ResultDescription are: * for Scalar results: one component resuit_nurrber_| scalar_value for Vector results: three components result_number_i x_value y_value =_value for Matrix results: six components (30 medels)3D: result_number_i Six_value Syy_value S2z_value Sxy_value Syz_value Sxz_value * for PlainDeformationMatrix results: four components result_number_| Six_value Syy_value Sxy_value Sez_value + for MainMatrix results: prelve components result_number_i Si_value Sil_value Sill_value Vix_value Viy_value Vie_value Viix_value Viiy_value Viiz_value Vilix_value Vily_value Viiz_value for LocalAxes resuits: three components describing the Euler angles result_number_i euler_ang 1_value ‘euler_ang_?_value euler_ang_3_value * End Values: is not case-sensitive, and indicates the end of the results group values section. Jectors in a ResultGroup alw ays have three components. Matrices in a ResuitGroup alw ays have six components: All the results of one node or gauss point should be mritten on the same line. Note: For Matrix and PlainDeformationMatrix results, the Si, Sii and Sill components are calculated by GiD, which represents the eigen values & vectors of the matrix results, and which are ordered according te the eigen value. Nodal ResultGroup example:Result group 56 ResultGroup ‘Lead Analysis" 1 Onledes ResultDescription "Ranges test” Scalar ResultRangesTable "My cab) ResultDescription "Scalar test" Scalaz ResultRangesTable "Presser ResultDescription "Displ acemen ‘ComponentNames "{-Displ", "Y-DispI" *Z-Displ ResultDescription Medal Stresses" Maer ComponentNames "Sx", "Sy", "Se", "Sey", "Sys", "See" Gauss Points ResultGroup example: GaussPoints "iy Gauss" Elentype Triangle ‘Number Of Gauss Points: 2 Natural Coordinates: Inteznal 7.2 Mesh format: MedelName.post.msh Not ‘This postprocess mesh format requires GiD version 6,0 or higher. Comments are allow ed and should begin wth a'#, Blank lines are aso allow ed. To enter the mesh names and result names in another encoding, just write # encoding your_encoding for example # encoding wee-8 Inside this fle one or more MESHes can be defined, each of them should: * Begin mith a header that follons this model MESH "mesh_name” dimension mesh_dimension Elemtype element_type Nnede element_nur_nodes where + MESH, dimension, elemtype, nnode: are key ords that are not case-sensitive; + mesh_name": ig an optional name for the mesh; + mesh dimension: ig 2 of 3 according to the geometric dimension of the mesh; + elenent_eype: describes the element type of this MESH. It should be one of the following: Peint, Line,Mesh format: ModelName.post.msh 57. Teiagle, Quadrilateral, Tetrahedra, Hershedra, Prism, Pyramid, Sphere, Cizcle ; + element_nom nodes: the number of nodes of the element: * Point: 4 node, Point connectivity’ + Line: 2 or 3 nodes, : | __ Line connectivities: we Ay + Triangle: 3 or 6 nodes, ‘Triangle connectivities: A&é + Quadrilateral: 4, 8 or 9 nodes, Quadrilateral connectivities + Teerahedra, 4 of 10 nodes, Teerahedsa, connectivities & & + Mexahedsa, 9, 20 of 27 nodes, Hexaheds2, connectivities: mH 7 of * Prism: 6,15 or 18 nodes, Prism connectivities: + Pyramid: 5 or 13 nodes, Pyramid connectivities:Mesh format: ModelName.post.msh 58 + Sphere: 1 node and a radius + Circle: node, 2 radius and a normal (x,y. 2) Note: For elements of order greater than linear, the connectivities must written in hierarchical order, ve, the vertex nodes first, then the middle ones. * An optional line declaring the units of the mesh coordinates + An optional line describing its colour with # color R GBA, where R, G, B and A are the Red, Green, Blue and Alpha components of the color written in integer format betw een 0 and 255, or in floating (real) format betw een 0.0 and 1.0. (Hote that if is found in the line it will be understood as integer, and so 1 above 255, rather than floating, and so 1. above 1.0). Alpha values represent the transparency of the mesh when this visualization options is active, being 0.0 totally opaque and 3.0 tetally transparent, # color 127 1270 In this way different colours can be specified for several meshes, taking into account that the # color line rust be bet een the MESH line and the Coordinates line. * Be follow ed by the coordinates: coordinates end coordinates where * the pair of keywords coordinates and end coordinates are not case-sensitive: * between these keyu ords there should be the nodal coordinates of all the MESHes or the current one, Note: If each MESH specifies its own coordinates, the node number should be unique, for instance, f MESH "mesh cone’ uses nodes 1..100, and MESH "other mech” uses 50 nodes, they should be numbered from 103 up. + Be follow ed by the elements connectivity elements Bet end elements where + the pair of keywords elements and end elements are not case-sensitive: + beti aan these keywords there should be the nodal connectivities for the my_type elements, Note: On elements of order greater than linear, the connectivities must written in hierarchical order, ie. the vertex nodes first, then the middle ones; + There is optionally 2 material number. * For Sphere elements : Elenent_number Wode number Radius [optional_material_nonber] + For Circle elements ; Elenent_nonber ode nunber Radius [optional_nermal_x optional_nezmal_y optional_nozmal_s] (opeional_material_nunber] If the normal is not written for circles, normal ( 0.0, 0.0, 1.0) vill be used.Mesh example 59. 7.2.1 Mesh example This example clarifies the description: ne coordinates then they are already in the fizse MESH 7.2.2 Group of meshes If the same meshes are used for all the analyses, the following section can be shipped. ‘Anew concept has been introduced in Postprocess: Group, which allows the postprocessing of problems which requireGroup of meshes 60. re-meshing or adaptive meshes, where the mesh change depending on the time step. Normal operations, such as animation, displaying results and cuts, can be done over these meshes, and they will be actualized when the selected analysis/step is changed, for example by means of View results -> Default analysis/step ‘There are tw o ways to enter in GiD the diferent meshes defined por diferent steps or analysis: 1. define separate files for each mash, for instance: = binary format: mesh+tresuit_1.post.bin, mesh+result_2.post.bin, mesh+result_3.post.bin, ~ ascii format: mesh_1.post.msh + mesh_L.post.res, mesh_2.post.msh + mesh_2.post-res, Note: the steps values ( or analysis) should be diferent for each pair mesh+result. To read them you can use File--> Open Multiple (see POSTPROCESS > Files menu from Reference Manual) 2. define on binary file or tv asci files (msh+res): Meshes that belong to a group should be defined betw een the following highlighted commands Group “group name" MESH "mesh_name” dimension .. tend elerments MESH "anther_mesh” tend elerments end group Results which refer to one of the groups should be written between these highlighted commands OnGroup “group name’ Result "vesult name" end values end ongroup Note: GID versions 7.7.36 and later only allow one group at a time, i-e. only one group can be defined across several steps of the analysis. Care should be taken so that groups do net overlap inside the same step/ analysis. For instance, an analysis which is 10 steps long © For steps 1, 2, 3 and 4: an ‘environment’ mach of 10000 elements and a 'body' mesh of 10000 elements are used and its results * For steps 5, 6, 7 and 8: with some refinement, the ‘environment’ mesh now being used has 15000 elements and theGroup of meshes 61 "body' mesh needs 20000 elements and its results are * For steps 9 and 10: the last meshes to be used are of 20000 and 40000 elements, respectively and its results are ‘There are tw o ways to postprocess this: * store the information in three pairs (or three binary files), thus © steps 1.2.3 4,post.msh and steps_1_2.3_4.post.msh (or steps_1_2 3. 4,post.bin) + steps_5_6_7_8.post.mch and steps_5_6_7_8.post.msh (or steps_5_6_7_8.post.bin) * steps_9_20.postimsh and steps_9_10,postimsh (or steps_9_10,post.bin) land use the ‘Open multiple’ option (see POSTPROCESS > Files menu fram Reference Manual) to selected the six (or three) files; or * sirite them in only ta files (one in binary) by using the Group concept: + all_analysis,post.meh (note the group - end group pairs) Group "steps 1, 2, 3 and 4” MESH “environmer MESH "body" . end group Group “steps 5, 6, 7 and 8” MESH “environmerGroup of meshes 62 MESH "body" . end group Group "steps 9 and 10" MESH “environment”. MESH "bods end group and + all_analysis.post.res (note the ongroup - end ongroup pairs) GiD Post Results File 1.0, OnGroup "steps 1, 2, 3 and 4” Results Results "result 2 Results "result 2 Results ‘end ongroup OnGroup "steps 5, 6, 7 and 8” Results "result 2 Results "result 2" "time" 6.0... Results "result 2 Results "result 2" "time" 8.0... ‘end ongroup OnGroup "steps 9 and 10) Results "result 2 Results ‘end ongroup land use the normal Open option, 7.2 List file format: ModelName postlst New file *.post.st can be read into GiD, postprocess, This file is automatically read when the user works in a GID project and changes from pre to postprocess, ‘This file can also be read with File-->Open ‘The file contains alist of the files to be read by the postprocess:List file format: ModelName.post.{st 63 + The first line should contain one of these words: * Single: just a single file (ti 0 for asci files: one for mesh and another for results) is provided to be read: + Merge: several filenames are provided, one filename per line, which are to be merged inside GID, for instance when the files come from a domain decomposed simulation: + Multiple: several filenames are provided, one filename per line, which are read in GiD, for instance if they belong to a DEM simulation, or FEM simulation with mesh refinements + next lines: the mesh and results files to be read, with one filename per line: + following the postprocess mesh and result files, a list of graphs filenames can be provided so that GID reads them too; fraphs files have the extension .grf; + comment lines begin with the # character and blank lines are also adrrited; + file names may have absolute path names or relative to the lst fle location; Example of alist file: # postprocess files graph files File names may have absolute path names or relative to the lis file location. 7.4 Graphs file format: ModelName.post.grf “The graph file that GID uses is a standard ASCIT fie. Every line of the file is a point on the graph with X and coordinates separated by a space. Comment lines are also allowed and should begin with a'#" ‘The title of the graph and the labels for the X and Y axes can alzo be configured with some ‘special’ comments: + Title: Ifa comment line contains the Keyw ord 'Graphs' the string betw ean quotes that follows this keyw ord will be used as the title of the graph, + Axes labels: The string between quotes that follows the keywords "X:' and 'Y: ‘Y-axes respectively. The same is true for the Y axis, but with the Keyword "7! + Axes units will be used as labels for the X- and Example: B Graph: "Serenses! 8Graphs file format: ModelName.post.grf The file *.grf (which contains graphs) is read when changing from pre to post projectiiame.gid/projectitame.post.grf exists, or the postprocess files are read through example.msh/res/bin and exarrple.grf are read. “The post list file ( *.post-Ist) can also contain a list of graphs (*.arf ). process and Flle-->Open, then 646s 8 TCL AND TK EXTENSION This chapter looks at the advanced features of GiD in terms of expandability and total control. Using the Tel/Tk extension ‘you can create script files to automatize any process created with GiD. With this language new window s and functionalities can be added to the program. For more information about the Tcl/Tk programming language itself, look at w ww. scriptics.com http://w w.seriptics.com. If you are going to use a Tcl file, it must be located in the Problem Type directory and be called problem_type_name.tl Problem Type directory D -1 Event procedures A Event procedure’ is a Tel procedure that is invoked from GiD when doing some actions, I allow's developers to interleave its code with the GID flow. The structure of problem _type_name.tel can optionally implement some of these Tel prototype procedures (and other User-defined procedures). The procedures listed below are automatically called by GiD. Their syntax corresponds to standard Tel/Tk language: Not isis possible to get the list of Tel events with the procedure GiD_Info events proc InieGIProjece ( az} ¢ > proc BeforeinieGIDPostProcess () ( > proc InieGIDPostProcess () ( seurn fvaiee > proc EndoipPregect () ( > proc EndGipPostProcess () ( > proc AfverdpenFile ( filenane format exsoz ) ( > proc AfverSaveFile ( filename format exzoz ) ( > proc AfverSavelmage ( filename fozmar } ( > proc BeforeReadGIDProject ( filename } ( boay,Event procedures 66 zecurn fvalue > proc AfvesReadGIDProject ( filenane } ( > proc LoadGInProject ( filespa } ( > proc SaveGIDProject ( filespa } ( > prec AfvesSaveas (ol: > 1 filename new filename } ( proc LoadResulesGipPostProcess ( file } ( > proc BeforelfeshGenezation ( elenentsize } ( seurn fvaiee > proc AfvenifesAGeneracion ( fail } ( > proc AfterRenumber ( uscof leveltype renuneration ) ( > proc SelectGIDBaeFile ( diz basename } ( seurn fvaiee > proc BeforeRunCalcul ation ( batfilenane basenane diz problencypediz gidexe args) ( seurn fvaiee > proc AfvesRunCalculation ( basenane diz problentypediz where exzoz exrozfilenane ) ( seurn fvaiee > proc Changedbanguage ( language } ( > proc BeforeWriveCalcPilecimProject ( €ile ) ( seurn fvaiee > proc AfvestiriveCalcFileGIDProject ( file exzoz } ( seurn fvaiee > proc BeforeTzansfornProblentype { file oldproblencype newproblemtype } ( seurn fvaiee > proc AfvesTransfosnProblenType ( file oldproblemtype newpreblencype messages } ( seurn fvaiee > proc TelCalcModelBowndaries( wseof ) (Event procedures 67. > Semin Gymin Gamin Gemae dyer fama proc A€vesthangeBackgzound ( ) ( > proc BeforeCopy ( useof transformation exzoz } ( proc AfvesCopy ( useof transformation exzor } ( proc Beforetove ( useof transformation exzoz } ( proc Afvesifove ( useof transformation exzor } ( proc AfvesCreatePoine ( mum } ( proc AfvesCzeateLine (mum) ( proc AfverCeearesurtace (mam } ( proc AfvesCreateVolune ( num} ( proc BeforeDelevePoine ( num) ( proc BeforeDeleveLine ( mum } ( proc BeforeDelevesurface ( num } ( proc BeforeDelereVolume ( mam } ( proc AfvesCreateLayer ( name) ( proc AfvesRenaneLayer ( oldnane nemane } ( > proc BeforeDeleveLayer (name } ( setusn fvalue > proc AfvesthangeLayer ( nane property } ( > proc AfvesthangeParentLayer ( oldnane nemane } ( proc AfverSeclayesTolse ( mane} ( proc A€verSendToLayer ( name) ( proc AfterCreateGroup ( name ) ( proc AfterRenmeGroup ( oldnane nemane ) ( > proc BeforeDeleteGroup ( name ) (Event procedures 68. zecurn fvalue > proc AftesDeleveGroup ( name) ( proc AfterthangeGroup ( nane property } ( proc AfvesthangeParentGroup ( oldnane nesmane } ( proc AfterthangeLicenceStatus ( status} ( proc AfverCzeateHlaverial ( nawe } ( proc AfvesRenaneHlaverial ( oldnane nemane ) ( > proc BeforeDeleveaterial ( mane) ( seurn fvaiee > proc AfvesthangeHlaterial ( nane changedfields } ( > proc AfverAssignilacerial ( nane leveleype } ( > proc BeforelfeshEzrors ( filename ) ( setusn fvalue > proc BeforeResultReadEzzors ( filenane meg format} ( setusn fvalue > proc AfvesProcess ( words iz_zotation } ( > proc AfverCreateVolumesee (mane) ( > proc AfvesRenaneVolumesee ( oldnane nemane } ( > proc BeforeDeleveVolumeser ( mane } ( value ~cancel- to avoid delecion zecurn fualee > proc AtvesCreatesurfaceser ( mane} ( > proc AfvesRenanesurfaceSet ( oldname nemane } ( > proc BeforeDeleveSurfaceser ( name ) ( value “cancel co avoid delecion zecurn fualee > proc AfvesCeeareCutser (name } ( > proc AfvesRenaneCutset { oldnane nemane ) ( >Event procedures 69 proc BeforeDeleveCueser ( mane} ( value “cancel co avoid deletion zecurn fualee > proc AfverthangeViewtfode ( wseof ) ( > proc AfvesCreateGraph ( name) ( > proc BeforeDeleteGraph ( name ) ( setusn fvalue > proc AfvesDeleveGraph ( name) ( proc AfvesthangeGraph ( nane property } ( proc AfvesRenaneGraph ( oldnane nemane } ( proc AfverCzeateGraphser ( mane} ( > proc BeforeDeleveGraphsee (mane ) ( seurn fvaiee > proc AfvesDeleveGraphser ( mane} ( proc AfverthangeGraphser ( nane property ) ( proc AfvesRenaneGraphser ( oldnane newmane ) ( proc AfverSecGraphSecToUse ( mane} ( + IniteIDProject: will be called when the problem type is selected. It receives the dir argument, which is the absolute path to the proble_type_name.cid directory, which can be useful inside the routine to locate some alternative files + BeforeInitGIDPostProcess: will be called just before changing from pre to postprocess, and before read any postprocess fle (this event can be used for example to check the results fle existence and/or rename files). It has no ‘arguments, If t returns ~cancel- as a value then the sy apping to postprocess mode will be cancelled. InitG1DPostProcess: wll be called when postprocessing starts, It has no arguments, + EndGIDProject: wil be called when this project is about to be closed. It has no arguments. + EndGIDPostProcess: will be called when you leave Postprocess and open Preprocess. It has no arguments * AfterOpentile: will be called after a geometry or mesh file is read inside GID. Tt receives as arguments: * filename: the full name of the file that has been read: * format: ACIS_FORMAT, CGNS_FORMAT, DXF_FORMAT, GID_BATCH FORMAT, GID_GEOMETRY_FORMAT, GID_MESH FORMAT, IGES_FORMAT, NASTRAN_FORMAT, PARASOLID_FORMAT, RHINO_FORMAT, ‘SHAPEFILE_FORMAT, STL_FORMAT, VDA_FORMAT, VRML_FORMAT or 3DSTUDIO_FORMAT, * error: boolean 0 or 1 to indicate an error when reading, + AfterSaveFile: will be called after a geometry or mesh file is exported to 2file It receives as arguments: * filename: the full name of the fle that has been written; * format: ACIS_FORMAT, DXF_FORMAT, GID_GEOMETRY_FORMAT, GID_MESH FORMAT, IGES_FORMAT, RHINO_FORMAT, AMELET_FORMAT, KML_FORMAT, * error: boolean 0 or 3 to indicate an error when reading + AfterSavelmage: will be called after a picture or modal is saved to disk. It receives as arguments:Event procedures 70 * filename: the full name of the file that has been saved: * Format: eps, ps. tif, bmp. ppm, gif, png. jpg. tga, wl + BeforeReadGIDProject: 1 ll be called just before read a GID project, It receives the argument filename, which is the path of the model folder, without the .gid extension, If it retuns -cancel- then the reading is cancelled. + AfterReadGIDProject: will be called just after read 2 GiD project. It receives the argument filename, which is the path of the model folder, without the .gid extension, + LoadG1DProject: will be called when a GID project or problem type is loaded. It receives the argument flespd, which is the path of the file which is being opened, but wth the extension .spd (specific problemtype data). This path can be Useful if you w ant to write specific information about the problem type in anew file + SaveGIDProject: wll be called when the currently open file is saved to dick, It receives the argument filespd, which is the path of the file being saved, but nith the extension .spd (specific problemtype data). This path can be useful if you want to write specific information about the prablem type in a new file. © AfterSaveAs: will be called after GiD save its information in the new_filename location, when this folder and the model files exists, and provide the old_filename argument for example to allow to copy extra data, like result files handled by the problemtype, + LoadResultsGIDPostPracess: will be called when a results file is opened in GiD Postprocess. It receives one argument, the name of the file being opened without its extension. * BeforeMeshGeneration: wil be called before the mesh generation. It receives the mesh size desired by the user as the elementsize argument. This event can typically be used to assign some condition automatically. It returns ~cancel- the mesh generation is cancelled. + AfterMeshGeneration: will be called after the mesh generation, It receives as its fail argument a true value if the mash is not created + AfterRenumber: ll be called after renumber the geometry or the mesh (to update for example fields storing entity identifiers) * useof : could be GEOMETRYUSE or MESHUSE * leveltype: the kind of entity that w as renumbered. Geometry: must be ALL LT: Mesh: could be NODE_LT of ELEM_LT, + enumeration: Geometry: four sublists with the old and new idenfiers for points, ines, surfaces and volumes. Mesh: a sublist with the old and new identifiers for nodes or elements. + SelectGIDBatFile: must be used to snitch the default batch file for special cazes. This procedure must return as a value the alternative pathname of the batch file. For example itis used as a trick to select a different analysis from a list of batch calculation files + BeforeRunCalculation: will be called before running the analysis. It receives several arguments: * batfilename: the name of the batch file to be run (see EXECUTING All EXTERNAL PROGRAM -paq 274)s *+ basename: the short name model; * dir: the fll path to the model directory: * problemtypedir: the full path to the Problem Types directory: © idexe: the full path to gid: + args: an optional lst with other arguments. If it returns -cancel- ?? then the calculation is not started, is an optional message to be shown, + AfterRun Calculation: wil be called just after the analysis finishes. If it returns nowindow as a value then the window that inform about the finiched process will not be opened. It receives as arguments: * basename: the short name model; * dir: the fll path to the model directory: * problemtypedir: the full path to the Problem Types directory: + here: must be local or remote (remote if it vas run in a server machine, using ProcServer); * error: returns 2 if an calculation error w as detected; * errorfilename: an error filename with seme error explanation, or nothing if everything » as ok + ChangedLanguage: will be called when you change the current language. The argument is the new language (en, @5, .). Tt s used, for example, to update problem type custorrized menus, ete, © BeforeWriteCalcFileGIDProject: ll be called just before writing the calculation file. It is useful for validating sere parameters.Event procedures 71 If it returns -cancel- as a value then nothing will be written * file: the name of the output calculation file. + AfterWriteCalcFileGIDProject: wll be called just after writing the calculation file and before the calculation process. It s useful for renaming files, or cancelling the analysis If it returns -cancel- as a value then the calculation is not invoked * file: the name of the output calculation fle error: an error code if there is some problem writing the output calculation file. * BeforetransformProblemType: will be called just before transforming a model from 2 problem type to 2 new problem type version. IFit returns -canca/- as a value then the transformation will net be invoked, * file: the name of the model to be transformed; * oldproblemtype: the name of the previous problem type: * new problertype: the name of the problem type to be transformed. + AfterTransformProblemType: sll be called just after transforming a model from a problem type to a new problem type version. ‘The messages argument explains the transferring operations done. 1t must return 1 if there » ere modal changes dene in this procedure, 0 else. It returns ~cancel- as a special value, then the transformation messages w on't be shown, * file: the name of the model to be transformed; * oldproblemtype: the name of the previous problem type: * new problerrtype: the name of the problem type to be transformed. + TelCaleModelBoundaries: will be called when recalculating the bounding box, for example when user select "zoom frame" * useof: can be "GEOMETRYUSE”, "MESHUSE", "POSTUSE” or "GRAPHUS! This procedure must return xin yrrin 2rrin xmax ymax zmaz of the bounding box of the entities directly managed by the problemtype (this entities must be directly drau’n with the draw opengl command) If" is returned instead "xrrin ymin zrin xmax ymax zmaz” then any additional bounding box is considered. * AfterChangeBackground: will be called just after change some background property, like color, direction or image. * Before Copy /Move AfterCopy/Move: will be called just before or after use copy or move tod, * useof : could be GEOMETRYUSE or MESHUSE + transformation : could be ROTATION, TRANSLATION, MIRROR, SCALE, OFFSET, SWEEP or ALIGN + AfterCreatePoint/Line /Surface /Volume: »ll be called just after create the entity, providing its number + BeforeDeletePoint/Line /Surface/Volume: wil be called just before delete the entity, providing its number + AfterCreateLayer: will be called just after create the layer ‘name! + AfterRenameLayer: yl be called just after the layer ‘oldname’ has been renamed to ‘newname! * BeforeDeleteLayer: will be called just before delete the layer ‘name’ If it returns ~cancal- the layer deletion is cancelled. * AfterChangeLayer: will be called just after change some property of the layer ‘name! * ‘property’ could be ON, OFF, FROZEN, UNFROZEN, ALPHA , COLOR whit RRR, GGG, BBB, AAA from 0 to 255 + AfterChangeParentLayer: will be called when moving a layer to another parent of the tree. + AfterSetLayerToUse: will be called when setting ‘name! ax current layer to use + AfterSendToLayer: will be called when changing entities to the layer 'narne! + AfterCreateGroup: sirilar to layer commands + AfterRenameGroup: + BeforeDeleteGroup: wll be called just before delete the group ‘name! If it returns ~cancel- the deletion is cancelled, * AfterDeleteGroup: + AfterChangeGroup: property could be color, visible, state, alow ed_types + AfterGroupParentLayer: Will be called when moving a group to another parent of the tree, + AfterChangelicenceStatus: will be called when the licence status of GiD changes. Possible status could be "academic", "professional" or "ternporallyprofessional” * AfterCreateMaterial: will be called just after create the material ‘name! + AfterRenameMaterial: wil be called just after the mateial‘oldname’ has been renamed to ‘nen name! + BeforeDeleteMaterial: will be called just before delete the material ‘name! If it returns -cancel- the material deletion is cancelled © AfterChangeMaterial: ll be called just after change some field value of the material ‘name! changedfields jg alist with the index of the changed fields (index starting from 1) + AfterAssignMaterial: will be called just after arsign or unassign the material of some entities,Event procedures 72 name is the name of the new material. If tis "™ then the material has been unassigned leveltype: is the kind of entity, if could be For geometry: POINT_LT, LINE_LT, SURFACE_LT.VOLUME_LT For mesh: ELEM_LT, * BeforeMeshErrors: filename is the full path to the file that has information about the meshing errors, Retuning -cancel- the standard 'Mesh error window’ won't be opened + BeforeResultReadErrors: filename iz the results file that was read, mag is the error message, format provide Information about the kind of file: cand be "GID_RESULTS_FORMAT’, "3DSTUDIO_FORMAT", “TECPLOT_FORMAT", "FEMAP_FORMAT", "XYZ_FORMAT" Retuning -cancel- the standard 'Read results errar window w on't be opened + AfterProcess: will be called just after GiD has finished the process of 'words! (the parameter is_rotation==1 if the command is a view movement). This event could be interesting for some tricks, like save processed commands in a batch fle, or send the commands to be processed by other GID slave, etc + AfterCreateVolumeset, AfterCreateSurfaceSet, AfterCreateCutset: will be called just after 2 postprocess set of volumes, surfaces or cuts is created, providing its name * AfterRenameVolumeset, AfterRenamesurfaceSet, AfterRenameCutSet: ill be called just after 2 postprocess set of volumes, surfaces or cuts has been renamed providing its old and current name * BeforeDeleteVolumeset, BeforeDeleteSurfaceSet,BeforeDeleteCutSet: will be called just before a postprocess set of volumes, surfaces or cuts will be deleted created, providing its name, If the procedure return ~cancel~ then the set won't be deleted * AfterChangeViewMode: usecfi can be "GEOMETRYUSE", "MESHUS! + AfterCreateGraph: ill be called when a new graph is created + AfterRenameGraph: + BeforeDeleteGraph: will be called just before delete the graph ‘name’ If it returns -cancel- the deletion is cancelled, + AfterDeleteGraph: + AfterChangeGrap! values, visible + AfterCreateGraphSet: will be called when a new graphset is crested © AfterRenameGraphSet: * BeforeDeleteGraph Set: will be called just before delete the graphset ‘name’ If it returns ~cancel- the deletion is cancelled, © AfterDeleteGraphSet: * AfterChangeGraphSet: property could be! legend_location, ttle_visible + AfterSetGraphSetToUse: sill be called when setting ‘name’ as current graphset to use 'POSTUSE" or "GRAPHUSE: property could be: coler, contour fill, ine_pattem, line width, pattern factor, point_size, style, Note: To use Tel to improve the capabilities of writing the calculations file, itis possible to use the command ‘tl in the template file (-bas file); see Specific commands for details, .2 GD_Process function GiD_Process command_t command? ‘Tel command used to execute GID commands, ‘This is a simple function, but a very pov erful one, It is used to enter commands directly inside the central event manager “The commands have the same form as those typed in the command line within GID. You have to enter exactly the same sequence as you would do interactively, including the escape sequences (using the word escape) and selecting the menus and operations used, You can obtain the exact commands that GiD needs by checking the Right buttons menu (Utlities -> Tools -> Toolbars). It is also possible to save a batch file (Utilities -> Preferences) where the commands used during the GID session can be checked. Here is 2 simple example to create one line: Note: Mescape is a multiple ‘escape’ command, to go to the top of the commands tree.GiD_Info function 73 .2 GD_Info function GiD_Info “Tel command used to obtain information about the current GiD project ‘This function provides any information about GID, the current data or the state of any task inside the application. Depending on the arguments introduced after the GiD_Info sentence, GiD will output different information: 2.1 automatictolerance GiD_Info AutomaticTolerance This command returns the value of the Import Tolerance used in the project. This value is defined in the Preferences window under Import 2.2 conditions GiD_Info conditions ovpnt | oviine | ovsurf | owl | ovlayer | ovgroup This command returns a list of the conditions in the project. One of the arguments ovpnt, ovline, ovsurf, ovvol must be given to indicate the type of condition required, respectively, conditions over points, lines, surfaces or volumes. Instead of ovpnt, ovline, ovsurf, evel, ovlayer, evgroup the follow ing options are also available: + Pinterval ? 24ocalaxes | localaxesmat | localaxescenter | localaxesmatcenter? ?geometry|mesh|groups ?|-count? if a condition name is given, the command returns the properties of that condition. It is also possible to add the options geometry|mesh |groups. and all geometry or mesh entities that have this condition assigned will be returned in a list if its integer identifiers. The word ‘groups’ must be used only if the condition was declared as ‘over groups! and then the list contain its names. 1f interval "intv" is set, then the conditions on this interval ("intv"=1,,..n) are returned instead of those on the current interval. If docalaxes is set, then the three numbers that are the three Euler angles that define a local axes system are also returned (only for conditions with local axes, see DATA>Local Axes from Reference Manual). Selecting -localaxesmat, the nine numbers that define the transformation matrix of a vactor from the local axes ystern to the global one are returned. Hf Jocalaxescenter is set, then the three Euler angles and the local axis center are also returned. Selecting ‘localaxesmatcenter returns the nine matrix numbers and the center. ‘Adding the number id of an entity ( ) after the options mesh or geometry, the command returns the value of the condition assigned to that entity. It is possible to specify a range of ids with the syntax if -count is specified then the amount of entities with the condition is returned instead of thelist of entities and its values. Other options available ifthe condition name is given are otherfields: to get some special fields of that condition book: to get the book of the condition. condmeshtype: to know how the condition was defined to be applied on mesh entities: ever nodes, over body elements, over face elements, over face elements multiple canrepeat: to know how the condition » as defined to be applied only once or more to the same entity: values are O or 1 roupallow: to know how the condition ‘over groups’ 1 as defined to allow the group to have entities of one or more kinds of {points lines surfaces volumes nodes elements Faces} * books: If this option is given, a lst of the condition books of the project is returned, Examples: owe: (CE 8 ~ 2928) (E 2a) (21 242))conditions 74 cue: (EE = (4 71288sc028ae087 1 5707Se92e7¢485ee 0-0) Hm 0.9 0.2 HAWS) 2.3 coordinates GiD_Info Coordinates ?-no_model? | [geometry|mesh] This command raturns the coordinates (x,y,2) of a given point or node. If -no_model flag is specified then entities are stored in a special container, it doesn't belong to the model 3.4 check GiD_Info check This command returns some specialized entities chack For lines it has the following syntax: GiD_Info check line isclosed For surfaces GiD_Info check surface isclosed | isdegeneratedboundary | selfintersection And for volumes: GiD_Info check volume orientation | boundaryclose The result for each argument is: * Hine | surface | volume: Type of entity. + : The number of an entity. + isclosed: For lines: 1 if start point is equal to end point, 0 otherwise. For surfaces: A surface is closed if its coordinate curves (of the full underlying surface) with parameter 0 and 1 are equal. It returns a bit encoded combination of closed directions: 0 if tis not closed, 1 ifit is closed in u, 2 ifit is closed in v, 3 iit is closed in both u and v directions. + isdageneratedboundary: A surface is degenerated if some boundary in parameter space (south, east, north or wast) bacomas 2 point in 3d space. It raturns a bit encoded combination of degenerated boundaries, for example 0 if tis not degenerated, 9: * selfintersection: Intersections check between surface boundary lines. It returns a list of detected intersections Each itam contains the two line numbers and their paramater values * orientation: For volumes, it raturns a two-item list. The first item is the number of bad oriented volume surfaces, ‘90422 if south and wast boundaries are degenerated. land the second item is a list of these surfaces" numbers. + boundaryelose: For volumes, 2 boundary is topologically closed if each line is shared by two volume surfaces. It returns 0 if itis not closed and must be corractad, or 1 ifit iz closed. Example: Jn: GiD_info check volume $ orientation out: 2 {4 38) 2.5 events This command returns a sorted list with the names of the GID Tel event procedures, that could be something like this: After XX: AfterAssigntiaterial AfterChangeBackground AfterChangelayer AfterChangeLicenceStatus AfterChangeMaterial AfterChangeParentLayer AfterChangeParentGroup AfterChangeViewHlode AfterCopy AfterCreateCutSet AfterCreateDimension AfterCresteGroup AfterCreatelayer AfterCreateline AfterCreatatlaterial AfterCreatePoint AfterCreateSurface AfterCraateSurfaceSat AfterCreateVolume AfterCresteVolumasat AfterDeleteGroup AfterDrawhodel AfterLoadGIDProject AftertieshGeneration Aftertiove AfterOpenfileevents 75 AfterRedraw AfterRenameCutSet AfterRenameGroup AfterRenamelayer AfterRenamelaterial AfterRenamaSurfaceSet AfterRenameVolumaSet AfterRenumbar AfterRunCaleulation AfterSaveAs AfterSavelmage AfterSetLayerToUse AfterTransformProblemTyp= AfterWriteCalcFileGIDProject BeforeXX: BeforeCopy BeforeDeleteCutSet BeforeDeleteDimension BeforeDelateGroup BeforeDeletelayer BeforeDaleteLine BeforeDeletatiaterial BeforeDeletePoint BeforeDeleteSurface BaforaDaleteSurfaceSet BaforeDeleteVolume BeforeDalateVolumeSet BeforeintGIDPostProcess BeforateshErrors BaforalleshGeneration Beforetiove BeforeRezultReadErrors BeforeRunCalculation BeforetransformProblemT ype BeforalWriteCalcFileGIDProject Other: ChangedLanguage EndGIDPostProcess EndGIDProject IntGIDPostProcess IntGIDProjact Load 1DProjact LoadResultsGI0PostProcess SaveClDProjact SelactIDBatFile TelCaletiodelBoundaries ‘vant procedures “pag. 65 3.6 gendata GiD_Info gendata ‘This command returns the information entered in the Problem Data window (see Problem and intervals data file (rb). ‘The following options are available: * [otherfields]: itis possible to add this option to get the additional fields from the Problern Data window + [books]: If this option is given, a lst of the Prablem Data books in the project is returned, Example: Unie_Syotenf CBE (SI, CGS User) SI Ticle MLeiele” 8.3.7 geometry GiD_Info Geometry ‘This command gives the user information about the geometry in the project: For each entity, there are tre possibilities: + [NumPoints]: Returns the total number of points in the model. *+ [Numtines]: Returns the total number of lines, + [Numsurfaces]: Returns the total number of surfaces. + [NumVolumes]: Returns the total number of volumes. + [NumDimensions]: Returns the total nurrber of dimensions. + [MaxNumPoints]: Returns the maximum point number used (can be higher than NurPeints). [MaxeNumtines]: Returns the maximum line number used. [MaxeNumSurfaces]: Returns the maximum surface number used. [MaxeNumVolumes]: Returns the maximum volume number used. [MaxeNumDimensions]: Returns the maximum dimension number used, 8.3.8 gidbits GiD_Info GiDbits If Gi is a x32 binary executable, then this command returns 32. If GID is a x64 binary executable, then this command returns 64.gidversion 76 3.9 gidversion GiD_Info GiDVersion This command raturns the GiD version number. For example 10.0.8 8.3.10 graphcenter GiD_Info graphcenter, This command returns the coordinates (x,y,2) of the cantar of rotation 2.11 intvdata GiD_Info intvdata ‘This command returns a lst of the interval data in the project (see Problem and intervals datafile (.pr6)) ‘The following options are available: + -interval : To get data from an interval different from the number 0 (default). * [otherfields]: It is possible to add this option to get the additional fields from the Interval Data window + [books]: if this option is given, a lst ofthe Interval Data books in the project is returned, © [num]: If this option is given, a list of tue natural numbers is returned. The first element of the list is the current interval and the second element is the total number of intervals 8.3.12 ispointinside GiD_Info IsPointinside GiD_Info IsPointInside ?-no_model? ?-tolerance ? Line| Surface| Volume { <2>} This commands returns 1 ifthe point {x y 2) is inside the specified volume/surface/curve, or 0 flies outside If -no_model flag is specified then entities are stored in a special container, it doesn't belong to the mode! 8.3.13 layers GiD_Info layers “This command returns a list of the layers in the project: These options are also available: + : If a layer name is given, the command returns the properties of that layer. + -on: Returns a list of the visible layers. + -off: Returns a list of the hidden layers, + chasbacklayers: Returns 1 if the project has entities inside back layers. © Note: GiD_Info back layers returns alist with the back layers Example: + -bbox ?-use geometry|mesh? Returns ty coordinates (xc,y1,21,*2,y2,22) which define the bounding box of the entities that belong to the list of layers. If the option -use geometrylmesh is used, the command returns the bounding box of the geometry or the bounding box of the mesh. If the list of layers is empty, the maximum bounding box is returned + 2-count? -entities ?-elementtype ? ?-higherentity ?: One of the following ‘arguments rust be given for : nodes, elements, points, lines, surfaces or volumes. A layer name ‘rust also be given. The command will return the nodes, elements, points, lines surfaces or volumes of that layer If -count is set then the amound of entities is returned instead of the list of its ids. For elements itis possible to specify -elementtype to get only this Kind of elements. -higherentity Alloy to get only entities with this amount of higherentities, + -canbedeleted returns a list with two items: a boolean Ol to know if layer or its child layers have some entity or parts in back layer or conditions over the layer, the second itern is a message explaining the cause to not delete it directly. Examples:layers 7 3.14 listmassproperties GiD_Info ListMassProperties ?-no_model? Points|Lines| Surfaces | Volumes | Nodes | Elements With the option more, more information is returned about the entity. The -more option used with lines returns the length of the line, its radius (arcs), and the list of surfaces which are higher entities of that line; used with elements it returns the type of element, its number of nodes and its volume. Example 1 out: Example 2 out: Mon: 12 HighexEneiey: 0 conditions: 0 material: 0 Example 3 (using -more). out:list_entities 79 LUNE (nore) Lengeh=21242 Radius=100000 2.16 localaxes GiD_Info localaxes ?? ?-localaxesmat?info localaxes Returns a list with all the user defined local axes. info localaxes returns the paramaters (three euler angles and the center) that define the local axes called info localaxes -localaxesmat instead of raturning the three euler angles, it returns the nine numbers that define the transformation matrix of a vactor from the local axes system to the global one 8.3.17 magnitudes GiD_Info magnitudes 0] 1 2 units|basic|reference? Return information about units and the conversion factor betw een units of a magnitude, iD_Info magnitudes 0 return a list with the available default magnitude names of GiD and iD_Info magnitudes 2 return alist with the available magnitude names of the project is the name of the magnitude, like LENGTH or other magnitudes that could be defined by the problemtype iD_Info magnitudes 0 LENGTH units return a list ike this {2.0m mO mr} (400 em {em O em} {4.0643 mm mm mm} with the multiplication factor to convert the length magnitude from the reference unit to another unit. 2.18 materials GiD_Info materials ‘This command returns a lst of the materials in the project. GiD_Info materials () returns only the materials that belong to the book ) These options are also available: + : If 2 material name is given, its properties are returned. * Ikis also possible to add the option otherfields to get the fields of that material, or the option book to get the book of that material. * books: If this option is given, a list of the material books in the project is returned, examples out: "1 Density 7850" Giblingo materials (prodiles) 8.3.19 mesh, GiD_Info Mesh ‘This command gives the user information about the selected mesh in the project Without arguments it returns 1 if there is mesh, follow ed by alist with all types of element used in the mesh, + NumElements : returns the number of elements of the mesh. Flemtype can be: Line | Triangle | Quadrilateral | Tetrahedra | Hexahedra | Prism | Pyramid | Point | Sphere | Circle | Any. node is the number of nodes of an element: + NumNodes: Returns the total number of nodes of the mesh.+ MaxNumElements: Returns the maximum element number. + MaxNumNodes: Returns the maximum node number + 2-pre | -post -step ?: To specify to use the preproces or postprocess mesh, and the time step if it changes along the time. + Elements ?? 22 ?-sublist]-array? ?-avoid_frozen_layers? : Returns list ith the element number, the connectivities, radius ifit is a sphere, normal if itis a circle, and the material umber, from 'frst_id' to last_id, if they are specified. + Nodes ? ?? ?-sublist|-array? ?-avoid_frozen_layers?: Returns a list with the node number and x y 2 coordinates, from 'first_id' to 'lact_id’ if they are spacified Modifiers: -sublist : Instead of a plane list returns each result item as a Te lst (enclosed in braces) array : Instead of a plane list it returs the reculs as a lit of vectors (more efficient) In fact with -array itis returned an ‘objarray': a Tcl_Obj object specialized for arrays, implemented as a Tel package named ‘obj array’. (for more information see scripts\objarray\obj array pd) -avoid_frozen_layers : to ignore nodes or elements of frozen layers Examples: 3.20 meshquality GiD_Info Mesh Quality This command raturns a list of numbers. These numbers are the Y relative values of the graph shown in the option Meshing -> Mesh quality (see NESH>Mash Quality from Referance Manual) and two additional real numbers with the minimum and maximmurn limits This command has the following arguments: + Minangle / MaxAngle / ElemSize / ElemMinEdge / ElemMaxEdge / ElemShapeQuality / ElemMinJacobian / Radius: quality criterion * Line / Triangle / Tetrahedra / Quadrilateral / Hexahedra / Prism / Pyramid / Point / Sphere / Circle type of element. + : e.g. minimum number of degrees accepted. + : 2.9. maximum number of degrees accepted. ‘# min_value and max_value are set to 0 then limits will be automatically set to the minimum and maximum of the mash + : number of divisions. Example: 3.21 opengl GiD_Info Opencl Returns information about the Opengl/slew version and renderer. 8.3.22 ortholimits GiD_Info ortholimits This command returns a list (Left, Right, Bottom, Top, Hear, Far, Ext) of the limits of the geometry in the project In perspective mode near and far have the perspective distance substracted. 2.23 bounding_box GiD_Info bounding_box 2pointiline|surface|volume ? “This command returns a list (rin x_max y_min y_max z min 2 max} of the bounding box that contains the visualized mode! with the current settings (on layers). It also could return the bounding box of a geometric entity, specified by its category and .parametric 81 3.24 parametric GiD_Info parametric This command returns geometric information (coordinates, derivates, etc.) about parametric lines or surfaces, For lines it has the following syntax: GiD_Info parametric ?-no_model? line entity id coord | derivt | deriv_tt | t fromcoord | t_fromrelativelength | length_to_t|t| xyz And for surfaces: GiD_Info parametric ?-no_model? surface entity_id coord | deriv_u | deriv_y | deriv_uu | deriv_w | deriv_uv | normal | uv_fromcoord | maincurvatures|uv_projection_z_fromcoord: uv | xyz If -no_model flag is specified then entities are stored in a special container, it doesn't belong to the mode! The result for each argument is: * line|surface: Type of entity. + entity_id: The number of an entity. + coord: 3D coordinate of the point with parameter t (line) or u,v (surface) + deriv_t First curve derivative at parameter t © deriv_tt: Sacond curve derivative at parameter t + € fromcoord: t parameter for 2 3D point. + t fromrelativelength: parameter corresponding to 2 relative (from 0 to 1) arc length t * length_to_t: lenght of the curve until the parameter t (if =1.0 then it is the total lengh) * deriv ideriv_v: First partial u or v surface derivatives. © deriv_uujderiv_wyjderiv_uv: Second surface partial derivatives. + normal: Unitary surface normal at u,v parameters. + uv_fromcoord: u,v space parameters for 2 3D point + maincurvatures: return a list with 8 numbers: vix viy viz v2x v2y v2z cl 2 vix viy viz ; first main curvature vector direction (normalized) v2x v2y v2z : second main curvature vactor direction (normalized) ef c2: main curvature values + uv_projection_z_fromcoord: to get the location uv of a point x y projected in direction z on 2 surface (the 2 of the point must not be supplied) e.g: a0 wv (GiD_Inéo paramctric surface fid wy_projection_» fremcoerd fx fy] Note: The vector derivatives are not normalized Example: out: 8.060864 ~1.4¢2580 0.000000, 3.25 perspectivefactor GiD_Info perspectivefactor This command returns which perspective factor is currently being used in the project. 8.3.26 postprocess GiD_Info postproces + GiD_info postproces arewein This command ratuens YES if the user is in the GiD postprocess, and NO, if not. * GiD_Info postprocess get This command returns information about the GiD postprocess. The following options are available. |_volumesets: Returns a list of all volumes. « all_surfacesets: Returns a list ofall surfaces |_cutsets: Returns a lst ofall cuts |_graphs: Returns a list of all graphs + all_volumes_colors: Returns a list of the volume colors used in the project. Colors are represented in RGB hexadecimal format. Example: #000000 would be black, and #FFFFEF would be white + all_surfaces_colors: Returns a list of the surface colors used in the project. Colors are represented in RGBpostprocess 82 hexadecimal format. Example: #000000 would be black, and #FFFFEF would be white + all_cuts_colors : Returns a list of the cut colors used in the project. Colors are represented in RGB hexadecimal format. Example: #000000 would be black, and #FFFEFF would be white © cuur_volumes: Returns a list of the visible volumes. + cur_surfaces: Returns 2 list ofthe visible surfaces. + cuur_cuts: Returns a list of the visible cute. + all_display_styles: Returns a lst ofall types of display styles available + cur_display_style: Returns the currant display style + all_display_renders: Returns a list of all types of rendering available + cur_display_render: Returns the current rendering method. + all_display_culling: Returns 2 list ofall types of culling available + cur_display_culling: Returns the current culling visualization + cur_display_transparence: Returns Opaque or Transparent depending on the current transparency. Transparency is chozen by the user in the Select & Display Style window. + cur_display_body_type: Returns Massive if the option Massive is selected in the Select & Display Style window. It returns Hollow if that option is not activated. + all_analysis: Returns a lst ofall analyses in the project. steps “analysis_name": Returns the numbar of steps of "analysis_name" + cur_analysis: Returns the name of the current analysis. ccur_step: Raturns the current step. + is_mesh_variable_along_steps : Returns 1 ifthe postprocess mash is changing along the time + all_results_views: Returns all available result views. + cur_results_view: Returns the current result view. + cur_results list This option has one more argument: the kind of result visualization must be given. The available hinds of result visualization are given by the option all_results_views. The command returns a list of all the results that can be represented with that visualization in the current step of the current analysis. + results list: This option has three arguments: the first argument is the kind of result visualization. The available hinds of result visualization are given by the option all_results_views. The second argument is the analysis name. The third argument is the step number. The command returns a list of all the results that can be represented with that visualization in the given step. + cur_result’ Returns the currant selected result. The kind of result ic selected by the user in the View results window + cur_components_list "result_name" Returns a lis of all the components of the result "result_name", + cur_component: Returns the current component of the currant result + main_geom_state: Returns whether the main geomatry is Deformed or Original + main_geom_all_deform: Returns list of all the deformation variables (vectors) of the main gaometry. + main_geom_cur_deform: Return: the currant deformation variable (vactors) of the main geomatry. + main_geom_cur_step: Returns the main geometry currant step + main_geom_cur_anal: Returns the main geometry current analysic. + main_geom_cur_factor: Returns the main geometry current deformation factor. + show_geom_state: Returns whether the reference geometry is Deformed or Original. + show_geom_cur_deform: Returns the currant deformation variable (vactors) of the reference geometry. + show_geom_cur_analysis: Returns the reference geometry current analysis. + show_geom_cur_step: Returns the reference geometry current step. display_styles: Returns a list ofall available display styles for sosurfaces display_style: Returns the current display style for isosurfaces. display_renders: Returns a list of all types of rendering available for isosurfaces. display_render: Returns the current rendering method for isosurfaces + ise_cur_display_transparence: Returns Opaque or Transparent depending on the current transparency of isosurfaces, + contou imits: Returns the minimum and maximum value of the contour limits. Before each value, the word STD ‘appears ifthe contour limit value is the default value, and USER if tis defined by the user. + animationformat: Returns the default animation format. + cur_show_conditions: Returns the option selected in the Con Style window. (Possible values: Geometry Mesh Hone) + all_show_conditions: Returns all the options available in the Conditions combo box of the Select & Display Style window. (Geometry Nesh None) jons combo box of the Select & Displaypostprocess 83 + cur_contour_limits: Returns the minimum and maximum valve of the current value + current_color_scale: Returns a list of the colors used for the color scale; the first element of the list is the number of colors. Each color is represented in RGB hexadecimal format. Example: #000000 would be black, and “#FEFEFF would be white + graphs_option: ?-alloy ed_values? | whith -allow ed_values flag tis returned a list with the possible values of the property instead of the current property value To get graphset properties ‘ could be: Currentstyle Grids MainTitle TitleVisible LegendLocation CoordType AngleAxis ‘AngleUnit Shou OrigAxes Show RadMarks ColerOrig ColorRad PatRtad OutlineOnModel Show Graphs X_axls Y_axis Show ModalView LineWidth Pointsize ‘To ge graph properties (must specify also the ) could be: Style Color ColorAsCFill LineWidth Pattern PatternFactor PointSize Title NumResults Resultsx ResulteY LabelX LabelY Visible 8.3.27 problemtypepath GiD_Info problemtypepath This command raturns the absolute path to the currant problem type. 3.28 project GiD_Info Project ? ‘This command returns information about the project. More precisely, it returns a lst mith * Problem type name. + Current modal name + "There are changes’ flag. + Current layer to use. + Active part (GEOMETRYUSE, MESHUSE, POSTUSE or GRAPHUSE). + Quadratic problem flag Drawing type (normal, polygons, render, postprocess). + WOPOST or YESPOST. + Debug or nodebug. * GiD temporary directory + Must regenerate the mesh flag (0 er 4). * Last element size used for meshing (NONE if there is no mesh), + Backgroundfilename is the name of a background mesh fileto assign mesh sizes. + RequireMeshSize. (1 if all sizes are specified by the number of divisions, then user is not required to specify the mach size) + RecommendedMeshSize, (The value of the mesh size that the program will recommend, based on the model size) It s possible to ask for a single item only rather than the whole list, mith equal to: ProblemType | MedelName | AreChanges | LayerToUse | ViewMode | Quadratic | RenderMode | ExistPost | Debug | TmpDirectory | MustReMesh | Lastélementsize | BackgroundFilename | RequireMeshSize | RecommendedMeshSize Example! ove: Nemaued e:\models\cas_model 1 1ayes? MESHUSE 0 nosmal YVESPOST nodebug C:\TEMP\gidz 0 1.4" ous: *el\models\ eas node 8.3.29 rgbdefaultbackground GiD_Info RGBDefaultBackground This command returns the default background color in RGB. The format is three 8 bit numbers separated by # Example: 255#255#255 would be whiteunitssystems 84 3.30 unitssystems GiD_Info unitssystems ?gid|prj|usersys |modunit|prbsys|udstate|magused? return information about the sytems of units GiD_Info unitssystems return 1 ifthe problerrtype is using units, 0 else GiD_Info unitesystems medunit return information about the current length units of the model it return a list with three items like "LENGTH 1 0°, the second one is the index of the current length unit 2.31 variables GiD_Info variables -pre|-post| ‘This command returns the value of the variable indicated. GID variables can be found in the Right buttons manu (see UTILITIES> Tools from Reference Manual), under the option Uslities > Variables: Note: this command is deprecated to get a variable value, The more modern GiD_Set command can be used to get or set the value of a GiD variable, look into Special Tel commands>Other for more information. If the argument is -pre or -post then it returns a sorted list of the GiD variables of preprocess or postprocess respectivelly 2.32 view GiD_Info view This command returns the current view parameters. Something like {x -13.41030216217081 13.41030216217041} {y 10.724431991577148 -10.724431991577148) {2 -30.0 30.0} {2 10.0} (v0.0 0.00.0} {r 1.0) fm 1.0 0.00.00.00.0 100.00.00.00.0 1.0 0.00.00.00.0 1.0} {c 0.00.0 0.0} {pd 0.0} {pno 0.0} {pf 0.0} {oF 4.0) {pv 0.0} {HlowUse 0? {DrawingType 0} {LightVector 90.0 90.0 150.0 0.0) See VIEW>View entry>Save/Read View of Reference Manual for 2 brief axplanation of this parameters }-4 Special Tel commands GiD add to the standard Tel/Tk keywords some extra commands, to do specific thinks, 4.1 Geometry GiD_Geometry ?-no_model? create|delete|get!|list point |line|surface|volume |append To create, delete, get data of list the identifiers of geometric entities: + lappend: is the entity identifier (integer > 0). You can use the ward ‘append’ to set a new number automatically. + : is all the geometric definition data (create) or a selection specification (delete, get or list): If -no_model flag is specified then entities are stored in a special container, it doesn't belong to the model ro make new geometric entities + Gid_Geometry create volume | append layer numsurfaces {surfacel verso}... ?contactvolume <? for contactvolume is necessary to specify the + a vector of 16 reals representing a 4xé transformation matrix that maps surface into surface2 + Gid_Geometry create surface | append plsurface | nurbssurface | coonsurface |_meshsurface | contactsurface layer numlines ?? {lined versot} ... ‘ must be provided only for NURBS surfaces and are this variables: u_degree v_dagree numpoints_u nurmpoints_v istrimmed istational - depends of each entity type (see get command) * Gid_Geometry create line append nurbsline layer inipeint endpoint degree numpoints isrational {pointt_x pointt_y pointt_z 2pointi_w7} ... knot_t Instead the NURBS parameters is possible to create a curve that interpolates list of points (also tangents at startGeometry 85 and end can be specified) GiD_Geometry create line | append nurbsline layer inipoint endpoint -interpolate numpoints {pi_x ply pia}. {pn_x pn_y pn_s} ?-tangants {t0_x t0_y t0_s} {t1_xtt_y ts}? + GiD_Geometry create line | append stline layer inipoint endpoint + Gid_Geometry create point |append layer point_x point_y point_z delete: to erase model entities * GiD_Geometry delete point|line|surfacelvolume with : num numainumb numa: layet:layer_name get: to obtain al the geometrical data to define a single entity * GiD_Geometry get pointlline| =urfacel volume ith : nur 2line_uv ? line_uv extra arguments must be only used in case of nurbs surfaces, to get the information of the < curve (integer from 1 to the number of trimming curves) on the surface, defined in its uv space parameter, * GiD_Geometry get point will return: ‘ is the layer name ‘ the coordinates x y 2 + GiD_Geometry get line will returns - ‘ can be: stline, nurbsling, ardiine, polyline < is the layer name ‘

identifier of start point ‘ identifier of end point ‘ depends of each entity type stline: nothing rurbsline: {xy 2202 (xy 2207} ShO> wa degree number of contral points < 1 if rational, else 0 {si yi 2wi2} control points coordinates. If rational wi is the » eight knots ardine: {xe ye} <1> <2a> {mit ... m44) {xc ye} 2D center <1> radius start angle (rad) end angle (rad) {md ... md} transformation 4x4 matrix (the identity for 2 2D case) mn ...3 is a rotation 3x3 matrix m4 ,..m34 is a translation 3x. vactor mn is an scale factor nf... 43 must be 0 polyline: net implemented + Gid_Geometry get surface will return: - ?? {It 02}... {Inl onl} ‘ can be: nurbssurface plsurface coonsurface meshsurface < is the layer name ‘ number of boundary lines (including holes) “ only for NURBS surfaces ( ) {li 0} identifier of line and its orientation for the surface (1 if opposite to the line advance, 0 else) Note: turning left of a line with orientation O we go inside the surface.Geometry 86 depends of each entity type pleurface: nathing coonsurface: nething nurbssurface Oxy 2 2 2}1a. fey 2 20 7}moxny va. wo degree in u, v direction number of control points in each direction < 1 if rational, 0 else {0 yi 21 02} control points coordinates. If rational wi is the w eight - knots in each direction meshsurface: nn ne node {xs 71 21.1 xan Yon Zan} {an bi c1 2ch? «1. ane Bre Gne ?dhe?} rnni number of nodes ne: number or elements (triangles or quadrilaterals) node: number of nodes by element: 3 or 4 % yi 21 coordinates abi c di: connectivities (d only for quadrlaterals) GiD_Geometry get surface line_uv : will return the information of the curve in uv space of the surface , with similar format as GiD_Geometry get ine in case of a nurbs curve. * Gid_Geometry get volume will returns {s1 of} ... {snl onl} is the layer name number of boundary surfaces (including holes) {si of} identifier of surface and its orientation for the volume (1. if opposite to the surface normal, 0 else) Note: the normal of a surface with orientation 0 points inside the volume list: to get alist of entity identifiers of a range or inside some layer + Gid_Geometry list point | line | surface | volume with : | : | :end layer: unrendered (only valid for surface) Examples: Creation of a new NURBS surface: GiD_Geoneczy creave surface 1 nusbssusface Layer0 @112200 (11) (44) 2D (2 1, (0.17785 €.s€0381 0-0} (-6.42092700 €.SE0841SS 0.0) (0.1779S400 0.28510 0.0) \ (8.4002 0.28510 0.0) 0.0.0.0 1.0 1.00.00.01.010 Get the list of points of the layer named 'layer_name' Get the list of problematic surfaces that couldn't be rendered 4.2 Mesh 4.2.1 Preprocess mesh GiD_Mesh create|delete|editiget To create, delete, modify or know information about mesh nodes or elements of the preprocess: GiD_Mesh create node |append + lappend: is the identifier (integer > 0) for the node. You can use the word ‘append’ to set a nev number automatically. The number of the crested entity is returned as the result. + are the node coordinates. Ifthe 2 coordinate is missing, itis set to 2=0.0. GiD_Mesh create element |append ??Preprocess mesh 87, + |append: is the identifier (integer > 0) for the node. You can use the word ‘append’ to set a nev number automatically. The number of the crested entity is returned as the result. + : must be one of "Point | Line | Triangle | Quadrilateral | Tetrahedra | Hexahedra | Prism | Pyramid | Sphere | Circle" + is the number of nodes an element has + is a Tel list with the element connectivities + is the element radius, only for sphere and circle elements + is the normal of the plane that contain the circle, must be specified for circle elements only + is the optional element material name GiD_Mesh delete node|element < is the identifier (integer > 0) for the node or element to be deleted, It is possible to use a list of multiple ids GiD_Mesh editnode GiD_Mesh edit clement ? Nonede> Same syntax as create GiD_Mesh get node It return the list: <2> GiD_Mesh get element ?face|face_linear ? + is the identifier (integer > 0) for the element to be asked + face optional, instead of the element nodes it returns the nodes of the face, frst the linear corner nodes and then the quadratic nodes + face_linear optional, instead of the element nodes it returns only the linear corner nodes, also is the element is quadratic + is the local face index from 1 to the number of faces of the element ‘get elerment return the list: ... ‘get element facelface_linear: ... Examples: GiD_Mesh create node append (1.5 9.4e2 €.0) GaDlMeah create clenent 50 triangle 2 (715 2) steel GaDlMeah delete element (58 60) 8.4.2.2 Cartesian grid This command is only valid for preprocess GiD_Cartesian get|set ngridpoints|boxsize|comer| dimension |coordinates|iscartesian “To get and set cartesian grid properties + ngridpoints: the number of values of the grid axis on each direction x, y.2 (3 integers) + boxsize: the size of the box of the grid en each direction (3 reals) * commer: the location of the low er-left corner of the grid box (3 reals) * dimension: the dimension of the atid: 2 for 2D or 3 for 3D + coordinates: the list of rid coordinates on each direction (ntny+tnz reals) + iscartesian: return 1 i current mach is cartesian, 0 else 8.4.2.3 Postprocess mesh GiD_MeshPost create ?-zere_based_array? ?? 2? To create a postprocess mesh, ‘This command create all mesh nodes and elements in a single step (unlike GiD_Mesh that create each node or element one by one) + : the name of the mesh + : must be one of "point | line | triangle | quadrilateral | tetrahedra | hexahedra | prism | pyramid | sphere | circle” + : is the number of nodes an element has. All elements of the mesh must have the samePostprocess mesh. 88 number of nodes + -zero_based_array: optional flag. By default node and element indexes start from 1, but setting this flag indexes rust start from 0, + : list of node indentifiers. fit is an empty list them numeration is implicitly increasing. + : a list of real numbers with the thee coordinates of each node {x0 yd 20.» xnm yon-t 2nn-t} + : list of elerment indentifiers. If itis an empty list them numeration is implicitly increasing, + : a list of integers with the nodes of each element: the id of each node is the lacation on the vactor of nodes, starting from 0 + : + only for spheres, Is alist of reals with the radius or each sphere {fo «re + ionly for circles. Is a list of reals with the radius and normal to the plane or each circle Lg Pp AY Me Fed nes AYE Maes + : optional color components, to set the mesh color. rgb a are the red, green, blue and alpha transparency components of the coler, rust be real numbers from 0.0 to 1.0. If the color is not specified, an automatic color will be set 4.3 Groups + GiD_Groups create To create a nex group. must be the full name (2.9, if 2 group 8 has as parent A then must use as fullname A//8) + GiD_Groups delete To delete a group * GiD_Groups edit rename|color|visible|allowed_types|parent|state ‘To modify group properties: + rename: change its name + color: set the color to draw its entities (with format #rrggbbaa) * visible: set visibility of its entities (0 or 1) + allow ed_types: set the lit type of geometric or mesh entities allow ed to be in the group, rust be a list with some of {points lines surfaces volumes nodes elements faces) * parent: to change the parent of group * state: to change the groups state (normal, disabled or hidden). hidden groups are not listed or visible in window = * GiD_Groups get color|visible|allowed_types|num_entities |jnum_conditions |id|parent|state To obtain the current value of some property’ + num_entities: the total number of geometric or mesh entities that belong to the group + num_conditions: the total number of conditions applied to the group + id: the numeric identifier of the group + GiD_Groups list?? ‘To get the list of fullnames of the current groups. If a parent is specified, then only relative names of child groups willbe listed. Root parent could be specified with an empty string” + GiD_Groups window open|cose Show or hide the groups window * GiD_Groups exists Return 1 if group exists, 0 else + GiD_Groups is_forbidden_name Return 1 if group name has forbidden syntax + GiD_Groups draw { ... } Starts drawing the specified groups * GiD_Groups end_draw Finish drawing groups. 4.3.2 Entities GiD_Entities Groups assign|unassign get|entity_groupsEntities 89 ‘To handle the entities that belong to groups + GiD_EntitiesGroups assign |unassign get ?-also_lower_entities? ‘To add, remove or know entities of a group * GiD_EntitiesGroups assign ‘To assing the selection of entities of kind over to the group isthe full name of the group <-alzo_lower_entities> is an optional flag, to select also all low er entities of the selected ones (e.g, curves and points of the selected surfaces) could be points, lines, surfaces, volumes, nodes, elements, faces, all_geometry, all mesh is alist of integer entity id's starting from 1. In case of faces it is a lit with 2 iterns, the first is the list of element id's and the second the lit of face id's (the local number of the face on the element: a number from 1 to nfaces of the element) In case of all_geometty is expected a list with 4 iteme with the list of ids of points, lines, surfaces and volumes. In case of all_mesh is expected a list with 3 itemos with the list of ids of nodes, elements and faces, and for faces there are ty.o subitems {element_ids face_ids} + GiD_Entitiescroups unassing ?-also_l ‘To unassing the selection of entities of kind over of the group. wer_entities? ?? If is missing, then all entities of kind are unassigned of + GiD_EntitiesGroups unassign all_geometry |all_mesh|all all_geometry:To unassign all groups of all geometric entities all_mesh: To unassign all groups ofall mesh entities all: To unassign all groups of all entities + GiD_EntitiesGroups get ?-count? 2-element_type ? To get the list of entities of kind that belong to , If is faces then is obtained a list with 2 sublists: elernent id's and face id's If is all_geometry then is obtained a list with 4 sublists: point id's, line ids, surface id's and volume id's If is all mesh then is obtained a list with 3 sublists: node id's, element id's, face id's (and face id's is a list with 2 items: element id's and face id's) if -count is speficfied, then only the number of objects is returned instead of its lst. if -element_type is specified then only the types of elements listed in will be taken into account, must be a list of triangle quadrilateral, etc. In fact itis returned an ‘objarray': 2 Tel_Obj object specialized for arrays, implemented as a Tel package ‘named 'objarray’. (For more information see scripts\obj array\ obj array.pd*) + GiD_EntitiesGroups entity_groups ‘To get the list of groups to which the entity of type belongs could be points; lines, surfaces, volumes, nodes, elements, Faces < is the entity number, starting from 1. In case of faces itis a lit with tho items: ( ), ith starting from 4 8.4.4 Data GiD-Tel special commands to manage materials, conditions, intervals, general data or local axes: GiD_Book material|condition create|setlexists To create or know if a book of materials or conditions exists, or to set its current book. * GiD_Book material|condition create To create anew book named in the collection of books of materials or conditions * GiD_Book material|condition set To set as az current book of a material or condition named * GiD_Book material|condition exists ‘To check ifthe book exists in the collection of books of materials or conditions GiD_CreateData create|delete material |condition .. To create or delete materials: GiD_CreateData create material Data 80. + this only applies to the create material operation, and is the base material from which the new material is derived; + is the name of material or condition itself; © is a list ofall field values for the new material or condition. GiD_CreateData delete material To create or delete condition: GiD_CreateData create con 2{value_1 value_n}?} * must be ovpntlovline|ovsurflowvol jovlayer|ovgroup * must be ovnode|ovbedyelem|ovfaceelem GiD_CreateData delete condition jon {{question_1 ... question_n} Example: set id_material [6iD_CzeateDaca create material Steel Aluminéwn (2.5 40.291 see id condicion [6iD_CreateData create condition surface pressure ovsurf ovfaceelem ((pzessure) (0.0771 Gib_CeeateData delete condivion surface pressure GiD_AssignData material [condition ?? To assign materials or conditions over entities: + is the name of the material or conditions must be: points, lines, surfaces, volumes, layers, groups, nodes, elements, body_elements, or face_elements (elements is equivalent to bedy_elements). Layers and groups is valid for conditions defined over them, but not for materials. © is only required for conditions. If itis set to" then the default values are used; + alist of entities (itis valid to use ranges as a:b ,can use “all” to select everything, "end’ to specify the last entity, layer: to select the entities in this layer) ; if is face_elements then you must specify a list of "entitynurrface” instead just "entity" Example: GiD_AvsignData materials Steel Surtace (2:end) GiD_AssignData condivion Poine-Load Hodes (2-5 2.1 6.0) all GiDLAssignData condivion FacevLoad face elenents (2.6 2.18.0) (15 118 , GiD_UnAssignData material condition ?wherefield ? “To unassign materials or conditions of some entities + is the name of the material or condition; Can use "*" to match all materials * must be: points, lines, surfaces, volumes, layers, nodes, elements, body elements, or face_elernents (elements is equivalent to body_elerments); It is possible to use all_geometryl.all_mesh]|all to unassign of all entities of geometry or mesh or both. Then must not be provided + alist of entities (itis valid to use ranges as a:b ,can use “al to select everything, "end" to specify the last entity, layer: to select the entities in this layer) ; if is face_elements then you must specify a list of "entitynurrface” instead just "antty” + wherefield To unassign this condition olny for the entities where the field named 'fieldname! has the value 'ieldvalue! Example: GiD_VnAssignDava materials * Surface (end-S:end) Gip_UnassignDaea condition Point-Load Hodes Layer:Layer0 GiD_UndssignDava condition Face-Load face elenenes (15 118 120 GiD_ModifyData ?-book? material |condition intvdata|gendata ?? To change all field values of materials, interval data or general data: + is the material name or interval number: © is a list ofall the new field values for the material, interval data or general data if -book is specified then this value is the nen book name, and could be applied only to material or condition Exar G&D _ModityDara material Steel (2.126 0.2 7800)Data 91 GiD_AccessValue ?-index? set|get ?-default? material |condition intvdata|gendata ?? 2? “To get or set some field values of materials, interval data or general data: if index is specified then the material of condition number will be expected instead ofits name if -default is specified then the get option returns the default value instead of the current value (the default value is value set in the problerrtype file) © is the material, condition name of interval number (not necessary for gendata): + is a field name; * is the attribute name to be changed (STATE, HELP, etc.) instead of the field value: + is the new field or attribute value. Example: net mass (6iD AccesaValue “index gee materials fmacerial_id mass] nee deeaule value {6iD_AccenaValue gee "defasit genasta Fqueae ion] GiD_IntervalData ?? ?copyconditions? To create, delete or set interval data; + must be ‘create’, ‘delete’ or ‘set + is the interval number (integer >=1). Create returns the number of the newly crested interval and can optionally use ‘copyconditions' to copy to the new interval the conditions of the current one, For create mode, if is supplied the nes interval is inserted in this location, elze is append to end, For set mode, if is not supplied, the current interval number is returned Exarrle: see current (6iD_IncezvalDava set] see newnum (GiD_IntervalDava create] See newmun (Gil IntervalData create copyconditions] See new (6il_incervalData cxeave $i_insezt copycondicions] GiD_Local Axes ?? ? To create, delete or modify local axes: + : must be one of "createldelete|editlexists', which correspond to the operations: create, delete, edit or exists; + : is the name of local axes to be created or deleted: + : must be one of "rectangular|cylindricall spherical C_XZ_7|¢_XY_X". Currently, GID only supports rectangular axes. C_XZ_Z is an optional word to specify one point over the XZ plane and ancther over the Z axis (default) €_XY_X is an optional w ord to specify one point over the XY plane and another over the X axis: + <0x Cy Cz> is a Tel lst with the real coordinates of the local axes origin: + is 2 Tel list with the coordinates of a point located over the 2" local axis (w here 2 is positive), ‘The coordinates must be separated by a space, If the z coordinate is missing, itis set to 2=0.0; + is 2 Tel lst with the coordinates of a point located over the 2'x’half-plane (where X’ is positive), For the ‘exists! operation, if only the field is specified, 1 is returned if this name exists, and 0 if it does not. IF the other values are also apecified, is ignored. ‘The value returned is: 1 ifthe global axes match; 2 ifthe automatic local axes match; -3 ifthe automatic alternative local axes match; Of it does not match with any axes: -en> ifthe user-defined number (n>0) local axes match, Exarrole Giptecalaces exives "rectangular € EEX (9 0 0) (010) (1.00) this last sample returns 1. (equivalent to glabal axis) sectangular CXYX (0 0 0) (0 1.0) (1.0 07Results 92. 4.5 Results GiD_Result create|delete|exists get get_nodes|gauss_point|result_ranges_table ?-array? To create, delete or get postorocess results: + GiD_Result create ?-array? {Result header} ?{Unit }? ?{componentNames namet ...}? {entity_id scalar|vector|matrix_values} {...} {...} : these creation parameters are the same as for the postprocess results format (see Result -paq, 49:Jof Results format: Nodll ame post res -paq. 43-) where each line is passed as Tl lst argument of this command: Optionally the names of the resul’s components could be specified, with the componentitames item, and the unit label ofthe resut with the Unit item if the -array flag is used (recommended for efficiency), then the syntax of the data changes. Instead to multiple items {idt vod vyt ...} - fide van vyn} a single item with sublists is required, {{idi ... ide} ({vxd...vxn} {vyl..wyn}}}, where idi are the integers of the node or element where the result are defined, and vi are the real values. The amount of values depends on the type of result: 4 for Scalar, 2 for ComplexScalar, 3 for Vector (4 if signed modulus is provided), 6 for Matrix. In fact with -array itis returned an ‘objarray': a Tcl_Obj object specialized for arrays, implemented as a Tel package named ‘obj array’. (for more information see scripts\objarray\obj array. pd) Examples: Gid_Result create ~array (Result "MyVectfodal" "Load analysis" 10 Vector Gnifedes) (ComponentIames "et Ny" iwelocieyI") ((1 9) (2-0-1 ~2.Se-2) (2-Oe-d 4-Se-1) (0.4 =2-10)) GiD_Resule ceeate (Result “Res Modal 1! er) (22) 22) aa 2 ebara Gip_Resule create (Result "Rex Modal 2" “Load analysis" 4 ecco Onlfodes) (Componencifanes cop" *nedulus"} (10.9 0.5 0.1 0-561) (22.5 0-8 -0.2 2.641) Gi_Result create ~array (Result "Rez Todal 2" "Load analysis" 4 Vector Gnifedes) (ComponentIames Se Comp" “y comp" “e conp" modulus") ((1 2) ((0.2 2.5) (0.5 0.8) (0-1 -0-2) (0-581 2.641))) + GiD_Resultdelete {Result_name result_analysis step_value} : deletes one result: Examples: Ga _Resule delete (Res Nodal 1° “Load analysis" 4) + GiD_Result exists {Result_name result_analysis step_value} : return 1 ifthe result exists. + GiD_Result get ?-max|-min|-compmax|-compmin info? ?-sets ? ?-selection ? ?-array? {Result_name result_analysis step_value} : retrieves the results value list of the specified result. array flag: the values are returned more efficiently grouping the information in arrays, else values are grouped as, alist with one itern by entity list>: only the results of nodes/elements (depending on the result) of the sets belonging to -sets are returned selection : only the results of nodes/elements (depending on the result) with id belonging to < are returned < must be an intarray (list of integer ids) of increasing ids of nodes/elements to be returned. if one of the -max, -min, -compmax, -compmin, or “info flags was specified instead of the full results value only the minimur/maximum value of the result, every minimurn/maximum of the components of the result, or the header information of the result is retrieved, respectively: (case of a scalar result defined on triangles with 3 gauss points) [ise "Tese Gauss" “LoaD ANALYSIS" 10 OMD MIALYSIS" 10 Scalaz OnGaussPoints “Trimgles") (ComonentIanes (ces 170) (126.25 ssss227060547 78.250000281968727 26. 2595¢se18520272 GiD_Resule gee “selection (165 170) [Lise "Test Gauss” “LOAD ANALYSIS" 10 <> [aerult Test Gauss" "LOAD MIALYSIS" 10 Scalar OnGaussPoints "Teiangles") (ComponentTames Gauss") (165 26.25 27.298sss20706087 2e.2500003914e6727) (170 2é.98¢S98e15520279,Results 93 + GiD_Result get_nodes: returns a list of nodes and their coordinates, + GiD_Result gauss_point create|get|names|delete ?-nodes_included? ?? * create ?-nodes_included? ?? Define a new kind of gauss point where element results could be related, is the gauss point name, Internal Gauss points are implicitly defined, and its key names (GP_LINE_1,GP_TRIANGLE_1,...) are reserved words and can't be used to create new gauss points or be deleted. (seqSauss Points -paa 42) rust be one of "point | line | triangle | quadrilateral | tetrahedra | hexahedra | prism | pyramid | sphere | circle’. (see Mash format: ModelN'ame post meh -paa: Se) nurrber of gauss points of the element snodes_inchided ‘optional w ord, only for line elements, to specify that start and end points are considered (by defauit are not included) : vector with the local coordinates to place the gauss points: 2 coordinates by node for surface elements, 2 coordinates for volume elements, For line elements now is not possible to specify its coordinates, ‘the n points will be equispaced, If coordinates are" then internal coordinates are assumed, : optional mesh name where this definition is applied, by default itis applied to all meshes + get Return the information of this gauss point Return a list with the names of all gauss points defined + delete Examples: Gip_Result gauss poine creace GPTL Quadrilaceral 1 (0.5 0.5) Gi Result create (Result "Res Gauss 1° “Load analysis" 1.0 Scalar OnGaussPoints GPTL) (165 > (ay ea 5) (4) (> * GiD_Result result_ranges_table create|get|names|delete { ... } * create { .., } Define a new kind of result ranges table to map ranges of result values to labels is the result ranges table name. : is the label to show for result values from min to max + get Retutn the information of this result ranges table Return a lit with the names ofall result ranges tables defined * delete array flag can be specified, for create and get subcommands, to use list of vectors to handle the information in a more efficient w ay 4.6 Sets 4.6.1 Definition GiD_sets get ‘To handle the definition of postprocess sets (similar to preprocess layers) + GiD_sets get color|visible|type|num_entities|id To obtain the current value of some property: + type: set type. could be 0==unknown, 1==mesh, 2==set, 3 © num_entities: the total number of mesh elements that belong to the set + id: the numeric identifier of the set cut 4.6.2 Entities GiD_EntitiesSets getlentity_sets To handle the entities that belong to postprocess sets (similar to preprocess layers)Entities 94 + GiD_Entitiessets get/entity_sets ‘To know the entities of a set or to know the sets of an entity + GiD_EntitiesSets get nodes|elements|all_mesh ?-count? ‘To get the list of entities of kind that belong to If is all_mesh then is obtained a list with 2 sublists: node id's, element id's if -count is speficfied, then only the number of objects is returned instead ofits lst. In fact itis returned an ‘objarray': 2 Tel_Obj object specialized for arrays, implemented as a Tel package ‘named 'objarray’. (For more information see scripts\obj array\ obj array.pd*) Example: see count_elements_set (GiD_Encitiessets get Layez0 elements ~coune] see nodes ids_one see (Gil Eneivieasees get Layer0 nodes] + GiD_Entitiessets entity_sets nodes|elements ‘To get the set that contain the element or the list of set that contain a node (the sets that contain elements with the node as vertex) Example: see clenent_21_set [64D _EneitiesSers entity sets elenents 211 see node_o sets [GAD Enbiviessers entity sets nodes 6] 4.7 Graphs GiD_Graph clear|create|delete|edit|exists|get|hide|list|show To create, delete or get postprocess graphs: All commands accept an optional parameter , else the current graphset is assumed. + clear??: delete all graphs in GiD; * create 2?: creates the graph "graph_name” with the provided information, causing an error if the graph already exists: for instance the graph of the picture »as created with 'y values" {0 1.2.3} {0.5 2.1 -4.5. 9.6} aa far + delete ??: deletes the graph "graph_name" causing an error if does not exists: + edit 2?: modify a the graph with the new values, but without lost other settings like line color, etc. * exists ??: return 1 the graph "graph_name" exists * get ??: gets a list with the values of the graph with name "graph_name', the values are the same used to create a grant label_s> getname ?? : get the name of the graph with global identifier . If ‘ is specified then the graph is only find in this graphset instead ofall graphsets. * hide? ?: hides the graphs and switches back to mesh viewGraphs 95. + list 2?: gets a list of the existent graphs, an empty list if there is no graph. + selection get|swap| set : set o get the flag of selection of the graph. is must be 0 or and is only needed in case of set. snap change the current selection state to the opposite one. Selected graphs are show ed in red color + show2?: switches the graphic view and shows the graphs. 4.8 Graphsets GiD_GraphSet create|current|delete|editlexists|list To create, delete or get postprocess graphs sets: ‘A graphset is a container of graphs sharing the same x, y axes * create ??: creates a nev graph set. IF the name is not provided an automatic unused name is assigned. The name of the graph set is returned. + current ??: get or set the current graph set, There iz alw ays a current graph set © delete : deletes the graphset "graphset_namne! * edit name|legend_location|tite_visible : modify the property of the graph set name: is the graphset identifier name legend_location: 0 - to not show the graph legend 11 to show the legend on the top-right (default) 2 = to show the legend on the top in a single ling, like a title ‘itle_visible: 0 oF 4, to print or notin the legend also the graphset name * exists : return 1 the graph set "graphset_name" exists; list : gets a list of the existent graph sets: 8.4.9 Openct. GiD_Openct It is possible to use OpenGL commands directly from GID-Tel by using the command" for C/C++ use: giBegin(GL_LIMES); givereex(xiyl,#2); givereex(22 72,22); SIENA; iD_OpenGl draw”. For example, for GiD-Tel use: Gip_openth draw —verven (Lise fel Syl $21 Giplapench. draw —werten (Lise #02 $y $02 ‘The standard syntax must be changed according to these rules: - OpenGL constants: "GL" prefix and underscore character '_' must be removed: the corrmand rust be written in lov ercase. Exarele: = OpenGL. functions: "GL" prefix must be removed and the command written in lowercase, Pass parameters ar lis, without using parentheses () Example: giBegin(GL_LIMES) -> gibegin Lines ‘The subcommand "GiD_OpenGL draw" provides access to standard OpenGL commands, but other "GiD_OpenGL” special GiD subcornmands also exist: + register Register a Tel procedure to be invoked automatically when redrawing the scene, It returns @ handle to unregister Example: proc MyRedranProcedure () ( body...) Bee id (65D _OpenGh register MyRedeanProcedure]OpenGL 96 * unregister Unregister a procedure previously registered with register: Example: GsD_opench wnegister #48 + registercondition Register a Tel procedure to be invoked automatically when redraw ing the specified condition. ‘The tel funcion must have this prototype proc xxx { condition use entity_id values} { return 4 + “The supplied parameters are: condition ithe condition name, defined in the .cnd file of the problemtype use: GEOMETRYUSE, MESHUSE of POSTUSE entity_id: the integer number that identity the entity where the condition is applied. The kind of entity is known because it is declared in the definition of the condition in the .cnd, depending ifthe current state is geometry or mesh values: 2 list of the field's values applied to this entity. The amount of values must match the amount of fields of the condition definition, ‘The return value of this procedure is important: return 0: then the standard representation of the condition Is also invoked after the procedure return 1: the stardard representation of the condition is avoided, unregistercondition Unregister 2 procedure previously registered with registercendition. draw <-cmd args -cmd args> This is the most important subcormand, it calls standard OpenGL commands, See the list of supported OpenGL functions. + drawtext Dray a text more easily than using standard OpenGL commands (draw in the current 2D location, see rasterpos OpenGL command). example iD. dpendi deaw “tartespes (Lise fe fy Fa] + font push | pop | measure | current | metrics P-ascent|-descent-linespace| fixed? push sets the current OpenGl font, pop restores the previous one tmeasure returns the amount of space in presto ply this Carrer returns alist with the current font name and size rmetris returns ait with curren for metres information ascent -descent and -linespace in pixels, -fixed is 1. if all characters have equal size Example: GiD_OpenGh fone push (Times Hew Roman" 15) see wich [650] Openth measure "hello world] drawentity ?-mode normal | filled? point | line | surface | volume | node | element | dimension To draw an internal GiD prepracess entity. Example: GiD_Openct aravencity “node filled surface (15 6) For elements it is possible to draw only a face, specifying items of element_id and face_id, whith face_id a number from 1 to the number of faces of the element. Example: GiD_OpenGL draventity node £illed element ((1 1) (5 2) (€ 297OpenGL 97. * project Given three world coordinates, this returns the corresponding three window coordinates. + unproject Given three window coordinates, this returns the correspanding three world coordinates, + doscrzoffset Special trick to avoid the lines on surfaces hidden by the surfaces. List of supported OpenGL functions: Gnienames light lightmedel Lineseipple linewidth leadidentity loadmateix Loadname Lockat map map? Eeadpinel> rect zendernede rotate scale scissor selectbuffer shademedel stencilfine svencilmase List of special non OpenGL standard functions: List of supported OpenGL constants: accu accumbuffer accubufferbic add alphatest always allaterib allatecibhies ambiene packrowlengeh packskippixels packskiprows packowapbyees pixelnode pixelmodebie poine poinebie poines eransformbit triangles trianglefan crianglestrip unpackalignsent wipacklsbfizse wnpackrowl engeh sunpacksieipp iel> wnpackskiprows unpackswaphytes vendor version viewport wiewpozebie exe ‘You can find more information about standard OpenGL functions in a guide to OpenL. 4.10 Other GiD_Set ?-meshing_parameters_model? ?-default? ?? ‘This command is used to set or get GiD variables. GID variables can be found through the Right buttons menu under the option Utlities -> Variables: + is the name of the variable; © if this ic omitted, the current variable value is returned (analogous with 'GiD_Info variables ') + -default return the defauit value of the variable ( its not accepted) + -meshing_parameters_model if added manage variables used in current model instate of general variables Example: GinLsee “meshing parameters model Surfacelfevhex GiD_SetModelName ‘To change the current model name, If name is not specificied then the current model name is returned. GiD_SetProblemtypeName Other 98 ‘To change the current problemtype name, If name is not specficied then the current problertype name is returned, GiD_ModifiedFileFlag set|get 2? ‘There is a GiD internal flag to indicate that the model has changed, and must be saved before exit, With this command it is possible to set or get this flag value: + is only required for set: must be 0 (False), or 2 (true), Exarele: Gid Medigiearinertag set 2 Gib Medifiearitertag gee GiD_MustRemeshFiag set|get ?? ‘There is a GiD internal flag to indicate that the geometry, conditions, etc. have changed, and that the mesh rust be re-generated before calculations are performed. With this command it is possible to set or get this flag value: + is only required for set: must be 0 (False), or 2 (true), Exarle: GiD_Backgroundimage get|set show |filename|location This command allow to get and set the background image properties Valid set values are: + show: 3 oF 0 © filename the full flename of some valid GID image format to be used as background image to release the current image * location: ‘fl'to fil the whole screen, oF six floating values for a real size image, to set the origin and x,y lecal axes: ox oy ix iy jxjy GiD_RegisterExtensionProc <.extension> PRE|POST|PREPOST To register a Tel procedure to be automatically called when dropping a file with this extension es GiD_RegisterE xtensionProc ".hS" PRE Amelet: ReadPre GiD_RegisterPlugin AddedMenuProc To register a Tel procedure to be automatically called when re-creating all menus (e.g, when doing files new ) this procedure is responsible to add its on options to default menu, es GiD_RegisterPluginaddedMenuProc Amelet: :AddToMenu GiD_File fopen|felose |fprintfllist To allow print data from a Tel procedure with standard fprintf command, specially to write the calculation file from Tel or @ imix of -bas template and Tel procedures + GiD_File fopen ?? Open a fle named for writting access. By default access is "w", but is possible to use "a" to append to a previous fle (and "wb" or “ab” to open the file in binary mode). It returns a long integer representing the channel + GiD_File felose Clase a channel + GiD_File fprintf -nonewline ?? ...?? Print data from a Tel procedure in a file opened with GiD_File fopen and returns the number of printed characters. (a .bas template implicly open/close a file with this command, and the file_id could be send to a tcl procedure az a parameter with the *Fileld template keyword) < must be a valid file descriptor, that could be obtained in a .bas template with the *Fileld command (or with GiD_File fopen)Other 99 rust be a valid C/C++ format, according with the arguments return + GD_File list It returns a list of currently open file_ids eo! bas file Number of points and lines: *tel(tiyHethod *Fileld) sel file: proc MyMethod {channel } GiD_File fprintf -nonewline channel (ed %6d) [6ID_Info Geometry umPoints] [GiD_Info Geometry NumLines] ? Some special commands exist to control the redrau and wait state of GID; world ( model) is done by intersecting the line perpendicular to the screen, passing through the coordinates ( screen_x, screen_y), with the plane parallel to the screen ( in real, model, world ) at the centre of the view / model. The returned normal is the normal of this plane. GiD_Togl currentllist To get or set the current togl (Tk OpenGL object), and the lst of all tog!'s of all windows EXAMPLE see ogi [64D Togl current] Gip_togi cuszene frost pee eogis (620 Togl ise] .5 HTML help support Problem type developers can take advantage of the internal HTML brow ser if they wish to provide online help. “The GiDCustomHelp procedure below is how you can show help using the new format: where args is alist of pairs option value. The valid options are: + title : specifies the title of the help window. By default itis "Help on " + -dir + gives the path for the help content, If -dir is missing it defaults to "/htr\". Multilingual content could be present, in such a case it is assumed that there is a directory for each language provided. If the current language is not found, language ‘en’ (for English) is tried. Finally, if ‘en’ is not found the value provided for I> -.. (default) b> --. ‘The first isthe one generated by texinfo, For instance: 5.4 IndexPage If we specify a topic index by IndexPage, we can take advantage of the search index. In IndexPage we can provide a set of htral index pages along with the structure type of the index. The type of the index could be:

... (default)

• ...

(only one level of

) ‘The first isthe one generated by texinfo, For instance: IndexPage henl-version/gid_18 hemi Renl~faq/faq_11 hen! 8.6 Managing menus GiD offers you the opportunity to customize the pull-down menus, You can add new menus or to change the existing cones. If you are creating a problem type, these functions should be called from the InitGIDProject or InitGIDPostProcess functions (see[ICL AND TK EXTENSION -paq. 65: Note: Menus and option menus are identified by their names. Note: It is not necessary to restore the menus when leaving the problem type, GID does this automatically. ‘The Tel functions are: + GiDMenu::Create { menu_name_untranslated prepost {pos -1} {translationfunc _} } Creates anew menu, New menus are inserted betw een the Calculate and Help menus. + menu_name_untranslated: text of the new menu (English) * prepost can have these values: PRE" to create the menu only in GiD Preprocess. POST" to create the menu enly in GiD Postprocess. 'PREPOST" to create the menu in both Pre and Postprocess, * pos: optional, index where the new menu ull be inserted (by default itis inserted before the ‘Help’ menu) + translationfunc: optional, must be _ for GID strings (default), o for problertype stringsManaging menus 102 + GiDMenu::Delete { menu_name_untranslated prepost {translationfunc _} } Deletes a menu. + manu_name_untranslated: text of the menu to be deleted (English). * prepost can have these values: PRE" to delete the menu only in GiD Preprocess. POST" to delete the menu only in GiD Postprocess “PREPOST to delete the menu in both Pre- and Pastprocess. + translationfune: optional, must be _ for GiD strings (default), or = for problertype strings + GiDMenu: \sertOption { menu_name_untranslated option_name_untranslated position prepost command {acceler} {icon ""} {ins_repl "replace"} {translationfunc _} } Creates a nen option for a given menu in a given position (positions start at 0, the word ‘end’ can be used for the last one). + menu_name_untranslated: text of the menu into which you wish to insert the new option (English), e.g "Utilities" * option_name_untranslated: name of the new option (English) you w ant to insert, ‘The option name, is a menu sublevels sublevele list, like [list "List" "Points"] If you wish to insert a separator line in the menu, put "---" as the option_name. * position: position in the menu where the option is to be inserted. Note that positions start at 0, and separator lines also count. * prepost: this argument can have the following values! "PRE" to insert the option into GID Preprocess menus. POST to insert the option into GiD Postprocess menus, 'PREPOST" to insert the option into bath Pre- and Postprocess menus. * command: is the command called when the menu option is selected + acceler: optional, key accelerator, like "Control-s" * icon: optional, name of 2 16x16 pixels icon to show in the menu * ins_repl: optional, if the argument is + replace: (default) the new option replaces the option in the given position * insert: the new option is inserted before the given position, * insertafter: the new option is inserted after the given position. * translationfunc: optional, must be _ for GiD strings (default), or = for problemtype strings * GiDMenu::RemoveOption {menu_name_untranslated option_name_untranslated prepost {translationfunc ae Removes an option from a given menus + menu_name_untranslated: name of the menu (English) which contains the option you want to remove, =.g "Ulitie * eption_name_untranslated sublevels list, lke [list "List" repost: this argument can have the following values: "PRE" to insert the option into GID Preprocess menus. POST to insert the option into GiD Postprocess menus, 'PREPOST" to insert the option into bath Pre- and Postprocess menus. + translationfune: optional, must be _ for GiD strings (default), or = for problertype strings name of the option (English) you want to remove, The option name, is 2 menu ‘To remove separators, the option_name is ~ rust be removed, if there are more than ene. es GiDMenn: -Removeopeion "Geonetsy" [Lise "Create 1 but you can append an index (starting from 0) to specify wich separator | PRE + GiDMenu: (odifyOption { menu_name_untranslated option_name_untranslated prepost ew_option_name {new_command -default-} {new_acceler -default-} {new_icon ~default-} {translationfunc _} } Edit an existent option from a given menu some parameters can be '=defauit~’ to keep the current value for the command, accelerator, ete + GiDMenu: ipdateMenus {} Updates changes made on menus. This function must be called when all cals to create, delete or modify menus are made.Managing menus 103 * GiD_RegisterPluginAddedMenuProc and GiD_UnRegisterPlugin AddedMenuProc ‘This commands can be used to specify 2 callback procedure name to be called to do some change to the criginal Gib_RegisterPluginAddedtienuProc GiD_UnRegisterPluginAddedMenuProc ‘The procedure prototype to be registered must not expect any parameter, something like this: proc {) { fo something > 8.9: 2 plugin can modify a menu to add some entry, but this entry will be lost when GiD create again all menus, for ‘example when starting a new model. Registering the procedure will be applied again when recreating menus. + GiD_RegisterExtensionProc and GiD_UnRegisterExtensionProc ‘This tel command must be used to register @ procedure that is able to handle when using ‘drag and drop! of a file on the GiD window. It s possible to specify the extension (or alist of extensions) of the files to be handled, the mode PRE or POST where it will be handled, and the name of the callback procedure to be called, GiD_RegisterExtensionProc GiD_UnRegisterExtensionProc - is the file extension, preceded by a dot < could be PRE or POST “The procedure prototype to be registered must expect 2 single parameter, the dropped file name, something like this, proc { filename } { fo something > Example: GiD_RegisterEstensionProc ".gif .png" PRE MylmageProcedure EXAMPLE: creating and modifying menus In this example we create a new menu called "Nev Menu" and w/e modify the GiD Help menu! TT] |. rm Tees esa a Sort ERI tet oe whebe el Fei a oat ‘The code to make these changes would be: GiDMenn: : InsezeOpeion ‘Mew Hens” [Lise GiDMen: : InsezeOpeion ‘Mew enw” [Lise GiDMen: : InsezeOpeion ‘Mew enw” [Lise GiDMen: :InsezeOpeion ‘Mew Wena” [Lise GiDMenn: -RenoveOption ‘Help (1ise “Customiastion Melp"] PRE __ GiDlena: “Renovedption "Help" (List "What is new" PRE GiDMens: -RemoveOpeion "Help" (1ise FAQ") PRECustom data windows 104 .7 Custom data windows In this section the Tel/Tk (scripted) customization of the look and feel of the data windows is shown, The layout of the properties drawn in the interior of any of the data window's - either Conditions, Materials, Interval Data or Problem Data ~ can be custorrized by a feature called ThWidget; moreover, the commen behaviour of tue specific data windows, Conditions and Materials, can be modified by a Tel procedure provided for that purpose. This common behaviour includes, in the case of Materials for example, assigning/unassigning, drawing, geometry types, where to assign materials, creating/deleting materials, etc. 7.1 Th Widget ‘The problem type developer can change the w ay a QUESTION is displayed and if he wishes he can also change the whole contents of @ window , while maintaining the basic behavior of the data set, i.e. In the Condition window : assign, unassign, draw in the Material window : create material, delete material; and so on. With the default layout for the data windows, the questions are placed one after anather in one colurnn inside a container frame, the QUESTION’ label in column zero and the VALUE in column one. For an example see picture below. QUEST IOM: Local_AresBLM(-Defsule~,~Automatic~) QUEST IoM: SeeelMane QUESTION: Seee1Type -Asos Sesion - a Aesop) foie Dow Uacn “The developer can override this behavior using TKWIDGET. TKWIDGET is defined as an attribute of 2 QUESTION and the value associated mith it must be the name of a Tel procedure, normally implemented in a Tel file for the problem type. This procedure will take care of drawing the QUESTION. A TKWIDGET may also dran the entire contents of the window and deal with sorne events related to the window and its data. ‘The prototype of a TKWIDGET procedure is as follow : proc THWidgeeProc (event args) ( suiech fever ( mr > sure ¢ DEPEMD ¢ > cose tis also allow ed to add extra arguments before the ‘event’ argument, and provide its values in theTKWIDGET fieldThwidget 105 2-9, declare this tharidget procedure with a first argument "-w ith 20" THUIDGET: Giaveiis: -TewidgeetneryContigure (“wideh 20) and then define the Tel procedure ready to get the first extra argument 'configure_options' before ‘events’ proc Gidltils: -ThusdgetEneryConéigure ( configure options event azgs } ( > ‘The argument event is the type of event and args is the list of arguments depending on the event type. The possible events are: INIT, SYNC, CLOSE and DEPEND. Below is a description of each event. ‘+ INIT: this event is triggered when GID needs to display the corresponding QUESTION and the list of arguments is {frame row-var GDN STRUCT QUESTION}: frame is the container frame where the widget should be placed; row-var is the name of the variable, used by GiD, with the current row in the frame; GDN and STRUCT are the names of internal variables needed to access the values of the data; QUESTION is the QUESTION's name for mhich the TKWIDGET procedure was invoked, Normally the code for this event should initialize some variables and draw the widget + SWIC! this is triggered when GID requires a synchronization of the data. Normally it involves updating some of the QUESTIONSs of the data set. The argument list is {GON STRUCT QUESTION} + CLOSE: this is triggered before closing the window, as mentioned this can be canceled if an ERROR is returned from the procedure. © DEPEND: this event is triggered when a dependence is executed over the QUESTION for which the TKWIDGET is defined, ie, that QUESTION is an value of the dependence. The list of arguments is (GDN STRUCT QUESTION ACTION valus} where GDN, STRUCT and QUESTION are as before, ACTION could be SET, HIDE or RESTORE and value is the value assigned in the dependence. ‘The argument args is 2 variable amount of arguments, provided here as a list. Its content depends on the ‘event! argument. es INIT argst PARENT CURRENT_ROW_VARIABLE GDN STRUCT QUESTION SYNC args: GDN STRUCT QUESTION DEPEND args: GDN STRUCT QUESTION ACTION VALUE CLOSE args: GDN STRUCT QUESTION and its meaning is CURRENT_ROW_VARIABLE: store a name of variable that provide the integer row nurrber of the current field GDN and STRUCT: identify the data (e.g set value [DWLocalGetValue $GDN $STRUCT $QUESTION]) QUESTION is the name of the question that identify the field ACTION could be "HIDE", "SET" oF "RESTORE" “The procedure should return: * an empty string" meaning that every thing was OK: + a tworlist element {ERROR-TYPE Description} where ERROR-TYPE could be ERROR or WARNING, ERROR means that something is wrong and the action should be aborted. IF ERROR-TYPE is the WARINING then the action is not aborted but Description is shown as a message. In any case, if Description is not empty a message is displayed. The picture below shows a fragment of the data definition file and the GUI obtained. This sample is taken from the problem type RamSeries/rambshell and in this case the TKWIDGET is used to create the whole contents of the condition window s. Fer afull implementation, please dow nload the problem type and check it. QUEST IOM: Local_AresBLM(-Defsule~,~Automatic~) QUEST IoM: ‘SeeeiMane QUESTION: SeeeitTypeThwidget 106 Zucpeation 1S lem text 79 9 $$$ en? 9-8 L-16 Ten 4 Iyer Seds23en¢ Wes? Wentatsen!aye32en aston tects Pe potin.ee gine Dew asin Predefined TKWIDGET procedure: There are some useful features that have been implemented in tcl procedures provided by default in GID, inside the dev_kitte file, specially to replace the standard entry of a question by some specialized widget. + GidUtils:ThwidgetGetFilenameButton To show an entry and a select fis button that open the dialog window to select an existent fie lena (ea + GidUtils:sThwidgetPickPointOrNode ‘To show an entry and a button to pickin screen the id nurrber of a point in geometry mode or a node in mesh mode To show a combobox with the current layers Layemane Layed| . + GidUtils:ThwidgetGetVector3D To show in a single row three entries for x,y, 2 real coordinates of points or directions vedo 80 .7.2 Data windows behavior In this subsection we explain a Tel procedure used to configure the commen behaviour of Materials. We are working on providing a sirilar functionality for Conditions using the same interface. GiD_DataBehaviour controls properties of data window = for Materials and Conditions (not currently implemented). For Materials we can modify the behaviour of assign, draw, unassign, impexp (import/export), new, modify, delete and rename, We can also specify the entity type lst mith the assign option throught the subcommands georlist and meshlist, “The syntax of the procedure is as follow s:Data windows behavior 107 where + data_class could be “material” if ve want to modify the behaviour of a particular material, or "materials' if a whole book is to be modified: © name takes the value of a material's name or a book's name, depending on the value of data_class: In case that the materials are not classified in books the keyu'ord "Default" means its default implicit book. + cmd can take one of the values: hon, hide, disable, geommlist and meshlist: © proplist is a list of options or entity types. When the value of cmd is show, hide or disable, then proplist can be a subset of {assign draw unassign impexp new modify delete}. If the value of crnd is show it makes the option visible, if the value is hide then the option is not visible, and when the value i disable then the option is visible but unavailable. When the value of cmd is georlist then proplist can take a subset of {points lines surfaces volumes} defining the centties that can have the material assigned when in geometry mode; if the value of cmd is meshlist then proplist can take the value elements. Bear in rind that only elements can have a material assigned in mesh mode, If cmd is not provided, the corresponding state for each of the items provided in proplist is obtained as a result. Example: GiD_DacaBehaviour materials Default geoml ist (ouzfaces volumes) GipDavaBehaviour materials Solid hide (delete impexp) GiD_ShowBook i 2 procedure co hide/show 2 book fzom the menus where * class rust be: gendata materials conditions or intvdata * book is the name of the book to be show or hidden © show must be 0 or 2 [After change the book properties is necessary to call to GiDMenut:UpdateMenus Exarpl: Interaction with themes From GiD 11, a themes system has been integrated inside Gib. In the following chapters, how to manage and use these system is explained in order to get a full integrated lock of your module. A theme contain: * visual aspect as colors and shape of toolbars and windows. * collection of cursors. * collection of images (images can be classified in 2 categories, images on a roct folder: logos, auxiliar images, and images representin icons, this ones can be found on subfolders grauped by image size). * Definitions of which icon size is used in each categories (toolbars, menus). + Default colors of entities and background (this colors will be applied to user the first time that the theme is charged, after that, user could change colors by going to preferences) Now there are ony two themes inside GiD: GiD_classic and GiD_black. {As this manual is for modules developers, you must know that the most commen situation is to use most images provided by GiD and for only the new icons that you want to use in your module, implement the themes structure inside your module, creating the appropiated folder structure and configuration files, and providing images of the new icons for each theme. 1 Asking forimages Use in your module the same image as GiD use In order to use an image that GID use, you must use the tel function gid_themnes::Getimage, to see 2 complet list of images available you can take a look for example to the folder (GiD Folder)\themes\GiD_classic\images\large_size(24andmore)\As 19 for images 108 proc gid_themes::Getimage { filename IconCategory } IconCategory could be! "small_icons”,“large_icons", “menu”, "toolbar" ‘There is another IconCategory, "generic", that is the category used when the parameter is omitted, Using this category the image is retrieved from root image folder (Example: (GID Folder)\themes\GiD_classic\images\ ), but the use of this category its not recommended, since images from root folders are not guaranteed on future versions: ‘The corresponding folder for each icon category is defined on the configuration of theme (will be one of the subfolders inside image folder) Example. To get surface image for use on a button. gid_themes::Getlmage surface.png toolbar This will return appropriate image depending on current theme, it could be for example: (GiD Folder)\thernes\GiD_classic\images\large_size(24andmore)\surface.png Use in your module your own nages If your module needs other images from ones supplied by GiD You can use: * cid themes::GetimageModule to get the appropriate image, from inside the module folder, depending on current theme. + cid themes::Getimage { full_path filename}, image will be equal regardless of current theme. This is the ‘old sytle with the module images stored as module developer want, without follow the previously recommended folder layout. Note: the full_path filename points to a ‘module! file, but it must be build in a relative way, based on the problerrype location, es prec InieGIProjece ( diz} ¢ see full pach filename (Eile join Saiz ay_images_folder ay_image-pngl See ing [gid thenes:- Get image #£ull_path Filename] To use proc gid_themes::GetimageModule { filename IconCategory }, you must replicate folder structure of (GiD Folder)\themes\ inside your module folder. inside each theme must be a configuration. xml file (could be a copy of the one found in GiD) but also can be configured with only the following parameters - <1.4 < GiD_black < - small size <small_size(16andmore) GiD_black/images/size16 large size large_size(24andmore) GiD_black/images/ size24 small_size large_size19 for images 109 - small_size <large_size “The option "alternative theme" its used if some file its net found, for try to find on the alternative theme (example themes still on develop ) [Also using this redirection, a complet themes that module is net interested on can be redirected to our main theme, in this case we will need just 1 folder for each theme and configuration. xml inside it. .2 Forcing themes use When 2 module is loaded from inside Gio, module can not control theme configuration But if you are installing GiD together with your module, there is a variable inside scripts/ConfigureProgram.tel to contral how GiD manage themes. “The variable is ::GidPriv(ThemeSelection), and its value can be + 4 (by default), user can choose the theme selection + Any existing theme (Example: GiD_classic), user will be forced to use this theme and options on menus and window's about themes will be disabled With this option ts possible to obtain a package gid-+module totally customiced with your prefered visual aspect. 8.8.3 Creating new themes Create themes are only for modules that distribute they own package including GiD, or for GiD developers. If you have created a theme for GiD and want that the theme will be distributed with GiD, just contact us at: sid@cimne.upe, edu For creating anew theme you must know Inside (GiD_Folder)/themes: Each folder represent a theme (Example (GiD_Folder)/thernes/GiD_black) Inside each folder must be a configuration. xrl ‘This file must contain the follow ing information: - theme name is the same as its folder name images folder is always "GiD/themes/(name of theme)/images/" cursors folder is always "GiD/themes/(name of theme)/eursors/" ft does not find a folder it will use the alternative definition size folder start inside "images" theme folder alternative folder start from "GiD/themes/" folder GiD Black 1.1 GiD_classic - - large size <siza20 GiD_classic/images/large_size(24andmore) Creating new themes 110 size16- toolbar'>size20 small_icons'>size16 larga_icons'>size20 -false <nawgid <true - 000#000#000 1 < #000000 - #32346 < d 220#220#220 220#220#220 091#094#225 - 000#143#039 - 218#036#220 220#218#036 086#217#216 153#153#153 ‘This file configure colors of entities and background, also which images to display and where to find images, but for tatal different look of GiD, you must understand this 3 lines! <false newgid -true If option OnlyDefineColorsOnMainGiDFrame is true, only GiD's main frame will be modified with the visual aspects, windows and other elements wll remain in native look (as GiD_classic does) ‘The second option associate a tk theme in this case is newgid, the configuration of tk themes can be found on: (GiD_Folder)\scripts\gid_themes\tth_themes\ by changing the ttk configuration, we can achieve any look of Gib. “The last option ThFromTheme its important to obtain a complet integrated look, tk colors will be adapted with tt colors, we recomment oposite value of OnlyDafineColorsOntiainGiDFrame (true=> false, false=>true) Normally, a problem type requires a minimum version of GiD to run, Because the problem type can be distributed or sold separately from GID, itis important to check the GiD version before continuing with the execution of the problem type. GiD offers 2 function, GidUtils::VersionCmp, which compares the version of the GID currently being run with a given version. Giduti: jersionCmp { Version } ‘This returns a negative integer if Version is greater than the currently executed GiD version; zero i the two versions are identical; and a positive integer if Version is less than the GiD version, Not This function will av ays return the value -1 ifthe GID version is previous to 6.1.5, Example: proc InieGIDProject ( ai Af ({Gidveils: :VersionCnp {VezsionRequized] <0) ( Warnlin (= "This incerface requires GiD ts or later" $VersionRequizedlDetailed example un -10 Detailed example Here is a step by step example of how to create a Tel/Tk extension. In this example we will create the file emas2dLtel, so we will be extending the capabilities of the cmas2d problem type, The file cmas2ditc has to be placed inside the cdmas2d Problem Type directory, Note: The cmas2d problem type calculates the center of macs of a 2D surface, This problem type is located inside the Problem Types directory, in the GID directory. In this example, the cmas2d.tel creates a window which appears when the problem type is selected, (CHASEDTEL- Earp fe a Ch ngon sampletorCMAS20 poner pe Proton Teepe Chg oetpcbenpsamplsemac ak This window gives information about the lecation, materials and conditions of the problem type. The window has tre buttons: CONTINUE lets you continue w orking with the emas2d problem type RANDOM SURFACE creates a random 2D surface in the plane XY. What follows is the Tel code for the exarrple. There are three main procedures in the cmas2d.td file: * proc InitGIDProject {dir} proc Inite1DProject {air} { set materials [GiD_Info materials] set conditions [GiD_Info conditions ovpnt] CCreateWindow $dir $materials $conditions + ‘This is the main procedure, It is executed when the problem type is selected. It cals the CreateWindow procedure, * proc Createwindow {dir mat cond} proc Creave¥indow (4iz mat cond) ( sf ( (GidUeils:- AreWindowsDisabledl ) > InieWindew fw T= "CHAS2D.TCL - Eeawple tel €:1e"] Eeanplectas SE ( '(win€o exists fu] } return jf windows disabled || usenorewindows eek: frame fu-cop ‘eek: label fultop-title text —text [2 °TCL window example for CHAS2D problem type"l ek: iframe fu information “relief ridge eek: Label fw infosmaeion path “ext (= "Problem Type path: ts" gaiz] eek: Label fw infosmaeion materials “exe (= "Available maveziala: ¥2" faze] ek: Label fw infosmation conditions text [= "Available conditions: #2!" Seona] cee: frame fu boctom eek: shueton fu-bottem. start “eext [= "Continue"] “command "destroy fu" ‘eek: shuceon fu _bottem random text [= "Random surface] “comand "CreateRandonSuzface fu" grid Gu-cop-citle cexe “sticky ow grid fuceep ~svicky new grid $y information pach “sticky w pads 6 ~pady & seid fo.inturmsbionmaberials ~sticky w “pais 6 ~pady 6 eid Fe.informbion conditions ~sticly w “pade 6 “pady 6 grid $y informacion ~seieky nsew grid fu bottom stare $y boteom. random “paar 6 grid fu bottom ~seicky sew -pade 6 “pady € Se ( eel version >= 8.5 } ( grid anchor fw.bottom center) grid rowconfigare fu 1 ~weight 1 grid columcontigure #4 0 “weight 1Detailed example 112 , This procedure creates the window with information about the path, the materials and the conditions of the project: ‘The srindon has tye buttons: if CONTINUE is pressed the window is dismissed; if RANDOM SURFACE is pressed, it calls the CreateRandomSurface procedure. * proc CreateRandomSurface {w} proc CreateRandonsuréace (1H) ( see ree (tk dialogRMt fw-aialog (= "Wasning"] \ Warning: his will create a nubs surface in your current project") "2 aesezey # This procedure is called when the RANDOM SURFACE button is pressed. Before creating the surface, 2 dialog box asks you to continue with or cancel the creation of the surface. If the surface is to be created, the Create_surface procedure is called. Then, the window is destroyed, proc Create suréace () ( ee ae (expe and()*10) see ay (expe zana()*10) see be (expe Gax + zana()*i0) see bly (expe Gary + rand) 10) see ce (expe hoe + rand) *10) see cy (expe Shy ~ Eand()*10) ie Gay < fey pee ay (expe fay ~ zandtt0) see ax (expe fax + ean) 710] d etze ( dee ay Cexpe fey ~ zangoti0) ae fee - eang020) > Gin_Process excape escape excape geometry create Line \ $a.x/#a y, 0.000000 # ,98.y,0-000000 $< x,c_y,0-000000 #4 x,4_y,0.000000 close Gin_Process escape escape escape escape geometry cxeate MurbsSurface Automatic \ IN — Se A 20 surface (a four-sided 2D polygon) is crested, The points of this surface are chosen at random.13 9 PLUG-IN EXTENSIONS This section explains a new way to expand GiD capabilities: the plug-in mechanism. Plug-ins which should be used by GID shoud be present inside the $G1D/plugins directory. ‘There are tw o possible plugin mechanisms: + Tel plugrin 9.1 Td plugin If a file nith extension -tel is located inside the GiD ‘plugins’ folder, with the same name as the folder containing it, then it is automatically sourced when starting GiD. This allow to do what the developer want, with Tel language, e.g. change menus, source other Tel files or load a "Tel loadable library’ that extend the Tel language with new cornmands implemented at C level. To know how to create 2 "Tel loadable library’ some Tel book must be read. See chapter about '¢ Programming for Tel’ of "Practical Programering in Tel and Tk" by Brent Welch, Ken Jones, and Jeff Hobbs at http://w .beedub.corn/book 9.2 GID dynamic library plug-in Note that 'GiD dynamic libraries! ae different of Tel loadable libraries! ‘iD dynamic libraries’ must do specifically the task that GiD expects: now itis only available an interface for libraries that import mesh and create resuits for GiD postpracess. In the future new interfaces to do other things could appear, and to be usable must follow the rules explained in this chapter. 9.2.1 Introduction [As the variety of existent formats w orldn ide is too big to be implemented in GID and, currently, the number of supported formats for mesh and results information in GID is livited, the GiD team has implemented a new mechanism which enables third party libraries to transfer mesh and results to GiD, so that GID can be used to visualize simulation data written in whatever format this simulation pragram is using, This new mechanism is the well know mechanism of plug-ins. Particularly GiD supports the loading of dynarric libraries to read any simulation data and transfer the mesh and results information to GD. Viewing GiD as a platform of products, this feature allows a further level of integration of the simulation code in GiD by means of transferring the results of the simulation to GiD in any format specified by this simulation code thus avoiding the use of a foreign format “The recognized plug-ins are automatically loaded in GiD and appear in the top menu bar in the Files->Import->Plugins submen, 922m GD “The recognized import plug-ins appear in the top menu bar under the menu Files->Import-> Plugins!In gid 14 Fie) view iter cit Vewreuts Options Whew Hp cad oe BASE ST {© openmutie. ese ce pone , et) NasteANmen Snot Femi Bowe ett ost. ‘These dynarric libraries can be manually loaded and called via TCL scripts, in GID post-process's command line, of using the post-process's right menu ‘Files ImportDynamictib’ and the options LoadDynamiclib, UnloadDynamiclib, Callbynamictib: For one plugrin library, named MylmportPlugin.dll (or MyImportPlugin.so in Linux or MylmportPlugin.dylib in mac 0 X ) to be automatically recognized by GiD and to be loaded and listed in the top's menu Files->Import->Plugins, the library should lie inside a directory of the same name, i.e. MylmpertPlugin/MyimportPlugin.dll, under any sub-folder of the 9661D%/plugins/Import directory Note that only the GID 32 bits version can handle 32 bits import plugin dynamic libraries, and only GiD 64 bits can handle 64 bits import plug-in dynamic libraries, Which version of GID is currently running can be easily recognized in the title bar cof the main window (Title bar of GiD's window showing ‘GID x64", so the current GID is the 64 bits version) “Together with the GiD installation, follow ing import plug-ins are provided + 083: Wavefront Object format from Wavefront Technologies + OFF: Object file Format vector graphics file from Geornview = PLY: Polygon file format, aka Stanford Triangle Format, from the Stanford graphies lab. + pLy-tel: this plug-in is the same as the above PLY one but with a tel's progress bar showing the tasks done in the library while 2 ply file is imported. Fer all of these plug-in examples both the source code, the Microsoft Visual Studio projects, Makefiles for Linux and Mac OS X, and some little models are provided The eof Object le Formet example “Te ny. steers ty Patygon le 19.2.3 Developing the plug-in GID is compiled with the Tel/Tk libraries (the Tel version could be seen in Help->About - More... Remember that if the developed plugin is targeted for 32 bits, only GiD 32 bits can handle it. If the developed plugin isDeveloping the plug-in 11s developed for 64 bits systems, then GID 64 bits is the proper one to load the plugin + Header inclusion In the plug-in code, in one of the .cc/-epp/.cxx source files of the plug-in, following definition must be made and following file should be included: Baetine BUILD_GID_PLUCIT Binclude "gid plugin iopore-h* In the other .cc/.cpp/-cxx files which also use the provided functions and types, only the gid_plugin_importh fle should be included, without the macro definition ‘The macro is needed to declare the provided functions as pointers so that GiD can find them and link with its internal functions, * Functions to be defined by the plug-in Follow ing functions should be defined and implemented by the plug-in GID_DLL_EXPORT ine GiD_PostInporeFile( const char “£ilename) ) ( return 0; // 1 ~ on exroz (GID_DLL_EXPORT const char *GiD_Post ImportGetLibane( void) ( GID_DLL_EXPORT const char *GiD_Post InportGeeFileEutensions( void) ( setusn "((Bavefzont Objects) (.0b3)) ((All files) 712", GeeDescription( void) ( (GID_DLL_EXPORT const char *GiD_Post ImportGetExxerstz( void) ( sevusn 6 exx_stz; // if exzer, returns the exzor string When GiD is told to load the dynamic library, it will look for, and will call these functions: GiD_PostimportGetLibName : returns the name of the library and should be unique. This name will appear in the File->Import->Plugin menu and in the right menu. GiD_PostimportGetFileExtensions : which should return a list of extensions handled by the library and will be used az filter in the Open File dialogue window. GiD_PostimportGetDescription: : returns the description of the library and will be displayed in the title bar of the Open File dialogue window Once the library is registered, when the user selects the menu entry File->Import->Plugin->New Plugin the Open File dialogue window will appear show ing the registered filters and description of the plug-in. recone Be mp =e)" son nen ag ingen Flezame suenes) Fis ofan Oe (08) When the user selects a file then follow ing functions are called GiD_Postimporttile : this function should read the file, transfer the mesh and results infermation to GID and return 0 if no problems appeared while the file was read or 1 in case of error. GiD_PostimportGetErrorSte : this function will be called if the previous one returns 1, to retrieve the error string and show the message to the user. 9.2.4 Functions provided by GiD Inside the GiD_PostimpertFile function, following functions can be called to pass information to GiD}Functions provided by GiD 116 extern "C" int GiD_HewPostProcess( void); ode, © gidifeshtype mesh eype, conse char “nane); extern "CY ine GiD_SetColoz( ine id, float red, float green, float blue, float alpha); extern "CH int GiD_SetVertenPointer( int id, Teigiavercextisetype list type, unsigned int offset_next_element, const void *peinter); int G3D_SetElementPoinces( int 4a, const void ‘pointer, Sinse void télewe pees ine GiD_MewResult( const char *analyzis_nane, double step_value, (const char *result_name, int mesh id); ing GiD_SetResulePoinces( ine 5a, Telgianesetenisetype Lise type, conse void *peinees); extern "C" int GiD_EndResule( ine id); ‘Tel_Intexp *GiD_GetTel Interpreter(); Here is the description for each provided function: GiD_NewPostProcess : starts a ne post-process session, deleting all mash and results information inside GID. GiD_NewMesh : a new mesh will be transferred to GiD and an identifier will be returned so that more information can be defined for this mesh, Follow ing parameters must be specified: _£.gidMode gid_mode : may be one of GID_PRE or GID_POST. At the moment only GID_POST is supported _tgidMeshType mesh_type : may be one of GIDPOST_NEW MESH, GIOPOST_MERGE_MESH and GIDPOST_MULTIPLE_MESH. At the moment only GIDPOST_NEW_MESH has been tested const char *hame : name of the mesh which will appear in the Display Style window GiD_Setcolor : to specify 2 colour for the mesh identified by the given id. The red, green, blue and alpha components should be betw een 0.0 and 2.0. GiD_SetVertexPointer : sets the vertices of the mesh identified by the given id. This vertices are the ones to be referred from the element's connectivity. Following parameters may be set: tL gidBasicType basic_type : data type of the coordinates of the vertices, should be one of GIDPOST_FLOAT or GIDPOsT_DOUBLE: _£.gidVertexListType list type : herewith the format of the vertices is specified, Should be one of GIDPOST_VERTICES: where all_num_components coordinates are specified with no label and so they will be numerated bet een 0 and num_vertices-1 GIDPOST_IDX_VERTICES: where each set of num_components coordinates are preceded by a label indicating its node number (should be 2 4-byte integer) int nur_components : number of coordinates per vertex int nur_vertices : number of vertices in thelist Unsigned int offset_next_element : distance in bytes betu een the beginning of vertex i and the beginning of vertex i+ 1. If Oi entered then the vertices are all consecutive const void "pointer : pointer to the list of verticesFunctions provided by GiD 117 GiD_SettlementPointer : sets the elements of the mesh identified by the given id. The elements connectivity refers to the previous specified list of vertices. Note that for spheres and circles net only their connectivity should be specified but also their radius and eventually their normal. In this case bro separate vectors should passed: one for the integer data and another one for the floating point data. Following parameters may be set: _t.gidBacicType basic type : data type of the extra data entered for sphere and circle elements, should be one of GIDPOST_FLOAT or GIDPOST_DOUBLE _t.gidelermentlistType list type : herewith the format of the slements is specified. Should be one of GIDPOST_CONNECTIVITIES: where all the elements are specified without element number, thus being automatically numbered bet ean 0 and num_elements-2 GIDPOST_IDX_CONNECTIVITIES: where each element is preceded by a label indicating its element number (should be a 4-byte integer) _tgidelementType element type: type of clement to be defined. May be one of GIDPOST_TRIANGLE, GIDPOST_QUADRILATERAL, GIDPOST_LINE, GIDPOST_TETRAHEDRON, GIDPOST_HEXAHEDRON, GIDPOST_POINT, GIDPOST_PRISM, GIDPOST_PYRAMID, GIDPOST_SPHERE, GIDPOST_CIRCLE int num_elements : number of elements inthe list Unsigned int offset_next_element : distance in bytes bet een the beginning of element i and the beginning of element 42. IFO is entered then the elements are all consecutive const void *pointer : pointer to the list of the elements connectivity (integer data) Unsigned int offset_float_data : distance in bytes bet een the beginning of float data of elerment i and the beginning of float data of element i41. If 0 is entered then the element's float data are all consecutive const void *float_ptr : pointer to the list of the floating point data for the elements. For spheres only the radius should be specified, s0just a single value, and for circles four values should be specified: its radius and the three components of the normal. GiD_NewResult : a nev result will be defined for GiD and an identifier will be returned so that more information can be defined for this result, Follouing parameters must be specified const char *analysis_name ! analysis name of the result double step_value : step value inside the analysis where the result should be defined const char *result_name : result name int mesh_id : mash identifier where the result is defined. If 0 is entered the result will be defined for all meshes. GiD_SetResultPointer : specifies the lit with the result values for a given results id, Following parameters may be set “t gidB asicType basic type : data type of the results, should be one of GIDPOST_FLOAT or GIDPOST_DOUBLE Te gidRecultListType list_type : herewith the format of the results is specified. Should be one of GIDPOST_RESULTS: where all results are defined consecutively and will refer to the nodes / elements bet een 0 and nur_results-1 GIDPOST_IDX_RESULTS: where each result is preceded by a label indicating its node /element number (should be a 4-byte integer) _tgidResultType result_type : type of result which will be defined May be one of GIDPOST_SCALAR, GIDPOST_VECTOR_2 (vector result with 2 components), GIDPOST_VECTOR_3 (vector with 3 components), GIDPOST_VECTOR_4 (vector with 4 components, including signed modulus), GIDPOST_MATRIX_3 (matrix with 3 components Sxx, Syy and Sxy), GIDPOST_MATRIX.4 (Sixx, Syy, Sxy and Szz, GIDPOST_MATRIX_6 (Sx, Syy, Sxys ‘Sez and Syz and Sxz), GIDPOST_EULER (with 3 euler angles), GIDPOST_COMPLEX_SCALAR (real and imaginary part), GIDPOST_COMPLEX_VECTOR_$ (2d complex vector: Var, Vxi, Vyr and Vyi), GIDPOST_COMPLEX_VECTOR_6 (2d complex vector: Var, Vii, Vyr, Vyir Var and V2i) and GIDPOST_COMPLEX_VECTOR_9 (3d complex vector: Vir, Vii, Vyrs yi. Var, Vai, [real part|, imaginary part| and signed |vectorl) __t gidResultLocation resuit_lecation : location of the result. May be one of GIDPOST_NODAL, GIDPOST_ELEMENTAL or GIDPOST_GAUSSIAN. At the moment GIDPOST_GAUSSIAI is not supported int nurm_resuits : number of results in the list Unsigned int offset_next_elerent : distance in bytes bet een the beginning of result i and the beginning of result i+. If Oi entered then the reusits are all consecutive const void "pointer : pointer to the list of results. GiD_EndResult : indicates GiD that the definition of the result with the give id is finished. GiD will process the result GiD_EndMesh : indicates GiD that the definition of the mesh with the give idis finished. GiD will process the mesh. GiD_GetTelInterpreter : returns 2 pointer to GiD's global interpreter so that the plugin can open their windows or execute their tcl scripts using the predefined tel procedures of Gib.Functions provided by GiD 118 ‘The developer should keep in mind that all the plug-in code is executed inside GiD's memory space and so, all the memory allocated inside the plug-in should also be freed inside the plug-in to avoid memory accumulation when the dynarric library is called repeatedly. This also includes the arrays passed to GiD, which can be deleted just after passing them to GiD. 9.2.5 List of examples ‘The plug-in examples provided by GiD also include some little models of the pravided import format: ‘These are the import plug-ins provided by GID so far: OBJ: Wavefront OBJ format ‘This is a starter example which includes the create_deme_triangs function which creates a very simple mesh, “The obj format is a very simple ascii format and this plug-in: reads the file, creates a GiD mech with the read triangles and quadilaterale, and, ifthe information about the vertex normals is present, then this information is passed to GiD as nodal vector results, OFF: Object file format This example is very similar to the previous ene. “The off format is a very simple ascii fermat but including n-agons and colour on vertices and faces. So, this plug-in reads the file, creates a GID mesh with the read triangles and quadiilaterals and triangulates the read pentagons and hexagons (and discards bigger n-agons), if colour information is present in the off file, which can be present on the nodes or on the elements, then this Information is passed to GiD as nodal or elemental results. PLY: Polygon file format This example is a little bit more complex. Ply files can be ascii or binary, and the code of this plug-in is based in Greg Turk's code, developed in 1998, to read ply files. This format allow s the presence of several properties on nodes and faces, too. This plugsin: reads the file, creates a GiD mech with the read lines, triangles and quadrilateral, if information about the vertex normals is found, then this information is passed to GiD as nodal vector results, all the properties defined in the ply file are passed to GID. This properties can be defined on the nodes of on the faces of the model, and so are they transferred to GiD. Here the complexity alzo resides in the liberation of the reserved memory, which is wildly allocated in the ply code, PLY + Tcl : Polygon file format ‘This plug-in is the same as the previous PLY plug-in but a tcl script is added inside the code to show a progress bar in tel to keep the user entertained while big files are read.119 10 APPENDIX A (PRACTICAL EXAMPLES) To learn how to configure GiD for a particular type of analysis, you can find some practical examples: * By following the tutorial of the chapter Defining a problem type of the GiD user manual. * By studing and modifing some existing Problem Types Problem types included in GiD by default as example in $61D/problemtypes/Examples: + emas2d: This is the problem type created in the tutorial, which finds the distance of each element relative to the center of masses of a two-dimensional surface, It uses the follow ng files: end, .mat, -pxb, -bas, tel and -ba®, ‘There is a help file inside directory cmas2d.gid called cmas2d.html ‘emas2d_customlib: The same problem type, but implemented using the ‘Custom library’ developed by CompassiS. http://w ow .compassis.com. complex_example: uses some basic Tel/Tk interaction (in complex_example tel) with GiD to! + add anew menu in GiD's menu bar: * create an icon bar for the problem type, mith their own images: * using conditions to evaluate user defined formulae at the nodes of the domain: look into complex_ecanple ond and compl ex_ecanple bas Other problemtypes can be downloaded from the Data->Problem type->Intemnet retrievemenu: © Kratos: Multiphysics FEM open source C++ code. + RamSeries: This is a problem type w hich performs the structural analysis of either beams or shells ot a combination of both using the Finite Element Method, This problem type uses the latest features offered by GiD . The -*x* file for Windows systems is also included in a limited version, dyn: Multiphysics solver (including CFD, heat transfer, species advection, pde solver and free surface problems) CompassFEM is a suite that includes both Tdyn and RamSeries codes © NASTRAN: Static and dynamic interface for the NASTRAN commercial analysis program (not included) For the full version without limtations check http://1rw v .compassis.com,APPENDIX B (classic problemtype system) 120121 11 APPENDIX B (classic problemtype system) From version 13 of GiD, a new system of problem types has been developed, which offers several advantages compared with the old (classic) system: it organizes better the data, provides with a more intuitive and user-friendly GUI, enable more sofisticated integration tools, atc... From this version on, this ‘classic’ system of problemtypes is considered deprecated, how ever, itis stil supported by GiD. ‘The classic problem type system uses the files .prb, .mat, .cnd, .uni to define general properties, materials, conditions, units Each cathegory of data is show ed in a kind of window , and materials and conditions are associated to entities. About writting the input file for the solver, the classical approach uses simple .bas GiD terrplates 411.1 PROBLEMTYPE ‘CLASSIC’ ‘The creation of a Problem Type involves the creation of a directory located inside the \problemtypes GiD folder, with the name of the problem type and the extension . id. Problemtypes that exists when GiD start will appear in its menu (see Problem type from Reference Manual). ‘The problerrtype configuration files are a collection of files inside this subfolder. The name for most of them mill follow the format problem_type_name.xxx where the extension refers to their particular function. Considering problem type_name to be the name of the problem type and project_name the name of the project, file configuration is described by the following diagram: Prprosess GO mp Resutefie | Posprososs Pospeost 60 * Directory name: problem _type_name.cid * Directory location: c/\a\b\c\SiD_directory\problertypes Configuration files * problem type_name. xml XML-based configuration * problem type_name.cnd Conditions definitions * problem type_name.mat Materials properties * problem type_name-prb Problem and intervals data * problem type_name.uni Units SystemsPROBLEMTYPE ‘CLASSIC’ 122 * problem type_name:sim Conditions symbols . ‘*¥*,ge0 Symbols geometrical definitions . ‘*¥*.ge0 Symbols geometrical definitions + Template files * problem type_name-bas Information for the data input fle . *#*;bas Information for additional files . ****;bas Information for additional files .. * Tel extension files * problem type_namectel Extensions to GID written in the Tel/Tk prograrnming language + Command execution files * problem type_name-bat Operating system shell that executes the analysis process ‘The files problem type_name.sim, ***.geo and ***.bas are not mandatory and can be added to facilitate visualization (both kinds of file) or to prepare the data input for restart in additional files Gust ***.bas files). In the same way problem type_name.xml is not necessary; it can be used to customize features such ast version info, icon identification, passu ord validation, ete 11.4.4 CONFIGURATION FILES ‘These files generate the conditions and material properties, as wall as the general problem and intervals data to be transferred to the mesh, at the same time giving you the chance to define geometrical draw ings or symbols to represent some conditions on the screen, ana 1 Conditions file (.end) Files with extension .cnd contain all the information about the conditions that can be applied to different entities. The condition can adopt different field values for every entity. This type of information includes, for instance, all the displacement constraints and applied loads in a structural problem or all the prescribed and initial temperatures in a thermial analysis, 'An important characteristic of the conditions is that they rust define what kind of entity they are going to be applied over, ike. over points, over lines, over surfaces, over volumes, over layers or over groups, and hat kind of mesh entity they will be transferred over, i.e, over nodes, over face elements or over body elements. + Over nodes This means that the condition will be transferred to the nodes contained in the geometrical entity where the condition is assigned, * Over face elements ?multiple? If this condition is applied to a line that is the boundary of a surface or to a surface that is the boundary of a volume, this condition is transferred to the higher elements, marking the affacted face, If tis declared ac multiple, it can be transferred to more than one element face (if more than one exists). By default it ir considered as single, and only one element face will be marked * Over body elements If this condition is applied te lines, it will be transferred to line elements. If assigned to surfaces, it ill be transferred to surface elements, Likewise, if applied to volumes, it will be transferred to volume elements. Note: For backw ards compatibility, the command ‘over elements! is also accepted; this will transfer the condition either to elements or to faces of higher level elements. ‘Another important feature is that all the conditions can be applied to different entities with different values for all the defined intervals of the problem. ‘Therefore, a condition can be considered as a lst of fields containing the name of the particular condition, the geometric entity over which it is applied, the mesh entity over which it will be transferred, its corresponding properties and their values. “The format of the file is as follows COMMMESMTWE: ‘over nedes', ‘over face elements’, ‘over face elements mltiple!, ‘ever body elements! QUEST IoM: field name "BCBE "(optional value {,---)] VALUE: detaule Field valuel '#¥IDTHF (optional _enczy Lengeh)] QUESTION: fie14 panel ‘#CBE'(..joptional_value_{,--.)1Conditions file (.end) 123 VALUE: default _¢ie14_valuel '#VIDTME(optional_enczy_Lengeh) Note: CONDTYPE and CONDMESHTYPE are compulsory, and only a kind of type must be set Note: GROUPALLOW is only valid for conditions ‘over groups! , is an special optional field to restrict allowed categories of tenties of the group to the ones listed (if this field is missing then all kind of entities are allowed). A list of multiple types could be set Note: #cB# means Combo Box. Note: #WIDTH# means the size of the entry used by the user to enter the value of the condition, Spacifies an integer value indicating the desired width of the entry window , in average-size characters of the widget's font. Local Axes QUESTION: fietd pane 'PLAB'( ‘global ', ‘aucomavic!, ‘automatic altesnative!, ‘automatic main!) VALUE: detaule Field valuel '#¥IDTME'(opeional_entzy length) 1 ‘This type of field refers to the local axes system to be used, The position of the values indicates the kind of local axes. If it only has a single default value, this will be the name of the global axes. Ibo values are given, the second one will reference a system that will be computed automatically for every node and will depend on geometric constraints, like whether or not itis tangent, orthogonal, etc If a third value is given, it will be the name of the automatic alternative axes, which are the automatic axes rotated 90, degrees. If a fourth value is given, it will be the name of the automatic main axes, valid only for sufaces using the main curvature directions. (note that sometimes main curvatures are not well defined, e.g. for a planar surface or a sphere all directions are main directions, bacause the curvature is constant) All the diferent user-defined systems will automatically be added to these default possibilities, To enter only a specific Kind of local axes it is possible to use the modifiers #G#,#A# ,#L#,#ME. + #68: global axes; + Aw: automatic axes: + HL: automatic alternative axes. + #M: main curvature axes When using these modifiers the position of the values does net indicate the kind of local axes. Example QUEST IoM: Local_Aves#LAS (option auconaticHAF, Option automatic ale#i#) Not 1 All the fields must be filled with words, where @ word is considered as a string of characters without any blank spaces, The strings signaled between quotes are literal and the ones inside brackets are optional. The interface is case-sensitive, s0 any uppercase letters must be maintained, The default field_value entry and various optional_value_j entries can be alphanumeric, integers or reals. GID treats them as alphanumeric until the moment they are written to the solver input files. Global axes: 00 10 z-002 Automatic axes For surfaces, this axes are calculated from the unitary normal i aN IF Wis coincident with the glebal Y direction (1Nx or Itz > some tolerance) then PVM /IYXN| else ZaN/ IZ XN YeW xx!Conditions file (.end) 124 zen For lines, this axes are calculated from the unitary tangent T! x=T if Tis coincident with the global Z direction (Wx or Ny > some tolerance) then ‘Automatic alternative axes: ‘They are calculated like the automatic case and then sw ap x and y axes: For curves x'=unitary tangent to the curve on the place where the condition is applied If this tangent is different of the Z global axe=(0,0,1) then VV x! ase Yezxx Bex xy! Note: the tangent x' is considered different of (0,0,2) is the fist or second component is greater than 1/64 Main curvature axes: They are calculated for surfaces finding on a point the directions where the curvatures are maximum and minimum, but these directions are not always well defined, 49, in a planar point the curvature is zero in all directions, all directions could be seen as main directions, and in 2 sphere the curvature is constant=1/Radius and it happen the same. Multiple assign By default @ condition can be applied only once to the same entity and last assignation replace previous one, but this behavior can be changed: One fiag that can optionally be added to a condition is It is written after CONDMESHTYPE and means that one condition can be assigned to the same entity several times. Self Calculated #FUNC# fields: ‘Another type of field that can be included inside a condition is a #FUNC# to do some calculation, where the key #FUNC#, means that the value of this field will be calculated just when the mash is generated. It can be considered ac a function that evaluates when meshing. Valid variables for a #FUNC# field are: + thane ity; to track the numerical id of the geometric source entity + y= : touse the coordinates of the node or entity center y here the condition is applied + Cond(num_£ield,FEAL); to use the value of other fields of this condition (REAL or INT declare that must be considered as a real or a integer number) * Valid mathematical operations are the sare as the used for the "Operation termplate command. es QUEST IoM: Surface runbex#FUNCE (imEne icy) In the above example, TunEne ity js one of the possible variables of the function. It will be substituted by the label of the ‘geometrical entity from where the node or element is generated. QUEST IoM: ¥_press#FUNCH (Cond(2,REAL)*(x-Cona(1,REAL))/ (Cond BEAL) -Cond(1,BEAL))) In this second example, the variable is used, which means the x-coordinate of the node or of the center of the element. Others fields of the condition can also be used in the function. Variables ¥ and = give the y- and z-coordinates of this point.Conditions file (.end) 125 Note: There are other options available to expand the capabilities of the Conditions window (see Special fields), ana -1 Example: Creating the conditions file Here is an example of how to create a conditions file, explained step by step: 1. First, you have to create the folder or directory where all the problem type files are located, problem _type_name.cid in this case 2 Then create and edit the file (problem_type_name.cnd in this example) inside the recently crested directory (where all your problem type files are located). As you can see, except for the extension, the names of the fle and the directory are the same, 2 Create the first condition, which starts with the lin ‘The parameter is the name of the condition. A unique condition name is required for this conditions file, 4 This first line is follow ed by the next pair: hich declare what entity the condition is going to be applied over. The fist line, CONDTYPE:... refers to the geometry, and may take as parameters the sentences “over points", “over lines", "over surfaces" or “over volumes” ‘The second line refers to the type of condition applied to the mesh, once generated. GiD does not force you to provide this second parameter, but ifit is present, the treatment and evaluation of the problem will be more acurate, The available parameters for this staterent are "over nodes" and "over elements! 5 Next, you have to declare a set of questions and values applied to this condition, QUEST IoM: Local-AcesBLAg (-GLOBAL-) QUEST IoM: X-Force QUEST TOM: x-Consezaine:#¢B8(1,0) QUEST Tom: x_axis:#cBg (DEFORMAT 1OH_Xx,DEFORMAT ToM,_X¥,DEFORMAT Iom_x2) ‘After the QUESTION: prompt, you have the choice of putting the follow ing kinds of w ord * An alphanumeric field name, * An alphanumeric field name follon ed by the #LA# statement, and then the single or double parameter. * An alphanumeric field name follov ed by the #CB# statement, and then the optional values bet ean parentheses. ‘The VALUE: prompt must be followed by one of the optional values, if you have declared them in the previous QUESTION: line. If you do not observe this format, the program may not » ork correctly, In the previous example, the X-Force QUESTION tales the value 0,0, Also in the example, the X-Constraint QUESTION includes a Combo Box statement (4CB#), follow ed by the declaration of the choices 1 and 0. In the next line, the value takes the parameter 1. The X_axis QUESTION declares three items for the combo box: DEFORMATION_Xx,DEFORMATION_XY,DEFORMATION_XZ, with the value DEFORMATION_XX chosen. Bev are of leaving blank spaces between parameters. If in the first question you put the optional values (-GLOBAL, -AUTO-) (note the blank space after the comma) there mill be an error when reading the file. Take special care in the Combo Box question parameters, so as to avoid unpredictable parameters, 6 The conditions defined in the .end file can be managed in the Conditions window (Found in the Data menu) in the Preprocessing component of GiD.Example: Creating the conditions file 126 11.1.1.2 Problem and intervals data file (.prb) Files with the extension .prb contain all the information about general problem and intervals data The general problem datas all the information required for performing the analysis and it does not concern any particular geometrical entity ‘This differs from the previous definitions of conditions and materials properties, which are assigned to different entities. An example of general problem data is the type of solution algorithm used by the solver, the value of the various time steps, convergence conditions and so on. Within this data, one may consider the definition of specific problem data (for the whole process) and intervals data (variable values along the different solution intervals). An interval would be the subdivision of a general problem that contains its own particular data, Typically, one can define a different load case for every interval or, in dynamic problems, not only variable loads, but also variation in time steps, convergence conditions and so on. “The format of the file is as follows QUEST IoM: fie1d_nanet '$CBE'(..,optional_value_{,--.)1 QUESTION: fieta panel 'BCBB'(...,optional_value_{,--.)1 QUEST IoM: fieid panel 'BCBE'(..,optional_value_{,--.)1 QUESTION: fie14 panel 'BCBE'(..,optional_value_{,--.)1 All the fields must be filled with w ords, where a word is considered as a string of characters without any blank spaces, The strings signaled betw een quotes are literal and the ones inside brackets are optional. The interface is case-sensitive, so any Uppercase letters must be maintained The defauit field value entry and various optional_value_i entries can be alphanumeric, integers or real numbers, depending on the type, Not ‘There are other options available to expand the capabilties of the Problem Data window (see Special fields). 11.1.1.2.1 Example: Creating the PRB data fle Here is an example of how to create a problem data file, explained step by step: 11 Create and edit the file (problem type_name.prb in this example) inside the problem_type_name directory (where all your problem type files are located). Except for the extension, the names of the file and the directory rust be the 2 Start the file with the line 3 Then add the follow ing lines: QUESTION: Unie_systenfCBE(ST,C63,Usex)Example: Creating the PRB data file 127 question: Tiete ‘The first question defines a combo style menu called Unit_System, which has the SI option selected by defauit. The second question defines a textfield called Title, and its default value is Default_ttle. 4 To end the file, add the following line 5S The whole file is as follows: QUEST IOM: Unie_systenfCBE(ST,C63,Usex) QUEstion: Tscte 6 The options defined in the .prb file can be managed in the Problem Data window (found in the Data menu) in the Preprocessing component of GiD. ese a 411.1.1.3 Materials file (.mat) Files with the extension .mat include the definition of different materials through their properties. These are base materials as they can be used as templates during the Preprocessing step for the creation of newer ones. You can define as many materials as you nish, with a variable nurrber of fields. None of the unused materials will be taken into consideration when writing the data input files for the solver. Alternatively, they can be useful for generating a materials library Conversely to the case of conditions, the same material can be assigned to different levels of geometrical entity (lines, surfaces or volumes) and can even be assigned directly to the mesh elements. In a sirvilar way to how @ condition is defined, a material can be considered as a group of fields containing its name, its corresponding properties and their values. “The format of the file is as follows QUEST IoM: field panel "BCBE'(...joptional_value_{,--.)1 QUESTION: fie14 panel 'BCBE'(..,optional_value_{,--.)1 All the fields must be filled with w ords, where a word is considered as a string of characters without any blank spaces, The strings signaled betw een quotes are literal and the ones within brackets are optional. The interface is case-sensitive, so any uppercase letters must be maintained The default field value entry and various optional_value_i entries can be alphanumeric, integers or real numbers, depending on their type, Not ‘There are other options available to expand the capabilities of the Materials window (see Special fields).Example: Creating the materials file 128 11.1.1.3.1 Example: Creating the materials file Here is an example of how to create a materials file, explained step by step: 1. Create and edit the file (problem type_name.mat in this example) inside the problem type_name directory (where all your problem type files are located). As you can see, except for the extension, the names of the fle and the directory are the same, 2 Create the first material, which starts with the line: “The parameter is the name of the material. A unique material name is required for this into this materials file (do not use blank spaces in the name of the material) 3 The next two lines define a property of the material and its default value: GUEST 10M; Density ‘You can add as many properties as you wish. To end the material definition, add the following line: 4 In this example w @ have introduced some materials; the .mat file would be as follows: QUEST Iom!: Denssey question: Yount _(Ex) QUEST Ion: SHEAR MODUL question Porssom_cmuxy) question aLex QUEST Iom DENSITY_(DENs) QUEST om: Denssey 5 The materials defined in the .mnat file can be managed in the Materials window (found in the Data menu) in the Preprocessing component of GiD. 1.1.1.4 Special fields + Array fields Fields of conditions, problem data or materials could store an array of values, and the lenght of this array is not predefined, could be set at runtime. For example, if a material has a variable property (an exarrple would be where a property was dependent on temperature and was defined with several values for several temperatures) a table of changing values may be declared for thisSpecial fields 129 property. When the solver evaluates the problem, it reads the values and applies a suitable property value. “The declaration of the table requires two lines of text: “The first is @ QUESTION line with a list of alphanumeric values bety ean parentheses. QUEST IoM: fieid_nane(colwm eitle_ty-..,colwm eitie_n) ‘These values are the names of each of the colurmns in the table so that the number of values declared is the number of columns. This first line is follow ed by another with the default data values. It starts with the words VALUE: #1N#, and is follow ed by 2 number that indicates the quantity of elements in the matrix and, finally, the lst of values, VALUE: 8 nonber_of values value... value_o “The number of values m declared for the matrix obviously has to be the number of colurans n multiplied by the number of rows to be filled es GUEST ion. Typela QUEST om: Inteznal_Poines(,¥,2) VALUE: gg 20.0 0-0 0.0 and example writting the values of this material from the .bas template: TEMPLATE FILES Sse (sezonp (Maepzep (Type la) , Mleval ")==0) seee var lttacprop (Ineernal_Poines, ine) Seoe(s21; $e—m S442) SMatprop| Inteinal Points *i) *Matprop (Internal Points, toperation(it1)) ‘Matprop( Internal Points, *operati entit2)) Note that in the example a hidden field named "Typeld! is used to identify this and its derivated materials, © Aesthetic fields ‘These fields are useful for organizing the information within data files. They make the information shown in the data windows more readable, In this w ay you can better concentrate on the data properties relevant to the currant context. + Books: With the Book field itis possible to split the data windows into other windows. For example, we can have ‘bro windows for the materials, one for the steals and another for the concretes All steals come here All concretes come here boneSpecial fields 130 “The same applies to conditions. For general and interval data the book field groups a set of properties. + Title: The Title field groups a set of properties on different tabs of one bosk. All properties appearing after this field will be included on this tab. Basics properties Advanced properties + Help: With the Help field it is possible to assign a description to the data property preceding it, In this w ay you ‘can inspect the meaning of the property through the help context function by holding the cursor over the property or by right-clicking on it. (QUESTION: X-Constraint## CB # (1.0) VALUE: 2 HELP: IF this flag is set, movernent is. * Image: The Image field is useful for inserting descriptive pictures in the data window. The value of this field is the file name of the picture relating to the problem type location.Special fields 131, ata window with an image © Unit field: With this feature itis possible to define and w ork with properties that have units, GiD is responsible for the conversion bet een units of the same magnitude QUESTION: Norrmal_pressure#UNITS# VALUE: 0.0Pa Data property with units + Dependencies: Depending on the value, we can define some behavior associated with the property. For each value we-can have a list of actions, The syntax is as follow: DEPENDENCIES:( ,[ TITLESTATE,