没有合适的资源?快使用搜索试试~ 我知道了~
首页ensight format.pdf
资源详情
资源评论
资源推荐

EnSight 7 User Manual 11-1
11 EnSight Data Formats
This section describes the format for all readable and writable files in EnSight
which you may need access to. The formats described are only for those files that
are specific to EnSight. We do not describe data formats not developed by CEI
(for example, data formats for various analysis codes). For information about
these formats, consult the applicable creator.
Note: If you are using this documentation to produce your own data translator, please
make sure that you follow the instructions exactly as specified. In many cases,
EnSight reads data in blocks to improve performance. If the format is not
followed, the calculations of how much to read for a block will be thrown off.
EnSight does little in the way of error checking data files when they are read. In
this respect, EnSight sacrifices robustness for performance.
Section 11.1, EnSight Gold Casefile Format describes in detail the EnSight
Gold case, geometry, and variable file formats.
Section 11.2, EnSight6 Casefile Format describes in detail the EnSight6 case,
geometry, and variable file formats.
Section 11.3, EnSight5 Format describes in detail the EnSight5 geometry and
variable file formats.
Section 11.4, FAST UNSTRUCTURED Results File Format describes the
“executive” .res file that can be used with FAST unstructured solution and
function files.
Section 11.5, FLUENT UNIVERSAL Results File Format describes the
“executive” .res file that can be used with FLUENT Universal files for transient
models.
Section 11.6, Movie.BYU Results File Format describes the “executive” .res file
that can be used with Movie.BYU files.
Section 11.7, PLOT3D Results File Format describes the “executive” .res file
that can be used with PLOT3D solution and function files.
Section 11.8, Server-of-Server Casefile Format describes the format of the
casefile used with the server-of-server capability of EnSight.
Section 11.9, Periodic Matchfile Format describes the format of the file which
can be used to explicitly specify which nodes match from one periodic instance to
the next.
Section 11.10, XY Plot Data Format describes the format of the file containing
XY plot data.
Section 11.11, EnSight Boundary File Format describes the format of the file
which can define unstructured boundaries of structured data.
Section 11.12, EnSight Particle Emitter File Format describes the format of the
optional file containing particle trace emitter time and location information.

11.1 EnSight Gold Casefile Format
11-2 EnSight 7 User Manual
11.1 EnSight Gold Casefile Format
Include in this section:
EnSight Gold General Description
EnSight Gold Geometry File Format
EnSight Gold Case File Format
EnSight Gold Wild Card Name Specification
EnSight Gold Variable File Format
EnSight Gold Per_Node Variable File Format
EnSight Gold Per_Element Variable File Format
EnSight Gold Undefined Variable Values Format
EnSight Gold Partial Variable Values Format
EnSight Gold Measured/Particle File Format
EnSight Gold Material Files Format
EnSight Gold General Description
EnSight Gold data consists of the following files:
• Case (required) (points to all other needed files including model
geometry, variables, and possibly measured geometry and variables)
EnSight makes no assumptions regarding the physical significance of the scalar,
vector, 2nd order symmetric tensor, and complex variables. These files can be
from any discipline. For example, the scalar file can include such things as
pressure, temperature, and stress. The vector file can be velocity, displacement, or
any other vector data, etc.
In addition, EnSight Gold format handles "undefined" as well as "partial" variable
values. (See appropriate subsections later in this chapter for details.)
All variable results for EnSight Gold format are contained in disk files—one
variable per file. Additionally, if there are multiple time steps, there must either be
a set of disk files for each time step (transient multiple-file format), or all time
steps of a particular variable or geometry in one disk file each (transient single-file
format).
Sources of EnSight Gold format data include the following:
• Data that can be translated to conform to the EnSight Gold data format
(including being written from EnSight itself using the Save Geometric
Entities option under File->Save)
• Data that originates from one of the translators supplied with the EnSight
application
The EnSight Gold format supports an unstructured defined element set as shown
in the figure on the following page. Unstructured data must be defined in this
element set. Elements that do not conform to this set must either be subdivided or

