This is gid.info, produced by Makeinfo version 3.12h from gid.texinfo.

   This is the GiD manual

   Copyright 1997-2002 CIMNE


File: gid.info,  Node: postprocessing results,  Next: Customization,  Prev: POSTPROCESS OPTIONS,  Up: Top

POSTPROCESSING RESULTS
**********************

* Menu:

* Contour Fill::
* Contour Ranges::
* Contour Lines::
* Show Minimum and Maximum::
* Display vectors::
* Iso Surface::
* Stream Lines::
* Line Diagrams::
* Legends::
* Graphs::
* Deform Mesh::
* Do Cuts::
* Animation::
* Automatic comments::
* Several results::

   The possible results to be displayed can be grouped into five major
categories:
   * Scalar view results: Show Minimum & Maximum, Contour Fill, Contour
     Lines, Iso Surface and its configuration options.

   * Vector view results: Mesh deformation, Display Vectors, Stream
     Lines (Particle Tracing)

   * Line diagrams: Scalar line diagram and vector diagrams.

   * graph lines: XY plots.

   * animation: animation of the current result visualization ( now
     only deformation and contour fill/lines).


   The View Results menu and the View Results window are used to manage
the visualization of the different type of results.

   The View Results menu lets you select any type of result:

   - Contour fill

   - Contour lines

   - Diplay vectors

   - Show min/max

   - Iso surfaces

   - Stream Lines

   - Graphs

   - Deformation


   The View Results window manages the visualization of the following
type of results:

   - Contour fill

   - Contour lines

   - Diplay vectors

   - Show min/max

   As the results are grouped into steps and analysis, GiD must know
which analysis and step is the currently selected for displaying
results.  The `Analysis' menu of the View Results window is used to
select the current analysis and step to be used for the rest of the
results options. If some of the results view requires another analysis
or step, the user will be asked for it.

   *Note*: To stop viewing a result, the user can select `No Result' in
this window or in the View results menu.

* Menu:

* Contour Fill::
* Contour Lines::
* Show Minimum and Maximum::
* Display vectors::
* Iso Surface::
* Stream Lines::
* Line Diagrams::
* Legends::


File: gid.info,  Node: Contour Fill,  Next: Contour Ranges,  Prev: postprocessing results,  Up: postprocessing results

Contour Fill
============

   This option allows the visualization of colored zones, in which a
variable, or a component, varies between two defined values. GiD can
use as many colors as allowed by the graphical capabilities of the
computer. When a high number of colors is used, the variation of these
colors looks continuous, but the visualization becomes slower unless
the Fast-Rotation option is used.  A menu of the variables to be
represented will be shown, from which the one to be displayed will be
chosen, by using the default analysis and step selected.

   Vectors will be unfolded into X, Y, and Z components and its module.
Symmetric matrix values will be unfolded into Sxx component, Syy
component, Szz component, Sxy component, Syz component and Sxz
component of the original matrix and also into Si component, Sii
component and Siii component in 3D problems or angular variation in 2D
problems. Any of these components can be selected to be visualized.

   Several configuration options can be accessed via the Options menu.

   * Number Of Colors: Here the number of colors of the results color
     ramp can be specified.

   * Width Intervals: fixes the width of each color zone. For instance,
     if a `width interval' of 2 is set, each color will represent a
     zone where the results differ at the most in two units.

   * Set Limits: this option is used to tell the program which contour
     limits should use when there are no user defined limits: the
     absolute minimum and maximum of all sets or shown sets, for the
     actual step or for all steps.

   * Define limits: when choosing this option the `Contour Limits'
     window appears (this option is also avalaible in the postprocess
     toolbar). With this window the user can set the minimum/maximum
     value that Contour Fill should use. Outliers will be drawn with
     the color defined in the `Out Min Color/Out Max Color' option.

   * Reset Limit Values: this option resets the values defined in the
     `Define limits' option.

   * Reset All: this option sets all Contour Fill options by default.

   * Max/Min Options: Inside this group, several options for the
     minimum or maximum value can be defined:

        - *ResetValue:* here the user can reset the maximum/minimum
          value, so that the default value is used.

        - *OutMaxColor / OutMinColor:* with this option the user can
          specify how the outliers values should be drawn: `Black',
          `Max/Min Color', `Transparent' or `Material'.

        - *Def. MaxColor / Def. MinColor:* this option lets the user
          define the color for the minimum or maximum value for the
          color scale to start with.


   * Color scale: Specifies the propertyes of the color scale:

        - *Standard:* the color scale will be the default: starting
          from blue (minimum) through green until red (maximum).

        - *Inverse Standard:* the color scale will just be the inverse
          of the default: starting from red (minimum) through green
          until blue (maximum).

        - *Terrain Map:* a physical-map like color ramp will be used.

        - *Black White:* Black for Minimum and White for Maximum, the
          scale will be a grey ramp.

        - *Scale Ramp:* this option lets the user specify how should
          the ramp change from minimum color to the maximum color:
          `Tangent', `ArcTangent' or `Linear'. The default is
          `ArcTangent'.

        - *Scale Type:* tells GiD how the colors between the minimum
          color and the maximum color should change: `RGB' or `HSV'.

   * *Color window:* a window is poped up to let the user configure the
     colour scale of the contours easily


