UserManual User Manual

2011-02-17

: Ensight Usermanual UserManual EnSight92_Docs

Open the PDF directly: View PDF .
Page Count: 854

Download
Open PDF In Browser	View PDF

EnSight User Manual
for Version 9.2
Table of Contents
1
2
3
4
5
6
7
8
9
10
11
12
13

Overview
Input
Parts
Variables
GUI Overview
Main Menu
Features
Modes
Transformation Control
Preference and Setup File Formats
EnSight Data Formats
Utility Programs
Parallel and Distributed Rendering
Index
How To Table of Contents

Computational Engineering International, Inc.
2166 N. Salem Street, Suite 101, Apex, NC 27523
USA • 919-363-0883 • 919-363-0833 FAX
http://www.ceintl.com or http://www.ensight.com

© Copyright 1994–2009, Computational Engineering International, Inc. All rights reserved.
Printed in the United States of America.
EN-UM Revision History
EN-UM:5.2-1
EN-UM:5.2.2-1
EN-UM:5.5-1
EN-UM:5.5.1-1
EN-UM:5.5.2-1
EN-UM:6.0-1
EN-UM:6.0-2
EN-UM:6.0-3
EN-UM:6.0-4
EN-UM:6.1-1
EN-UM:6.2-1
EN-UM:6.2.1-1
EN-UM:7.0-1
EN-UM:7.1-1
EN-UM:7.3-1
EN-UM:7.4-1
EN-UM:7.4-2
EN-UM:7.6-1
EN-UM:8.0-1
EN-UM:8.2-1
EN-UM: 9.0.-0
EN-UM: 9.1.-0
EN-UM: 9.2.-0

October 1994
January 1995
September 1995
December 1995
February 1996
June 1997
August 1997
October 1997
October 1997
March 1998
September 1998
November 1998
December 1999
April 2000
March 2001
March 2002
October 2002
May 2003
December 2004
August 2006
September 2008
December 2009
December 2010

This document has been reviewed and approved in accordance with Computational Engineering
International, Inc. Documentation Review and Approval Procedures.
This document should be used only for Version 9.2 and greater of the EnSight program.
Information in this document is subject to change without notice. This document contains proprietary
information of Computational Engineering International, Inc. The contents of this document may not
be disclosed to third parties, copied, or duplicated in any form, in whole or in part, unless permitted by
contract or by written permission of Computational Engineering International, Inc. Computational
Engineering International, Inc. does not warranty the content or accuracy of any foreign translations of
this document not made by itself. The Computational Engineering International, Inc. Software License
Agreement and Contract for Support and Maintenance Service supersede and take precedence over
any information in this document. EnSight® is a registered trademark of Computational Engineering
International, Inc. All registered trademarks used in this document remain the property of the owners.
CEI’s World Wide Web addresses:
http://www.ceintl.com
or
http://www.ensight.com
Restricted Rights Legend
Use, duplication, or disclosure of the technical data contained in this document by the Government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause
at DFARS 252.227-7013. Unpublished rights reserved under the Copyright Laws of the United States.
Contractor/Manufacturer is Computational Engineering International, Inc., 2166 N. Salem Street, Suite 101,

Apex, NC 27523 USA

Table of Contents

Table of Contents
1 Overview
2 Input
2.1 Reader Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Dataset Format Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Reading and Loading Data Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.2 Native EnSight Format Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
EnSight Case Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
EnSight5 Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

2.3 Other Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
ABAQUS_FIL Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
ABAQUS_ODB Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
AIRPAK/ICEPAK Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Medina BIF-BOF PERMAS Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
AcuSolve Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
ANSYS Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
AUTODYN Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34
AVUS Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
CAD Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
CFF Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
CFX4 Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
CFX5 Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
CGNS Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
CTH Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
ESTET Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
EXODUS II Gold Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
FAST UNSTRUCTURED Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
FIDAP NEUTRAL Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
FLOW3D-MULTIBLOCK Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59

EnSight 9 User Manual

Table of Contents

FLUENT Direct Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-63
FLUENT UNIVERSAL Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-68
Inventor Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-69
LS-DYNA Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-71
Movie.BYU Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-73
MPGS 4.1 Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-74
MSC.DYTRAN Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-75
MSC.MARC Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-76
MSC.NASTRAN Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-78
Nastran Input Deck Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-83
N3S Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-85
OpenFOAM Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-87
OVERFLOW Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-90
PLOT3D Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-94
RADIOSS Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-96
POLYFLOW Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-97
SDRC Ideas Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-99
SILO Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-102
STAR-CD and STAR-CCM+ Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-104
STL Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-107
Tecplot Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-110
Vectis Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-114
XDMF Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-116

2.4 Other External Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-118
External Translators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-118
Exported from Analysis Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-118

2.5 Command Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-119
Saving the Default Command File for EnSight Session . . . . . . . . . . . . . . . . . .2-123
Auto recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-124

2.6 Archive Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-125
Saving and Restoring a Full backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-125

2.7 Context Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-128

EnSight 9 User Manual

Table of Contents

Saving a Context File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-128
Restoring a Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-128

2.8 Session Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-130
Saving a Session File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-130
Restoring a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-131

2.9 Scenario Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-132
2.10 Saving Geometry and Results Within EnSight. . . . . . . . . . . . . . . 2-135
Saving Geometric Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-135
If Rigid Body Transformations in Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-137

2.11 Saving and Restoring View States. . . . . . . . . . . . . . . . . . . . . . . . 2-139
2.12 Saving and Printing Graphic Images . . . . . . . . . . . . . . . . . . . . . . 2-140
Troubleshooting Saving an Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-142

2.13 Saving and Restoring Animation Frames . . . . . . . . . . . . . . . . . . 2-143
2.14 Saving Query Text Information . . . . . . . . . . . . . . . . . . . . . . . . . . 2-144
From Query/Plot Save... Formatted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-144
From Query/Plot Show Text. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-144
From EnSight Message Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-145

2.15 Saving Your EnSight Environment. . . . . . . . . . . . . . . . . . . . . . . . 2-146

3 Parts
3.1 Part Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Part Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Part Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

3.2 Part Selection and Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
3.3 Part Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
3.4 Part Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
3.5 Part List Shortcuts (Right-click) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
3.6 Part Graphics Window Shortcuts (Right-click) . . . . . . . . . . . . . . . . . 3-36

EnSight 9 User Manual

vii

Table of Contents

3.7 Part Shortcuts (Click-and-Go) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37

5 GUI Overview
GUI Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-5

4 Variables
General Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

4.1 Variable Selection and Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5

4.2 Variable Summary & Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Palette Editor Items Available on Every Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8
Palette Editor Simple Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-9
Palette Editor Advanced Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-9
Palette Editor Markers Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-10
Palette Editor Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-10
Palette Editor Files Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-11

4.3 Variable Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

6 Main Menu
6.1 File Menu Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
6.2 Edit Menu Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
6.3 Query Menu Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
6.4 View Menu Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
6.5 Tools Menu Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
6.6 Window Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-48
6.7 Case Menu Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-49
6.8 Help Menu Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52

viii

EnSight 9 User Manual

Table of Contents

7 Features
7.1 Solution Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7.2 Flipbook Animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
7.3 Keyframe Animation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
7.4 Variable Calculator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
7.5 Query/Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
7.6 Interactive Probe Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
7.7 Contour Create/Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
7.8 Isosurface Create/Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43
7.9 Clip Create/Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47
7.10 Vector Arrow Create/Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-69
7.11 Particle Trace Create/Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-74
7.12 Subset Parts Create/Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-95
7.13 Profile Create/Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-97
7.14 Elevated/Offset Surface Create/Update. . . . . . . . . . . . . . . . . . . . 7-101
7.15 Vortex Core Create/Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-106
7.16 Shock Surface/Region Create/Update. . . . . . . . . . . . . . . . . . . . . 7-111
7.17 Separation/Attachment Lines Create/Update . . . . . . . . . . . . . . . 7-117
7.18 Boundary Layer Variables Create/Update . . . . . . . . . . . . . . . . . . 7-121
7.19 Material Parts Create/Update . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-126
7.20 Tensor Glyph Parts Create/Update . . . . . . . . . . . . . . . . . . . . . . . 7-130
7.21 Developed Surface Create/Update . . . . . . . . . . . . . . . . . . . . . . . 7-133
7.22 Point Parts Create/Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-137
7.23 Extrusion Parts Create/Update . . . . . . . . . . . . . . . . . . . . . . . . . . 7-139

EnSight 9 User Manual

Table of Contents

8 Modes
8.1 Part Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
8.2 Annot Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
8.3 Plot Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30
8.4 VPort Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41
8.5 Frame Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50
8.6 Quick Desktop Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-59

9 Transformation Control
General Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-1

9.1 Global Transform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
9.2 Frame Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
9.3 Frame Transform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
9.4 Tool Transform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
9.5 Center Of Transform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
9.6 Z-Clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
9.7 Look At/Look From. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
9.8 Copy/Paste Transformation State . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
9.9 Camera . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24

10 Preference and Setup File Formats
10.1 Window Position File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
10.2 Connection Information File Format. . . . . . . . . . . . . . . . . . . . . . . . 10-3
10.3 Palette File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Color Selector Palette File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5
Function Palette File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5

EnSight 9 User Manual

Table of Contents

Predefined Function Palette. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Default False Color Map File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7

10.4 Default Part Colors File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
10.5 Data Reader Preferences File Format . . . . . . . . . . . . . . . . . . . . . . 10-9
10.6 Data Format Extension Map File Format . . . . . . . . . . . . . . . . . . . 10-10
10.7 Parallel Rendering Configuration File . . . . . . . . . . . . . . . . . . . . . 10-12
10.8 Resource File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13

11 EnSight Data Formats
11.1 EnSight Gold Casefile Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
EnSight Gold General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
EnSight Gold Case File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
EnSight Gold Geometry File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19
EnSight Gold Variable File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-46
EnSight Gold Per_Node Variable File Format . . . . . . . . . . . . . . . . . . . . . . . . . 11-46
EnSight Gold Per_Element Variable File Format. . . . . . . . . . . . . . . . . . . . . . . 11-62
EnSight Gold Undefined Variable Values Format . . . . . . . . . . . . . . . . . . . . . . 11-76
EnSight Gold Partial Variable Values Format . . . . . . . . . . . . . . . . . . . . . . . . . 11-80
EnSight Gold Measured/Particle File Format . . . . . . . . . . . . . . . . . . . . . . . . . 11-85
EnSight Gold Material Files Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-86

11.2 EnSight6 Casefile Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-98
EnSight6 General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-98
EnSight6 Case File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-101
EnSight6 Geometry File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-109
EnSight6 Variable File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-114
EnSight6 Per_Node Variable File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-114
EnSight6 Per_Element Variable File Format . . . . . . . . . . . . . . . . . . . . . . . . . 11-117
EnSight6 Measured/Particle File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-121
Writing EnSight6 Binary Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-121

11.3 EnSight5 Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-126

EnSight 9 User Manual

Table of Contents

EnSight5 General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-126
EnSight5 Geometry File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-128
EnSight5 Result File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-132
EnSight5 Variable File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-134
EnSight5 Measured/Particle File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-135
Writing EnSight5 Binary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-138

11.4 FAST UNSTRUCTURED Results File Format. . . . . . . . . . . . . . 11-141
11.5 FLUENT UNIVERSAL Results File Format . . . . . . . . . . . . . . . . 11-145
11.6 Movie.BYU Results File Format . . . . . . . . . . . . . . . . . . . . . . . . . 11-147
11.7 PLOT3D Results File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-150
11.8 Server-of-Server Casefile Format . . . . . . . . . . . . . . . . . . . . . . . 11-155
11.9 Periodic Matchfile Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-162
11.10 XY Plot Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-165
11.11 EnSight Boundary File Format . . . . . . . . . . . . . . . . . . . . . . . . 11-167
11.12 EnSight Particle Emitter File Format . . . . . . . . . . . . . . . . . . . . 11-171
11.13 EnSight Rigid Body File Format . . . . . . . . . . . . . . . . . . . . . . . 11-173
11.14 Euler Parameter File Format. . . . . . . . . . . . . . . . . . . . . . . . . . 11-177
11.15 Vector Glyph File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-181
General Comments: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-181
File description: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-182
Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-184

11.16 Constant Variables File Format . . . . . . . . . . . . . . . . . . . . . . . 11-186
General Comments: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-186
Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-187

11.17 Point Part File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-188
11.18 Spline Control Point File Format . . . . . . . . . . . . . . . . . . . . . . . 11-189
11.19 EnSight Embedded Python (EEP) File Format . . . . . . . . . . . . 11-190
The “module” case (“__init__.py”): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-190

xii

EnSight 9 User Manual

Table of Contents

The “installer” case (“autoexec.py”): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-190
Usage notes: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-190

11.20 Camera Orientation File Format . . . . . . . . . . . . . . . . . . . . . . . 11-191
Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-191

12 Utility Programs
12.1 EnSight Case Gold Writer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

13 Parallel and Distributed Rendering
13.1 Shared-memory parallel rendering . . . . . . . . . . . . . . . . . . . . . . . . 13-2
13.2 Distributed Memory Parallel Rendering . . . . . . . . . . . . . . . . . . . . 13-18
13.3 EnSight Networking Considerations . . . . . . . . . . . . . . . . . . . . . . 13-27

EnSight 9 User Manual

xiii

Table of Contents

xiv

EnSight 9 User Manual

1 Overview

Overview
EnSight (for Engineering inSight) provides engineers and scientists with an easyto-use graphics postprocessing package. EnSight supplies powerful, easy-to-use
tools through a user-friendly interface.
The purpose of this chapter is to give you an overview of the EnSight system and
its documentation. Because of the power and flexibility of EnSight, the synergy
between features provides a great many visualization techniques.
The Overview topics discussed are:
Part Concepts
Data Types
Graphical Environment
Transformations
Frames
Coloration
Created Parts
Queries
Transient Data
Animation
Implementation
Documentation
Contacting CEI

Part Concepts

EnSight processing begins with your model. Usually the elements of your model
are grouped into parts. Within EnSight, nearly all information is associated with
parts, and nearly all actions are applied to parts. The current maximum number
of parts is 65000.

Geometry

A part consists of nodes and elements (elements are sets of nodes connected in a
particular geometric shape). Each node, which is shared by its adjoining elements,
is defined by its coordinate-location in the model frame of reference.

Variable Values

EnSight-compatible data files provide variable values either at each part’s nodes,
element centers, or both. When needed (or requested) EnSight will find any
variable’s value at any point on or within an element by utilizing the element’s
shape function. The current maximun number of variables is 10000.

EnSight 9 User Manual

1-1

1 Overview

Part Attributes

Within EnSight, you can specify additional information about each part. These
part attributes tell EnSight how to display each part and how the part responds to
EnSight controls and display options. Part attributes include:
Category

Includes attributes that control....

General Attributes

Visibility (including visibility per viewport)
Susceptibility to Auxiliary Clipping
Reference frame
Response to changes in time (frozen or active)
Fast display representation
Visual Symmetry options
Coloration (constant, by a palette associated with a variable, or a
2D texture)
Shaded Surface susceptibility
Surface shading (flat, Gouraud, smooth)
Hidden Line susceptibility
Fill density (for transparency)
Lighting (diffuse, shininess, and highlight intensity)

Node, Element, and Node visibility
Line Attributes
Node type (dot, cross, or sphere)
Node size (constant or variable)
Node detail (for spheres)
Element-line visibility
Element-line width
Element-line style (solid, dotted, or dot-dash)
Element representation on client (full, border,
3D border/2D full, 3D feature/2D full, 3D nonvisual/2D full,
bounding box, feature angle, or nonvisual)
Element-size shrink-factor
Polygon Reduction
Failed element variable and rules
Node and element label visibility
Displacement
Attributes

Displacement variable and scale factor

IJK axis display
attributes

IJK axis visibility and scale factor

Part Operations

Parts can be copied to show, for example, the same part colored by a different
variable. Model parts can be split along an arbitrary plane or any quadric surface,
and merged with other model parts. The geometry of parts can be simplified by
creating a new part by extracting a simpler representation of an existing part.

Part Representation

Parts can be represented with simpler geometry, both to enhance visualization
performance and for special effects. Representation modes include:
Full mode, which represents all the part’s elements in the graphics window.
Border mode, which represents 3D elements with their 2D external faces.
Feature angle mode, which represents with 1D elements the “significant”
edges of the part (you control what is “significant”)
Nonvisual, which does not represent any of the part’s elements in the
graphics window (but still loads in memory on the server).
Bounding box, which represents the box bounding the coordinate extremes.
(see Section 3.3, Part Editing, and Section 8.1, Part Mode)

1-2

EnSight 9 User Manual

1 Overview

Data Types

EnSight supports a number of common data formats as well as interfaces to
various simulation packages. If an interface is not available for your data,
EnSight includes a library of routines to create your own custom User-Defined
Reader. User-Defined Readers have the advantage of not requiring a separate data
translation step and thus reduce user effort and disk storage requirements. A
number of User-Defined Readers are provided with EnSight; complete
documentation and dummy routines may be found in the directory $CEI_HOME/
ensight92/src/readers.
There are four different means to get your data into EnSight.
Type 1 - Included Readers - Are accessed by choosing the desired format in the
Data Reader dialog. These include common data formats as well as a number of
readers for commercial software. These can be internal EnSight readers as well as
User-Defined Readers. If the included reader is a User-Defined Reader there may
be more info in a README file found in $CEI_HOME/ensight92/src/readers.
Type 2 - Not Included User-Defined readers - A number of User-Defined
Readers have been authored by EnSight users, but are not provided with EnSight.
See the Comments column below for more information. Also for more info see
our website, www.ensight.com and go to the Support page.
Type 3 - Stand - Alone Translators - May be written by the user to convert data
into EnSight format files. A complete description of EnSight formats may be
found in Chapter 11 of the EnSight Online User Manual. Several translators are
provided with EnSight. These are found in the directory $CEI_HOME/ensight92/
translators. Translators must first be compiled before they may be used. Some
require links to libraries provided by the vendor of the program in question. See
the README files found in each translator’s directory.
Type 4 - EnSight Format - A growing number of software suppliers support the
EnSight format directly, i.e. an option is provided in their products to output data
in the EnSight format.
The table that follows summarizes all of the data formats and software packages
for which an interface of Type 1-4 exists. As this information changes frequently,
please consult our website (www.ensight.com) or your EnSight support
representative should you have any questions. If your format or program is not
listed here, there is the possibility that an interface does indeed exist. Contact
EnSight support for assistance. Should you create a User-Defined Reader or
Stand-Alone Translator and wish to allow its distribution with EnSight, please
send an email to this effect to support@ensight.com.

Data Format / Program

Type

Comments

ABAQUS_FIL

ABAQUS_ODB

ACUSOLVE
ADAGIO
ADINA
ALEGRA
ANSYS

2
1
3
1
1

Direct reader for binary or ascii (.fil) files (ABAQUS STANDARD or
EXPLICIT)
Direct reader for binary .odb files (ABAQUS STANDARD or
EXPLICIT). Only available for platforms supported by ABAQUS
Contact vendor for information
Use Exodus II reader
Use I-DEAS neutral files and translators
Use Exodus II reader
Direct reader for binary .rst, .rth, .rmq, .rfl files. (Internal legacy reader =
Ansys; single part < 2Gb file reader = Ansys Results (v10); largefile
multipart reader = Ansys-Multi-Part)

EnSight 9 User Manual

1-3

1 Overview

Data Format / Program
AVUS
Case (EnSight6, EnSight Gold)
CAD
CFD++
CFD-ACE
CFD-FASTRAN
CFDESIGN
CFF

CFX4
CFX5
CFX-TASCflow

Comments

1, 4
1

Formerly COBALT. User reader - or - Exports EnSight Case Gold format
Native EnSight formats, EnSight6 Case and EnSight Gold Case. (Gold
reader handles SOS auto-distribute.)
Direct Reader for CAD formats as well as STL
Exports EnSight Case format
Contact vendor for DTF reader
Contact vendor for DTF reader
Uses Tecplot files and reader
User reader for Common File Format from BOEING (WIND/CFF code).
Source supplied with EnSight install, executable supplied on some
platforms.
User reader, and translator (useful if results contain massed particles)
Code exports EnSight Case format, and direct reader available for all
platforms except Macintosh
Converts TASCflow output to EnSight format (or use PLOT3D converter
from vendor)
User reader
See AVUS User reader - or - Exports EnSight Case Gold format
Exports EnSight Case Gold format
Exports EnSight Case Gold format
User reader. (Handles SOS internally)
Use Exodus II reader
Contact CEI for details
Original EnSight format (unstructured)
Direct reader
User reader. (Handles SOS internally)
Direct reader for NASA FAST unstructured format
Contact vendor for information
Use GMS reader
Contact vendor for information
Direct reader for FIDAP neutral (FDNEUT) files
User reader for Fieldview 2.5 unstructured data
Use PLOT3D or CGNS files/reader
Use PLOT3D or CGNS files/reader
Code exports EnSight format
User reader for FLOW-3D results (flsgrf) files
Converts Fluent particle file to EnSight format
User reader for .cas and .dat files - or - Fluent exports EnSight Casefile
format
Contact developer (Imperial College) for interface details
User reader imports ASCII .gpp files
Exports EnSight Case format
User reader for GMS groundwater modeling framework, contact CEI for
information
Exports EnSight Case format
Contact CEI for information
LLNL hierarchical triangulated surface format.
User reader for Inventor (.iv) files
Translator for I-DEAS FEA neutral file
Contact CEI
User reader for MODELS 3 framework, contact CEI for information
Conversion routines to export EnSight format, contact CEI for info
User reader for d3plot files
Use LS-DYNA reader
Contact CEI

1
4
2
2
1
1

1, 3
1, 4
3

CGNS
COBALT
CRAFT
CRUNCH
CTH
DMC
ECLIPSE
ENSIGHT (EnSight 5)
ESTET
EXODUS II
FAST UNSTRUCTURED
FEFLO
FEMWATER
FENSAP
FIDAP
FIELDVIEW
FINE/Aero
FINE/Turbo
FIRE
FLOW-3D
FLUENT (particle files)
FLUENT

1
1, 4
4
4
1
1
3
1
1
1
1
3
2
4
1
1
1
1
4
1
3
1, 4

FOAM
FPRP
GASP
GMS

2, 4
1
4
2

GUST
HDF5
HTS
INVENTOR
I-DEAS
IMEX
IO/API
KIVA
LS-DYNA
MADYMO
MAGMA
1-4

Type

4
2
1
1
3
2
2
2, 3,4
1
1
2

EnSight 9 User Manual

1 Overview

Type

Comments

MAYA ESC
MEDINA BIF/BOF
MODELS 3
MOVIE.BYU
MPGS 4.1
MSC.ADAMS
MSC.DYTRAN
MSC MARC
MSC.NASTRAN
MSC.NASTRAN INPUT
MSC.PATRAN

Data Format / Program

4
1
2
1
1
4
1
1
1
1
3

MUSES/Prism
NCC
N3S
NetCDF
NIFTI-1/Analyze
NSMB
NSU2D / NSU3D
OVERFLOW
PAM-FLOW
PHOENICS
PLOT3D
POLY-3D
POLYFLOW
POWERFLOW
PERMAS

2
2
1
1
1
2
4
1
2
1
1
3
4
3
1

PRESTO
PRONTO
PXI
RADIOSS
RADTHERM
RESCUE

1
1
1
1
2
2

