Ensight Usermanual User Manual

2017-12-05

User Manual: Ensight Usermanual UserManual EnSight10_Docs www3.ensight.com 3:

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

DownloadEnsight Usermanual User Manual
Open PDF In BrowserView PDF
EnSight User Manual
for Version 10.2
Table of Contents
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Overview
Input
List Panels
Main Menu
Features
Transformation Control
Variables and EnSight Calculator
Preference and Setup File Formats
EnSight Data Formats
Utility Programs
Remote Display and Parallel Compositing
Caves, Walls & Head-mounted displays
CEIShell
EnSight Networking Considerations
Raytracing
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.ceisoftware.com

© Copyright 1994–2013, 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
EN-UM: 10.0.-0
EN-UM: 10.1.-0
EN-UM: 10.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
January 2012
June 2014
September 2016

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 10.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.ceisoftware.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

Table of Contents
1 Overview
1.1 Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Reading and Loading Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Part Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Created Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Part Selection and Identification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Transient Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

1.2 GUI Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
1.2.1 Main Graphics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 List Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.3 User Interface Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.4 Feature and Quick Action Icon Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.5 Tools Icon Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.6 Main Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.7 Quick Color Widget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.8 Feature Panel (FP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.9 Click/Touch-n-Go . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.10 Drag-n-Drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-16
1-17
1-18
1-19
1-20
1-21
1-21
1-22
1-24
1-28

1.3 Other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
1.4 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
1.5 Contacting CEI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
EnSight 10.2 User Manual

iii

Table of Contents

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-12
EnSight Case Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-13
EnSight5 Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-14

2.3 Other Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
ABAQUS_ODB Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-17
AIRPAK/ICEPAK Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-26
AcuSolve Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-29
ANSYS Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-30
AUTODYN Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-34
AVUS Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-37
Barracuda Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-38
CAD Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-40
CFF Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-42
CFX4 Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-43
CFX5 Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-44
CGNS Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-46
CGNS-XML Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-53
Converge_Input Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-58
CTH Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-60
EXODUS II Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-63
FAST UNSTRUCTURED Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-73
FIDAP NEUTRAL Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-74
FLOW3D-MULTIBLOCK Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-75
FLUENT Direct Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-82
Inventor Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-88
LS-DYNA Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-89
MSC.DYTRAN Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-92
MSC.MARC Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-94

iv

EnSight 10.2 User Manual

Table of Contents

MSC.MARC Legacy Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-98
NASTRAN OP2 Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-100
Nastran Input Deck Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-105
OpenFOAM Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-107
OVERFLOW Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-110
PLOT3D Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-113
RADIOSS Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-114
POLYFLOW Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-115
SDRC Ideas Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-118
SILO Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-121
Software Cradle FLD Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-123
STAR-CD and STAR-CCM+ Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-125
STL Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-131
Synthetic Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-133
Tecplot Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-138
Vectis Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-142
VTK Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-144
XDMF Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-146

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

2.5 Command Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-149
Saving the Default Command File for EnSight Session. . . . . . . . . . . . . . . . . . 2-153
Auto recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-154

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

2.7 Context Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-158
Saving a Context File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-158
Restoring a Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-158

2.8 Session Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-160
Saving a Session File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-160
Restoring a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-161
EnSight 10.2 User Manual

v

Table of Contents

2.9 Scenario Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-162
2.10 Saving Geometry and Results Within EnSight . . . . . . . . . . . . . 2-166
Saving Geometric Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-166
If Rigid Body Transformations in Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-169

2.11 Saving and Restoring View States. . . . . . . . . . . . . . . . . . . . . . . 2-171
2.12 Saving Graphic Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-172
Troubleshooting Saving an Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-177

2.13 Saving and Restoring Animations . . . . . . . . . . . . . . . . . . . . . . . 2-178
2.14 Saving Query Text Information . . . . . . . . . . . . . . . . . . . . . . . . . 2-179
From EnSight Message Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-181

2.15 Saving Your EnSight Environment. . . . . . . . . . . . . . . . . . . . . . . 2-182
2.16 Saving EnSight Graphics Rendering Window Size. . . . . . . . . . 2-183

3 List Panels
3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2 Part List Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.2.1 Default View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5
3.2.2 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5
3.2.3 Right Mouse Button Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6
3.2.4 Part Group Visual Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16

3.3 Variables List Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
3.3.1 Default View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22
3.3.2 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22
3.3.3 Right Mouse Button Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-23

3.4 Annotations List Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
3.4.1 Default View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-26
3.4.2 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-26
3.4.3 Right Mouse Button Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-27

3.5 Queries/Plotters List Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
3.5.1 Default View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-29
3.5.2 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-29
vi

EnSight 10.2 User Manual

Table of Contents

3.5.3 Right Mouse Button Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

3.6 Frames List Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
3.6.1 Default View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
3.6.2 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
3.6.3 Right Mouse Button Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34

3.7 Viewports List Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
3.7.1 Default View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
3.7.2 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
3.7.3 Right Mouse Button Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

3.8 Quick Color Widget Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37

4 Main Menu
4.1 File Menu Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2 Edit Menu Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.3 Create Menu Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
4.4 Query Menu Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
4.5 View Menu Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
4.6 Tools Menu Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
4.7 Window Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
4.8 Case Menu Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
4.9 Help Menu Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62

5 Features
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.0.1 Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

5.1 Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5.1.1 Parts Quick Action Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.1.2 Model Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Feature Panel Turndowns Common To All Part Types . . . . . . . . . . . . . . . . . . . 5-36
5.1.3 Clip Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
EnSight 10.2 User Manual

vii

Table of Contents

5.1.4 Contour Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-65
5.1.5 Developed Surface Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-69
5.1.6 Elevated Surface Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-74
5.1.7 Extruded Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-79
5.1.8 Isosurface Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-82
5.1.9 Material Interface Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-87
5.1.10 Particle Trace Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-92
5.1.11 Point Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-113
5.1.12 Profile Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-116
5.1.13 Separation/Attachment Line Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-120
5.1.14 Shock Regions/Surfaces Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-125
5.1.15 Subset Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-131
5.1.16 Tensor Glyph Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-134
5.1.17 Vector Arrow Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-137
5.1.18 Vortex Core Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-143
5.1.19 Auxiliary Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-148
5.1.20 Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-150

5.2 Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-151
5.2.1 Text Annotation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-152
5.2.2 Line Annotation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-156
5.2.3 Shape Annotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-159
5.2.4 3D Arrow Annotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-162
5.2.5 Dial Annotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-168
5.2.6 Gauge Annotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-171
5.2.7 Logo Annotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-174
5.2.8 Legend Annotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-175
5.2.9 Query/Plotter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-177

5.3 Query/Plotter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-178
5.3.1 At Line Tool Over Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-185
5.3.2 At 1D Part Over Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-186
5.3.3 At Spline Over Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-188
5.3.4 At Node Over Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-189
5.3.5 At Element Over Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-190
5.3.6 At IJK Over Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-191
5.3.7 At XYZ Over Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-192
5.3.8 At Minimum Over Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-193
5.3.9 At Maximum Over Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-194
5.3.10 By Scalar Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-195

viii

EnSight 10.2 User Manual

Table of Contents

5.3.11 By Constant on Part Sweep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.12 By Operating on Existing Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.13 Read From an External File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.14 Read From a Server File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.15 Plotters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.16 Viewports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-196
5-197
5-199
5-200
5-201
5-208

5.4 Viewports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-209
5.4.1 Viewports Quick Action Icons & Feature Panel . . . . . . . . . . . . . . . . . . 5-211
5.4.2 Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-217

5.5 Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-218
5.5.1 Frames Quick Action Icons and Feature Panel. . . . . . . . . . . . . . . . . . .
5.5.2 Frame Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.3 Frame Transform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.4 Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-220
5-226
5-229
5-231

5.6 Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-232
5.6.1 Flipbook Animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-232

5.7 Flipbook Animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-233
5.7.1 Interactive Probe Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-238

5.8 Interactive Probe Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-239
5.8.1 Keyframe Animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-241

5.9 Keyframe Animation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-242
5.9.1 Solution Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-249

5.10 Solution Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-250
5.11 Tools Icon Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-259
5.11.1 User Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-270

5.12 User Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-271

6 Transformation Control
General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6.1 Global Transform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6.2 Tool Transform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

EnSight 10.2 User Manual

ix

Table of Contents

6.3 Center Of Transform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
6.4 Z-Clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
6.5 Look At/Look From. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
6.6 Copy/Paste Transformation State . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
6.7 Camera . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19

7 Variables and EnSight Calculator
General Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1

7.1 Variable Selection and Activation. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
7.2 Variable Summary & Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Palette Editor Items Available on Every Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-9
Palette Editor Simple Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-9
Palette Editor Advanced Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-9
Palette Editor Markers Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-10
Palette Editor Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-10
Palette Editor Files Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11

7.3 Variable Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Threaded Calculator Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-18

7.4 Boundary Layer Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-81

8 Preference and Setup File Formats
8.1 Palette/Color File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Palette Editor File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-3
Predefined Function Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-4
Default False Color Map File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5
Default Part Color File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5

8.2 Data Reader Preferences File Format . . . . . . . . . . . . . . . . . . . . . . . 8-7
8.3 Data Format Extension Map File Format . . . . . . . . . . . . . . . . . . . . . 8-8
8.4 Parallel Rendering Configuration File . . . . . . . . . . . . . . . . . . . . . . 8-10
x

EnSight 10.2 User Manual

Table of Contents

8.5 Resource File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
8.6 Other Preferences Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
8.7 Python Extension Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14

9 EnSight Data Formats
EnSight Maximums . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

9.1 EnSight Gold Casefile Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
EnSight Gold General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
EnSight Gold Case File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
EnSight Gold Geometry File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Partial example of per-part connectivity usage . . . . . . . . . . . . . . . . . . . . . . . . . 9-52
EnSight Gold Variable File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-53
EnSight Gold Per_Node Variable File Format . . . . . . . . . . . . . . . . . . . . . . . . . . 9-53
EnSight Gold Per_Element Variable File Format. . . . . . . . . . . . . . . . . . . . . . . . 9-69
EnSight Gold Undefined Variable Values Format . . . . . . . . . . . . . . . . . . . . . . . 9-83
EnSight Gold Partial Variable Values Format . . . . . . . . . . . . . . . . . . . . . . . . . . 9-87
EnSight Gold Constant Per Part Variable Files . . . . . . . . . . . . . . . . . . . . . . . . . 9-92
EnSight Gold Measured/Particle File Format . . . . . . . . . . . . . . . . . . . . . . . . . . 9-97
EnSight Gold Material Files Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-98

9.2 EnSight6 Casefile Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-110
EnSight6 General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-110
EnSight6 Case File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-113
EnSight6 Geometry File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-121
EnSight6 Variable File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-126
EnSight6 Per_Node Variable File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-126
EnSight6 Per_Element Variable File Format . . . . . . . . . . . . . . . . . . . . . . . . . . 9-129
EnSight6 Measured/Particle File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-133
Writing EnSight6 Binary Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-133

9.3 EnSight5 Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-138
EnSight5 General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-138
EnSight5 Geometry File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-140

EnSight 10.2 User Manual

xi

Table of Contents

EnSight5 Result File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-144
EnSight5 Variable File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-146
EnSight5 Measured/Particle File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-147
Writing EnSight5 Binary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-150

9.4 FAST UNSTRUCTURED Results File Format . . . . . . . . . . . . . . . 9-153
9.5 FLUENT UNIVERSAL Results File Format . . . . . . . . . . . . . . . . . 9-157
9.6 Movie.BYU Results File Format . . . . . . . . . . . . . . . . . . . . . . . . . . 9-159
9.7 PLOT3D Results File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-162
9.8 Server-of-Server Casefile Format . . . . . . . . . . . . . . . . . . . . . . . . 9-168
Partition Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-168
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Spatially decomposed Case files9-172
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Threading9-173
NETWORK_INTERFACES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-173

9.9 Periodic Matchfile Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-175
9.10 XY Plot Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-178
9.11 EnSight Boundary File Format . . . . . . . . . . . . . . . . . . . . . . . . . . 9-180
9.12 EnSight Particle Emitter File Format . . . . . . . . . . . . . . . . . . . . . 9-184
9.13 EnSight Rigid Body File Format . . . . . . . . . . . . . . . . . . . . . . . . . 9-186
Version 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-186
Version 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-190

9.14 Euler Parameter File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-202
9.15 Vector Glyph File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-207
General Comments: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-207
File description: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-208
Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-210

9.16 Constant Variables File Format . . . . . . . . . . . . . . . . . . . . . . . . . 9-212
General Comments: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-212
Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-213

9.17 Point Part File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-214
xii

EnSight 10.2 User Manual

Table of Contents

9.18 Spline Control Point File Format . . . . . . . . . . . . . . . . . . . . . . . . 9-215
9.19 EnSight Embedded Python (EEP) File Format . . . . . . . . . . . . . 9-216
The “module” case (“__init__.py”): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-216
The “installer” case (“autoexec.py”): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-216
Usage notes: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-216

9.20 Camera Orientation File Format . . . . . . . . . . . . . . . . . . . . . . . . 9-217
Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-217

9.21 Multi-Tiled Movie (MTM) File Format . . . . . . . . . . . . . . . . . . . . . 9-218
Example Tiling of large movie by subdividing into two parts in the X: . . . . . . . 9-218
Example Stereo movie using a series of left and right png files: . . . . . . . . . . . 9-218
Example Tiling of two movies to play them side by side: . . . . . . . . . . . . . . . . . 9-219

10 Utility Programs
10.1 EnSight Case Gold Writer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

11 Remote Display and Parallel Compositing
11.1 Remote Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
11.2 Parallel Compositing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7

12 Caves, Walls & Head-mounted displays
12.1 CAVES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
12.2 WALLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
12.3 Head-Mounted Displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20
12.4 SpaceNavigator and Gamepad . . . . . . . . . . . . . . . . . . . . . . . . . 12-22

13 CEIShell
EnSight Virtual Communication Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Operational Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
EnSight 10.2 User Manual

xiii

Table of Contents

CEIShell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-3
Basic CEIShell Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-8
Using CEIStart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-9
Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-12
Determining Where EnSight Components Run. . . . . . . . . . . . . . . . . . . . . . . . .13-13
Legacy Case SOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-15

14 EnSight Networking Considerations
15 Raytracing

xiv

EnSight 10.2 User Manual

1 Overview

1

Overview
EnSight (for Engineering inSight) provides engineers and scientists easy-to-use,
high performance graphics postprocessing capabilities.
Similar to any power tool, you are well advised to learn how the tool works in
order to maximize your investment in time and resources. EnSight is not a
difficult tool to master but it has a vocabulary and some basic functionality which,
lacking understanding, can make you unproductive.
The remainder of this manual will detail the capabilities of EnSight which can be
summarized as: viewing, creating geometry and variables, performing queries,
and saving various forms of data.

1.1

Concepts

Architecture

EnSight has an architecture designed for compatibility with a variety of compute
environments - ranging from desktops to distributed memory clusters perhaps
located at remote locations. The extent to which you utilize or ignore this
architecture is up to you.
As an overview, EnSight always has, at minimum, two processes running. The
process that you interact with on your desktop is called the “client”. It is
responsible for user interaction as well as all graphics functions. The other process
that is running when you launch EnSight is the “server”. The server process reads
the data and extracts the portion (geometry, variables, queries, etc.) that you wish
to view - either as 3d geometry or queries of various kinds. The server process can
run on the same machine as the client but may also run on other systems - in
which case the two processes communicate with each other across the network.
For the most part, users will find satisfactory performance with EnSight “out of
the box” transparently running client and server processes on their same machine.
However, EnSight has much more powerful options.
Moving your large dataset from a compute server to your desktop for visualization
is a waste of time and resources. You should never need to move large datasets!
The EnSight server should always run on the compute system(s) that generated
the large data. As your datasets become larger, the EnSight client can run on your
local machine with a good graphics hardware card and the EnSight server can be
run on your big memory solver machine near the data.
EnSight sometimes uses multiple servers. It uses multiple servers to read multiple
datasets, or multiple servers to partition a single, large dataset or to cache transient
data for faster time change. For example, the client can compare multiple datasets
by connecting to multiple servers; each separate server loads its own dataset
(called a case). Or, a single, large dataset can be spatially partitioned among a
number of servers with a server of server (SOS) acting as a communication hub
between the servers and the client. And finally a single, large, transient dataset can
be automatically temporally partitioned among multiple servers (each with one
full timestep) to speed up the time change using caching.
Data on the server is inherently 3D. With one exception (volume rendering), data
on the client is inherently 2D polygons, i.e., 3D information has been reduced one

EnSight 10.2 User Manual

1-1

1 Overview

dimension by the time you see it on the client.
EnSight can use multiple clients. For extremely large datasets that result in an
extremely large number of 2D polygons on the client, multiple clients can be used
to overcome rendering problems. EnSight can subdivide the rendering problem
into manageable portions using multiple clients.
EnSight writes temporary files for caching purposes, to the directory defined by
the environmental variable CEI_TMPDIR (if set) or TMPDIR. These files will be
prefixed “Ensi” + “pid_” where pid is the process id using 6 digits, i.e. if pid=325
and the generated temporary file extension is 12, then we have “Ensi000325_12”.
Temporary files are written during isosurface creation, command file recording,
certain licensing operations and certain backup operations.

Cases

Each time you read a new set of data you open a “Case”. Cases can be deleted,
added, or replaced. You can have multiple cases loaded simultaneously and each
case can be a different format and can contain different geometric and variable
information.
A case can be “transient” - meaning something (geometry and/or variables) is
changing over time - or “static” meaning steady state with no data changing over
time.
Each case will contain “Parts” and possibly (usually) “Variables”.
Loading multiple cases is usually used to perform comparisons between similar
solver runs or to composite solutions from an assembly.
A Case is read via a “Data Reader”. Multiple data readers and translators currently
exist and are constantly being worked on and expanded. They consist of the
following 4 types:
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.
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.
They are often available via a third party.
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 10 of this manual. Several translators are provided with EnSight.
Others may be available from third parties.
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.
In order to keep the list of readers and translators as current as possible, tables are
maintained on our website. Please go to the following location to see the latest
(http://www.ceisoftware.com/ensight-data-interfaces/). If your format or
program is not listed, there is the possibility that an interface does indeed exist.
Contact EnSight support for assistance. Also, if 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@ceisoftware.com.

Parts
1-2

The Part is the fundamental visualization entity in EnSight. Virtually every

EnSight 10.2 User Manual

1 Overview

postprocessing task you perform will involve a Part, thus it is vital to understand
how Parts work.
A part is a collection of nodes and elements that are grouped together and share
the same attributes. When you start EnSight, you either read directly or
interactively extract parts from the data files. Parts which come from the original
dataset are referred to as model parts. Other parts created within EnSight, are
referred to as created (or dependent) parts. Model parts are defined by the data
readers and are usually a logical grouping of nodes and elements as defined by the
solver. It might be a material or property or perhaps a defined geometric entity
such as a “wheel” or “inlet”.
Clip Plane

Contours

Elevated Surface

Isosurface

Profile

Vector Arrows
Figure 1-1
Various EnSight Part Types

Definition

Particle Traces

Model Part

EnSight uses a computational grid and has no concept of parametric surfaces/
volumes.

Computational
Grid

The computational grid (or mesh) used by EnSight is either an unstructured
definition (where each mesh element is defined) or a structured definition (an IJK
definition) defining a rectilinear or curvilinear space. It is also possible to have a
mixed definition where some parts are unstructured and other parts are structured.

Nodes (Vertices)

Nodes - or sometimes referred to as vertices - are a 3d definition given by a x, y, z
coordinate in reference to the model coordinate space.

Elements

Are shapes defined by connecting Nodes. EnSight supports linear and quadratic
elements as well as n-sided and n-faced elements. There are 0D, 1D, 2D, and 3D
elements. See EnSight Data Formats for a definition of the various elements
supported by EnSight.
Structured data does not directly define the elements in use but rather implies
quads (in 2D) or hexahedra (3D) elements. These elements may also be modified
by “Iblanking” which may result in the corners of the elements collapsing to form
new element types.

Reading and Loading Parts
When you read data you will choose the file name that will be read and set the
format and options for the file. Then you will choose one of two options - either to

EnSight 10.2 User Manual

1-3

1 Overview

load all the parts or to select parts to load.

The “Load all parts” option will read the specified data (the “case”) and create
(i.e. “load”) all of the parts into EnSight. The other option - “Select parts to
load...” - will read the data but will not load any parts. This second option will
allow you to select on a per part basis which parts will be loaded into EnSight.
This “load” process is performed through the Part List.
The Part List contains all parts that have been read in (“loaded”) from your
specified data file as well as those created within EnSight. Additionally, it may
show model parts from the data that are not already loaded. These are referred to
as Loadable Parts or LPARTs.
LPARTs may be loaded zero or more times. You may choose not to load a
particular part from a data set if it is not needed for the visualization or analysis of
the case. This is advantageous to save memory and processing time. You may also
choose to load a part multiple times - so you could, for example, color the part by
multiple variables at the same time in multiple viewports.
LPARTs are shown as grayed out parts in the Part List. You can load a LPART by
selecting the part(s) and performing a right click operation to “Load part”

Part Attributes
Attributes define how a part appears and how it is created (in case of created
parts). All loaded parts have attributes.
The attributes that control how a part appears are referred to as “general” or
“visual” attributes. All part types have these same general attributes and include
settings such as visibility, line width, color, lighting parameters, etc.
Created parts have creation attributes, i.e., settings which specify how the part is
created. Each part type will have a different set of creation attributes.
Element
Representation

One of the general attributes that deserves some discussion in this overview is
“Element Representation”.
At the start of this chapter the EnSight architecture was briefly discussed,
indicating that the server has the data from the case you have loaded and the client
shows the extracts of data that you desire. The less data you extract to the client
the smaller the memory requirements and higher the performance. One way to
minimize the data sent to the client for visualization is to take advantage of the
“Element Representation” attribute.
Element Representation has no effect whatsoever on the data stored and used on
the EnSight server process. It only effects what is sent to the client for display.
Except for the “volume” representation, no 3D elements are ever sent to the client.
Even when a 3D element is viewed (“Full” representation) it is viewed on the
client as a set of 2d faces for the 3d element.

1-4

EnSight 10.2 User Manual

1 Overview

The choices for Element Representation are:
Full

The client receives all of the vertices, as well as the definition
for all 0D, 1D, and 2D elements and all of the element faces
for 3D elements. It is usually a mistake to load parts
containing 3D element in this mode. 2D parts are usually best
loaded in this mode.
The image below shows two parts. The part on the left is
composed of quad (i.e., 2D) elements, while the part on the
right is composed of hexahedra (i.e., 3D) elements. The 3D
part is showing all of the faces of all of the 3D elements
resulting in “clutter” in the interior of the part.

Figure 1-2
Full Element Representation of 2D and 3D parts.

Border

The shared edges between 2D elements and the shared faces
between 3D elements are removed. Using the same geometry
from above, the figure below shows the result of this mode.
Note that the 3D part no longer contains interior lines. Border
mode is usually the best mode to use for loading 3D parts, and
not usually used for 2D parts.

Figure 1-3
Border Element Representation of 2D and 3D parts.

EnSight 10.2 User Manual

1-5

1 Overview

Feature angle

This representation works on 2D elements, thus for 3D parts
the server first computes the Border representation. Then
given 2D elements, the edge between two elements is
removed if the normal between the two elements sharing the
edge is less than an angle (default 10 degrees) specified by the
user. The result is 1D information on the client that represents
“sharp” edges of the part. The figure below shows the result
of feature angle mode. Since the 2D part is planar all of the
interior edges are removed. Similarly for the 3D part - since
all the exterior bounds of the part are planar - all of the
interior edges of each face are removed, leaving just the sharp
edges of the box.

Figure 1-4
Feature Angle Element Representation of 2D and 3D parts.

1-6

Nonvisual

No data is sent to the client. Please note that this is entirely
different than loading the part with some other Element
Representation and then turning off the visible attribute. The
visible attribute simple turns off the rendering of a part. The
data has still been sent to the client! This is the recommended
mode for parts that do not need to be viewed but will be used
for extracting information such as a fluid field around a
geometry.

Bounding box

Send only the bounding box geometry to the client for display.

EnSight 10.2 User Manual

1 Overview

Volume

Volume rendering displays all 3D elements at once, drawing
each element semi-transparently according to the value of a
variable.
Raw volume rendering (Use volume rep. as selected radio
button as shown in the figure below) will divide the elements
into tets and send them to the client and then adjust the
opacity per element based on the value of a variable.
Unstructured tet volume rendering uses 96 bytes per element
and 72 bytes per pixel. For example, if you have a 21x21x21
hex grid with roughly 10000 elements and each hex divides
into six tetrahedrons, you have 60k tet elements, using about
6MB. Suppose we have a 1K x 1K pixel screen, using about
72MB. This results in a combined estimate of about 6MB +
72MB for a total of 78MB. Note the estimate provided in the
dialog for this situation is 74MB, shown below.
A few million unstructured elements can easily overwhelm
the client and graphics card, so another, preferable option is
available to do a structured remesh (Use structured box clip
radio button shown in the figure below) using user-selected x,
y, and z dimensions to control the number of elements passed
up to the client. This structured, volume rendering uses up to
4 bytes/cell + 72 bytes per pixel on the client graphics card.
So a 21x21x21 structured grid (shown below) with 1kx1k
pixel screen, is roughly 40KB + 72 MB, or roughly 72MB.
So for small grid size, the bytes per pixel dominates and there
is little difference in the memory requirements between
structured and unstructured. But for large grids the bytes per
cell dominates (for a 1024x1024x1024 structured grid, this
takes 2GB for a structured and 100GB for unstructured) and
structured volume rendering is the only feasible way to go.

Figure 1-5
Volume Element Representation of a 3D part.

EnSight 10.2 User Manual

1-7

1 Overview

The default Element Representation used by EnSight, unless the data reader for
the format you have specified indicates otherwise, is “2D Full, 3D Border”.
Meaning 2D elements will be sent to the client in Full mode and 3D elements will
be sent in Border mode.

Created Parts
Parts that are created within EnSight are referred to as created (or dependent)
parts. The types of parts that you create depend on what features within EnSight
you choose to utilize. Any created part is derived from parts that already exist,
which is why created parts are sometimes called dependent parts—they depend on
the parts from which they were created. The parts that are used to create a
dependent part are referred to as parent parts. Any time that a parent part changes,
its dependent parts also change. A parent part will change when you change its
attributes, or modify the current time in the case of transient data.
Failure to select the proper parent part(s) will result in an incorrect part being
created. For example, if I intend to create a clip through the flow field on the
geometry shown in the image below:

Figure 1-6
Clip example geometry

And I select the part representing the external flow field I will indeed see the clip I
intend.

Figure 1-7
Clip through flow field part

But if I instead select the surface part as the parent I will get:

Figure 1-8
Clip through surface part

1-8

EnSight 10.2 User Manual

1 Overview

Both model parts and created parts can be parent parts. For example in the clip
example above, if I wanted to view vector arrows on the clip part I would select
the clip part as the parent.
See Section 5.1, Parts for a complete list and description of derived parts that
EnSight can create.
Auxiliary
Geometry

Auxiliary geometry can be created around existing parts on which textures or
images can be mapped, or shadows from the existing parts can be cast when
exporting ray traced images. Various attributes of the geometry can be controlled
such as, visible components, outline, thickness, double walls, etc. (see Section
5.1.19, Auxiliary Geometry)

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
cross the intersection surface (a “crinkly” surface). You can also choose to cut the
parent parts into half spaces.
(see Section 5.1.3, Clip Parts)

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 5.1.4, Contour Parts)

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 5.1.5, Developed Surface Parts)

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 5.1.6, Elevated Surface Parts)

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 5.1.7, Extruded Parts)

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 5.1.8, Isosurface Parts)

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,

