GiD - The personal pre and post processor

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Menu: Files->Export→ACIS...


GiD can export the geometry in ACIS ASCII format, version 4.0 (files with .sat extension).

Rhinoceros


Menu: Files->Export->Rhinoceros...
With this option it is possible to write Rhinoceros 5.0 CAD files. This files have the .3dm extension.


GiD mesh


Menu: Files->Export->GiD mesh...
With this option a file is written with all of the project's mesh or meshes inside. This file can be read with Import GiD Mesh (see GiD mesh).

Exodus II


GiD can export the mesh by groups in Exodus II HDF5 format (files with .e extension).


Nodes-Raster


Menu: Files->Export->Nodes->Raster...
With this option a file is written with a raster object created from the current mesh nodes.
The size of the cell must be asked to the user.
The file is saved with Arc/Info grid ASCII format.

Text data report


Menu: Files->Export->Text data report...
With this option a file is written containing all the information within the project. It is created in a way that is easily understood when read with an editor. This is useful for checking the information.
Note: This ASCII format is only used to check information. It cannot be read again by GiD. To write ASCII files that can be read again use the option SaveAsciiProj (see ASCII project ).

ON layers


Menu: Files->Export->ON layers...
With this option, only the geometrical entities with their layers set to ON will be saved in a new project (see Layers and groups (only Preprocessing)).
Note: Lower entities necessary to define the saved entities will be also saved in the new project (e.g. the two extreme points of a line are also saved if the line is saved).

Calculation file


Menu: Files->Export->Calculation file...
If GiD runs the solver module automatically, this command is not necessary. However, it is useful if the solver program has to be run outside GiD, or to check the data input prior to any calculations.
This command writes the data file needed by the solver module.
The format of this file must be defined in a Template File (see Template File from Customization Manual). GiD uses the template file of the current Problem Type to write the data file; so, to run this command, a problem type must be selected.
When testing a new problem type definition, GiD produces messages about errors within the configuration. When the error is corrected, the command can be used again without leaving the example and without having to reassign any conditions or meshing.


Using template .bas (only mesh)


Menu: Files->Export->Using template .bas (only mesh)
This command does the same thing as Export -> Calculation file (see Calculation file), but it uses a .bas file provided by the user, instead of using the template file of the current problem type. This means it is not necessary to select a problem type in order to run this command.
When choosing 'Others...' from the submenu, GiD asks for a .bas file (see Template File from Customization Manual) and, using that file, writes the data file needed by the solver module. There are some .bas codes available in the submenu which write output files in some formats (DXF, NASTRAN, STL, VRML). These example .bas files are located in the Templates directory of the main GiD directory. It is possible to add other .bas files to that directory so they appear in the submenu.




Export Postprocessing
Files Menu>Export>Postprocessing>Post information

  • ASCII files: saves meshes, sets and results to ASCII files using the new PostProcess format (see Postprocess results format: ProjectName.post.res and Postprocess mesh format: ProjectName.post.msh from Customization Manual). If multiple meshes are read with the 'Open multiple' option explained above, only two files will be saved, one for the meshes and another one for the results, where each post information file (or pair .msh + .res) will define a Group (see Re-meshing and adaptivity from Customization Manual).


  • Binary (whole model): Saves meshes, sets and results to one binary file. If multiple meshes are read with the 'Open multiple' option explained above, only one file will be written, where each previously read post information file (or pair .msh + .res) will define a Group (see Re-meshing and adaptivity from Customization Manual).


  • HDF5 GiD Post: Saves meshes, sets and results into one HDF5 file. If multiple meshes are read with the 'Open multiple' option explained above, only one file will be written, where each previously read post information file (or pair .msh + .res) will define a Group (see Re-meshing and adaptivity from Customization Manual).


  • Binary (only results): Saves results information only, so the transition between Pre- and Postprocess will be quicker.


  • ASCII boundaries: Saves the boundaries of the meshes and sets, with its nodal results, to ASCII files (one for mesh information ".msh", one for the results ".res"). The boundary of a hexahedron/tetrahedron mesh is a quadrilateral/triangle mesh. The boundary of a quadrilateral/triangle mesh is a line mesh. There is no boundary of a line/point mesh.


  • Stream lines: the created stream lines can be exported with this option as meshes of lines. Together with the mesh lines also some internal information is also incorporated, such as the seed point, so that it can be imported to the current model in another separated session witth the option Files --> import --> Stream lines Stream lines

Files Menu>Export>Postprocessing>Cut
Menu: Files->Export->Cut...
Saves cut planes, cut wires and iso-surface mesh cuts so that the same cuts can be used among several postprocess meshes. Cut spheres can also be saved.
The information stored to 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 in the file from a 'Cut Wire' is the points list of the cut-wire, i.e. the intersection 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 coefficients of the plane that defines the cut, 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' file where three planes were written:

  1. planes created from a 'cut succession'
    -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 '2D polygonal cut' file:
    -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
    Files Menu>Export>Postprocessing>Graph
    Menu: Files->Export->Graph...
    Saves graphs in ASCII (gnuplot) format. If the option All is chosen, you will be asked for a prefix. GiD will then create a file for each graph with the names prefix-1.cur , prefix-2.cur , prefix-3.cur and so on.
    Read the GiD customization manual to know the description of this graph format.
    Files Menu>Export>Postprocessing>Cover mesh
    Menu: Files->Export->Cover mesh...
    After visualizing the cover mesh of the points/nodes, this mesh can be saved for other uses.
    Files Menu>Export>Postprocessing>Visible surfaces to STL
    Menu: Files->Export->Visible surfaces to STL...
    Exports the displayed triangular and quadrilateral surfaces in ascii or binary STL format with this window:
    Only the displayed meshes are written in the STL file. If the displayed meshes are deformed, then the meshes in the STL file are also deformed.

    STL export windows with ascii or binary format.
    Files Menu>Export>Postprocessing>Vtk
    Menu: Files->Export->Vtk...
    With this option it is possible to write Vtk files, in xml format (with .vtu or .vtp extension), with ASCII, binary and compressed options
    This exporter is implemented as a Tcl plugin, based on the Vtk package library.
    Postprocess meshes and results are exported, of the current analysis and step, or all writting several files.
    Files Menu>Export>Postprocessing>KML
    Menu: Files->Export->KML...
    With this option it is possible to write Kml files of Google Earth, in xml format (with .kml or .mkz extension for compressed files)
    This exporter is implemented as a Tcl plugin.
    To properly georeference the mesh the current coordinates could be transformed to geographical coordinates declaring the current coordinate system (e.g. UTM zone and hemisphere)
    Postprocess meshes and results are exported in a vectorial way. It is possible also export coloured results as a collection of images.
    Files Menu>Export>Postprocessing>Visible surfaces to PLY
    Menu: Files->Export->Visible surfaces to PLY...
    Exports the displayed triangular and quadrilateral surfaces in ascii or binary PLY format with this window:
    Only the displayed meshes are written in the PLY file. If the displayed meshes are deformed, then the meshes in the STL file are also deformed.
    Also the nodal results for the current step of the analysis are exported as nodal attributes in the PLY file.

    PLY export window
  • No labels

COPYRIGHT © 2022 · GID · CIMNE