File: gid.info,  Node: Contour Ranges,  Next: Contour Lines,  Prev: Contour Fill,  Up: postprocessing results

Contour Ranges
==============

   This is the same as the `Contour Fill' visualization type, but the
coloured areas are created following a `'Result range table'' specified
in the results file, *note Result Range Table::., and the name of these
areas are also visualized as text labels.


File: gid.info,  Node: Contour Lines,  Next: Show Minimum and Maximum,  Prev: Contour Ranges,  Up: postprocessing results

Contour Lines
=============

   This display option is quite similar to contour fill (*note Contour
Fill::.), but here, the isolines of a certain nodal variable are drawn.
In this case, each color ties several points with the same value of the
variable chosen.

   Here the configurations options are almost the same than the ones
for Contour Fill (*note Contour Fill::.), with the only difference that
the number given in the `Number of Colors' option will be used as the
number of lines for this contour lines representation.


File: gid.info,  Node: Show Minimum and Maximum,  Next: Display vectors,  Prev: Contour Lines,  Up: postprocessing results

Show Minimum and Maximum
========================

   With this option the user can see the minimum and maximum of the
chosen result.

   *Note:* This minimum and maximum can be absolute, for all the
meshes/sets/cuts, or relative (local) to the shown ones. This can be
enabled or disabled through the `Right Button' menu `Results
ContOptions WhichContLimits'.


File: gid.info,  Node: Display vectors,  Next: Iso Surface,  Prev: Show Minimum and Maximum,  Up: postprocessing results

Display vectors
===============

   This option displays a menu with results from vectors and matrices
(where the principal values are previously evaluated by the program). A
menu of variables to be represented will be shown, from which the one
to be seen should be chosen, using the default analysis and step
selected. Once a vector is chosen, the program will display the nodal
vectors of the chosen result. The drawn vectors can be scaled
interactively. The factor can be applied several times and every time it
changes to the new input value.

   The user can modify the colour of the vectors, which, by default,
are drawn in green, so that all the vector are drawn with the same
colour, or let the vectors colour vary according to the result module.

   When drawing a matrix result, such as the stress tensor, only a
single color representation of principal values is available: blue when
negatives (also drawn as >-< representing compressions), and red when
positives (also drawn as <-> representing tensions).

   Several configuration options can be accessed via the Options menu.

   Color Mode: This option lets the user choose if vectors are drawn in