EnSight 10.2 User Manual

1-9

1 Overview

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 visible 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, or as
the emitter part element boundary representation is updated.
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
max variable location occurs.
(see Section 5.1.10, Particle Trace Parts)
Points

Point parts are composed only of nodes. They can be created by reading an
external file containing the xyz coordinates of the nodes, and/or by placing the
cursor tool at desired locations and adding nodes. This feature can be used to
essentially place probes in the model at particular locations. It can also be used to
create parts that can be meshed with the 2D or 3D meshing capability within
EnSight.
(see Section 5.1.11, Point Parts)

Profiles

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

Separation/
Attachment Lines

Separation and attachment lines show where flow abruptly leaves or returns to the
2D surface in 3D fields.
(see Section 5.1.13, Separation/Attachment Line Parts)

Shock Surfaces/
Regions
Subsets

1-10

Shock surfaces or regions show the location and extent of shock waves in a
3Dflow field.
(see Section 5.1.14, Shock Regions/Surfaces Parts)
A subset Part can contain node and element ranges of any model Part.
(see Section 5.1.15, Subset Parts)

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 5.1.16, Tensor Glyph Parts)

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
EnSight 10.2 User Manual

1 Overview

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 5.1.17, Vector Arrow Parts)
Vortex Cores

Vortex cores show the center of swirling flow in a flow field.
(see Section 5.1.18, Vortex Core Parts)
Part creation occurs on either the server or the client. Since the data that is
available on the client and server are different, it is useful to understand where
Parts are created and where the resulting data is stored. By understanding this, you
will understand why some Parts can be created with certain parent Parts and
others cannot. For example, why you can’t clip through a particle trace part (clips
are created on the server and the particle trace part is not defined there). This
information can be gained by examining the following table.
Table 1–2 Part Creation and Data Location
Part Type

Where Created

Data on
Server

Data on Client

Clip

Server

Yes

Depending on Element Rep

Contour

Client

No

Yes

Developed
Surface

Server

Yes

Depending on Element Rep

Elevated Surface

Server

Yes

Depending on Element Rep

Isosurface

Server

Yes

Depending on Element Rep

Material Part

Server

Yes

Depending on Element Rep

Particle Trace

Server

No

Yes

Point Part

Server

Yes

Depending on Element Rep

Profile

Client

No

Yes

Separation/
Attachment Line

Server

Yes

Depending on Element Rep

Shock Surface/
Region

Server

Yes

Depending on Element Rep

Subset

Server

Yes

Depending on Element Rep

Tensor Glyph

Client

No

Yes

Vector Arrow

Client. Server if
necessary.

No

Yes

Vortex Core

Server

Yes

Depending on Element Rep

(see Introduction to Part Creation)

Part Selection and Identification
In the process of creating a Part you will need to be able to select the parent
Part(s). This operation can be done from either the part list, the graphics window,
or by key words from a search dialog.
See How to Select Parts.

EnSight 10.2 User Manual

1-11

1 Overview

Transformations
The standard transformations of rotate, translate, and scale are available, as well
as positioning of the Look-At and Look-From points and camera positions. The
transformation-state (the specific view in the Graphics Window and Viewports)
can be saved for later recall and use to a views manager. Transformations can be
performed with precision in a dialog, or interactively with the mouse.
(see Chapter 6, Transformation Control)

Frames
Normally transformations are performed on the entire scene. But they can also be
performed on a subset of the geometry (such as an “exploded” view). This is done
by creating a coordinate frame and assigning part(s) to the new frame definition.
The frame can be offset and rotated from the model axis system. 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.

Variables
While Parts are the fundamental entity in EnSight, the purpose of using EnSight is
nearly always the pursuit of understanding the simulation results, i.e., Variables.
Variables can either originate with the data file read or they can be computed
using provided variables and geometry.
Variables can be defined on all nodes/elements or can be declared “undefined” for
specified parts or node and element ranges.
Location

A field variable can be defined on an element center or at the vertices of the part.

Constant Variable

A Constant variable defines a single value and may or may not be associated with
any specific part. A Constant Variable may change value over time or be
recomputed based on its parent parts. Total Volume of a model is an example of a
constant variable. It is often referred to as a constant per case.

Constant Per Part
Variable

A Constant Per Part variable defines a single value for a given part. Each part can
have its own value for the variable. It can change overtime. Part Area would be a
good example of a constant per part variable. Note that created parts will only
inherit this variable if all parent parts have the same value.

Scalar Variable

A Scalar variable defines a single value for each node or element on each part
where it is defined. It creates a “field” of data values. Temperature would be an
example of a Scalar variable.

Vector Variable

A Vector variable defines three values - representing the x, y, and z components of
a vector - for each node or element on each part where it is defined. It creates a
“field” of data values. Velocity would be an example of a Vector variable.

Tensor Variable

A Tensor variable defines nine values - representing the components of a tensor for each node or element on each part where it is defined. It creates a “field” of
data values. A stress tensor would be an example of a Tensor variable.

Complex Scalars/
Vectors

1-12

Scalar and Vector variables may have a real and imaginary portion.

EnSight 10.2 User Manual

1 Overview

Variable Creation

New variables can be created either by specifying an equation via a calculator
dialog or a predefined definition can be used. Similar to creating new parts, you
will in most cases need to specify on what part(s) the new variable is computed. A
large number of functions are currently available.
(see Section 7.3, Variable Creation)

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, number 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

The plotter plots Y vs. X curves. The user controls line style, axis control, line
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.
(see Section 5.3, Query/Plotter and Section 5.8, Interactive Probe Query)

Transient Data

CoProcessing

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 and variables 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). Note that this “continuous” option is only
available for cases without changing connectivity.
EnSight has the ability to update the number of timesteps dynamically (that is,
perhaps if the solver is in the process of writing the data and you are loading it as
the solution proceeds: CoProcessing). The only caveat is that EnSight needs a
never-to-exceed, maximum number of timesteps. This can be achieved by putting
a maximum time steps keyword in a Case Gold file, or in a PLOT3D file, or by
inserting a special routine (USERD_get_max_time_steps) into your user-defined
reader, indicating dynamically updating the number of timesteps may occur. See
Advanced section of the Load Transient Data for details.

Animation
You can animate your model in four ways: particle trace animation, flipbook

EnSight 10.2 User Manual

1-13

1 Overview

animation, solution time streaming, and keyframe animation.
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 requires no computation to move from frame to
frame.
However, 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 frame. The user can then manipulate the model during
animation play back or b) Image animation where a bitmap image is created and
stored 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 5.7, 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 one time step at a time. While you don’t see the animation speed of a
flipbook, you only need enough memory to load in one step.

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 5.9, Keyframe Animation)

1-14

EnSight 10.2 User Manual

1 Overview

1.2

GUI Overview
This section gives an overview of the EnSight 10 user interface. Common terms
are described along with a brief summary of their purpose. References to other
sections of the documentation are noted for further details.
Figure 1-9 shows the EnSight user interface along with identification of several of
the major user interface elements. While EnSight typically follows the “look and
feel” guidelines for Microsoft Windows, Apple Macintosh, and Linux desktops, it
generally has a similar appearance on all of the platforms. Throughout this
document images of the interface may come from any of the three platforms;
nonetheless, the functionality is common to all three platforms in spite of minor
differences from the respective user interface guidelines.
The EnSight user interface is highly user configurable. For example, which icons
and where they’re displayed can be configured as can the scrolling lists to the left
of the graphics area. As such, the EnSight user interface may look significantly
different from what is shown in the documentation based on user preference.
Running EnSight with the command line option -no_prefs will revert EnSight
back to its default layout (see Command Line Start-up Options).
“Desktop” - refers to the upper level of the GUI. It contains the following areas:

Feature
Icons

Quick
Action
Icons

Secondary
Feature
Icons
Parts
List
Variables
List

Main
Graphics
Window

Object
List
Tabs

Picking and
recording

Shading, Hidden
Line, & Highlighting
Figure 1-9
EnSight 10 Startup GUI

EnSight 10.2 User Manual

Transformation
Control

Information
Button

Undo / Redo
Transformation

1-15

1 Overview

1.2.1 Main Graphics Window
Contents

This area shows a graphical representation of the currently loaded datasets’ visible
geometry. For example, a fluid dynamics dataset might show only boundary
surfaces, clips of fluid domains, and particle traces for flow fields but not the
entire fluid flow field; whereas FEA datasets might show all visible geometry for
a single time step from a transient simulation.

Mouse Usage

Within this area of the user interface the user may use the computer mouse to
interact with the graphics in many ways. While clicking and holding down the left
or middle mouse buttons and moving the mouse, the graphics may be
transformed. By default, clicking and holding the left button while moving the
mouse controls the default transformation, typically rotation. Clicking and
holding the middle button while moving the mouse controls translation. EnSight
preferences, via the EnSight Preferences Dialog, may be set to indicate how the
mouse behaves in the Main Graphics Window. See How To Set or Modify
Preferences, section To Set Mouse and Keyboard Preferences: for further details.

Selection

Clicking the left mouse button over an object drawn in the Main Graphics
Window while not moving the mouse selects the object beneath the mouse.
Holding down the Ctrl-key while performing this operation has the affect of
adding or removing the object below the mouse from the selection; thus, multiple
objects may be selected with the mouse. By default, the object selected in the
Main Graphics Window is highlighted. Additionally, the object is selected or
deselected in the appropriate list panel (described below).

Click-n-Go

Selecting an object in the Main Graphics Window activates various hotspots on
the object. For example left clicking on an isosurface activates a multi-arrow
marker on the isosurface. Clicking and dragging on this marker will change the
value of the isosurface. Similarly, activating the multi-arrow marker on a clip part
allows that marker to be dragged to change the location of the clip part.
Annotations can be dragged around the graphics window, resized, and rescaled. In
general most objects drawn in the graphics window may be directly manipulated
with the mouse. (see Section 1.2.9, Click/Touch-n-Go)

Right-mouse click

Clicking the right mouse button over an object in the Main Graphics Window will
display the popup context sensitive menu. The menu’s contents depend on the
object beneath the mouse pointer. If the mouse is over a clip plane, then a context
sensitive menu with options relevant to Parts, and in particular Clip Parts, will be
displayed containing applicable and common operations. Whereas if the mouse is
over a color legend, common operations applicable to legends are displayed.

Keyboard
interaction

Keystrokes may be used in the graphics window. The Del-key deletes the
currently selected object(s). The P-key is used by several different picking
operations. The function keys (F1-key through F12-key) are used for various
graphics transformations. See How To Rotate, Zoom, Translate, Scale and How
To Enable Stereo Viewing for further details. Additionally, EnSight Macros may
be defined to bind user-defined operations to other keys. See How To Define and
Use Macros for details.

Drag-n-Drop

The Main Graphics Window also supports drag and drop from the various List
Panels. For example, a variable such as Pressure may be dragged from the
Variable List and dropped onto a clip part in the Main Graphics Window. This will
color the clip part by the pressure variable. (see Section 1.2.10, Drag-n-Drop)

1-16

EnSight 10.2 User Manual

1 Overview

1.2.2 List Panels
List Panels show lists of commonly used EnSight Objects such as Parts, Variables,
Annotations, Queries, Plotters, Viewports, and Coordinate Frames. By default List
Panels are displayed to the left of the Main Graphics Window; but, because they
are a form of docking window, they may be moved to any edge of the main
EnSight Window, resized, undocked, or stacked on top of each other. Figure 1-10
shows the default layout of the list panels: the Parts list panel by itself and list
panels for Variables, Annotations, Queries/Plots, and Viewports stack atop of each
other in a tabbed layout. Chapter 3, List Panels of this document fully describes
the various List Panels.

Figure 1-10
List Panels

EnSight 10.2 User Manual

1-17

1 Overview

1.2.3 User Interface Panels
Other Panels

Other User Interface Panels, such as the Time, Flipbook, Keyframe, and various
User Defined Tools, are also displayed in the same areas as the List Panels.
Similarly as with the List Panels, these panels are also dockable windows and may
be moved, resized, undocked, or stacked. Figure 1-11 shows an example of this.

Figure 1-11
Abbreviated Parts List

1-18

EnSight 10.2 User Manual

1 Overview

1.2.4 Feature and Quick Action Icon Bar
By default icons along the top edge of the EnSight user interface are arranged into
three clusters: Feature Icons, Secondary Feature Icons, and Quick Action Icons.
The Feature Icons and Secondary Feature Icons are organized into a single Icon
Bar with a simple delimiter between them. The Quick Action Icons are in their
own Icon Bar. Each Icon Bar may be repositioned along any of the edges of the
user interface or even undocked. This is done by grabbing and dragging the left
dimpled edge of the Icon Bar. All of these icons are fully described in Chapter 5,
Features.
Feature Icons

The Feature Icons represent major functions of EnSight such as Part operations,
Calculator, Plotting, Queries, Viewports, Annotations, Time, Animation, and User
Defined Tools. Clicking on one of these icons activates the appropriate user
interface elements for that operation which may include displaying the
appropriate User Interface or List Panel, displaying the Feature Panel, and
displaying the relevant Secondary Feature Icons and Quick Action Icons.

Secondary Icons

By default Secondary Feature Icons are displayed for common Part creation
including: Contours, Isosurfaces, Clips, Vector Arrows, and Particle Tracing.
Clicking on these displays the appropriate user interface in the Feature Panel.

Customize
Toolbar

The Customize Feature Toolbar Dialog (see Figure 1-12), activated via right
clicking on the Feature Icons context sensitive menu, allows the user to select
which Feature Icons to show and in what order. It may be advantageous to
customize these icons to show only those that are typically used by the user.

Figure 1-12
Customization of the Feature Toolbar

Quick Action
Icons

The Quick Action Icons provide common operations to modify the most recently
selected EnSight Object such as a Part or Annotation. Specifically, these icons
operate on the what ever is selected in the last updated List Panel. For example, if
two plots were last selected, then the Quick Action Icons operate on those two
plots. If all parts where last selected, then the Quick Action Icons operate on all
parts.

EnSight 10.2 User Manual

1-19

1 Overview

1.2.5 Tools Icon Bar
The Icon Bar along the lower edge of the EnSight user interface, shown in Figure
1-13 contains a variety of icons for commonly used operations. They are briefly
described here, see Section 5.11, Tools Icon Bar for further details.
Fast Display

Highlight
Selected
Region Tool

Reinit Transforms

Undo / Redo

Fit View

Information
dialogue

Recording animations
Pick Mode
Shade Surfaces

Select View
Transformations
Cursor Tool
Line Tool
Tool Reset & Locate
Hidden Line Display
Plane Tool
Figure 1-13
Tools Icon Bar

Record animation

Displays the Save Animation Dialog for recording animations.

Pick mode for the Main
Graphics Window

Submenu to set the type of pick operation performed by the Pkey.

Display shaded surfaces Toggles shaded surface rendering.
toggle
Display hidden line
overlays toggle

Toggles hidden line overlays on the geometry.

Highlight selected parts
toggle

Toggles graphical highlighting of selected part(s).

Region tool visibility
toggle

Toggles the visibility of the region tool.

Cursor tool visibility
toggle

Toggles the visibility of the cursor tool.

Line tool visibility toggle

Toggles the visibility of the line tool.

Plane tool visibility
toggle

Toggles the visibility of the plane tool.

Tool locations / Reset
dialog submenus

Options to display either the Tool Locations Dialog or the
Reset Tools / Viewports Dialog

Graphics window
transformations
submenu

Rotate

Translate

1-20

Sets the Selected Transformation
operation to rotation. By default the
left mouse button is mapped to the
Selected Transformation.
Sets the Selected Transformation
operation to translation.

Zoom

Sets the Selected Transformation
operation to zoom.

Rubberband zoom

Sets the Selected Transformation
operation to rubberband zoom.

Rubberband region

Sets the Selected Transformation
operation to rubberband region.

Transformation editor

Displays the transformation Editor.

Reset…

Displays the Reset Tools / Viewports
Dialog.

EnSight 10.2 User Manual

1 Overview
Fast display mode
toggle

Toggle for Fast display mode. When on, reduced geometry
representations may be used for some or all of the parts to
speed interactive transformations.

Fit view

Reinitializes the graphics transformations so that all geometry
fits well within the Main Graphics Window while preserving the
current viewing orientation.

Reinitialize transforms

Resets the graphics transformations to initial values.

Views orientation
submenu

Options to look up or down each of the three axes and an
option to display the Views Dialog.

Info dialog display

Displays the EnSight Info Dialog.

Undo / redo last
transformation

Undo or Redo the last graphics transformation.

1.2.6 Main Menu Bar
The Main Menu Bar appears in the appropriate location for the operating system
in use. See Figure 1-14 for how it appears on the Apple Macintosh. Note that the
options are identical on all platforms. The Main Menu Bar options are described
in Chapter 4, Main Menu.

