Graphic Display and Data Export Specifications

<< Click to Display Table of Contents >>

Navigation:  Problem Descriptor Reference > The Sections of a Descriptor > Monitors and Plots >

Graphic Display and Data Export Specifications

Previous pageReturn to chapter overviewNext page

The MONITORS or PLOTS sections can contain one or more display specifications of the following types:

 

CDF ( arg1 [,arg2,...] )        

Requests the export of the listed values in netCDF version 3 format.
The output will be two or three dimensional, following the current coordinate system or subsequent ON SURFACE modifiers.
The included domain can be zoomed.
If the FILE modifier does not follow, then the output will be written to a file "<problem>_<sequence>.cdf".
Staged, eigenvalue and time-dependent problems will stack subsequent outputs in the same file, consistent with netCDF conventions.
CDF uses a regular rectangular grid, so interface definition may be ragged.
Use ZOOM to show details.

 

CONTOUR ( arg )        

Requests a two dimensional contour map of the argument, with levels at uniform intervals of the argument.

 

CONTOUR ( arg1, arg2 )        

Requests a two dimensional contour map of both arg1 and arg2, each with levels at independent uniform intervals.
A level table is displayed for both arg1 and arg2.

 

ELEVATION ( arg1,   [arg2,...] ) path        

Requests a two dimensional display (some times called a line-out) which displays the value of its argument(s) vertically and the value of its path horizontally.
Each ELEVATION listed must have at least one argument and may have multiple arguments separated by commas.
path can be either a line segment specified using the forms FROM (X1,Y1) TO (X2,Y2) or ON name, where name is a literal string selecting a path named in the BOUNDARIES section.

 

GRID ( arg1, arg2 )        

Requests a two dimensional plot of the computation grid, with nodal coordinates defined by the two arguments.
Grids are especially useful for displaying material deformations.
In 3D problems, a two-argument GRID plot will show a cut-plane, and must be followed by an ON specification.
3D cut plane grid plots do not necessarily accurately represent the computational grid.        

 

GRID ( arg1, arg2, arg3 )        

Requests a three dimensional plot of the computation grid, with nodal coordinates defined by the three arguments.
Only the outer surface of the grid will be drawn.
This plot can be interactively rotated, as with SURFACE plots.

 

MODE_SUMMARY

In eigenvalue problems, this produces a SUMMARY page for each mode (comparable to the version 5 SUMMARY).
This has been replaced with MODE SUMMARY (no underscore).

 

SUMMARY        

This plot type defines a text page on which only REPORT items may appear.
A SUMMARY page can be EXPORTed to produce text reports of scalar values.        

 

SUMMARY ( 'string' )        

If a string argument is given with a SUMMARY command, it will appear as a page header on the summary page.

 

SURFACE ( arg )        

A quasi three dimensional surface which displays its argument vertically.
If no VIEWPOINT clause is used, the viewing azimuth defaults to 216 degrees, the distance to three times the size, and the viewing elevation to 30 degrees.    

 

TABLE ( arg1 [,arg2,...] )        

Requests the export of the listed values in tabular ASCII format.
The output will be two or three dimensional, following the current coordinate system or subsequent ON modifiers.
The included domain can be zoomed.
If the FILE modifier does not follow, then the output will be written to a file "<problem>_<sequence>.tbl".
Staged, eigenvalue and time-dependent problems will create separate files for each stage or mode, with additional sequencing numbers in the name.
TABLE output  uses a regular rectangular grid, so interface definition may be lost.
Use ZOOM to show details.

 

TECPLOT ( arg1 [,arg2,...] )        

Requests the export of the listed values to a file readable by the TecPlot visualization system.
The output will be two or three dimensional, following the current coordinate system.
The entire mesh is exported.
If the FILE modifier does not follow, then the output will be written to a file "<problem>_<sequence>.dat".
Staged, eigenvalue and time-dependent problems will stack subsequent outputs in the same file, consistent with TecPlot conventions.
TecPlot uses the actual triangular or tetrahedral computation mesh (subdivided to linear basis), so material interfaces are preserved.

 

TRANSFER ( arg1 [,arg2,...] )        

Requests the export of the listed values and finite element mesh data in a file readable by FlexPDE using the TRANSFER or TRANSFERMESH input command. This method of data transfer between FlexPDE problems retains the full accuracy of the computation, without the error introduced by the rectangular mesh of the TABLE function.  
The exported domain cannot be zoomed.
If the FILE modifier does not follow, then the output will be written to a file "<problem>_<sequence>.dat". This export format uses the actual computation mesh, so material interfaces are preserved.
The full computation mesh is exported.
When used in Staged, Time dependent or Eigenvalue problems, each output file will be identified by appending a sequence number to the file name.
Note: TRANSFER files do not record the state of HISTORY plots.  Problems restarted from a TRANSFER file will have fragmented HISTORY plots.

         

VECTOR ( vector )        

Requests a two dimensional display of directed arrows in which the direction and magnitude of the arrows is set by the vector argument.
The origin of each arrow is placed at its reference point.        

 

VECTOR ( arg1, arg2 )        

Requests a two dimensional display of directed arrows in which the horizontal and vertical components of the arrows are given by arg1 and arg2.
The origin of each arrow is placed at its reference point.

 

VTK ( arg1 [,arg2,...] )        

Requests the export of the listed values to a file in VTK (Visualization Tool Kit) format for display by visualization systems such as VisIt.
The output will be two or three dimensional, following the current coordinate system.
The entire mesh is exported.
If the FILE modifier does not follow, then the output will be written to a file "<problem>_<sequence>.vtk".
Staged, eigenvalue and time-dependent problems will produce a family of files distinguished by the sequence number.
VTK format uses the actual triangular or tetrahedral computation mesh, so material interfaces are preserved.
The VTK format supports quadratic finite element basis directly, but not cubic.  To export from cubic-basis computations, use VTKLIN.

 

VTKLIN ( arg1 [,arg2,...] )

Produces a VTK format file in which the native cells of the FlexPDE computation have been converted to a set of linear-basis finite element cells.
This command may be  used to export to VTK visualization tools from cubic-basis FlexPDE computations, or in cases where the visualization tool does not support quadratic basis.

 

-----------------------------------------------------------------------------

For all commands, the argument(s) can be any valid expression.