one color `(Mono Color)' or in several colors `(Colour Modules)'.

   Number of Colors: If the user uses `Colour Modules' to draw vectors,
it is possible to choose the number of colors.

   Offset: With this option, the user controls where the vector should
be in relation of the node, ranging from 0, to tie the tail of the
arrow to the node, to 1, to tie the tip of the arrow to the node.

   *Note:* These options have no effect when viewing a matrix result.

   Detail: The level of detail can be adjusted to draw the vectors
quicker or nicer.  The different options are:
   - Point: the arrow head will be drawn as a point. The style used to
     draw these point like arrow heads can be modified through the
     point options window described before, *note Point and Line
     options::..

   - Lines: the arrow head will be drawn as four lines.

   - 2 Triangles: the arrow head will be drawn with 2 self intersecting
     triangles.

   - 4 Triangles: the arrow head will be drawn as cones of 4 triangles.

   - 8 Triangles: the arrow head will be drawn as cones of 8 triangles.

   *Note:* This last option affects also matrix and local axes results.


File: gid.info,  Node: Iso Surface,  Next: Stream Lines,  Prev: Display vectors,  Up: postprocessing results

Iso Surfaces
============

   Here a surface is drawn that ties a fixed value inside a volume mesh.
A line is drawn for surface meshes.  To create iso-surfaces there are
several options:
   * Exact: After choosing a result, or a result component, of the
     current analysis and step, the user can input several fixed values
     and then for each given value a iso-surface is drawn.

   * Automatic: Similarly, after choosing a result, or a result
     component, the user is asked for the number of iso-surfaces to be
     created. GiD calculates the values between the Minimum and the
     Maximum (these not included).

   * Automatic Width: After choosing a result, or result component, the
     user is asked for a width. This width is used to create as many
     iso-surfaces as needed between the Minimum and the Maximum (these
     included) values defined.

   Several configuration options can be accessed via the Options menu.

   * Display Style: For Iso-Surfaces there is also a `Display Style'
     option, like for Volumes/Surfaces/Cuts. The options `All Lines',
     `Hidden Lines', `Body', `Body Lines' are avalaible. (*note Display
     Style::.)

   * Render: The `render' option for Iso-Surfaces renders that surfaces
     `Flat' or `Normal'. (*note Display Style::.)

   * Transparency: The Iso-Surfaces can be set to `Transparent' or
     `Opaque'. (*note Display Style::.)

   * Convert to cuts: Another interesting option is `Convert To Cuts'.
     With this options all the Iso-Surfaces drawn will be turn into
     cuts, so that they can be saved, read, and used to drawn results
     over them.


File: gid.info,  Node: Stream Lines,  Next: Line Diagrams,  Prev: Iso Surface,  Up: postprocessing results

Stream Lines
============

   With this option the user can display a stream line, or, in fluid
dynamics, a particle tracing, in a vector field.  After choosing a
vector result, using the default analysis and step selected, the
program asks the user for a point to start with the plotting of the
stream line. This point can be given in several ways:
   - just clicking on the screen: the point will be the intersection
     between the line orthogonal to the screen and the plane parallel
     to the screen and containing the `Rotation center',

   - joining a node: the selected node will be used as a start point,

   - select nodes: here several nodes can be selected to start with,

   - along line: with this option the user can define a segment, along
     which several start points will be chosen. The number of points
     will also be asked for, including the ends of the segment. In case
     of just one point start, this  will be the center of the segment.

   - in a quad: the user can enter here four lines that define a
     quadrilateral area which will be used to create a N x M matrix of
     points. These points will be the start for the stream lines. When
     giving N x M, N lies on the first and third line, and M on the
     second and fourth.  So, points ( 0, 0..N), ( M, 0..N), ( 0..M, 0)
     and ( 0..M, N) will lie just on the lines. But in case of N=1 or
     M=1, this will be the center of the line, and if N = 1 and M = 1,
     this will be the center of the Quad.

   - intersectset  the point will be the intersection between the line
     orthogonal to the screen and the current viewed sets nearest the
     view point.

   When viewing `Stream Lines', labels can be drawn to show the times
at start and end points of the stream line.

   Stream lines can also be deleted, and its, by default, green colour
can be changed too.

   Two options can be chosen for `Stream Lines':

   Delete: this option lets the user select stream lines to be deleted.

   Label: this option lets the user select the kind of label:
   - `None': no labels are drawn.

   - `0_End': labels are drawn with the following convention: 0 at the
     start of the stream line and the total time taken for the particle
     to travel at the end.

   - `Ini_End': labels are drawn with the following convention: 0 at
     the chosen point, and `- time before' at the begin of the stream
     line and `time after' at the end.



File: gid.info,  Node: Line Diagrams,  Next: Legends,  Prev: Stream Lines,  Up: postprocessing results

Line diagrams
=============

   This result visualization option is only active when line elements
are used in the mesh, and only will be represented over these line
elements.  When using this result visualization option, graph-style
lines will be drawn over the line elements.

   When drawing a Scalar Diagrams the graph-style lines are drawn on a
plane paralel to the screen ( with its normal vector pointing to the
user) when this result view is selected.  The positive 'axis' will be
the vector resulting of the cross product between this normal vector
and the one that the line defines.

   When drawing a Vector Diagrams the graph-style lines are drawn on a
plane that withholds the result vector and the one that the line
defines.  The graph-style line represent the module of this vector.
The positive 'axis' is also defined by the result vector.  As modules
are positive, to allow negative values, the input format for vector
results allows the introduction of a fourth component: the signed
vector module (*note File ProjectName.flavia.res::.).

   There is a `Show Elevations' option only accesible through the