Figure 1-14
Main Menu Bar

1.2.7 Quick Color Widget
The Quick Color Widget appears in the top right location in the EnSight window.
See Figure 1-15. The Quick Color Settings widget allows you to store your

Figure 1-15
Quick Color Widget

favorite colors and drag/drop them onto objects (not viewports) that have a color
attribute. When any object with a constant color is selected, the large color patch
will show that object’s color. Drag and drop a color from any of the patches to any
single object to color that object by a constant color. Drag a color patch to any
other color patch. Right click on the patch to set its color. Currently parts, plotters,
queries, and all annotation types will accept a drag/drop color operation from the
widget.
Colors on the Quick Color Settings widget are stored as part of the user's
preferences and thus the colors on the widget are available between EnSight
sessions. For more details, see Use Quick Color Settings.

EnSight 10.2 User Manual

1-21

1 Overview

1.2.8 Feature Panel (FP)
While many common operations can be performed through direct interaction with
objects drawn in the Main Graphics Window, Icons, and various List and User
Interface Panels, more complex operations are typically found in the Feature
Panel (also known as the ‘FP’). Figure 1-16 shows the Feature Panel when used
for Isosurface Part Creation.

Figure 1-16
Isosurface Feature Panel (FP)

To avoid a proliferation of dialogs, EnSight typically reuses the Feature Panel for
many purposes. The Feature Panel will completely reconfigure itself
appropriately for the requested operation. The title bar of the Feature Panel will
indicate its current functionality. Common to most operations the Feature Panel
will also display its functionality in the upper left corner (‘Isosurfaces’ in Figure
1-16).
Simple and
Advanced

1-22

To simplify EnSight use while still providing a robust feature set, the Feature
Panel typically has a ‘Simple’ and an ‘Advanced’ view for most operations.
Toggling the ‘Advanced’ checkbox will display all options relevant to the current
operation. The Feature Panel also distinguishes, where appropriate, between
‘Create’ and ‘Edit’ mode. Create mode is used for creating new objects such as a
new Isosurface Part; whereas Edit mode is used to change attributes associated for
an existing object.

EnSight 10.2 User Manual

1 Overview

Figure 1-17
Part List

Selection and
Feature Panel
Selection

Figure 1-17 shows the Part List containing three parts. It is important to note three
visual metaphors shown. The blue highlighting around the ‘Isosurface part’
indicates that this part is the currently selected part. The pencil icon to the left of
the name ‘ami-x hypersonic body’ indicates that this part is the Feature Panel
selected part. The ‘P’ icon to the left of the ‘external flow field’ part indicates that
it is a parent part of the currently selected part(s). The concept between selected
and Feature Panel selected is important to understand and is common to all List
Panels. Selected objects are those that will be affected by operations in the main
user interface whereas Feature Panel selected objects are those that will be
affected by operations in the Feature Panel. This concept will be further
elaborated upon in Chapter 3, List Panels

EnSight 10.2 User Manual

1-23

1 Overview

1.2.9 Click/Touch-n-Go
Click-n-go is a way to grab a “handle” in the graphics window, using the mouse,
and drag it to affect the attribute attached to the handle. There are two methods
available, both of which perform the same operation and differ only in how the
handles appear. With click-n-go you use the left mouse button and click on an
object in the graphics window. If that objects has handles they will appear. With
touch-n-go the handles will automatically appear for the object found under the
mouse cursor (assuming your graphics hardware is capable of the function). With
either method, the next step is to “grab” a handle and modify its value by clicking
and dragging the handle.
Click-n-go is always active. Touch-n-go can be turned on/off via preferences. This
is done under Main Menu -> Edit -> Preferences -> View and using the “Set
Click-n-go preferences” button.
There are no touch-n-go handles on created parts – you must left click them to see
a handle (if it exists for the selected part type). The single handle will appear at the
picked location.
The following part types have a click-n-go handle with the function indicated:
Part Type

Handle function tied to

Isosurfaces

Isosurface value

Clip - XYZ

X, Y, or Z clip value

Clip - Plane

Translates the clip plane

Clip - Line

Translates the clip line

Clip - Cylinder

The radius

Clip - Cone

The cone angle

Clip - Sphere

The radius

Clip - IJK

I, J, or K value

Particle traces - streamlines

Translates emitter location

Vector arrows

Arrow scale factor

Contours

Number of sub-levels

Elevated Surface

Scale factor

Profiles

Scale factor

Click-n-go and Touch-n-go both show the same handles for the objects shown
in the figures below.
Text Annotation

The upper right handle performs a rotate of the text annotation. The other
handle performs a translate. It is not necessary to select the translate handle click/drag anywhere on the object (except the rotate handle) will perform a
translate.

1-24

EnSight 10.2 User Manual

1 Overview

Lines Annotation

The center handle translates the line annotation. The left/right handles move the
left/right end points. It is not necessary to select the translate handle - click/drag
anywhere on the object (except the other handles) will perform the translate.
Logo Annotation

The upper right handle will scale the logo. The other handle performs translate.
It is not necessary to select the translate handle - click/drag anywhere on the
object (except the other handles) will perform the translate.
Legend Annotation

The center handle will translate the legend. The upper right handle will resize.
The left top handle will modify the max value for the palette. Likewise, the
lower left handle will modify the min value. It is not necessary to select the
translate handle - click/drag anywhere on the object (except the other handles)
will perform the translate.

EnSight 10.2 User Manual

1-25

1 Overview

Dial Annotation

The upper right handle will size the dial while the other handle will translate. It
is not necessary to select the translate handle - click/drag anywhere on the
object (except the other handles) will perform the translate.
Gauge Annotation

The upper right handle will size the gauge dial while the other handle will
translate. It is not necessary to select the translate handle - click/drag anywhere
on the object (except the other handles) will perform the translate.
Shapes Annotation

The upper right handle will size the shape while the other handle will translate.
It is not necessary to select the translate handle - click/drag anywhere on the
object (except the other handles) will perform the translate.

1-26

EnSight 10.2 User Manual

1 Overview

Viewports

The cross handle will translate the viewport while the corner handles will resize.
There are no touch and go handles for this object - you must use click-n-go.
Once the click-n-go handles are visible you may click/drag anywhere on the
object (except the other handles) to perform a translate.
Plotters

Upper right corner handle will scale the plotter. The marker on the plotter
legend will move the legend. The cross marker (that is not attached to the
legend) will translate the plotter. The up/down arrows on the y-axis will scale
the top/bottom values of the axis. Similarly, the left/right arrows on the x-axis
will scale the left/right values of the axis. It is not necessary to select the
translate handle - click/drag anywhere on the object (except the other handles)
will perform the translate.

EnSight 10.2 User Manual

1-27

1 Overview

1.2.10 Drag-n-Drop
You can drag (left click and hold the mouse button down, then move the mouse)
an object and drop (release the left mouse button) it onto a "target". The target can
be in the user interface (always available) or in the graphics window (will work
only if your graphics hardware supports the operation). The following drag and
drop actions are currently implemented:
Parts

Variables

Plots and Queries
Styles

1-28

When dropped in a viewport (user interface or graphics window) will make the
part visible in the viewport.
When dropped onto a group in the Parts List will make the part belong to the
group.
A constant variable dropped in the graphics window will create an annotation text
string with the value of the constant.
When scalars or vector variables are dropped in a viewport the parts with viewport
visibility True (regardless of their regular show/hide visibility status) will be
colored by the variable.
If you drop a scalar or vector onto a visible part the result will be that the part is
colored by the variable. Similarly, if you drop the variable onto a group in the
Parts list all the parts that belong to the group will be colored.
You can assign a query to a plotter by dropping the query on the plotter
From the Style manager you can drag/drop a style onto objects of the right type,
i.e., if you have a style that was saved for a curve you can drop it onto a curve on
a plotter.

EnSight 10.2 User Manual

1 Overview

1.3

Other Features

Server-of-Servers

Virtual Reality

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 9.8, Server-of-Server Casefile Format)
EnSight is fully capable of running multi-pipe display, virtual reality and
distributed rendering modes.
(see Section 11, Remote Display and Parallel Compositing)

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 be modified. Command files can be played
all the way through, or you can choose to stop the file and step through it line-byline.
(See How To Record and Play Command Files)

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.
(see Chapter 7, EnSight Python Interpreter)

Batch Processing

EnSight can be run in batch bringing up no visible windows (user interface or
graphics window) and producing output according to the command file processed
(see Use Batch)

Context Files

You can define a “context” and apply it to similar datasets.
(See How To Save/Restore Context)

Graphics

EnSight uses the OpenGL graphic libraries and is available on a multitude of
hardware platforms. The rendering can be done through the hardware or can be
performed in software.

Parallel
Computation

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

Distributed
Memory Parallel
Computation
Macros
Saving and
Archiving

Environment
Variables

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”.
You can define macros tied to mouse buttons or keyboard keys to automate
actions you frequently perform.
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)
You can control a number of aspects of EnSight (both client and server) with
environment variables.

EnSight 10.2 User Manual

1-29

1 Overview

(See How To Use Environment Variables)

1-30

EnSight 10.2 User Manual

1 Overview

1.4

Documentation
An Installation Guide is provided.
The on-line EnSight documentation consists of the EnSight Getting Started
Manual, How To Manual, User Manual, and Interface 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 - GUI Overview. This chapter describes the EnSight Graphic User
Interface.
Chapter 4 - List Panels. This chapter describes the various list panels, for parts,
variables, annotations, plots/queries, viewports, frames, etc.
Chapter 5 - 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 6 - Features. This chapter describes the features and functions available
through the Icon buttons of the GUI.
Chapter 7 - 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 8 - Variables and EnSight Calculator. This chapter describes the
selection and activation of variables, color palettes, and the creation of new
variables.
Chapter 9 - Preference and Setup File Formats. This chapter describes the
format of various preference files which the uses can affect.
Chapter 10 - EnSight Data Formats. This chapter describes in detail the format
of the various EnSight data formats.
Chapter 11 - Utility Programs. This chapter describes a number of unsupported
utility programs distributed with EnSight.
Chapter 12 - Parallel and Distributed Rendering. This chapter describes how
to configure EnSight for various VR configurations and for parallel rendering.
Chapter 13 - CEIShell. This chapter describes the EnSight Virtual
Communications Utility.
Chapter 14 - EnSight Networking Considerations. This chapter describes
various things that should be considered when running EnSight on a network.
Chapter 15 - EULA. This chapter contains the User agreements.
Cross References in the User Manual will appear similar to:
(see Chapter __

or

(see Section __

Clicking on these Cross References will automatically take you to the referenced
Chapter or Section.
EnSight 10.2 User Manual

1-31

1 Overview

How To...

Interface...

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.
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.ceisoftware.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.ceisoftware.com.

1.5

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:

1-32

Fax:

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

Email:

support@ceisoftware.com

EnSight 10.2 User Manual

2

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 EnVision 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 Graphic Images describes options for saving and printing graphic
images.
2.13 Saving and Restoring Animations 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.
2.16 Saving EnSight Graphics Rendering Window Size describes options for
precise resizing of your Graphics Rendering Window.
Note: Formats for EnSight related files are described in chapters 10 and 11.
Formats for the various Analysis codes are not described herein.

EnSight 10.2 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 accommodate 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

EnSight 10.2 User Manual

2.1 Reading and Loading Data Basics

in the ensight_reader_extension.map file found in the $CEI_HOME/ensight102/
site_preferences and/or in the EnSight Defaults Directory which is located

Figure 2-1
File Open Dialog - Simple Interface

at %HOMEDRIVE%%HOMEPATH%\(username)\.ensight102 commonly
located at C:\Users\username\.ensight102 on Vista and Win7, C:\Documents and
Settings\yourusername\.ensight102 on older Windows, and ~/.ensight102 on
Linux, and in ~/Library/Application Support/EnSight102 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 be one up from the current.
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.

Okay

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

EnSight 10.2 User Manual

2-3

2.1 Reading and Loading Data Basics
Cancel

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

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

Changes the Look in directory to be one up from the current.
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.

2-4

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.

Data Tab

Contains settings for file format and file names.
EnSight 10.2 User Manual

2.1 Reading and Loading Data Basics
Set

Format

Comments
Format Options
Tab

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

Other Options

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 the following:
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.
Each data reader may have its own set of format options.

EnSight 10.2 User Manual

2-5

2.1 Reading and Loading Data Basics
Time Options
Tab

Contains Time specific information.

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

Time Settings

SOS Options
Tab

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
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
Load All Parts

2-6

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
Click to read and load all of the parts associated with the file names specified and close the
dialog.

EnSight 10.2 User Manual

2.1 Reading and Loading Data Basics
Select Parts to
Load
Cancel

Click to read the data files specified, close the dialog and show the parts in the Parts list as
loadable (grayed out) parts. These parts can be loaded by performing a right click
operation.
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

If you right click on a grayed out part in the Parts list you can load (i.e., read it on
the server and show its element visual representation on the client). When you
load the part you can also specify the part description (if desired) as well as
specify the element visual representation. There are two basic part loader
windows. Details of these windows will be discussed below, and variants 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

If the part(s) in the Parts list is unstructured you will see the Unstructured Part Builder
dialog as shown above.

Structured Data

If the part(s) in the Parts list is structured you will see the Structured Part Builder Dialog.

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 10.2 User Manual

2-7

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.

Volume

Volume render all 3D elements and ignore all other elements.

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).

Use Default

This specifies that the part(s) should be loaded in the visual representation as defined by
the reader mapping file for the format specified.

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 as New Part

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.

Structured Data
Domain

2-8

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

EnSight 10.2 User Manual

2.1 Reading and Loading Data Basics
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.

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.

Load as New Part

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.
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
selection exceed the bounds of a given part, they are modified for that part so that its
bounds are not exceeded.
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.

(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
Section 5.1.1, Parts Quick Action Icons).

EnSight 10.2 User Manual

2-9

2.1 Reading and Loading Data Basics

• 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 7.1, Variable Selection and
Activation).

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.

Error reading data

2-10

EnSight 10.2 User Manual

2.1 Reading and Loading Data Basics

Problem

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

EnSight 10.2 User Manual

Probable Causes

Solutions

Format of the data is incorrect

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

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

Format the file according to
examples listed under EnSight
Variable Files (see Chapter 9,
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-11

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 unstructured or
structured grids. 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. All
licensed versions of EnSight read all three versions of Ensight formats, with the
exception of a special, bundled EnSight for Converge which reads only Converge
Case Gold translator output. 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 9,
EnSight Data Formats). The application ens_checker102 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

2-12

EnSight 10.2 User Manual

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
Set Case

Use the Case format to read EnSight6 or EnSight Gold data.
Select the casefile (typically .case) and click this button

Format Options Tab
Endian

Native, Big or Little-Endian. Since all modern platforms use the
Intel platform, which is little-endian we no longer automatically do
this check. Legacy files written from Unix platforms will need this
pulldown set to big-endian to read correctly.

(see How To Read Data)

EnSight 10.2 User Manual

2-13

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
Set geometry
Set results

Use the EnSight 5 format.
Select the geometry file (typically .geo) and click this button
Select the results file (typically .res), and click this button.

Format Options Tab
Set measured
Endian

Select the measured file and click this button.
Native, Big or Little-Endian. All modern platforms use the
Intel platform, which is little-endian. Legacy files from Unix
will be big-endian.

(see How To Read Data)

2-14

EnSight 10.2 User Manual

2.3 Other Readers

2.3 Other Readers
ABAQUS_ODB Reader
AcuSolve Reader
AUTODYN Reader
AIRPAK/ICEPAK Reader
ANSYS Reader
AVUS Reader
CAD Reader
Barracuda Reader
CFF Reader
CFX4 Reader
CFX5 Reader
CGNS Reader
CGNS-XML Reader
Converge_Input Reader
CTH Reader
EXODUS II Reader
FAST UNSTRUCTURED Reader
FIDAP NEUTRAL Reader
FLOW3D-MULTIBLOCK Reader
FLUENT Direct Reader
Inventor Reader
LS-DYNA Reader
MSC.DYTRAN Reader
MSC.MARC Legacy Reader
NASTRAN OP2 Reader
Nastran Input Deck Reader
OpenFOAM Reader
OVERFLOW Reader
PLOT3D Reader
POLYFLOW Reader
RADIOSS Reader
SDRC Ideas Reader
SILO Reader
Software Cradle FLD Reader
STAR-CD and STAR-CCM+ Reader
STL Reader
Synthetic Reader
Tecplot Reader
Vectis Reader
VTK Reader
XDMF Reader

User Defined
Reader
Description

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.
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

EnSight 10.2 User Manual

2-15

2.3 Other Readers

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
* Filtered elements are 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
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 EnSight Interface Manual. Samples, source code, makefiles, etc can be found
in the following location and its subdirectories:
On the CD: /CDROM/ensight102/src/readers
In installation
directory: $CEI_HOME/ensight102/src/readers
Start EnSight (or EnSight server) with the command line option (-readerdbg), for
a step-by-step echo of reader loading progress (see Command Line Start-up
Options).
ensight102 -readerdbg
The actual working user defined readers included in the EnSight distribution may
vary by hardware platform.

2-16

EnSight 10.2 User Manual

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/ensight102/src/readers/abaqus/README.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
Set geometry
Set results

Use the ABAQUS_ODB format.
Select the geometry file (typically .odb) and click this button
Not used

Format Options Tab

EnSight 10.2 User Manual

Set measured
Reader GUI

Select the measured file and click this button.
User controls as shown below are available:

Load Surface
Sets

Toggle ON (default) to load all Surface Sets

2-17

2.3 ABAQUS_ODB Reader

Load Node
Sets
Load “*All*”
Parts

Load Freq
Step

Load
Element
Faces
Load internal
decomposition
parts

Load
Analytical
Rigid Surface
parts
Load History
Data

Interpolate
History to
Constants

2-18

Toggle ON to load all Node Sets (default OFF).
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.
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.
Toggle ON to convert Surface Sets with 3D elements with
Face Sets into 2D elements using face specifications where
indicated by the ABAQUS dataset. (default ON).
Toggle ON to load internal decomposition sets (that show the
parallel decomposition of the ABAQUS solver) as EnSight
parts.(default OFF).
Toggle ON to load rigid surface parts as transient, rigid line
segments that can be extruded in 3 dimensions. This can be
done using a python script. Contact support@ensight.com for
details. (default OFF).
Toggle ON to load History data which will load either as
constants or as queries over time (default ON). Some datasets
contain history data at extremely high sample rates with large
number of xy data pairs. EnSight is not structured to be able to
handle large numbers of queries with a large number of data
pairs, and will abort the loading of history data if it encounters
a data pair with more than 3000 samples. The reader will
output a warning that it has aborted the history data read and
that you can override this number; set the environmental
variable on the server as follows: set
ENSIGHT_READER_MAX_QUERY_PAIRS to the
maximum number of pairs that you wish to allow and restart
EnSight.
History data is typically input to EnSight as queries (curves).
EnSight has the ability to use constant (single values at each
timestep) in ways that are not available to queries. If this is ON
then History variables will be interpolated as EnSight
Constants (if extrapolation is not necessary). If OFF then
History variables will be read in as constants only if there is an
exact one to one match of time values for each EnSight
timestep (Default OFF).

EnSight 10.2 User Manual

2.3 ABAQUS_ODB Reader

Skip Last
Frame if
Suspect

Smart
Uniform
Delta Time

If the ABAQUS solver crashes, it can dump out a variety of
variable values for the last FRAME in the ODB file that may
be spurious. Toggle this ON (default) to check the last
FRAME in a STEP for an increase in the number of variables
and, if so, skip it. Toggle this OFF to ignore warning signs and
load the data from the last frame. If suspect values are found in
the last FRAME, then NAN checking of each variable value is
turned on, with NANs returned as zero (Default ON).
Some ABAQUS STEPs have frame values that are constant
(and very small). Frame values are used by EnSight for time
steps and thus from this type of STEP are not monotonically
increasing in time and EnSight will skip these timesteps.
Toggle this ON, and EnSight will automatically convert time
values from selected ABAQUS STEPs into using a delta time
of 1.0 (default is ON).
Because EnSight is automatically changing the timestep
values, this will only be done to selected ABAQUS STEPs
(more may be added over time) The current list of these
includes only one ABAQUS STEP: "*STEP
PERTURBATION, *STATIC". As new STEPs are
encountered they may be added to this list and documented. If
a new STEP is encountered with non monotonically changing
time values that should be added to this list, please contact
EnSight support and send us an example dataset. And the
workaround is to toggle ON the other toggle “Uniform Delta
Time” which will make the delta time = 1.0 for ALL timesteps
for all ABAQUS Frames in all ABAQUS STEPs.

Uniform
Delta Time

Extrapolate
Variables to
Nodes

EnSight 10.2 User Manual

Because EnSight is automatically changing the ODB time
values, this Toggle has been added to allow the user to turn
this off and use the frame values as timestep time value in
EnSight.
Some ABAQUS STEPs have Frame values that are constant
(and very small). Frame values are converted to float values
and are used by EnSight for time steps. Time values may
therefore become not monotonically increasing in time and
then EnSight will skip these timesteps.
Toggle this ON, and EnSight will automatically convert the
ABAQUS Frame time values from all ABAQUS STEPs into
using a uniform delta time of 1.0. Because this changes the
ABAQUS ODB time values for ALL of the ABAQUS STEPs
it is by default OFF.
Variable values are extrapolated to the nodes using the
ABAQUS internal API from each element’s internal
integration points to the nodes from each element. The reader
then does a simple average of the nodal values from each
element. This has been demonstrated to give the same results
as ABAQUS CAE.

2-19

2.3 ABAQUS_ODB Reader

Use Section
Integration
Point
Console
Output

Instance
Step
Shell Section
Starting Part
Number

Shell elements include variable data for each section. This
reader allows the use of the First (default) or the Last section.
Shell elements include variable data for each of several
integration points. Choose max, min or average (default).
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
Choose an instance (1 to the number of instances). Default is
to load them all.
Choose a step (1 to number of steps). Default is to load all
non-frequency steps.
Which shell section to use (1 to number of shell sections).
Which part to begin loading (1 to number of parts). Default is
1 (load all parts).

