...
The IGES geometric entities generated are:
116 Point
110 Line
102 Composite curve
126 Rational B-spline curve
128 Rational B-spline surface
142 Curve on a parametric surface
144 Trimmed surface
and the topological entities are (B Rep style):
186 Manifold solid B-rep object
502 Vertex
504 Edge
508 Loop
510 Face
514 Shell
STEP
...
ACIS
...
Exodus II
...
Text data report
...
ON layers
...
Calculation file
...
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:
- 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