`Right buttons' menu under 'Results / LineDiagram / Options'.
Elevations are lines that connect the nodes and the gauss points of the
line element and the graph style line that represents the result.  The
options are:

   * None: to switch the elevations off,

   * Nodes only: to draw the elevation lines only on the nodes,

   * Whole line: to draw the elevation lines along the whole line,
     using nodes and gauss points,

   * Filled line: to draw orange filled elevations,

   * Contour filled line: the colours used for the filled elevations
     will be the same as of a contour fill done along the line.


File: gid.info,  Node: Legends,  Next: Graphs,  Prev: Line Diagrams,  Up: postprocessing results

Legends
=======

   Legends appear when Contours visualization, iso-surfaces or color
vector visualization are used:

   - Show: legends can be switched on and of.

   - Opaque: legends can be transparent, showing the result
     visualization behind them, or not.

   - Show title: with this option the result name of the current
     visualization appears on the top of the legend.

   - Outside: activating this option, the legend is shown on a separate
     window, thus freeing precious graphical surface on GiD's windows.

   - Automatic comments: if this option is activated, information about
     the type of analysis, the actual step and the kind of result, is
     added at the bottom of the screen.



File: gid.info,  Node: Graphs,  Next: Deform Mesh,  Prev: Legends,  Up: postprocessing results

Graphs
======

* Menu:

* Graph Lines Description::
* Graph Lines Options::
* Graph Lines File Format::


File: gid.info,  Node: Graph Lines Description,  Next: Graph Lines Options,  Prev: Graphs,  Up: Graphs

Graph Lines description
-----------------------

   Here the user can draw graphs in order to have a closer look to the
results.  Several graphs types are available: point analysis against
time, result 1 vs.  result 2 over points and result along a boundary
line.  The user can also save or read a Graph (*note files -
postprocess::.). The format of the file will be described later. (*note
Graph Lines File Format::.)

   Under the Graphs option of the View Results menu there are the
following options:
   * `Show': here the user can switch between the graphs view and the
     post-processing view.

   * `ClearGraphs': to reset all the graphs and do a new start.

   * `Point Analysis': this graph shows the evolution of a result on a
     point along all the steps in the current analysis.

   * `Point Graph': after choosing a point or points, the user can
     contrast a result against another.

   * `Border Graph': after selecting a border, the user can see how the
     results varies along this boundary. You can also use the `Border
     Graph' window (`Windows' menu) to configure this type of graphs.

   The user can also view the labels of the points of the graphs, not
only the Graph points number, but also theirs X and Y values. If some
points of the Graphs are labeled, when turning into the normal results
view, the labels also appear on the results view.


File: gid.info,  Node: Graph Lines Options,  Next: Graph Lines File Format,  Prev: Graph Lines Description,  Up: Graphs

Graph Lines options
-------------------

   * `Grids': here the user tells whether to drawn grids or not.

   * `Current Style': the user can choose how the new graphs should
     look like. The possible styles are `Dot', `Line' and `Dot-Line'.

   * `Change Style Graph': the user can change the style of the
     selected graph.

   * `Change Title Graph': the user can change the title of the
     selected graph.

   * `Title': the user can change the title, its position or reset its
     value.

   * `X_Axis': here the user can set min and max values and divisions
     for the X axis, reset them, and change its Label.

   * `Y_Axis': here the user can set min and max values and divisions
     for the Y axis, reset them, and change its Label.


File: gid.info,  Node: Graph Lines File Format,  Prev: Graph Lines Options,  Up: Graphs

Graph Lines File Format
-----------------------

   The Graph file that GiD uses is an standard ASCII file. Every line
of the file is a point of the Graph with X and Y 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 axis can
also be configured. If a comment line contains the Keyword '`Graf:''
the string between quotes that follows this keyword will be used as
title of the graf. The string  between quotes that follows the Keyword
'`X:'' will be used as label for the X axis. The same is also true for
the Y axis, but for the Keyword '`Y:''.

   Here an example:

             # Graf: "Nodes 26, 27, 28, ... 52 Graf."
             #
             # X: "Szz-Tensiones_Nods." Y: "Sxz-Tensiones_Nods."
             -3055.444 1672.365
             -2837.013 5892.115
             -2371.195 666.9543
             -2030.643 3390.457
             -1588.883 -4042.649
             -1011.5 1236.958
             # End


File: gid.info,  Node: Deform Mesh,  Next: Do Cuts,  Prev: Graphs,  Up: postprocessing results

Deform Mesh
===========

   Volumes, surfaces and cuts can be deformed according to a nodal
vector and a factor. When doing so all the results are drawn on the
deformed volumnes, surfaces and cuts. This is called in GiD `Main
Geometry'. Thus, when the `Main Geometry' is deformed, results are also
drawn deformed; and when `Main geometry' is in its original state,
results are also drawn in its original state.

   In GiD there is a `Deform Mesh' window to allow this.

   On the upper part of this window, the user can choose between the
`Original' state of the `Main Geometry' and the `Deformed' state, for
which a nodal vectorial result, and an anlysis and step, must be
selected and a factor entered.

   There is also a so-called `Reference Geometry' option. This allows
to visualize volumes, surfaces or cuts like `Main Geometry' but NO
results can be displayed over these volumes, surfaces or cuts.  It is
merely provided as a reference, to contrast several deformation or
changes of the original geometry. Remember that the current Mesh
`Display Style' will be used for the `Reference Geometry' and it can be
only changed when redoing it.

   On the lower part of the `Deform Mesh' window, this `Reference
Geometry' can be configured. The user can choose between:

   `Off', so this reference visualization is not displayed.

   ` Original', if `Main Geometry' is deformed and the user wants to