Older version ODB
files

The EnSight odb reader will be able to read .odb files from 6.1 to the current
version using the upgrade utility. If upgrade is needed, the original odb file is read
in and left unchanged, while an upgraded copy is automatically written in the
same directory (user must have write permission in this directory).
UPGRADE_6_* is added to end of filename prefix, where the * is the current
library version, for example UPGRADE_6_14 for ODB library version 6.14. The
current library version can be seen in the file open dialog under the Data Tab,
when you choose the ABAQUS_ODB reader in the reader selection pulldown.
The reader version will appear just below the pulldown in the reader description
box. The first numbers (for example, 6.14-1) indicate the API (which corresponds
to solver version 16) and the release (which corresponds to release 1).

Shell Elements

In ABAQUS, many shell elements have sections and integration points. Sections
are regions such as top or bottom of a beam. Integration points are specified
locations on the sections. In contrast, EnSight elements have only one value per
element. So it is necessary to have a mapping scheme between the multiple
element values in ABAQUS and the single EnSight elemental value. Choose the
Format Options Tab in the data reader dialog to change the mapping of shell
elemental variable data from ABAQUS to EnSight.
Integration Point pulldown allows the choice of the max, min or average (default)
of the integration points at a shell element to use as the EnSight variable value.
The Use Section pulldown allows the choice of the first (default) or last section at
a shell element to use as the EnSight variable value.
To enter in a section number of your choosing (if there are more than two), simply
enter a value (1 to number of sections) into the Section field. Entering a value into
this field (default is empty) supersedes the choice in the pulldown.

Modal Data

2-20

Sometimes the analysis will have transient/static STEPs along with
FREQUENCY STEPS. Ensight can handle either transient/static or frequency

EnSight 10.2 User Manual

2.3 ABAQUS_ODB Reader

data, so by default, with mixed data, the FREQUENCY STEPs are skipped, and
only the transient/static STEPs are loaded.
If you want the only the modal data toggle ON the "Load FREQ STEP" toggle,
and the reader will use the first modal frequency STEP. Also, if, for example, you
know the modal FREQUENCY STEP, you can also select the step number by
entering it in the "STEP (1 to num)" field
Once your modal data is loaded, to visualize the modal displacement, select the
part(s) of interest, and displace by the displacement vector, U. Each modal
frequency is loaded in as a separate EnSight timestep, so step through EnSight
"times" to step through the frequencies. Similarly you can view the modal
velocity, V or the acceleration, A.
Each modal frequency is stored as a single value for a given EnSight
"timestep". You can access these EnSight constants as follows:
Modal Frequencies (single value constants) are stored in the constant, single value
variable, H_EIGFREQ. Modal Eigen values (single value constants) are stored in
the single value variable H_EIGVAL. Note for any given mode, H_EIGVAL is ( 2
* PI * H_EIGFREQ )^2 . These values are helpful, for example, to display the
frequency as an annotation that updates when the timestep is updated.
Modal Participation Factors (single value constants) are as follows:
H_PF1 - Participation factor, x-component
H_PF2 - Participation factor, y-component
H_PF3 - Participation factor, z-component
H_PF4 - Participation factor, x-rotation
H_PF5 - Participation factor, y-rotation
H_PF6 - Participation factor, z-rotation
Analytical Rigid
Surfaces

ABAQUS ODB data includes three Analytical Rigid Segments that do not have
variable data, do not deform, and only move rigidly in translation or rotation that
are of type
1. REVOLUTION - A rigid segment rotated about a point
2. CYLINDER - A rigid segment translated in a given direction
3. BSURF - A line segment used in 2D analysis
These parts are read in as line segments if the user toggles ON the Load
Analytical Rigid Surface parts toggle in the Format Options Tab in the data reader
dialog for the ABAQUS_ODB reader. These segments are translated and rotated
independently of the rest of the ABAQUS model using U and UR of the reference
node using EnSight's rigid body capability. These segments will displace and
rotate automatically according to their proscribed motion in the ODB file using
EnSight's rigid body implementation, so U and UR cannot be applied to the ARS
segments, and all variables are disabled for ARS segments. Conversely, you
cannot 'undisplace' an Analytical Rigid Segment. To get other parts to match the
automatic displacements / rotations of the ARS, you will need to turn on
displacements of your normal parts.

Analytical Rigid
Surfaces manual
creation

In order to turn the Analytical Rigid Segment into an Analytical Rigid Surface,
you can use EnSight's Extrude function. If the segment part has REV in the name,
then you'll want to rotate, and you can toggle ON to rotate about a part centroid,

EnSight 10.2 User Manual

2-21

2.3 ABAQUS_ODB Reader

and choose the part id of the rigid reference node corresponding to this ARS part,
pick the rotational degrees and the axis, and click Create to construct the extruded
rotational surface. Note that since the ARS segment is moving automatically, and
the rigid reference node is not moving automatically, if you want to track the
actual motion of the rigid revolution part, you will want to turn on displacements
for the Rigid Reference point part, then toggle on Displace Computationally so
that the rigid reference node displacements are used in the calculations. If the
segment part has CYL in the name, then you'll want to extrude the part in a given
direction, with a total translation. This extruded part should automatically move
correctly without any other steps.
Analytical Rigid
Surfaces automatic
creation using
Python tool

Should you want all of this done for you automatically, there is a python tool
included with EnSight that will automatically create all of your Analytical Rigid
Surfaces. As shown in the Figure below, simply click on the tools icon at the top
and choose the Create ARS icon under the Visualize folder. Simply fill in the
GUI and it will turn on computational displacements of the rigid reference nodes
automatically and just create the rigid reference surfaces as expected.

Figure 2-8
Analytical Rigid Surface Python Tool

Problems
If the default behavior of the reader is unexpected (that is, no parts loaded, too few
timesteps loaded, or variables not available) then reload the odb file and select the
Format Options Tab and choose Console Output: Debug. Then take a look at the
output in your server console.
Missing Parts

Are you missing parts? By default, EnSight does not load the nodesets. Toggle
this ON to load the nodal parts. By default, EnSight does not load parts whose
names containing ALL or All because these are often duplicate parts that double
the required memory and slow down the operation of the reader. Toggle ON the
Load *all* toggle to load these parts. If you have no parts loaded, take a careful
look at the console output (see below) and notice that all of the nodesets are
skipped, as is the ALL_ELEMENTS part, thus you have no parts loaded.
----------------------------------------------------------EnSight ABAQUS Parts

2-22

EnSight 10.2 User Manual

2.3 ABAQUS_ODB Reader
Total num Instances 1
Total num nodes 936
Total num elements 625
Choose 'Format options' tab in data reader dialog
To load or skip node or surface sets:
Toggle OFF 'Load Surface Sets'
Toggle OFF 'Load Node Sets'
To load or skip sets with ALL in their name:
Toggle OFF 'Load *ALL* Parts'
----------------------------------------------------------------------------------ABQ Ens
Part
Instance & Type
Number
Status
Num Num
Name
Elements
---------------------------------------1.
1. ALL NODES
Assm
0 Nodeset
2.
1. ALL NODES
Assm
1 Nodeset
3.
1. ASSEMBLY_CONSTRAINT-1_NODES
Assm
1 Nodeset
4.
1. ASSEMBLY_CONSTRAINT-1_POINT
Assm
0 Nodeset
5.
1. ALL ELEMENTS
Assm
1 Elemset
----------------------------------------------------------Number of regular ABAQUS parts = 5
Number of Analytical Rigid Surface parts = 0
Total number of Abaqus parts = 5
Total number of EnSight parts = 0
---------------------------------------------------------------------------------------------------------------------

Missing Timesteps

1
936
36
1
625

SKIPPED
SKIPPED
SKIPPED
SKIPPED
SKIPPED

Are you missing timesteps? Each ABAQUS FRAME is an EnSight timestep. If
the change in time between two successive frames is too small to represent as a
float value, then EnSight will skip it.
ABAQUS data is loaded in STEPs. Since EnSight has only timesteps (transient) or one
timestep (static) there is a bit of mapping that goes on to read in an odb dataset.
ABAQUS STEPs of type "*STEP PERTURBATION, *STATIC" STEP” are now loaded
with their timesteps incremented by 1.0.And the Toggle "Smart Uniform Delta Time" has
been added to turn this off and use the frame values (which are 2E-16). This is ON by
default. Warning: this automatically changes timestep time values. Since other STEPs may
also have very small delta time, the Toggle "Uniform Delta Time" is included so that the
time values can be made to increment by 1.0 for ALL STEPs of the ODB data. (default
OFF).
To pick a given ABAQUS STEP, for example, STEP 4 (1- based), simply enter 4 into the
"STEP (1 to num)" field.
Here is the details on the load steps and "times" and is consistent with ABAQUS handling
of .fil
Abaqus STEP is an EnSight Case. Each Abaqus FRAME is a time increment to the final
STEP value. The EnSight total time is a unique cumulative value for each EnSight
timestep that is monotonically increasing.
Each odb STEP is like a sequential, but separate analysis

Tot
time

EnSight 10.2 User Manual

STEP3
\
|<--- STEP 1 --->|<--STEP 2 -->||<-------- STEP 4 ------->|
|----------------+-------------++------------------------>|
|
100s|
175s||175+delta
375s|

2-23

2.3 ABAQUS_ODB Reader

STEP
time

|
|
||
|
|--------------->|------------>||------------------------>|
|
100s
75s||1e+36s
200s|

The ODB API reports data by STEP with each step having a series of FRAMES each
representing an EnSight timestep. EnSight use the Abaqus TOTAL TIME as our Solution
Time. Apparently, an Abaqus user can look at his status file and know what TOTAL
TIME relates to the STEP.
EXAMPLE
If we had a file with 3 ABAQUS STEPS, and 5 increments per step:
Notice the ABAQUS odb details in the left columns and the resulting
EnSight mapping on the right. The 'X' is a timestep that is
excluded from EnSight because there is no time change from the
previous step.
------------------- ABAQUS --------------------TOTAL "Time"
STEP "Time"
STEP #
FRAME #
---------------------------------0.0
0.0
0
0
0.1
0.1
0
1
0.3
0.3
0
2

|
|
|
|
|
|

---- EnSight --Step
Sol. Time
-----------0
0.0
1
0.1
2
0.3

0.3
0.8
1.3
1.8

1.0E-10
0.5
1.0
1.5

1
1
1
1

0
1
2
3

|
|
|
|

3
4
5
6

0.35
0.8
1.3
1.8

1.8
3.8
5.8
7.8

0.0
2.0
4.0
6.0

2
2
2
2

0
1
2
3

|
|
|
|

X
7
8
9

1.8
3.8
5.8
7.8

............. etc ................

Therefore, if you wanted to look at:
The 1st load case (STEP 0): Look at Ensight times 0 - 0.3
or EnSight steps
0-2
The 2nd load case (STEP 1): Look at Ensight times 0.35 - 1.8
or EnSight steps
3-6
The 3rd load case (STEP 2): Look at Ensight times 1.8 - 7.8
or EnSight steps
6-9

NOTE: Times that have no total time increment are dropped from
EnSight.
Times that have an extremely small increment (e.g. 1E-10) are
incremented larger so that the time can be represented as a
float.
For example, when you see the X in the left hand column below, this timestep is skipped
because you can see that the increment is essentially zero. A number of steps are skipped
below for that reason.
----------------------------------------------------------EnSight to ABAQUS Temporal Mapping Table
-----------------------------------------------------------EnS
EnS
ABQ
ABQ
ABQ
STEP
Soln
STEP
FRAME
STEP
#
Time
#
#
Time

2-24

EnSight 10.2 User Manual

2.3 ABAQUS_ODB Reader
------

--------

--------

---------

-------

0
0
1
0
0
1
2.22E-16
1
1
2.22E-16
X
2.22E-16
1
2
2.22E-16
X
2.22E-16
1
3
2.22E-16
X
2.22E-16
1
4
2.22E-16
X
2.22E-16
1
5
2.22E-16
2
0.01
1
6
2.22E-16
---------------------------------------------------------------------------------------------------------------------

Missing Variables

When you choose Console Output Debug, you can see the list of variables in the
console output and that some of the variables are skipped. Skipped variables
include the _MAG variables, which are vector magnitude that EnSight autocalculates for vector variables from the components. You can see that some of the
contact variables, which are part-specific are combined into one, single value.

Odd Part Shapes

When you read in your parts if the Surface Set parts seem to have full elements
showing and you only want the selected faces of the elements to be used to form
your parts, then reload your data and choose Load Element Faces in the Format
Options Tab of the Data Reader dialog.
Surface Set Part
Load Element Faces Toggle OFF
Load Element Faces Toggle ON

(see How To Read Data)

EnSight 10.2 User Manual

2-25

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/ensight102/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.
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 its 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 its 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
Set cas
Set dat

To use this reader, select the Fluent format.
Select the geometry file (typically .cas or .cas.gz) and click
this button. For transient data, use *.cas or *.cas.gz.
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
Other
Options

Select the measured file and click this button.

using the
current
Fluent reader

2-26

EnSight 10.2 User Manual

2.3 AIRPAK/ICEPAK Reader

Load Internal
Parts

Use Meta
Files

Load _M1
_M2 vars

Load all cell
types

Console
Output

Toggle this ON to load the Fluent Internal Parts. This will
show all 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.
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.
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.
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.
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.

EnSight 10.2 User Manual

2-27

2.3 AIRPAK/ICEPAK Reader

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-28

EnSight 10.2 User Manual

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.
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
Set file

Use the AcuSolve format.
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
Other
Options

Select the measured file and click this button.

Reset time
Extended
output
Mesh Motion
Unique parts

When toggle is on, time begins at 0.0 (default is off).
When toggle is on, console output will be verbose (default is
off).
When toggle is on, moving meshes are visible (default is on).
When toggle is on, a unique set of surfaces is shown in the part
list (default is off).
Enter the comma separated list of runs (3, 5, 10, 10:20:2), or
_all. (default is _none).

Additional
runs

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

EnSight 10.2 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/ensight102/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 theories) 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
Set file
(or results)

Use the Ansys Results format.
Select the geometry/results file (typically .rst, .rth, .rfl, or
.rmg) and click this button

Format Options Tab
Set measured

2-30

Select the measured file and click this button.

EnSight 10.2 User Manual

2.3 ANSYS Reader

Other
Options

Include Face/
Edge Parts
Include
NodeSet
Parts
Include local
elem res
comps (if
any)

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 any Face or Edge sets defined. These are some logical
set of particular faces and/or edges of full elements. Default is
off.
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 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 10.2 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 = 1 for 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

Regular Part
Creation
Convention

Var naming
convention

or any legal combination. example: for VonMises and Max
Shear only, use 18. Default is off
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
Use Content Field (if provided) - Variable names will be what
is in the Content field, if provided. If not provided, they willbe
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 10.2 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. This is a global averaging, so shared nodes are
affected by all parts that share a node.
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. This is a global averaging, so shared
nodes are affected by all parts that share a node.
Ave 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. This is a local averaging, so all
averaging is contained within each part.

If Sections,
which:

Geom weighted ave to node  - Element results
(whether centroidal or element nodal) will be averaged to the
nodes using geometry weighting. Thus will be per_node
variables in EnSight. This is a local averaging, so all averaging
is contained within each part.
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

Section Num

Separate Vars per Section - A separate variable will be created
for each section.
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 10.2 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. Supported only on Windows.

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

The File Selection dialog is used to specify which files you wish to read.
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
Set file

Use the Autodyn format.
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
Other
Options

Select the measured file and click this button.

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-34

EnSight 10.2 User Manual

2.3 AUTODYN Reader

Include Face/
Edge Parts
Include
NodeSet
Parts
Include local
elem res
comps (if
any)

Include
Tensor
derived
(VonMises,
etc.)

Include any Face or Edge sets defined. These are some logical
set of particular faces and/or edges of full elements. Default is
off.
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 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
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 = 1 for 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

Regular Part
Creation
Convention

Var naming
convention

or any legal combination. example: for VonMises and Max
Shear only, use 18. Default is off
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
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).

EnSight 10.2 User Manual

2-35

2.3 AUTODYN 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. This is a global averaging, so shared nodes are
affected by all parts that share a node.
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. This is a global averaging, so shared
nodes are affected by all parts that share a node.
Ave 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. This is a local averaging, so all
averaging is contained within each part.

If Sections,
which:

Geom weighted ave to node  - Element results
(whether centroidal or element nodal) will be averaged to the
nodes using geometry weighting. Thus will be per_node
variables in EnSight. This is a local averaging, so all averaging
is contained within each part.
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

Section Num

Separate Vars per Section - A separate variable will be created
for each section.
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)

2-36

EnSight 10.2 User Manual

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/ensight102/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
Set grid
(or file)
Set solution

Use the AVUS or AVUS Case format.
Select the geometry file (typically .grd) and click this button
(or select the .case file for AVUS Case)
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)

EnSight 10.2 User Manual

2-37

2.3 Barracuda Reader

Barracuda Reader
Overview
This reader inputs the format from the Barracuda solver by Computational
Particle Fluid Dynamics (CPFD). This data traditionally has a large number of
changing particle points within a static geometry composed of 2D walls and 3D
fluids. This reader optimizes the geometry to only reload the particles each
timestep, thus improving performance.
GMV.xxxxx files contain the transient data where x is a digit (0-9) representing
the timestep. In addition, there are a number of .gmv files, some of which must be
present in the folder with the GMV files: 00cells.gmv, 00drawcells.gmv,
00gridstl.gmv, 00mat.gmv, 00nodes.gmv, and 00poly.gmv. The 00gridstl.gmv file
can be read separately to view the STL geometry (no variable, fluids, nor discrete
particles), and the 00poly.gmv can be read separately as well to view the 2D
polygon geometry (no variable, fluids, nor discrete particles).
Please visit http://cpfd-software.com/ for more information about this solver.
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
Set File

Use the Barracuda format.
Select any one of the transient files (e.g. GMV.00000) and
click this button and all of them will be loaded.

Format Options Tab

2-38

Set measured
Reader GUI

Select the measured file and click this button.

Include
Polygon
Parts
Read Single
GMV File

Include polygon parts will include parts with polyhedral and/
or polygon elements. Default is off.
Toggle this On to read only the file you have selected and only
the timestep represented by this file will be available. If off,
this will read all the Gmv files as a transient dataset, when you
select only one. Default is off.

EnSight 10.2 User Manual

2.3 Barracuda Reader

Console
Output

Normal - Minimal console output, only for errors.
Verbose - Normal output plus information about the model.
Debug - Full information for the developer to diagnose a
problem. Use this output to help to diagnose a problem or to
send it to CEI.

(see How To Read Data)

EnSight 10.2 User Manual

2-39

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), Pro/Engineer (.prt,
.asm), 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/ensight102/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
Set File

Use the CAD format.
Select the CAD geometry file and click this button

Format Options Tab
Set measured
Reader GUI

2-40

Select the measured file and click this button.

EnSight 10.2 User Manual

2.3 CAD Reader

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

CAD Format

Surface
Tolerance in
degrees
Normal
Tolerance in
degrees
Max edge
length in mm
Save
translated
STL file to
STL ASCII
file tolerance

Debug - Messages indicating progress through the reader and
useful for diagnosing problems
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, ProE, STEP, Unigraphics, and STL
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
The maximum angle in degrees between two normals on two
adjacent facet nodes. Default value: 25. It is a floating point
value.
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)
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
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 10.2 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/ensight102/src/readers/cff

2-42

EnSight 10.2 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/ensight102/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
Set cfx4 dmp

Use the CFX-4 format.
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 10.2 User Manual

2-43

2.3 CFX5 Reader

CFX5 Reader
Overview
Reads a CFX results (.res) file. Currently reads version 16.1-0 and earlier.
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
Set file

Use the CFX-5 format.
Select the geometry/results file (.res) and click this button

Format Options Tab
Set measured
Reader GUI

Select the measured file and click this button.

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 -

Variable
Boundary
Correction

Read
Regions?

2-44

Level 3 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.
No - (default) - Do not read Regions.
YES - Read Regions.

EnSight 10.2 User Manual

2.3 CFX5 Reader

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
that the solver will write mesh information to each .trn file.
Failure to do this results in a static, unmoving mesh over time.
No - (default).

Particles as
Part?

Yes - Coordinates only.
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 10.2 User Manual

2-45

2.3 CGNS Reader

CGNS Reader
Overview
Legacy reader

There are three CGNS readers in EnSight: this one (CGNS, which is a secondary reader),
the preferred CGNS-XML Reader which is the default for .cgns files and a legacy,
unsupported reader (CGNS-Legacy) which is unavailable by default, but can be made
visible in the list of readers in the data section of the preferences.

Some information on this reader is available at:
$CEI_HOME/ensight102/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
Set cgns

Use the CGNS format.
Select the geometry/results file (typically .cgns) and click this
button. For models contained in multiple files, wildcards or a
special executive file can be used here. See the Special Notes
section below.

Format
Options
Tab

Set measured

2-46

Select the measured file and click this button.

EnSight 10.2 User Manual

2.3 CGNS Reader

Include Face/
Edge Set
Parts
Include
NodeSet
Parts
Include local
elem res
comps (if
any)

Include
Tensor
derived
(VonMises,
etc.)

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 any Face or Edge sets defined. These are some logical
set of particular faces and/or edges of full elements. Default is
on.
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 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
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 = 1 for 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

Regular Part
Creation
Convention

EnSight 10.2 User Manual

or any legal combination. example: for VonMises and Max
Shear only, use 18. Default is on.
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

2-47

2.3 CGNS Reader

Element Vars
as

Single element
values

Averaged to node
values

Geom weighted
average to node
values

Ave to node values


Geom weighted
ave to node 

2-48

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.
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. This is a global
averaging, so shared nodes are affected
by all parts that share a node.
Element results (whether centroidal or
element nodal) will be averaged to the
nodes using geometry weighting. Thus
will be per_node variables in EnSight.
This is a global averaging, so shared
nodes are affected by all parts that share
a node.
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. This is a local
averaging, so all averaging is contained
within each part.
Element results (whether centroidal or
element nodal) will be averaged to the
nodes using geometry weighting. Thus
will be per_node variables in EnSight.
This is a local averaging, so all
averaging is contained within each part.