11.1 EnSight Gold General Description
EnSight 7 User Manual 11-3
discarded.
The EnSight Gold format also supports the same structured block data format as
EnSight6, which is very similar to the PLOT3D format. Note that for this format,
the standard order of nodes is such that I’s advance quickest, followed by J’s, and
then K’s.
A given EnSight Gold model may have either unstructured data, structured data,
or a mixture of both.
This format is somewhat similar to the EnSight6 format, but differs enough to
allow for more efficient reading of the data. It is intended for 3D, binary, big data
models.
Note: While an ASCII format is available, it is not intended for use with large
models and is in fact subject to limitations such as integer lengths of 10 digits.
Use the binary format if your model will exceed 10 digits for node or element
numbers or labels.
Starting with version 7, EnSight writes out all model and variable files in EnSight
Gold format. Thus, it can be read by all version 7 EnSight licenses (i.e. standard,
gold, and custom licenses).
ens_checker A program is supplied with EnSight which attempts to verify the integrity of the
format of EnSight 6 and EnSight Gold files. If you are producing EnSight
formatted data, this program can be very helpful, especially in your development
stage, in making sure that you are adhering to the published format. It makes no
attempt to verify the validity of floating point values, such as coordinates, variable
values, etc. This program takes a casefile as input. Thus, it will check the format
of the casefile, and all associated geometry and variable files referenced in the
casefile. See How To Use ens_checker.

11.1 EnSight Gold General Description
11-4 EnSight 7 User Manual
Supported EnSight Gold Elements
The elements that are supported by the EnSight Gold format are:
eight node hexahedron twenty node hexahedron
six node pentahedron
9
10
7
8
12123
1
2
3
12
3
4
56
1
2
3
4
12
3
45
6
7
8
12
3
4
5
6
1
2
3
4
5
6
9
10
7
8
1
2
3
4
56
11
12
13
14
15
16
17
18
19
20
two node bar three node bar
three node triangle six node triangle four node quadrangle eight node quadrangle
four node tetrahedron ten node tetrahedron
1
point
1
2
3
4
1
4
8
2
3
5
6
7
5 node pyramid 13 node pyramid
11
2
2
3
3
44
5
5
6
7
8
9
10
11
12
13
fifteen node pentahedron (wedge)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
(wedge)
Figure 11-1
Supported EnSight Gold Elements
1 .
.
.
n
2
n-sided polygon
convex n-faced polyhedron
(described by n, n-sided faces)

11.1 EnSight Gold Geometry File Format
EnSight 7 User Manual 11-5
EnSight Gold Geometry File Format
The EnSight Gold format is part based for both unstructured and structured data.
There is no global coordinate array that each part references, but instead - each
part contains its own local coordinate array. Thus, the node numbers in element
connectivities refer to the coordinate array index, not a node id or label. This is
different than the EnSight6 format!
The EnSight Gold format consists of keywords followed by information. The
following items are important when working with EnSight Gold geometry files:
1. Node ids are optional. In this format they are strictly labels and are not used in
the connectivity definition. The element connectivities are based on the local
implied node number of the coordinate array in each part, which is sequential
starting at one. If you let EnSight assign node IDs, this implied internal
numbering is used. If node IDs are set to off, they are numbered internally,
however, you will not be able to display or query on them. If you have node
IDs given in your data, you can have EnSight ignore them by specifying
“node id ignore.” Using this option may reduce some of the memory taken up
by the Client and Server, but display and query on the nodes will not be
available. Note, prior to EnSight 7.4, node ids could only be specified for
unstructured parts. This restriction has been removed and user specified node
ids are now possible for structured parts.
2. Element ids are optional. If you specify element IDs, or you let EnSight
assign them, you can show them on the screen. If they are set to off, you will
not be able to show or query on them. If you have element IDs given in your
data you can have EnSight ignore them by specifying “element id ignore.”
Using this option will reduce some of the memory taken up by the Client and
Server. This may or may not be a significant amount, and remember that
display and query on the elements will not be available. Note, prior to EnSight
7.4, element ids could only be specified for unstructured parts. This restriction
has been removed and user specified element ids are now possible for
structured parts.
3. Model extents can be defined in the file so EnSight will not have to determine
these while reading in data. If they are not included, EnSight will compute
them, but will not actually do so until a dataset query is performed the first
time.
4. The format of integers and real numbers must be followed (See the Geometry
Example below).
5. ASCII Integers are written out using the following integer format:
From C:
10d
format
From FORTRAN:
i10
format
Note: this size of integer format places a limitation on the number of nodes
and the node and element labels that can make up a model. Use the
binary format for large models!
ASCII Real numbers are written out using the following floating-point format:
From C:
12.5e
format
From FORTRAN:
e12.5
format
剩余157页未读,继续阅读






安全验证
文档复制为VIP权益,开通VIP直接复制

评论0