compare it with its original state without loosing a results
representation.

   `Deformation', where, after providing an analysis, step, result and
factor, the user can use it to contrast two deformation states, or a
deformed state and an original geometry.


File: gid.info,  Node: Do Cuts,  Next: Animation,  Prev: Deform Mesh,  Up: postprocessing results

Do Cuts
=======

   Here the user can cut and divide volumes, surfaces and cuts. A cut
of a volume mesh results into a cut plane. The cut is done for all the
meshes, despite that some of them are switched off.  When cutting
surfaces, a line set will be created. Here only those surfaces that are
switched on are cut.

   Another feature is that a cut can be deformed, if meshes are also
told to do so (*note Deform Mesh::.). A cut of a deformed mesh, when
changing to the original shape, will be deformed accordingly.

   When dividing volumes/surfaces only those elements of the
volumes/surfaces switched on that lie on one side of a specified plane
will be used to create another volume/surface.

   * Cut Plane: the user specifies a plane which cuts the
     volumes/surfaces. Several options can be used to enter this plane.
     With `Two Points' ( the default), the plane is defined by the
     corresponding line and the orthogonal direction to the screen.
     With `Three Points', the plane is defined by this three points.
     When choosing the points, the nodes of the mesh can also be used.
     All the volume meshes are cut, whether they are drawn or not.

   * Divide Volume Sets: the user specifies a plane which is used to
     divide the meshes. Several options can be used to enter this
     plane. With `Two Points' ( the default), the plane is defined by
     the corresponding line and the orthogonal direction to the screen.
     With `Three Points', the plane is defined by these three points.
     When choosing the points, the nodes of the mesh can also be used.
     After defining the plane, the user should choose which section of
     the mesh should be saved by select the side of the plane to use.
     Only those elements that lie entirely on this side are selected.
     Only those volume meshes that are shown are divided.

   * Divide Surface Sets: the user specifies a plane which is used to
     divide the sets. Several options can be used to enter this plane.
     With `Two Points' (the default), the plane is defined by the
     corresponding line and the orthogonal direction to the screen.
     With `Three Points', the plane is defined by these three points.
     When choosing the points, the nodes of the mesh can also be used.
     After defining the plane, the user should choose which section of
     the mesh should be saved by select the side of the plane to use.
     Only those elements that lie entirely on this side are selected.
     Only those surface meshes that are shown are divided.

     When doing a division, clicking with the right button mouse,
     inside the Contextual menu, there are several useful options:
        - exact: to do a exact division, i.e. elements are cut to
          create the division.

        - parallel planes: the remaining elements will be ones between
          two paralel planes, a `distance' can also be entered, after
          choosing this option from the same contextual menu

   * Divide lines: the user specifies a plane which is used to get the
     lines at one side of this plane

   * Succession: This option is an enhancement of `Cut Plane'. Here the
     user specifies an axis that will be used to create cut planes
     orthogonal to this axis. The number of planes is also asked for.

   * Cut Wire: Here the user can define a 'wire' tied to the edges of
     the elements of the volumes/surfaces. So when the volumes/surfaces
     are deformed, the wire is deformed too. And viceversa, if a wire
     is defined while the volumes/surfaces are deformed, when turning
     them into its original shape, the cut-wire is "undeformed" with
     them.

   * Convert cuts to surface sets: With this options cuts can be
     converted to surface sets so they can be saved, or cut again.

   Cuts can also be read and write from/to a file. The information
stored into the file from a 'Cut Plane' is the plane equation that
defines the plane ( Ax + By + Cz + D = 0), so it can be used with
several models.  The information stored into the file from a 'Cut Wire'
is the points list of the cut-wire, i.e. the interseccion between the
wire and the edges of the meshes/sets.  These files are standard ASCII
files. A line of a 'Cut Plane' archive contains the four coeficients of
the cut defining plane separated by spaces. A line of a 'Cut Wire'
archive contains the three coordinates of a point of the wire. Comment
lines are allowed and should begin with a '`#''.

   An example of a 'Cut Plane' archive were three planes are stored:

             # planes created of a 'cut succesion'
             -10.82439 0.5740206 0 51.62557
             -10.82439 0.5740206 0 12.45994
             -10.82439 0.5740206 0 -26.70569

   An example of a 'Cut Wire' archive:

             -2.444425 3.883427 2.487002
             2.130787 2.762815 3.885021
             0.8411534 4.458836 3.215301
             4.270067 3.795048 2.037187
             5.66561 3.414776 0.8219391
             2.945865 3.600701 3.29012
             0.4487007 3.764661 3.574121


File: gid.info,  Node: Animation,  Next: Automatic comments,  Prev: Do Cuts,  Up: postprocessing results

Animation
=========

   With this window a little bit of automatization has been done to