EnSight 10.2 User Manual

2.3 CGNS Reader

Spatial
Decomp
Multiple File
Search

Normally, a single cgns file is specified and read. Namely, the
model is neither decomposed spatially into more than one file,
not temporally into more than one file. Thus the first option is
the default. However, when a model is spatially decomposed,
it can be read as long as it conforms to one of the other three
options below. (Note: this is not for temporally partitioned
data. See the Special Notes below this table for how to specify
that situation.)
Use file specified
Opens only the file you specify. This is
the default.
Numbered in same Opens and combines data from all
dir
filenames with the same pattern, but
different ending numbers, that are in the
same directory.

Same name in
numbered dirs

Numbered in
numbered dirs

Doing
Structured as:

Structured

Unstructured

Var naming
convention

Use Content Field
(if provided)

Use VKI dataset
name

EnSight 10.2 User Manual

file.cgns.1 <= specify this one
file.cgns.2
...
file.cgns.9
Opens and combines data from all
filenames with the same name, but in
different numbered subdirectories.
dir1/file.cgns <= specify this one
dir2/file.cgns
...
dir9/file.cgns
Opens and combines data from all
filenames with the same pattern, but
different ending numbers, that are in
different numbered subdirectories.
dir1/file.cgns.1 <= specify this one
dir2/file.cgns.2
...
dir9/file.cgns.3
will cause originally structured parts to
be created as structured parts in
EnSight. This is the default.
will cause originally structured parts to
be created as unstructured parts in
EnSight.
Variable names will be what is in the
Content field, if provided. If not
provided, they willbe the VKI dataset
name. This is the default.
Variable names will be the VKI variable
dataset name (which are reasonably
descriptive).

2-49

2.3 CGNS Reader

If Sections,
which:

Section Num

Special Notes:

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
The section number entered in the field
(below)
below will be used
Separate Vars per
A separate variable will be created for
Section
each section.
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.

Special file input methods for temporally decomposed models. Namely, a file
per timestep. Possible file input methods:
1) Normally, a single .cgns file would be specified.
Thus for a non-decomposed model, or to view one particular time step, you
would enter the desired file.
2) If multiple .cgns files exist because of transient results, you can use a
wildcard (asterisk) in the name of the file, or subdirectory.
ex 1) For the situation where multiple .cgns files reside in the same directory:
/mydirectory/cfd_out.cgns.1
cfd_out.cgns.2
specify: /mydirectory/cfd_out.cgns.*
ex 2) For the situation where multiple .cgns files with the same name reside in
their own subdirectories:
/mydirectory/sub1a/cfd_out.cgns
/sub2a/cfd_out.cgns
specify: /mydirectory/sub*a/cfd_out.cgns
ex 3) For the situation where multiple .cgns files with different names reside in
their own subdirectories:
/mydirectory/sub1a/cfd_out.cgns.1
/sub2a/cfd_out.cgns.2
specify: /mydirectory/sub*a/cfd_out.cgns.*
Note that, in general, you can't have a mixture of these two examples with this
method. Namely, the following cannot be properly specified with this method:
/mydirectory/cfd_out.cgns.1
/sub2a/cfd_out.cgns.2
You would need to either copy the .cgns file in the subdirectory to the data
directory, or you will need to create a subdirectory for each .cgns file in the data
directory, and move the .cgns files into those subdirectories. You could
obviously take advantage of symbolic links to avoid actually moving any data.
Your other alternative is to use method 3) below.
HOWEVER, having said that, there is one special case where you can use this
method with the final file not being in the pattern subdirectories.

2-50

EnSight 10.2 User Manual

2.3 CGNS Reader

Special case requirements:
1. All but the last file is in the pattern subdirectories.
2. Each of the files in the subdirectories must have the same name, and it must
be the same as the one in the parent directory.
Example:
/mydirectory/sub1a/cfd_out.cgns
/sub2a/cfd_out.cgns
cfd_out.cgns
specify: /mydirectory/sub*a/cfd_out.cgns
and the
/mydirectory/sub1a/cfd_out.cgns,
/mydirectory/sub2a/cfd_out.out
files will be loaded.
Then the
/mydirectory/cfd_out.cgns
file will be loaded.
3) You can create a special executive file in which you list all of the .cgns files.
This would allow them to be placed in or anywhere below the data directory.
Thus, you could handle the mixture discussed in 2) above.
Rules for this special file:
a. The file must be named exactly: MULTILPLE_CGNS
b. The .cgns files must be one per line in this file.
c. They must NOT have a full path, because the path to the
MULTIPLE_CGNS file will be prepended to them.
d. There is no concept of comment lines, so no extraneous lines (even empty
lines) are allowed.
ex 1 above, specified in this manner:
/mydirectory/cfd_out.cgns.1
cfd_out.cgns.2
MULTIPLE_CGNS
where MULTIPLE_CGNS file would contain just 2 lines, like:
-----------------dashed lines are NOT in the file
cfd_out.cgns.1
cfd_out.cgns.2
-----------------ex_2 above, specified in the manner:
/mydirectory/sub1a/cfd_out.cgns
/sub2a/cfd_out.cgns
MULTIPLE_CGNS
where MULTIPLE_CGNS file would contain just 2 lines, like:
-----------dashed lines are NOT in the file
sub1a/cfd_out.cgns
sub2a/cfd_out.cgns
-------------

EnSight 10.2 User Manual

2-51

2.3 CGNS Reader

ex_3 above, specified in the manner)
/mydirectory/sub1a/cfd_out.cgns.1
/sub2a/cfd_out.cgns.2
MULTIPLE_CGNS
where MULTIPLE_CGNS file would contain just 2 lines, like:
------------dashed lines are NOT in the file
sub1a/cfd_out.cgns.1
sub2a/cfd_out.cgns.2
------------And for the mixed mode situation:
/mydirectory/cfd_out.cgns.1
/sub2a/cfd_out.cgns.2
MULTIPLE_CGNS
where MULTIPLE_CGNS file would contain just 2 lines, like:
------------dashed lines are NOT in the file
cfd_out.cgns.1
sub2a/cfd_out.cgns.2
-------------

(see How To Read Data)

2-52

EnSight 10.2 User Manual

2.3 CGNS-XML Reader

CGNS-XML Reader
Overview
There are three CGNS readers in EnSight: this one, the default CGNS Reader, and a
legacy, unsupported reader (CGNS-Legacy) which is unavailable by default, but can be
made visible in the list of readers in the data section of the preferences.
The CGNS-XML reader reads in a single .cgns file or a single.cgnsxml file. The cgnsxml
file is just an XML file is described below and defines various ways to read data, including
spatially decomposed .cgns files.
Limitations

The reader has the following limitations.
See the following file for current information on this reader.
$CEI_HOME/ensight102/src/readers/cgns-xml/README

Data Reader
Simple Interface
Data Load

Load your .cgns file using the Simple Interface method.

Advanced Interface
Data Load

Load your .cgns file using the Advanced Interface method.
Data Tab
Format
Set cgns/xml

Use the CGNS-XML format.
Enter your .cgns filename or the .cgnsxml filename.

Format Options Tab
Set measured

EnSight 10.2 User Manual

Select the measured file and click this button.

2-53

2.3 CGNS-XML Reader

Format
Options

The following options are customized for the reader:

Ignore boundary conditions - If toggled on, boundary
condition parts will not be loaded (default OFF).
Use part groups - If toggled on, parts will be placed into
groups (default ON).
Simple part names - If toggled on, parts will be named without
part number (ie. _00001, _00002, etc) appended. Default is
OFF.
Simplified .cgns file input - If toggled on, and a single .cgns
file is in use, the part grouping is turned off and simple part
names are turned on (default is ON).
Converge changing constants to scalars (default is ON). When
a zonal constant changes between zones, this "zonal constant"
is converted to a scalar variable (rather than per-case
constant).
Show dimensioned variables in list (default is ON). This will
show variables in the variable list that have been defined in the
cgnsxml file.
Show reference variables in list (default is OFF). This will
show reference variables in the variable list that have been
defined in the cgnsxml file.
Console Output - Can control amount of output that comes to
the console. Options are: Normal, Verbose, or Debug
CGNS base to read - If a CGNS file has more than one base
this allows specific bases to be read. The CGNS base is equal
to (1-#bases). By default, all are read (-1)
Spatially
decomposed

EnSight can start up in a parallel mode where each server is responsible for a
portion of your CGNS file. If you have a single CGNS file, then the CGNS reader
does a round-robin assignment of parts to servers. If more servers than parts, then
some servers will have no parts. If less servers than parts, then some servers will
be responsible for multiple parts.
If you have multiple CGNS files (e.g. a spatially decomposed or partitioned
dataset), then the reader requires a .cgnsxml file which describes the relationships

2-54

EnSight 10.2 User Manual

2.3 CGNS-XML Reader

between the individual blocks in the CGNS file and EnSight Parts and Groups.
The file itself is encoded in XML. The reader on each Server (in parallel SOS
mode) reads the .xml file and does a round-robin on the parts to assign to the
servers. The algorithm is biased such that each reader opens as few CGNS files as
possible. If a CGNS zone, section, or boundary condition is not specified in the
.xml file then it will not be read in.
The example below forms parts and groups from CGNS entities. A part can be a
simple CGNS entity (Zone, section, boundary condition surface-See part
name="Inlet_zone0) or it can be multiple entities combined into one (See part
name="blade1"). Parts can be grouped (See group name="Shroud") so that you
can select and operate on all grouped items within EnSight or you can expand the
group and operate on the parts individually within the group.
CGNSXML
example

XML Tags:





























































EnSight 10.2 User Manual

can contain  or  objects

can contain  or  objects

can contain  objects

2-55

2.3 CGNS-XML Reader
Tag attributes:



name required and maps to the EnSight part name.
sym_axis optional and specifies an axis over which the part has
rotational symmetry.
sym_count optional and specifies the number of copies of the object that
make up 360 degrees.
autoload optional and if set to "0", specifies that the part should not be
autoloaded if the user selects "Load all parts".
sect optional and specifies that the part comes from a specific CGNS
zone section.
boco optional and specifies that the part comes from a specific CGNS
zone boundary condition.

name required and is currently only used internally by the reader.
(for now just set to zone####, where #### is a 0 prefilled zone number
such as 0001)
base required and specifies the CGNS base number
zone required and specifies the CGNS zone number
type requried and specifies "1" = structured zone, "0" = unstructured zone
file required and specifies the CGNS file to extract information from
faces optional, but if specified and the zone is structured it specifies that
the zone should be read as the noted (2D) faces of the zone instead of the
volumetric elements. i=min I axis, I=max I axis, etc.
cgns2xml utility

cgns2xml is a simple example xml file generation utility found in
$CEI_HOME/ensight102/machines/PLATFORM, where PLATFORM is the
hardware and os where you are running EnSight. This utility can be used to take a
list of .cgns files and generate a basic .xml file from them. The command line
looks like:
cgns2xml {infilelist} {outfile}
infilelist is the name of a file that contains the list of the .cgns files to
read. If the filename is '-', the list will be read from stdin, one filename per
line. If a filename of 'verbose' is given, verbose mode will be toggled on.
outfile is the name of the output .xml file. If the filename is '-', the
output will be sent to stdout.
(see How To Read Data)

2-56

EnSight 10.2 User Manual

2.3 CGNS-XML Reader

EnSight 10.2 User Manual

2-57

2.3 Converge_Input Reader

Converge_Input Reader
Overview

Details

Reads the input file (inputs.in) and other files in the same directory in order to
allow inspection, verification, and visualization of the input setup prior to the
ConvergeCFD solver. The reader will import the required files in order to create
the surfaces used for the Converge solver, along with a select number of variables,
such that user can visualize the boundary values and the movement of the surfaces
over time. The reader will generate the surface, movement, and boundary values
necessary for visualization.Also, if the model contains a spatially varying
variable, an additional point part will be created to visualize the spatially varying
boundary.
The reader looks for input.in file and if exists, it reads the crank_flag (1 time units
are in crank angle, and 0 time units in seconds).It reads start_time and end_time of
the simulation and chooses a time interval corresponding to a 0.5 degree crank
angle.These time steps in crank angles are converted into seconds and returned as
solution times which we see as Analysis_time in EnSight.
The reader then looks for the engine.in file. The presence of this file indicates that
it is IC engine case. The reader then gets the values of stroke, bore, connecting rod
length and rpm from the engine.in file and then finds the intake_lift and exhaust
lift.in files for intake and exhaust lift values (these are transient constants and are
used to make intake and exhaust translating parts to translate).
Note that if the engine.in file is missing, it indicates the analysis is a generic CFD
analysis.
The reader then looks for boundary.in file to get the boundary conditions for each
part, the number of parts and the part names. The boundary.in file also has rigid
body motion (for IC engine cases only translations for piston motion, intake and
exhaust lift) using rigid body flags. The boundary.in file contains the names of
other files containing other boundary conditions.
The reader then gets the geometry (nodes, elems, ids) from the surface*.dat file(s).
The boundary.in file specifies other files which contain variable information. The
reader must interpolate the variable start and end times in these variable files to
match the other timesteps. The reader does linear interpolation making use of the
720 degree cyclic nature in order to obtain variable values for all time steps.

Rigid body motion

Piston motion is identified by the $ symbol in the boundary.in file. The piston and
crevice (if it exists) follow this motion. Translating intake parts and exhaust parts
translations are found using the file names intake_lift.in and exhaust_lift.in
respectively. Simple rigid body motion is created by algebraic sum of each
original coordinate value and the product of direction component and motion
value at particular time step (piston movement, intake lift or exhaust lift
depending on the kind of motion). More complex, general rigid body motion is
also available and it uses the supplied direction cosines converted into Euler
angles.

Limitations

The reader uses the inputs.in file to determine the directory where the data files
are located. It expects that the names of inputs.in, boundary.in, engine.in,
intake_lift.in and exhaust_lift.in are unaltered.
The reader was built with the primary intention of visualizing In-cylinder engine
models. The reader is expected to read in arbitrary motion models, as well as

2-58

EnSight 10.2 User Manual

2.3 Converge_Input Reader

spatially varying boundary conditions. Currently, only Temperature, Pressure, and
Total Pressure spatial variables are imported into EnSight. For In-Cylinder
models, constants are imported for Bore, Stroke, Con_rod_length, RPM,
Intake_Lift, Exhaust_Lift, Piston_motion, Crank_angle, and Analysis_Time.
For more info, see

$CEI_HOME/ensight102/src/readers/converge_input/

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

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

Load your geometry/results file (must be named inputs.in) using the Simple
Interface method.

Advanced Interface
Data Load

Load your geometry/results file (must be named inputs.in) using the Advanced
Interface method.
Data Tab
Format
Set .inputs.in
file

Use the Converge_input format.
Select the Converge_input file (must be inputs.in) and click
this button

Format Options Tab
Moving
Liner

Console
Output

Default is OFF. If set, the liner will be defined as a changing
coordinates part, which effectively compresses and expands
the liner part in conjunction with the movement of the piston.
This option is valid only for In-cylinder engine models.
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

Set measured

Debug - Detailed output and progress through the reader
routines often valuable for understanding and reporting
problems.
Select the measured file and click this button.

(see How To Read Data).

EnSight 10.2 User Manual

2-59

2.3 CTH Reader

CTH Reader
Overview
Reads a Spymaster .spcth file.
See the following file for current information on this reader.
$CEI_HOME/ensight102/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
Set spcth*

Use the CTH format.
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

2-60

Set measured
Reader GUI

Select the measured file and click this button.
User controls as shown below are available:

SOS Autodistribute

When running EnSight in SOS mode, turn this ON (default) to
tell the reader that you want it to intelligently distribute the
data among the servers. Turn it off if you have already
distributed the spcth files into different directories, or on
different machines and want to use a Case SOS file to assign
the spcth file(s) to EnSight Server(s) manually.

EnSight 10.2 User Manual

2.3 CTH Reader

Open files
one at a time

Use Ghosts

Console
Output

(Set) Params

When running EnSight in SOS mode, turn this ON to tell the
reader that you want it to only open one of the spcth files at a
time. When this is OFF (default) every server process may
open a number of the files simultaneously. This could be a
problem if you have a thousand files and a thousand servers
and your process reaches a limit with too many files opened at
once.
Ghosts are invisible elements between the Server geometries
that allow for interpolation of data results rather than
extrapolation. Ghosts can be
inner (default) - use only the inner ghosts between blocks
all - use both inner as well as ghosts around blocks
none - no ghosts
normal - read in ghosts as normal cells.
outer zero - read in the inner and outer, but zero the variable
values on the outer locations. This is useful to create end caps
on the isosurfaces.
Normal - Normal console output
Verbose - Extra output useful to the user to understand their
data better.
Debug - Extra output often useful in debugging problems.
Allows user to enter parameters to change the behavior of the
reader, often for debugging purposes. For example to limit the
number of blocks in the part to 102, enter the following:
-numblocks 101

Special Variables

EnSight’s CTH reader has several special variables useful for understanding SOS
data. FILE_ID is the file ID number for each cell. BLOCK_ID is the block index.
And SERVER_ID is the server that has the data.

SOS details

You can start up SOS using ceishell, or the legacy Case SOS file, or the legacy
resources file (.res) file, each discussed elsewhere in this manual.
Reader-distribute is the default behavior of EnSight. In Reader Distribute mode,
if you have more files than servers, files are distributed to servers in a round-robin
fashion according to file size to even the load. If you have more servers than files,
servers are allocated to files according to total file size per server. In Reader
Distribute mode, all files must be available to all servers.
Shown below are GUI images showing sample user input for a sample SOS read
of 8 spatially distributed spcth files into EnSight SOS using a resource (.res) file.
If you decide that you want to manually distribute the files, then you must move
the sets of files into separate directories, create the SOS casefile with different
directories and the filename* casefile, and toggle the reader SOS auto-distribute
OFF in the Format Options above.
See the Problems section of the Use Server of Servers for more tips problemsolving your SOS visualization.

EnSight 10.2 User Manual

2-61

2.3 CTH Reader

(see How To Read Data)

2-62

EnSight 10.2 User Manual

2.3 EXODUS II Reader

EXODUS II 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, and they are installed with EnSight.
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

Loading Data

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.

Summary

Selecting the first file of any multi-file Exodus dataset will cause the reader to
load the entire dataset. Selecting a non-first file of a spatially decomposed or a
temporally decomposed dataset will cause the reader to load only that file. If the
user wishes to load only the first file, the “Read Selected File Only” toggle must
be turned ON and that file selected. If a dataset is both spatially and temporally
decomposed and a non-first file is selected, only the selected spatial
decomposition will be loaded and it will be loaded for all time steps.

Single file - no
decomposition

If the file is not decomposed spatially nor temporally, then you will have only one
Exodus file. Selecting this file will load all of the geometry and variables over all
time. The file will be named something like file.e .

Spatially
decomposed files

If the files are decomposed only spatially as shown below (each file contains a
portion of the geometry over all time), then EnSight will behave as follows:
a. To load all the files automatically, choose the first file.
b. To load a particular file, choose that file. If only the first file is desired toggle
ON the “Read Selected File Only” reader option.
file.e.4.0
file.e.4.1
file.e.4.2
file.e.4.3

Temporally
decomposed files

If the files are decomposed only temporally as shown below (each file contains all
the geometry but only for a subset of the total time), then EnSight will behave as
follows:
a. To load all the files automatically, choose the first file.
b. To load a particular file, choose that file. If only the first file is desired toggle
ON the “Read Selected File Only” reader option.
file.e
file.e-s0002
file.e-s0003

EnSight 10.2 User Manual

2-63

2.3 EXODUS II Reader

...Spatially and
Temporally
decomposed files

If the files are decomposed spatially and temporally, as shown below, then there is
a portion of the geometry in each file (indicated by 4.0, 4.1, 4.2, and 4.3) and a
portion of the total time range in each file (indicated by s0002, and s0003) as
shown below. EnSight will behave as follows:
a. To load all the files automatically, choose the first file.
b. To load only one portion of the geometry, choose any non-first file (for
example: choosing file.e.4.1 will load the .1 geometry over all time steps,
choosing file.e-s0002.4.0 will load the “.0” geometry over all time steps). Note
that EnSight loads all time steps of the selected spatial decomposition.
c. To read only one file, choose the file and toggle ON the “Read Selected File
Only” reader option.
file.e.4.0
file.e.4.1
file.e.4.2
file.e.4.3
file.e-s0002.4.0
file.e-s0002.4.1
file.e-s0002.4.2
file.e-s0002.4.3
file.e-s0003.4.0
file.e-s0003.4.1
file.e-s0003.4.2
file.e-s0003.4.3

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.

2-64

EnSight 10.2 User Manual

2.3 EXODUS II Reader
More info

See the following file for current information on this reader.
$CEI_HOME/ensight102/src/readers/exodusII/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)
using the Advanced Interface method.

Data Tab
Format
Set exo

Use the Exodus II format.
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, select the first file to load all of the data.

Format Options Tab
Set measured

EnSight 10.2 User Manual

Select the measured file and click this button.

2-65

2.3 EXODUS II Reader

Reader GUI

When you choose Exodus reader, and toggle on the Advanced
interface button, then click on the format options tab, you will
see a number of options for controlling the reader behavior.
Each of the choices in the data reader dialog has a
corresponding Environment variable described below that you
can set to control the default behavior. If you find yourself
repeatedly toggling on or off choices in the Format Options
tab of the data reader dialog, consider setting specific
Environment variables to change the default behavior of.the
reader.

Read
Distribution
Factors

Sets in Exodus can have distribution factor weights. If this is
ON (default ON) then distribution factors will be read in as
variables defined only on Set parts. The Environment variable
ENSIGHT_EXODUS_DF can be used to set the default value
(1 is ON, 0 is OFF).
Toggle ON (default) to read Side set parts. The Environment
variable ENSIGHT_EXODUS_READ_SIDESETS can be
used to set the default value (1 is ON, 0 is OFF).
Toggle ON (default) to read Node set parts. The Environment
variable ENSIGHT_EXODUS_READ_NODESETS can be
used to set the default value (1 is ON, 0 is OFF).

