Menu: Data->Problem type
This option lets you choose between all installed Problem Types. When selecting a new problem type, all information about materials, conditions and other data parameters that were already selected or defined is lost.
Note: When defining a new problem type which is not already installed, it must be selected by other means. One possibility is to select Problem type -> Load... . Another possibility is to select "data defaults problemtype" in the Right buttons menu or enter it in the command line.
A problem type is considered to be installed when it has been copied to the GiD Problem Types directory (<GiD>/problemtypes) or to another subdirectory within this (then will appear in the Problem type menu)
It is also possible to copy the problemtype inside the user settings directory of a GiD version
e.g.
| Code Block |
|---|
C:\Users\<your_windows_user>\AppData\Roaming\GiD\<version>\problemtypes |
or
| Code Block |
|---|
$(HOME)/.gid/<version>/problemtypes |
This option if interesting if an user doesn't has privileges to copy the problemtype at <GiD>/problemtypes
Note: Instead of copying the problem type to the Problem Types directory, it is also possible to create a Windows shell link (a direct access), or a UNIX link, pointing to the real location. This option is particularly interesting for developers, as it avoids duplicating the code.
Data Menu>Problem type>Transform problem type
Menu: Data->Problem type->Transform...
This option can be found inside the Problem Type menu and is useful for updating a model from an old problem type to a newer one that is similar to the first.
When converting, it tries to maintain all the conditions and materials assigned to the geometry or mesh. Also, it tries to maintain the rest of the data.
It will typically be used when a problem type has been updated and it is necessary to reuse a model defined with the old version.
Data Menu>Problem type>Internet retrieve
Menu: Data->Problem type->Internet retrieve...
With this option it is possible to download new problem types or update existing ones.
It is also possible to download other resources like themes, fonts, translations, examples, plugins,...
Note: You need to be connected to the Internet to use this option.
Select a list item and use the Problem type info and Problem type news buttons to get information about them.
Use the Retrieve Problem type button to download the selected problem type. The problem type will be installed inside the Problem Types directory.
download.xml file
If a problemtype folder contain a file named 'download.xml' then if the user try to select this problemtype it will be asked to be downloaded through the 'Internet retrieve' mechanism. This avoid install all big problemtypes and later download the ones that the user really wants.
The content of this file must be something like this:
<?xml version="1.0" encoding="utf-8"?>
<DownloadProblemtype version='1.0'>
<Program>
<Name>Abaqus</Name>
<Version></Version>
<ShortDescription>Pre and postprocessing nonlinear analysis software ABAQUS</ShortDescription>
</Program>
</DownloadProblemtype>
Data Menu>Problem type>Load
Menu: Data->Problem type->Load...
The Load... option allows you to load a previously installed problem type from the current or another directory. This possibility is useful when developing a new problem type which cannot be installed until it is finished, or if the developer does not have permission to write to the Problem Types directory.
Data Menu>Problem type>Unload
Menu: Data->Problem type->Unload
This option unloads the problem type currently in use.
Sometimes it is easier to work with a model that does not have an associated problem type. It is also useful for sending a model to another user who does not have the problem type in question.
Data Menu>Problem type>Debugger
Menu: Data->Problem type->Debugger...
This tool is a graphical debugger for the scripting language Tcl/Tk.
It can be opened also with the <F12> key
This debugger has additional capabilities such as:
- Editing the code. It is possible to edit the code inside its own editor and resend the new code without closing the debugged program.
- The Tcl/Tk source code is colorized and supports automatic indentation.
- When one source code line stops the debugger, it is possible to view all the variables and expression values, as well as change them.
- It has additional options to measure execution times in the debugged program.
It is possible to use Tcl/Tk to enhance a problem type (see TCL\TK EXTENSION from Customization Manual).
Tcl code can be invoked inside GiD from a problem type (.tcl, .bas, .bat or .xml files), from user-defined macros, from a batch file, etc.
To start debugging must open the desired tcl file, press <F9> to set/remove breakpoints, and press <F5> to re-instrument its procedures and start debugging
More information can be found in this debugger's own help section.