create animations inside GiD.  Nowadays, almost all the results
visualization are animated. Only stream-lines are not automatized along
all the steps of the current analysis.

   On the right of the `Step:' label, the step value is shown. On the
slide bar, the step number is shown.

   The four buttons under the slide bar are autoexplicative, they
should 'Rewind', 'Stop', 'Play' and 'Step' the animation. Also clicking
on the slide bar the animation can be stepped down or up. The green led
will change to red when an animation is beign stored on a file, after
pressing the 'Play' button. This led wil change back to green when the
animation is finished, or the 'Stop' button is pressed.

   Options are:

   * `Automatic Limits': here GiD searches for the minimum and maximum
     values of the results along all the steps of the analysis and uses
     them to draw the results view through all the steps.

   * `Endless': to do the animation forever.

   * `Delay': here the user can specify a delay time between steps in
     miliseconds.

   * `Save TIFF/GIFs on': with this option the user can save snapshots,
     in TIFF or GIF format, of each step, when the '`Play'' button is
     pushed. Here the filename given will be used as a prefix to create
     the TIFF/GIFs, for instance, if the user writes `MyAnimation',
     TIFF/GIF files will be created with names
     `MyAnimation-01.tif'/`MyAnimation-01.gif',
     `MyAnimation-02.tif'/`MyAnimation-02.gif', and so on.

   * `Save MPEG/AVI True Color/AVI 15bpp/GIF on': giving here a
     filename, a MPEG/AVI/GIF file will be created when 'Play' button
     is pushed.
     *Note*: To avoid problems when trying to view an MPEG format
     animation in Microsoft Windows, it is strongly recommended to use
     the Default menu to select a 'standard' size and press the Resize
     button. The graphical window will change to this 'standard' size.
     After finishing the animation, just selecting Default on the menu
     and pressing the Resize button, the previous size will be restored.

   * `Static analysis animation profile': if the project has only one
     step, it's possible to simulate an animation by generating
     intermediate steps. Use this option to automatically generate many
     frames, following a lineal, cosine, triangular or sinusoidal
     interpolation between the normal state and the deformed state.



File: gid.info,  Node: Automatic comments,  Next: Several results,  Prev: Animation,  Up: postprocessing results

Automatic comments
==================

   While displaying results, comments can be automatically generated by
switching on the `Automatic' checkbox in the Comments window, which
appears selecting `Utilities->Graphical->Comments'.

   If this option is selected and the comment lines are empty, the
program will create its own automatic comments, like these ones:


     Load Analysis, step 3
     Display Vectors of Desplacements, |Desplacements| factor 68095.4.
     Deformation ( x127.348): Desplacements of Load Analysis 2, step 8.

   in bold, the fields which will change when the visualization changes.

   The user can also create its own automatic comments, just filling
the comment lines.  To tell the program where the result name, analysis
name, etc., should be placed, following fields can be used:

   * %an: for analysis name of the current visualized result

   * %sv: for step value of the current visualized result

   * %vt: for result visualization type of the current visualized result

   * %vf: for vectors factor used in the current visualized result ( if
     any)

   * %rn: for result name of the current visualized result

   * %cn: for component name of the current visualized result

   * %da: for analysis name of the current deformation ( if any)

   * %ds: for step value of the current deformation ( if any)

   * %dr: for result name of the current deformation ( if any)

   * %df: for factor of the current deformation ( if any)

   GiD will substitute the fields by the values of the current
visualization.  Fields which can not be fulfilled will be empty.


File: gid.info,  Node: Several results,  Prev: Automatic comments,  Up: postprocessing results

several results
===============

   With the windows which appears under `Windows->Several Results' the
user can select whether to view the results one by one, as usual, or to
view some results visualization types at once, for instace a contour
fill of preassure and velocity vectors at once.  From this window the
user can also delete not desired results visualization.  After
selecting the desired behaviour, the user needs to press the `Apply'
button


File: gid.info,  Node: Customization,  Next: POSTPROCESS DATA FILES,  Prev: postprocessing results,  Up: Top

CUSTOMIZATION
*************

* Menu:

* Introduction - ProblemType::
* Configuration Files::
* Template File::
* Executing an external program::


File: gid.info,  Node: Introduction - ProblemType,  Next: Configuration Files,  Prev: Customization,  Up: Customization

Introduction
============

   When GiD is to be used for a particular type of analysis, it is
necessary to predefine all the information required from the user and
to define the way 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 call Problem Type to this this collection of files
used to configure GiD for a particular type of analysis.

   *Note:* You can also learn how to configure GiD for a particular