Contact vendor for information
User reader for Medina bif/bof files using Konfig file
Use IO/API reader
Direct reader for MOVIE.BYU format files
Direct reader for MPGS, EnSight’s predecessor
Plug-in support
User reader for MSC/Dytran archive (.arc) or data (.dat) files
User reader for t16 and t19 files
User reader for binary OP2 files
User reader for NASTRAN geometry input (.nas, .dat, .bdf) files
Converts PATRAN neutral files to MOVIE.BYU format -or- export to
EnSight using PATRAN macro
User reader from Thermoanalytics
User reader interface to National Combustion Code, contact CEI for info
Direct reader for the EDF code N3S
User reader, contact CEI for information
Analyze format with NIFTI extensions. (http://nifti.nimh.nih.gov)
User reader developed by CERFACS and CSCS
Contact CEI for information
User reader (modified PLOT3D reader) for OVERFLOW files
User-defined reader from ESI for native PAM-FLOW files
Use PLOT3D file/reader, contact CEI for information
Direct reader for PLOT3D and FAST structured formats
Contact vendor for information
Outputs EnSight Case format
Contact CEI for information on interfaces available
User-defined BIF/BOF reader (see Medina BIF/BOF). Not available on
Mac
Use Exodus II reader
Use Exodus II reader
User reader for Parallel Exodus Interface format
User-defined reader
User reader from Thermoanalytics
User reader for Schlumberger reservoir modeling framework, contact CEI
for information
User reader
Exports EnSight Casefile format.
Reads various formats supported by SILO API. (Handles SOS
internally)
Code exports EnSight format
Code exports EnSight Casefile format (including particle data)
Use the CAD User reader for STL geometry files
Contact CEI
Contact CEI for information on interfaces available
User reader for TECPLOT 7 structured and unstructured formats
User reader for TECPLOT 360 ASCII
Code exports EnSight format
User reader, contact CEI for details
Contact vendor for details
From TetrUSS code. Contact CEI for information
User reader
Polygonal model file format.
User reader for XDMF format files

SCRYU
SC/TETRA
SILO
SPHINX
STAR-CD (Version 3.0.5 & up)
STL
SUPERFORGE
TAHOE
TECPLOT
TECPLOT ASCII
Telluride
UNCLE
UNIC-CFD
USM3D
VECTIS
Wavefront OBJ
XDMF 2.0

EnSight 9 User Manual

1
4
1, 3
4
4
1
4
1
1
4
2
3
4
1, 3
1
1

1-5

1 Overview

Geometry

EnSight reads unstructured and structured geometric data grouped by parts. Data
can be 0D, 1D, 2D or 3D.

Analysis Results

EnSight reads scalar, vector, complex scalar, complex vector, and tensor variable
values associated with each node and/or element of the geometry. The loading of
variable values is optional, and variables can be unloaded to free memory.

Measured Data

EnSight can read measured or computed particles (referred to as discrete particles
in EnSight). Particles can have the same variables as the model geometry, or their
own variables. Particles can be displayed as points, crosses, or spheres whose size
can vary according to a variable value. Sphere smoothness is also controllable.
Discrete particles can be time dependent with the geometry, or time dependent
with a steady geometry.
(See EnSight Gold Measured/Particle File Format, in Section 11.1)

Cases

EnSight provides the capability to read and manipulate up to 16 datasets or
models at a time. Each new “Case” is handled by its own Server process while the
Client appropriately deals with merged variables, solution times, etc. This option
allows both the recombination of models partitioned for parallel analysis and a
number of comparative operations.

Graphical Environment
Parts are visualized in a main Graphics Window. You can create additional
viewports and adjust their size to your needs. Each viewport has its own
transformations (global, local, look-at, look-from, and Z-clip locations). Part
visibility is also controllable in each viewport. The current maximum number of
viewports is 16.
A separate “Show Selected Part(s)” window helps in identifying parts.
Hidden Lines and
Shaded Surfaces

You can choose to shade surfaces and/or hide hidden lines for realistic views of
your model. Visible element edges can be overlaid on shaded solid images.

Clipping

In addition to user-control of the front and back visual clipping planes of your
workspace, you can visually cutaway parts or portions of parts along any plane
using Auxiliary Clipping. Individual parts can be made immune to the effect,
enabling you to look at parts inside of other parts.

Annotations

EnSight can display text-strings, lines, arrows, logos, entity labels, and color-map
legends. Text annotations (which may include variables) can be made to
automatically update for time-dependent data. The current maximum number of
characters in a given annotation string is 1024.

Image Output

Screen images can be saved from within EnSight. Conversion to popular formats
is under user control as the image is saved.

Perspective

You have your choice of a perspective view or an orthographic view. The latter is
useful for comparing the position of parts and positioning EnSight tools.

Background Color
or Image

You can specify a constant or blended color background for the main Graphics
Window and independently for any Viewports displayed in the Graphics Window.
You can also use an image as the background.

Transformations
The standard transformations of rotate, translate, and scale are available, as well
1-6

EnSight 9 User Manual

1 Overview

as positioning of the Look-At and Look-From points. An automatic zoom control
is available. The transformation-state (the specific view in the Graphics Window
and Viewports) can be saved for later recall and use. Transformations can be
performed with precision in a dialog, or interactively with the mouse. For the
latter case, you can choose to represent the parts with bounding-boxes (or by
points only or reduced elements) all the time or only while they are moving.
Transformations can individually be reset by type.
(see Chapter 9, Transformation Control)

Frames
Transformations actually apply to frames—the parts attached to the frames
transform right along with their frame. You can create new frames and transform
them like parts (in a dialog or with the mouse), and change to which frame a part
is attached. You control whether and how frames are displayed, enabling you to
use them as rulers. Frames can have rectangular, cylindrical, or spherical
coordinates.
Frames, and therefore all parts attached to them, can be “periodic”. Rotational or
translational periodicity (as well as mirror symmetry) attributes are under user
control allowing, for example, an entire pie to be built from one slice of the pie.
(see Section 8.5, Frame Mode and Section 9.3, Frame Transform)

Coloration
Parts can be constant colored, colored according to the value of a variable, or
colored by a texture. This feature works for both lines and surfaces. The
coloration of each part is an attribute of that part.
Variable Palettes

You control the value-color correspondence with a palette. A palette’s scale can
be linear, logarithmic, or exponential. Palettes can have a continuous range of
colors, or color bands. Off-the-scale parts or portions of parts can be made
invisible.
(see Section 4.2, Variable Summary & Palette)

Created Parts
In addition to the model parts defined in the dataset, you can (and usually will)
define additional created parts based on both the geometry and variable-values of
existing parent-parts. Model parts and most kinds of created parts can be used as
parent parts. Created parts have their own part attributes, including the creation
attributes that define them, but remain dependent upon their parent-parts. A
created part automatically regenerates if any of its parent-parts are changed in a
way that will affect its representation.
Clips

A clip is a plane, line, box, ijk surface, xyz plane, rtz surface, quadric surface
(cylinder, sphere, cone, etc.), or revolution surface passing through specified
parent-parts. A clip can either be limited to a specific area (finite), or clip
infinitely through the model. You control the location of the various clips with an
interactive Tool or appropriate parameter or coefficient input.
A clip line or plane will either be a true clip through the model, or can be made to
be a grid where the grid density is under your control.
Clip surfaces can be animated as well as manipulated interactively.
In most cases you will create a clip which is the intersection of the clip tool and
the parent parts. This clip can either be a true intersection or all elements that

EnSight 9 User Manual

1-7

1 Overview

cross the intersection surface (a “crinkly” surface). You can also choose to cut the
parent parts into half spaces.
(see Section 7.9, Clip Create/Update)
Contours

Contours are created by specifying which parts are to be contoured, and which
variable to use. The contour levels can be tied to those of the palette or can be
specified independently by the user.
(see Section 7.7, Contour Create/Update)

Developed Surfaces

Developed Surfaces can be created from cylindrical, spherical, conical, or
revolution clip surfaces. You control the seam location and projection method that
will flatten the surface.
(see Section 7.21, Developed Surface Create/Update)

Elevated Surfaces

Elevated Surfaces can be displayed using a scalar variable to elevate the displayed
surface of specified parts. The elevated surface can have side walls.
(see Section 7.14, Elevated/Offset Surface Create/Update)

Extrusions

Parts can be extruded to their next higher order. Namely a line can be extruded
into a plane, a 2D surface into a 3D volume, etc. The extrusion can be rotational
(such as would be desired for an axi-symmetric part) or translational.
(see Section 7.23, Extrusion Parts Create/Update)

Isosurfaces

Isosurfaces can be created using a scalar, vector component, vector magnitude, or
coordinate. Isosurfaces can be manipulated interactively or animated by
incrementing the isovalue.
(see Section 7.8, Isosurface Create/Update)

Particle Traces

Particle traces—both streamlines (steady state) and pathlines (transient)—trace
the path of either a massless or massed particle in a vector field. You control
which parts the particle trace will be computed through, the duration of the trace,
which vector variable to use during the integration, and the integration time-step
limits. Like other parts, the resulting particle trace part has nodes at which all of
the variables are known, and thus it can be colored by a different variable than the
one used to create it. Components of the vector field can be eliminated by the user
to force the trace to, for example, lie in a plane. The particle trace can either be
displayed as a line, a ribbon, or a square tube showing the rotational components
of the flow field. Streamlines can be computed upstream, downstream, or both.
Streamline and pathline particle traces originate from emitters, which you create.
An emitter can be a point, rake, net, or can be the nodes of a part. Each emitter has
a particle trace emit time specified which you set, and a re-emit time (if the data
case is transient) can also be specified. Point, rake, and net emitters can be
interactively positioned with the mouse. For streamlines, the particle trace
continues to update as the emitter tool is positioned interactively by the user.
Another form of trace that is available is entitled node tracking. This trace is
constructed by connecting the locations of nodes through time. It is useful for
changing geometry or transient displacement models (including measured
particles) which have node ids.
A further type of trace that is available is a min or max variable track. This trace
is constructed by connecting the min or max of a chosen variable (for the selected
parts) though time. Thus, on transient models, one can follow where the min or

1-8

EnSight 9 User Manual

1 Overview

max variable location occurs.
(see Section 7.11, Particle Trace Create/Update)
Profiles

Profile plots can be created by scalar, vector component, or vector magnitude. You
control the orientation of the resulting profile plot.
(see Section 7.13, Profile Create/Update)

Subsets

A subset Part can contain node and element ranges of any model Part.
(see Section 7.12, Subset Parts Create/Update)

Vector Arrows

Vector arrows show the direction and magnitude of a vector field. Vector arrows
originate from element vertices, element nodes (including mid-side nodes), or
from element centers. You specify which parts are to have arrows and which
vector variable to use for the arrows, as well as a scale factor. You can eliminate
components of the vector, and can also filter the arrows to eliminate high, low,
low/high, or banded vector arrow magnitudes. The vector arrows can be either
straight or curved, and can have arrow heads. The arrow heads are either
proportional to the arrow or can be of fixed size.
(see Section 7.10, Vector Arrow Create/Update)

Tensor Glyphs

Tensor glyphs show the direction of the principal eigenvectors. You specify which
eigenvectors you wish to view and how you wish to view compression and
tension.
(see Section 7.20, Tensor Glyph Parts Create/Update)

Vortex Cores

Vortex cores show the center of swirling flow in a flow field.
(see Section 7.15, Vortex Core Create/Update)

Shock Surfaces/
Regions

Shock surfaces or regions show the location and extent of shock waves in a
3Dflow field.
(see Section 7.16, Shock Surface/Region Create/Update)

Separation/
Attachment Lines

Separation and attachment lines show where flow abruptly leaves or returns to the
2D surface in 3D fields.
(see Section 7.17, Separation/Attachment Lines Create/Update)

Queries
In addition to visualizing information, you can make numerical queries.
You can query on information for a node, point, element, or a part.
You can query on information for a data set (such as size, no. of elements, etc.)
You can query scalar and vector information for a point or node over time.
You can query scalar and vector information along a line. The line can either be a
defined line in space, or a logical line composed of multiple 1D elements for a
part (for example query of a variable on a particle trace).
You can query to find the spatial or temporal mean as well as the min/max
information for a variable.
Where applicable, query information can be in the form of a Fast Fourier
Transform (FFT).
Plotting
EnSight 9 User Manual

The plotter plots Y vs. X curves. The user controls line style, axis control, line
1-9

1 Overview

thickness and color. All query operations that result in multiple value output in
EnSight can be sent to the plotter for display. The user can control which curves to
plot. Multiple curve plots are possible. All plotable query information can be
saved to a disk file for use with other plotting packages. The current maximum
number of plotters at one time is 25.
(see Section 7.5, Query/Plot and Section 7.6, Interactive Probe Query)
Variable Creation

New information can be computed resulting in a constant, a scalar, or a vector.
EnSight includes useful built-in functions for computing new variables:
Lambda2
Area
Boundary Layer Cf Edge
Boundary Layer Cf Wall Shear Stress
Boundary Layer Displ Thickness
Boundary Layer Momentum Thickness
Boundary Layer Y1 Plus off Wall
Boundary Layer Recovery Thickness
Boundary Layer Velocity at Edge
Coefficient
Complex Argument
Complex Imaginary
Complex Transient Response
Curl
Density, Normalized
Density, Normalized Stagnation
Distance Between Part Elements
Distance Between 2 Nodes
Element to Node
Energy, Kinetic
Enthalpy, Normalized
Enthalpy, Normalized Stagnation
Flow
Fluid Shear Stress
Force
Gradient
Gradient Tensor
Helicity Density
Helicity, Relative Filtered
Integral, Line
Integral, Volume
Line Vectors
Mach Number
Make Nodal Scalar
Mass Flux Average
Material Species
Max
Moment
Momentum

1-10

Q_criteria
udmf_sum
Boundary Layer Cf Wall
Boundary Layer Cf Wall Components
Boundary Layer Scalar
Boundary Layer Dist to Value fr Wall
Boundary Layer Thickness
Boundary Layer Velocity Mag Gradient
Boundary Layer Shape Parameter
Case Map
Complex from real and imaginary
Complex Conjugate
Complex Modulus
Complex Real
Density
Density, Stagnation
Density, Log of Normalized
Divergence
Element Size
Energy, Total
Enthalpy
Enthalpy, Stagnation
Entropy
Flow Rate
Fluid Shear Stress Max
Force1D
Gradient Approximation
Gradient Tensor Approximation
Helicity, Relative
Iblanking Values
Integral, Surface
Length
Make Element Scalar
Make Vector
Mass Particle Scalar
Material Species to Scalar
Min
Moment Vector
Node to Element

EnSight 9 User Manual

1 Overview

Normal
Normalize Vector
Offset Variable
Pressure Coefficient
Pressure, Normalized
Pressure, Pitot
Pressure, Stagnation
Pressure, Stagnation Coefficient
Radiograph Grid
Rectangular to Cylindrical Vector
Shock Plot3d
Speed
SoS Constant
Statistical Regression
Stream Function
Temperature
Temperature, Stagnation
Temperature, Log of Normalized
Tensor Component
Tensor Eigenvalue
Tensor Make
Tensor Tresca
Velocity
Vorticity

Normal Constraints
Offset Field
Pressure
Pressure, Dynamic
Pressure, Log of Normalized
Pressure, Pitot Ratio
Pressure, Normalized Stagnation
Pressure, Total
Radiograph Mesh
Server Number
Spatial Mean
Sonic Speed
Statistical Moment
Statistical Regression 1 or 2 values
Swirl
Temperature, Normalized
Temperature, Normalized Stagnation
Temporal Mean, Min, or Max
Tensor Determinate
Tensor Eigenvector
Tensor Make Asymmetric
Tensor Von Mises
Volume

A calculator and built-in math functions also are useful for creating variables. Any
created variable is available throughout EnSight, and is automatically recomputed
if the user changes the current time (in case of transient data).
(see Section 4.3, Variable Creation)
In addition to the built-in general functions and the calculator options, variables
can be derived from user written external functions called User Defined Math
Functions (UDMF). The UDMF’s appear in EnSight’s calculator in the general
function list and can be used just as any calculator function.
Another feature of EnSight facilitates the creation of boundary layer variables.
(see Section 7.18, Boundary Layer Variables Create/Update)

Transient Data
EnSight handles transient (time dependent) data, including changing connectivity
for the geometry. You can easily change between time steps via the user interface.
All parts that are created are updated to reflect the current display time (you can
override this feature for individual parts). You can change to a defined time step,
or change to a time between two defined steps (EnSight will linearly interpolate
between steps), though the “continuous” option is only available for cases without
changing connectivity.

Animation
You can animate your model in four ways: particle trace animation, flipbook
animation, solution time streaming, and keyframe animation.

EnSight 9 User Manual

1-11

1 Overview

Particle Trace
Animation

Particle trace animation sends “tracers” down already created particle traces. You
control the color, line type, speed and length of the animated traces.
If transient data is being animated at the same time, animated traces will
automatically synchronize to the transient data time, unless you specifically
indicate otherwise.

Flipbook Animation

A Flipbook animation reads in transient data step by step or moves a part spatially
through a series of increments and stores the animation in memory. Playback is
much faster as it is from memory rather than disk, but the trade-off is that
Flipbook Animation can fill up your client memory. Flipbook animation is
simpler to do than keyframe animation, while allowing four common types of
animation:
Sequential presentation of transient data
Mode shapes based on a nodal displacement variable
EnSight created parts with an animation delta that recreates the part at a new
location (i.e., moving isosurfaces and Clip surfaces).
Sequential displacement by linear interpolation from zero to maximum
vector value.
You can specify the display speed, and can step page-by-page through the
animation in either direction. You can load some, or all the desired data. If you
later load more data, you can choose to keep the already loaded data. With
transient data, you can create pages between defined time steps, with EnSight
linearly interpolating the data.
Flipbooks can be created in two formats: a) Object animation where new objects
are created for each time step. The user can then manipulate the model during
animation play back or b) Image animation where a bitmap of the Main View
image is created and stored off for each animation page. For large models, image
animation can sometimes take less memory - while trading off the capability to
manipulate the model during animation.
(see Section 7.2, Flipbook Animation)

Solution Time
Streaming

Solution time streaming accomplishes the same result as a flipbook animation of
transient data except the data is never loaded into memory: it is streamed directly
from disk. While you don’t see the animation speed of a flipbook, you only need
enough memory to load in one step at a time.

Keyframe
Animation

Keyframe animation performs linearly interpolated transformations between
specified key frames to create animation frames. Command language can be
executed at key frames to script your animation. Some minimal editing is possible
by deleting back to defined key frames. Animation key frames can be saved and
restored from disk. Animation can be done on transient data and can automatically
synchronize with simultaneous flipbook animation and particle trace animation.
“Fly-around”, “rotate-objects”, and “exploded-view” quick animations are
predefined for easy use.
Keyframe animation can be recorded to disk files using a format of your choice.
(see Section 7.3, Keyframe Animation)

1-12

EnSight 9 User Manual

1 Overview

Implementation
Interface

EnSight uses the OSF/Motif graphical user interface conventions for the Unix
version and Win32 conventions under the Windows 2000/XP operating system.
Many aspects of the interface can be customized.

Client-Server

EnSight is a distributed application—it runs as separate processes that
communicate with each other via a TCP/IP or similar connection. The Server
performs most CPU-intensive and data-handling functions, while the Client
performs the graphics-display and user-interface functions. The Client and Server
can run together on one host workstation in a “stand-alone” installation or on two
host systems with each hardware system performing the functions it does best.
When more than one case is loaded the Client communicates with multiple Server
processes.

Server-of-Servers

A special server-of-servers (SOS) can be used in place of a normal server if you
have partitioned data or utilize the auto-decompose feature. This SOS acts like a
normal server to the client, but starts and deals with multiple servers, each of
which handle their portion of the dataset. This provides significant parallel
advantage for large datasets.
(see Section 11.8, Server-of-Server Casefile Format)

Virtual Reality

EnSight is fully capable of running multi-pipe display, virtual reality and
distributed rendering modes.
(see Section 13, Parallel and Distributed Rendering)

Command
Language

Each action performed with the graphical user interface has a corresponding
EnSight command. A session file is always being saved to aid in recovery from a
mistake or a program crash. The user will be prompted upon restart, after a crash,
whether or not to use a recovery file to restore the session. The command
language is human-readable and can easily be modified. Command files can be
played all the way through, or you can choose to stop the file and step through it
line-by-line.

Python

For more powerful scripting, EnSight supports the Python programming
language. The EnSight Python implementation includes every EnSight command
as well as looping, conditionals, and a large library of standard utilities.

Context Files

You can define a “context” and apply it to similar datasets.

Graphics Hardware

Many graphics functions of EnSight are performed by your workstation’s graphics
hardware. EnSight uses the OpenGL graphic libraries and is available on a
multitude of hardware platforms.

Parallel
Computation

EnSight supports shared-memory parallel computation via POSIX threads.
Threads are used to accelerate the computation of streamlines, clips, isosurfaces,
and other compute-intensive operations. (See How To Setup for Parallel
Computation for details on using.)

Distributed Memory
Parallel
Computation

EnSight supports distributed memory parallel computations (clusters) via serverof-server operations. The data decomposition may either be done by you or can be
done “on the fly”.

Macros

You can define macros tied to mouse buttons or keyboard keys to automate
actions you frequently perform.

EnSight 9 User Manual

1-13

1 Overview

Saving and
Archiving

You can save the entire current status of EnSight for later use, and can save other
entities as well (including the geometry of created parts for use by your analysis
software).
(see Section 2.6, Archive Files)

Environment
Variables

You can control a number of aspects of EnSight (both client and server) with
environment variables. (See How To Use Environment Variables)

Documentation
The printed EnSight documentation consists of the Installation Guide.
The on-line EnSight documentation consists of the EnSight Getting Started
Manual, How To Manual, User Manual, Interface Manual, and a Command
Language Reference Manual. The online documentation is available via the Help
menu.
User Manual

The EnSight User Manual is organized as follows:
User Manual Table of Contents
Chapter 1 - Overview
Chapter 2 - Input/Output. This chapter describes the reading of model data
(with internal or user-defined readers), command files, archive files, context files,
scenario files, and various other input and output operations.
Chapter 3 - Parts. This chapter describes the various types of Parts, selection,
identification, and editing of Parts, and various Part operations,
Chapter 4 - Variables. This chapter describes the selection and activation of
variables, color palettes, and the creation of new variables.
Chapter 5 - GUI Overview. This chapter describes the EnSight Graphic User
Interface.
Chapter 6 - Main Menu. This chapter describes the features and functions
available through the buttons and pull-down menus of the Main Menu of the GUI.
Chapter 7 - Features. This chapter describes the features and functions available
through the Icon buttons of the Feature Icon Bar of the GUI.
Chapter 8 - Modes. This chapter describes the features and functions available
through the Icon Buttons of the Mode Icon Bar in the six different Modes.
Chapter 9 - Transformation Control. This chapter describes the Global
transformation of all Frames and Parts, the transformation of selected Frames and
Parts as well as selected Frames alone, the transformation of the various Tools,
and the adjustment of the Z-Clip planes and the Look At and Look From Points.
Chapter 10 - Preference File Formats. This chapter describes the format of
various preference files which the uses can affect.
Chapter 11 - EnSight Data Formats. This chapter describes in detail the format
of the various EnSight data formats.
Chapter 12 - Utility Programs. This chapter describes a number of unsupported
utility programs distributed with EnSight.
Chapter 13 - Parallel Rendering and Virtual Reality. This chapter describes
how to configure EnSight for various VR configurations and for parallel
rendering.

1-14

EnSight 9 User Manual

1 Overview