Read Side
Sets
Read Node
Sets

2-66

EnSight 10.2 User Manual

2.3 EXODUS II Reader

Read
Element Sets

Read Face
Sets
Read Edge
Sets
Read node
and element
maps

Verbose
Mode

Read higher
order
elements

Read
constant
variables

NAN filter
input data

EnSight 10.2 User Manual

Toggle ON (default) to read Element set parts. The
Environment variable
ENSIGHT_EXODUS_READ_ELEMENTSETS can be used
to set the default value (1 is ON, 0 is OFF).
Toggle ON (default) to read Face set parts. The Environment
variable ENSIGHT_EXODUS_READ_FACESETS can be
used to set the default value (1 is ON, 0 is OFF).
Toggle ON (default) to read Edge set parts. The Environment
variable ENSIGHT_EXODUS_READ_EDGESETS can be
used to set the default value (1 is ON, 0 is OFF).
Toggle ON (default) to read node and element ids or labels
(referred to in Exodus as node maps or element maps). There
is no guarantee (particularly if using spatially decomposed
Exodus files) that the node and element labels will be unique.
If this option is toggled OFF then EnSight will ignore the
labels in Exodus file and generate an internal numbering
scheme guaranteed to have unique node and element ids. The
Environment variable
ENSIGHT_EXODUS_USE_NODEMAPS can be used to set
the default value (1 is ON, 0 is OFF).
Toggle ON (default OFF) to output more detailed information
to the server console. The Environment variable
ENSIGHT_EXODUS_VERBOSE can be used to set the
default value (1 is ON, 0 is OFF).
Toggle ON (default ON) to preserve higher order elements.
Toggle OFF to down convert these elements to simpler
elements (e.g. convert a HEX20 into a HEX08). The
Environment variable
ENSIGHT_EXODUS_USE_HIGHERORDERELEMENTS
can be used to set the default value (1 to preserve higher order
elements and to 0 to convert these elements to simpler
elements.
Toggle ON (default ON) to load the variables that have a
single value at each timestep (called Constants in EnSight).
The Environment variable
ENSIGHT_EXODUS_READ_CONSTANTS can be used to
set the default value (1 to load constant variables and 0 to not
load them).
Toggle ON to check all floats (geometry as well as variables)
for IEEE nans and set to zero if nan (default ON). The
Environment variable ENSIGHT_EXODUS_CHECK_NANS
can be used to set the default value (1 to check all floats and 0
to not check floats).

2-67

2.3 EXODUS II Reader

Clip
Overlapping
timesteps

Epsilon

Read
Selected File
Only

Use Undef
value for
missing
variables

Read element
attribute vars

2-68

EnSight must have monotonically increasing time values in
each successive timestep. Exodus files sometimes have
overlapping timesteps. Toggle this ON, and when overlapping
times are encountered, EnSight will truncate the former values
and use the latter timesteps to construct the timeline.
If this is toggled OFF (default) and EnSight encounters
duplicate time values in subsequent timesteps it will apply the
epsilon value (see Epsilon below) and increment the latter
timestep so it remains monotonically increasing. With this
option toggled OFF, EnSight will retain all timesteps but
change the time values and is therefore not recommended. The
Environment variable
ENSIGHT_EXODUS_CLIP_TIMESTEP_OVERLAP can be
used to set the default value (1 to truncate the timesteps with
overlapping time ranges, and 0 to keep all timesteps).
A delta time value (default 1.0) to be substituted when a nonincreasing delta time float value is encountered. If the reader
detects two sequential time values that are not increasing the
later solution time value will be set to the earlier time plus this
epsilon value. This will have a cascading effect, shifting other
solution times later as well. This is useful when the solution
times are all the same value in the Exodus dataset. Set the
Environment variable ENSIGHT_EPSILON to a positive float
value to change the default value.
Toggle ON to read one and only one file which is the selected
file. Toggle OFF (default) to allow automatic pattern
recognition (and loading) of certain categories of file naming
schema as discussed in the beginning of this section.
ENSIGHT_EXODUS_READ_SELECTED_FILE_ONLY can
be used to set the default value ( 1 to read only one file and 0
to read all matching files in the schema).
Toggle ON (default) to return EnSight’s undefined value
when missing variable values are encountered (see EnSight
Gold Undefined Variable Values Format). Toggle OFF to
return a value of 0.0 for missing variable values, which is the
behavior of the reader prior to reader version 2.72). The
Environment variable
ENSIGHT_EXODUS_USE_UNDEF_VALUE can be used to
set the default value ( 1 to return UNDEF and 0 to return 0.0
for missing variable values).
Some elements have unique attributes (such as thickness for
2D shell elements). Toggle ON (default) to read in element
attribute variables and OFF to not read these in. Use the
Environment variable
ENSIGHT_EXODUS_READ_ELEMENT_ATTRS to set the
default value ( 1 to read these values 0 to not read them).

EnSight 10.2 User Manual

2.3 EXODUS II Reader

Use detected
DTA XML
file

Auto
generate
DTA XML
file
Read part
names

Assume
unchanging
connectivity

Toggle this ON (default is OFF) to check for the existence of a
.dta file (and read it in). The DTA file has extra metadata
more fully describing the parts. Set the Environment variable
ENSIGHT_EXODUS_USE_DTA_FILE to change the default
(1 is read .dta file, and 0 is do not check).
Toggle this ON (default is OFF) to generate a ‘stub’ .dta file
from the Exodus datafile. Set the Environment variable
ENSIGHT_EXODUS_AUTOGEN_DTA to change the
default (1 generate ‘stub’ .dta file, 0 is do not generate .dta
file).
Toggle this ON (default is ON) to read in the part names from
the Exodus data file. Set the Environment variable
ENSIGHT_EXODUS_USE_FULL_NAMES to change the
default (1 to read in the part names from the Exodus data file,
0 to not read them in).
By default, with this Toggle OFF, when an Exodus dataset has
multiple temporal files, the reader assumes that this is a
changing connectivity file. Changing connectivity geometries
lose some capabilities within EnSight, such as the ability to
interpolate variable values between timesteps. If you know
your temporally decomposed dataset does not change
connectivity, then toggle this ON to tell EnSight to not make
this a changing connectivity dataset; the dataset will become a
changing coordinates geometry (which does allow
interpolation between timesteps). To change the default, set
the environment variable as follows:
ENSIGHT_EXODUS_ASSUME_UNCHANGING_CONNECTIVITY

Scale Factor

EnSight 10.2 User Manual

to a value of 1 and the toggle will appear ON.
Enter a positive float value (default 1.0) to be used as a scale
factor for geometry and vectors (not for scalars). Set the
Environment variable ENSIGHT_EXODUS_SCALE to a
positive float value to change the default value.

2-69

2.3 EXODUS II Reader

Max time
steps

By default, EnSight can read from an Exodus file while the
simulation code is updating the Exodus file. For allocation
purposes, EnSight needs an absolute maximum number of
steps that will appear in the data file(s) during your EnSight
session. Currently, the maximum number of time steps that
EnSight will read is given here as 100000. Increase this value
if your solver may exceed this amount.
A value less than or equal to 1 will disable the ability to check
for new time steps. Note, this field is ignored on Exodus files
with HDF5 as the underlying format, as HDF5 files cannot
safely be read and written simultaneously.
Set the environment variable
ENSIGHT_EXODUS_MAX_TIMESTEPS to change the
default.
For details on how to use this capability in EnSight, see How
To Change Time Steps and the Advanced section in How To
Load Transient Data).

SOS

You can start up SOS using ceishell, or the legacy Case SOS file, or the legacy
resources file (.res) file, each discussed elsewhere in this manual.
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.
The Exodus reader does the decomposition automatically when running in Server
of Server (SOS) mode, which is called Reader-distribute mode. In Reader
Distribute mode, data is distributed to servers in a round-robin fashion. In Reader
Distribute mode, all files must be available to all servers.
If you decide that you want to manually distribute the files, then you must move
the sets of files into separate directories, create the SOS casefile with different
directories and the filename* casefile, and toggle the reader SOS auto-distribute
OFF in the Format Options above.
Shown below are GUI images showing sample user input for a sample read of
spatially distributed Exodus files (4 processors) into EnSight SOS using a simple
4-server resource (sos.res) file as follows. Also shown is the geometry colored by
the Server number calculated using the Calculator Function ServerNumber (which
is an excellent way of showing the allocation of the geometry among the EnSight
Servers. See the Problems section of the Use Server of Servers for more tips
problem-solving your SOS visualization.
#!CEIResourceFile 1.0
SOS:
host: localhost
SERVER:
host: localhost

2-70

EnSight 10.2 User Manual

2.3 EXODUS II Reader
host: localhost
host: localhost
host: localhost

EnSight 10.2 User Manual

2-71

2.3 EXODUS II Reader

(see How To Read Data)
2-72

EnSight 10.2 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
Set grid

Set solution

Use the FAST Unstructured format.
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.
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

Select the measured file and click this button.

(see How To Read Data)

EnSight 10.2 User Manual

2-73

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
Set geometry

Use the FIDAP Neutral format.
Select the geometry/results file (typically .fdneut) and click
this button

Format Options Tab
Set measured

Select the measured file and click this button.

(see How To Read Data)

2-74

EnSight 10.2 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 as
well as the “prpgrf*” files written out in preprocessor mode (which contain only
one timestep). Flowscience is no longer supporting compressed formats with the
*.fgz and *.dat suffix.
Requirements

If any extra FlowScience API debug files are desired from the EnSight session,
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.
EnSight attempts to implement the latest FLSGRF API and 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 its 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.

Parallel Solution

If multiple flsgrf files (flsgrf1.dat, flsgrf2.dat, ... flsgrfn.dat) from a parallel run
and the number of servers equals the number of files, then choose the first one
(flsgrf1.dat) and choose decomposition spatial and the remainder will be
automatically loaded. Each server reads only one of the spatially decomposed
files thus dividing up the memory requirements. For temporal decomposition,
load all the spatially decomposed files flsgrf*.dat and choose temporal
decomposition. In this mode, each server loads a separate timestep thus speeding
up transient postprocessing.

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). All FSI/TSE data is node-based (per node).
To visualize the fluid in the block try creating an isosurface of the Fluid Fraction

EnSight 10.2 User Manual

2-75

2.3 FLOW3D-MULTIBLOCK Reader

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 its 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
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).

Units

If the units are specified in a known unit system in the data file, then EnSight can
convert them to any of the other known unit systems at read in. Also, EnSight can
annotate by the units for any of the variables (those not non-dimensionalized).

Updated info

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

Simple Interface
Data Load

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

Advanced Interface
Data Load

Load your Flow3d file (typically named flsgrf* ) using the Advanced Interface
method.
Data Tab
Format
Set flsgrf

Use the Flow3d-Multiblock format.
This field should be an flsgrf or prpgrf file. If multiple flsgrf
files (flsgrf1.dat, flsgrf2.dat, ... flsgrfn.dat) from a parallel run,
then choose all using an asterisk (flsgrf*.dat) in place of the
numbers, or one by specifying the particular file (flsgrf1.dat).

Format Options Tab

2-76

EnSight 10.2 User Manual

2.3 FLOW3D-MULTIBLOCK Reader

Format
Options

Rename
Variables
Include
Symmetry
Ghosts

Variables are renamed by default to be easier to interpret for
Flow3D users.
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 optional (using a toggle) for the following
boundary conditions.
a. symmetry - include symmetry ghosts toggle
b. wall - include wall ghosts toggle
c. other - (continuative, specified velocity, grid overlay and
outflow) - include other ghosts toggle.
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.

EnSight 10.2 User Manual

2-77

2.3 FLOW3D-MULTIBLOCK Reader

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 optional (using a toggle) for the following
boundary conditions.
a. symmetry - include symmetry ghosts toggle
b. wall - include wall ghosts toggle
c. other - (continuative, specified velocity, grid overlay and
outflow) - include other ghosts toggle.
By default, wall ghosts are removed so that the EnSight fluid/
wall interface does not show up using the isosurface of the
fluid fraction.

Include Other
Ghosts

However toggling ON this flag will cause the fluid/wall
interface to show up using the isosurface of the fluid fraction.
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 optional (using a toggle) for the following
boundary conditions.
a. symmetry - include symmetry ghosts toggle
b. wall - include wall ghosts toggle
c. other - (continuative, specified velocity, grid overlay and
outflow) - include other ghosts toggle.
By default, these other ghosts are removed so that the EnSight
fluid/wall interface does not show up using the isosurface of
the fluid fraction.

Read History
Queries

2-78

However toggling ON this flag will cause the fluid/wall
interface to show up using the isosurface of the fluid fraction.
The flsgrf file often includes xy plotting data in the form of
history data that is loaded into EnSight as pre-defined Queries
accessible by clicking on the Query/Plot icon or below the part
list in the Parts/queries tab. Default is ON.

EnSight 10.2 User Manual

2.3 FLOW3D-MULTIBLOCK Reader

Load FSI
TSE Parts

Restart
Selected
Particle Data
Console
Output

Fluid-Structure Interaction and Thermal Stress Evolution
unstructured parts (hexa8 and tet4’s) and their associated
stress, strain, temperature, displacement and blanking
(STATUS) nodal variables are loaded into EnSight by default.
A TSE (thermal stress evolution) component is a region in the
fluid, where the fluid solidified and a structural analysis is
performed in the solid in response to thermal gradients. An
FSI (fluid-structure interaction) components, is a solid region
in the fluid where the flow-induced structural deformations in
turn, influence the flow, requiring simultaneous structural and
fluid flow solution There can be only one TSE part in a
simulation.
Load the variables on the Restart Timeline. Default ON.
Load the variables on the Selected Timeline. Default OFF.
By default, particle data is not read into EnSight. Choose the
appropriate timeline to read in the Particle data.
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.

Treat Ghosts

Debug - Verbose output plus more detailed output and
progress through the reader routines often valuable for
understanding and reporting problems. Also detailed block
information, variable information, boundary condition
information, and timeset information
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.

Load Internal
STL

EnSight 10.2 User Manual

3. Normal - Use ALL ghost elements as NORMAL, visible
elements. This is useful for understanding boundary
conditions around part blocks.
The flsgrf file sometimes includes surface, boundary
condition, or other important surface geometry on one or more
timelines. Default is to load None, but the pulldown allows the
user to choose Selected, Restart, or Static STL geometry
timelines.

2-79

2.3 FLOW3D-MULTIBLOCK Reader

FS Meta File
Output

The FlowScience reader API, optionally writes out optional
performance and debug files when a flsgrf file is opened if you
have write permission. These can help to speed up reading the
second time a file is opened or to understand the details of the
read or to diagnose a failed read. However, if multiple users
each with different file mask permissions attempt to open a
flsgrf file on a shared network hard drive, the writing and
overwriting of these files becomes problematic and can cause
a read to fail. The safest option, if others may follow your read
of a given file, is to choose to not write out these optional files.
The API offers four options on opening a file named, for
example, flsgrf:
None - write out no additional files
Performance - writes out c-flsgrf, flsgrdr, g_flsgrf, and t_flsgrf
files.
Debug - writes out the flsout.rdr file

Units

All - writes out both Performance and Debug files.
Convert units to selected type. FlowScience reader API
allows the conversion of a known system units (CGS, SI or
English) to another known system (CGS, SI, or English).
EnSight will not convert from an unknown or unspecified unit
system.
Unchanged (default) - use the system of units in the data file
CGS - Uses grams, centimeters, and seconds.
SI - Uses kilograms, meters, and seconds.

Temperature
Units

English - Uses slugs, feet, and seconds.
Temperature units are always known (C, K, F, or R) and can
therefore always be converted to any other unit system.
Celsius - Convert to Celsius
Kelvin - Convert to Kelvin
Fahrenheit - Convert to Fahrenheit
Rankine - Convert to Rankine

Decomposition

Unchanged (default) use the temperature units in the data file
If running in EnSight SoS mode, the type of decomposition to
use.
None Spatial - Traditional SOS mode in which each server is
assigned one of the spatially decomposed block files.

Set measured
2-80

Temporal - Temporal SOS in which the data is not spatially
decomposed, but rather each of the available servers reads a
different timestep to speed up transient post processing.
Select the measured file and click this button.
EnSight 10.2 User Manual

2.3 FLOW3D-MULTIBLOCK Reader
Parallel post
processing (SOS)

The Flow3d solver can calculate its solution in parallel. This type of solution
writes out the data as separate files (flsgrf1.dat, flsgrf2.dat, flsgrf3.dat, ....), each
containing one structured block.EnSight can read each of these files onto a
separate server. Server 1 will read in the unstructured data plus block 1, server 2
will read in block 2, server 3 will read in block 3, etc.
You can create an SOS casefile (.sos), which maps out which server loads what
data and start EnSight up in SOS mode, and just load the sos casefile directly.
Alternatively, you can create a .res file to set up the servers, start up EnSight in
SOS mode, and load the data as flsgrf*.dat, and, in the data reader dialog, choose
the .res file and choose to allow sos to use the *. For more details (including a
sample resource file and sample SOS case file and how to use them, see How to
Use Server of Servers and search for Flow3d.
(see How To Read Data)

EnSight 10.2 User Manual

2-81

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 or .fdat)
file. The second method to get data into EnSight is to use Fluent’s EnSight Case
Gold Export option and read the resulting .encas file directly into EnSight using
the Case reader. The third and 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/ensight102/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).
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
Set cas

Set dat

To use this reader, select the Fluent format.
Select the geometry file (typically .cas or .cas.gz) and click
this button. For transient data, use a single asterisk to replace
the number (*.cas or *.cas.gz).
Select the results file (typically .dat or .dat.gz), and click this
button. For transient data, use a single asterisk to replace the
number (*.dat or *.dat.gz). Note that .fdat files (see Airpak /
Icepak reader) are also usable in place of the .dat file. Because
the .dat file is the automatic selection, if a .dat file is
collocated with a .fdat file, the user will have to manually
select the .fdat file and then click on the Set dat button to use a
.dat file variant.

Format Options Tab
Set measured

2-82

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.

EnSight 10.2 User Manual

2.3 FLUENT Direct Reader

Other
Options
using the
current
Fluent reader

Load Internal
Parts

Use Meta
Files

Load _M1
_M2 vars

Load all cell
types

EnSight 10.2 User Manual

Toggle this ON to load the Fluent Internal Parts. This will
show all 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.
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.
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.
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-83

2.3 FLUENT Direct Reader

Poly to
Regular Cell

Poly faced
Hex to Poly

Fix Hanging
Nodes

Read Parallel
CAS
Variables

Read Particle
Variables
Use Zone IDs
for Parts

Read all files
to create
variable list

2-84

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.
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 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.
Some Fluent polyhedral cells and all transition hex cells
converted to polyhedrals will have hanging nodes. A hanging
node is a 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.
For parallel investigation, if the user toggles on read cas
variables, this option creates two new elemental scalars:
ELEMENT_INDEX and PARTITION only if the data is
solved in parallel and has partition section(s). This is primarily
useful to visualize the Fluent geometric decomposition of
parallel solutions.
This will read particle coordinates and variable data from the
DAT file. The number of particle parts is equal to the number
of injections.
A heterogenous mix of serial and parallel solution files will
result in a jumbled part ordering between CAS files. Toggle
this ON to use the part zone id to reorder the parts consistently
from CAS file to CAS file using the first file loaded as the
canonical order.
Some transient datasets have different variables in the
different DAT files. If this is OFF (default) then only the last
DAT file will be used to create the variable list. If ON, then all
DAT files will be used to create the master variable list.
Regardless of the option, a variable will be assigned the
EnSight Undefined value at time steps where it is undefined.

EnSight 10.2 User Manual

2.3 FLUENT Direct 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.

Time Values

Debug - Verbose output plus more detailed output and
progress through the reader routines often valuable for
understanding and reporting problems.
'Use Filename Numbers' will read the sequential numbers at
the tail of the filenames and adjust them by making the first
number 0 and shift all subsequent values. That is,
file4000001.cas, file4000004 ... file4000020 is as follows:
timestep 0 has time value 0.0, timestep 1 has time value 3.0,
and timestep n has time value 19.0.
‘Use Time Steps’ will make timestep and time value the same
for example: timestep 0 will have time value 0.0 and timestep
5 have time value 5.0.
'Read Time Values' (default) will open each file and find the
exact time value using the 'flow-time' keyword. Note that this
means that every file has to be opened and searched. Failing
that it defaults to the 'Calc Const Delta'.
'Calc Const Delta' reads a delta time from one file using
'physical-time-step' keyword, and calculates the time values
by multiplying the delta value by the adjusted filename
number. Failing that, it defaults to the ‘Use Filename
Numbers’ option.
It is essential that your time values are correct for some
calculations (for example, if you are going to do pathline
tracing). Keep in mind that if your timesteps are uniform then
you can use the ‘Use Time Steps’ option and just scale your
time values using the Time Options tab in the data reader
dialog. If your timesteps are not uniform, but your File
Numbers are proportional to your timesteps then you can
select ‘Use Filename Numbers’ and then scale the time values
using the Time Options Tab in the data reader dialog.

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

EnSight 10.2 User Manual

2-85

2.3 FLUENT Direct Reader

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 in the dat file. 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 and EnSight
does not have the boundary conditions nor the solver physics algorithms to
extrapolate variable values to boundary parts. 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.

Extra Variables

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

gzipped files

Files that are gzipped can be read by EnSight. However, with large numbers of
parts this can result in a substantial slow down in the access of variable
information in the DAT file because this involves non sequential access (seeking
around various places in the file rather than sequentially moving through the file
in order) which has been shown to result in dramatic slow downs. The
workaround is to simply ungzip your files prior to reading them into EnSight.

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

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

2-86

EnSight 10.2 User Manual

2.3 FLUENT Direct Reader

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 .encas file
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 continuous boundaries.

Particles

The reader should attempt to read particles if they are present in the file(s).
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/ensight102/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/ensight102/translators/fluent/Particles/

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

EnSight 10.2 User Manual

2-87

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/ensight102/src/readers/inventor

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

