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.

Note: now it is also possible to have a /problemtypes extra folder located at the <GiD user preferences folder>. This is interesting in case that the user doesn't has privileges to copy a problemtype inside <GiD folder>/problemtypes

This set of files define the problemtype and contain the full functionality for customizing the pre-process. The main files that configure the problem type are shown in the table below.

File extension	Description
<namd>.xml	Simple declarations of name, version, etc. XML-based
<name>.spd	Main configuration file of the data tree, XML-based
<name>.bas	Template with simple GiD syntax to create data input file.
<name>.tcl	Main Tcl/Tk file, initialization. e.g. to create data input file.
<name>.cnd	Conditions definition. It should not be modified by the user
<name>.transform	To aid to convert data from a model created with an old version of the problemtype

<name>.spd 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 is defined in XML format with the extension .spd (specific problem type data) and contains all the definition of all the data that defines the analysis like boundary conditions, loads, materials, load cases, 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 it is 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.

<name>.tcl Main Tcl file, initialization

A Tcl initialization file is used to create complex windows or menus. Contains the initialization routines. Can source other Tcl files.

Output description to the file of analysis

A Tcl file located in the <scripts> folder determines the way in which the final information has to be written inside the input files that will be read by the solver.

<name>.cnd

File with extension .cnd is used but should not be modified by the problemtype creator. It is only required if local axes are used.

<name>.transform

An optional file that describe how to map old names into current problemtype names. Is used to read models created with old versions of the problemtype, with some differences of names, etc along the versions.