User Manual Index
Cross References in the User Manual will appear similar to:
(see Chapter __

(see Section __

Clicking on these Cross References will automatically take you to the referenced
Chapter or Section.
Command
Language Reference
Manual

This manual describes each command of EnSight’s command language.

How To...

The various How To documents available on-line provide step-by-step, click by
click instructions explaining how to perform tasks within EnSight such as creating
an isosurface or reading in data.

Interface...

This manual describes the various methods and API’s that exist for interfacing
with EnSight.

Ordering

To order printed copies of EnSight documentation, go to our website at
www.ensight.com and click on support and choose documentation and follow the
instructions.

Newsletter

CEI periodically publishes an electronic EnSight newsletter. If you would like to
subscribe to the newsletter, see our website:
www.ensight.com.

Contacting CEI
EnSight was created to make your work easier and more productive. If you have
any questions about or problems using EnSight, or have suggestions for
improvements, please contact CEI support:
Phone:

EnSight 9 User Manual

Fax:

(800) 551-4448 (USA)
(919) 363-0883 (Outside-USA)
(919) 363-0833

Email:

support@ensight.com

1-15

1 Overview

1-16

EnSight 9 User Manual

Input
This chapter provides information on data input and output for EnSight.
2.1 Reader Basics provides a detailed description of the basics for reading data.
This section is referenced by all formats, in that they all use some or all of these
basic procedures. The quick load, as well as the more flexible two step load
process is discussed for both unstructured and structured data formats.
2.2 Native EnSight Format Readers describes the specifics for reading the
EnSight formats.
2.3 Other Readers describes the specifics for reading many other formats into
Ensight. These can be internal or user-defined readers.
2.4 Other External Data Sources describes other ways in which model data can
be prepared to be read into EnSight.
2.5 Command Files provides a description of the files that can be saved for
operations such as automatic restarting, macro generation, archiving, hardcopy
output, etc.
2.6 Archive Files describes options for saving and restoring the entire current
state of the program.
2.7 Context Files describes the options for saving and restoring context files.
2.8 Session Files describes the options for saving and restoring session files.
2.9 Scenario Files describes the options for saving scenario files that can be
displayed in the EnLiten program.
2.10 Saving Geometry and Results Within EnSight describes how to save
model data, from any format which can be read into EnSight, as EnSight gold
casefile format.
2.11 Saving and Restoring View States describes options for saving and
restoring given view orientations.
2.12 Saving and Printing Graphic Images describes options for saving and
printing graphic images.
2.13 Saving and Restoring Animation Frames describes options for saving and
restoring flipbook and keyframe animation frames.
2.14 Saving Query Text Information describes options for saving query
information to a text file.
2.15 Saving Your EnSight Environment describes options for saving various
environment settings which affect EnSight.
Note: Formats for EnSight related files are described in chapters 10 and 11.
Formats for the various Analysis codes are not described herein.

EnSight 9 User Manual

2-1

2.1 Reader Basics

2.1 Reader Basics
Dataset Format Basics
Reading and Loading Data Basics

Dataset Format Basics
EnSight is designed to be an engineering postprocessor, and supports data formats
for popular engineering simulation codes and generally used data formats. Yet its
many features can be used in other areas as well. EnSight has been used to
visualize and animate results from simulations of diesel combustion,
cardiovascular flow, petroleum reservoir migration, pollution dispersion,
meteorological flow, as well as results from many other disciplines.
EnSight reads node and element definitions from the geometry file and groups
elements into an entity called a Part. A Part is simply a group of nodes and
elements (the Part can contain different element types) which all behave the same
way within EnSight and share common display attributes (such as color, line
width, etc.).
EnSight allows you to read multiple datasets and work with them individually in
the same active session. Each dataset comprises a new “Case” and is handled by
its own Server process and can be added by using EnSight’s main menu Case >
Add... option. Note: if the client and the server are each on different computers,
then the data directory path is that seen from the server. Each server process has
its own console window and the output from the data read is directed to this
console. On Windows it is sometimes helpful to enlarge the default buffer size on
the server window to accomodate the sometimes large amount of output. Rightclick on the top left of the server window (named at top
C:\WINDOWS\System32\cmd.exe) and choose Screen Buffer size to be Width of
120 and Height of 9999, and Window size of Width 120 and Height of 40. Then
when you save it, save it for all windows of this name and every time the server
window is opened it will have these defaults and to see all of the server console
output.

Reading and Loading Data Basics
Reading and then Loading Data into EnSight can be done from “Simple” or
“Advanced” interface.
Simple Interface

2-2

The simple interface allows you to select a dataset which is read by the EnSight
server and then have all parts loaded and displayed on the Client. This is quick but
it does not allow control of which parts to load, nor does it allow you to control
the visual representation. Also, the simple interface only works for files mapped
in the ensight_reader_extension.map file found in the $CEI_HOME/ensight92/

EnSight 9 User Manual

2.1 Reading and Loading Data Basics
site_preferences

and/or in the EnSight Defaults Directory which is located

Figure 2-1
File Open Dialog - Simple Interface

at %HOMEDRIVE%%HOMEPATH%\(username)\.ensight92 commonly located
at C:\Users\username\.ensight92 on Vista and Win7, C:\Documents and
Settings\yourusername\.ensight92 on older Windows, and ~/.ensight92 on Linux,
and in ~/Library/Application Support/EnSight92 on the Mac) directories.
Look in

This field specifies the directory (or folder) name that is used to list the files and
directories in the list below.

File type

Limits the directory content list to the file type chosen. The default is to show all files.

File/Directory
Manipulation
Buttons

Changes the Look in directory to the one previously displayed.
Changes the Look in directory to be one up from the current.
Creates a new directory/folder in the current directory. You can rename
the new directory/folder by right clicking on it in the file listing and
selecting Rename.
Show the content of the Look in directory in list view. In this view the
directory and file names are listed in alphabetical order. This is the
default.
Show the content of the Look in directory in detail view. This view will
show all directories and file names in alphabetical order and also show
size, type, date, and read/write attributes.

Content List

Shows the content of the Look in directory/folder. Single click to select a file. This will
insert the file name with full path as described in the Look in field in to the File field. If
you double click a file name, the file will be inserted into the File field and the Okay
button will execute. If you double click on a directory/folder name, you will change the
Look in filter.

File

Specifies the file name that will be read once the Okay button is selected. As some file
formats require more than one file (geometry and results potentially) any associated files
will also be read according to the ensight_reader_extension.map file.

EnSight 9 User Manual

2-3

2.1 Reading and Loading Data Basics
Okay

Click to read the file (and associated files) specified in the File field and close the dialog.

Cancel

Click to close the Open... dialog without reading any files.
(For a step-by-step tutorial please see How To Read Data).

2-4

EnSight 9 User Manual

2.1 Reading and Loading Data Basics
Advanced
Interface

The advanced interface allows you to select a dataset which is read by the EnSight
server and then select which parts out of the dataset you wish to load and display
on the Client. You can control the format option, extra user interface options that
may be defined for your data file format and time settings.

Figure 2-2
File Open Dialog - Advanced Interface - Data Tab

Look in

This field specifies the directory (or folder) name that is used to list the files and
directories in the list below.

File type

Limits the directory content list to the file type chosen. The default is to show all files.

File/Directory
Manipulation
Buttons

Content List

EnSight 9 User Manual

2.1 Reading and Loading Data Basics

button will execute. If you double click on a directory/folder name, you will change the
Look in filter.
Data Tab
Set

Format

Comments
Format Options
Tab

Contains settings for file format and file names.
The name for this field will depend on the file format. For example, for EnSight it is "Set
case" while for CTH it is "Set spcth*". This field describes the file name used to read the
dataset. Depending on the file format, there may be two (or possibly more) Set fields. The
use of the second (or third) set field depends on the file format and is described in the
Comments section of the dialog.
Specifies the Format of the dataset. This pulldown will vary depending upon what readers
are installed at your local site, and what readers are made visible in your preferences.
Note: you can start up ensight with the -readerdbg flag to view verbose information on the
readers as they are loaded into EnSight.
Helpful information that is reader-specific will appear here, such as what file types are
entered into what fields.
Contains format specific information.

Figure 2-3
File Open Dialog - Advanced Interface - Format options Tab

Binary files are

Set measured

Set boundary
Extra GUI

2-6

This is typically checked automatically by the reader, and thus usually there is no need to
use this toggle. If the file is binary, sets the byte order to:
Big-Endian - byte order used for HP, IBM, SGI, SUN, NEC, and IEEE Cray.
Little-Endian - byte order used for Intel and alpha based machines.
Native to Server Machine - sets the byte order to the same as the server machine.
Name of an EnSight 5 format measured results file (typically .mea file). Measured data is
read independently of the reader and is entered here for all readers except Case file format.
For Case file format, this field is not used and the measured data filename is entered into
the Case file. The measured data filename is always optional. Clicking the button inserts
the file name shown in Selection field and also inserts path information into Path field.
File names can alternatively be typed into the field.
Name of a boundary file. This field is used only for structured data in Case file, Plot3d, or
Special HDF5, or other user-defined formats with structured data.
The User-Defined Reader API includes routines to add Toggles, Text Fields, and
Pulldown Menus that can allow the user to modify the reader behavior. Only a subset of

EnSight 9 User Manual

2.1 Reading and Loading Data Basics

the readers make use of this feature.
Time Options
Tab

Contains Time specific information.

Figure 2-4
File Open Dialog - Advanced Interface - Time options Tab

Time Settings

SOS Options
Tab

EnSight 9 User Manual

Specify starting time step. If not specified, EnSight will load the last step (or whatever
step you have set in your preferences, see Edit>Preferences>Data). This section also
allows you to shift, scale and/or offset the original time values according to the values
entered into the equation.
If connected to an SOS server, this tab will be available and controls how the servers will

2-7

2.1 Reading and Loading Data Basics

behave when handling data as well as what resources will be used.

Figure 2-5
File Open Dialog - Advanced Interface - SOS options Tab

Set resources
Pass wild cards
to server
Auto distribute
Don’t
Server
Reader

Sets a filename to be used for SOS and Server resources.
This toggle will pass wildcard filenames on to the server as opposed to resolving them on
the SOS. The usefulness of this toggle is entirely dependent on the specific reader in use.
How to decompose and distribute the data to each of the servers.
Data is already stored on disk decomposed.
Use the server to automatically partition the data
Use the reader to automatically partition the data

Load All

Click to read and load all of the parts associated with the file names specified and close the
dialog.

Choose Parts

Click to read the data files specified, close the dialog and bring up the Data Part Loader.

Cancel

Click to close the Open... dialog without reading any files.
(For a step-by-step tutorial please see How To Read Data).

Data Part Loader

2-8

The Data Part Loader will allow you to select the parts to be loaded on the server,
as well as their new name (if desired) and representation. There are two basic part
loader windows. Details of these windows will be discussed below, and variants

EnSight 9 User Manual

2.1 Reading and Loading Data Basics

from these windows will be discussed under each specific reader format.

Unstructured Part Loader Dialog

Structured Part Loader Dialog

Figure 2-6
Typical File Data Part Loader dialogs

All Parts or some of those available on the Server may be loaded to the Client and
their visual representation can be chosen. The Data Part Loader may be reopened
at a later time and additional or duplicate parts loaded as desired.
Unstructured Data

This toggle indicates that the Part(s) listed in the Part List is(are) unstructured.

Structured Data

This toggle indicates that the Part(s) listed in the Part List is(are) structured.

Parts List

Lists all Parts in the data files which may be loaded to the Server (and subsequently to the
Client). Some formats such as EnSight6 or EnSight Gold data can have unstructured,
structured, or both types of Parts.

Element Visual
Rep.

Parts are defined on the server as a collection of 0, 1, 2, and 3D elements. EnSight can
show you all of the faces and edges of all of these elements, but this is usually a little
overwhelming, thus EnSight offers several different Visual Representations to simplify the
view in the graphics window. Note that the Visual Representation only applies to the

EnSight 9 User Manual

2-9

2.1 Reading and Loading Data Basics

EnSight client—it has no affect on the data for the EnSight server.

Figure 2-7
Element Visual Representation pulldown

3D Border, 2D
Full

In this mode, load the designated parts, show all 1D and 2D elements, but show only the
unique (non-shared) faces of 3D elements.

3D Feature, 2D
Full

In this mode, load the designated parts, but show the 3D elements in Feature Angle mode
(see Feature below), and show all of the 1D and 2D elements.

3D nonvisual,
2D full

In this mode load the 3D parts but do not display them in the graphics window (see Non
Visual below) and load all the 1D and 2D elements.

Border

In Border mode all 1D elements will be shown. Only the unique (non-shared) edges of 2D
elements and the unique (non-shared) faces of 3D elements will be shown.

Feature Angle

When EnSight is asked to display a Part in this mode it first calculates the 3D Border, 2D
Full representation to create a list of 1D and 2D elements. Next it looks at the angle
between neighboring 2D elements. If the angle is above the Angle value specified in the
Feature Angle Field, the shared edge between the two elements is retained, otherwise it is
removed. Only 1D elements remain on the EnSight client after this operation.

Bounding Box

All Part elements are replaced with a bounding box surrounding the Cartesian extent of
the elements of the Part.

Full

In Full Representation mode all 1D and 2D elements will be shown. In addition, all faces
of all 3D elements will be shown.

Non Visual

This specifies that the loaded Part will not be visible in the Graphics Window because it is
only loaded on the Server. Visibility can be turned on later by changing the representation
(at which time the elements of the selected representation will be sent to the client).

Load Points and
normals only

If toggled on, only the vertices of the element representation, with normals, will be loaded
to the client.

Group these parts

If more than one part is selected, they can be grouped into a single entity. The name of the
group will be according to the New Part Description filed and the individual parts will
receive the names shown in the part list.

New Part
Description

This allows the user to name the part. If nothing is entered here, then the part is named
from the partlist.

Load Selected

Loads Parts selected in the Parts List to the EnSight Server. The Parts are subsequently
loaded to the EnSight Client using the specified Visual Representation. If Non Visual is
specified, the selected Parts will be loaded to the Server, but not to the Client.

Load All

Loads all Parts in the Parts List to the EnSight Server. The Parts are subsequently loaded
to the EnSight Client using the specified Visual Representation. If Non Visual is specified,
the selected Parts will be loaded to the Server, but not to the Client.

2-10

EnSight 9 User Manual

2.1 Reading and Loading Data Basics
Structured Data
Domain

Specifies the general iblanking option to use when creating a structured Part. If the model
does not have iblanking, InSide will be specified by default.
Inside
Iblank value = 1 region
Outside
Iblank value = 0 region
All
Ignore iblanking and accept all nodes

Using Node Ranges:
From IJK

Specifies the beginning I,J,K values to use when extracting the structured Part, or a
portion of it. Must be >= Min value.

To IJK

Specifies the ending I,J,K values to use when extracting the structured Part, or a portion of
it. Must be <= Max value.
Valid values for the From and To fields can be positive or negative. Positive numbers are
the natural 1 through Max values. Negative values indicate surfaces back from the max, so
-1 would be the max surface, -2 the next to last surface etc. There are therefore two ways
to indicate any of the range values; the positive number from the min towards the max, or
the negative number from the max toward the min. The negative method is provided for
ease of use because of varying max values per part. (Zero will be treated like a -1, thus it is
another way to get the max surface)
1, 2, 3,... --->
<--- ...-3, -2 ,-1
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
min
max
(always 1)
(varies per zone)

Step IJK

Specifies the step increment through I,J,K. A Step value of 1 extracts all original data. A
Step value of 2 extracts every other node, etc. Thus step values greater than 1 give a
coarser resolution.

Delta IJK

Specifies the delta to use when creating more than one surface from the same ijk part.
Only one of the directions may be non-zero. Note that an unstructured part is the result of
any non-zero delta values.

Min IJK

Minimum I,J,K values for Part chosen (for reference).
Maximum I,J,K values for Part chosen (for reference).

Max IJK
Part Description

Text field into which you can enter a description for the Part. If left blank a default will be
used.

Create And Load
from selected

Extracts the data from the data files and creates a Part on the Server (and on the Client
unless NonVisual has been specified for Representation) based on all information
specified in the dialog.
If only one part is highlighted, the values shown in the From and To fields (as well as the
Min and Max fields) are the actual values for the selected part. Using the From and To
fields you can control whether an EnSight part will be created using the entire ijk ranges
or some subset of them. The Step field allows you to sample at a more coarse resolution.
And the Delta field allows for multiple “surfaces” in a given part (like blade rows of a jet
engine). Please note that use of a non-zero delta produces an unstructured part instead of a
structured one.
If more than one Part is highlighted, the values shown in the From and To fields are the
combined bounding maximums of the selected parts. The same basic functionality
described for a single part selection applies for multiple part selection, with one part being
created for each selected part in the dialog. If the specified ranges for the multiple

EnSight 9 User Manual

2-11

2.1 Reading and Loading Data Basics

selection exceed the bounds of a given part, they are modified for that part so that its
bounds are not exceeded.

Figure 2-8
Iblanked Part Creation Section of Structured Part Loader dialog

You use this portion of the Part Loader dialog to further extract iblanked regions from
structured parts which were created either as inside, outside, or all portions of the model.
Structured Part(s)
To Be Parent of
Iblanked Part

Lists all structured parts that have been created thus far in the dialog above.

Iblank Values For
Entire Mesh

Lists all possible iblank values found in the model. This is a global list and may not apply

Iblank Part
description

Text field into which you can enter a part name for the iblanked part.

Create And Load
Iblanked
Unstructured Part

Extracts a new iblanked part from an existing structured part. This new part will actually
be an unstructured part.

to all parts.

(For step-by-step instructions see How To Read Data)
Loading Tips

For large datasets, you should try to reduce the amount of information that is being
processed in order to minimize required memory. Here are some suggestions:
• When writing out data from your analysis software, consider what information will
actually be required for postprocessing. Any filtering operation you can do at this step
can greatly reduces the amount of time it takes to perform the postprocessing.
• For each Part you do load to the Client, a representation must be chosen. This visual
representation can be made very simple (through the use of the Bounding Box or
Feature Angle option, for example), or can be made more complex (by using the border
or full elements). The more you can reduce the visual representation, the faster the
graphics processing will occur on the Client (see Node, Element, and Line Attributes in
(see Section 3.3, Part Editing).
• Load to the Client only those Parts that you need to see. For example, if you were
postprocessing the air flow around an aircraft you would normally not need to see the
flow field itself and could load it non-visual, but you would like to see the aircraft
surface and Parts created based on the flow field (which remains available on the
Server).
• If you have multiple variables in your result file, activate only those variables you want
to work with. When you finish using a variable, consider deactivating it to free up
memory and thereby speed processing (see Section 4.1, Variable Selection and
Activation).

2-12

EnSight 9 User Manual

2.1 Reading and Loading Data Basics

Troubleshooting Loading Data
Problem

Probable Causes

Solutions

Data loads slowly

Loading more Parts than needed

For some models, especially
external fluid flow cases, there is a
flow field Part which does not need
to be visualized. Try loading this
Part non-visual.

Too many elements

Make sure the default element
representation for Model Parts is set
to 3D Border/2D Full before
loading the data. In some cases it is
helpful to set the representation to
Feature Angle or 3D Feature 2D
Full, before loading.

Client is swapping because it does
not have enough memory to hold all
the Parts specified.

Try loading fewer Parts or installing
more memory to handle the dataset
size.

Server is swapping because it does
not have enough memory to hold all
of the Parts contained in the dataset.

Install more memory in your Server
host system, reduce the number of
variables activated, or somehow
reduce the geometry’s size. (If you
can get the data in, you can cut
away any area not now needed.
What is left can then be saved as a
geometric entity and that new
dataset used for future
postprocessing.)

Incorrect path or filename

Reenter the correct information.
Remember, the Path is on the server.

Incorrect file permissions

Change the permissions of the
relevant directories and files to be
readable by you.

Temporary file space is full

Temporary files are written to the
default temporary directory or the
directory specified by the
environment variable TMPDIR for
both the Client and Server. Check
file space by using the command
“df” and remove unnecessary files
from the temporary directory or
other full file systems.

Format of the data is incorrect

Recheck the data against the data
format definition. (Can use
ens_checker for Ensight6 or
EnSight Gold format checking.)

Error reading data

EnSight 9 User Manual

2-13

2.1 Reading and Loading Data Basics

Problem

Probable Causes

Solutions

EnSight format scalar (or vector)
data loads, but appears incorrect.
Often range of values off by some
orders or magnitude.

Scalar (or vector) information not
formatted properly in data file

Format the file according to
examples listed under EnSight
Variable Files (see Chapter 11,
EnSight Data Formats) (Can use
ens_checker for Ensight6 or
EnSight Gold format checking.)

Extra white space appended to one
or more of the records

Check for and remove any extra
white space appended to each
record

2-14

EnSight 9 User Manual

2.2 Native EnSight Format Readers

2.2 Native EnSight Format Readers
EnSight’s native data format is useful as a general data format for finite elements
or structured data. EnSight has three native data formats (from oldest to newest,
EnSight5, EnSight6 and EnSight Case Gold) which are well defined and well
documented so that they can be easily interfaced to your analysis code. EnSight 5,
which is now considered a legacy format, used a global coordinate array and
supported unstructured meshes only. EnSight 6 format again used a global
coordinate array but added support for structured meshes. EnSight Case Gold
(often just called Case format) is the most recent (and recommended) format.
Case Gold defines geometry on a part by part basis and uses element index for
connectivity. Case Gold format is tuned to the EnSight internal data structure and
is the fastest and most memory efficient format available for EnSight.
A dramatic speed up in performance can sometimes be realized simply by reading
in data in the given format and saving it back out as Case Gold, then re-reading
the data back in using the native Case Gold reader. However, a number of solvers
now output data directly into the well-documented Case format. (see Chapter 11,
EnSight Data Formats). The application ens_checker is included with EnSight to
enable error checking of the Case and EnSight 6 formats output by third-party
software.
Described below is the process for reading the latest (Case & EnSight 6) and the
legacy (EnSight 5) native formats:
EnSight Case Reader
EnSight5 Reader

EnSight 9 User Manual

2-15

2.2 EnSight Case Reader

EnSight Case Reader
In order to use this reader, you must be familiar with the basic data reader and part
loader dialogs discussed previously (see Chapter 2.1, Reader Basics).
EnSight6 and EnSight Gold are input using the exact same process. The data
consists of the following files:
•
•
•
•

Case file (required)
Geometry file (required)
Variable files (optional)
Measured/Particle files (optional)
- Measured/Particle geometry files
- Measured/Particle variable files

• Rigid body file (optional)
The Case file is a small ASCII file which points to all other files which pertain to
the model. The Case file names the geometry and variable files and records time
information. The geometry file is a general finite-element format describing nodes
and Parts, each Part being a collection of elements, and/or structured ijk blocks.
The variable file contains scalar (one value), vector (three values) or tensor (six or
9 values) data at each node and/or element. Measured/Particle files contain data
about discrete Particles in space from the simulation code or information directly
from experimental data.
EnSight data is based on Parts. The Parts defined in the data are always available
on the Server. However, all Parts do not have to be loaded to the Client for display.
Large flow fields for CFD problems, for example, are needed for computation by
the Server, but can be loaded non-visual.
EnSight data can be transient. The geometry as well as the variables can change
with each timestep. The casefile contains the filenames or filename patterns for
the transient data.
Simple Interface
Data Load

Load your casefile (typically named with a suffix .case) using the Simple Interface
method.

Advanced Interface
Data Load

Load your casefile (typically named with a suffix .case) using the Advanced
Interface method.
Data Tab
Format

Use the Case format to read EnSight6 or EnSight Gold data.

Set Case

Select the casefile (typically .case) and click this button

(see How To Read Data)

2-16

EnSight 9 User Manual

2.2 EnSight5 Reader

EnSight5 Reader
EnSight5 input data consists of the following files:
•
•
•
•

Geometry file (required)
Result file (optional)
Variable files (optional)
Measured Particle Files (optional)
- Measured/Particle geometry files
- Measured/Particle results files
- Measured/Particle variable files

The geometry file is a general finite-element format describing nodes and Parts,
each Part being a collection of elements. The result file is a small ASCII file
allowing the user to name variables and provide time information. The result file
points to variable files which contain the scalar or vector information for each
node. Measured/Particle files contain data about discrete Particles in space from
the simulation code or information directly from actual experimental tests.
EnSight5 data is based on Parts. The Parts defined in the data are always available
on the Server. However, all Parts do not have to be loaded to the Client for display.
Large flow fields for CFD problems, for example, are needed for computation by
the Server, but do not generally need to be seen graphically.
EnSight5 data can have changing geometry, in which case the changing geometry
file names pattern is contained in the results file. However, it is still necessary to
specify an initial geometry file name in the (Set) Geometry field.
Simple Interface
Data Load

Load your geometry file (typically named with a suffix .geo) using the Simple
Interface method.

Advanced Interface
Data Load

Load your geometry and result files (typically named with a suffix .geo and .res)
using the Advanced Interface method.
Data Tab
Format

Use the EnSight 5 format.

Set geometry

Select the geometry file (typically .geo) and click this button

Set results

Select the results file (typically .res), and click this button.

Format Options Tab
Set measured

Select the measured file and click this button.

(see How To Read Data)

EnSight 9 User Manual

2-17

2.3 Other Readers

2.3 Other Readers
ABAQUS_FIL Reader
ABAQUS_ODB Reader
AcuSolve Reader
AUTODYN Reader
AIRPAK/ICEPAK Reader
ANSYS Reader
AVUS Reader
CAD Reader
CFF Reader
CFX4 Reader
CFX5 Reader
CGNS Reader
CTH Reader
ESTET Reader
EXODUS II Gold Reader
FAST UNSTRUCTURED Reader
FIDAP NEUTRAL Reader
FLOW3D-MULTIBLOCK Reader
FLUENT Direct Reader
FLUENT UNIVERSAL Reader
Inventor Reader
LS-DYNA Reader
Movie.BYU Reader
MPGS 4.1 Reader
MSC.DYTRAN Reader
MSC.MARC Reader
MSC.NASTRAN Reader
Nastran Input Deck Reader
N3S Reader
OpenFOAM Reader
OVERFLOW Reader
PLOT3D Reader
POLYFLOW Reader
RADIOSS Reader
SDRC Ideas Reader
SILO Reader

2-18

EnSight 9 User Manual

2.3 Other Readers

STAR-CD and STAR-CCM+ Reader
STL Reader
Tecplot Reader
Vectis Reader
XDMF Reader

EnSight includes a number of readers for non-native (non-EnSight) formats. This
section includes a description of each of these included readers and includes
instruction for their use. Some of the included readers are custom, internal
readers, and some of them are written using the standard, User Defined Reader
interface.
User Defined
Reader
Description

A user defined reader capability is included in EnSight which allows otherwise
unsupported structured or unstructured data to be read. In other words, the user
can create their own data readers. Each user defined reader utilizes a dynamic
shared library produced by the user. Once produced, these readers show up in the
list of data formats in the File Open Dialog just like the included readers.

User Defined
Reader
Implementation

The readers are produced by creating the routines documented in the user-defined
API. Three versions of the user defined API are available The 1.0 API (which has
been available since EnSight version 6) was designed to be friendly to those
producing it, but requires more manipulation internally by EnSight and
accordingly requires more memory and processing time. The 2.0 API (starting
with EnSight 7.2) was designed with efficiency in mind. It requires that all data be
provided on a part basis, and as such lends itself closely to the EnSight Gold type
format. A few of the advantages of the 2.0 API (Now at version 2.08) are:
* Less memory, more efficient, and faster - as indicated above.
* Model extents can be provided directly, such that EnSight need not read all the
coordinate data at load time.
* Tensor and complex variables are supported
* Exit routine provided, for cleanup operations at close of EnSight.
* Geometry and variables can be provided on different time lines (timesets).
* If your data format already provides boundary shell information, you can use it
instead of the “border” representation that EnSight would compute.
* Ghost cells (for both structured and unstructured data) are supported
* User specified node and/or element ids for structured parts are supported
* Material handling is supported
* Nsided and Nfaced elements are supported
* Structured ranges can be specified
* Failed elements is supported
* Material Species is supported
* Rigid Body values can be supplied from the reader.
* Reader can be allowed to deal with block min, max, and stride within itself instead of having EnSight deal with it.
A 3.0 reader API is available in EnSight 9. The 3.0 API aims to provide the

EnSight 9 User Manual

2-19

2.3 Other Readers

flexibility of both of the previous versions while simplifying the reader
development processes. Contact CEI for more information on this API.
Creating Your Own
Custom User
Defined Reader

The process for creating and using a user-defined reader is explained in detail in
the Interface Manual. Samples, source code, makefiles, etc can be found in the
following location and it’s subdirectories:
On the CD: /CDROM/ensight92/src/readers
In installation
directory: $CEI_HOME/ensight92/src/readers
Start EnSight (or EnSight server) with the command line option (-readerdbg), for
a step-by-step echo of reader loading progress.
ensight92 -readerdbg
The actual working user defined readers included in the EnSight distribution may
vary by hardware platform.

2-20

EnSight 9 User Manual

2.3 ABAQUS_FIL Reader

ABAQUS_FIL Reader
The ABAQUS .fil reader is available to EnSight users, but the preferred method
of loading ABAQUS data is to use the .odb reader (see Section , ABAQUS_ODB
Reader).
ABAQUS_FIL input data consists of the one file with a .fil extension:
• Geometry/Results file (required). This file (the ABAQUS .fil file)
contains both the geometry and any requested results. It can be either
ASCII or binary.
• EnSight5 Measured/Particle Files (optional). The measured .res file
references the measured geometry and variable files.

Simple Interface
Data Load

EnSight will read ASCII or binary .fil files directly. The element sets in the .fil file
will be used for creating parts.
Load your geometry/results file (typically named with a suffix .fil) using the
Simple Interface method.

Advanced Interface
Data Load

Load your geometry/result file (typically named with a suffix .fil) using the
Advanced Interface method.
Data Tab
Format

Use the ABAQUS fil format.

Set results

Select the geometry/results file (typically .fil), and click this
button.

Format Options Tab
Set measured
Data Part Loader

Select the measured file and click this button.

The Part Loader for this reader is simply an informational message with Okay and
Cancel buttons, as shown below. There is no way to load part by part in this
reader.

Figure 2-9
ABAQUS FIL Reader Part Loader dialog

EnSight 9 User Manual

2-21

2.3 ABAQUS_ODB Reader

ABAQUS_ODB Reader
Overview
Because the reader is dependent upon the ABAQUS libraries, this reader is only
available for platforms supported by ABAQUS. See their website for more
details.
For updated information please see the file in the following directory:
$CEI_HOME/ensight92/src/readers/abaqus/README_67.txt or _68.txt

The ABAQUS odb reader is the recommended method of importing ABAQUS
data into EnSight.
Simple Interface
Data Load

Load your geometry/results file (typically named with a suffix .odb) using the
Simple Interface method.

Advanced Interface
Data Load

Load your geometry/result files (typically named with a suffix .odb) using the
Advanced Interface method.
Data Tab
Format

Use the ABAQUS_ODB format.

Set geometry

Select the geometry file (typically .odb) and click this button

Set results

Not used

Format Options Tab

2-22

Set measured

Select the measured file and click this button.

Reader GUI

User controls as shown below are available:

Load Surface
Sets

Toggle ON (default) to load all Surface Sets

Load Node
Sets

Toggle ON to load all Node Sets (default OFF).

EnSight 9 User Manual

2.3 ABAQUS_ODB Reader

Load “All”
Sets

Often, ABAQUS parts that are simply the global element
matrix are redundant (e.g. E_ALL contains all elements).
Toggle OFF (default) to skip loading Parts with “all” in their
name, saving memory and time.

Load Freq
Step

Often, ABAQUS will include multiple steps in an ODB file
and the one desired is the modal analysis. Toggle this ON to
skip all other steps loading only the frequency step (Default
is OFF). If multiple frequencies, then each EnSight timestep
now becomes a different frequency.

Load
Element
Faces

Toggle ON to convert Surface Sets with 3D elements with
Face Sets into 2D elements using face specifications (default
OFF).

Use Section

Shell elements include variable data for each section. This
reader allows the use of the First (default) or the Last section.

Integration
Point

Shell elements include variable data for each of several
integration points. Choose max, min or average (default).

Console
Output

Normal - Informational and error output to the console.
Verbose - Detailed informational and error output to the
console.
Debug - Step by step progress through the reader with detail
numerical output for results to the console.
None - No console output

Instance

Choose an instance (1 to the number of instances). Default is
to load them all.

Step

Choose a step (1 to number of steps). Default is to load all
non-frequency steps.

Shell Section

Which shell section to use (1 to number of shell sections).

Starting Part
Number

Which part to begin loading (1 to number of parts). Default is
1 (load all parts).

(see How To Read Data)

EnSight 9 User Manual

2-23

2.3 AIRPAK/ICEPAK Reader

AIRPAK/ICEPAK Reader
Overview
The current FLUENT Direct Reader also reads AIRPAK and ICEPAK data. The
Fluent Direct reader typically loads a Fluent Case (.cas) file and the matching data
(.dat) file. However, AIRPAK/ICEPAK writes out a .fdat file which doesn’t
automatically get recognized by the EnSight Fluent reader and some extra
understanding (and sometimes user-intervention) is necessary as described below.
See the following files for latest information on the Fluent reader.
$CEI_HOME/ensight92/src/readers/fluent/README.txt

The comments that follow are for the current Fluent reader. The reader loads
ASCII, binary single precision, or binary double precision. The files can be
uncomrpessed or compressed using gzip.
Data file
description

ICEPAK can generate files: filename.cas, filename.dat just like Fluent, but also if
the analysis uses a nonconformal mesh (not available in Fluent) then there will be
filename.fdat, and filename.nc.cas files. The filename.nc.cas is a nonconformal
mesh geometry and it’s matching results file is the filename.fdat file.

Simple Interface
Data Load

Load your geometry file (typically named with a suffix .cas) using the Simple
Interface method. EnSight will automatically load the matching .dat file.
However, if you want to load the filename.nc.cas data file and it’s corresponding
filename.fdat file, then you will either need to rename it to match exactly and have
the .dat extension (filename.nc.dat), or go to the advanced data load.

Advanced Interface
Data Load.

In EnSight if you don’t want to rename your files, then switch to the Advanced
Interface toggle in the data reader dialog and manually choose the *.nc.cas and the
*.fdat files as described below.
Data Tab
Format

To use this reader, select the Fluent format.

Set cas

Select the geometry file (typically .cas or .cas.gz) and click
this button. For transient data, use *.cas or *.cas.gz .

Set dat

Note that the Fluent reader will automatically select the
matching .dat file. If you want to use the .fdat file, then select
the results file (typically .fdat or .fdat.gz), and click this Set
Dat button. For transient data, use *.fdat or *.fdat.gz .

Format Options Tab
Set measured

2-24

Select the measured file and click this button.

EnSight 9 User Manual

2.3 AIRPAK/ICEPAK Reader

Other
Options
using the
current
Fluent reader

EnSight 9 User Manual

Load Internal
Parts

Toggle this ON to load the Fluent Internal Parts. This will
show all the the internal walls forming all the cell volumes. If
you do toggle this on, then it is recommended that you click on
the 'Choose Parts' button at the bottom of the data reader
dialog, rather than 'Load all', as you'll only want to load the
interior parts of interest to save memory and time. Default is
OFF.

Use Meta
Files

Meta files are small summary files that contain highlights of
the important locations inside each of the Fluent files.
Allowing the EnSight reader to write out Meta Files that map
the locations of important data can provide a significant speed
up the next time you access that timestep. It is recommended
that you leave this toggle ON. If you have write permission in
the directory where your data is located, three types of binary
Meta Files will be written when you first access each file, with
extensions .EFC for the cas file, .EFD for the .dat file and
.EFG for the time-history data. They are optional, and if you
don't have write permission, the reader will take the extra time
to read the entire .CAS and .DAT file to find the relevant data
each time you come back to that timestep.

Load _M1
_M2 vars

Variables that end in '_M1' and '_M2' occur in Fluent unsteady
flow. They represent the value of the variable at the prior
iteration time and the time prior to that respectively. By
default this toggle is OFF and these variables are not loaded.
Toggle this ON to load these variables.

Load all cell
types

Fluent cells have a boundary condition flag. By default
(toggle OFF) EnSight loads only the cells with a boundary
condition flag equal to 1 (one). Toggle this option ON to load
all cells with a non-zero boundary condition. For example, if
you have a part with cells of boundary condition 32 (inactive),
EnSight will, by default not load this part. Toggle this option
ON and EnSight will load this part. Note: parts containing
cells with a boundary condition of zero are never loaded.

2-25

2.3 AIRPAK/ICEPAK Reader

Console
Output

Use this flag to determine the amount of output to the console.
Normal - Usually only echo errors to console.
Verbose - Normal output plus an echo of every Fluent part
that is in the dataset, whether it is interior or not, whether it is
skipped, what variables are defined for which parts, and to
echo it's Ensight Part number.
Debug - Verbose output plus more detailed output and
progress through the reader routines often valuable for
understanding and reporting problems.

Time Values

Default is 'Calc Const Delta', to read a delta time from one file
and calculate the time values from that. If you choose 'Read
Time Values' then the reader will open each file and find the
exact time value. This will be stored in the EFG file if you've
not disabled Meta Files. Finally, the simplest is to 'Use File
Steps' which will just use the file step number as the time
value. This is quick, but is not a good idea if you need real
time for anything such as particle tracing.

(see How To Read Data)

2-26

EnSight 9 User Manual

2.3 Medina BIF-BOF PERMAS Reader

Medina BIF-BOF PERMAS Reader
Overview
Currently this reader is supported only for the following architectures: UNIX 64bit, Linux 32-bit, IBM 5.3 64-bit, and Win32.
This reader reads in an ASCII configuration file with a .konfig suffix, which lists
the geometry and results filenames.
To use this reader, you need to set the HDMcat environment variable to point to
the dscat.ds file as described in the README.
$CEI_HOME/ensight92/src/readers/medina_bifbof/README_single_part.txt
Simple Interface
Data Load

Load your geometry/results file (typically named with a suffix .konfig) using the
Simple Interface method.

Advanced Interface
Data Load

Load your geometry/result files (typically named with a suffix .konfig) using the
Advanced Interface method.
Data Tab
Format

Use the Medina bif/bof format.

Set file

Select the geometry/results file (typically .konfig) and click
this button

Format Options Tab
Set measured

Select the measured file and click this button.

(see How To Read Data)

EnSight 9 User Manual

2-27

2.3 AcuSolve Reader

AcuSolve Reader
Overview
Description

This reader from AcuSim will read results from Acusolve. Select the .log file
from the simple or advanced interface.

Data Reader
Main Menu > File > Data (reader)...

The File Selection dialog is used to specify which files you wish to read.
Access: Main Menu > File > Data (Reader)...

Simple Interface
Data Load

Load your AcuSolve .log file using the Simple Interface method.

Advanced Interface
Data Load

Load your AcuSolve .log file using the Advanced Interface method.
Data Tab
Format

Use the AcuSolve format.

Set file

This field contains the first file name. For the first file you
should choose a file with extension .log. Clicking button
inserts file name shown into the field. Loading the .log file
will load all both geometry and results.

Format Options Tab
Set measured

Select the measured file and click this button.

Other
Options

Reset time

When toggle is on, time begins at 0.0 ( default is off).

Extended
output

When toggle is on, console output will be verbose ( default is
off ).

Mesh Motion

When toggle is on, moving meshes are visible ( default is on).

Unique parts

When toggle is on, a unique set of surfaces is shown in the part
list ( default is off).

Additional
runs

Enter the comma separated list of runs ( 3, 5, 10, 10:20:2), or
_all. ( default is _none).

Note: there is an older AcuSolve (v10 api) reader available from AcuSim.
(see How To Read Data)

2-28

EnSight 9 User Manual

2.3 AcuSolve Reader

EnSight 9 User Manual

2-29

2.3 ANSYS Reader

ANSYS Reader
Overview
Four Ansys
Readers

There are four ANSYS readers available in EnSight: three older, unsupported
legacy readers and the supported Ansys Results. Long-term, Ansys Results is the
reader of choice. This reader should read the latest Ansys results as well as older
versions. The other three, legacy readers will not show up in the reader list by
default and will not be documented in this manual.

Legacy Reader
Visibility Flag

The older readers, by default, are not loaded into the list of available readers, and
are not discussed in the remainder of this document. In the unlikely event you
need to enable these readers, go into the Menu, Edit > Preferences and click on
Data and toggle on the reader visibility flag. The legacy reader documentation is
found in $CEI_HOME/ensight92/src/readers/ansys/README and is not included here.

Ansys Results
Reader

The Ansys Results reader supports scalar, vector and tensor variables, including
the capability to compute several common scalar variables derived from tensors
(such as the common failure therories) as well as local element result components
(such as axial stress in truss elements) when such element results are available.
Additionally, there is some control over the creation of variables from elementbased results. For example, they can be averaged to the nodes (with or without
geometry weighting) if desired. See the format options below for more details.
Results are always presented in the global coordinate system. Thus, any results in
local coordinate systems, or in non-cartesian coordinate systems are transformed
as needed into the model system.
For shell elements that have multiple layers (sections), the user can choose the
section that will be used. Additionally, the user can choose to have a different
variable be created for each section. See format options below for more details.
The user can control how parts are created. Parts can be created according to the
part id, the property id, or the material id.

Simple Interface
Data Load

Load your geometry/results file (typically named with a suffix .rst) using the
Simple Interface method.

Advanced Interface
Data Load

Load your geometry/result files (typically named with a suffix .rst) using the
Advanced Interface method.
Data Tab
Format

Use the Ansys Results format.

Set file
(or results)

Select the geometry/results file (typically .rst) and click this
button

Format Options Tab
Set measured

2-30

Select the measured file and click this button.

EnSight 9 User Manual

2.3 ANSYS Reader

Other
Options

Include
ElemSet
Parts

Include any Element sets defined. These are sets of full
elements which are generally some logical subset of the total
number of elements. Default is on.

Include Face/
Edge Parts

Include any Face or Edge sets defined. These are some logical
set of particular faces and/or edges of full elements. Default is
on.

Include
NodeSet
Parts

Include any Node sets defined. These are generally the subset
of nodes needed for the Element, Face, or Edge sets above. As
such, they are generally not needed as separate parts, but can
be created if desired. Default is off.

Include local
elem res
comps (if
any)

Include the local stresses components, etc that are in the
element's local system.
A simple example is a bar (such as a truss element), which
only has tension or compression in the element's axial
orientation. Such an element would have an axial stress
variable.
Other elements would have appropriate result component
variables. Default is on

EnSight 9 User Manual

2-31

2.3 ANSYS Reader

Include
Tensor
derived
(VonMises,
etc.)

For tensor results, calculate scalars from the following derived
results (principal stress/strains, and common failure theories):
Mean
VonMises
Octahedral
Intensity
Max Shear
Equal Direct
Min Principal
Mid Principal
Max Principal
By default, all 9 of these will be derived. You can control
which are created by this toggle, with an environment
variable. Namely,
setenv ENSIGHT_VKI_DERIVED_FROM_TENSOR_FLAG n

where n = 1for Mean only
2 for VonMises only
4 for Octahedral only
8 for Intensity only
16 for Max Shear only
32 for Equal Direct only
64 for Min Principal only
128 for Mid Principal only
256 for Max Principal only
512 for all
or any legal combination. example: for VonMises and Max
Shear only, use 18. Default is off
Regular Part
Creation
Convention

Parts will be created according to the following:
Use Part Id - Part Id

(this is the default)

Use Property Id - Property Id
Use Material Id - Material Id

Var naming
convention

Use Content Field (if provided) - Variable names will be what
is in the Content field, if provided. If not provided, they will
be the VKI dataset name. This is the default.
Use VKI dataset nameVariable names will be the VKI variable
dataset name (which are reasonably descriptive).

2-32

EnSight 9 User Manual

2.3 ANSYS Reader

Element Vars
as

Single element values - Element results (whether centroidal or
element nodal) will be presented as a single value per element.
Thus will be per_elem variables in EnSight.This is the default.
Averaged to node values - Element results (whether centroidal
or element nodal) will be averaged to the nodes without using
geometry weighting. Thus will be per_node variables in
EnSight.
Geom weighted average to node values - Element results
(whether centroidal or element nodal) will be averaged to the
nodes using geometry weighting. Thus will be per_node
variables in EnSight

If Sections,
which:

Which section will be used to create the variable
First - The first section will be used (this is the default)
Last - The last section will be used
Section Num (below) - The section number entered in the field
below will be used
Separate Vars per Section - A separate variable will be created
for each section.

Section Num

If the previous option is chosen to be Section Num, then the
value in this field is the 1-based section number to use to
create the variable.

(see How To Read Data)

EnSight 9 User Manual

2-33

2.3 AUTODYN Reader

AUTODYN Reader
Overview
Description

Reads a series of .adres files as a transient solution. Simply select one of the
.adres files and the sequence will be detected. Requires that the .adres_base files
exists in the same directory.

Data Reader
Main Menu > File > Data (reader)...

The File Selection dialog is used to specify which files you wish to read.
Access: Main Menu > File > Data (Reader)...

Simple Interface
Data Load

Load your AUTODYN .adres file using the Simple Interface method.

Advanced Interface
Data Load

Load your AUTODYN .adres file using the Advanced Interface method.
Data Tab
Format

Use the Autodyn format.

Set file

This field contains the first file name. For the first file you
should choose a file with extension .adres. Clicking button
inserts file name shown into the field. Loading any .adres file
will load all .adres files in the directory which includes both
geometry and results.

Format Options Tab
Set measured

Select the measured file and click this button.

Other
Options

2-34

EnSight 9 User Manual

2.3 AUTODYN Reader

Include
ElemSet
Parts

Include any Element sets defined. These are sets of full
elements which are generally some logical subset of the total
number of elements. Default is on.

Include Face/
Edge Parts

Include any Face or Edge sets defined. These are some logical
set of particular faces and/or edges of full elements. Default is
on.

Include
NodeSet
Parts

Include local
elem res
comps (if
any)

EnSight 9 User Manual

2-35

2.3 AUTODYN Reader

Include
Tensor
derived
(VonMises,
etc.)

Parts will be created according to the following:
Use Part Id - Part Id

(this is the default)

Use Property Id - Property Id
Use Material Id - Material Id

Var naming
convention

2-36

EnSight 9 User Manual

2.3 AUTODYN Reader

Element Vars
as

If Sections,
which:

Section Num

If the previous option is chosen to be Section Num, then the
value in this field is the 1-based section number to use to
create the variable.

(see How To Read Data)

EnSight 9 User Manual

2-37

2.3 AVUS Reader

AVUS Reader
Overview
The AVUS reader has been recently renamed, and was formerly called the
COBALT reader.
CEI provides the AVUS user-defined-reader on as "as-is" basis, and does not
warrant nor support its use.
There are two distinct readers for AVUS data (formerly Cobalt60) -- one for static
data, AVUS (formerly Cobalt60), and one for transient solution data, AVUS Case
(formerly Cobalt60 Case).
Both readers will read formatted and unformatted (single or double precision)
Cobalt60 grids, solution files (pix files), and Cobalt60 restart files. The file format
is determined automatically by the reader. The readers also support an enhanced
solution (pix) format that contains additional solution data beyond the normal six
fields.
See the following README file for current information on this reader and
contact the author as listed in the README file for further information.
$CEI_HOME/ensight92/src/readers/avus_cobalt_2/README
Simple Interface
Data Load

Load your geometry file (typically named with a suffix .grd) using the Simple
Interface method.

Advanced Interface
Data Load

Load your geometry and restart files (typically named with a suffix .grd and .pix)
using the Advanced Interface method.
Data Tab
Format

Use the AVUS or AVUS Case format.

Set grid
(or file)

Select the geometry file (typically .grd) and click this button
(or select the .case file for AVUS Case)

Set solution

Select the restart file (typically .pix), and click this button.

Format Options Tab
Set measured
Limitation

Select the measured file and click this button.

This reader does not support restoring EnSight Context Files.
(see How To Read Data)

2-38

EnSight 9 User Manual

2.3 CAD Reader

CAD Reader
Overview
This reader uses an external translation program to get various CAD files into an
STL formatted temporary file which then read into EnSight. With the proper
licensing, the following CAD file formats can be read: IGES (.igs), STEP
(.STEP), CATIA V4 (.model, .dlv, .exp, .session), CATIA V5 (.CATPart,
.CATProduct, or .CATDrawing, on Windows 32/64-bit only), Parasolid (.x_t,
.x_b), Pro/Engineer (.prt, .asm), SolidWorks (.sldprt, .sldasm), Unigraphics (.prt),
and possibly others.To manually convert this ProE data set into an STL using the
CEI CAD translator, run this command:
ConvertSTL -i ./asm0002.asm.15 -o rs.stl

Additional licensing may be required. Please visit http://cad.ensight.com for more
information.
The CAD reader will also load STL files directly (either ASCII or binary) that
consist only of surfaces (triangles) and have no associated variables. See the STL
Reader.
See the following README file for current information on this reader in the
following directory.
$CEI_HOME/ensight92/src/readers/stl
Simple Interface
Data Load

Load your geometry file using the Simple Interface method and trust that the
translator will recognize the file type using the suffix.

Advanced Interface
Data Load

For more options, load your geometry using the Advanced Interface method and
click on the Format Options Tab as described below.
Data Tab
Format

Use the CAD format.

Set File

Select the CAD geometry file and click this button

Format Options Tab
Set measured

EnSight 9 User Manual

Select the measured file and click this button.

2-39

2.3 CAD Reader

Reader GUI

Console
Output

Allows the user control of the amount and detail of the
console output. The allowable choices are as follows
Normal - Typically only error messages displayed (the
default)
Verbose - Normal messages plus informational messages
Debug - Messages indicating progress through the reader and
useful for diagnosing problems

2-40

CAD Format

A pulldown to specify the format if the file name and
extension are not sufficient for automatic selection of the CAD
format. Allowable selections include CATIA v4, CATIA v5,
IGES, Parasolid, ProE, SolidWorks, STEP, Unigraphics, and
STL

Surface
Tolerance in
degrees

The maximum distance between a facet edge and the true
surface. It is a floating point value between 0 and 360 degrees,
with a default value: 15.0

Normal
Tolerance in
degrees

The maximum angle in degrees between two normals on two
adjacent facet nodes. Default value: 25. It is a floating point
value.

Max edge
length in mm

Maximum length of a side of a cell in world space in
millimeters. It is a floating point value with default of 0 (no
max)

Save
translated
STL file to

The name of the translated STL output file. If this name is
specified, then the STL output file is not automatically deleted
after processing. Default value: determined by system call
tempnam(). Example: /var/tmp/my_data.stl

EnSight 9 User Manual

2.3 CAD Reader

STL ASCII
file tolerance

A positive floating point value used to round off coordinate
values read from ASCII STL files to compensate for the fact
that there is often a roundoff error on the last digit which leads
to discontinuity in the triangle facets.
Example: 1.0E-3 - Sets tolerance value to 1.0E-3
For example: If coordinate value is 147.3247 and Tolerance is
1.0E-3 then new coordinate is 147.324 If Tolerance is 1.0E-2
then new coordinate is 147.32

(see How To Read Data)

EnSight 9 User Manual

2-41

2.3 CFF Reader

CFF Reader
Overview
The CFF Reader is supplied compiled on Linux platforms on as "as-is" basis, and
CEI does not warrant nor support its use. A README file as well as the source
code is also supplied with the EnSight distribution in the directory below.
$CEI_HOME/ensight92/src/readers/cff

2-42

EnSight 9 User Manual

2.3 CFX4 Reader

CFX4 Reader
Overview
Reads a 3D Static Cbinary dump (.dmp) file.
See the following file for current information on this reader.
$CEI_HOME/ensight92/src/readers/cfx4/README.txt
Simple Interface
Data Load

Load your geometry/results file (typically named with a suffix .dmp) using the
Simple Interface method.

Advanced Interface
Data Load

Load your geometry/results file (typically named with a suffix .dmp) using the
Advanced Interface method.
Data Tab
Format

Use the CFX-4 format.

Set cfx4 dmp

Select the geometry/results file (typically .dmp) and click this
button

Format Options Tab
Set measured

Select the measured file and click this button.

(see How To Read Data)

EnSight 9 User Manual

2-43

2.3 CFX5 Reader

CFX5 Reader
Overview
Reads a CFX version 10, 11, or 12 results (.res) file.
Simple Interface
Data Load

Load your geometry/results file (typically named with a suffix .res) using the
Simple Interface method.

Advanced Interface
Data Load

Load your geometry/results file (typically named with a suffix .res) using the
Advanced Interface method to customize the read, for example to read transient
geometry (see below).
Data Tab
Format

Use the CFX-5 format.

Set file

Select the geometry/results file (.res) and click this button

Format Options Tab
Set measured

Select the measured file and click this button.

Reader GUI

Variable User
Level

Allows the user control of number of variables read based on
a call into the CFX API. The allowable choices are as follows:
Level 0 - Read in all variables
Level 1 - (default)
Level 2 Level 3 -

2-44

EnSight 9 User Manual

2.3 CFX5 Reader

Variable
Boundary
Correction

Variable values are corrected using a boundary value
correction if this toggle is Yes.
YES - (default) Variable values adjusted using a boundary
value correction.
No - Variable values are not corrected.

Read
Regions?

No - (default) - Do not read Regions.

Transient
Geometry?

A flag to the reader if the data is transient. Note: by default, a
transient .res file will fail to load unless this is changed to Yes.
CFx transient data will have a .res file and a series of .trn files
(one for each timestep) located in a subdirectory. The res file
will have the names of the .trn files, the time value and path. If
the data is changing variables only then the .trn will not
contain the mesh. If the mesh is moving, then the user must
turn on the “Include Mesh” in the Transient Result options so
tha tthe solver will write mesh information to each .trn file.
Failure to do this results in a static, unmoving mesh over time.

YES - Read Regions.

No - (default).
Yes - Coordinates only.
Particles as
Part?

If this is Yes, then EnSight reads in the particle data as a
separate EnSight point part.
No - (default) Do not read in particles as a separate EnSight
Part.
Yes - Read in the particles as a separate EnSight part

The CFx solver does export to EnSight Case Gold format.
(see How To Read Data)

EnSight 9 User Manual

2-45

2.3 CGNS Reader

CGNS Reader
Overview
See the following file for current information on this reader.
$CEI_HOME/ensight92/src/readers/cgns/README.txt
Simple Interface
Data Load

Load your geometry/results file (typically named with a suffix .cgns) using the
Simple Interface method.

Advanced Interface
Data Load

Load your geometry/results files (typically named with a suffix .cgns) using the
Advanced Interface method.
Data Tab
Format

Use the CGNS format.

Set cgns

Select the geometry/results file (typically .cgns) and click this
button

Format Options Tab
Set measured

Select the measured file and click this button.

(see How To Read Data)

2-46

EnSight 9 User Manual

2.3 CTH Reader

CTH Reader
Overview
Reads a Spymaster .spcth file.
See the following file for current information on this reader.
$CEI_HOME/ensight92/src/readers/cth/README.txt
Simple Interface
Data Load

Load your geometry/results file(s) (typically named with a suffix .spcth) using the
Simple Interface method.

Advanced Interface
Data Load

Load your geometry/results files (typically named with a suffix .spcth) using the
Advanced Interface method.
Data Tab
Format

Use the CTH format.

Set spcth*

To read one Spymaster file, put the CTH Spymaster file
(typically named something filename.spcth) into the (Set)
Geometry field. To read in multiple, related CTH Spymaster
files (for example several files solved in parallel) as follows:
filename.spcth.0
filename.spcth.1
filename.spcth.2

Put an asterisk ‘*’ in the filename (filename.spcth.*).
Format Options Tab
Set measured

Select the measured file and click this button.

Reader GUI

User controls as shown below are available:

(see How To Read Data)

EnSight 9 User Manual

2-47

2.3 ESTET Reader

ESTET Reader
Reader Visibility
Flag

By default, this reader is not loaded into the list of available readers. To enable
this reader go into the Menu, Edit > Preferences and click on Data and toggle on
the reader visibility flag.

Overview
ESTET input data consists of one file that contains all geometry and results
information. Data is loaded in a multi-step process. The ESTET data is a
structured grid. The data file is binary.
Simple Interface
Data Load

Load your geometry/results file (typically named with a suffix .estet using the
Simple Interface method.

Advanced Interface
Data Load

Load your geometry/results file (typically named with a suffix .estet) using the
Advanced Interface method.
Data Tab
Format

Use the ESTET format.

Set geometry

Select the geometry/results file (typically .estet) and click this
button

Format Options Tab
Set measured

Select the measured file and click this button.

When reading this data into EnSight, the part loader dialog will be essentially the
same as that found in the reader basics for structured data (See Reading and
Loading Data Basics). The data can be in rectangular, cylindrical, or curvilinear
coordinates. EnSight will interpret and convert properly for any of these types.

Figure 2-10
ESTET Vector Builder and Data Part Loader dialogs

One difference from the Reader Basics, is that once the desired geometry has been
extracted as Parts, you are presented with a list of the results variables contained
in the file. There is no way to automatically determine which of the results
2-48

EnSight 9 User Manual

2.3 ESTET Reader

variables are actually vector components, so you are given the opportunity to
build the vectors from the variables. The descriptions usually make this a
straightforward process. All variables not used as components to vectors are
assumed to be scalar variables.
ESTET Vector Builder and Data Part Loader dialogs

Figure 2-11
ESTET Vector Builder and Data Part Loader dialogs

You use the File Selection dialog to read ESTET data files, the ESTET Vector Builder
dialog to build vector variables from scalar components for an ESTET dataset, and the
Data Part Loader dialog to extract Parts from an ESTET dataset. The latter two dialogs
open in sequence automatically after you click Okay in the File Selection dialog.
Access: Main Menu > File > Data (Reader)…> ESTET

(see How To Read Data)

EnSight 9 User Manual

2-49

2.3 EXODUS II Gold Reader

EXODUS II Gold Reader
Overview
Misc Notes

The Exodus reader links to the exodus routines in libexoIIc.a and the netcdf
routines in libnetcdf.a. You must have these libraries to compile and run the
ExodusII reader.
Variable names that end in "_x", "_y", "_z" will be treated as components of a
vector. For example, the variables "vel_x", "vel_y", "vel_z" will be treated as a
vector named "vel_vec". Case is ignored in matching variable names.

GUI control of
Reader

Note reader behavior can also be controlled in the Data Reader GUI via
checkboxes and fields. The environment variables, if set, are used to set the
default values for the GUI.

Advanced Multiple
File Naming

This reader supports two extensions to the filename fields. The first supports
Exodus datasets where the geometry changes at some point in time. In this case, a
new Exodus file (or set of files), is used for each set of solution times. To support
this feature, insert wildcard characters (e.g. "*" and "?") in the filename that
expand to the name of the first files in each timeset.
The second extension allows for multiple files to be read as part of the same
timeset (e.g. domain decomposed files). This feature takes the form of a tag
() appended to the filename. The value of "X" is the number of files in the
timeset and "Y" is the sprintf() format string on the integer (%d) formatting
options) for expanding an integer argument into a string. For example, if a dataset
consists of the following files:
Times 0-10
foo.e.03.00
foo.e.03.01
foo.e.03.02

Times 11-15
foo.e-s0002.03.00
foo.e-s0002.03.01
foo.e-s0002.03.02

Where the "foo.e.*" files contain timesteps 0 through 10 and the "foo.e-s0002.*"
files contain timesteps 11 through 15. Also, each timeset is spatially decomposed
into 3 subfiles, which each contain some portion of the dataset for the given
timesteps. For this dataset, use the file pattern "foo.*.03.<3:%0.2d>" to tell
EnSight there are multiple timesets and to generate the filenames for each timeset
by replacing the "<..>" substring with a number from 0 to 2 as generated using
sprintf() and "%0.2d". Note that the "<...>" marker must be the last part of the
filename. The ‘*’ will wildcard the timeset number and the “<...>” specifies the
spatial decomposition.
When using SoS casefiles, the servers will automatically distribute the subfiles
over all of the specified servers. There can be no more servers than the number of
sub-files however (but fewer servers are legal and in most cases, recommended).
Finally, if there are sub-files, the number and the naming convention must be the
same over all timesets.
Autodetection of
Spatially and
Temporally
Decomposed
Datasets

The Exodus reader includes a ‘Autodetect Spatial Decomp’ option. In the
‘MultiExodusII’ reader, this option is off by default, but in the ‘MultiExodusIIng’
reader, it is enabled by default. When using this option, simply select one of the
files in the dataset and EnSight will attempt to figure out the spatial and temporal
decomposition scheme by parsing the filename and scanning the directory.
If your dataset naming conventions follow the example above, this option is a

2-50

EnSight 9 User Manual

2.3 EXODUS II Gold Reader

much simpler way of opening the entire dataset. In the previous example, the user
need only select to load the file ‘foo.e.03.00’ to load the entire dataset. For must
users who follow the general filenaming guidelines, it is strongly suggested they
use the ‘MultiExodusIIng’ reader (and its dataset autodetection scheme) to load
their decompoased data.
The “autodetection” scheme parses the name, looking for a trailing .X.Y scheme,
where X and Y are zero padded integers, to detect that the file is spatially
decomposed. If the name does not end in this form, it is assumed that the dataset is
not spatially decomposed. The scheme also parses the filename looking for the
string ‘.e’ and checks the current directory for other files in the same directory that
have other text between the ‘.e’ and the spatial ‘.X.Y’ (if it exists). If multiple files
are found (checked using patial chunk 0), then the autodetection assumes that the
dataset is temporally decomposed as well. The reader will load all of the Exodus
II files matching the autotected scheme as a single temporal and/or spatially
decomposed dataset.
Note that the option effectively prevents you from being able to open an
individual Exodus temporal or spatial “chunk”, but for most situations, that is not
an issue.
Environmental
variables

The following Environmental variables can be se to modify the behavior of the
Exodus reader. Many of these are available as well in the reader dialog. When
you choose Exodus reader, under the format options tab, will be a number of
options for controlling the reader behavior. The advantage of setting the
Environmental variables is that you can control the default behavior.
ENSIGHT_EXODUS_SCALE - set to a scaling factor (default 1.0)
ENSIGHT_EPSILON - set to a temporal epsilon (default 1.0)
ENSIGHT_EXODUS_DF (or EXODUS_DF) - if nonzero, support distribution
factors (off by default)
ENSIGHT_EXODUS_NO_SIDESETS - if nonzero, disable sideset support
(enabled by default)
ENSIGHT_EXODUS_NO_NODESETS - if nonzero, disable nodeset support
(enabled by default)
ENSIGHT_EXODUS_VERBOSE - if nonzero, enable verbose mode (off by
default)
ENSIGHT_EXODUS_USE_NODEMAPS - if nonzero, use node maps (default
true)
ENSIGHT_EXODUS_USE_HIGHERORDERELEMENTS - if non-zero, read
element order will be presered in EnSight. if zero, return first order elements for
higher order elements in the file (e.g. convert a HEX20 into a HEX08). (default
true)
ENSIGHT_EXODUS_IGNORE_CONSTANTS - if non-zero, constant variables
will not be read (default false)
ENSIGHT_EXODUS_CHECK_NANS - if non-zero, all read floats will be
checked for IEEE nans and set to zero if nan.
ENSIGHT_EXODUS_CLIP_TIMESTEP_OVERLAP - if non-zero, when

EnSight 9 User Manual

2-51

2.3 EXODUS II Gold Reader

multiple timesets result in overlapping time ranges, the ones in the first file read
are dropped.
ENSIGHT_EXODUS_AUTODETECT_DECOMP - if set and the filename
passed ended in the numbering scheme used in spatial decomposition of the form
.XX.00 the reader will convert the filename to the brace form: .XX..
This allows the user to select the first file in the decomposition and have the
proper template automatically generated.
ENSIGHT_EXODUS_USE_UNDEF_VALUE - if non-zero (the default), the
reader will return the server 'Undefined' float value when a variable is not defined
on a part. if set to 0, the value returned is actually 0.0 (this is the behavior for the
reader prior to 2.72).
ENSIGHT_EXODUS_NO_ELEMENT_ATTRS - if non-zero, the reader will not
attempt to read/use any element attribute variables.
ENSIGHT_EXODUS_USE_FULL_NAMES - By default, this option is set off
(0) and names are "reduced" to the original 19 character limits. If this option is
enabled (non-zero), the limit is updated to the current EnSight limit of 49
characters.
ENSIGHT_EXODUS_USE_DTA_FILE - By defualt, if there is a .dta file present,
the reader will pass its contents on the to the client. If this is set to 0, .dta files will
be ignored.
ENSIGHT_EXODUS_AUTOGEN_DTA - if non-zero, and there is no .dta file, a
"stub" .dta file will be automatically generated and passed to the client. This is
disabled by default.
Names file format

The .names file can be used to name parts in a Exodus file. Note that the names for
these files are generated by clipping off the input Exodus filename at the
rightmost '.' and adding the suffix ".materials" or ".names". External part names
and materials files have the same syntax.

*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*

2-52

File containing block, sideset, nodeset names
--------------------------------------------(Must have the same root as the .exo file, and reside in the same
directory, and have a .names extension)
Note:

1. Comments have a # in first column of the line.
2. Three types of sections (must be exactly as indicated):
blocks
sidesets
nodesets
(Presence of any of the sections is optional - for example,
if you only have blocks, you don't need the sidesets or
nodesets sections.)
3. There must be a number, white space, then name
on lines within the sections.
numbers must be 1-based (relates to the block number)
names must be a single token - no spaces (Underscores or

EnSight 9 User Manual

2.3 EXODUS II Gold Reader
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*

dashes are okay.)
4. Line length must be less than 80 chars - which should be
plenty since EnSight truncates names at 49 chars.
Thus, general format is:
blocks
1
name_for_block_1
2
name_for_block_2
.
.
.
.
.
.
n
name_for_block_n
sidesets
1
name_for_sideset_1
2
name_for_sideset_2
.
.
.
.
.
.
m
name_for_sideset_m
nodesets
1
name_for_nodeset_1
2
name_for_nodeset_2
.
.
.
.
.
.
p
name_for_nodeset_p

Here is an Example:
------------------blocks
1
Strongback
2
bolt_1
3
bolt_2
4
bolt_3
5
nut_1
6
nut_2
7
nut_3
8
Tab
9
screw_1
10
screw_2
11
screw_3
12
Block
sidesets
1
Strongback_end
2
Strongback_front
3
Strongback_back
nodesets
1
Tab_nodes

For the previous example, the files would be named "foo.1_03.names" and
"foo.1_03.materials". Only one .names and one .materials file is required.
See the following file for current information on this reader.
$CEI_HOME/ensight92/src/readers/exodus_gold/README.exodus

Data Reader
Simple Interface
Data Load

Load your geometry/results file (typically named with suffix .ex, or .ex2, or .exo)
using the Simple Interface method.

Advanced Interface
Data Load

Load your geometry/results file (typically named with suffix .ex, or .ex2, or .exo)

EnSight 9 User Manual

2-53

2.3 EXODUS II Gold Reader

using the Advanced Interface method.
Data Tab
Format

Use the MultiExodusII or MultiExodusIIng format.

Set exo

Select the geometry/results file (typically .ex, or .ex2, or .exo)
and click this button. If there are multiple Exodus files in the
solution set, you may enter a filename with wildcard characters,
for example, "mydata*.exo2" or "mydata1?.exo2"

Format Options Tab
Set measured Select the measured file and click this button.
Extra GUI
Parameters

These toggles and fields below are customized for the Exodus
reader.

Use
Distribution
Factors

2-54

If nonzero, use support distribution factors (off by
default). Node sets and side sets in Exodus can
have distribution factor weights associated with
them. If this option is set, these distribution factors
will be read by EnSight as additional scalar
variables on the node or side set parts. If the
Environment Variable ENSIGHT_EXODUS_DF
(or EXODUS_DF) is set, then the reader will use it
to set the default value.

EnSight 9 User Manual

2.3 EXODUS II Gold Reader

Ignore Side
Sets

If nonzero, disable sideset support (enabled by
default). If the Environment Variable
ENSIGHT_EXODUS_NO_SIDESETS is set then
the reader will use it to set the default value.

Ignore Node
Sets

If nonzero, disable nodeset support (enabled by
default). If the Environment Variable
ENSIGHT_EXODUS_NO_NODESETS is set then
the reader will use it to set the default value.

Use Node
and Element
Maps

If nonzero, use node maps (default true). Exodus
files may contain element and nodal labels, referred
to as nodemaps. If this option is set, EnSight will
use the labels in the Exodus files. There is no
guarantee (particularly when using spatially
decomposed Exodus files) that these numbers are
unique over all the nodes and elements. If this
option is not set, EnSight will ignore the labels in
the Exodus file and use an internal numbering
scheme guaranteed to generate unique node and
element labels.
If the Environment Variable
ENSIGHT_EXODUS_USE_NODEMAPS is set
then the reader will use it to set the default value.

EnSight 9 User Manual

Verbose
Mode

If nonzero, enable verbose mode (off by default).
See the console for the verbose output. If the
Environment Variable
ENSIGHT_EXODUS_VERBOSE is set then the
reader will use it to set the default value.

Use higherorder
elements

Higher order elements will be preserved and not
down converted to simpler elements.

Ignore
constant
variables

Does not load single-value variables (called
Constants in EnSight).

NaN filter
input data

Check all floats for validity.

Clip
overlapping
timesteps

Restarts datasets that overlap in time use the later
datasets to construct the timeline

Autodetect
spatial
decomp

Automatically recognize all the files using one of
the files.

Use Undef
value for
missing vars

Use EnSight’s Undef value to indicate missing
variables

Ignore
element
attribute vars

Do not read/use element attribute variables.

2-55

2.3 EXODUS II Gold Reader

Use detected
DTA XML file

Use a specific XML formatted file to name parts
and assign attributes

Auto generate
DTA XML file

Auto generate this XML file and use it for part
naming.

Use full object
names

Long variable names.

Epsilon

Set to a temporal epsilon (default 1.0). This number
is used to adjust non-monotonically increasing
solution times. If the reader detects consecutive
solution times (as floats) that do not progress
forward in time, the later solution time value will
be set to the earlier time plus this value. Note: this
can have a cascading effect shifting other solution
times later as well. This feature is generally useful
when the solution times in the Exodus II file are all
the same value. If the Environment Variable
ENSIGHT_EPSILON is set, then the reader will
use it to set the default value.

Scale Factor

Set to a scaling factor (default 1.0). This number is
multiplied by each of the x, y, and z geometry
coordinates in order to scale the geometry. If the
Environment Variable
ENSIGHT_EXODUS_SCALE is set, then the
reader will use it to set the default value.

(see How To Read Data)

2-56

EnSight 9 User Manual

2.3 FAST UNSTRUCTURED Reader

FAST UNSTRUCTURED Reader
Overview

Simple Interface
Data Load
Advanced Interface
Data Load

FAST UNSTRUCTURED is a format containing triangle and/or tetrahedron
elements. The triangles have tags indicating a grouping for specific purposes.
EnSight will read the unstructured single zone grid format for this data type,
placing all tetrahedral elements into the first Part, and the various triangle element
groupings into their own Parts.
Load your grid file using the Simple Interface method.
Load your grid and solution files using the Advanced Interface method.
Data Tab
Format

Use the FAST Unstructured format.

Set grid

Select the grid file and click this button. This is the FAST
UNSTRUCTURED single zone grid file. Defines the geometry
as unstructured triangles and/or tetrahedrons.

Set solution

Select the solution file and click this button. The Results file
can either be a Modified Result file which utilizes a modified
EnSight results file format, or can be variable files (optional)
which are either a PLOT3D solution file (Q-file) or FAST
function file with I = number of points and J=K=1. The
modified EnSight results file provides access to multiple
solution files that are produced by time dependent simulations.
FAST UNSTRUCTURED data can have changing geometry.
When this is the case, the changing geometry file names are
contained in the results file. However, it is still necessary to
specify an initial geometry file name.
WARNING: Do not use your solution file (e.g. file.q) here. You
must create a special results file to handle FAST variable files.

Format Options Tab
Set measured
Part Loader

Select the measured file and click this button.

The FAST UNSTRUCTURED reader uses a simplified Part Loader as follows:
•

All Parts: all parts are loaded to the client in the
default visual representation (typically 3D
Border, 2D Full).

•

Part 1 Only: Only the first part is loaded to the
client in the default visual representation. The
other parts will have the NonVisual
representation.

•

All But Part 1: All parts other than part 1 are
loaded to the client in the default visual
representation. Part 1 will be NonVisual.

•

No Parts: No parts are loaded to the client (i.e.the
representation of all parts is set to NonVisual).

(see How To Read Data)

EnSight 9 User Manual

2-57

2.3 FIDAP NEUTRAL Reader

FIDAP NEUTRAL Reader
Overview
A FIDAP Neutral file contains all of the necessary geometry and result
information for use with EnSight.
A neutral file is produced by a separate procedure defined in the FIDAP
documentation. If the data is time dependent this information is also defined here.
Simple Interface
Data Load

Load your geometry/results file (typically named with a suffix .fdneut) using the
Simple Interface method.

Advanced Interface
Data Load

Load your geometry/results file (typically named with a suffix .fdneut) using the
Advanced Interface method.
Data Tab
Format

Use the FIDAP Neutral format.

Set geometry

Select the geometry/results file (typically .fdneut) and click
this button

Format Options Tab
Set measured
Part Loader

Select the measured file and click this button.

The FIDAP reader uses a simplified Part Loader as follows:
•

All Parts: all parts are loaded to the client in the
default visual representation (typically 3D
Border, 2D Full).

•

Part 1 Only: Only the first part is loaded to the
client in the default visual representation. The
other parts will have the NonVisual
representation.

•

All But Part 1: All parts other than part 1 are
loaded to the client in the default visual
representation. Part 1 will be NonVisual.

•

No Parts: No parts are loaded to the client (i.e.the
representation of all parts is set to NonVisual).

(see How To Read Data)

2-58

EnSight 9 User Manual

2.3 FLOW3D-MULTIBLOCK Reader

FLOW3D-MULTIBLOCK Reader
Overview
This EnSight reader uses the FLSGRF READER API LIBRARY from
FlowScience in order to read data from a FLOW3D "flsgrf" output data file,
which ends in .dat or in .fgz if compressed in their API.
Requirements

The FLSGRF API requires that the user have write permissions in the directory
where the flsgrf file resides.
THE FLSGRF API is only available for Windows 32-bit, 64-bit, Linux 32-bit, and
Linux 64-bit platforms.
The FLSGRF API is for FLOW3D version 9.2, however the FLSGRF API should
read flsgrf files written by older versions of FLOW3D.

Data Types

There are several kinds of data available in a FLOW3D flsgrf output file, each
with it’s own EnSight timeset: Restart, Selected, Fixed, and Particle data.

Restart data

By default, there are 11 restart timesteps per solution: t=0 and an additional ten
each spaced at 1/10th of the total simulation time. The user can change this
frequency in FLOW3D using the plotting interval (PLTDT) in the PREPIN input
file.

Selected data

This consists of selected variables output at a higher number of timesteps. Restart
and selected data can both be available in the data file.

Fixed time group

This data does not change over time. It consists of simulation parameters such as
binary flags used to activate physical models as well as mesh data.

Particle data

If particles are present in the simulation they will be present in the Restart data. If
the user requests particle information in the Selected data (from their project file
where anmtyp(i)='part') then particle information will also be available in the
Selected data timesets.
Particle data is not imported into EnSight by default. To import this data, Choose
the Multipart Flow3d reader then click on the Format Options Tab and select the
type of Particle data that you wish to import.
Geometry is STATIC in EnSight unless Particle data is imported and then the
geometry is CHANGING CONNECTIVITY because the number of particles can
change with each timestep.

Technical notes

All block part variable data is cell-based (per element data). All particle variable
data is node-based (per node data).
To visualize the fluid in the block try creating an isosurface of the Fluid Fraction
using an isosurface value of 0.51. Now to see the surrounding structure, make
another isosurface with a value of 0.51 using the Cell_Volume_Fraction_Fixed
variable. Click on the paint can icon and change your shading to smooth to
improve the isosurface look. To see the fluid as an isovolume, File>command and
type in ‘test: simple_isovolume_off’ then make an isovolume from 0.5001 to 1.0
using the Fluid Fraction and again change it’s shading to smooth.
To see detailed information about variables, blocks, boundary conditions, etc.
choose Console Output Debug as described below.
This reader makes use of Timesets. Each of the variable types has it's own
Timeset timeline and EnSight merges them all together. For details on using these

EnSight 9 User Manual

2-59

2.3 FLOW3D-MULTIBLOCK Reader

timesets see the advanced section of the Change Time Steps in the How To
Manual.
Ghost cells

Ghost cells are invisible elements that help EnSight to interpolate variable values.
For example, Ghost cells between blocks allow for a smooth transition of the
isosurface of the fluid surface at part block boundaries. Ghosts that are not used
have a zero value for the variable, and must be removed: removal of ghosts at a
symmetry surface allows for smooth mirroring of the part(s).

Updated info

$CEI_HOME/ensight92/src/readers/multi_flow3d/README.txt

Simple Interface
Data Load

Load your Flow3d file (typically named flsgrf.dat ) using the Simple Interface
method.

Advanced Interface
Data Load

Load your Flow3d file (typically named flsgrf.dat) using the Advanced Interface
method.

Table 1:
Data Tab
Format

Use the Flow3d-Multiblock format.

Set flsgrf

This field should be an flsgrf file.

Format Options Tab
Format
Options

Rename
Variables

2-60

Variables are renamed by default to be easier to interpret for
Flow3D users.

EnSight 9 User Manual

2.3 FLOW3D-MULTIBLOCK Reader

Table 1:
Include
Symmetry
Ghosts

Flow3d includes the following boundary conditions:
symmetry, wall, continuative, periodic, specified pressure,
specified velocity, grid overlay, outflow and interblock.
Ghost elements are always included in periodic, specified
pressure, and inter-block boundary conditions. Ghosts are
always removed for continuative, specified velocity, grid
overlay and outflow boundary conditions. Ghosts are optional
for symmetry and wall boundary conditions.
By default, symmetry ghosts are removed so that mirroring in
EnSight has no seam.
However toggling ON this flag will include the symmetry
ghosts for example for inviscid flow using the symmetry
condition to simulate a wall.

Include Wall
Ghosts

Flow3d includes the following boundary conditions:
symmetry, wall, continuative, periodic, specified pressure,
specified velocity, grid overlay, outflow and interblock.
Ghosts are always included in periodic, specified pressure, and
inter-block boundary conditions. Ghosts are always removed
for continuative, specified velocity, grid overlay and outflow
boundary conditions. Ghosts are optional for symmetry and
wall boundary conditions.
By default, wall ghosts are removed so that the EnSight fluid/
wall interface does not show up using the isosurface of the
fluid fraction.
However toggling ON this flag will cause the fluid/wall
interface to show up using the isosurface of the fluid fraction.

Particle Data

By default, particle data is not read into EnSight. Toggle this
ON to read in the Particle data.

Console
Output

EnSight 9 User Manual

2-61

2.3 FLOW3D-MULTIBLOCK Reader

Table 1:
Treat Ghosts

Ghost elements are invisible elements that help EnSight to
interpolate variable values. Ghosts can be read in as Ghost
cells, as normal (visible) cells, or they can be not read in at all.
1. Ghosts - include invisible ghost elements according to the
Flow3d boundary conditions (default) and user settings.
2. None - Use NO ghost elements. This will especially be
apparent in the gaps in the isosurface between data blocks due
to the lack of these invisible interpolating elements.
3. Normal - Use ALL ghost elements as NORMAL, visible
elements. This is useful for understanding boundary
conditions around part blocks.

Set measured

Select the measured file and click this button.

(see How To Read Data)

2-62

EnSight 9 User Manual

2.3 FLUENT Direct Reader

FLUENT Direct Reader
Overview
There are three methods to get Fluent data into EnSight. The first is to use the
current Fluent reader. This loads a Fluent Case (.cas) file and data (.dat) file. The
second method to get data into EnSight is to use Fluent’s EnSight Case Gold
Export option and read it directly into EnSight using the Case reader.The last
method is a little-used legacy reader for Fluent Universal file and is described
later under the FLUENT UNIVERSAL Reader.
See the following files for current information on the Fluent direct reader.
$CEI_HOME/ensight92/src/readers/fluent/README.txt

The comments that follow are for the current Fluent reader. The reader loads
ASCII, binary single precision, or binary double precision. The files can be
uncompressed or compressed using gzip. Note also, this reader is used to load
AIRPAK/ICEPAK .fdat data files (see AIRPAK/ICEPAK Reader) and .cdat (‘lite’
data file, or ‘extra CFD variables’ file).
Simple Interface
Data Load

Load your geometry file (typically named with a suffix .cas) using the Simple
Interface method.

Advanced Interface
Data Load

Load your geometry and result files (typically named with a suffix .cas and .dat)
using the Advanced Interface method.
Data Tab
Format

To use this reader, select the Fluent format.

Set cas

Select the geometry file (typically .cas or .cas.gz) and click
this button. For transient data, use *.cas or *.cas.gz. For the
old Fluent reader the asterisk must replace a 4-digit number.

Set dat

Select the results file (typically .dat or .dat.gz), and click this
button. For transient data, use *.dat or *.dat.gz . Note that
.cdat files (‘lite’ dat file, or an ‘extra CFD variables’ file) are
also useable in place of the .dat file. Finally .fdat files (see
Airpak / Icepak reader) are also useable in place of the .dat
file. Because the .dat file is the automatic selection, if a .dat
file is colocated with a .cdat or a .fdat file, the user will have to
manually select the .cdat or .fdat file and then click on the Set
dat button to use these .dat file variants.

Format Options Tab
Set measured

EnSight 9 User Manual

Select the measured file (typically a .mea suffix) and click this
button. If you have fluent particle data you can translate it into
EnSight’s measured data format and import the particles as
measured data.

2-63

2.3 FLUENT Direct Reader

Other
Options
using the
current
Fluent reader

2-64

Load Internal
Parts

Use Meta
Files

Load _M1
_M2 vars

Load all cell
types

EnSight 9 User Manual

2.3 FLUENT Direct Reader

Poly to
Regular Cell

Fluent polyhedral cells when composed of the correct kind and
number of regular faces can be converted to regular cells
(tetrahedrons, hexahedrons, pyramids, or wedges) boosting
EnSight speed and decreasing memory requirements. Toggle
ON and reader checks each polyhedron to see if it can be
converted to a regular cell (default) and OFF to not convert
any polyhedral cells. There is very little slowdown during the
read to do this and a big payoff for some datasets with large
numbers of convertible polyhedra. Leave it on.

Poly faced
Hex to Poly

Fluent hex cells that transition to a more refined hex mesh will
sometimes have one or more of the quad4 faces subdivided
into four quad4 faces. For example a hexahedral cell with one
transition face will have the six full faces, and four subdivided
faces for a total of 10 faces. Toggle ON and the the
subdivided faces are kept rather than the full face and the cell
is changed into a polyhedral which will slow down EnSight
performance, and greatly increase memory. The polyhedral
also will have hanging nodes (see the next toggle). Toggle
OFF (default) to convert the hex element to a six-sided hex
which will be adjacent to four smaller cells rather than
completely connected to them slowing down EnSight’s
adjacency searching. The default is thought to be the lesser of
two evils.

Fix Hanging
Nodes

Some Fluent polyhedral cells and all transition hex cells
converted to polyhedrals will have hanging nodes. A hanging
node not shared by at least 3 faces. A polyhedral element with
hanging nodes is not water tight and can cause real problems
in EnSight, so it is best to leave this toggle ON (default) and
only turn it OFF for experimental purposes.

Console
Output

Time Values

EnSight 9 User Manual

2-65

2.3 FLUENT Direct Reader
Node and Elem IDs

Parts have node and element ids to enable querying your data. Node ids are
created from the coordinate global node. Element ids are created as follows. Face
part elements are uniquely numbered according to their zone index. Cell part
elements are uniquely numbered using their zone index added to the total number
of faces. So a dataset with 100 face elements and 300 cell elements would have
the face elements number 1-100 and the cell elements numbered 101-400. In
Verbose mode, the element id range for each part are written to the console.

Variable Location

Variables that are cell-centered remain where they are found in the .dat file, that is
the reader does not interpolate the cell-centered variables to the nodes. Fluent can
export variable data to EnSight’s Case Gold format at either the nodes (default) or
at the elements (same as .dat file). Unfortunately older versions of Fluent export
variables averaged to the nodes leading to flow into and out of walls which causes
particles to stop prematurely and skews mass flow calculations. Later versions of
Fluent consider boundary conditions prior to averaging the data to the nodes,
yielding a much more realistic representation of the physics.

Variables
Undefined

Not all variables exist on all parts. If you select a part and color by a variable and
get undefined, then load the data using Verbose mode and take a look at the
console. Your variable is probably not defined for this part The EnSight reader
does not currently extrapolate data from the cells to faces. Create a clip on the
location of an interior part on a volume part if you want to see a plane with the
values from the volume.

Variable Names

Many variables that formerly were named improperly have been fixed. However
if you see a variable that is not named properly, send the variable number and
what it should be named to support@ensight.com and we will ask Fluent the
proper name and fix it.

Extra Variables

EnSight will try to calculate extra CFD variables given the existing DAT variables
for your convenience.

CAS Constants

Extra CAS Single Value Variables - A number of single value variables are read
from the CAS file(s). These will show up in the EnSight Calculator named as
follows.
'PRESSURE_ABS' - operating pressure (absolute)
'PRESSURE_ABS_INIT'- initial operating pressure (absolute)
'GAMMA_REF' - reference gamma, ratio of specific heats
'VISCOSITY_REF' - reference viscosity
'TEMPERATURE_REF' - reference temperature
'PRESSURE_REF' - reference pressure
'DENSITY_REF' - reference density
'SPEED_SOUND_FAR' - far field speed of sound
'PRESSURE_FAR' - far field relative pressure
'DENSITY_FAR' - far field density
'R_ref' - Calculated reference gas constant = PRESSURE_ABS /
(DENSITY_REF * TEMPERATURE_REF)
'V_def' - Calculated default velocity magnitude from x, y and z-velocity default
values
'M_def' - Calculated from V_def / SPEED_SOUND_FAR

2-66

EnSight 9 User Manual

2.3 FLUENT Direct Reader
UDS, UDM
Variables

UDM and UDS variables now read in as UDM_0, UDM_1, UDM_2... and
UDS_0, UDS_1, .... Fluent differentiates between UDS (User defined scalar) and
UDM (user defined memory) as follows.
A UDS is a scalar variable for which a transport equation can be solved (e.g.
transport of a red color from an injection nozzle into the volume; convective
terms, diffusive terms,..) The single terms of this transport equation are
programmed via UDF (user defined functions) in C and are run time libraries.
A UDM is a node-based value which also is calculated using a UDF (e.g.viscosity
against local temperature and density). For UDMs transport equations are not
solved. Thus they require less memory compared to UDS.
UDMs and UDSs are available for additional physics which are not available in
Fluent (for example one can use a UDM for the calculation of dust concentration
in filter elements.

Polyhedral
elements

There are two methods to import polyhedral elements into EnSight. The first is to
try using the direct reader. This has the advantage that the direct reader will
attempt to convert polyhedral elements back to regular elements, saving memory
and speeding up EnSight. The second is to export EnSight Case Gold from
Fluent. Case Gold has the advantage of currently supporting automatic Server of
Server decomposition, which can distribute the many tasks to multiple servers and
speed up post processing.

Periodic elements

The reader now supports rotational symmetry to provide continous boundaries.

Particles

Included with EnSight is a Fluent particle file translator to translate the Fluent
.part file into an EnSight measured (.mea) data file. To get help with this
translator, type
$CEI_HOME/ensight92/machines/$CEI_ARCH/flupart -h

where $CEI_ARCH is your hardware/OS architecture (e.g. linux_2.6_64 or
apple_10.5, win32, etc.).
Source code and README for this translator are located
$CEI_HOME/ensight92/translators/fluent/Particles/

This measured data file is entered in the the measured data field under the Format
Options tab of the data reader dialog.
(see How To Read Data)

EnSight 9 User Manual

2-67

2.3 FLUENT UNIVERSAL Reader

FLUENT UNIVERSAL Reader
Reader Visibility
Flag

This is not the preferred reader for Fluent data. Therefore, by default, this reader is
not loaded into the list of available readers. The preferred reader for Fluent data is
the Fluent Direct Reader. If you have Universal file data, you can enable this
reader as follows: go into the Menu, Edit > Preferences and click on Data and
toggle on the reader visibility flag.
The FLUENT Universal file contains all of the necessary geometry and result
information for use with EnSight for a steady-state case. If the case is transient,
EnSight needs a Universal file for each time step of the analysis and a modified
version of the EnSight results file.

Simple Interface
Data Load

Load your geometry/results file (typically named with a suffix .univ or .fluniv)
using the Simple Interface method.

Advanced Interface
Data Load

Load your geometry/results file (typically named with a suffix .univ or .fluniv)
using the Advanced Interface method.
Data Tab
Format

Use the Fluent Universal format.

Set universal

Select the universal file (typically .univ or .fluniv) and click
this button

Format Options Tab
Set measured
Part Loader

Select the measured file and click this button.

The Fluent Universal reader uses a simplified Part Loader as follows:
•

All Parts: all parts are loaded to the client in the
default visual representation (typically 3D
Border, 2D Full).

•

Part 1 Only: Only the first part is loaded to the
client in the default visual representation. The
other parts will have the NonVisual
representation.

•

All But Part 1: All parts other than part 1 are
loaded to the client in the default visual
representation. Part 1 will be NonVisual.

•

No Parts: No parts are loaded to the client (i.e.the
representation of all parts is set to NonVisual).

(see How To Read Data)

2-68

EnSight 9 User Manual

2.3 Inventor Reader

Inventor Reader
Overview
Reads inventor (.iv) datasets for which there is a one-to-one correspondence in
Part, coordinate index, geometry index and element record. That is, there is one
set of coordinates, one geometry, one set of elements per inventor node. To read
in one inventor file, enter the .iv filename.
To read in multiple .iv files us a Case Inventor file (.civ). The user has the option
in the reader Format Options Tab to toggle off one part per file option (default on).
The .civ file is an ASCII file with the number of files on the first line, and the
filenames on the remaining. The filenames must be in quotes, and if they don't
include the path, the .civ file must be in the directory where the files are located. A
'.civ' filename cannot be in a '.civ' file: only '.iv' filenames are allowed.
Example Format:
numfiles: 2
"filename1.iv"
"filename2.iv"
For more info, see
$CEI_HOME/ensight92/src/readers/inventor

Data Reader
Main Menu > File > Data (reader)...

The File Selection dialog is used to specify which files you wish to read.
Access: Main Menu > File > Data (Reader)...
Simple Interface
Data Load

Load your geometry/results file (typically named with a suffix .iv or .civ) using
the Simple Interface method.

Advanced Interface
Data Load

Load your geometry/results file (typically named with a suffix .iv or .civ) using
the Advanced Interface method.
Data Tab
Format

Use the Inventor format.

Set .iv file

Select the inventor file (typically .iv or .civ) and click this
button

Format Options Tab
One Part per
file

EnSight 9 User Manual

Makes one part out of each file.

2-69

2.3 Inventor Reader

Console
Output

Use this flag to determine the amount of output to the console.
Normal - Usually only echo errors echoed to console.
Verbose - Normal plus high level output describing dataset and
progress while reading
Debug - Detailed output and progress through the reader
routines often valuable for understanding and reporting
problems.

Set measured

Select the measured file and click this button.

(see How To Read Data).

2-70

EnSight 9 User Manual

2.3 LS-DYNA Reader

LS-DYNA Reader
Overview
The LS-DYNA reader reads in a single or multiple unstructured C-binary d3plot files.
It supports bars, quads, bricks and thick shell elements.
Key File for Part
Naming

Limitations

Can use of Key file to name parts as follows:
a. Works only if Material IDs are in the d3plot file
b. Put key file name into Params field
c. Looks for *PART keyword in keyfile
d. '$' in first column is a comment in keyfile
e. First non-comment line after *PART is used as partname if alpha or digit
f. Second non-comment line after *PART, 3rd integer is Material ID
g. If Mat'l ID in d3plot matches Mat'l ID in keyfile partname from key file is
substituted for Material ID in EnSight name.
The reader has the following limitations.
Doesn't support PACKED data (3 integers per word)
Skips over Smooth Particle Hydrodynamics Node data
Skips over Rigid Road Surface Data.
Skips over Computational Fluid Dynamics Data.
Does not read in LS-DYNA time-history plots
Coordinate System: Global vs. Local: Beam stresses and strains are always
output in the local r,s,t system. Per LSTC manual, stresses and strains of the other
elements are generally in the global system. However, shells & thick shells have
an option to output in local system (see LS-DYNA 960 keyword users manual
page 9.18. flag CMPFLG). The reader has no way of knowing whether stresses
and strains are output in the global or local system and just shows the values
contained in the files.
See the following file for current information on this reader.
$CEI_HOME/ensight92/src/readers/ls-dyna3d/README

EnSight 9 User Manual

2-71

2.3 LS-DYNA Reader

Data Reader
Simple Interface
Data Load

Load your d3plot file using the Simple Interface method.

Advanced Interface
Data Load

Load your d3plot file using the Advanced Interface method.
Data Tab
Format

Use the LS-DYNA3D format.

Set d3plot

This field should have the first d3plot file name. All of the
d3plot files will be loaded starting with this first one

Set key

This field can be used to import parameters that modify the
behavior of the reader, or the Extra GUI section can be used to
choose which ids to use for naming and to name the keyfile
respectively.
keyfilename - Type the keyfile name into this field
-mid - use material id in keyfile to name parts in d3plot file.
-pid - use part id in keyfile to name parts in d3plot file.

example:
file.key -mid
This will use the material ids in keyfile named file.key to name
parts.
Format Options Tab
Set measured

Select the measured file and click this button.

Format
Options

The following options are customized for the reader:

Remove Failed Elems - Toggle on to remove failed elements
Keyfile IDs - This pulldown provides the choice of either
Material IDs or Part IDs from the keyfile to be used for part
naming. Alternatively, the ID can be specified in the (Set)
Params field as described above.
Console Output - Can control amount of output that comes to
the console. Options are: Normal, Verbose, or Debug
ASCII File Inpt - Can input glstat, abstat, matsum, rcforc,
rwforc, nodout, secforc, sleout, elout xy ascii files.
(see How To Read Data)
2-72

EnSight 9 User Manual

2.3 Movie.BYU Reader

Movie.BYU Reader
Reader Visibility
Flag

By default, this reader is not loaded into the list of available readers. To enable
this reader go into the Menu, Edit > Preferences and click on Data and toggle on
the reader visibility flag.

Overview
Movie.BYU has a general n-sided polygon data format. In translating this format
to the element-based EnSight data format, not all elements possible in the
Movie.BYU format can be converted to EnSight format. However, for most
practical cases there are no problems.
Movie.BYU data can have changing geometry. When this is the case, the
changing geometry file name patterns are found in the results file. However, it is
still necessary to specify an initial geometry file name in the (Set) Geometry field.
Simple Interface
Data Load

Load your geometry file (typically named with a suffix .geo) using the Simple
Interface method.

Advanced Interface
Data Load

Load your geometry and result files (typically named with a suffix .geo and .res)
using the Advanced Interface method.
Data Tab
Format

Use the Movie BYU format.

Set geometry

Select the geometry file (typically .geo) and click this button

Set results

Select the results file (typically .res), and click this button.

Format Options Tab
Set measured
Part Loader

Select the measured file and click this button.

The reader uses a simplified Part Loader as follows:
•

All Parts: all parts are loaded to the client in the
default visual representation (typically 3D
Border, 2D Full).

•

Part 1 Only: Only the first part is loaded to the
client in the default visual representation. The
other parts will have the NonVisual
representation.

•

All But Part 1: All parts other than part 1 are
loaded to the client in the default visual
representation. Part 1 will be NonVisual.

•

No Parts: No parts are loaded to the client (i.e.the
representation of all parts is set to NonVisual).

(see How To Read Data)

EnSight 9 User Manual

2-73

2.3 MPGS 4.1 Reader

MPGS 4.1 Reader
Reader Visibility
Flag

MPGS is considered a legacy format. Therefore, by default, this reader is not
loaded into the list of available readers. To enable this reader go into the Menu,
Edit > Preferences and click on Data and toggle on the reader visibility flag.

Overview
MPGS4.x uses a general n-sided polygon, n-faced polyhedral data format. In
going from this format to the specific element data format of EnSight, you
encounter the problem associated with translating from a general format to a
specific format. Not all elements possible in MPGS4.x can be converted to
EnSight format. However, there will not be a problem in most situations.
MPGS4.x models of modest size can be read directly into EnSight. Size can
become an issue since the amount of memory needed to do the conversion in
EnSight to the internal data format in a reasonable length of time can become
excessive for large models.
MPGS4.x data can have changing geometry. When this is the case, the changing
geometry file name patterns are contained in the results file. However, it is still
necessary to specify an initial geometry file name in the (Set) Geometry field.
Simple Interface
Data Load

Load your geometry file (typically named with a suffix .geo) using the Simple
Interface method.

Advanced Interface
Data Load

Load your geometry and result files (typically named with a suffix .geo and .res)
using the Advanced Interface method.
Data Tab
Format

Use the MPGS 4.1 format.

Set geometry

Select the geometry file (typically .geo) and click this button.
The MPGS Geometry file defines all geometric model Parts in a
general n-sided polygon format.

Set results

Select the results file (typically .res), and click this button.

Format Options Tab
Set measured
Part Loader

Select the measured file and click this button.

The MPGS reader uses a simplified Part Loader as follows:
•

All Parts: all parts are loaded to the client in the
default visual representation (typically 3D
Border, 2D Full).

•

Part 1 Only: Only the first part is loaded to the
client in the default visual representation. The
other parts will have the NonVisual
representation.

•

All But Part 1: All parts other than part 1 are
loaded to the client in the default visual
representation. Part 1 will be NonVisual.

•

No Parts: No parts are loaded to the client (i.e.the
representation of all parts is set to NonVisual).

(see How To Read Data)

2-74

EnSight 9 User Manual

2.3 MSC.DYTRAN Reader

MSC.DYTRAN Reader
Overview
Reads archive files ".ARC" directly, a modified case file, or a .dat file (which is
the preferred method).
See the following file for current information on this reader.
$CEI_HOME/ensight92/src/readers/dytran/README
Simple Interface
Data Load

Load your dytran file (typically named with a suffix .dat or .arc) using the Simple
Interface method.

Advanced Interface
Data Load

Load your dytran file (typically named with a suffix .dat or .arc) using the
Advanced Interface method.
Data Tab
Format

Use the MSC/Dytran format.

Set dytran

This field should have the .dat or .arc suffix. Selecting any one
file will read only that file. Inserting wild card characters, such
as '*' and '?', will cause all files of a set to be read. For
example, if I enter CONTAINER_EUL_*.ARC, the program
will matches the pattern to all the files below.

Format Options Tab
Set measured

Select the measured file and click this button.

(see How To Read Data)

EnSight 9 User Manual

2-75

2.3 MSC.MARC Reader

MSC.MARC Reader
Overview
Reads a t16 or t19 file (which is the preferred method).
See the following file for current information on this reader.
$CEI_HOME/ensight92/src/readers/marc/README
Simple Interface
Data Load

Load your marc file (typically named with a suffix .t16 or .t19) using the Simple
Interface method.

Advanced Interface
Data Load

Load your marc file (typically named with a suffix .t16 or .t19) using the
Advanced Interface method.

Table 2:
Data Tab
Format

Use the MSC.Marc format.

Set t16/t19

This field should have the .t16 or .t19 suffix file.

Format Options Tab
Format
Options

Analysis data: Transient, Modal, Buckling. Please choose the
type of data to be read. The "Transient" option supports any
time-dependent result types (static, quasi-static and transient).
Gauss to node extrapolation: Shape functions. Currently only
one choice.
Averaging method: Average over all elements. Currently only
one choice.
Set measured
Features

Select the measured file and click this button.

1. Can read both t16 binary result files and t19 formatted result files
2. Supports most analysis types (structural, thermal, magnetic, etc.)
3. Supports results for nodes (scalar / vector) and gauss-points (scalar, vector and
tensor). Gauss point results are extrapolated to nodes and averaged at the nodes.
4. Handles remeshing (global and local) and element activation / de-activation.

2-76

EnSight 9 User Manual

2.3 MSC.MARC Reader

5. Can read results for DMP runs: If the main result file is selected, all domains
are imported. Domain result files can be selected individually
6. Can read static / transient results, modal results and buckling results.
7. Works on all Marc versions from Marc 2000 up to 2005r2.
8. Little-endian and Big-endian results are handled transparently. A message "Not
a native format file. May not work correctly!" will appear if the reader suspects it
is not in the native machine format, and automatic conversion will start.
9. For Buckling and Modal results, a variable called "Load_Factor" or
"Frequency" is created respectively that gives the mode frequency or buckling
load factor.
10. Ensight does not support the ability for the time to move backwards as the
Arc-length methods will make happen. When the reader detects time that moves
backwards at any point in the results file, the times will be reset to be 0., 1., 2. etc.,
and an extra variable "Time" will be created that contains the actual time.
11. Reader supplies Stress as a Tensor (when available in the data)
a. To calculate Principal Stress, use EnSight's TensorEigenvalue calculator
function
b. To calculate VonMises Stress, use EnSight's TensorVonMises calc function
Limitations

1. Cannot read pre Marc 2000 results.
2. Rigid contact bodies and their results are not read.
3. Flow line data is not used.
4. Springs and Tyings are not used.
5. Only time-dependent results (static and / or transient), modal or buckling
results can be read at a time. If more than one of these exist in a single result file,
only the one selected on the options form will be read.
6. No Mentat sets (or Patran groups) are imported.
7. The t19 (formatted) results files read much slower than t16 (binary) result files.
It is faster to convert a t19 file to t16 (by using the "pldump2000" executable that
is always installed with Marc) than read t19 files directly in Ensight.
(see How To Read Data)

EnSight 9 User Manual

2-77

2.3 MSC.NASTRAN Reader

MSC.NASTRAN Reader
Overview
Reads .op2 suffix files including most PDA Patran (PARAM POST = -1) and
SDRC I-DEAS (PARAM POST = -2) files.
Limitations

a) Binary format only. (If you need to read ASCII, convert using the Nastran
utility that will do this.)
b) Some non-linear and composite element types have not yet been implemented.

Recent
Enhancements

1. Extra GUI options were added to allow the user control over part creation and
variable extraction.
2. Location and displacement coordinate systems are now recognized and applied.
3. Multiple op2 files can be read by the reader, and thus will appear in the same
EnSight case. This is controlled by a simple ascii file (.mop file).
The format of the .mop file is:
---------------------------------line 1:
The word mop, in quotes
line 2:
The number of files
line 3 and up: Each op2 filename, in quotes
example:
---------mop
3
“boom.op2”
“bucket.op2”
“hframe_side.op2”
NOTE: The .mop file extension has been added to the Nastran reader section
of the ensight_reader_extension.map file (in site_preferences).
4. Rigid Body euler parameters are being read and passed to EnSight. (EnSight
has also been modified to apply these rigid body parameters to the geometry
and vector variables.) The specification of the rigid body file and the
registration of which parameters apply to what - is also done in the .mop
format.
The format of the .mop file, with rigid body information as well, is:
---------------------------------------------------------------------------line 1:
The word mop, in quotes
line 2:
The number of files
line 3 and up: Each op2 filename, the euler parameter filename, the title of the
rigid body transformation in the euler parameter file that apply to
this .op2 file, and a unit conversion scale factor (if needed). All
on one line per file, and all in quotes.
example:
---------mop
3
“boom.op2”
“bucket.op2”

2-78

“rigid.eet” “BOOM” “1000.0”
“rigid.eet” “BUCKET” “1000.0”
EnSight 9 User Manual

2.3 MSC.NASTRAN Reader

“hframe_side.op2” “motion.eet” “HFRAME” “1000.0”
NOTE: Since an euler parameter file contains the transformation information
for many different “parts”, the same file will generally be indicated for each
.op2 file. However, this can be a different file for each .op2 file.
Also, the last column is not required - but is provided in the case that unit
conversion is needed between the .op2 system and the euler parameter system.
In our example, the .op2 system was in millimeters, while the translations
values in the euler parameter file were given in meters.
NOTE: If there is an additional offset to the CG that is needed (other than that
specified in the euler parameter file), these offsets can also be placed in the
.mop file. Simply add three more columns containing the x, y, z offsets, like the
following:
example:
---------mop
3
“boom.op2”
“rigid.eet” “BOOM” “1000.0” “883.7” “207.4” “0.0”
“bucket.op2”
“rigid.eet” “BUCKET” “1000.0” “-10.5” “67.2” “7.89”
“hframe_side.op2” “rigid.eet” “HFRAME” “1000.0” “367.5” “-12.45” “0.0”
5. You can also add a rotation order and yaw, pitch, and roll values on each of the
file lines if the coordinate system needs to be re-oriented. These additional
columns follow the same format as those in the EnSight Rigid Body (.erb) file.
(see Section 11.13, EnSight Rigid Body File Format)

6. The reader deals with timelines and needed interpolations between them.
Generally, EnSight readers need only provide data at the given timesteps of a
model. EnSight takes care of getting both ends of a time span and interpolating
between them if needed. However, if rigid body motion is provided, the
controlling timeline will be the rigid body timeline. Thus, for a given rigid
body timestep, we may fall between timesteps for the nastran model. This
reader can interpolate properly for this situation.
Also, if not using rigid body, but are using multiple files - with different
timelines - a combined timeline will be created and sent to EnSight. This also
can require interpolation within the different files - and this is handled as well.
7. How variables are handled has been completely redone. The old reader simply
presented the values of whatever was in the file. This lead to many different
variables, depending especially on which element types were used. It also did
not assure that some of the standard variables were available.
This reader now presents a standard list of the component and principal
stresses/strains, and the useful failure theories. These values are obtained either
by reading them from the file (if provided), or computing them from the data
that is provided. We believe it is It is much more friendly and useful!.
8. Because of the way that element variable values now may lead to nodal
variables - requiring averaging, and because the way data is stored in a .op2 file
is not always conducive to being used efficiently by EnSight - various caching
schemes have been implemented to attempt to improve the efficiency of the
reader. Hopefully appropriate trade-offs between memory and speed have been
EnSight 9 User Manual

2-79

2.3 MSC.NASTRAN Reader

utilized. As such, it should be pointed out that one can color all parts by a
variable about as quickly as coloring only one.
9. Static models with multiple loadcases use the Solution Time dialog to switch
between loadcases. Thus, a “change of timestep” in EnSight will actually
change between loadcases.
NOTE: The preference within EnSight to have the Color Palette update at each
time step is especially nice to have set for this situation.
README

See the following file for current information on this reader.
$CEI_HOME/ensight92/src/readers/nastran/README.txt

Simple Interface
Data Load

Load your geometry/results file (typically named with a suffix .op2) using the
Simple Interface method.

Advanced Interface
Data Load

Load your geometry/results file (typically named with a suffix .op2) using the
Advanced Interface method.
Data Tab
Format

Use the Nastran OP2 format.

Set op2

Enter the .op2 filename if reading a single NASTRAN .op2
file, or a .mop filename if reading multiple .op2 files. The
.mop file is an ASCII file listing .op2 filenames. See the
description above or the README file indicated above for
more details.

Format Options Tab

2-80

Set measured

Select the measured file and click this button.

Extra GUI

The following parameters are available. They are described
below.

EnSight 9 User Manual

2.3 MSC.NASTRAN Reader
Extra GUI
Parameters

The toggles and fields below are customized for the Nastran OP2 reader. They allow the
user to specify basic options before the data is read. They may not all apply to any given
model.

Include 1D
elements

Toggle on to include any 1D (bar, rod, etc.) elements.

Include 2D
elements

Toggle on to include any 2D (tri, quad, etc.) elements.

Include 3D
elements

Toggle on to include any 3D (tet, hex, etc.) elements.

Rigid Body
Timeline Controls

Toggle on to have the geometry timeline controlled by the rigid body times (if
present). If off, the flex body times in the .op2 file will control.

Convert Modal
Freq to Time

Toggle on to compute solution time from the “frequency” field in the file for eigen
analysis (default is on). The is done with Time = (sqrt(freguency))/(2*PI). Toggle
off to no perform this computation and instead read the “frequency” value as the
time.

Elem Var:

This pulldown provides control over the way Nastran element values will be
presented as variables within EnSight.
Centroidal

produces per_elem variables from the value at each element centroid

Ave@Nodes

produces per_node variables, by averaging all vertex values at a given
node

Max@Nodes

produces per_node variables, by taking the maximum vertex value at a
given node

Min@Nodes

produces per_node variables, by taking the minimum vertex value at a
given node

Elem Var Type:

This pulldown provides the choice of extracting either Strain or Stress from
Nastran element values.

GridPt Var Type:

This pulldown provides the choice of extracting either Strain or Stress from
Nastran Grid Point values.

1D Bar loc:

This pulldown provides the choice of where along the bar (EndA, EndB) or across
the cross-section (Pts 1-4), and what type of stress or strain to extract from
Nastran bar elements.
Axial

EnSight 9 User Manual

Bend, EndA, Pt1

Combined, EndA, Pt1

Bend, EndA, Pt2

Combined, EndA, Pt2

Bend, EndA, Pt3

Combined, EndA, Pt3

Bend, EndA, Pt4

Combined, EndA, Pt4

Bend, EndB, Pt1

Combined, EndB, Pt1

Bend, EndB, Pt2

Combined, EndB, Pt2

Bend, EndB, Pt3

Combined, EndB, Pt3

Bend, EndB, Pt4

Combined, EndB, Pt4

2-81

2.3 MSC.NASTRAN Reader
2D Shell Fibre:

This pulldown provides the choice of which cross-sectional fibre (@Z1 or @Z2)
to extract from Nastran 2D Shell elements.

GridPt Surface loc:

This pulldown provides the choice of which cross-sectional fibre (@Z1, @Z2, or
@MID) to extract from Nastran 2D Grid Point surfaces.

Part Creation:

This pulldown provides part creation choices (which are most useful when a .mop
file is used to bring in multiple OP2 files together:

NX Nastran
Version:

2D Composite ply:

One Per File

One part for each file will be created. If a single OP2 file is being
read, all elements will be placed in a single part. If multiple OP2 files
are being read, one part per file will be produced.

By Property id

Parts will be created by property id. According to how property ids
were used in the OP2 file, this will generally create several parts per
file.

This pulldown provides the user with some control over the changes that occured
in the element record length at NX Nastran version 4.0. This is needed because
there is not a good way to determine the version used from the .op2 file itself.
Attempt to Detect

Attempts to divine the version number, but may not always work
correctly. If it can’t tell, will default to less than version 4.

Declare as >= 4.0

Declares the version to be 4.0 or greater, so doesn’t go through
the detection process.

This field allows the user to specify from which ply number to extract values from
Nastran 2D composite elements
(see How To Read Data)

2-82

EnSight 9 User Manual

2.3 Nastran Input Deck Reader

Nastran Input Deck Reader
Overview
Description

This reader will load Nastran input deck or bulk data files (typically .nas, .bdf,
.dat). These files contain the geometry for a Nastran run.

Usefulness

Being able to read this format allows for the display of the original Nastran
geometry for verification as well as for use with rigid body motion.

Usage

The Nastran input deck reader can read in and individual .nas/.dat/.bdf file, or it
can read in an exec file so that more than one file can be included in the same
case.

Limitations

The current reader does not deal with local coordinate systems and only
recognizes the following elements:
1D Elements

2D Elements

3D Elements

CBAR

CTRIA

CTETRA

CBEAM

CTRIAR

CPENTA

CROD

CTRIA6

CHEXA

CGAP

CTRIAX

CTUBE

CTRIA6X

CVISC

CQUAD

CONROD

CQUAD4

PLOTEL

CQUADR

RROD

CQUAD8

RBAR

CQUADX

CELAS1

CSHEAR

CELAS2
Simple Exec file
format

An exec file is used to read in multiple Nastran input deck files into one case. This
exec file is a very simple ascii file that must conform to the following:
1. All lines must begin in column 1
2. No blank or comment lines allowed
3. If the stl filenames begin with a "/", it will be treated as absolute path.
Otherwise, the path for the exec file will be prepended to the name given in the
file. (Thus, relative paths should work).
line 0:
[line 1:

numfiles: N
version #]

next N lines:

Example Simple
Exec file (without
version number)

EnSight 9 User Manual

(where N is the no. of files)
(optional line containing the
version number)
nasfilename1
. . .
. . .
nasfilenameN

numfiles: 3
CASTLE.DAT
bincastle.bdf
test.nas

2-83

2.3 Nastran Input Deck Reader
Example Simple
Exec file (with
version number)

numfiles: 3
version 1.1
CASTLE.DAT
bincastle.bdf
test.nas

Rigid Body Motion
Exec file

The reader includes the capability to link each input deck file with a rigid body
transformation file to allow the parts in each file to rigidly translate and rotate over time.
The rigid body motion Exec file has additional columns that contain the Euler Parameter
filename (see Section 11.14, Euler Parameter File Format), the transformation title in the
Euler Parameter file, and a units scale factor. The rigid body version of this Exec file
requires quotes as shown around the strings and values of the file lines.
example:
numfiles: 3
"CASTLE.DAT"
"bincastle.bdf"
"test.nas"

"motion.dat" "CASTLE" "1000.0"
"motion.dat" "BCASTLE" "1000.0"
"motion.dat" "TEST"
"1000.0"

And if an additional offset is needed to the CG, add these in 3 more columns
example:
numfiles: 3
"CASTLE.DAT"
"motion.dat" "CASTLE" "1000.0" "1.35" "2.66" "0.0"
"bincastle.bdf" "motion.dat" "BCASTLE" "1000.0" "-2.45" "1.0" "-2.0"
"test.nas"
"motion.dat" "TEST"
"1000.0" "60.2" "23.4" "0.0"

You can also add a rotation order and yaw, pitch, and roll values on each of the file lines if
the coordinate system needs to be re-oriented. These additional columns follow the same
format as those in the EnSight Rigid Body (.erb) file.
(see Section 11.13, EnSight Rigid Body File Format)
README

See the following file for current information on this reader.
$CEI_HOME/ensight92/src/readers/nas_input/README.txt

Simple Interface
Data Load

Load your geometry file (typically named with a suffix .nas, .bdf, or .dat) using
the Simple Interface method.

Advanced Interface
Data Load

Load your geometry file (typically named with a suffix .nas, .bdf, or .dat) using
the Advanced Interface method.
Data Tab
Format

Use the Nastran Input Deck format.

Set geometry

Select the geometry file (typically .nas, .bdf, or .dat) and
click this button

Format Options Tab
Set measured

Select the measured file and click this button.

(see How To Read Data)

2-84

EnSight 9 User Manual

2.3 N3S Reader

N3S Reader
Reader Visibility
Flag

Overview
Description

By default, this reader is not loaded into the list of available readers. To enable
this reader go into the Menu, Edit > Preferences and click on Data and toggle on
the reader visibility flag.
N3S is a data format developed by Electricité de France (EDF) consisting of a
geometry file and a results file. For this data format, both files are always
required. Versions 3.0 and 3.1 are both supported.
When reading N3S data into EnSight, you extract Parts from the mesh
interactively based on different color numbers or boundary conditions. The
available color numbers and boundary conditions for the model are presented.

Simple Interface
Data Load

Load your geometry file (typically named with a suffix .geo) using the Simple
Interface method.

Advanced Interface
Data Load

Load your geometry and result files (typically named with a suffix .geo and .res)
using the Advanced Interface method.
Data Tab
Format

Use the N3Sformat.

Set geometry

Select the geometry file (typically .geo) and click this button

Set results

Select the results file (typically .res), and click this button.

Format Options Tab
Set measured

Select the measured file and click this button.

N3S Part Creator dialog

Figure 2-12
N3S Part Creator dialog

You use the File Selection dialog to read in N3S dataset files. You use the N3S Part

EnSight 9 User Manual

2-85

2.3 N3S Reader

Creator dialog to extract Parts from a N3S dataset.
Access: Main Menu > File > Data (Reader)...> N3S
Create N3S Parts By
All Elements

Selection to create a Part using all of the elements available within the data file.

Color Number

Selection to create a Part according to the color number associated with each element.

Boundary
Information

Selection to create a Part according to specified conditions and codes.

Condition

Select boundary condition to use for Part creation.

Code

Select Code to use for boundary condition.

Part Descript

Specify name for Part.

Create Part

Click to create a Part. The Part is listed in the main Parts list of the Parts & Frames dialog
and is displayed in the Main View window.

(see How To Read Data)

2-86

EnSight 9 User Manual

2.3 OpenFOAM Reader

OpenFOAM Reader
Overview
Description

Reads OpenFOAM controlDict file found in modelname/system/controlDict.

Data Reader
Main Menu > File > Data (reader)...

The File Selection dialog is used to specify which file you wish to read.
Access: Main Menu > File > Data (Reader)...

Handles steady state geometry with either steady state or transient variables. Steady state
variables with multiple iterations will use each iteration as an EnSight timestep.
Not yet supported:
a. Changing coordinates or changing connectivity. Utilize the "foamToEnsight" translation
routine from OpenFOAM to convert the OpenFOAM data into EnSight Case Gold format.
b. Parallel files. Reconstruct the parallel files into a single, serial file using the
OpenFOAM utility 'reconstructPar' OpenFOAM.
c. Ongoing solution. The reader cannot handle newly available timesteps or iterations (for
example from an ongoing OpenFOAM solution) after the model has been read into
EnSight the first time. Should new iteration or timesteps become available after the model
was originally read into EnSight, the user must reload the dataset.
Command Line
Data Load

To automatically start EnSight and load the current directory’s OpenFOAM
dataset from the command line, type ‘ensight92 -Eensfoam’. This will trigger
EnSight to start up, look for the current directory’s “system/controlDict” file, and
automatically load the dataset into EnSight (using the default reader settings).
This reduces the number of steps to load the file into EnSight and thus the real
time required to load the data, and provides a level of integration with this data
format.

Sample Data

A sample OpenFOAM dataset is included as a sample session with your install.
To access the welcome screen, at the top menu choose Window>Welcome To...
and load the Dam Break example session. Or, to load the same dataset manually,
find the controlDict file in $CEI_HOME/ensight/other_data/openfoam .

Simple Interface
Data Load

Load your OpenFOAM controlDict file using the Simple Interface method. Or
from the command line, simply run ensfoam.

Advanced Interface
Data Load

Load your OpenFOAM file using the Advanced Interface method.
Data Tab
Format

Use the OpenFOAM format.

Set file

This field contains the controlDict file. Clicking button inserts
the file name shown into the field.

Format Options Tab
Set measured

EnSight 9 User Manual

Select the measured file and click this button.

2-87

2.3 OpenFOAM Reader

Other
Options

Include
ElemSet
Parts

Include any Element sets defined. These are sets of full
elements which are generally some logical subset of the total
number of elements. Default is on.

Include Face/
Edge Parts

Include any Face or Edge sets defined. These are some logical
set of particular faces and/or edges of full elements. Default is
on.

Include
NodeSet
Parts

Include local
elem res
comps (if
any)

Include the local stresses components, etc that are in the
elemen

Include
Tensor
derived
(VonMises,
etc.)

For tensor results, calculate scalars from the tensors.

Regular Part
Creation
Convention

Parts will be created according to the following:

Default is on

Default is off

Use Part Id - Part Id

(this is the default)

Use Property Id - Property Id
Use Material Id - Material Id

2-88

EnSight 9 User Manual

2.3 OpenFOAM Reader

Var naming
convention

Use DataSource field - By default variables are named using
the variable filename. For example, "U" is velocity, "p" is
pressure, etc.
Use Content Field (if provided) - Known variables are given
full, meaningful names, for example, "Velocity" or "Pressure".
Use VKI dataset name - Long, hybrid variable name that is
guaranteed to be unique, but perhaps cryptic.

Element Vars
as

If Sections,
which:

Not used

Section Num

Not used

(see How To Read Data)

EnSight 9 User Manual

2-89

2.3 OVERFLOW Reader

OVERFLOW Reader
Simple Interface
Data Load

Load your geometry file using the Simple Interface method.

Advanced Interface
Data Load

Load your geometry and result files using the Advanced Interface method.
Data Tab
Format

Use the OVERFLOW format.

Set geometry

Select the grid file (grid.in or single ‘x.’ file, e.g ‘x.14200’, see
details below) and click this button. This file is a structured
GRID file with FAST enhancements.

Set results

Select the results file and click this button. The Results File is
either a modified EnSight Results file (q.res) or standard plot3d
Q-file (q.save or single ‘q.’ file, e.g. ‘q.14200’). The standard
plot3d Q-file is a variable file for a single timestep and is
optional.
The modified EnSight results file directs the reader to handle
multiple grid (x.) files and/or multiple variable (q.) files from
transient simulations. If using a .res file, then enter only the
first ‘x.’ file into the set geometry field, and the ‘.res’ into the
set results field.
Note: The Q-file(s) (and result file) may be located in a
different directory than the grid file.

Format Options Tab

Extra Information

Set bounds

The optional boundary file defines boundary portions within
and/or across structured blocks. (Note: this can be EnSight’s
boundary file format or a .fvbnd file.)

Set measured

Select the measured file and click this button.

OVERFLOW reader extracts structured parts and iblanked unstructured parts
essentially the same way as PLOT3D, and as described in the basic structured
reader (see Reading and Loading Data Basics).
Additionally to successfully read OVERFLOW data, the following information
must be known about the data:
1. format - Fortran binary
2. whether single or multizone
3. dimension - 3D, 2D, or 1D
4. whether iblanked or not

2-90

EnSight 9 User Manual

2.3 OVERFLOW Reader

5. precision - single or double

Figure 2-13
Part Data Loader (PLOT3D)
used for OVERFLOW

EnSight attempts to determine these five settings automatically from the grid file.
The settings that were determined (for the first four) are shown in the Part Builder
dialog, where you can override them manually if needed. Note that OVERFLOW
data is restricted to only FORTRAN Binary format.
The precision setting is not reflected in the dialog, but is echoed in the Server shell
window. The q file precision will by default be set the same as that of the grid file.
In the rare case where the automatic detection is wrong for the grid file or the
precision is different for the q file than for the grid file, commands can be entered
into the Command dialog to manually set the precision.
test:
test:
test:
test:
Limitation

plot3d_grid_single
plot3d_grid_double
plot3d_qr_single
plot3d_qr_double

read grid file as single precision
to read grid file as double precision
to read q (or function) file as single precision
to read q (or function) file as double precision

In order to automatically recognize the data as Overflow, the files must have the
format ‘x.’ and ‘q.’ format (For example x.14000, x.14200, q.14000, and q.14200
would be appropriate filenames).
Note that the overflow reader can read in transient geometry files but these files
must have the same number of zones (EnSight parts) at each timestep. Each zone
can change in size (changing connectivity), but the total number of zones must
remain constant throughout time.

Example .res file

For example, if you have files x.14400 to x.16000 and q.14400 to q.16000, then an
example q.res file would be as follows. Then, put x.14400 into the set geometry
and q.res into set results field and you will have transient geometry and variables.
2 1 1
10
1.0 2.0 3.0
14400 200
x.*****
q.***** S 1
q.***** S 5
q.***** S 2

EnSight 9 User Manual

4.0 5.0 6.0 7.0 8.0 9.0 10.0

Density
Energy
3 4 Momentum

2-91

2.3 OVERFLOW Reader
OVERFLOW Q FIle
Variables

The variables of the flow information read by the OVERFLOW reader basically
conforms to those read by the PLOT3D reader, and includes additional flow
constants as well as additional Q variables such as γ and possible turbulance field
and species densities variables.
The 'Constant Variables' include (where the first 4 are the standard PLOT3D
constants):
FSMACH

ALPHA
RE
TIME

GAMinf

freestream Mach number Minf

angle-of-attack α
Reynolds number Re
= iteration (file) number (in OVERFLOW; in PLOT3D, time
value)
= freestream gamma γinf
=

sideslip angle β
= freestream temperature Tinf (in degrees Rankine)

BETA
Tinf

IGAM

variable gamma option where:
0 = use constant γ value of GAMinf
1 = Single gas with variation of γ with temperature
computed using LT_A0-4, UT_A0-4 below
2 = Two gases, with variation of γ with temperature
computed using LT_A0-4, UT_A0-4 below all gas 1
below HT1, all gas 2 above HT2, linear mix in
between.

HTinf

freestream stagnation enthalpy h0*inf

RefMACH

Tvref

DTvref

RGAS1
RGAS1_SMW

reference mach number (Note: in OVERFLOW “restart”
files only)
actual simulation time (Note: in OVERFLOW “restart”
files only)
delta simulation time (Note: in OVERFLOW “restart”
files only)
species gas constant 1
species gas constant 2

The 'Q-Field Scalars' include (where the first 4 are the standard PLOT3D Qvariables):
Density
Momentum

2-92

=
=

Q1-field variable = dimensionless density, ρ*
dimensionless momentum vector with:
Momentum[X] = Q2-field variable = x component of
Momentum ρ*u*
Momentum[Y] = Q3-field variable = y component of
Momentum ρ*v*
Momentum[Z] = Q4-field variable = z component of
Momentum ρ*w*

EnSight 9 User Manual

2.3 OVERFLOW Reader

Energy

Gamma_Q6_field =

And for SA model:
=
Q7_field
And for k-e model:
Q7_field, Q8_field =
Assigning
Analysis_Time

Q5-field variable = dimensionless total energy ρ*e0*
Q6-field variable = gamma γ (constant field, unless you
use the gamma option of the code)

Q7-field variable = turbulence variable

Q7-field and Q8-field variables which are the k and
epsilons

By default, the Analysis_Time constant variable value is assigned the time values
listed in the q.res file. (see Section 11.7, PLOT3D Results File Format). In order
to use the TIME (or Tvref - if using an OVERFLOW restart q.file) value located
in the header of the q-file(s), edit the q.res file:
a) change the total number of time steps to a negative value, and
b) remove the list of time values in the q.res file.

(see How To Read Data, and Section 11.7, PLOT3D Results File Format)

EnSight 9 User Manual

2-93

2.3 PLOT3D Reader

PLOT3D Reader
Example Source

See the following directory for an example User-defined source code
implementation this reader.
$CEI_HOME/ensight92/src/readers/plot3d/

Simple Interface
Data Load

Load your geometry file using the Simple Interface method.

Advanced Interface
Data Load

Load your geometry and result files using the Advanced Interface method.
Data Tab
Format

Use the PLOT3D format.

Set geometry

Select the grid file and click this button. This file is a structured
GRID file with FAST enhancements.

Set results

Select the results file and click this button. The Results File is
either a modified EnSight Results file or standard plot3d Q-file.
Variable files (optional) are solution (PLOT3D Q-files) or
function (FAST) files. The modified EnSight results file
provides access to multiple solution files that are produced by
time dependent simulations.

Format Options Tab

Extra Information

Set bounds

The optional boundary file defines boundary portions within
and/or across structured blocks. (Note: this can be EnSight’s
boundary file format or a .fvbnd file.)

Set measured

Select the measured file and click this button.

PLOT3D reader extracts structured parts and iblanked unstructured parts
essentially the same way as described in the basic structured reader (see Reading
and Loading Data Basics).
Additionally to successfully read PLOT3D data, the following information must
be known about the data:
1. format - ASCII, C binary, or Fortran binary
2. whether single or multizone
3. dimension - 3D, 2D, or 1D
4. whether iblanked or not
5. precision - single or double

Figure 2-14
Part Data Loader (PLOT3D)

2-94

EnSight 9 User Manual

2.3 PLOT3D Reader

EnSight attempts to determine these five settings automatically from the grid file.
The settings that were determined (for the first four) are shown in the Part Builder
dialog, where you can override them manually if needed.
The precision setting is not reflected in the dialog, but is echoed in the Server shell
window. The q (or function) file precision will by default be set the same as that of
the grid file. In the rare case where the automatic detection is wrong for the grid
file or the precision is different for the q (or function) file than for the grid file,
commands can be entered into the Command dialog to manually set the precision.
test:
test:
test:
test:
Assigning
Analysis_Time

plot3d_grid_single
plot3d_grid_double
plot3d_qr_single
plot3d_qr_double

read grid file as single precision
to read grid file as double precision
to read q (or function) file as single precision
to read q (or function) file as double precision

By default, the Analysis_Time constant variable value is assigned the time values
listed in the q.res file. (see Section 11.7, PLOT3D Results File Format). In order
to use the TIME value located in the header of the q-file(s), edit the q.res file:
a) change the total number of time steps to a negative value, and
b) remove the list of time values in the q.res file.

(see How To Read Data)

EnSight 9 User Manual

2-95

2.3 RADIOSS Reader

RADIOSS Reader
Overview
Description

Reads Radioss 4.x ANIM files.

Data Reader
Main Menu > File > Data (reader)...

The File Selection dialog is used to specify which files you wish to read.
Access: Main Menu > File > Data (Reader)...
Simple Interface
Data Load

Load your radioss file using the Simple Interface method.

Advanced Interface
Data Load

Load your radioss file using the Advanced Interface method.
Data Tab
Format

Use the RADIOSS_4.x format.

Set anim

This field contains the first Radios file name in the series.
Clicking button inserts file name shown into the field. File
name can then be modified with an asterisk “*” or question
mark “??” to indicate the unique identifiers in the file series.

Format Options Tab
Set measured

Select the measured file and click this button.

(see How To Read Data)

2-96

EnSight 9 User Manual

2.3 POLYFLOW Reader

POLYFLOW Reader
Overview
Description

Reads Polyflow .msh and .res files.

Data Reader
Main Menu > File > Data (reader)...

The File Selection dialog is used to specify which files you wish to read.
Access: Main Menu > File > Data (Reader)...
Simple Interface
Data Load

Load your Polyflow file using the Simple Interface method.

Advanced Interface
Data Load