The File Selection dialog is used to specify which files you wish to read.
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
Set .iv file

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

Format Options Tab
One Part per
file
Console
Output

Makes one part out of each file.
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

Set measured

Debug - Detailed output and progress through the reader
routines often valuable for understanding and reporting
problems.
Select the measured file and click this button.

(see How To Read Data).

2-88

EnSight 10.2 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

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.

FEMZIP

The reader uses the publicly-available “femunzip” utility to unzip the compressed
files. This unzip utility can be downloaded for free. The user must set the
environmental variable “FEMUNZIP_UTILITY_PATH” to point to the location
of this executable. The reader will call this executable on the d3plot file(s) to
ensure that the file(s) are unzipped into a temporary folder prior to reading. A
“mapfile.txt” pointing to the unzipped files will be created which will be used in
subsequent runs avoid the need to unzip again.

CFD data

The reader skips legacy CFDDATA sections, and reads instead the ICFD data
from the incompressible CFD and incompressible CFD surface solvers.

DEM/DES

The reader now includes this particle data.

AMR

The reader can read AMR data even if the expected, first d3plotaa is not available.

Duplicate
timesteps

The reader skips duplicate timesteps, caused perhaps by double precision to float
conversion.

Limitations

The reader has the following limitations.
Does not read airbag particle data
Doesn't support PACKED data (3 integers per word)
Skips over Rigid Road Surface Data.
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/ensight102/src/readers/ls-dyna3d/README

Data Reader
Simple Interface
Data Load

Load your d3plot file using the Simple Interface method.

EnSight 10.2 User Manual

2-89

2.3 LS-DYNA Reader
Advanced Interface
Data Load

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

Use the LS-DYNA3D format.
This field should have the first d3plot file name. All of the
d3plot files will be loaded starting with this first one
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
Format
Options

Select the measured file and click this button.
The following options are customized for the reader:

Remove
Failed Elems
Use ALE
Variables
Keyfile IDs

Failed elements will not be shown (default)

d3plot IDs
Console
Output

2-90

Include the ALE variables
This pulldown provides the choice of either Material IDs or
Part IDs from the keyfile to be used for part naming.
Use either Material IDs (default) or Part IDs within the d3plot
file to read in the data.
Can control amount of output that comes to the console.
Options are: Normal, Verbose, or Debug

EnSight 10.2 User Manual

2.3 LS-DYNA Reader

ASCII File
Input

Binary
(binout) File
Input

Can input glstat, abstat, matsum, rcforc, rwforc, nodout,
secforc, sleout, elout, dbfsi, and spcforc xy ascii files as
EnSight xy queries. These files must be in the same directory
as the d3plot file(s). Choose none (default) or all for all of the
available files. Choose filenames.txt if you wish to name a
subset of the files to read.
Can input the binout file (default none) glstat, abstat, matsum,
rcforc, rwforc, nodout, secforc, sleout, elout, dbfsi, and
spcforc and nodfor, or all curve sets as EnSight xy queries.
The binout file must be in the same directory as the d3plot file.
This uses the LSTC binout API to read the xy data.

(see How To Read Data)

EnSight 10.2 User Manual

2-91

2.3 MSC.DYTRAN Reader

MSC.DYTRAN Reader
Overview
Reads any of the following (in preferred order):
1. The .dat file (which refers to .ARC files in the directory)
or 2. One of the .ARC files (which will get all .ARC files of the same pattern)
or 3. The modified case file (for specific control).
See the following file for current information on this reader.
$CEI_HOME/ensight102/src/readers/dytran/README.txt
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
Set dytran

Use the MSC/Dytran format.
The preferred input is the file with .dat suffix. The root name
of this file will be used to find all .ARC files in the directory
which match the Dytran naming convention. And all parts of
the model will be made available to EnSight. Additionally,
this method allows for the most efficient setting for changing
geometry, because it can glean some pertinent information
thereto within the .dat file.
Alternatively, you can enter one of the .ARC files, and all
.ARC files in the directory which match the pattern will be
found and used. Note: no widcards are needed - just select one
of the .ARC filenames.
The third method is to enter a custom case file. This user
generated ascii file allows one to specify particular parts, etc.
Since one can accomplish the same thing by only loading
specific parts within EnSight, this method is probably
obsolete.

Format Options Tab
Set measured

2-92

Select the measured file and click this button.

EnSight 10.2 User Manual

2.3 MSC.DYTRAN Reader

Format
Options

The following options are customized for the reader, in
version 2.05 or later.

Make vector vars from standard scalars - Toggle on to have
vector variables automatically generated from known standard
scalar components. On is the default.
Example: If toggled on, a vector variable named VEL will be
created from the scalars XVEL, YVEL, ZVEL
Load Time History Queries - Toggle on to have all xy timehistory queries (contained in pattern matching .THS files in
the directory) loaded automatically into EnSight. On is the
default.
Note: These have traditionally been read into EnSight in the
Query/Plot feature, but reading each .THS file as an “external
file”. While this option still exists, it is not needed if this
toggle is on.
If you choose to not have the Dytran XY time-history data (from the .THS files)
loaded automatically, or if you are using a prior version of the reader, you can later
click on the XY Query/Plot icon and choose to load data from an external file in
the pulldown, and choose the desired .THS file(s). For details, see the How To
Manual section on Queries From External Sources.
(see How To Read Data)

EnSight 10.2 User Manual

2-93

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.
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.
Data Tab
Format
Set t16/t19

Use the MSC.Marc format.
This field should have the .t16 or .t19 suffix file.

Format Options Tab
Format
Options

Include
ElemSet
Parts
Include Face/
Edge Set
Parts
Include
NodeSet
Parts

2-94

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 any Face or Edge sets defined. These are some logical
set of particular faces and/or edges of full elements. Default is
on.
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.

EnSight 10.2 User Manual

2.3 MSC.MARC Reader

Include local
elem res
comps (if
any)

Include
Tensor
derived
(VonMises,
etc.)

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
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 = 1 for 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

Regular Part
Creation
Convention

EnSight 10.2 User Manual

or any legal combination. example: for VonMises and Max
Shear only, use 18. Default is on.
Parts will be created according to the following:

2-95

2.3 MSC.MARC Reader

Element Vars
as

Var naming
convention

If Sections,
which:

2-96

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
Element results (whether centroidal or
values
element nodal) will be averaged to the
nodes without using geometry
weighting. Thus will be per_node
variables in EnSight. This is a global
averaging, so shared nodes are affected
by all parts that share a node.
Geom weighted
Element results (whether centroidal or
average to node
element nodal) will be averaged to the
values
nodes using geometry weighting. Thus
will be per_node variables in EnSight.
This is a global averaging, so shared
nodes are affected by all parts that share
a node.
Ave 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. This is a local
averaging, so all averaging is contained
within each part.
Geom weighted
Element results (whether centroidal or
ave to node 
nodes using geometry weighting. Thus
will be per_node variables in EnSight.
This is a local averaging, so all
averaging is contained within each part.
Use Content Field
Variable names will be what is in the
(if provided)
Content field, if provided. If not
provided, they willbe the VKI dataset
name. This is the default.
Use VKI dataset
Variable names will be the VKI variable
name
dataset name (which are reasonably
descriptive).
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
The section number entered in the field
(below)
below will be used
Separate Vars per
A separate variable will be created for
Section
each section.
EnSight 10.2 User Manual

2.3 MSC.MARC Reader

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 10.2 User Manual

2-97

2.3 MSC.MARC Legacy Reader

MSC.MARC Legacy 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/ensight102/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.
Data Tab
Format
Set t16/t19

Use the MSC.Marc Legacy format.
This field should have the .t16 or .t19 suffix file.

Format Options Tab
Format
Options

Set measured
Features

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.
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.
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.

2-98

EnSight 10.2 User Manual

2.3 MSC.MARC Legacy Reader

8. In the past, Little-endian and Big-endian results were handled transparently in
the reader. 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. This is becoming irrelevant as nearly all machines are using
Intel processors.
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 10.2 User Manual

2-99

2.3 NASTRAN OP2 Reader

NASTRAN OP2 Reader
Overview
There are two Nastran readers: Nastran OP2, and Nastran OP2 (beta). This section
documents only the Nastran OP2. It 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.
c) To read the NASTRAN input deck (.nas, .bdf, or .dat) there is a separate
reader: use the Nastran Input Deck Reader.

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:
----------

2-100

EnSight 10.2 User Manual

2.3 NASTRAN OP2 Reader

mop
3
“boom.op2”
“rigid.eet” “BOOM” “1000.0”
“bucket.op2”
“rigid.eet” “BUCKET” “1000.0”
“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 9.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 much more friendly and useful.
8. Because of the way that element variable values now may lead to nodal
EnSight 10.2 User Manual

2-101

2.3 NASTRAN OP2 Reader

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
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/ensight102/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
Set op2

Use the Nastran OP2 format.
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. To read the NASTRAN input deck (.nas, .bdf, or
.dat) there is a separate reader: use the Nastran Input Deck
Reader.

Format Options Tab
Set measured

2-102

Select the measured file and click this button.

EnSight 10.2 User Manual

2.3 NASTRAN OP2 Reader

Extra GUI

The following parameters are available. They are described
below.

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.

Elem Var Type:

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

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

EnSight 10.2 User Manual

2-103

2.3 NASTRAN OP2 Reader
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
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

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 occurred
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-104

EnSight 10.2 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)

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

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

EnSight 10.2 User Manual

2-105

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 9.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 9.13, EnSight Rigid Body File Format)
README

See the following file for current information on this reader.
$CEI_HOME/ensight102/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
Set geometry

Use the Nastran Input Deck format.
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-106

EnSight 10.2 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.
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. 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 ‘ensight102 -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
Set file

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

Format Options Tab
Set measured

EnSight 10.2 User Manual

Select the measured file and click this button.

2-107

2.3 OpenFOAM Reader

Other
Options

Include
ElemSet
Parts
Generate
Wall Parts
Include
between
processor
surfaces
Check and
cap infinite
results

Regular Part
Creation
Convention
Var naming
convention

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.
Generate 2D Face Sets. Default is on.
If toggled ON and the data is from a parallel solution, then the
surfaces between the processors will be generated as parts.
Default is off.
If toggled ON and there exists values in the file that are
beyond the 32-bit size limit (thus creating ‘inf’ infinite
values), they will be capped at a value just below that limit
value.
Default is off
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

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.

2-108

EnSight 10.2 User Manual

2.3 OpenFOAM 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. This is a global averaging, so shared
nodes are affected by all parts that share a node.
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. This is a global averaging, so shared
nodes are affected by all parts that share a node.
Ave 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. This is a local averaging, so all
averaging is contained within each part.
Geom weighted ave to node  - Element results
(whether centroidal or element nodal) will be averaged to the
nodes using geometry weighting. Thus will be per_node
variables in EnSight. This is a local averaging, so all
averaging is contained within each part.

(see How To Read Data)

EnSight 10.2 User Manual

2-109

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
Set geometry

Set results

Use the OVERFLOW format.
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.
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
Set bounds

Set measured
Limitation

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.)
Select the measured file and click this button.

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

2-110

4.0 5.0 6.0 7.0 8.0 9.0 10.0

Density
Energy
3 4 Momentum

EnSight 10.2 User Manual

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 turbulence 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

EnSight 10.2 User Manual

=
=

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*

2-111

2.3 OVERFLOW Reader

Assigning
Analysis_Time

Energy

=

Gamma_Q6_fiel
d

=

Momentum[Z] = Q4-field variable = z component of
Momentum *w*
Q5-field variable = dimensionless total energy *e0*
Q6-field variable = gamma  (constant field, unless
you use the gamma option of the code)

And for SA model:
=
Q7_field

Q7-field variable = turbulence variable

And for k-e model:
=
Q7_field,
Q8_field

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 9.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 9.7, PLOT3D Results File Format)

2-112

EnSight 10.2 User Manual

2.3 PLOT3D Reader

PLOT3D Reader
Supported Files

The PLOT3D reader shipped with EnSight is an internal reader that supports C Binary,
Fortran Binary as well as ASCII formats. It will read double precision data, but will
convert it to single precision for use in EnSight.

Example Source

The PLOT3D reader is an internal EnSight reader and the source code is
unavailable. But there is an example source code with limited functionality found
in the following directory that would be useful as a starting point for creating your
own user-defined implementation of this reader.
$CEI_HOME/ensight102/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
Set geometry
Set results

Use the PLOT3D format.
Select the grid file and click this button. This file is a
structured GRID file with FAST enhancements.
Select the results file and click this button. The Results File is
either a modified EnSight Results file or standard plot3d Qfile. 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
Set bounds

Set measured
Assigning
Analysis_Time

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.)
Select the measured file and click this button.

By default, the Analysis_Time constant variable value is assigned the time values
listed in the q.res file. (see Section 9.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.

SOS

Use of the Plot3D reader in parallel using EnSight’s Server of Server capability can be
done automatically using EnSight ceistart102 application, designating the number of
servers in the startup GUI and then just loading the file in auto distribute mode to let the
server do the allocation of file data to each server, or in a very controlled fashion using an
sos case file as discussed in the How To Manual (See How To Use Server of Servers).

(see How To Read Data)

EnSight 10.2 User Manual

2-113

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.
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
Set anim

Use the RADIOSS_4.x format.
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-114

EnSight 10.2 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.
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
Set .msh
Set .res

Use the Polyflow format.
This field contains the mesh file. Clicking button inserts .msh
file name shown into the field.
This field contains the result file.

Format Options Tab
Set measured
Other
Options

Include Face/
Edge Parts

EnSight 10.2 User Manual

Select the measured file and click this button.

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 any Face or Edge sets defined. These are some logical
set of particular faces and/or edges of full elements. Default is
off.

2-115

2.3 POLYFLOW Reader

Include
NodeSet
Parts
Include local
elem res
comps (if
any)
Include
Tensor
derived
(VonMises,
etc.)
Regular Part
Creation
Convention
Var naming
convention

Element Vars
as

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 the local stresses components, etc that are in the
element
Default is on
For tensor results, calculate scalars from the tensors.
Default is off

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

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).
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. This is a global averaging, so shared nodes are
affected by all parts that share a node.
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. This is a global averaging, so shared
nodes are affected by all parts that share a node.
Ave 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. This is a local averaging, so all
averaging is contained within each part.

If Sections,
which:

2-116

Geom weighted ave to node  - Element results
(whether centroidal or element nodal) will be averaged to the
nodes using geometry weighting. Thus will be per_node
variables in EnSight. This is a local averaging, so all averaging
is contained within each part.
Not used

EnSight 10.2 User Manual

2.3 POLYFLOW Reader

Section Num

Not used

(see How To Read Data)

EnSight 10.2 User Manual

2-117

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.
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
Set file

Use the SDRC Ideas format.
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
Other
Options

Include Face/
Edge Parts

2-118

Select the measured file and click this button.

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 any Face or Edge sets defined. These are some
logical set of particular faces and/or edges of full elements.
Default is off.

EnSight 10.2 User Manual

2.3 SDRC Ideas Reader

Include
NodeSet
Parts
Include local
elem res
comps (if
any)

Include
Tensor
derived
(VonMises,
etc.)

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 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
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 = 1 for 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

Regular Part
Creation
Convention
Var naming
convention

or any legal combination. example: for VonMises and Max
Shear only, use 18. Default is off
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

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).

EnSight 10.2 User Manual

2-119

2.3 SDRC Ideas 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. This is a global averaging, so shared
nodes are affected by all parts that share a node.
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. This is a global averaging, so shared
nodes are affected by all parts that share a node.
Ave 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. This is a local averaging, so all
averaging is contained within each part.

If Sections,
which:

Geom weighted ave to node  - Element results
(whether centroidal or element nodal) will be averaged to the
nodes using geometry weighting. Thus will be per_node
variables in EnSight. This is a local averaging, so all
averaging is contained within each part.
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

Section Num

Separate Vars per Section - A separate variable will be created
for each section.
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)

2-120

EnSight 10.2 User Manual

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

EnSight 10.2 User Manual

.5

2-121

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/ensight102/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
Set file

Use the Silo format.
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)

2-122

EnSight 10.2 User Manual

2.3 Software Cradle FLD Reader

Software Cradle FLD Reader
Overview
FLD File

This reader imports a .fld file, which is a common file format of the solvers
developed by the Software Cradle Company. The following three solvers export
this format: scSTREAM, SC/Tetra, and HEAT Designer. This reader is designed
to work with version 4 of the FLD format, which is written by version 6 or later of
these solvers.

Platforms

This reader was supplied only on Windows, and CEI compiled it on Linux and
Mac. Therefore, only the Windows version of the reader is officially supported by
Software Cradle.

Case Gold

The SC/Tetra solver no longer exports EnSight Case Gold.

Undefined
variables

When a variable does not exist on a node or element, the EnSight undefined value
is set. Consider changing the display of the variable in the color palette editor and
choose Display Undefined as “By invisible” to avoid displaying undefined
regions.
Does not read measured data. Maximum material number is limited to 10000.
When timestep is changed, the material number of elements does not change.

Limitations
Simple Interface
Data Load

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

Advanced Interface
Data Load

Load your FLD file (typically named with a suffix .fld) using the Advanced
Interface method.
Data Tab
Format
Set file

Use the Software Cradle FLD format.
Select the FLD file (typically .fld) and click this button. For
transient data, there will be one FLD file per timestep. Select
any one FLD file and the reader will automatically find all
other related files and load them as transient data.

Format Options Tab

EnSight 10.2 User Manual

Set measured
Other
Options

Select the measured file and click this button.

Simplify
reading
sequential
FLD files

Creates a location map of the FLD file data that is used to
facilitate subsequent finding of data within the file.

2-123

2.3 Software Cradle FLD Reader

(see How To Read Data)

2-124

EnSight 10.2 User Manual

2.3 STAR-CD and STAR-CCM+ Reader

STAR-CD and STAR-CCM+ Reader
Overview
Description

This reader reads .ccm, .ccmg (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.

.ccmt input

When there exists a single .ccmt file, and it exists in the same directory as the
other files, and especially if there is changing geometry, the .ccmt file should be
entered into the first field. It has pointers to the .ccmp/.ccmg files.
If there is no changing geometry, then one can still generally use the rule of
entering the .ccmt file if it exists, else the .ccmp file if it exists, else the .ccmg file
into the first field.
However sometimes there are multiple .ccmt files. And as long as the model is not
changing geometry, you can use the method described below to handle some
varied situations. Namely, enter the .ccm or .ccmp or .ccmg file into the first field.
And in the second field, enter the .ccmt file with an asterisk in the filename or the
directory to use pattern matching to read them all in: star*.ccmt or /mydir/run*/
star.ccm. If you have a mixture of different ccmt filenames and directory
locations that cannot be matched with one asterisk create a MULTIPLE_CCMT
text file with the relative path names (relative to MULTIPLE_CCMT file) and the
ccmt file names listed one to a line. See below for more details.

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/ensight102/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

EnSight 10.2 User Manual

2-125

2.3 STAR-CD and STAR-CCM+ Reader

field described below.

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

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

Simple Interface
Data Load

Load your .ccm file using the Simple Interface method.

Advanced Interface
Data Load

Load your STAR-CCM file using the Advanced Interface method.
Data Tab
Format
Set .ccm[t/p/g]

Use the STAR-CD CCM format.
Generally, one should enter one of the following in priority
order. The .ccmt file if it exists, else the .ccmp file if it exists,
else the .ccmg file. And nothing would be needed in the
second field.
Note:
A .ccmt file contains transient data. Generally just transient variable
data - but can contain transient geometry as well. It contains
pointers to needed .ccmp .ccmg files.
A .ccmp (or .ccm) file contains both geometry and results.
A .ccmg file contains geometry only.

Set .ccmt

Alternatively, if there is no changing geometry, for the first file
you should choose the file with extension .ccmp, .ccm, or .ccmg.
And then set the .ccmt file in the second field as described
below.
Again, generally, you do not need this field, and should have
entered the .ccmt file in the first field.
However, if you chose to use the alternate method for time
varying variable data with no changing geometry, set the .ccmt
file using this field. The file must only contain transient
variable data.
For multiple .ccmt files, star1.ccmt, star2.ccmt and star3.ccmt,
input star*.ccmt.
For multiple directories dir1/star.ccmt, dir2/star.ccmt, dir3/
star.ccmt specify full path as follows /mydir/dir*/star.ccmt.
Or, enter /mydir/MULTIPLE_CCMT and create a text file
named exactly MULTIPLE_CCMT in this directory
containing one ccmt file per line. The pathname location of the
MULTIPLE_CCMT will be prepended to each of the .ccmt
filenames so use relative pathnames to your .ccmt filenames
(or none). See below for details.

2-126

EnSight 10.2 User Manual

2.3 STAR-CD and STAR-CCM+ Reader

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

Generate
Wall Parts
Regular Part
Creation
Convention
Var naming
convention

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.
Toggle on to create 2D Face set parts. Default is on.
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

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).

EnSight 10.2 User Manual

2-127

2.3 STAR-CD and STAR-CCM+ 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. This is a global averaging, so shared nodes are
affected by all parts that share a node.
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. This is a global averaging, so shared
nodes are affected by all parts that share a node.
Ave 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. This is a local averaging, so all
averaging is contained within each part.
Geom weighted ave to node  - Element results
(whether centroidal or element nodal) will be averaged to the
nodes using geometry weighting. Thus will be per_node
variables in EnSight. This is a local averaging, so all averaging
is contained within each part.

Advanced .ccmt
alternate input
method

1) Normally, a single .ccmt file would be specified.
Thus, for: /mydirectory/star.ccmp
star.ccmt
In the second field, specify: /mydirectory/star.ccmt
2) However, if multiple .ccmt files exist because of restarts
of the solver, you can use a wildcard (asterisk) in
the name of the file, or subdirectory.
ex 1) For the situation where multiple .ccmt files reside
in the same directory: /mydirectory/star.ccmp
star_1.ccmt
star_2.ccmt
star_3.ccmt
In the second field, specify: /mydirectory/star_*.ccmt
ex 2) For the situation where multiple .ccmt files reside
in their own subdirectories: /mydirectory/star.ccmp
RESULTS.001d/star.ccmt
RESULTS.002d/star.ccmt
RESULTS.003d/star.ccmt
In the second field, specify: /mydirectory/RESULTS.*d/star.ccmt