type of analysis, following the Problem Type Tutorial; this tutorial is
included with the GiD package you've bought. You can also download it
from the GiD web page. (http://gid.cimne.upc.es/support)

   Due to the vocation of GiD as  general purpose pre and post
processor, the configuration for the different analysis must be
performed according to the particular specifications of every solver.
This implies the necessity of creating specific data input files for
every solver. However, GiD allows to perform this configuration process
inside itself without any change in the solver and without having to
program any independent utility.

   To configure these files means to define the data that must be input
by the user, as well as the materials to be implemented and other
geometrical and time-dependent conditions. It is also possible to add
some symbols or drawings to represent the defined conditions. GiD gives
the oportunity of working whith units when defining the properties of
the mentioned data, but there must be a configuration file where it
could be found the definition of the units systems.It must be also
defined the way that all this data must be written inside a file that
will be the input file to be read by the corresponding solver.

   The creation of a Problem Type implies the creation of a directory
with the Problem's Type name and the extension `.gid'. This directory
can be located in the current working directory or in the main GiD
executable directory.  The first case, the creation inside the current
working directory, can be useful during the development of the project.
Once it is finished, it can be advisable to move the directory to the
one where GiD is stored; like this, your Problem Type will be added to
those included in the system and it will appear in the GiD menu (*note
Problem type::.). In both cases, the series of files must be inside the
problem type directory. The name for most of them will be composed by
the same problem type's name and an extension referring to their
function. Considering `problem_type_name' to be the name of the Problem
Type and `project_name' the name of the project, the diagram of the
file configuration is the following:


   * directory name: `problem_type_name.gid'


   * directory location: `c:\a\b\c\GiD_directory\problemtypes'

     NOTE: In versions previous to 6.0 the `problemtypes' directory
     does not exist, so your problem type must reside in the
     `GiD_directory'. In versions later to 6.0 it's recommended to put
     your problem type inside the `problemtypes' directory.


   * Configuration files
        - `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'

        - `problem_type_name.sim  Conditions symbols '

        - `                   ***.geo  Symbols geometrical definitions'

        - `                   ***.geo  Symbols geometrical definitions'
          ...


   * Template files
        - `problem_type_name.bas  Information for the data input file'

        - `                  ***.bas  Information for additional files'

        - `                  ***.bas  Information for additional files'
          ...



   * TCL extension files
        - `problem_type_name.tcl  Extensions to GiD written in the
          TCL-TK programming language'


   * Command execution files
        - `problem_type_name.bat  Operating system shell that executes
          the analysis process'

   Files `problem_type_name.sim', `***.geo' and `***.bas' are not
mandatory and can be added to facilitate the visualization (files
`problem_type_name.sim' and `***.geo') or to prepare the data input for
the restart in additional files (files `***.bas').


File: gid.info,  Node: Configuration Files,  Next: Template File,  Prev: Introduction - ProblemType,  Up: Customization

Configuration Files
===================

   These files generate the conditions and material properties, as well
as the proper general problem and intervals data to be transferred to
the mesh, giving at the same time the chance to define geometrical
drawings or symbols to represent some conditions on the screen.

* Menu:

* Conditions file::
* Materials file::
* Problem and intervals data file::
* Conditions symbols file ::
* Unit System file::
* Special fields::


File: gid.info,  Node: Conditions file,  Next: Materials file,  Prev: Configuration Files,  Up: Configuration Files

Conditions file (.cnd)
----------------------

   The file with extension's name `.cnd' contains 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 thermical analysis.

   An important characteristic of the `conditions' is that they must
define over what kind of entity are going to be applied, i.e., over
points, lines, surfaces, volumes or layers and over what kind of entity
will be transferred, i.e., over nodes, over face elements or over body
elements.

   * over nodes means that the condition will be transferred to the
     nodes contained in the geometrical entity where condition is
     assigned.

   * over face elements 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 affected face.

   * over body elements If this condition is applied to lines, it will
     be transferred to line elements. If it is assigned to surfaces, it
     will be transferred to surface elements. If in volumes, to volume
     elements.

   *Note:* For backwards compatibility, it is accepted the possibility
`over elements', that will transfer 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 group of fields
containing the name of the referred 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:

     NUMBER: condition_number CONDITION: condition_name
     CONDTYPE: 'over' ('points', 'lines', 'surfaces', 'volumes', 'layer')
     CONDMESHTYPE: 'over' ('nodes', 'face elems', 'body elements')
     QUESTION: field_name['#CB#'(...,optional_value_i,...)]
     VALUE: default_field_value
       ...
     QUESTION: field_name['#CB#'(...,optional_value_i,...)]
     VALUE: default_field_value
     END CONDITION
     NUMBER: condition_number CONDITION: condition_name
       ...
     END CONDITION

   Note: `#CB#' means Combo Box.

   Note that this file format does not permit to put blank lines between
the last line of a condition definition, `END CONDITION', and the first
one of the next condition definition.

Local Axes

     QUESTION: field_name['#LA#'('global', 'automatic', 'automatic alternative')]
     VALUE: default_field_value

   This type of field makes reference 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. If two values are given, the second one will reference a
system that will be automatically computed for every node and that will
depend on the geometric constraints, like tangencies, orthogonalities,
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.

   All the different user defined systems will be added automatically
to these default possibilities.

   To enter only a specific kind of local axes it's possible to use the
modifiers `#G#',`#A#',`#L#'.
   - `#G#': global axes

   - `#A#': automatic axes

   - `#L#': automatic alternative axes

   When using these modifiers the position of the values doesn't
indicate the kind of local axes.

   Example
     QUESTION: Local_Axes#LA#(Option automatic#A#,Option automatic_alt#L#)
     VALUE: -Automatic-

NOTE: All the fields must be fulfilled with words, considering as a
word a character string without any blank space amongst them. The
strings signaled between quotes are literal and the ones inside
brackets are optional. The interface is case-sensitive, so the
uppercase letters must be maintained. `Default_field_value' and
different `optional_value_i' can be alphanumeric, integers or reals. GiD
treats them as alphanumeric until the moment that are written to the
solver input files.

   NOTE: The numbers of the conditions must be consecutive, beginning
with number 1.  There is no need to point out the overall number of
conditions or the respective number of fields for each one. This last
one can be variable for each condition.

   One optional flag to add to a condition is:

     CANREPEAT: yes

   It is written after CONDMESHTYPE and means that user can assign one
condition several times to the same entity.

   Another type of field that can be included inside a condition is:

     QUESTION: Surface_number#FUNC#(NumEntity)
     VALUE: 0
   Where the key `#FUNC#', means that the value of this field will be
calculated just when the mesh is generated. It can be considered a
function that evaluates when meshing. In the example above, `NumEntity'
is one of the possible variables of the function. It will be
substituted by the label of the geometry entity from where the node or
element is generated.

     QUESTION: X_preass#FUNC#(Cond(3,REAL)*(x-Cond(1,REAL))/(Cond(2,REAL)-Cond(1,REAL)))
     VALUE: 0
   In this second example, `x' 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 `y' and
`z' give the y ans z-coordinate of this point.

   NOTE: There are other available options to expand the capabilities
of the conditions window. (*note Special fields::.)

* Menu:

* Example Conditions File creation ::


File: gid.info,  Node: Example Conditions File creation,  Prev: Conditions file,  Up: Conditions file

Example: Creating the conditions file
.....................................

   Next is an example of a condition file creation, 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.gid/' on this
     case.

  2. Then create and edit the file (`problem_type_name.cnd' on this
     example) inside the recently created directory (where all your
     problem type files are located).  As you can see, except for the
     extension, the name of the file and the directory are the same.

  3. Create the first condition, which starts with the line

          NUMBER: 1 CONDITION: Point-Constraints

     where the first number is used to index the condition. Each
     condition will be refered  with one unique number (two conditions
     can not share the same number). The second parameter is the name
     of the condition. Again, a unique condition name into this
     condition file is required.

  4. This first line is followed by the next pair:

          CONDTYPE: over points
          CONDMESHTYPE: over nodes

     which declare over what entity is going to be applied the
     condition. The first  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 to provide this second
     parameter, but if it is present, the treatment  and evaluation of
     the problem will be more acurate.  The available parameters for
     this statement are "over nodes" and "over elements".

  5. Then, you'll have to declare a set of questions and values applied
     to this condition.

          QUESTION: Local-Axes#LA#(-GLOBAL-)
          VALUE: -GLOBAL-
          QUESTION: X-Force
          VALUE: 0.0
          QUESTION: X-Constraint:#CB#(1,0)
          VALUE: 1
          QUESTION: X_axis:#CB#(DEFORMATION_XX,DEFORMATION_XY,DEFORMATION_XZ)
          VALUE: DEFORMATION_XX
          
          END CONDITION

     After the QUESTION: word you have the choice of put:
        * An alphanumeric field name followed by the #LA# statement,
          and then the single or double parameter.

        * An alphanumeric field name.

        * An alphanumeric field name followed by the #CB# statement,
          and then the optional values between parenthesis.

     The VALUE: word must be followed by one of the optional values, if
     you  have declared them in the previous QUESTION: line. If you
     don't follow this statement, the program may not work correctly.
     In the previous example, the `X-Force' QUESTION takes the value
     0.0. Also in the example, the `X-Constraint' QUESTION includes a
     combo box statement (`#CB#'), followed 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' choosen.  Beware 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 will be an error when reading the file. Take this precaution
     specially in  the Combo Box question parameters, to avoid
     inpredictable parameters.

  6. The management of the conditions defined in the `.cnd' file, is
     done in the Conditions window (found in the Data menu), in the
     preprocess of GiD.