Load your Polyflow file using the Advanced Interface method.
Data Tab
Format

Use the Polyflow format.

Set .msh

This field contains the mesh file. Clicking button inserts .msh
file name shown into the field.

Set .res

This field contains the result file.

Format Options Tab
Set measured

Select the measured file and click this button.

Other
Options

Include
ElemSet
Parts

EnSight 9 User Manual

Include any Element sets defined. These are sets of full
elements which are generally some logical subset of the total
number of elements. Default is on.

2-97

2.3 POLYFLOW Reader

Include Face/
Edge Parts

Include any Face or Edge sets defined. These are some logical
set of particular faces and/or edges of full elements. Default is
on.

Include
NodeSet
Parts

Include local
elem res
comps (if
any)

Include the local stresses components, etc that are in the
elemen

Include
Tensor
derived
(VonMises,
etc.)

For tensor results, calculate scalars from the tensors.

Regular Part
Creation
Convention

Parts will be created according to the following:

Default is on

Default is off

Use Part Id - Part Id

(this is the default)

Use Property Id - Property Id
Use Material Id - Material Id

Var naming
convention

Use Content Field (if provided) - Variable names will be what
is in the Content field, if provided. If not provided, they will
be the VKI dataset name. This is the default.
Use VKI dataset name - Variable names will be the VKI
variable dataset name (which are reasonably descriptive).

Element Vars
as

If Sections,
which:

Not used

Section Num

Not used

(see How To Read Data)

2-98

EnSight 9 User Manual

2.3 SDRC Ideas Reader

SDRC Ideas Reader
Overview
Description

Reads SDRC/Ideas Universal files in Ascii and Binary format. Select the .unv file
and select "SDRC/Ideas" in the format pulldown on the Advanced reader tab.

Data Reader
Main Menu > File > Data (reader)...

The File Selection dialog is used to specify which files you wish to read.
Access: Main Menu > File > Data (Reader)...

Simple Interface
Data Load

You cannot use the Simple Interface method to load your SDRC Ideas data
because the .unv extension is used by other formats.

Advanced Interface
Data Load

You must load your SDRC Ideas .unv file using the Advanced Interface method.
Data Tab
Format

Use the SDRC Ideas format.

Set file

This field contains the first file name. For the first file you
should choose a file with extension .unv. Clicking button
inserts file name shown into the field. Loading the .unv file
will load both geometry and results.

Format Options Tab
Set measured

Select the measured file and click this button.

Other
Options

Include
ElemSet
Parts

EnSight 9 User Manual

Include any Element sets defined. These are sets of full
elements which are generally some logical subset of the total
number of elements. Default is on.

2-99

2.3 SDRC Ideas Reader

Include Face/
Edge Parts

Include any Face or Edge sets defined. These are some logical
set of particular faces and/or edges of full elements. Default is
on.

Include
NodeSet
Parts

Include local
elem res
comps (if
any)

Include
Tensor
derived
(VonMises,
etc.)

2-100

EnSight 9 User Manual

2.3 SDRC Ideas Reader

Regular Part
Creation
Convention

Parts will be created according to the following:
Use Part Id - Part Id

(this is the default)

Use Property Id - Property Id
Use Material Id - Material Id

Var naming
convention

Element Vars
as

If Sections,
which:

Section Num

If the previous option is chosen to be Section Num, then the
value in this field is the 1-based section number to use to
create the variable.

(see How To Read Data)

EnSight 9 User Manual

2-101

2.3 SILO Reader

SILO Reader
Overview
Description

The Silo reader can read .silo files directly or can read them using a Casefile
which lists the geometry variable filenames, the timesteps and the constants all in
one ASCII file. The .silo file contains both the geometry and the results.

Library

The Silo reader requires the Silo library version 4.2 or later. For information on
Silo please see the following website:
http://www.llnl.gov/bdiv/meshtv/software.html

SILO Casefile
format

The User Defined SILO Reader reads a restricted version of the EnSight Gold
ASCII casefile as described below.
1. FORMAT
type: - "silo" required
2. GEOMETRY
model:
3. VARIABLE
constant per case:
4. TIME
(But only one of these!!!!)
number of steps: - required
time values:
- required
# Use the following if transient and
#
evenly spaced values
filename start number:
filename increment:
# Use the following if transient and
#
list all values
filename numbers:
5. All commands and options must start in first
column. However, A space, newline, or # can
be used in first column to indicate a comment
line.
The following examples could be read by the user defined ensight gold reader
Example 1: A static model
------------------------FORMAT
type:
silo
GEOMETRY
model:
example1.silo
VARIABLE
constant per case:
Density
TIME
number of steps:
1
time values:
0.0

2-102

EnSight 9 User Manual

2.3 SILO Reader

The following files would be needed for Example 1:
example1.silo
Example 2: A transient model
---------------------------FORMAT
type:
silo
GEOMETRY
model:
example2.*.silo
change_coords_only
VARIABLE
constant per case:
Density
.5
constant per case:
Modifier
1.0 1.01 1.025 1.04
1.055
TIME
number of steps:
5
time values:
.1 .2 .3 .4 .5
filename start number: 1
filename increment:
2
The following files would be needed for Example 2:
example2.1.silo
example2.3.silo
example2.5.silo
example2.7.silo
example2.9.silo
README

See the following file for current information on this reader.
$CEI_HOME/ensight92/src/readers/silo/README.txt

Simple Interface
Data Load

Load your silo file (typically named with a suffix .silo or .pdb or .case) using the
Simple Interface method.

Advanced Interface
Data Load

Load your silo files (typically named with a suffix .silo or .pdb or .case) using the
Advanced Interface method.
Data Tab
Format

Use the Silo format.

Set file

This field should have the Silo Case file name or the .silo file.

Format Options Tab
Set measured

Select the measured file and click this button.

(see How To Read Data)

EnSight 9 User Manual

2-103

2.3 STAR-CD and STAR-CCM+ Reader

STAR-CD and STAR-CCM+ Reader
Overview
Description

This reader reads .ccm, .ccmg (static geometry), .ccmp (variable), .ccmt (transient
variable) data exported from STAR-CD version 4.x or STAR-CCM+.

Export Case Gold

STAR-CD version 3.x, STAR-CD version 4.x and STAR-CCM+ all export the
native format of EnSight (EnSight Case Gold). Prostar exports to EnSight Case
Gold Format. Use the 'automatic' export found with the NavCenter to export all
parts and all primary variables. Use the Prostar command line to export separate
parts, and/or any variable or combination of calculated variables. Both Steady
State and Transient Models can be exported in a similar manner, with options of
"automatic", or user controlled. The Case Gold format is likely to be more
efficient, robust and faster in EnSight.

Read .sim file

This reader does not support .sim files written by STAR-CCM+. The .sim file
should be translated using STAR-CCM+ into EnSight Case Gold.

Read Version 3 file

This reader does not support output from STAR-CD version 3.x. This data should
be translated using Prostar into EnSight Case Gold.

Transient geometry

This reader does not support transient geometry. Transient geometry data must be
exported to EnSight Case Gold.

Particle data (.trk)

Particle data is contained in the .trk file, which was formerly a File.33 file. The
EnSight install includes a source file which can be compiled and run to translate
the .trk (or File.33) file into EnSight’s measured data format, which can be
loaded together with the .ccm file (as described below), or the EnSight .case file
can be edited to include the measured file name and it will automatically load.
The source file to the translator is found in the following location:
$CEI_HOME/ensight92/translators/starcd_file33
There is a README that guides you through compiling and using the translator. If
you have difficulty with this, contact support@ensight.com and we will supply
you with a compiled version for your hardware/OS. If you are using the translator
and have a case gold format file, the translator will automatically edit the case file
so that input of the measured data is automatic when your case file is loaded into
EnSight. If you are using this reader and a .ccm file, then choose the EnSight 5
option and you will get a .res file that you can use to load in the measured data
field described below.

Data Reader
Main Menu > File > Data (reader)...

The File Selection dialog is used to specify which files you wish to read.
Access: Main Menu > File > Data (Reader)...

Simple Interface
Data Load

2-104

Load your .ccm file using the Simple Interface method.

EnSight 9 User Manual

2.3 STAR-CD and STAR-CCM+ Reader
Advanced Interface
Data Load

Load your STAR-CCM file using the Advanced Interface method.
Data Tab
Format

Use the STAR-CD CCM format.

Set file

This field contains the first file name. For the first file you
should choose the file with extension .ccm, .ccmg, or .ccmp.
Clicking button inserts file name shown into the field. The
.ccmg file contains geometry only and the geometry must be
static. Loading a .ccm or .ccmp file will load both geometry and
results. .

Set .ccmt

For a time varying variable data, set the .ccmt file using this
field. This is only transient variable data.

Format Options Tab
Set measured

Select the measured file and click this button. This can be the
measured file obtained from the File.33 or the .trk file using
the EnSight translator (see above).

Other
Options

EnSight 9 User Manual

Include
ElemSet
Parts

Include any Element sets defined. These are sets of full
elements which are generally some logical subset of the total
number of elements. Default is on.

Include Face/
Edge Parts

Include any Face or Edge sets defined. These are some logical
set of particular faces and/or edges of full elements. Default is
on.

Include
NodeSet
Parts

2-105

2.3 STAR-CD and STAR-CCM+ Reader

Include local
elem res
comps (if
any)

Include the local stresses components, etc that are in the
elemen

Include
Tensor
derived
(VonMises,
etc.)

For tensor results, calculate scalars from the tensors.

Regular Part
Creation
Convention

Parts will be created according to the following:

Default is on

Default is off

Use Part Id - Part Id

(this is the default)

Use Property Id - Property Id
Use Material Id - Material Id

Var naming
convention

Use Content Field (if provided) - Variable names will be what
is in the Content field, if provided. If not provided, they will
be the VKI dataset name. This is the default.
Use VKI dataset name - Variable names will be the VKI
variable dataset name (which are reasonably descriptive).

Element Vars
as

If Sections,
which:

Not used

Section Num

Not used

(see How To Read Data)

2-106

EnSight 9 User Manual

2.3 STL Reader

STL Reader
Overview
Description

Reads .ccm files exported from STAR-CCM and STAR-CCM+.
Note: There is no longer an EnSight STL reader. this format is now read using the
CAD reader.

Overview
Description

This reader will load STL files (either ASCII or binary). Note that STL files
consist only of surfaces (triangles) and have no associated variables.

Usefulness

STL geometry format is widely compatible with a number of codes. Multiple STL
files geometries can be created to represent scenery or background, then read in
and scaled (using the -scaleg option) as a separate case to add to the presentation
of your existing model results in EnSight.

Usage

The STL reader can read in an individual .stl file, or it can read in an exec file so
that more than one stl file can be included in the same case.

Limitations

The current reader does not allow the coloring of each facet, nor does it allow
coloring of each part, and just skips over color statements in the file.

STL binary file
format

If the file is a binary STL (.stl) file, then it must contain exactly one part.

STL ASCII file
format

If the file is an ASCII STL (.stl) file, then it can contain one or multiple parts. If
you wish to read in multiple files
Single file multipart ASCII format is as follows:
solid part1
...
endsolid part1
solid part2
...
endsolid part2

Simple Exec file
format

An exec file (.xct) is used to read in multiple STL files into one case. Because
binary STL can contain only one part, if you wish to read in more than one binary
STL file into a single case, then you must use an exec file. ASCII STL files with
one or multiple parts can be read in to a single case using the exec file. An exec
file can read in binary and ASCII files together into a single case. This exec file is
a very simple ascii file that must conform to the following:
1. All lines must begin in column 1
2. No blank or comment lines allowed
3. If the stl filenames begin with a "/", it will be treated as absolute path.
Otherwise, the path for the exec file will be prepended to the name given in the
file. (Thus, relative paths should work).
line 0:
numfiles: N
line 1-n: stlfilename1
. . .
. . .
stlfilenameN

EnSight 9 User Manual

(where N is the no. of files)

2-107

2.3 STL Reader
Example Simple
Exec file

numfiles: 3
CASTLE.STL
bincastle.stl
test.slp

Rigid Body Motion
Exec file

Release 2.1 of the STL reader includes the added ability to link each STL part with a rigid
body transformation file to allow the STL part to rigidly translate and rotate over time.
The rigid body motion Exec file has additional columns that contain the Euler Parameter
filename (see Section 11.14, Euler Parameter File Format), the transformation title in the
Euler Parameter file, and a units scale factor (This is used to scale the translations, not the
geometry. Scaling of the geometry is accomplished in the Part Feature Detail Editor.). The
rigid body version of this Exec file requires quotes as shown around the strings and values
of the file lines.
example:
numfiles: 3
"CASTLE.STL"
"bincastle.stl"
"test.slp"

"motion.dat" "CASTLE" "1000.0"
"motion.dat" "BCASTLE" "1000.0"
"motion.dat" "TEST"
"1000.0"

And if an additional offset is needed to the CG, add these in 3 more columns
example:
numfiles: 3
"CASTLE.STL"
"motion.dat" "CASTLE" "1000.0" "1.35" "2.66" "0.0"
"bincastle.stl" "motion.dat" "BCASTLE" "1000.0" "-2.45" "1.0" "-2.0"
"test.slp"
"motion.dat" "TEST"
"1000.0" "60.2" "23.4" "0.0"

See the following file for current information on this reader.
$CEI_HOME/ensight92/src/readers/stl/README

Simple Interface
Data Load

Load your geometry file (typically named with a suffix .stl or .xct) using the
Simple Interface method.

Advanced Interface
Data Load

Load your geometry file (typically named with a suffix .stl or .xct) using the
Advanced Interface method.
Data Tab

2-108

Format

Use the STL format.

Set geometry

Select the geometry file (typically .stl or .xct) and click this
button

EnSight 9 User Manual

2.3 STL Reader

Set results

As of version 8.0.7(h) this field is activated to allow flags to
change reader behavior. In order to truncate the float values
put in a tolerance value and the reader will retain only to the
designated significant digit. This can be used to eliminate
duplicate node problems due to roundoff error. Put in the
keyword
-tol 1e-3
to eliminate the fourth and smaller decimal point values in the
nodal coordinates during data file read. See the README file
for more details.

Format Options Tab
Set measured

Select the measured file and click this button.

(see How To Read Data)

EnSight 9 User Manual

2-109

2.3 Tecplot Reader

Tecplot Reader
Overview
Description

There are two Tecplot readers included with EnSight: Tecplot Binary and
Tecplot_ASCII which read binary and ASCII Tecplot data.

TECPLOT Binary
Reader Usage

The TECPLOT binary file format uses a Tecplot plt file.

Tecplot ASCII
Reader

A subset of the Tecplot 360 ASCII format is read using the Tecplot_ASCII reader.
In the format options tab of the data reader dialog, choose Debug to get extra
output to the console if EnSight fails to read your ASCII file.

README

See the following directory for current information on these readers.
$CEI_HOME/ensight92/src/readers/tecplot/

Simple Interface
Data Load

Load your Tecplot file (typically named with a suffix .plt or .plot or .dat) using
the Simple Interface method.

Advanced Interface
Data Load

Load your Tecplot file (typically named with a suffix .plt or .plot or .dat) using
the Advanced Interface method.
Data Tab
Format

Use the or Tecplot_ASCII, Tecplot Binary, or the legacy
TECPLOT 7.x format.

Set plot
(or dat)

This field should have the .dat file name for ASCII data and
the .plt name for binary data.

Format Options Tab
Set measured

Select the measured file and click this button.

Tecplot
Binary Other
Options

2-110

EnSight 9 User Manual

2.3 Tecplot Reader

Include
ElemSet
Parts

Include any Element sets defined. These are sets of full
elements which are generally some logical subset of the total
number of elements. Default is on.

Include Face/
Edge Parts

Include any Face or Edge sets defined. These are some logical
set of particular faces and/or edges of full elements. Default is
on.

Include
NodeSet
Parts

Include local
elem res
comps (if
any)

EnSight 9 User Manual

2-111

2.3 Tecplot Reader

Include
Tensor
derived
(VonMises,
etc.)

Parts will be created according to the following:
Use Part Id - Part Id

(this is the default)

Use Property Id - Property Id
Use Material Id - Material Id

Var naming
convention

2-112

EnSight 9 User Manual

2.3 Tecplot Reader

Element Vars
as

If Sections,
which:

Section Num

If the previous option is chosen to be Section Num, then the
value in this field is the 1-based section number to use to
create the variable.

(see How To Read Data)

EnSight 9 User Manual

2-113

2.3 Vectis Reader

Vectis Reader
Overview
Reader Visibility
Flag

By default, this reader is not loaded into the list of available readers. To enable
this reader go into the Menu, Edit > Preferences and click on Data and toggle on
the reader visibility flag.

Reader vs.
Translator

This reader is designed for files written before Vectis 3.6. For versions 3.6 or later,
we recommend using the Ricardo v2e translator to convert the Vectis POST file to
the Ensight format (for more details, see our FAQ on our website www.ensight.com/
FAQ/faq.0024.html).

Pre-version 3.6
Description

This reader inputs either .TRI or .POS datasets as follows
Single TRI file - Gives the CAD geometry, but no variables (If you must see this
along with your POST data, will have to read it as a second case), for example,
CYLINDER.TRI
Single POST file WITH NO *'s in the name - Gives the geometry and variables in
the post file, including surface patches and particles.
Multiple POST files - Enter a filename WITH *'s in the name
Gives the geometry and variables in the post files, which match the asterisks in a
sequentially increasing pattern (starts at 1, increases by 1). Note: If your naming/
numbering scheme is different than this, we require you to rename/renumber.
ex1) CYLINDER.POS.**
matches:
CYLINDER.POS.01
CYLINDER.POS.02

Query over time
Cell Variables

README

CYLINDER.POS.03

ex2) myfile***.pos
matches:
myfile001.pos
myfile002.pos
Query node over time operation within EnSight will only work for cell variables
on the cell part. Patch and drop variables will currently return all zeros.
You may request cell variables on patch or droplet parts. The cell variable will be
mapped onto them. BUT, be aware that any portions of the patches which are
actually in the "external" cells will have zero values, because VECTIS doesn't
contain that info directly. This leads to slightly "streaked" or "blotched" models
which basically show the variable, but are probably not presentation quality. In
order to eliminate this effect, neighboring cell information will need to be
accessed - and at this time that work has not been done. Consider using Ensight's
Offset Variable capability - it might be useful for certain models.
See the following file for current information on this reader.
$CEI_HOME/ensight92/src/readers/vectis/README.txt

Simple Interface
Data Load

Load your Vectis file (typically named with a suffix .TRI or .POS) using the Simple
Interface method.

Advanced Interface
Data Load

Load your Vectis file (typically named with a suffix .TRI or .POS) using the
Advanced Interface method.
Data Tab
Format

2-114

Use the Vectis format.

EnSight 9 User Manual

2.3 Vectis Reader

Set tri/pos

Select the vectis file (typically .TRI or .POS) and click this
button. This field should written by a Vectis version earlier
than 3.6

Format Options Tab
Set measured

Select the measured file and click this button.

(see How To Read Data)

EnSight 9 User Manual

2-115

2.3 XDMF Reader

XDMF Reader
Overview
Description

Reads eXtensible Data Model and Format files (.xdmf files).
This reader is based on the xdmf library from:
pserver:anonymous@public.kitware.com:/cvsroot/Xdmf

The reader can handle all the element types in Xdmf except:
XDMF_MIXED
XDMF_POLYGON

Structured meshes are converted to unstructured form automatically by the reader.
The reader supports variables of type:
XDMF_ATTRIBUTE_TYPE_SCALAR
XDMF_ATTRIBUTE_TYPE_VECTOR
XDMF_ATTRIBUTE_TYPE_TENSOR

With centering:
XDMF_ATTRIBUTE_CENTER_CELL
XDMF_ATTRIBUTE_CENTER_NODE

The reader can handle 'Tree' grids. The reader does automatically decompose
datasets for server of server mode (SOS) based on 'Tree' grids. The various grid
blocks are distributed round-robin over the servers. Grids that are not 'Tree' grids
will all be read on the first server.
The reader allows the user to pass a filename using a wildcard (* or ?) to select a
collection of .xmf files. The reader assumes that each .xmf file contains a separate
timestep. Some checks are made to verify that each file has the same structure/
variables, but the checks are not complete. Likewise, some basic checks are made
for grids defined by reference. If all but one file has its grids geometry/topology
by reference, the reader will assume that they can be reused for other timesteps.
The reader can also be passed a file in the schema:

UserManual User Manual

Navigation menu

Versions of this User Manual:

Views

Navigation