2-128

EnSight 10.2 User Manual

2.3 STAR-CD and STAR-CCM+ Reader

Note that you can't have a mixture of these two examples with
this method. Namely, the following cannot be properly specified
with this method: /mydirectory/star.ccmp
star_1.ccmt
RESULTS.002d/star.ccmt
You would need to either copy (and rename) the .ccmt file in the
subdirectory to the data directory, or you will need to create
a subdirectory for each .ccmt file in the data directory, and move
the .ccmt files into those subdirectories. You could obviously
take advantage of symbolic links to avoid actually moving any data.
Your other alternative is to use method 3) below.
3) You can create a special file in which you list all of the .ccmt files
This would allow them to be placed in or anywhere below the data directory.
Thus, you could handle the mixture discussed in 2) above.
Rules for this special file:
a. The file must be named exactly: MULTILPLE_CCMT
b. The .ccmt files must be one per line in this file.
c. They must NOT have a full path, because the path to the
MULTIPLE_CCMT file will be prepended to them.
d. There is no concept of comment lines, so no extraneous lines (even
empty lines) are allowed.
ex 1 above, specified in this manner)
/mydirectory/star.ccmp
star_1.ccmt
star_2.ccmt
star_3.ccmt
MULTIPLE_CCMT
In the second field, specify: /mydirectory/MULTIPLE_CCMT
where MULTIPLE_CCMT file would contain just 3 lines, like:
------------star_1.ccmt
star_2.ccmt
star_3.ccmt
-------------

dashed lines are NOT in the file

ex_2 above, specified in the manner)
/mydirectory/star.ccmp
RESULTS.001d/star.ccmt
RESULTS.002d/star.ccmt
RESULTS.003d/star.ccmt
MULTIPLE_CCMT

EnSight 10.2 User Manual

2-129

2.3 STAR-CD and STAR-CCM+ Reader

In the second field, specify: /mydirectory/MULTIPLE_CCMT
where MULTIPLE_CCMT file would contain just 3 lines, like:
------------dashed lines are NOT in the file
RESULTS.001d/star.ccmt
RESULTS.002d/star.ccmt
RESULTS.003d/star.ccmt
------------And for the mixed mode situation:
/mydirectory/star.ccmp
star_1.ccmt
RESULTS.002d/star.ccmt
MULTIPLE_CCMT
In the second field, specify: /mydirectory/MULTIPLE_CCMT
where MULTIPLE_CCMT file would contain just 2 lines, like:
------------dashed lines are NOT in the file
star_1.ccmt
RESULTS.002d/star.ccmt
------------(see How To Read Data)

2-130

EnSight 10.2 User Manual

2.3 STL Reader

STL Reader
Overview
Description

Reads .stl files and .xct exec files.
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

Example Simple
Exec file

(where N is the no. of files)

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

EnSight 10.2 User Manual

2-131

2.3 STL Reader
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 9.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 Panel.). 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"

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 9.13, EnSight Rigid Body File Format)
README

See the following file for current information on this reader.
$CEI_HOME/ensight102/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
Format
Set geometry
Set results

Use the STL format.
Select the geometry file (typically .stl or .xct) and click this
button
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)
2-132

EnSight 10.2 User Manual

2.3 Synthetic Reader

Synthetic Reader
Overview
Description

This “reader” is unique in that it does not actually read geometry/variable data
from the disk. Rather, it is designed to synthesize geometry/variables based on
commands read in from a file or options chosen interactively in the Data Reader
dialog. The Synthetic reader can create transient or static geometry comprised of
spherical and/or cube parts(s) with an arbitrary, user-defined number of elements
(of user-chosen element type), that varies linearly over a user-chosen number of
timesteps as well as any number of scalar, vector, or constant variables. Note that
it may not appear in your pulldown list of readers by default: to see this reader, go
into preferences in the data section and make this reader available.
The most common usage is to interactively choose the Synthetic reader and to
enter a dummy filename in the data field (data reader dialog requires an entry in
this field), and to toggle on the Advanced interface, and to interactively choose
values in the Format Options. These interactive sessions can be saved as
command files to be rerun later, or session files to be reloaded later. More rare, is
to hand-edit a synthetic options (.svn) file with specific entries, and then the load
in the .syn file that will provide the input for generation of the dataset.

Usefulness

Because the synthetic reader does not read the geometry nor variable data from
disk, it is useful for measuring EnSight performance separated from EnSight I/O.
Further, the Synthetic reader is compatible with all of EnSight’s parallel
capabilities (SOS, HPC+, threading). As such, it is useful for measuring graphics
hardware card performance by creating and controlling arbitrarily large numbers
of polygons to be rendered by the client graphics card. Also, it is useful for
supplying known models (size and element type) to quantify the benefits of
parallel computing (threading) performance, as well as parallel server (SOS)
performance, as well as parallel rendering performance. Further, in Compatibility
mode (one of the user options), the synthetic reader is useful for comparing
current versions of EnSight 10.2 to previous versions of EnSight. In addition,
with the power of the EnSight calculator and the simplicity of the geometry the
synthetic reader is a useful tool for verifying and validating the calculator
functions over the range of element types supported by EnSight.
Finally, the synthetic reader eliminates the need for transmitting extremely large
datasets for testing purposes. Since geometry is generated from commands,
arbitrarily large geometries for testing can be sent via email in the form of tiny
.syn files, or in .enc command files that contain the format options for creating the
gigantic dataset.

Usage

The synthetic reader must have text in the file field, even if it is dummy text
because of EnSight requirements (in which case it will ignore the dummy text) or
it can read in a .syn file so which will contain a simple list of options for autogenerating the geometry, timesteps, variables, etc.

Limitations

The current reader only allows a subset of the EnSight element types, and all parts
currently contain only one element type. Elements of type TRI03 are used to
create a surface mesh on the outer boundary of the sphere or the cube part(s) or the
plane part(s). Volume elements create a 3D volume of the sphere or cube part(s).
And QUAD04 elements create a series of layers in the cube part(s).

Elements

There are three part types: Spheres, Cubes and Planes. If you choose Tri 3 then
the surface of both the sphere and cube part(s) are meshed using this element type.

EnSight 10.2 User Manual

2-133

2.3 Synthetic Reader

Plane Parts

Variables

Transient

README

If you choose another element type, then the sphere(s) are meshed using the Hex 8
element type, and the cubes are meshed using the element type. For example,
choose the Point element type and the Cube nodes become point elements.
Choose the Quad4 and the cube becomes a series of xy planes meshed in Quad 4
elements. Similarly choose Tet 4, Penta6, Nfaced Polyhedral, or Structured Hex
and the cube part’s hex elements are converted into these supported 3D element
types. Planes must use Tri 3 or Quad 4 elements only. Unfortunately a large
number of element types are still unsupported: Bar 2, Bar 3, Tri 6, Quad 8, Tet 10,
Pyr 5, Pyr 13, Penta 15, Hex 20, and Nsided Polygon. Choose an unsupported
element type and the cubes and spheres are meshed using Hex 8 elements and a
warning message is sent to the server console.
Plane parts are unique as follows. Each part has one plane. Plane parts are all
normal to the Z-axis and appear back to front uniformly distributed along the Zaxis from Z=0 to Z=1. Planes interpolate between the beginning and ending
number of elements (which are elements per part). At earlier timesteps, parts with
higher part number are effectively given zero nodes and zero elements. As you
preoceed through time, parts are allowed to have elements. This allows the
appearance of parts as you proceed through time, from back to front, of
increasingly dense numbers of elements (when the ending number of elements is
higher than the beginning) resulting in an exponential increase in the number of
elements, for example, for graphics testing. If the Spread is set to Legacy, then the
planes x and y centers are exactly aligned. A different Spread will add some
random scatter to the x and y centers. If the number of plane parts is less than the
number of servers then the part will be assigned to the server by part number. If
there are more parts than servers, then a round-robin approach will apply.
Scalar and vector variables alternate as nodal and elemental, respectively. The
first scalar variable (nodal) is a nodal deformation scalar, and the second variable
(elemental) is simply the element index. The first vector variable (nodal) is a
spiraling vector simulating a swirling flow spiraling inward and downward. The
first two constant variables are the number of nodes and the number of elements,
respectively. Other variables will be added as needed/requested. Finally user
variables can be added using the calculator (e.g. a quadric dependent on the
Coordinates).
If one timestep is chosen the dataset is static. If more than one timestep is chosen,
and the dataset is in compatibility mode, then the dataset is changing connectivity.
If compatibility mode is off and the begin number of elements is the same as the
ending number of elements, then the dataset is changing coordinates only.
See the following file for current information on this reader.
$CEI_HOME/ensight102/src/readers/synthetic/README.txt

Simple Interface
Data Load

For auto-generating a dataset, simply load a synthetic file (typically named with a
suffix .syn) using the Simple Interface method. For interactive use, toggle on the
Advanced Interface Data Load.

Advanced Interface
Data Load

Toggle on the Advanced Interface for interactive creation of your dataset. Then,
put a junk filename in the data file name field (e.g. “dd”) because the EnSight
dialog requires a filename (even a bogus one) and then go directly to the Format
Options tab to control your geometry and variable generation. Interactive creation
of your data requires the Advanced Interface method.
Data Tab

2-134

EnSight 10.2 User Manual

2.3 Synthetic Reader

Format

Set
(Optional)

Choose the Synthetic format. If this format is not available in
this pull down list, then go into your preferences under the
data tab and make this reader available.
Optionally choose a .syn file. Or, for interactive use, enter a
bogus filename (required to be non-empty by the dialog) and
then toggle on the Advanced Interface and go to the Format
Options Tab to design your geometry, variables, etc.

Format Options Tab
Set measured
Verbose
mode
Use ghost
elements

Long names
Compatible
mode

Element type

Boundary
ghosts

Select the measured file and click this button.
Toggle this ON to get more output, useful for debugging
purposes, output to the console. Default is OFF.
Toggle this on to create ghosts between the boundary shared
by SOS servers. If running EnSight in SOS mode, then the
geometry is automatically allocated evenly to each of the
servers. Toggle this ON to use ghost elements between the
servers. (Default is OFF).
Toggle this OFF to use simple part and variable names. Toggle
ON to use long variable names. Default is ON.
Toggle this ON and new options will be limited to retain
compatibility with older versions of EnSight 10.0. Toggle this
OFF to take advantage of new variables and new names, and
other new features as they are added. Default is ON.
Choose an element type. The following are allowable types
but not all are supported (see above for details): Point, Bar 2,
Bar 3, Tri 3, Tri 6, Quad 4, Quad 8, Tet 4, Tet 10, Pyr 5, Pyr
13, Penta 6, Penta 15, Hex 8, Hex 20, Nsided Polygon, Nfaced
Polyhedral, and Structured Hex. (Default is Tri 3). Over
time, more supported types will be added.
Choose None, Convert, or Add for controlling ghosts around
the outer perimeter of the cube(s) and sphere(s). Ghosts are
useful for allowing EnSight to interpolate variable values
rather than extrapolate them.
Choose None to use NO ghosts around the outer boundary.
Choose Convert to convert the outer boundary of cells to ghost
cells. Choose Add to add another layer of cells all around the
outer perimeter of the part(s) that are ghost cells.

Spread out
parts

EnSight 10.2 User Manual

Default is None, so legacy command files should work fine.
Created parts by default are created only slightly off center.
This has the effect of creating overlapping parts when multiple
parts are created which is not useful if you want to see each
part individually. This option spreads the parts out “Little”,
“Medium” or “Large” amounts in the XYZ directions
randomly so that the parts are overlapping a little bit, some
and are mostly spread out, respectively. This is useful, for
example, if you want to see the individual coloration on a large
number of parts.

2-135

2.3 Synthetic Reader

Number of
spheres
Number of
cubes
Number of
planes
Number of
elements start

Number of
elements end
Number of
timesteps
Part scaling
factor
Random
number seed
Number of
scalars
Number of
vectors
Number of
constants

.syn file format

Choose the number of spherical parts. Default 0
Choose the number of cube parts. Default 1.
Choose the number of 2D plane parts. Default 0.
Starting number of elements at timestep 0 for each part.
Default 1000. The reader will attempt to create parts
containing roughly this number of elements using an odd
number of elements in each orthogonal direction. If you
choose 1000 and two cubes with Hex8 elements, and two
sphere parts then your total number of elements will be
roughly 4000 elements. In reality your cubes will be of
dimension 9x9x11 for a total of 891 elements and your spheres
will also have 891 elements because they are cubic elements
mapped onto a sphere resulting in 3564 total elements.
Ending number of elements at the last timestep for each part.
If you choose 10000 and two cube and two sphere parts then
your total number of elements will be 40000. Default 1000.
Choose the number of timesteps. 0 means static data. Default
is 0.
This is used for scaling the part. Default is 1.0
This is for shifting parts randomly around so they don’t all
overlap each other. Default is 0.
Even scalars are nodal and odd scalars are elemental. Default
is 0.
Even scalars are nodal and odd scalars are elemental. Default
is 0.
The first two constants are number of nodes in the dataset and
number of elements in the dataset. Default is 0.

The .syn file can contain the following text:
#!SYN_CASE 1.0
NUMBER_TIMESTEPS num
NUMBER_SPHERES num
NUMBER_CUBES num
NUMBER_ELEMENTS_START num
NUMBER_ELEMENTS_END num
PART_SCALE num
RAND_SEED num
USE_GHOSTS num
VERBOSE num
ELEM_TYPE {see list}
NUMBER_CONSTANTS num
NUMBER_VECTORS num
NUMBER_SCALARS num
LONG_NAMES num

2-136

EnSight 10.2 User Manual

2.3 Synthetic Reader

Valid values for ELEM_TYPE:
Point
Bar 2
Bar 3
Tri 3
Tri 6
Quad 4
Quad 8
Tet 4
Tet 10
Pyr 5
Pyr 13
Penta 6
Penta 15
Hex 8
Hex 20
Nsided Polygon
Nfaced Polyhedral
Structured Hex

For legacy reasons, the former 'tri' and 'hex' keywords are also still supported.
These options map 1 for 1 with the options found in the data reader dialog under
the Format Options Tab. Note: USE_GHOSTS, LONG_NAMES and VERBOSE
are true if  is non-zero.
.syn file example

The following example creates a 20 timestep dataset with 3 spheres and 2 cubes.
Each sphere/cube will have 1M triangles. Each cube and sphere will have a
diameter of 0.2 (and the centroid will be randomly placed inside of a 1.0x1.0x1.0
box).
#!SYN_CASE 1.0
NUMBER_TIMESTEPS 20
NUMBER_SPHERES 3
NUMBER_CUBES 2
NUMBER_ELEMENTS_START 1000000
PART_SCALE 0.2

(see How To Read Data)

EnSight 10.2 User Manual

2-137

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.
This is discussed below. 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/ensight102/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.
BINARY
Format
Set plot
(or dat)

Use the Tecplot Binary, or the legacy TECPLOT 7.x format.
This field should have the .plt name for binary data. Use a
asterisk for transient multiple files (one timestep per file),
filename*.dat

Format Options Tab Tecplot BINARY
Set measured
Tecplot
Binary Other
Options

Select the measured file and click this button.

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-138

EnSight 10.2 User Manual

2.3 Tecplot Reader

Include Face/
Edge Parts
Include
NodeSet
Parts
Include local
elem res
comps (if
any)

Include
Tensor
derived
(VonMises,
etc.)

Include any Face or Edge sets defined. These are some logical
set of particular faces and/or edges of full elements. Default is
off.
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 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
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 = 1 for 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

Regular Part
Creation
Convention
Var naming
convention

or any legal combination. example: for VonMises and Max
Shear only, use 18. Default is off
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

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).

EnSight 10.2 User Manual

2-139

2.3 Tecplot 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. This is a global averaging, so shared nodes are
affected by all parts that share a node.
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. This is a global averaging, so shared
nodes are affected by all parts that share a node.
Ave 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. This is a local averaging, so all
averaging is contained within each part.

If Sections,
which:

Geom weighted ave to node  - Element results
(whether centroidal or element nodal) will be averaged to the
nodes using geometry weighting. Thus will be per_node
variables in EnSight. This is a local averaging, so all averaging
is contained within each part.
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

Section Num

Separate Vars per Section - A separate variable will be created
for each section.
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.

ASCII
Format
Set plot
(or dat)

Use the or Tecplot_ASCII.
This field should have the .dat file name for ASCII data. Use a
asterisk for transient multiple files (one timestep per file),
filename*.dat

Format Options Tab Tecplot BINARY
Set measured

2-140

Select the measured file and click this button.

EnSight 10.2 User Manual

2.3 Tecplot Reader

Tecplot
ASCII Other
Options

Single File
Transient

Changing
Connectivity

Console
Output

Toggle this ON to load a single file as transient data (default is
OFF). If this toggle is ON, then the reader tries to find the
SOLUTIONTIME keyword to identify the time value of a
given part. If ZONE T= keyword is encountered prior to
finding a SOLUTIONTIME keyword, then the reader tries to
parse the Zone T contents to determine the time for that part.
So the ZONE T must contain a parseable time value if there is
no SOLUTIONTIME keyword.
There is no meta-data in the Tecplot ASCII file indicating
whether the connectivity changes over time. When this toggle
is ON, then transient data is loaded as changing connectivity
(coordinates and connectivity are read in at every timestep,
which is the safe (but slow) assumption (default ON). This
causes EnSight limitations, such as temporal calculations and
temporal queries. So if you know that your data doesn’t
change connectivity through time you can toggle this off. If
you are wrong then EnSight may crash.
If you want more information and detail about the file you are
reading, choose Console Output Verbose. If you are having
problems reading the file, choose Console Output Debug. The
Console output is generated at the Server console window.
Problem reports should include the Console output debug
information (note: default is Normal which includes very little
server console output).

(see How To Read Data)

EnSight 10.2 User Manual

2-141

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/ensight102/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
Set tri/pos

2-142

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

2.3 Vectis Reader

Format Options Tab
Set measured

Select the measured file and click this button.

(see How To Read Data)

EnSight 10.2 User Manual

2-143

2.3 VTK Reader

VTK Reader
Overview
Description

This reader is designed to read the VTM, VTU, VTS, and VTK file formats.

VTK

The VTK format is a legacy format containing both geometry and variable data.

VTU and VTS

The VTU and VTS formats are both a Serial Grid format using an XML-based
syntax containing both geometry and variable data. However, VTU uses an
Unstructured Grid, and VTS uses a Structured Grid.

VTM

The VTM file enables the user to pass in one filename that points to many
spatially decomposed files, each containing a portion of the solution that was run
in parallel. For example, the VTM file can contain multiple serial VTK, VTU, or
VTS filenames, that were perhaps solved by multiple, parallel compute nodes.
And, each of the VTK, VTU, or VTK files contains its own geometry and
variables representing a spatial decomposition of the total solution at a given
timestep.
For example, suppose you have transient data with two timesteps solved on four
solver compute nodes. You might have the following files and sub folders:
file_0.vtm
file_1.vtm
./dir0/file_0_0.vtu, ./dir0/file_0_1.vtu, ./dir0/file_0_2.vtu, ./dir0/file_0_3.vtu
./dir1/file_1_0.vtu, ./dir1/file_1_1.vtu, ./dir1/file_1_2.vtu, ./dir1/file_1_3.vtu

Note that file_0.vtm and file_1.vtm each points to the geometry and variables at
timestep 0 and 1, respectively. It is important to remember that file_0.vtm contains
XML pointing to its four files using a local folder structure as shown below, so it
is critical that the subfolder and file structure be maintained if the data is moved.
Shown below are the spatially decomposed files for timestep 0 found in dir0.
dir0/file_0_0.vtu
dir0/file_0_1.vtu
dir0/file_0_2.vtu
dir0/file_0_3.vtu
Transient

Since each file represents a single timestep, use an asterisk (*) to read in transient
data. Loading the transient VTM file in the example above would require picking
one of the .vtm files (so that it appears in the load field) and then typing in an
asterisk in place of the number: file*.vtm.

SoS

The VTK reader supports parallel reading of the parallel VTM file(s) (see Use
Server of Servers). Suppose you are running EnSight in Server of Server (SoS)
mode and enter in file*.vtm to read in transient data.
If you have the same number of servers as files then each file is assigned to one
server. In the above example, if you have four servers, then at timestep 0, the first
server will read only the data contained in dir0/file_0_0.vtu . When you change
time to timestep 1, the first server will now read the data from dir1/file_1_0.vtu.
Similarly for the other servers, so that each server is reading spatially decomposed
data completely separately from the other servers.
If you have less servers than files, then some servers will be assigned more than
one file to read based on file sizes for efficient allocation of resources.

2-144

EnSight 10.2 User Manual

2.3 VTK Reader

Currently the VTK reader does not support more servers than files.
Limitations

This reader does not read rectilinear grid (VTR) files, nor does it support polydata
files (VTP).
The reader does not support n-faced, 3D polyhedral elements in any of the formats
(they are simply skipped and will result in holes in your geometry), but does
support n-sided 2D polygon elements.
The reader does not read the parallel solution files (PVTK, PVTU, PVTS) which
contain extra information pertaining to the parallel solution.

Simple Interface
Data Load

Load your file (typically named with a suffix .vtk or .vtu or .vtm or .vts) using
the Simple Interface method.

Advanced Interface
Data Load

Load your file (typically named with one of the above suffixes ) using the
Advanced Interface method.
Data Tab
Format
Set vtm, vtu,
vts, vtk

Use the VTK format.
Select the VTK file (typically .VTK, .VTS or .VTU or
.VTM) and click this button. Use file*.vtk, file*.vts, etc.
(where the asterisk (*) replaces the number) for transient
datasets. Each file will represent one timestep.

Format Options Tab
Set measured
VTK Reader
Other
Options

Select the measured file and click this button.

Debug Mode

Toggle this ON to get extra, debugging information printed to
the console in the event of problems reading the data. Note:
default is OFF.

(see How To Read Data)

EnSight 10.2 User Manual

2-145

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: