Runtime Gateway

Trademarks and Legal Notices
Isight and Fiper are products of, and are offered by, Dassault Systèmes Simulia Corp. under license from
Engineous Software, Inc., Cary, North Carolina, USA, a member of the Dassault Systèmes Group. These
products may be used or reproduced only in accordance with the terms of such license.
This documentation is subject to the terms and conditions of either the software license agreement signed
by the parties, or, absent such an agreement, the then current software license agreement to which the
documentation relates.
This documentation and the software described in this documentation are subject to change without prior
notice. No part of this documentation may be reproduced or distributed in any form without prior written
permission of Dassault Systèmes or its subsidiary.
Export and re-export of the Isight and Fiper Software and this documentation is subject to United States
and other export control regulations. Each user is responsible for compliance with applicable export
regulations.
© Dassault Systèmes, 2009
Printed in the United States of America.
Isight, Fiper, the 3DS logo, and SIMULIA are trademarks or registered trademarks of Dassault Systèmes
or its subsidiaries in the United States and/or other countries. Other company, product, and service names
may be trademarks or service marks of their respective owners. For additional information concerning
trademarks, copyrights, and licenses, see the notices at: http://www.simulia.com/products/
products_legal.html.
OPEN SOURCE PROGRAMS: This release of Isight and Fiper uses several open source or free programs
(“OS Programs”). Each such program is distributed with the Isight and Fiper Software in binary form and,
except as permitted by the applicable license, without modification. Each such program is available online
for free downloading and, if required by the applicable OS Program license, the source code will be made
available by Dassault Systèmes or its subsidiary upon request. For a complete list of OS Programs utilized
by Isight and Fiper, as well as licensing documentation for these programs, see http://www.simulia.com/
products/products_legal.html.
Dassault Systèmes or its subsidiaries may have patents or pending patent applications, trademarks,
copyrights, or other intellectual property rights covering the Isight and Fiper Software and/or its
documentation. No license of such patents, trademarks, copyrights, or other intellectual property rights is
provided or implied except as may be expressly provided in a written license agreement from Dassault
Systèmes or its subsidiary.
3
Offices and Representatives

SIMULIA Worldwide Headquarters Rising Sun Mills, 166 Valley Street, Providence, RI 02909–2499, Tel: +1 401 276 4400,
Fax: +1 401 276 4408, simulia.support@3ds.com, http://www.simulia.com
SIMULIA European Headquarters Gaetano Martinolaan 95, P. O. Box 1637, 6201 BP Maastricht, The Netherlands, Tel: +31 43 356 6906,
Fax: +31 43 356 6908, info.europe@simulia.com
Sales, Support, and Services
North America Central, Main office, West Lafayette, IN, Tel: +1 765 497 1373, simulia.central.support@3ds.com
Central, Cincinnati office, West Chester, OH, Tel: +1 513 275 1430, simulia.central.support@3ds.com
Central, Minneapolis/St. Paul office, Woodbury, MN, Tel: +1 612 424 9044, simulia.central.support@3ds.com
East, Main office, Warwick, RI, Tel: +1 401 739 3637, simulia.east.support@3ds.com
Erie office, Beachwood, OH, Tel: +1 216 378 1070, simulia.erie.info@3ds.com
Great Lakes, Main office, Northville, MI, Tel: +1 248 349 4669, simulia.greatlakes.info@3ds.com
South, Main office, Lewisville, TX, Tel: +1 972 221 6500, simulia.south.info@3ds.com
West, Main office, Fremont, CA, Tel: +1 510 794 5891, simulia.west.support@3ds.com
Argentina Dassault Systèmes Latin America, Buenos Aires, Tel: +54 11 4345 2360, Horacio.Burbridge@3ds.com
Australia Dassault Systèmes Australia Pty. Ltd., Richmond VIC, Tel: +61 3 9421 2900, simulia.au.support@3ds.com
Austria Vienna, Tel: +43 1 929 16 25-0, simulia.at.info@3ds.com
Benelux Huizen, The Netherlands, Tel: +31 35 52 58 424, simulia.benelux.support@3ds.com
Brazil SMARTTECH Mecânica, São Paulo SP, Tel: +55 11 3168 3388, smarttech@smarttech.com.br
SMARTTECH Mecânica, Rio de Janeiro RJ, Tel: + 55 21 3852 2360, smarttech@smarttech.com.br
Czech Republic Synerma s. r. o., Psáry, Prague-West, Tel: +420 603 145 769, abaqus@synerma.cz
France SIMULIA France SAS, Main office, Velizy Villacoublay, Tel: +33 1 61 62 72 72, simulia.fr.support@3ds.com
Toulouse office, Toulouse, Tel: +33 5 61 16 99 47 (phone for sales only), simulia.fr.support@3ds.com
Germany Aachen office, Aachen, Tel: +49 241 474 01 0, simulia.de.info@3ds.com
Munich office, Munich, Tel: +49 89 543 48 77 0, simulia.de.info@3ds.com
Greece 3 Dimensional Data Systems, Athens, Tel: +30 694 3076316, support@3dds.gr
India Abaqus Engineering India Pvt Ltd., Main office, Chennai, Tamil Nadu, Tel: +91 44 43443000, simulia.in.info@3ds.com
Israel ADCOM, Givataim, Tel: +972 3 7325311, shmulik.keidar@adcomsim.co.il
Italy Milano (MI), Tel: +39 02 39211211, simulia.ity.info@3ds.com
Japan Tokyo office, Tokyo, Tel: +81 3 5474 5817, tokyo@simulia.com
Osaka office, Osaka, Tel: +81 6 4803 5020, osaka@simulia.com
Korea Mapo-Gu, Seoul, Tel: +82 2 785 6707/8, simulia.kr.info@3ds.com
Malaysia WorleyParsons Advanced Analysis, Kuala Lumpur, Tel: +603 2039 9405, abaqus.my@worleyparsons.com
New Zealand Matrix Applied Computing Ltd., Auckland, Tel: +64 9 623 1223, support@matrix.co.nz
Poland BudSoft Sp. z o.o., Sw. Marcin, Tel: +48 61 8508 466, budsoft@budsoft.com.pl
Russia, Belarus & Ukraine TESIS Ltd., Moscow, Tel: +7 495 612 44 22, info@tesis.com.ru
Scandinavia Västerås, Sweden, Tel: +46 21 15 08 70, info@simulia.se
Singapore WorleyParsons Advanced Analysis, Singapore, Tel: +65 6735 8444, abaqus.sg@worleyparsons.com
South Africa Finite Element Analysis Services (Pty) Ltd., 7700 Mowbray, Tel: +27 21 448 7608, feas@feas.co.za
Spain Principia Ingenieros Consultores, S.A., Madrid, Tel: +34 91 209 1482, abaqus@principia.es
Taiwan Simutech Solution Corporation, Taipei, R.O.C., Tel: +886 2 2507 9550, ariel@simutech.com.tw
Thailand WorleyParsons Advanced Analysis Group, Bangkok, Tel: +66 2 689 3000, abaqus.th@worleyparsons.com
Turkey A-Ztech Ltd., Istanbul, Tel: +90 216 361 8850, info@a-ztech.com.tr
United Kingdom Dassault Systèmes Simulia Ltd., Main office, Warrington, Tel: +44 1 925 830900, simulia.uk.info@3ds.com
Dassault Systèmes Simulia Ltd., Kent office, Nr. Sevenoaks, Tel: +44 1 732 834930, simulia.uk.info@3ds.com
Sales Only
North America East, Mid-Atlantic office, Forest Hill, MD, Tel: +1 410 420 8587, simulia.east.support@3ds.com
Great Lakes, East Canada office, Toronto, ON, Canada, Tel: + 1 416 466 4009, simulia.greatlakes.info@3ds.com
South, Southeast office, Acworth, GA, Tel: +1 770 795 0960, simulia.south.info@3ds.com
West, Pacific Southwest office, Southern CA and AZ, Tustin, CA, Tel: +1 510 794 5891, Ext. 152, simulia.west.info@3ds.com
West, Rocky Mountains office, Boulder, CO, Tel: +1 510 794 5891, Ext. 151, simulia.west.info@3ds.com
Finland Vantaa, Tel: +358 9 2517 8157, info@simulia.fi
India Abaqus Engineering India Pvt Ltd, Delhi office, New Delhi, Tel: +91 11 65171877, simulia.in.info@3ds.com
Abaqus Engineering India Pvt Ltd, Pune office, Tel: +91 20 30483382, simulia.in.info@3ds.com
China Representative Offices
China Main office, Chaoyang District, Beijing, P. R. China, Tel: + 86 10 65362345, simulia.cn.info@3ds.com
Shanghai office, Shanghai, P. R. China, Tel: + 86 21 5888 0101, simulia.cn.info@3ds.com
Complete contact information is available at http://www.simulia.com/locations/locations.html
Isight Runtime Gateway Guide

4

5
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
What is Isight?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Conventions Used in This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Mouse Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Keyboard Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Platform Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
SIMULIA Online Support System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Technical Engineering Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Systems Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Anonymous FTP Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Contacting Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Support for Academic Institutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1 Using the Runtime Gateway Interface . . . . . . . . . . . . . . . . . . . . . . 19

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Using the Runtime Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Accessing the Runtime Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Understanding Connection Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Loading a Model From the Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Loading a Model From the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

6 Table of Contents
Saving Models and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Understanding the Runtime Gateway Layout. . . . . . . . . . . . . . . . . . . . . . . . . . 28
Controlling Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Overview of the Available Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Viewing Tabs in Separate Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Setting Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Working With Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Defining the Local Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Accessing the Job Database Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Searching For a Job in the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Opening a Job from a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Stopping Running Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Re-running Failed Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Creating Custom Job Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Importing and Exporting Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Selecting Loaded Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Removing Jobs From Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Setting Job Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Deleting Jobs from the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Understanding the Displayed Job Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Setting Workflow Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Editing Process Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Changing Process Components in a Workflow . . . . . . . . . . . . . . . . . . . . . . . . 83
Viewing/Hiding Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Saving the Workflow Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Using the Component Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Understanding Graph, Table, and Other Data Analysis Options . . . . . . . . . . . . . . 87

Viewing Parameter Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Understanding the Parameters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Setting Viewed Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Viewing and Editing Problem Formulation Settings . . . . . . . . . . . . . . . . . . . . 91
Filtering Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Importing and Exporting Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Viewing Design Driver Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Using the History Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Table of Contents 7
Using the Data Analysis Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Using Approximation Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Viewing the Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Using the Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
Viewing the Log Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Accessing the Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Viewing the Dataflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118

Saving Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Importing Data From a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Creating a Report Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Creating a Report Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Searching for a Component, Parameter, or File in a Model . . . . . . . . . . . . . . . . . . .132

Using the Advanced Find Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
Creating an ACS Connection Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
2 Visual Design with Approximations . . . . . . . . . . . . . . . . . . . . . . . . 139

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140
Accessing Approximations of a Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141
Creating an Approximation Using System-Determined Default Settings . . . . . . . .142
Creating an Approximation Using the Approximation Wizard . . . . . . . . . . . . . . . .145
Creating an Automatic Approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
Creating a User-Defined Approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
Creating an Approximation Using a Previously Saved File . . . . . . . . . . . . . . .169
Editing an Existing Approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175

Using Approximations at Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
Initializing an Approximation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179
Visualizing an Approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
Adjusting Input and Output Values Using the Slider View . . . . . . . . . . . . . . . .185
Adjusting Input and Output Values Using the Table View . . . . . . . . . . . . . . . .186
Viewing the Approximation Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

8 Table of Contents
Creating New Approximation Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Exporting a Graph. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Setting Graph Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Removing Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Setting Graph Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Searching the Design Using Specified Criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Setting Your Criteria and Searching the Design . . . . . . . . . . . . . . . . . . . . . . . . 203
Setting Component Input Values from the Visual Design Tab . . . . . . . . . . . . . . . . 209
Comparing Actual and Approximation Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Analyzing Approximation Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Using the Error Analysis Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Understanding the Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Viewing Approximation Data After Initialization. . . . . . . . . . . . . . . . . . . . . . . . . . 218

Saving an Approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Deleting an Approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
3 Using Graphs, Tables, and Other Data Analysis Tools . . . . . . . . . 223

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Using Data Sampling with Graphs, EDM, and 2D Scatter Plots . . . . . . . . . . . . . . 224
Understanding the Graphs Overview Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Using Graphs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Creating a Graph for a Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Using Specialized Graphs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Updating an Existing Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Changing Graph Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Viewing Graph Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Exporting Graph Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Copying a Graph. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Normalizing a Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Deleting Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Using Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Creating a Table for a Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Updating an Existing Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Table of Contents 9
Viewing Table Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259

Customizing a Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264
Exporting Table Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266
Copying Table Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266
Deleting Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267
Using the Engineering Data Mining Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267

Accessing the Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268
Changing the Selected Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270
Viewing the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271
Using the Correlation Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273

Accessing the Correlation Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274
Viewing the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
Using the Graphing Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277
Working with the Filter Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277
Using the Two-dimensional (2D) Scatter Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . .279

Using the Taguchi Main Effects Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283
Viewing the Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285
Viewing the Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290
A Runtime Gateway Reference Information . . . . . . . . . . . . . . . . . . . 291

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292
Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293
Edit Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294
Run Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295
View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296
Jobs Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .297
Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298
Toolbar Buttons and Other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299

Setting Runtime Gateway Options Using Environment Variables . . . . . . . . . . . . . .300

10 Table of Contents
Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Runtime Gateway Keyboard Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Using Keyboard Shortcuts on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Command Line Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
B Approximation Reference Information . . . . . . . . . . . . . . . . . . . . . 311

Available Approximation Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
RBF Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Response Surface Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
DOE Technique Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Setting Data File Technique Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Setting Latin Hypercube Technique Options . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Setting Optimal Latin Hypercube Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Setting Orthogonal Array Technique Options . . . . . . . . . . . . . . . . . . . . . . . . . 327
Setting Parameter Study Technique Options . . . . . . . . . . . . . . . . . . . . . . . . . . 328
C Correlation Map and Pareto Plot Reference Information . . . . . . 329

Correlation Map Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Pareto Plot Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

11
Preface
This book is your guide to using the Isight Runtime Gateway for viewing and
interpreting results.
What is Isight?
Isight provides a suite of visual and flexible tools to set up and manage computer
software required to execute simulation-based design processes, including commercial
CAD/CAE software, internally developed programs, and Excel spreadsheets. The open
API supports the development of custom interfaces to link additional in-house and
commercial applications by partners and customers.
The rapid integration of these applications and Isight’s ability to automate their
execution greatly accelerates the evaluation of product design alternatives.
Using advanced techniques such as optimization, DFSS (Design for Six Sigma),
approximations, and DOE, engineers are able to thoroughly explore the design space.
Advanced, interactive post processing tools allow engineers to see the design space
from multiple points of view. Design trade-offs and the relationships between
parameters and results are easily understood and assessed, leading to the best possible
design decisions.
The process integration and design optimization capabilities in Isight enable design
organizations to reduce design cycle time and manufacturing cost, and significantly
improve product performance, quality, and reliability.
When used in conjunction with Fiper, an internet-based distributed framework is

created, which supports collaboration among geographically distributed engineering

12 Preface
and business partners. In this configuration, Isight acts as the “client” and Fiper acts as
the “server”.
Documentation
The following manuals are available in the Isight and Fiper library:
Isight Component Guide
Isight Development Guide
Isight Getting Started Guide

Isight User’s Guide
Fiper Installation and Configuration Guide - WebSphere and DB2
Fiper Installation and Configuration Guide - WebSphere and Oracle

Fiper Installation and Configuration Guide - WebLogic and Oracle
Fiper Express Installation Guide
Fiper Federation (B2B) Guide - WebSphere
Fiper WebTop Guide
Conventions Used in This Book

The following sections describe the typographic terminology and other conventions
used in this book.

Conventions Used in This Book 13
Typographical Conventions
This book uses the following typographical conventions:
Convention Explanation
italics Introduces new terms with which you may not be familiar,
and is used occasionally for emphasis.
bold Emphasizes important information. Also indicates button,
menu, and icon names on which you can act. For example,
click Next.
UPPERCASE Indicates the name of a file. For operating environments
that use case-sensitive filenames (such as UNIX), the
correct capitalization is used in information specific to
those environments.
Also indicates keys or key combinations that you can use.
For example, press the ENTER key.
monospace Indicates syntax examples, values that you specify, or
results that you receive.
monospaced Indicates names that are placeholders for values that you
italics specify. For example, filename.
forward slash / Separates menus and their associated commands. For
example, Select File / Copy means that you should select
Copy from the File menu.
The slash also separates directory levels when specifying
locations under UNIX.
vertical rule | Indicates an “OR” separator used to delineate items.
brackets [ ] Indicates optional items. For example, in the following
statement: SELECT [DISTINCT], DISTINCT is an
optional keyword.
Also indicates sections of the Windows Registry.
braces { } Indicates that you must select one item. For example, {yes |
no} means that you must specify either yes or no.
ellipsis . . . Indicates that the immediately preceding item can be
repeated any number of times in succession. An ellipsis
following a closing bracket indicates that all information in
that unit can be repeated.

14 Preface
Mouse Conventions
This action... Means to...
Click Point to an object with the mouse pointer and momentarily
press the left mouse button.
Double-click Press the left mouse button twice.
Right-click Momentarily press the right mouse button.
Drag Press and hold the left mouse button while dragging item(s)
to another part of the screen.
SHIFT+Click Click an object to select it; then, press and hold the SHIFT
key. Click another object to select the intervening series of
objects.
CTRL+Click Press and hold the CTRL key; then, click a selection. This
lets you select or deselect any combination of objects.
Keyboard Conventions
Select menu items by using the mouse or pressing ALT+ the key letter of the menu
name or item.
Platform Information
For complete details on supported platforms, refer to the following website:
http://www.simulia.com/support/sup_systems_info.html

Support 15
Support
Both technical engineering support (for problems with creating a model or performing
an analysis) and systems support (for installation, licensing, and hardware-related
problems) for Isight are offered through a network of local SIMULIA support offices.
Contact information is listed in the front of each manual.
SIMULIA Online Support System

The SIMULIA Online Support System (SOSS) has a knowledge database of SIMULIA
Answers. The SIMULIA Answers are solutions to questions that we have had to
answer or guidelines on how to use Abaqus, Isight, Fiper, SIMULIA SLM, and other
SIMULIA products. You can also submit new requests for support in the SOSS. All
support incidents are tracked in the SOSS. If you are contacting us by means outside
the SOSS to discuss an existing support problem and you know the incident number,
please mention it so that we can consult the database to see what the latest action has
been.
To use the SOSS, you need to register with the system. Visit the My Support page at
www.simulia.com for instructions on how to register.
Many questions can also be answered by visiting the Products page and the Support
page at www.simulia.com. The information available online includes:
Link to the SOSS

Systems information and computer requirements
Performance data
Status reports
Training seminar schedule
INSIGHTS Magazine
Technology briefs

16 Preface
Technical Engineering Support

Technical support engineers are available to assist in clarifying product features and
checking errors by giving both general information on using the product and
information on its application to specific analyses. If you have concerns about an
analysis, we suggest that you contact us at an early stage, since it is usually easier to
solve problems at the beginning of a project rather than trying to correct an analysis at
the end.
Please have the following information ready before contacting the technical
engineering support hotline, and include it in any written contacts:
The release of Isight that are you using, which can be obtained by accessing the
VERSION file at the top level of your Isight installation directory.
The type of computer on which you are running Isight.
The symptoms of any problems, including the exact error messages, if any.
Any log files associated with the error.
Workarounds or tests that you have already tried.
When contacting support about a specific problem, any available product output files
may be helpful in answering questions that the support engineer may ask you.
The support engineer will try to diagnose your problem from the model description and
a description of the difficulties you are having. The more detailed information you
provide, the easier it will be for the support engineer to understand and solve your
problem.
If the support engineer cannot diagnose your problem from this information, you may
be asked to supply a model file. The data can be attached to a support incident in the
SIMULIA Online Support System (SOSS). It can also be sent by means of e-mail,
tape, disk, or ftp. Please check the Support Overview page at www.simulia.com for the
media formats that are currently accepted.
If you are contacting us to discuss an existing problem, please give the receptionist the
support engineer's name if contacting us via telephone or include it at the top of any e-
mail correspondence.

Support for Academic Institutions 17
Systems Support
Systems support engineers can help you resolve issues related to the installation and
running of the product, including licensing difficulties, that are not covered by
technical engineering support.
You should install the product by carefully following the instructions in the installation
guide. If you encounter problems with the installation or licensing, first review the
instructions in the installation guide to ensure that they have been followed correctly. If
this does not resolve the problems, consult the SIMULIA Answers database in the
SIMULIA Online Support System for information about known installation problems.
If this does not address your situation, please create an incident in the SOSS and
describe your problem.
Anonymous FTP Site

To facilitate data transfer with SIMULIA, an anonymous ftp account is available on
the computer ftp.simulia.com. Login as user anonymous, and type your e-mail address
as your password. Contact support before placing files on the site.
Contacting Technical Support

Use the My Support page at www.simulia.com, or obtain local support office contact
information from the Locations page at www.simulia.com.
In addition, contact information for offices and representatives is listed in the front of
this manual.
Support for Academic Institutions

Under the terms of the Academic License Agreement we do not provide support to
users at academic institutions. Academic users can purchase technical support on an
hourly basis. For more information, please see www.simulia.com or contact your local
support office.

18 Preface
Training
SIMULIA offices offer regularly scheduled public training classes, including classes
on Isight. We also provide training seminars at customer sites. All training classes and
seminars include workshops to provide practical experience with our products. For a
schedule and descriptions of available classes, see www.simulia.com or call your local
representative.
Feedback
We welcome any suggestions for improvements to Isight software, the support
program, or documentation. We will ensure that any enhancement requests you make
are considered for future releases. If you wish to make a suggestion about the service
or products, refer to www.simulia.com. Complaints should be addressed by contacting
your local office or through www.simulia.com.

19
1 Using the Runtime Gateway

Interface
This chapter discusses using the different options available in the Runtime Gateway,
including the interface layout and non-visual options. Information on graphs, tables,
and other design analysis tools is provided in a separate chapter. This chapter is
divided into the following topics:
“Introduction,” on page 20
“Using the Runtime Gateway,” on page 20
“Working With Jobs,” on page 56

“Setting Workflow Options,” on page 82
“Understanding Graph, Table, and Other Data Analysis Options,” on page 87
“Viewing Parameter Information,” on page 88

“Viewing the Summary,” on page 111
“Using the Logs,” on page 113
“Viewing the Dataflow,” on page 118
“Saving Results,” on page 119
“Importing Data From a File,” on page 123
“Generating Reports,” on page 128
“Searching for a Component, Parameter, or File in a Model,” on page 132
“Creating an ACS Connection Profile,” on page 136

20 Chapter 1 Using the Runtime Gateway Interface
Introduction
In general, the Runtime Gateway provides execution control and monitoring options
for a model, displays execution related information, and can be used to create
approximations for components. Components are selected from the list on the left side
of the interface, and their corresponding information is displayed on several tabs
provided on the right side of the interface. You can use this list of components to
change between components at any time, for both information viewing and execution
purposes. You can also use the Runtime Gateway to control execution in various ways.
The Runtime Gateway is typically used in the following two configurations:
It automatically appears when a model is executed from the Design Gateway.
It can be opened as a separate interface, and it can execute models that already
exist (meaning they have already been created using the Design Gateway) and are
saved to disk or have been published.
Each of these configurations provides access to the same options. The main difference
is the way that the interface is initially accessed.
Note: Altering the graphs and tables on the Runtime Gateway changes the composition
of the model. Changes made to parameters using the Parameters tab on the Runtime
Gateway affect the model. All other changes are specific to the Runtime Gateway and
do not affect the model.
Using the Runtime Gateway

As stated, the Runtime Gateway is an interface that helps you control execution,
working with approximations, and view results of that execution. The interface can be
accessed at any time in order to run existing models, and automatically appears when
an execution is started from the Design Gateway.

Using the Runtime Gateway 21
This section is divided into the following topics:
“Accessing the Runtime Gateway” on this page
“Understanding Connection Profiles,” on page 22
“Loading a Model From the Interface,” on page 23
“Loading a Model From the Command Line,” on page 26

“Saving Models and Components,” on page 27
“Understanding the Runtime Gateway Layout,” on page 28
“Controlling Execution,” on page 31

“Overview of the Available Tabs,” on page 39
“Viewing Tabs in Separate Windows,” on page 41
“Setting Preferences,” on page 41
Accessing the Runtime Gateway

There are three methods for accessing the Runtime Gateway:
Executing a model from the Design Gateway. For more information, refer to the
Isight User’s Guide. This option opens the Runtime Gateway, loads the model
currently open in the Design Gateway, and executes the model.
Accessing the Runtime Gateway option from the Design Gateway View menu.
This option opens the Runtime Gateway with the current model loaded, but does
not execute the model. For more information on loading a model, see “Loading a
Model From the Interface,” on page 23.
Opening as a separate interface. You have two options for opening the interface
without using the Design Gateway:
Windows only: Click the Start button; then, point to All Programs / Isight 3.5
and click Runtime Gateway.
Execute the rt_gateway.exe file (or rt_gateway file on UNIX/Linux

systems) located in the <Isight_install_directory>\bin\win32 directory (or the
<Isight_install_directory>/bin directory on UNIX/Linux). When using this

option, you also have access to several command line options that can control
the start of the program. For more information, see “Loading a Model From
the Command Line,” on page 26.
Note: If you are starting the Runtime Gateway on a 64-bit Linux system, the
64-bit version of the interface is started by default. However, if you have
installed both the 32-bit and 64-bit versions, you can specify the version that
will be used by adding -32 or -64 to the end of the rt_gateway command
(be sure to leave a space between the two commands). Additionally, you can
set the default value for the rt_gateway command using the FIPER_BITS
environment variable. For more information on this variable and other
environment variables, refer to the Isight User’s Guide.
Understanding Connection Profiles

Connection profiles allow you to determine the type of environment you will use for
your Isight session. By default, Isight is automatically run in the Standalone connection
profile. However, if you have access to an ACS in the Fiper environment, you can use
connection profiles to connect to a specific ACS. Numerous ACS machines can be
defined, but you can only connect to one ACS at a time.
When you start an Isight interface and have defined at least one ACS connection
profile, the Logon dialog box appears, allowing you to determine your session
environment. If no ACS connection profiles have been created, the interface is
automatically launched in Standalone mode.
If you do not see a connection profile that corresponds to the correct ACS machine,
you can create the necessary connection profile as described in “Creating an ACS
Connection Profile,” on page 136.

The following two types of connections are available:
Standalone. This option, available at any time whether you have access to an ACS
in the Fiper environment or not, connects you to the local Library on your current
machine, and does not establish a connection with an ACS. This connection profile
is provided, by default, with Isight and does not need to be created. It is
automatically selected if no ACS connection profiles have been created.
Fiper ACS Connection. This option connects you to an ACS in the Fiper
environment, and provides access to a remote Library. It also requires you to enter
your user name (user ID) and password, if security is enabled on the ACS.
If you do not see a connection profile that corresponds to the correct ACS machine,
you can create the necessary connection profile as described in “Creating an ACS
Connection Profile,” on page 136.
Note: Although you may have multiple connection profiles defining connections to
multiple systems acting as an ACS, you can only connect to one ACS at a time.
For more information on configuring an ACS, refer to the Fiper Installation and
Configuration Guide that matches your ACS installation.
Loading a Model From the Interface

If you execute a model from the Design Gateway or access it from the View menu, the
model is automatically loaded into the Runtime Gateway. However, if you launch the
Runtime Gateway as a standalone interface, you need to specify the model you want to
use.
When loading a model into the Runtime Gateway, only the model information itself is
loaded. No job information (such as parameter values or results) is loaded. However,
you can load a model and job information if you have a connection to a job database.
When you select a specific job, the associated model is automatically opened in the
Runtime Gateway. For more information, see “Searching For a Job in the Database,”
on page 58.
Note: If you use the rt_gateway.exe file (rt_gateway file on UNIX/Linux) to

start the Runtime Gateway, you can specify a model at the command prompt. For more
information, see “Loading a Model From the Command Line,” on page 26.

The following options are available when loading a model:
“Opening a Model From the Disk” on this page
“Opening a Model From a Library” on this page
Opening a Model From the Disk

To open a model from the local hard drive:
1. Select Open... from the Runtime Gateway File menu. The Open dialog box
appears.
2. Navigate to the model; then, click it to select it.
3. Click Open. The model is loaded into the Runtime Gateway.
Opening a Model From a Library

Models opened from a Library must first be published to the Library. For more
information on publishing models, refer to the Isight User’s Guide.

To open a model from the current Library:
1. Select Open Model from Library... from the Runtime Gateway File menu. The
Isight Library dialog box appears.
2. Navigate to the model you want to use; then, click it to select it. If you cannot
locate the correct model, verify that you are connected to the proper Library, or
contact the individual who published the model for more information.

In the following example, the I-beam example model has been selected.
3. Click Open. The model is loaded into the Runtime Gateway.
Loading a Model From the Command Line

If you launch the Runtime Gateway from a Command Prompt dialog box (Windows)
or a terminal window (UNIX/Linux), you can specify the model to be loaded at the
time of the file execution.
Note: The rt_gateway.exe file is located in the <Isight_install_directory>\bin\

win32 directory on Windows-based systems. The rt_gateway file is located in the
<Isight_install_directory>/bin directory on UNIX/Linux-based systems.
For example, the following command opens the Runtime Gateway as a separate
interface on Windows, and loads the sample model from the local hard drive:
rt_gateway.exe \sample_models\sample.zmf

At the same time, the following command opens the Runtime Gateway as a separate
interface on Windows, and loads the sample model from a machine called fd_server:
rt_gateway.exe \\fd_server\sample_models\sample.zmf
Note: You must have the proper permissions to access machines across a network. For
more information, contact your local systems administrator.
For information on additional command line options available with the Runtime
Gateway, see “Setting Runtime Gateway Options Using Environment Variables,” on
page 300.
Saving Models and Components

You can save models and components from the Runtime Gateway, which can then be
opened by either the Runtime Gateway or the Design Gateway. This option allows you
to save Runtime Gateway-specific information to a model (for example,
approximations created directly in the Runtime Gateway).
Both models and components can be saved. The following procedures describe how to
save a model or component to your local disk. However, you can also publish a model
or component to your Library, which saves the same information but in a different
manner. For more information on publishing, refer to the Isight User’s Guide.
Saving a Model
To save a model, simply perform one of the following actions:
Select Save Model from the File menu to save the model with its current name. If
the model is new, and you have not yet specified a name, a dialog box appears
asking for this information. You can also click the button on the Runtime
Gateway toolbar to save your model.
Select Save Model As... from the File menu to save the model with a new name.
The model is saved.

Saving a Component
Once you save a component in the Runtime Gateway, you can use it to create a model
in the Isight Design Gateway.
To save a component:
1. Right-click the component you want to save on the Workflow tab, Dataflow tab, or
on the Model Explorer on the left side of the Runtime Gateway.
2. Select Save As from the menu that appears; then, specify the name and location for
the component. The component is saved.
Note: Components are saved as model files (*.zmf), and, once reopened, are displayed
by themselves in the Design Gateway. For information on using a saved component to
create a model, refer to the Isight User’s Guide.
Understanding the Runtime Gateway Layout

The Runtime Gateway’s layout is shown in Figure 1-1 on page 29 (with areas labeled).

Figure 1-1. Basic Layout of the Runtime Gateway
In many respects, the Runtime Gateway very closely resembles the Design Gateway.
However, there are numerous differences. Some of the main areas on this interface
include:
Menu Bar. The Runtime Gateway’s menu options are described in “Menu
Options,” on page 292.
Toolbar. The Runtime Gateway has an abbreviated toolbar, as well as numerous
other features related to execution, including the Current Job drop-down list, Run
Counter, Stop, Pause, and ReRun buttons. For more information on using these
options, see “Using the Runtime Gateway Toolbar Execution Buttons,” on
page 38.
Current Job Drop-down List. This drop-down list allows you to easily switch
between jobs that have been executed during the current session or loaded from the
Jobs Database. For more information, see “Selecting Loaded Jobs,” on page 72.

Tabs. The Runtime Gateway has a different arrangement of tabs compared to the
Design Gateway. For more information on using the tabs, see “Overview of the
Available Tabs,” on page 39.
Component Title Bar. This feature shows the name of the currently selected
component, and also provides additional options based on the type of component
selected (including editing options and access to approximations).
Model Explorer. This area allows you to navigate between the components that
make up the model. The component selected in this area has its information
displayed in the tabs on the right side of the interface. Each component contains a
subfolder for the component’s parameters and file parameters, if any exist. If the
Parameters tab is being viewed, the parameter is highlighted on the Parameters tab
if it is selected on the Model Explorer. You can also select parameters to create
graphs in the Graphs Overview area. For more information, see “Understanding
the Graphs Overview Area,” on page 226. Hovering the mouse over the Model
name displays the number of components, parameters, and files in the model. You
can hover the mouse over the Parameters node to view the type of parameters in
the component. The number of parameters and files is shown next to the
Parameters and Files nodes.
Graphs Overview area. This area allows you to create and view graphs and tables
while viewing workflow, parameter information, or data analysis tools. Graphs and
tables created in this area are also added to the Graphs tab. For more information,
see “Understanding the Graphs Overview Area,” on page 226.
Log Button. This button opens the Log Viewer dialog box, which allows you to
view the Design Gateway log file. For more information, see “Accessing the Log
File,” on page 115.
Server Information Button. This button provides access to ACS connection
information if you are connected to an ACS in the Fiper environment. If you are
using Isight in Standalone mode, this button doesn’t provide any details. For more
information, refer to the Isight User’s Guide.

Controlling Execution
There are several ways to control the execution of a model. You can set certain options
immediately prior to execution, you can select which jobs will be executed, and you
can pause or stop execution after it has started.
Model execution is submitted as a job. A job in Isight is the highest unit level of work.
A job consists of a model, optionally some initial data or values, and job control
information, such as logging level. Jobs are identified by a unique ID (generated by the
system when the job is submitted) and a readable job name provided by the user or
generated by the Runtime Gateway. The readable job name does not have to be unique.
A job is created when a model and job control information is submitted to the ACS for
execution, or run locally in the Runtime Gateway. Jobs progress through a series of
states as they execute, until they reach the “Done” state. A job that is done is persisted,
or saved, by the ACS for later analysis. Jobs run locally in the Runtime Gateway may
or may not be saved depending on whether or not the local database is configured. For
more information on local database settings, see “Setting Additional Preferences,” on
page 51.
Note: Jobs are saved into and can be accessed from the ACS or standalone database.
For more information, see “Searching For a Job in the Database,” on page 58.
For more information on these execution controls, see any of the following topics:
“Executing a Model or Component from the Runtime Gateway,” on page 32. This
section describes how execution starts automatically or can be started manually
using the Runtime Gateway.
“Using the Configure and Run Options,” on page 32. These options allow you to
specify execution information, such as the job name and the logging level, before
execution begins.
“Creating a Name-Value File,” on page 37. This section describes the format used
when creating a Name-Value file, which can be used with the Configure and Run
options to specify initial parameter values.
“Using the Runtime Gateway Toolbar Execution Buttons,” on page 38. These
buttons allow you to pause or stop execution once it has started.

Executing a Model or Component from the Runtime Gateway

If you run a model directly from the Design Gateway, then execution is started
automatically when the Runtime Gateway is opened.
If you open the Runtime Gateway from the Design Gateway View menu, or if you
open the Runtime Gateway as a standalone interface, you need to manually start the
model execution once you have loaded the model you want to use. You may also want
to re-execute a model originally started in the Design Gateway after altering some of
the information provided in the Runtime Gateway. Model execution in the Runtime
Gateway is similar to model execution in the Design Gateway.
Execution is started using the Run button on the Runtime Gateway toolbar. You
can click the button to simply execute the model, or you can click the down-arrow
portion of the button to execute only the currently selected component or to configure
and run the model or component. For more information on using the configure and run
options, see “Controlling Execution,” on page 31.
You can also execute a component by right-clicking the component icon on the
Workflow or Dataflow tabs and selecting Run from the menu that appears. This runs
the currently selected component.
Using the Configure and Run Options

The configure and run options are accessed using the Run button. You can also access
these options using the Run button or Run menu on the Design Gateway. These options
allow you to specify information for the following settings, rather than using the
system defaults:
Job name. By default, the job name consists of the file name, the current date, and
the current time.
Logging level for the Isight execution log file.
Fixed seed use and initial value.
Database lookup mode.
Set initial values for parameters on the root component.

To use the configure and run options in the Runtime Gateway:
1. Perform one of the following actions:
Click the arrow next to the Run button on the Runtime Gateway toolbar;
then, select Configure and Run Model from the menu that appears.
Select Configure and Run Model from the Runtime Gateway Run menu.
Note: You can choose to configure and run either the entire model or the selected
component.
The Run Info dialog box appears.
2. Set any of the following options, as desired:
Create a custom name for the job using the Job Name text box. Naming the
job may make it easier for you to locate it later for post-processing or
re-execution.
Set the log level for the execution using the Logging Level button.

The following options are available:

• Debug. These messages are intended for debugging system or component
code. These messages are generally meaningful only to the program
developers. This level can produce a large quantity of messages which can
affect system performance. This is the lowest level. Using this setting will
send all five types of messages to your log file.
• Info. These messages contain routine status or other informational items
that are not generally significant.
• Warning. These messages indicate a condition of which you should be
aware, but does not generally indicate a failure.
• Error. These messages indicate an error condition that was caused by user,
operational data, or some other condition that can be corrected.
• SysError. These messages indicate a software system failure. It may
indicate that some part of the infrastructure has become unusable (for
example, a database has gone down), or it may indicate a programming
error. These errors should be reported to system administrators for analysis.
This is the highest level. Using this setting will send only SysError
messages to your log file.
Use a Fixed Seed. The seed can be fixed by clicking this check box and
specifying the seed manually in the corresponding text box. If this check box is
not activated, the seed is determined randomly. If you are using Database
Lookup and you want to verify that all runs were replaced by lookup runs in
the second execution of the job, then you must enter a fixed seed.
Note: You can set this option permanently for the model using the Model
Properties dialog. For more information, refer to the Isight User’s Guide. Once
the setting is made on the Model Properties dialog box, you will always see it
(as the default setting) on the Run Info dialog box.
Database Lookup Mode. Isight has the capability, prior to executing an
activity component, to examine all past executions (or only those within the
current job) of this component to find out if this component has been run with
this exact set of input values. If so, the assumption is that the output values will
be identical and can be restored. Isight can restore these values rather than
executing the activity component. For long-running components, such as
simulation codes, this can save valuable execution time, since the results are
already in the database. Also, for Fiper ACS, database lookup will bypass the
distribution of the component to the Fiper Station and reduce the execution in

the Fiper ACS workflow, saving the additional dispatch time in a Fiper ACS
environment.
Database lookup is disabled by default to maintain backward compatibility

with previous versions and for cases where database lookup is not feasible to
use (e.g., component is designed to produce an external effect, such as mail).
Database lookup can be set at the model level or the component level. For
information about database lookup at the component level, refer to the Isight
Component Guide.
Select one of the following options to set the database lookup for the current
model:
• Do not reuse prior runs (execute all components). All components will
be executed in the current model.
• Reuse prior runs only within current job. This setting limits the database
lookups to come from prior executions of the component that were run by
this job. This option limits the scope of the lookup, which reduces its
effectiveness, but it protects the lookup integrity from external changes,
such as the simcode.exe being replaced by a newer version.
• Reuse prior runs from all compatible jobs. This setting limits the
lookups to any derivative (i.e., saved or copied version) of the original
model XML that has the same model name. Changing the model name (on
the Model Properties editor, not the name of the externally saved XML file
on disk) indicates that some incompatibility exists between all prior data, or
that this model is being altered to perform some unrelated work.
Note: If an external change (e.g., update of a simcode.exe) has occurred, the
component’s options (Advanced button) provides a means to indicate the
change without changing the model (which invalidates all prior data for all
components, not just the selected component). For more information about
using the Advanced button, refer to the Isight Component Guide.
Isight handles file parameters similar to parameter values with respect to

database lookup. However, unlike normal parameters which must be saved to
the database for database lookup to function, disabling the Save to Database
option for file parameters simply causes them to be ignored.
If all files are used to hold static data that is not driven by the model, this data
is not needed for database lookup. Click the Ignore All File Parameters when

performing lookups option to ignore all files when performing database

lookups.
Note: If only one file parameter holds static data, disabling the Save to
Database option for the file parameter will cause it to be ignored by database
lookup.
If the model enables database lookup, all activity components in the model are
enabled for database lookup, unless otherwise disabled by the activity
components metamodel (e.g., Mail component). Similarly, if the model does
not allow database lookup, then all activity components in the model are
disabled for database lookup.
If the component’s metamodel does allow database lookup, then the

component properties editor will allow you to enable/disable lookup at the
component level. For more information, refer to the Isight Component Guide.
Note: You can set these options permanently for the model using the Model
Properties dialog. For more information, refer to the Isight User’s Guide. Once
these settings are made on the Model Properties dialog box, you will always
see them (as the default settings) on the Run Info dialog box.
View component information in the Component Info area. Use the list on the
left side of this area to switch between components. The component
information is displayed on the right side of this area.
Change the starting values for unmapped parameters or the configuration for
unmapped file parameters in the Unmapped Input and Local Parameters area
on the right side of the dialog box. New parameter values can be typed directly
in the Value column. File parameter configuration settings can be accessed by
clicking the button in the Value column, which opens the Configure File
Parameter dialog box. For more information on the settings displayed on this
dialog box, refer to the Isight User’s Guide.
(Standalone mode only) Use the Write results to database check box to turn
on/off storing run data to the database, if you are running Isight locally and the
database is configured. For more information, see “Setting Additional
Preferences,” on page 51.

(ACS connection only) Use the Set Job Permissions button to control access
to the job. For more information on setting these permission, see “Setting Job
Permissions,” on page 73.
Click the Configure From Name-Value File button to set the values of
parameters in the root component to an existing Name-Value file.
3. Click OK to execute. The Run Info dialog box is closed, and you are returned to
the Runtime Gateway.
Creating a Name-Value File

You can use a Name-Value file to specify the initial parameter values when using the
Configure and Run options (from both the Design Gateway and the Runtime Gateway)
or when controlling executing using the Command Line Client.
For more information on using the Design Gateway and the Command Line Client,
refer to the Isight User’s Guide.
The Name-Value file is a simple text file that contains a list of parameters and their
corresponding values. Its format should be similar to the following example:
# FIPER Name/Value file encoding=Cp1252
parameter1 = 1234
paramter2 = 5678
parameter3 = 9.0
array1 = 1.1 1.2 1.3
file_parameter1 =C:\files\isight\file_para.dat
Component1.Optimal Design.aggregate_value1 = 3423

The following items should be noted when creating and using a Name-Value file:
If you are unsure about how to create a Name-Value file for an existing model, or
you have trouble importing the values into your model, you can use the Export
button on the Runtime Gateway (or Design Gateway) Parameters tab to create a
file template which can then be altered as desired. This method can also be used to
check the format of your existing Name-Value file for any syntax errors.
Note: The command fipercmd model file:xxx.zmf will also produce a

template Name-Value file for configuring the given model.
You can omit the equals sign between the parameter name and its value when the
parameter name does not contain any of the following: equals sign, space, or
pound (#) sign.
Array elements can be initialized all at once (as shown above in the example file)
or individually using the following syntax:
array1[0] = 5.0
array1[2] = 3.1415
The behavior of File parameters is determined by how the Source for the input file
parameter is configured in the model. If the Source is “in model,” then the given
file is copied into memory and sent as part of job submission. If the source is
“File,” then the File parameter is re-configured to point to the given file, and that
path is passed unchanged when execution begins.
Using the Runtime Gateway Toolbar Execution Buttons

Once you execute a job using the Design Gateway, the Runtime Gateway automatically
appears, showing you the status of the execution. You can control a job’s execution
using the following buttons on the Runtime Gateway toolbar:
. Stops the current job. If you stop the run, the icon appears in the Runtime
Gateway toolbar. Components that were already submitted to the Fiper Station will
be executed. The also appears above components that were not executed.
. Pauses the current job. Work items that have already been dispatched will
execute, but additional work items will not be dispatched.
. Allows you to re-run a job that stopped or failed during a prior execution,
allowing you to restart the job and resume execution where it left off. This feature

is designed for use when a job was running correctly and was terminated for some
(known or unknown) reason, such as a power failure or something else unexpected.
It is not designed for use with jobs that fail due to configuration problems. For
more information, see “Re-running Failed Jobs,” on page 66.
After the initial execution, you can select a job to execute again using the Current Job
drop-down list. Simply select the desired job, then click the Run button. For
information on the other toolbar buttons and options, see “Toolbar Buttons and Other
Features,” on page 299.
Overview of the Available Tabs

This section provides a brief overview of the tabs available on the Runtime Gateway,
and each tab’s usage.
Using the Workflow Tab

The Workflow tab is the initial tab that appears during execution from the Design
Gateway. It shows a copy of the workflow as it appears on the Design Gateway. This
tab also displays the execution progress of each component in the workflow. A flag
appears above each component when it has been successfully executed.
This tab provides you with some options for the individual components. For more
information, see “Setting Workflow Options,” on page 82.
This tab also has the same zoom and pan features as the Design Gateway workflow tab.
For more information on using these options, refer to the Isight User’s Guide.
Using the Dataflow Tab

The Dataflow tab graphically displays how information moves from one component to
the another. By default, this tab is hidden on the Runtime Gateway. You can display it
by selecting Dataflow from the View menu. For more information, see “Viewing the
Dataflow,” on page 118.

Using the Parameters Tab

The Parameters tab allows you to evaluate the results of parameters in your model’s
components. It displays the input and output parameter values for the most recent
execution. You can select to view information from different runs using the View Run
button at the bottom of the tab. However, you can only view one set of values at a time.
For more information on using this tab, see “Viewing Parameter Information,” on
page 88.
Using the History Tab

The History tab shows parameter values from the execution of a model. It differs from
the Parameters tab in that it shows the values for numerous runs. The number of rows
displayed is based on the number of times the specified component was executed (one
row means a single execution, twenty rows means twenty executions). For more
information on using this tab, see “Using the History Tab,” on page 103.
Using the Data Analysis Tab

The Data Analysis tab gives you access to the following tools that can be used to
examine your execution data:
Engineering Data Mining (EDM)

Correlation Map
Two-dimensional Scatter Plots
For more information on using these tools, see “Using the Data Analysis Tools,” on
page 110.
Using the Visual Design Tab

The Visual Design tab allows you to create and use approximations directly from the
Runtime Gateway, instead of having to set up the approximations using the Design
Gateway. For more information, see Chapter 2 “Visual Design with Approximations”.

Using the Graphs Tab

The Graphs tab allows you to use graphs and tables to view execution data. For more
information, see Chapter 3 “Using Graphs, Tables, and Other Data Analysis Tools”.
Using the Summary Tab

The Summary tab displays a summary containing post-execution information. All
components display basic information, such as execution start time and duration.
However, some components, such as DOE, display more detailed information. For
more information, see “Viewing the Summary,” on page 111.
Using the Logs Tab

The Logs tab displays log information that may be helpful during execution, especially
if an error occurs. For more information, see “Using the Logs,” on page 113.
Viewing Tabs in Separate Windows

You can view any Runtime Gateway tab in a separate window, which allows you to
view information on multiple tabs at the same time. This feature is done by selecting
the tab you want to view; then, clicking the button. All options available on the tab
when it is part of the Runtime Gateway are also available when the tab is viewed in a
separate window.
Note: This option is also available for the Graphs tab by selecting Graphs Popout
from the View/Graphs menu.
Setting Preferences
The preferences allow you to set certain default behaviors in the Runtime Gateway and
for select components.
Note: The same preferences are also available from the Design Gateway. Any change
to the preferences accessed from either the Runtime Gateway or the Design Gateway

impacts the other interface. For more information on the Design Gateway, refer to the
Isight User’s Guide.
To access the interface that allows you to set Isight preferences:
1. Select Preferences from the Edit menu. The Isight Preferences dialog box
appears.
2. Proceed to one of the following topics for more information:
“Setting Gateway Preferences,” on page 43 describes the options that affect

the Gateway (Design and Runtime) including the working directory, parameter
settings, and execution options.
“Setting Additional Preferences,” on page 51 describes options such as default
Approximation technique, local database settings, and mail server information.
“Setting Component Preferences,” on page 55 describes available
component-based preferences.

Setting Gateway Preferences

The Gateway preferences allow you to specify preferences for numerous aspects of the
Isight Gateway (Design and Runtime) including the following:
General preferences
Logon preferences
Parameter options
Execution
Sounds
Additional preference options are also available. For more information, see “Setting
Additional Preferences,” on page 51 and “Setting Component Preferences,” on
page 55.
To set Gateway preferences:

1. Access the Isight Preferences dialog box as described in “Setting Preferences,” on
page 41.
2. Verify that Gateway is selected on the left side of the dialog box; then, set the
following options as desired:
Working Directory. You can specify your default directory, which will be the
default directory when you save or open a component. You can type the full
path directly into the corresponding text box, or you can navigate to the
directory using the Browse... button.
Load last open model on Start-up. When activated, Isight will automatically
take you to the last model you had open on the Design Gateway. If this option
is not selected, Isight, on start-up, will take you to the Design Gateway with
the default model loaded. The default model is an empty Task component. For
more information on using the Design Gateway, refer to the Isight User’s
Guide.
Automatically save a back-up copy of the model. When this option is

selected, in the event that Isight exits incorrectly (e.g., system crash), you will
be prompted to use the saved file. The back-up file is saved to the model’s
directory. If the model is new, the back-up file will be saved to the Isight
temporary directory. The back-up files are removed after Isight exits correctly.
Enter the time between backups (in minutes) in the Interval text box. If no

value is entered, then currently loaded models will not be saved. The default is
5 minutes.
Show dialog when components are added to the palette. When this option is
selected, a verification dialog box appears every time a component is added to
the Design Gateway from the Library. For more information, refer to the Isight
User’s Guide.
Default Browser. This option allows you to set the location for your system’s
default web browser. The browser is used for viewing Isight’s online help and
if you view a report in HTML or text format (as described on page 128). You
can type the full path to the browser directly into the corresponding text box,
or you can navigate to the directory using the Browse... button.
• (Linux only) You can use the Show warning if default browser is not set
check box to alert you if this option is not set when the online help is
accessed.
3. Click Logon on the left side of the dialog box; then, perform the following, if
desired. If only one connection file (.cpr) is found, Isight will not prompt for a
logon.
Do not prompt for logon in standalone mode. If this option is selected, then
Isight will not prompt for a user name and password if a standalone profile was
selected at the last login, regardless of the number of connection profiles found
in the Isight installation directory.
New Profile. Click the New Profile... button to create a new connection
profile for accessing a Fiper ACS. The Profile Editor dialog box appears. For
more information on creating a profile, see “Creating an ACS Connection
Profile,” on page 136.
Create a default model upon start-up. Click this check box if you want to
create a default model when starting the Isight Design Gateway; then,
determine the root component of the default models using the Select... button.
This setting does not directly impact the Runtime Gateway.

4. Click Parameters on the left side of the dialog box. The Parameters Preferences
dialog box appears. It is divided into three subtabs:
Click the Consistency subtab; then, set the following options, as desired:
• Auto copy child parameters to parent. When activated, any parameter

added to a child component (a component within a process component) is
automatically added to the parent component. For example, if a Calculator
component is added within a Monte Carlo component, and a parameter is
added to the Calculator component, the parameter is automatically added to
the Monte Carlo component as well.
• Auto map matching parameters. This option creates an automatic
mapping between two components that have the same name and
comparable properties. This automatic mapping only occurs if the
components are siblings (share the same parent component) or have a
parent-child relationship.
• Adjust parameter modes for invalid mappings. If this option is selected,
when you manually create a mapping from one parameter to another, if the
parameters have modes that are invalid for mapping, one of the parameters
is automatically adjusted to be an “in/out” parameter, making the mapping
valid. For example, if you map from an input parameter of one component
to another input parameter of a component within that workflow, it will
change the mode of the first parameter to be “in/out”. In doing so, the first
parameter’s value can be properly mapped to the second component.
• Type, Value, and Mode drop-down lists. When changes are made to a
parameter that is mapped to/from other parameters, Isight can
automatically adjust the corresponding attributes of the mapped parameters
to maintain consistency. For example, if you change a parameter's datatype
from Real to String, any mappings to/from other Real parameters would be
invalid until those parameters were also changed to Strings. You may also
want corresponding changes made when a value is changed or the mode is
changed. Preferences are available for whether you want Isight to always
automatically make the changes to mapped parameters, never automatically
make the changes (forcing a manual change), or to prompt you before
automatically making changes to allow you to abort the changes.
• Array Resizability. This drop-down list allows you to determine what
happens to the “Dimensions are resizable” option (available when creating
or editing an array parameter) when you map an array parameter to another
array parameter and the setting of this option doesn't match (i.e., one is a
fixed size and one is resizable). You can decide to always make the two

settings match, to never make them match (essentially leaving them

unchanged), or to prompt you to make a decision on a case-by-case basis.
• Array Dimensions. This drop-down list allows you to determine array
parameter behavior between two mapped array parameters when an array
size is altered. You can choose to have the array size always updated in the
other parameter, never updated, or you can be prompted to update the array
size on a case-by-case basis.
Click the Display subtab; then, set the following options, as desired:
• How many significant ... This option allows you to specify how many
significant digits you want to use for displaying real values in the user
interface. While Isight will always maintain the full precision of the values,
this full precision is often not very meaningful when interpreting results.
The presentation of the data in the interface can be greatly simplified by
reducing the number of significant digits to display. Examples are shown in
this window to illustrate how changing the setting of this preference affects
the way numbers will be displayed. When editing values, you will still be
presented with the number in full precision.
• Use default locale as the decimal separator. To support full
internationalization, Isight allows you to control how you want the decimal
to appear throughout the interface. Isight uses the decimal setting from the
locale in which the operating system is currently running by default.
However, if you are running in a locale that uses a “,” for the decimal, but
you still want the decimal to appear as a “.” (or vice-versa), you can
explicitly set the decimal separator to be used with this option. This setting
is useful for globalized organizations who run their computers on different
locales (in different countries), yet want everyone to use a consistent
decimal separator.
Note: In a further attempt to simplify the presentation of values, Isight also
changes values to be presented using scientific notation (e.g., 1.23E7
instead of 12300000) when the value is greater than 1E7 or less than 1E-4.

• Globally default to grouping parameters by their parent component.

This option groups parameters by component in some component editors.
You can turn this option on/off in the component editor by right-clicking in
the parameter table and deselecting Group Parameters from the menu. This
preference option only sets the initial default. Once a change is made in a
component editor, that setting supersedes this option and is saved as the
new preference. For more information, refer to the Isight Component
Guide.
• Do NOT group those parameters associated with the currently selected
component. This option allows you to only group parameters owned by
other components and not the component with which you are currently
working.
Click the Creation subtab; then, set the following options, as desired:
• Save general parameter values to the database at runtime. This option

allows you to specify whether or not values for new parameters are saved to
the results database. If the check box is not selected then, during and after
execution, parameters which are not saved will not be displayed in the
Parameters or History tabs in the Runtime Gateway. This option is set to
save parameter values to the database at runtime by default.
It is generally preferred that, for each run of any component, all parameter
values are saved to the job database. This allows you to inspect the runs at
any time, to confirm that the components ran correctly, or investigate when
they ran incorrectly. It also allows results to be reused in other jobs.
However, saving these values can consume large amounts of storage space,
so some parameter values could be left unsaved to limit this consumption to
a manageable level. This option reduces the amount of data saved in
memory if the database is disabled. More specifically, parameter values
may be left unsaved because of the following reasons:
• The parameters are used only within their component. This includes
unmapped (constant) inputs, unmapped outputs, and parameters defined
to be local (meaning they are not exposed to be mapped to/from other
components in the model).
• The parameters receive their values at runtime via data mappings (so
parameters in other components record those values).

• The parameters are in a child component, and only the overall execution
results presented by its parent component need to be saved.
• The parameters are in a calculation or other very fast component, so
that, when the job is rerun, their values can be recalculated without great
cost, so they need not be looked up in the database.
When a job is rerun, (using the rerun button on the Runtime Gateway)
Isight will, if possible, set the values of a component’s parameters for any
given run by looking up the values in a matching run of the original job. If
this is not possible, then the component will be rerun. Generally, this
lookup will not be possible if the component’s parameters are not saved.
Parameters not saved to the database affect database lookup in the
following ways:
• Unsaved input parameters always prevent lookup. A component’s
input/output relation is usually not unique unless all inputs are satisfied.
• Unsaved output parameters prevent lookup only if those parameters are
mapped to parameters in other components. Otherwise, the missing
values have no effect.
• Unsaved local parameters never prevent lookup.
• Save File parameters to the database at runtime. This option allows you
to specify whether or not new file parameters attached to components are
saved to the database. File parameters are often used for temporary work,
so it is often desirable to not store the information for these files in the
database. During and after execution, file parameters which are not saved
will not be displayed in the Parameters or History tabs of the Runtime
Gateway. This option is set to not save file parameters to the database at
runtime by default.
5. Click the Execution folder on the left side of the dialog box; then, set the
following options as desired:
Minimize the Design Gateway on job submission. When you execute your
model, the Design Gateway is minimized on your screen, leaving only the
Runtime Gateway visible.
Show dialog when model execution produces errors. When selected, Isight
will display a dialog box containing error information if an error occurs during
model execution.

Default Runtime Logging Level. This setting allows you to determine what
information is sent to your Isight log file. Components create different levels
of log messages. You can define the minimum log information setting
(Debug), and you will receive information on that particular level, and all other
levels above it.

• Debug. These messages are intended for debugging system or component
code. These messages are generally meaningful only to the program
developers, not to end users. This level can produce a large quantity of
messages which can affect system performance. This is the lowest level.
Using this setting will send all five types of messages to your log file.
• Info. These messages contain routine status or other informational items
that are not generally significant.
• Warning. These messages indicate a condition of which the end user
should be aware, but does not generally indicate a failure.
• Error. These messages indicate an error condition that was caused by the
end user, operational data, or some other condition that can be corrected.
• SysError. These messages indicate a software system failure. It may
indicate that some part of the infrastructure has become unusable (for
example, a database has gone down), or it may indicate a programming
error. These errors should be reported to system administrators for analysis.
This is the highest level. Using this setting will send only SysError
messages to your log file.
Local execution multitasking level. This setting controls the maximum
number of work items (component executions) that will be executed
simultaneously (i.e., in parallel) at a given level of a multi-level model when
running in desktop (Standalone) mode. This limit is provided and enforced so
that the local machine CPU is not overwhelmed by more work than it can
handle at any given time. If the local machine is a multi-processor machine, it
is very possible that you will want to increase this value to allow more work to
be done in parallel, resulting in the job being completed more quickly.
If model execution directory is specified, create a sub-directory for each

work item. When this option is selected, sub directories are created under the
model execution directory specified in Model Properties. The default is true.
For more information on setting the model execution directory, refer to the

Warn about local/file directory references when submitting models to an

ACS. When this option is selected, a warning message appears if you attempt
to execute a model that uses absolute paths on the ACS. This warning simply
informs you that the execution on the ACS may not work. You can use this
option to disable the warning message itself. It does not change the absolute
paths impact on the actual execution.
Warn when components are not eligible for database lookup. When this
option is selected, a warning message appears if you have disabled the Save to
DB option for one or more eligible parameters on the Design Gateway
Parameters tab. It only appears when you execute a model from the Design
Gateway. You can use this preference option to disable the warning message
itself. It does not change the actual parameter settings. This preference does
not impact the Runtime Gateway. For more information on this parameter
option, refer to the Isight User’s Guide.
For more information on using the database lookup feature in the Runtime
Gateway, see “Using the Configure and Run Options,” on page 32.
Enable advanced LSF DRM options. If you select this option, then a DRM
Settings tab will be available on the Component Properties dialog box. The
DRM Settings tab allows you to set the specific LSF requirements for an
individual component in the workflow when that component is dispatched
with the LSF DRM. For more information about component properties, refer
to the Isight Component Guide.
6. Expand the Execution folder on the left side of the dialog box; then, click the
Results Filtering option.
7. Set the largest number of parameters that will appear on the Runtime Gateway
History and Parameter tabs using the Max # of parameters text box. Be aware that
increasing this number may slow down system performance. You can also specify
whether or not file parameters will appear on these two tabs using the Show File
Parameter check box.
Note: You can add any parameters to those tabs at a later time using the Configure
button, which is located on both the History and Parameter tabs. For more
information, see “Viewing Parameter Information,” on page 88.
8. Enter the maximum number of runs per component you wish to view in the
Runtime Gateway using the Limit number of runs held in memory text box.
This is useful if you are working with a model that has a large data set. If the

number of runs exceeds this value, the oldest runs are discarded. The default is
100,000.
Note: You may change this value, but you will have to unload and reload the job or
close the Runtime Gateway for the change to take effect. Changing this preference
setting does not affect currently running jobs. For more information, see “Filtering
Large Data Sets,” on page 95.
9. Enter the number of runs you want to include in graphs in the Limit number of
runs in graphs text box. Using this option sets limits for graphs, the EDM, and 2D
scatter plots. If the number of runs available to display exceeds the limit specified,
the graph will begin uniform sampling of the data to stay within the limit. This
option is useful to improve performance when you are working with complex
models that have many runs. The default is 10,000.
Note: Each point in multiline/overlay graphs (e.g., EDM and history graphs with
overlay) counts against the limit. Therefore, data sampling begins much sooner
than with more simple graphs. For example, a history graph showing 10
parameters on one graph, when there are 100 runs requires the points in the graph
to be 1000 or higher to not begin data sampling.
10. Click Sounds on the left side of the dialog box; then, set the actions that you want
to play a sound.
11. Proceed to “Setting Additional Preferences” on this page or click OK to close the
dialog box.
Setting Additional Preferences

The other available preferences allow you to specify preferences for numerous items
within Isight including the following:
Approximations
Report Generation
Files and Directories
Mail Server
Local Results Database (MySQL)
Default Permissions

To set additional preferences:
1. Access the Isight Preferences dialog box as described in “Setting Preferences,” on

page 41.
2. Click Approximations; then, specify the default technique that will always be
selected when using the Approximation Wizard using the corresponding
drop-down list.
3. Specify the Warn when a component with approximations is changed option.

When activated (checked), if an approximation has been defined for a component,
a warning appears when that component’s editor is accessed and then closed using
the OK or Apply buttons. This warning states that changes to the component may
invalidate the existing approximation(s), and you are asked to confirm the change.
4. Click Report Generation on the left side of the dialog box; then, set the following
options, if desired. Isight has the ability to create a report as Microsoft Word, text,
or HTML files from any model that has been loaded. The report information is
taken from the current task summary, current execution results summary, and
several other locations.
Default Report Format. Determine if you want the report created as a MS
Word (Windows Only) file, a Text - markdown file, or an HTML file.
Allow automatic generation of report after model execution from
Gateway. Click the check box if you want to allow a report to be generated
after model execution. However, selecting this option does not automatically
generate a report. For more information, see “Creating a Report
Automatically,” on page 130.
Default Location. Enter the path, or use the Browse... button to search for the
location, where you want the report to be saved.
After manually generating the report. If a report is manually generated

(using the toolbar button), then you can determine the action taken after the
report is generated:
• Prompt to display the report. You will be prompted to display the report
once it is generated. The prompt dialog allows you to save the preference
(Yes or No).

• Always display the report. The report will be displayed after the run is
executed.
• Never display the report. The report is not displayed after the run is
executed.
This setting does not affect automatically generated reports.
For more information on creating reports, including how these preference options
affect automatically and manually created reports, see “Generating Reports,” on
page 128.
5. Click Files and Directories on the left side of the dialog box.
6. Set either of the following options, as desired:
Define files and directories relative to the model directory. This option
allows you to determine if you want file and directory locations that are part of
the model configuration to be defined relative to the directory that the model
resides in by default. This option is especially useful when you want to
develop a model in such a way that a single directory contains all resources for
that model and can be easily moved to another location and still work with few
or no changes required. Note that not all components or other features in the
software will necessarily use this preference when file/directory references are
defined, and that some manual reconfiguration of the model might still be
necessary when the model directory is moved to a new location.
Show File type encoding on the Files tab. This option allows you to display
the type of encoding used when reading/writing a file parameter. The
information appears on the Design Gateway Files tab. You specify the type of
coding when you create a file parameter. For more information, refer to the
7. Define the symbolic names and actual local directory names for the Design
Gateway using the bottom portion of the right side of the dialog box. The “Shared
File System” feature of Isight allows Isight to adjust how it references a shared file.
This adjustment is necessary due to the fact that Shared or Network file systems
are often named differently on different machines. Instead of using an absolute
path, which will be incorrect on some machines, this option allows the file to be
referenced as a path relative to a “Symbolic Root Directory”.
On each machine, the symbolic root directory is set to the location where that
machine mounts the shared file system. Each time the file is referenced by the

Design Gateway, the local symbolic root value is used to build the absolute path to
the file that is appropriate for that machine.
For more information on this option, refer to the Isight User’s Guide.
8. (UNIX/Linux only) Click the File Types tab. This tab allows you to specify the
default viewer for specified file extensions (e.g., odb, html). If no viewer is
specified, then when you attempt to view a file, you will be prompted to enter a
command. The command you enter will be saved as a preference for your default
viewer.
9. Click Mail Server on the left side of the dialog box; then, set the following options
as desired. These options are related to the Mail component and to the e-mail
button on the Isight error dialog box, which allows you to e-mail error information
to SIMULIA technical support. If you specify this information here, it will
automatically be added to any Mail component that you use (so you don’t have to
manually enter it each time you use the component).
The following options can be specified:
Email Server. The name of your e-mail server.
Email User Name. Your user name in your e-mail system.

Email Address. Your full e-mail address.
Note: For more information on these settings, contact your local systems
administrator.
10. (Standalone only) Click Local Results Database on the left side of the dialog box;
then, set your database preferences. These preferences allow you to set database
information for storing execution results. When this option is deactivated,
execution results are stored in the local file.

You can also determine this setting on a per execution basis using the Write
results to database check box on the Run Info dialog box. For more information,
see “Using the Configure and Run Options,” on page 32.
Verify that the Save results to local database check box is selected, if you
want to save your results information. You can start using Isight with the
database at this point - no other setting changes are necessary. However, if
you’d like to specify where your execution data is stored (other than the
default) continue to the next step. For more information on these settings,
including local database limitations, refer to the Isight Getting Started Guide.
(optional) Change the location where your data is stored. By default, this
location is in your home directory (in the Documents and Settings directory on
Windows) in a new directory called fiperdb-35. You can change this setting by
clearing (unchecking) the Use my home directory check box; then, specify
the new location in the Database location text box. You can type the directory
name directly into the text box or locate it using the Browse... button.
11. Click Default Permissions on the left side of the dialog box. The Default
Permissions options appear. These permissions are specifically for use with the
Fiper environment. For more information setting publishing options (the top
portion of the dialog box), refer to the Isight User’s Guide. For more information
on setting job permission options (the bottom portion of the dialog box), see
“Setting Job Permissions,” on page 73.
12. Proceed to “Setting Component Preferences” on this page or click OK to close the
dialog box.
Setting Component Preferences

Some components give you the ability to set custom default options for specific
settings. For information on setting these options, refer to the component chapter in the
Isight Component Guide.
Click Components; then, determine When a new version of a component or plugin

is published in the library for the components listed on the left side of the dialog box.
This option is used to determine when a new version of a component or plugin, which
has been added to the library, will be used by Isight. You can begin using the new
version the next time Isight is started (this setting is recommended) or the next time a
model is loaded or executed.

Working With Jobs

A job consists of a model, optionally some initial data or values, and job control
information, such as logging level. Model execution is submitted as a job. Jobs are
identified by a unique ID (generated by the system when the job is submitted) and a
readable job name provided by the user or generated by the Runtime Gateway.
Jobs can be automatically saved to a local database, if configured (or to an ACS

database if you are accessing the Fiper environment), and the job information,
including parameter values, can be reloaded at any time.
Proceed to one of the following topics for more information:
“Defining the Local Database” on this page

“Accessing the Job Database Dialog Box,” on page 57
“Searching For a Job in the Database,” on page 58
“Stopping Running Jobs,” on page 64
“Re-running Failed Jobs,” on page 66
“Creating Custom Job Names,” on page 69
“Importing and Exporting Jobs,” on page 69

“Selecting Loaded Jobs,” on page 72
“Removing Jobs From Memory,” on page 72
“Setting Job Permissions,” on page 73
“Deleting Jobs from the Database,” on page 77
“Understanding the Displayed Job Details,” on page 79
Defining the Local Database

If you are executing locally (without using a Fiper ACS), you should verify that your
local database settings are correct. Default settings are provided, but it is recommended
that you confirm that these settings are correct for your environment. For more

Working With Jobs 57
information on these database settings, see “Setting Additional Preferences,” on

page 51.
Accessing the Job Database Dialog Box

The Job Database dialog box provides access to all stored job information, and allows
you to perform the following tasks:
opening a job
stop a running job
re-execute a failed job
create custom job names
select a loaded job
import and export jobs
set job permissions when using a Fiper ACS
delete jobs from your database
To access the Job Database dialog box:
Select Open Results from Job Database... from the Runtime Gateway File
menu.
Click the button on the Runtime Gateway toolbar.
Select View Job Database from the Jobs menu.
Execute one of the following files, based on your operating system, to open the
dialog box in Standalone mode:
• Windows: jobmanager.exe (located in the

<Isight_install_directory>\bin\win32 directory)
• UNIX/Linux: jobmanager (located in the <Isight_install_directory>/bin
directory)
Note: If you are starting the Job Database on a 64-bit Linux system, the 64-bit
version of the interface is started by default. However, if you have installed
both the 32-bit and 64-bit versions, you can specify the version that will be
used by adding -32 or -64 to the end of the jobmanager command (be

sure to leave a space between the command and the option). Additionally, you
can set the default value for the jobmanager command using the
FIPER_BITS environment variable described in the Isight User’s Guide.
In Standalone mode, this interface has the same functionality as it does when
opened from the Runtime Gateway (or Design Gateway) as described above. It
allows you to check the current job’s status as well as view previously
executed jobs independent from Isight.
The Job Database dialog box appears.
2. Proceed to one of the following topics:
“Searching For a Job in the Database” on this page

“Opening a Job from a Database,” on page 62
“Understanding the Displayed Job Details,” on page 79
Searching For a Job in the Database

Before you can work with any job stored in your job database, you need to locate the
job. The Job Database dialog box provides several options for locating the correct job.

To search for a job in the database:
1. Access the Job Database dialog box as described in “Accessing the Job Database
Dialog Box,” on page 57. Your dialog box may differ slightly from the one below
depending on whether you have a local or Fiper ACS connection.
2. Enter the search criteria at the top of the dialog box.
Note: If you have previously performed a search using this dialog box, your old
search parameters and results are automatically loaded.
You can search for jobs using any of the following job information:
No search parameters. You can simply click the Search button, without
specifying any search criteria, to view a list of all of the jobs in the database.
Job Name. The job name is usually specified by the Runtime Gateway using
the model name and the date and time of the execution. However, you can
create custom job names. For more information, see “Creating Custom Job
Names,” on page 69.

(Fiper ACS connections only) User. The name of the user who submitted the
job. By default, the name of the current user is added to this text box.
Model Name. The model name is a text string specified using the Design
Gateway. For more information, refer to the Isight User’s Guide.
Job completion status. The state of the model when it’s execution was
finished. The available options include OK, Failed, Cancelled, and System
Failed. A “failed” model is a model that failed due to some problem with the
model itself. A “system failed” model is a model that failed due to software
system failure. It may indicate that some part of the infrastructure has become
unusable (for example, a database has gone down), or it may indicate a
programming error. These errors should be reported to system administrators
for analysis.
Jobs that started on or after a specific date or time frame and Jobs that
started on or before a specific date or time frame. You can specify a date
using any of the pre-define time periods (today, last week, etc.) by clicking the
corresponding drop-down list. You can also click the button to access a
small calendar, which allows you pick a specific day. Finally, you can use a
locally accepted date format. For more details, place your mouse cursor in the
corresponding text box and review the information that appears.
3. Click the Search button.

All jobs that match the specified search criteria are listed.
4. Verify that the job you want to work with appears in the list of returned jobs. You
can organize the listed jobs by Time or Model name using the corresponding radio
button in the View by area on the left side of the dialog box. When sorted by time,
the jobs are first listed by when they were executed and then by their
corresponding model. When sorted by model, the jobs are first sorted by their
corresponding model and then by when they were executed. When you select an
item in the organization list, the job list is automatically updated.
If you have more than one model with the same name, but created at different
times, each model will have its own entry in the list. Isight is able to determine that
the job is different based on the history of the model.
Note: You can use the Show All button to display all jobs that match your search
criteria.
For more information on the job information displayed on the dialog box, see
“Understanding the Displayed Job Details,” on page 79.

5. Proceed to one of the following topics, based on what you want to do with your
job:
“Opening a Job from a Database” on this page

Opening a Job from a Database

This option allows you to open jobs stored in a database (local or ACS). Selecting a job
from the database automatically opens the associated model in the Runtime Gateway,
so you don’t need to first load a model and then load a job. You can perform both
actions in a single step.
Important: If you want to view multiple jobs using the Runtime Gateway (by loading
the jobs from a database), you need to be aware that loading too many jobs
simultaneously may lead to memory problems on your system. It is recommended that
you not view more than a few jobs at the same time. If you continue to load more than
a few jobs in one Runtime Gateway session, you should use the Unload Jobs… option
(available from the Runtime Gateway Jobs menu) to unload the jobs you are no longer
viewing to reduce your system’s memory use. For more information on unloading jobs,
see “Removing Jobs From Memory,” on page 72.

To open a job and its model from a job database:
2. Locate the job you want to open in the Runtime Gateway. For more information on
searching for a job, see “Searching For a Job in the Database,” on page 58.
3. Determine which jobs will appear in the list using the View by option. You can
organize the listed jobs by Time or Model name using the corresponding radio
button in the View by area on the left side of the dialog box. When sorted by time,
the jobs are first listed by when they were executed and then by their
corresponding model. When sorted by model, the jobs are first sorted by their
corresponding model and then by when they were executed. When you select an
item in the organization list, the job list is automatically updated.
Note: You can use the Show All button to display all jobs that match your search
criteria.

4. Select the job you want to use. When you select a job, the job details appear in the
lower portion of the dialog box. For more information on the job information
displayed on the dialog box, see “Understanding the Displayed Job Details,” on
page 79.
5. Click the Load Job button. The job is loaded into the Runtime Gateway.
Stopping Running Jobs

Typically, running jobs are stopped by using the button on the Runtime Gateway
toolbar. However, you can also stop jobs using the Job Database dialog box. For more
information on the toolbar button, see “Using the Runtime Gateway Toolbar Execution
Buttons,” on page 38. Jobs that are currently running are designated by the icon in
the Status column.
Important: If you are executing on a Fiper ACS, you can only stop jobs if you have
the proper permissions.

To stop a running job using the Job Database dialog box:
2. Locate the job you want to stop. The job must have the icon in the Status
column. For more information on searching for a job, see “Searching For a Job in
the Database,” on page 58.
3. Click the job to select it; then, click the button on the right side of the Job
Database dialog box. You may also right-click the job after selecting it, then click
Stop Job from the menu that appears. The job is stopped, and the icon in the
Status column is replaced with the icon.
4. (optional) Click the button to remove the job from the database. For more
information, see “Deleting Jobs from the Database,” on page 77.

Re-running Failed Jobs

The Job Database dialog box provides you with a simple method for re-running jobs
that failed during execution. The following two points should be noted about this
feature:
It is designed for use when a job was running correctly and was terminated for
some (known or unknown) reason, such as a power failure or something else
unexpected. It is not designed for use with jobs that fail due to configuration
problems.
In order to work correctly, the Save to DB option (available on the Design

Gateway’s Parameters tab) must be enabled (checked) for the model’s activity
components. For more information on this option, refer to the Isight User’s Guide.
This feature (also known as “Job Rerun”) uses the database to replay all of the prior run
data up to the point where the previous job terminated; then, the job continues to
execute normally. It allows the job to resume execution as quickly as possible by
restoring the data from all of the prior runs in the database. It does not attempt to
re-execute failed runs, if the process component finished with a non-failure completion
code. Therefore, if the prior job ran for quite some time and then started failing many
components, re-running the job will also lead to failed runs for only those components
whose parent component finished successfully. Once a process component fails, all its
failed subcomponents will be re-executed (i.e., no database lookup will be performed).
Re-running this job will pick up execution where the failure began and continue
running the job.
Note: You can also re-run a failed job directly from the Runtime Gateway using the
button in the upper right corner of the interface.
For more information, proceed to one of the following topics:
“Re-running a Job,” on page 67

“Understanding Re-running Criteria,” on page 68

Re-running a Job
To re-run a failed job:
2. Locate the job you want to re-run. Failed jobs are labeled with the icon in the
Status column. For more information on searching for a job, see “Searching For a
Job in the Database,” on page 58.
3. Click the job to select it; then, click the Rerun Job button at the bottom of the Job
Database dialog box. The job is re-run in the Runtime Gateway.

Understanding Re-running Criteria

The following criteria must be met to use this feature to restore a given run:
The affected component must be an activity component. Process components

cannot use this feature.
The activity component must not be a referenced component (such as an InModel
reference, a Library reference of partner (B2B) reference, etc.).
The activity component metamodel (determined by the component developer)
must not disallow database lookup, such as the “Mail” component.
All mapped output parameters must be marked “Save to DB” on the Design
Gateway’s Parameter tab. That is, the option must be enabled (checked) for the
mapped output parameters. For more information, refer to the Isight User’s Guide.
During execution, the restored input values must exactly match the execution input
values. The reason for this requirement is that many Isight process components
(design drivers) depend upon random number generators for their search logic.
When using this re-execution feature, the random number generator seed for the
re-executed job is initialized to the seed value used by the original job. However, if
there are custom or third-party process components that do not honor the
reproducible random results requirement of Isight, then as soon as a discrepancy is
detected, normal execution begins. This problem should not occur with the
Engineous-supplied components.
If the completion code of the activity component is any failed state, this feature
will restore that state if (and only if) its parent process component also has a
non-failure completion code. If the parent process component failed, then the
activity component will execute rather than be restored. The reason for this
requirement is that, for many components, it is normal to have a certain number of
failed runs (for example, bad inputs). If the process component that ran this
activity component ran to successful completion, then Isight restores the failed
activity component’s output values rather than rerun them. This step is taken
because to rerun the values has the potential to alter the output statistics of the
process component, which could alter the dependent workflow behavior and cause
the job re-execution to cease restoring values and begin executing them. However,
if the process component running the activity component failed, it is likely that this
point in the model is where the external dependency caused the model to fail. Also,
every component after this failed component would have failed to run due to

workflow rules. In this case, the job re-execution begins executing these activity
components rather than restoring the failed results.
Creating Custom Job Names

By default, the job name consists of the model name, the current date, and the current
time. If you simply click the Run button when executing, this default job name is
used and saved to the database (local or Fiper ACS). However, you can specify a name
for each job immediately prior to execution. This action may make the task of finding
the job at a later time easier.
To specify a job name, simply follow the procedure described in “Using the Configure
and Run Options,” on page 32; then, type the job name in the Job Name text box.
Once you click OK, the job is executed in the Runtime Gateway, and the job name you
entered appears on the Current Job drop-down list.
Importing and Exporting Jobs

You can import or export jobs in order to use them in different databases (local and
Fiper ACS). For more information, refer to one of the following topics:
“Importing Jobs” on this page
“Exporting Jobs,” on page 70
Importing Jobs
You can import jobs from other Isight databases into your database. These imported
jobs can then be executed and manipulated the same as all other jobs.

To import a job:
2. Click the button. A dialog box appears allowing you to locate a job.
3. Locate the job you want to import; then, click Open. The job is loaded into your
jobs database and can be accessed using the Job Database dialog box. For more
information, see “Opening a Job from a Database,” on page 62.
Exporting Jobs
You can export jobs from your Isight database. These jobs can then be imported into
other Isight databases. You can also save the job currently loaded in the Runtime
Gateway to a file, which can then be used in a different Isight database. For more
information, see “Saving Results to a Results File,” on page 119.

To export a job:
2. Locate and select the job you want to export. For more information on searching
for a job, see “Searching For a Job in the Database,” on page 58.
3. Click the button; then, save the job in the desired location. The job can
now be imported into another database. For more information, see “Importing
Jobs,” on page 69.

Selecting Loaded Jobs

If you have executed multiple jobs for a single model in your current Isight session,
you can easily switch from job to job using the Current Job drop-down list at the top
of the Runtime Gateway interface. Simply click the drop-down list and select the job
you wish to view. The job’s information is then loaded into the Runtime Gateway. You
can also remove jobs from this drop-down list. For more information, see “Removing
Jobs From Memory” on this page.
For more information on opening jobs from the database, see “Searching For a Job in
the Database,” on page 58.
Removing Jobs From Memory

There may be occasions when you want to remove old jobs from your system’s
memory. If you are using a database (local or Fiper ACS), the job remains stored in the
database, it is simply not available from the Current Job drop-down list. You can
reload the job from the database at any time as described in “Searching For a Job in the
Database,” on page 58.
To unload jobs from the Runtime Gateway memory:

1. Select Unload Jobs... from the Runtime Gateway Jobs menu. The Unload Jobs
dialog box appears.

2. Select the jobs that you want to unload individually (to select specific jobs), or
click the Select All button to select every job in the list.
Note: You can select multiple jobs to unload by holding down the CTRL key on
your keyboard and clicking numerous jobs on the list.
3. Click the Unload button. You are returned to the Runtime Gateway. The jobs you
removed are no longer accessible from the Current Job drop-down list at the top of
Setting Job Permissions

If you are connected to an ACS in the Fiper environment, you can set access
permissions to the jobs that are stored in the ACS database. You can set default
permissions, which are applied to each run. You can also set permissions on a
job-by-job basis.
For more information, see one of the following topics:

“Setting Default Job Permissions” on this page
“Setting Permissions for a Specific Job,” on page 76
Setting Default Job Permissions

You can set default job permissions, which are used whenever a job is executed and
stored in a Fiper ACS database. This option helps eliminate the need to manually set
permissions for each job. The interface described in the following procedure can be
used to set default permission for both objects (models and components) and jobs. For
more information on published objects, refer to the Isight User’s Guide.
Note: You can set default options for most jobs, but then set different options for
specific jobs. For more information, see “Setting Permissions for a Specific Job,” on
page 76.

To set default job permissions:
1. Select Preferences from the Runtime Gateway Edit menu.
2. Click the Default Permissions option on the left side of the dialog box. The
permissions options appear.
The default permissions for jobs are specified using the bottom half of the right
side of the dialog box. Now you need to add users to the list and set their
permissions.
3. Click the Add button. A cursor appears in the Managed Name field.
4. Enter the user name or group name whose permissions you are setting in the
Managed Name column. You’ll specify whether the name represents a user or a
group in step 6.
5. Click the Permission field; then, select the type of permission from the drop-down
list that appears. The following options are available:
ALTER. The user or group has full access to the job, including the ability to
edit the job’s permissions. The user or group can view the details of the job,
load the job into the Runtime Gateway and watch it run, and view any results
generated by the job. The user or group may also pause, resume, and stop the
job while it is running, and may delete the job and all its results at any time.
MODIFY. The user or group has all of the accessibility granted with the
ALTER option, with the exception of editing the job’s permissions.

READ. The user or group can only view the job’s workflow and execute it. No
parameter access is allowed.
NONE. The user or group will have no access to the published job.
6. Click the Represents field; then, select if the name specified in the Managed
Name column represents an individual user or a predefined group. The following
options are available:
USER. This option allows you to specify a particular user name for the
permission you are defining. The user name should be specified in the
Managed Name column as described in step 4.
Fiper GROUP. This option allows you to specify a group of users to share the
permission you are defining, instead of creating a permission for each user.
The group name should be specified in the Managed Name column as
described in step 4.
7. Repeat step 3 through step 6 for any additional user permissions you want to
define.
8. Set job permissions for all other users (except for those explicitly defined) using
the All other users drop-down list. The options available are the same as those
described in step 5 above. You can also specify that there is no default option for
other users.
9. (optional) Arrange the listed users, as desired. You can use the Up or Down
buttons to move a user up or down in the list. The selected user’s settings move up
or down one line. The order of your list is important since a user name may appear
in one or more groups (the Fiper GROUP option) as well as by itself. Therefore, it
is possible for a user to be assigned more than one permission for the same job.
When this multiple permission issue occurs, Isight uses the permission closest to
the top of the list to determine the user’s actual permission for the job.
You can also use the Delete button to remove a user from the list.
10. Click OK to save your changes.

Setting Permissions for a Specific Job

You can set access permission for particular jobs stored in a Fiper ACS database using
the Job Database dialog box.
Note: If all of your job permissions will be the same for every job, you can set the job
permission defaults prior to execution. Using this method, all of your jobs will have the
correct permissions as soon as they are created. For more information, see “Setting
Default Job Permissions,” on page 73.
To set permissions for a job:

Access the Job Database dialog box (as described in “Accessing the Job
Database Dialog Box,” on page 57) and locate the job for which you want to
set permissions (as described in “Searching For a Job in the Database,” on
page 58); then, verify that the job is selected from the list; then, click the
button on the right side of the dialog box. You may also right-click the
job after selecting it, then click Edit Job ACL from the menu that appears.
Note: If you do not see this button (or Edit Job ACL), then you are not
connected to a Fiper ACS, and job permission options are not available.
Access the Run Info dialog box for a specific job; then, click the Set Job
Permissions button. For more information on accessing this dialog box, see
“Using the Configure and Run Options,” on page 32.
Note: If you do not see this button, then you are not connected to a Fiper ACS,
and job permission options are not available.
The Job Permissions dialog box appears.

This dialog box is a copy of the one accessed using the Preferences dialog box,
except that the options for setting permissions for published objects have been
removed.
2. Specify the permissions for the job. For more information on the options available,
see “Setting Default Job Permissions,” on page 73.
3. Click OK. Your permission settings are saved and you are returned to the Job
Database dialog box.
Deleting Jobs from the Database

You can delete jobs from the jobs database. This action differs from removing the jobs
from memory. Removing the job from the database permanently deletes the job. The
results can no longer be recovered and used in the Runtime Gateway. Caution should
be used when deleting jobs from the database.

To delete a job from the database:
2. Locate the job you want to delete. For more information on searching for a job, see
“Searching For a Job in the Database,” on page 58.

3. Click the job you want to remove; then, click the button. You may also
right-click the job after selecting it, then click Delete Job from the menu that
appears. A confirmation message appears. If the job you want to delete is running
(designated by the icon in the Status column, you first must click the
button to stop the job. For more information, see “Stopping Running Jobs,” on
page 64.
Note: You can select multiple jobs to delete by holding down the CTRL key on
your keyboard and clicking numerous jobs on the list.
4. Click Yes. The job is permanently deleted from the database.
Understanding the Displayed Job Details

Many different types of information can be displayed for jobs retrieved from your
database and displayed on the Jobs Database dialog box. This information is displayed
both in the job list in the middle of the interface and on the tabs near the bottom of the
interface. Proceed to one of the following topics for more information:
“Understanding Job List Columns” on this page
“Understanding the Tabs,” on page 80
Understanding Job List Columns

Several columns are displayed by default. You can change which columns are
displayed using the button.
The following columns are available:
Status. This column displays the execution status of the job using different icons.
User. This column displays the name of user who is executing, previously
executed the job, or imported the job.
Job Name. This column displays the name of the job. By default, the name is
created using the model name, the date executed, and the time executed. This
default naming scheme can be changed. For more information, see “Creating
Custom Job Names,” on page 69.

Model. This column displays the name of the model that corresponds to the job.
Started. This column displays the time that the job started.
Ended. This column displays the time that the job ended. The value is cleared
while the job is running, and may be cleared if the job was interrupted in an
unusual way such as if the Runtime Gateway was closed during execution or if the
Fiper ACS was shutdown while the job was running.
Duration. This column displays how long the job took to execute (clock time).
Job ID. This column displays the system-generated identification number of the
job.
Import Date. This column displays the date the job was imported into the
database.
Original User. This column displays the name of the user who originally executed
the job. This name may be different than the current user if the job was sent to you
by another user.
Original Job ID. This column displays the original system-generated
identification number of the job. This identification number will differ from the
Job ID number if the job was originally executed on another Fiper ACS or local
system (Standalone mode) and imported to another ACS or local system.
Import Cancelled. This column indicates if an imported job was cancelled before
it fully loaded.
Job Size. This column displays the size of the job. The value reflects the total size
stored in the database and the total amount in the file system used to store File
parameter contents.
Understanding the Tabs

Three tabs are available at the bottom of the Jobs Database dialog box: Job Overview,
Job Sizing, and Run Summary.
The Job Overview tab displays some of the same information as the columns in the job
list including the following details: the name of the job, the job ID (which is defined by
Isight), the model name, the model version, the name of the user that saved the job, the

random seed, and the job’s execution status. This tab is useful for viewing large strings
of information that are difficult to view in the jobs list.
The Job Sizing tab displays the start and end date of the job and the duration (length) of
the job.The Size in DB, Size on Disk, and Total Size fields are shown for the selected
model. For models currently running, click the button to query the
database for the current size of the model. You can view updated sizes by clicking the
button again. This button may not appear for jobs that complete quickly.
The Run Summary tab shows the model hierarchy (left side) and a small table (right
side). The hierarchy breaks down the jobs in a model based on the components in the
model and the model’s structure. It allows you to gain some insight into the structure
and size of the model that corresponds to the selected job without having to load it into
When you select a job on the left side of the tab, the table on the right side displays the
following information for the selected job:
Count. This field displays the number of workitems that finished with the
displayed combination of EvalType, Completion Code, and Status. This value
gives you the ability to see the ratio of database lookup runs, approximation runs,
and exact evaluations for any given component.
Eval Type. This field displays the evaluation type of the corresponding portion of
the model. The following values may be displayed:
Exact. The component was (will be) executed using exact analysis. No
approximations are used in the analysis.
Approximation Update. The evaluation was made for the purposes of updating
an approximation model. It is an exact analysis.
Database Rerun. The evaluation was made by lookup in the workflow database
(the analysis was not run). This type of lookup restores the values associated
with a prior workitem - both inputs and outputs.
Approximate. The evaluation was made using an approximation.

Database lookup. The evaluation was made by database lookup in the results
database. The analysis was not run. For more information on database lookup,
refer to the Isight User’s Guide.
Normal. Any subflows or components with active approximations are

evaluated using those approximations. This evaluation is the usual mode of
operation. This value is used only to indicate how an evaluation is to be done;
it will never be the result of an evaluation.
Completion Code. This field displays whether or not the corresponding portion of
the model completed successfully or failed for some reason (including cancelled
by the user, failed, or failed due to system failure).
Status. This field displays the execution status of the corresponding portion of the
model.
Setting Workflow Options

The Workflow tab provides you with a view of the model’s workflow, as well as an
indication of the execution status of each component. If a component is successfully
executed, an icon appears above it. Also, the number of runs the component executed
is shown.
The following additional features are available on this tab:
“Editing Process Components,” on page 83
“Changing Process Components in a Workflow,” on page 83
“Viewing/Hiding Annotations,” on page 85
“Saving the Workflow Image,” on page 85
“Using the Component Options,” on page 85

Setting Workflow Options 83
Editing Process Components

While models are primarily built using the Design Gateway, process components can
be modified in the Runtime Gateway. This allows you to establish a well-defined
“analysis” workflow to analyze a single design point, apply a design driver component
to find a design that solves a defined problem, and then easily reconfigure the process
component that drives that analysis to either (a) change the settings of the design
driver, or (b) alter the problem being solved. You can access the component editor
using one of the following methods:
Double-click the process component icon in the workflow or in the Model

Explorer on the left side of the interface.
Right-click the process component icon in the workflow or in the Model Explorer;
then, select Edit from the menu that appears.
Click the button near the top of the Workflow tab (adjacent to the component
name).
For information on editing the process components, refer to the Isight Component
Guide. The process components include the following:
DOE
Loop
Monte Carlo
Optimization
SDI
Six Sigma
Taguchi Robust Design
Task
Changing Process Components in a Workflow

Any process component in the workflow can be replaced with another process
component.
Note: You cannot change components that are referenced (either from the current
model or separate referenced models). For more information on these referencing
options, refer to the Isight User’s Guide.

To change a process component in a workflow:
1. Right-click the component that you want to change.
2. Highlight Change To in the menu that appears; then, click the New... option. The
Select New Component dialog box appears, listing the new component options.
Note: If you have already changed the component at least once, the menu that
appears will list the old component setting(s), if you told Isight to save these old
components (see step 4 below), and an option to edit the setting(s) list.
3. Select the component that will replace the existing component. Only process
components are listed.
4. Set the following options, as desired:

Copy existing parameters to new component. Select this option if you’d like
to carry over all parameters from the old component to the new component you
are about to create.
Delete existing component. Select this option if you want the existing
component permanently removed and replaced with this new component. If
you do not select this option, the existing component will be retained, and you
can change back to it at any time.
5. Click OK. You are returned to the Workflow tab, and the process component has
been changed.
You can repeat this step as many times as necessary, replacing components any number
of times. However, each time you replace a component, the old component selection
appears on the Change to menu (unless you selected to delete the old component in
step 4 above).

Setting Workflow Options 85
For example, if you change an Optimization component to a DOE component,

right-clicking on the new DOE component and selecting Change to would display the
following two options: New... and Optimization.
You can edit the list of old component settings by selecting the Edit List... option on
the Change to menu. The Edit Surrogates dialog box appears, allowing you to delete
components that you don’t want appearing on the Change To menu.
Viewing/Hiding Annotations
If any workflow annotations were added to the model in the Design Gateway, these
annotations will appear on the Runtime Gateway’s Workflow tab. You can choose to
show or hide these options using the button to the left of the workflow. For more
information on workflow annotations, refer to the Isight User’s Guide.
Saving the Workflow Image

You can save the workflow images as a *.jpg or *.jpeg file using the button to the
left of the workflow. Once saved, you can open the file in the image viewing software
of your choice, or use it in another application.
Using the Component Options

You can right-click a component icon to view the following options:
Edit. This option allows you to alter the settings of process components. For more
information, see “Editing Process Components,” on page 83.
Disable. This option allows you to “turn off” activity components so that they are
not used in the model workflow during execution. This option is not available for
process components. A component that has been disabled is “grayed out” on the
workflow tab. Any disabled cabinet can be reactivated using the Enable option.
Properties. This option displays the information about the component, such as
type, version, and description. This information is for viewing purposes only and
cannot be edited.

Run. This option executes the selected component. If you are connected to a Fiper
ACS, you can choose to execute the component using the ACS or to run it locally
using the Test Locally submenu.
Print This Component Tree... This option prints information about the
component.
Save As. This option allows you to save a model with the component as the root.
Publish. This option allows you to publish the component, which makes it
available to other uses who access your Library. For more information on
publishing components, refer to the Isight User’s Guide.
Approximations. This option allows you to view approximations that have been
defined for a component. For more information on using approximations, and how
to create them for a component, see Chapter 2 “Visual Design with
Approximations”.
Change To. This option allows you to change a process component to another
process component. For more information, see “Changing Process Components in
a Workflow,” on page 83.
Save Results To Disk... This option allows you to save all of the results generated
by the currently loaded job for the component to a specified directory. For more
information on this option, see “Saving Results,” on page 119.

Understanding Graph, Table, and Other Data Analysis Options 87
Understanding Graph, Table, and Other Data

Analysis Options
The Runtime Gateway provides access to graph and table options that allow you to
work with execution data. Graphs and tables are collectively known as visuals. It also
describes special visuals including Engineering Data Mining (EDM), the Correlation
Map tool, two-dimensional Scatter Plots, and the Taguchi Main Effects Viewer.
Graphs Overview area. The feature, available on the Workflow, Parameters,

History, and Data Analysis tabs, allows you to view execution data and graphs
side-by-side. For more information, see “Understanding the Graphs Overview
Area,” on page 226.
Graphs and Tables. You can create graphs and tables of execution data using the
Graphs tab. For more information, see Chapter 3 “Using Graphs, Tables, and Other
Data Analysis Tools”.
Engineering Data Mining. This tool allows you to view results information for
models that use the NSGA-II optimization technique. For more information, see
“Using the Engineering Data Mining Tool,” on page 267.
Using the Correlation Map. This tool is a post-processing aid that calculates the
rank and linear correlation values of every pair of parameters in a given model. For
more information, see “Using the Correlation Map,” on page 273.
Using Two-dimensional (2D) Scatter Plots. This tool allows you to view
Engineering Data Mining information as a group of scatter plots. For more
information, see “Using the Two-dimensional (2D) Scatter Plots,” on page 279.
Taguchi Main Effects Viewer. This tool allows you to visualize the execution
results of a Taguchi Robust Design component. For more information, see “Using
the Taguchi Main Effects Viewer,” on page 283.

Viewing Parameter Information

You can view parameter information prior to execution using the Runtime Gateway
Parameters tab. Following execution, you can view parameter information using the
Parameters tab and the History tab. Some components (most notably design driver
components) provide results in a special output parameter that can be viewed on the
Parameters tab. The Parameters tab is also used to modify Problem Formulation (e.g.,
bounds, objectives, etc.) to interactively see how it affects the “grading” of the current
set of results. For more information, see one of the following topics:
“Understanding the Parameters Tab” on this page

“Setting Viewed Parameters,” on page 90
“Viewing and Editing Problem Formulation Settings,” on page 91
“Filtering Data,” on page 92
“Filtering Large Data Sets,” on page 95
“Importing and Exporting Parameter Values,” on page 95
“Viewing Design Driver Results,” on page 99
“Using the History Tab,” on page 103
Understanding the Parameters Tab

The Parameters tab displays parameter values and other parameter information for the
selected component. Before a model has been executed, the initial/starting values for
the parameters are displayed. After a model has been executed (or during execution),
the parameter values for a particular run of the selected component are presented. Two
viewing options are available when using this tab:
Name/Value View. This view shows only the name, value, unit, and description of
the displayed parameters.
Problem Formulation View. This view shows all problem formulation information
associated with the parameters, including lower and upper bounds, target, weight,
and scale. For more information, see “Viewing and Editing Problem Formulation
Settings,” on page 91.

Viewing Parameter Information 89
You can quickly switch between these two views using the Show names/values only
button in the bottom right corner of the tab. In each view you can also select which
columns to show in the table by clicking the button in the upper right corner of the
table, allowing you to focus on only the information you care about. These selections
are stored as preferences so that the same columns are shown for future models.
In the following example, the Compute Stress Script component from the I-Beam
example is displayed using the Name/value View.
This Parameters tab is divided into two sections, with one section showing the Input
parameters and one showing the Output parameters. You can move between
components using the Model Explorer on the left side of the Runtime Gateway. In/Outs
appear in both tables, with the starting value in the input table and the ending value in
the output table.
You can also use this tab to alter input parameter values before execution (or to initiate
execution of a new job), and you can view values of different runs for the current job
using the View Run button at the bottom of the tab. If you are using the Problem
Formulation View, you can also edit problem formulation information associated with

the parameters. For more information, see “Viewing and Editing Problem Formulation
Settings,” on page 91.
Setting Viewed Parameters

You can control which parameters are displayed on the Parameters tab by clicking the
Configure button in the bottom right corner of the tab.
The Select Parameters for Viewing dialog box appears.
This dialog box displays a list of all parameters for the current component. Only those
parameters checked in the Selected column are displayed. You can clear any check
boxes for parameters you wish to be hidden. You can also click the Select All check
box to display all parameters (instead of selecting each one in the list). Parameters that
are not defined to be saved to the database will not be able to be selected for viewing.
You can use this dialog box to work with dynamic (resizable) arrays. For more
information, see “Using Dynamic Arrays,” on page 108.
Click OK to save your changes and return to the Runtime Gateway.
Note: If the component has less than a 1000 parameters, all the parameters will appear,
by default. You can change this value by editing Isight preferences. Be aware that

increasing the parameters shown could slow down performance. For more information
on editing preferences, see “Setting Gateway Preferences,” on page 43.
Note: This option is also available on the History tab. For more information on using
this tab, see “Using the History Tab,” on page 103.
Viewing and Editing Problem Formulation

Settings
The Problem Formulation feature allows you to define a problem to be solved for each
process component in a model, which by default will be inherited from the parent
process component (only for the parameters that exist at that level).
This feature allows you to define the following information for scalar parameters and
array elements:
Lower/upper bounds
Objective (minimize, maximize, target)
Scale and weight factors (for objectives and bounds separately)
Typically, the formulation is defined using the Design Gateway. However, you can also
define or modify problem formulation on the Runtime Gateway, as described later in
this section. For more information on using this feature in the Design Gateway, as well
as detailed information on how Isight uses the feature, refer to the Isight User’s Guide.
The problem formulation, once defined, can be used to grade the designs for any of the
components in that subflow. The Runtime Gateway uses this formulation to visually
indicate how the runs of any component measure up against the stated
objectives/constraints.
The Parameters tab has the option of showing problem formulation information for
displayed components using the Show problem formulation button in the bottom
right corner of the tab. You can change problem formulation settings on the Parameters
tab and then dynamically view the impact on the History tab. The History tab uses
color-coding to display problem formulation information. For more details, see
“Understanding Color Usage (Run Grading),” on page 105.
Note: When a value violates a constraint on a parameter, it is colored red on the

Parameters tab. This is the only color-coding used on this tab.

Filtering Data
You can use the Runtime Gateway Data Filter feature to filter the history of runs for the
selected component, reducing the amount of information displayed, which may allow
you to better analyze the execution data. Filtering can be based on the desired
minimum/maximum values you want included for any parameters and/or based on the
“grading” of the runs using the problem formulation (lower/upper bounds, objectives).
The filtered data set is what is displayed on the Parameters, History, Data Analysis, and
Graphs tabs.
Note: Some of the post-processing graphs from design driver component (for example,
the Main Effects graphs for DOE) still use the full, unfiltered data set even after
filtering.
To filter parameter information:
1. Access one of the following tabs on the Runtime Gateway:
Parameters
History
Data Analysis
Graphs
2. Verify that you are viewing the parameters for the desired component. If not, select
the correct component on the left side of the Runtime Gateway.

3. Click the Data Filter button at the bottom of the tab. The filtering options appear.
The Data Filter options are divided by input and output parameters. Parameter
information is displayed in Data Filters tables near the bottom of the interface.
4. Change the values in the Min and Max columns for any input or output parameter.
The initial minimum and maximum values are set from the range of the full data
set. The data set presented in the Runtime Gateway for the selected component is
dynamically altered after each change to the minimum and maximum values. The
number of data points currently presented is displayed at the top of the Data Filters
table.

5. Click the Options button; then, perform any of the following actions, as desired, to
further filter your data:
To control the filtering based on the minimum/maximum values of parameters

in the data set, use the following options
• Activate min/max filters. Select this option to filter your data set using
specific min/max values and then selectively turn off/on the filtering
without losing the defined min/max values.
• Show active min/max only. Select this option if you want the Data Filters
tables to only display parameters whose defined min/max values have
resulted in data points being filtered.
• Clear all min/max filters. Select this option to return all min/max values
to the minimum/maximum values from the full data set (essentially
removing all min/max filtering).
To control the filtering based on the grading of the runs using the problem
formulation, use the following options:
• Show feasible and infeasible. Select this option to show runs whether they
are feasible (meet all defined lower/upper bounds) or infeasible (violate at
least one lower/upper bound).
• Show feasible only. Select this option to show only those runs that do not
violate any lower/upper bounds on parameters as defined in the problem
formulation.
• Show infeasible only. Select this option to show only those runs that
violate at least one lower/upper bound on a parameter as defined in the
problem formulation.
Note: The three options listed above cannot be activated together. When
one is activated, the other two are deactivated.
• Show improvements only. Select this option to show only those runs that
are considered “improvements” over all previous runs with respect to any
defined objectives (and satisfaction of constraints) in the problem
formulation.
For more information on using problem formulation in the Runtime Gateway, see
“Viewing and Editing Problem Formulation Settings,” on page 91. For more
information on using problem formulation in the Design Gateway, refer to the Isight
User’s Guide.

Filtering Large Data Sets

If you are working with a model that has a large data set you can limit the number of
result data rows that Isight displays in the Runtime Gateway. For information about
this preference, see “Setting Preferences,” on page 41. If the number of runs exceeds
the value set for this preference, the oldest runs are discarded and a button appears
next to the Data Filters button near the bottom of the tab. You can click this button to
change the number of rows that is currently displayed. The Data Filtered dialog box
appears.
This dialog box indicates how many rows have been discarded. If you change the value
from this dialog box and the job is not running, Isight automatically unloads and
reloads the job.
If you change this value while the job is running, then once the data reaches the new
limit, Isight begins discarding the oldest rows. If the new limit is less than the number
of data rows already displayed, the limit will not take effect until the next job is started.
Importing and Exporting Parameter Values

Isight allows you to import the values of one or more parameters of a selected
component from an Isight name/value file. Conversely, parameter values can be
exported to a name/value file. This feature can be used while constructing a model or
prior to executing a model.
Parameter values can also be imported and exported on the Design Gateway. For more
information, refer to the Isight User’s Guide.

“Importing Parameter Values” on this page
“Exporting Parameter Values,” on page 97
Importing Parameter Values

This feature allows you to import parameter values from a specifically formatted text
file into the Runtime Gateway.
Important: The file selected for import must be formatted as an Isight name/value file.
An easy way to generate a name/value file is to first export parameter values (as
described in “Exporting Parameter Values,” on page 97) and then edit the generated
file. This step will guarantee that you are using the correct file format.
Only parameters whose names exactly match parameters listed in the name/value file
are imported. If a selected parameter’s name does not appear in the file, the parameter’s
value is left unchanged. Conversely, a name/value pair in the file is ignored if there is
no selected parameter of that name on the Runtime Gateway Parameters tab.
Note: Case-sensitivity is not considered when importing parameter values. For

example, the feature considers parameter1 and Parameter1 as being the same
parameter.
It is possible to use this feature to import individual array elements. To do so, the
name/value file must contain one line per element, with the name portion equal to the
array name followed by the element subscript.
Once you have created the name/value file (either manually or via the parameter export
option), you can use the file to import the parameter values into this same model or a
different model.
To import parameter values:
1. Verify that you are viewing the correct model for the import. Remember, parameter
names must match between the name/value file and the parameters on the
Parameters tab for the import to be successful.
2. Select the component that will receive the imported parameters from the Model
Explorer on the left side of the Runtime Gateway.

3. Perform one of the following actions, based on how many parameters will be
impacted by the import:
To import values to a specific set of parameters: Select the parameters on the

Parameters tab that will receive the imported values. The parameters are
highlighted once selected.
To import values to all matching parameters: Proceed to the next step.
impacted by the import:
To import values to a specific set of parameters: Click the button next to the
Import button; then, select the Into selected parameters option.
To import values to all matching parameters: Click the Import Values button.
You can also click the button next to the Import button; then, select the
Into all parameters option.
A dialog box appears, allowing you to identify the name/value file that contains the
parameter values you want to import.
5. Locate and open the name/value file. The parameter values are imported and
appear on the Parameters tab. Remember, only parameters whose names exactly
match parameters listed in the name/value file receive imported values. If a value
is not correctly imported, you should compare the parameter name on the
Parameters tab with the name in the name/value file to verify that they match.
Exporting Parameter Values

You can write the parameter values in a model to a name/value file. Once exported, you
can edit (if desired) and import the values either back into the same model or into a
different model (as described in “Importing Parameter Values,” on page 96).

To export values to a name/value file:
1. Select the component whose parameters you want to export from the Model
Explorer on the left side of the Runtime Gateway.
impacted by the export:
To export values for a specific set of parameter: Select the parameters on the
Parameters tab. The parameters are highlighted once selected.
You can export individual array elements. Simply expand the array in the
Parameters tab and select the elements that you want to export.
If you want to export a parameter group, you cannot click the group itself. You
must select each parameter within the group.
To export values for all listed parameters: Proceed to the next step.
impacted by the export:
To export a specific set of parameters: Click the button next to the Export
button; then, select the From selected parameters option.
To export all listed parameters: Click the Export button. You can also click the
button next to the Export button; then, select the From all parameters
option.
A dialog box appears, allowing you to create the name/value file that will contain
the parameter values you are exporting.
4. Navigate to a location and save the name/value file. This file can be opened in any
text editor to verify that the parameter values are present.
5. (optional) If you want to import the parameter values into another model, open that
model; then, proceed to “Importing Parameter Values,” on page 96.

Viewing Design Driver Results

The following sections explain the output aggregate parameter created by some of the
Isight design drivers.
Viewing Optimization Results

When an Optimization component is created and configured, it creates an output
aggregate parameter called “Optimization Results”. After execution, every
optimization component writes in this aggregate some basic results: values of
constraints at the optimum point (member called “Constraint Values at Optimum”),
values of all selected input and output parameters at the optimal design (member called
“Optimal Design”), and a short summary of the execution (member called “Execution
Summary”).
For some optimization techniques (e.g., NLPQL and LSGRG), another member of this
aggregate is created called “Technique Log”. In order to see this member, you must
activate the Save Technique Log option (if available) in the Optimization Technique
Options area of the Optimization component editor’s General tab. In this member, all
the log messages produced by those algorithms are saved for later examination.
Viewing DOE Results

The DOE component provides an output aggregate parameter called “DOE Results”
that is initially empty. After configuring the DOE component by selecting factors and
responses, this parameter is populated with various members to represent the relevant
post-processing results from executing the DOE. The following items are included in
the DOE Results parameter:
Statistics. For each factor and response selected, the minimum, maximum, range,
mean, and standard deviation are calculated.
Main Effects. If the option to “Perform regression analysis” was selected on the
Post-Processing tab of the DOE component editor, for each response selected the
main effect of each factor on that response is reported.
Best Point. If an objective was defined for any of the selected responses, the best
point (input and output values) of all points executed is reported.

Data Set. If the option to write the experiment data to a file parameter was selected
on the Post-Processing tab of the DOE component editor, this data can be accessed
by clicking the File button in the value cell for this parameter. You may save this
information to an external file, if desired.
Execution Summary file. This file contains a brief summary of the DOE setup
(technique type, the number of experiments) and execution results (a table
displaying the estimated relative effects that the various factors had on each
response).
Viewing Monte Carlo Results

When a Monte Carlo component is created and configured, it creates an output
aggregate parameter called “Monte Carlo Results”. After execution, every Monte
Carlo component writes some basic results to its results aggregate. The following items
are included in this aggregate:
Execution Summary file. A file parameter that contains a brief summary of the
Monte Carlo execution is provided in HTML format. This file contains Monte
Carlo setup information (sampling technique, number of samples, random variable
definitions) and response results.
Probability. For each response for which limits were defined, probability values are
included. Results potentially include probability above a lower limit, probability
below an upper limit, total probability between the upper and lower limits, and the
value of the response at a specified percentile.
Statistics. Basic statistics are included for each random variable and response,
including mean, standard deviation, minimum, and maximum.

Viewing SDI Results

When an SDI component is created and configured, it creates an output aggregate
parameter called “SDI Results”. After execution, every SDI component writes some
basic results to its results aggregate. The following items are included in this
aggregate:
Monte Carlo execution is provided in HTML format. This file contains Monte
Carlo setup information (sampling technique, number of samples, random variable
definitions) and response results.
Probability. For each response, for which limits were defined, probability values
are included. Results potentially include probability above a lower limit,
probability below an upper limit, total probability between the upper and lower
limits, and the value of the response at a specified percentile.
Statistics. Basic statistics are included for each random variable and response,
including mean, standard deviation, minimum, and maximum.
Design Point (Improve Design execution mode only). The final values of the
design variables and responses are included in this member. The Improve Design
mode is specified on the SDI component editor’s General tab.
Viewing Six Sigma Results

When a Six Sigma component is created and configured, it creates an output aggregate
parameter called “Six Sigma Results” - if you have selected items to include in this
aggregate results parameter. The contents of the Six Sigma Results aggregate
parameter are determined using the Six Sigma component editor’s Options tab (Six
Sigma Analysis run mode only). After execution, the Six Sigma component writes the
requested results to its results aggregate parameter. The following items can be
included in this aggregate:
Defects per million. For all selected responses, the number of defects per million
parts, based on the response distribution and limits, is reported.
Mean. For each random variable and response, the mean of the sample data is
reported.

Probability of failure. For all selected responses with limits defined, the probability
of violating those limits is reported.
Probability of Success. For all selected responses with limits defined, the
probability of satisfying those limits is reported.
Sigma Level. For all responses with limits defined, the sigma level (based on
response limits, response standard deviation, and probability of success) is
reported.
Standard Deviation. For each random variable and response, the standard deviation
of the sample data is reported.
Viewing Taguchi Robust Design Results

When a Taguchi RD component is created and configured, it creates an output
aggregate parameter called “Taguchi Results”. After execution, the Taguchi component
writes the basic post-processing results to its results aggregate parameter. The
following items may be included in this aggregate:
Static and Dynamic System
Taguchi execution is provided in HTML format. This file contains Taguchi
Robust Design setup information (number of control and noise factors, number
of signal levels, DOE techniques used, number of samples) and Taguchi
response metric results.
Static System (for each response):
SN Ratio. The Signal-to-noise ratio is reported for each control experiment.
Mean. The mean response value is reported for each control experiment.
Variance. The variance of all response values is reported for each control
experiment.
Loss. The value of Taguchi’s loss function is reported for each control
experiment.

Dynamic System (for each response):
SN Ratio. The dynamic signal-to-noise ratio is reported for each control

experiment.
Sensitivity. The sensitivity is reported for each control experiment.

Beta. The slope of the signal/response relationship line is reported for each
control experiment.
St. The total sum of squares is reported for each control experiment.
Sb. The variation caused by the linear effect is reported.
Se. The variation associated with error and nonlinearity is reported for each
control experiment.
Ve. The error variance is reported for each control experiment.
Using the History Tab

The History tab shows parameter values from the execution of a model. It differs from
the Parameters tab in that it shows the values for numerous runs. The number of rows
displayed is based on the number of times that the specified component was executed
(one row means a single execution, twenty rows means twenty executions).

In the following example, the Compute Stress Script component from the I-Beam
example is displayed.
Notice the each parameter has its own column, and each row denotes a run for the
component.
The following additional options/features are available on this tab:
Run Success Indicator. The first column indicates if the run was successful. If the
run is successful, a symbol appears in the column. If the run was not successful,
a symbol appears in the column. If an approximation was executed instead of
the actual component, a symbol appears in the column. If data was replaced by
data from your database using either the Database Lookup feature or the Job Rerun
feature, a symbol appears in the column beneath the icon indicating a
successful or unsuccessful run (the previous example shows a successful run). By
default, the Database Lookup feature is disabled. For information on how to
activate this feature, see “Using the Configure and Run Options,” on page 32.
The next columns (before the parameter values) show the run for each component.
The components are shown in relation to one another. The root is always run once.

If process components are nested, you will notice that the run numbers for
components in the subflow of the lower-level process components will cycle from
1 to N numerous times.
The rows of the table may be color-coded based on how problem formulation
“graded” the runs. For more information on this feature, see “Understanding Color
Usage (Run Grading)” on this page.
You can select a run in the history tab and use the parameter values to start a new
model execution. For more information, see “Initializing the Model from a Prior
Run,” on page 107.
If an array parameter has been defined as “resizable” it can be resized during

execution. For more information, see “Using Dynamic Arrays,” on page 108.
You can sort the data on the tab. For more information, see “Sorting the Data,” on
page 110.
You can filter the data on the tab so that only specified information is displayed.
For more details, see “Filtering the Data,” on page 110.
Determine which parameters are displayed using the Configure button. For more
information, see “Setting Viewed Parameters,” on page 90.
Click the button to copy the highlighted information so that you can paste it
into a separate file. You can also access this option by right-clicking the contents of
the tab.
Click the button to save the information to a file.
Click the button to print the information.

You can export the data on the tab to a text file or Microsoft Excel. For more
information, see “Exporting Graph Data,” on page 249.
Understanding Color Usage (Run Grading)

The Problem Formulation feature allows the Runtime Gateway to determine which run
was best at meeting the defined objectives as well as which runs were infeasible
(outside of the defined bounds). Problem formulation options for models are usually
initially specified using the Design Gateway. For more information on setting Design
Gateway problem formulation options, refer to the Isight User’s Guide.

You can use the problem formulation interactively using the Parameters tab in
conjunction with the History tab. If you change any problem formulation setting for a
parameter on the Parameters tab, the color-coding on the History tab is automatically
updated. For more information on using the problem formulation settings on the
Parameters tab, see “Viewing and Editing Problem Formulation Settings,” on page 91.
The following colors/shading styles are used with problem formulation on the History
tab:
Light red (darker red in any graphs) represents an infeasible design point. For any
infeasible run, the History tab will also use bold text to indicate the actual values
that do not satisfy the defined constraint(s) for any parameter, allowing you to
easily determine why the point is infeasible.
Green represents the best design point (based on calculated objective). This point
is always a feasible point (i.e., no violated constraints).
Yellow represents the best design point but a point that is infeasible. This color is
used when there is at least one objective defined and either there are no feasible
points found, or the best feasible point (colored green) has a worse calculated
objective and penalty. In short, this point might be a better design even though it is
slightly infeasible.
The parameter value(s) that cause the violation in infeasible runs are highlighted in
bold.
You can disable the color-coding of the rows on the History tab using the
button at the bottom of the tab. The formulation information is saved, so that you can
turn it back on at any time using the same button. Disabling the color-coding has no
impact on the performance of the Runtime Gateway.
Run grading is also used in the graphs created within the Runtime Gateway. For more
information, see “Understanding Run Grading in Graphs,” on page 245.

The following characteristics/limitations should be noted when using the Problem

Formulation feature in the Runtime Gateway:
When altering the problem formulation in the Runtime Gateway (to simply see the
effects on grading the runs), the corresponding process component’s internal
configuration is changed in the loaded model to remain in sync. If you execute this
model again in the Runtime Gateway, it uses this new configuration. The process
component is not impacted if you re-execute from the Design Gateway.
There is no option in the Runtime Gateway that allows you to reset to the original
formulation that the model was initially run with.
Although changing the formulation to see how it affects the grading of the runs is a
good way to interactively find design alternatives from among all of the runs from
the loaded job, it is not as effective as executing the model again with the new
formulation since the process components can use this information to intelligently
find better designs.
Initializing the Model from a Prior Run

You can select a run from the History tab and easily set the model’s parameter values
and re-execute the model based on the values of the selected run. This process is
known as initializing the model. The parameter values are updated for each component
in the model’s execution path.
To initialize the model from a prior run:
1. Click the run on the History tab whose parameter values you want to use. The run
is highlighted.
2. Right-click the run; then, select Init model from this run from the menu that
appears.
The Model Changed Choice dialog box appears, warning you that job results will
be cleared.
3. Click OK. The Save Changes dialog box appears.
4. Click Yes to save the changes to the model. If the model had not been previously
saved, a dialog box appears allowing you to save the model to your system.

5. Save the model with a new file name. This step is recommended since your model
has changed, but is not necessary. The Set Parameter Values? dialog box appears.
6. Click Yes if you want to set the parameter values to the values from the last run for
each component. The new model is automatically loaded into the Runtime
Gateway.
7. Execute the model.
Using Dynamic Arrays

If an array parameter has been defined as “resizable” it can be updated during
execution. Arrays are initially defined, and their resizing setting is determined, using
the Design Gateway. All arrays are resizable from the Design Gateway. However, you
must specify if an array can be resized during execution. For more information on
specifying array information, refer to the Isight User’s Guide.
Any array parameter that is defined as resizable is marked with an asterisk (*) to the
right of the parameter’s name on the Parameters tab. In the following example, two
parameters are resizable.

You can use the History tab to actually work with dynamic arrays. To access dynamic
array options:
1. Click the History tab; then, click the Configure button near the bottom of the tab.
The Select Parameters for Viewing dialog box appears.
By default, no root array parameters or individual elements are selected.
2. Perform any of the following options, as desired:
Select only the root array parameter. This option allows you to see all of the
elements of the array, no matter the size, during execution.
Select only individual elements. This option allows you to only see the
elements you specify. Be sure the clear (uncheck) the root array parameter.
Note: There are two parameter preference settings that can help you define default
array parameter behavior with regard to mappings between components. For more
information, see “Setting Gateway Preferences,” on page 43.
3. Click OK to save your changes and return to the History tab.
Note: The Data Exchanger, Excel, and Script are examples of components that may
resize arrays. For more information, refer to the Isight User’s Guide.

Sorting the Data

You can sort in ascending or descending order for any parameter by clicking on that
parameter’s column header. The first click sorts in Ascending order. The second click
sorts in Descending order. A third click returns you to the original non-sorted option.
You can also right-click a column header, and select Sort from the menu that appears
to access these options.
Note: You can also sort multiple columns of data at the same time. Simply press and
hold either the Shift or Ctrl key on your keyboard; then, click the column headers that
correspond to the information you want to sort. When performing a multi-column sort,
the primary sort is always based on the first column clicked.
Filtering the Data

If you are working with large data sets or merely want to focus on certain ranges of
values for parameters, you can use the Data Filters options to change the set of runs
displayed on the History tab. For more information, see “Filtering Data,” on page 92.
Using the Data Analysis Tools

The following three tools are available in the Runtime Gateway that allow you to
analyze your execution data:
EDM. The Engineering Data Mining (EDM) tool provides an effective way to
view many designs (inputs and corresponding outputs) and view the relationships
and trends among those designs. More specifically, the tool provides
post-processing functionality for multi-objective optimization by analyzing the
results and effectively visualizing Pareto solutions and sorting (screening) the data
interactively. For more information, see “Using the Engineering Data Mining
Tool,” on page 267.
Correlation Map. Given the large sets of data that Isight can work with, it can be
very time consuming to sort the relevance of particular parameters. The
Correlation Map is a post-processing aid that calculates the rank and linear
correlation values of every pair of parameters in a given model. The Correlation

Using Approximation Models 111
Map can provide a bird’s eye view of the parameters and their relations to one
another. For more information, see “Using the Correlation Map,” on page 273.
Two-dimensional (2D) Scatter Plots. You can select numerous combinations of

scatter plots to display your execution results. The scatter plots that are displayed
are based upon the parameters you selected on the EDM subtab (using the
Engineering Data Mining tool). For more information, see “Using the
Two-dimensional (2D) Scatter Plots,” on page 279.
Using Approximation Models

The Runtime Gateway provides access to approximations as a means to visualize the
design space and to perform simplified, quick design studies. In accordance with the
intended usage of approximations, their access tools are located on the Visual Design
tab of the Runtime Gateway. Whether the intended usage is design space visualization
or reducing the execution time of a design study, the mechanics of creating and
initializing an approximation are the same. Therefore, most of the interface tools for
working with approximations in the Runtime Gateway are the same or very similar to
those found in the Design Gateway. For more information, see Chapter 2 “Visual
Design with Approximations”.
Viewing the Summary

All components display basic summaries on the Summary tab. However, some
components show detailed summaries (such as DOE and Optimization).

The following example shows the summary of the Compute Stress Script in the I-Beam
model.

Using the Logs 113
The following example shows the summary of the DOE in the SpringSamples model.
Using the Logs

You can access two distinct log files using the Runtime Gateway.
Log Tab: This tab displays execution related information, based on your Log Filter
setting. For more information, see “Viewing the Log Tab,” on page 114.
Log Viewer. This dialog box displays information that is written to the
gateway.log file. This log file is the Design Gateway log file, and can also be
accessed that interface. For more information, see “Accessing the Log File,” on
page 115.
In some cases, information that appears in one log display will also appear in the other
log display. If you are connected to an ACS in the Fiper environment, errors may not

be displayed in either log file, if the log file being written to is on a different machine
(such as a system running a Fiper Station).
Viewing the Log Tab

The Log tab displays execution information. The amount of information stored that is
displayed on the Log tab is customizable.
The following example shows a sample Log tab. Notice that a large amount of
information is displayed, since the Debug option was selected from the Log Filter
button. For more information on using this button, see the section below the figure.

Using the Logs 115
The following information and options are available:
Show log for selected component only check button. This option allows you to
specify log information for a single component. Only information for the
component selected in the model explorer is displayed.
Log Filter drop-down list. This option allows you to specify the information
displayed in the messages area. The options available from the drop-down list
include: Debug, Info, Warning, Error, and SysError. When a job is run, a logging
level is defined. The default setting is Warning. After a job runs, it is not possible
to get logs for a level below that which the job specified. For more information on
using these filter settings, as well as the type of message each provides, see
“Setting Gateway Preferences,” on page 43.
Messages area. This area shows the full text of the selected row in the log table.
Job Details area. This area contains information about the job, including the
model name, job identification, status, and the model hierarchy. The information is
divided into three separate tabs. For more information on using this area, see
“Understanding the Tabs,” on page 80.
Note: If model execution fails, and you view the details using the Logs tab, a
Rerun Job button appears next to the Status icon. For more information on using
this option, see “Re-running Failed Jobs,” on page 66.
Accessing the Log File

The Design Gateway log file can be easily accessed by clicking the button
at the bottom of the Runtime Gateway (or the Design Gateway). If warning messages
have been written to the log file, the button changes to . If an error has
occurred, and information has been written to the log file, the button changes to
.

The Log Viewer dialog box appears when the button is clicked. The following example
shows a log file that contains information about an error that has occurred.
The actual log file (gateway.log) is stored in the location specified in the Log File
text box.
You can perform any of the following tasks using the log viewer:
Click the Reset button to set the Log Severity icon back to the OK state.
This action does not clear the log file. The error messages remain in the log file.
Copy the text (in order to paste it into another application) using the Copy button.
You can select any part of the text you like. If no text is selected, the entire contents
of the log file are automatically copied.
Click the Email Log button to send the information to SIMULIA technical
support.

Using the Logs 117
The Send Gateway Log dialog box appears.
If necessary, specify your e-mail address in the From text box. You can set Isight
to use a default From e-mail address whenever an e-mail function is used. For
more information, see “Setting Additional Preferences,” on page 51.
Also, add text or attachments, as desired. When contacting technical support

regarding a problem, please provide the following information in addition to the
log file, if possible:
Detailed explanation of the problem
Screen captures
Click the Send button. A SIMULIA representative will contact you about your
problem as soon as possible.

Viewing the Dataflow

You can view the dataflow from the Runtime Gateway. However, this option is
deactivated by default. To activate the Dataflow tab, select Dataflow from the View
menu. The corresponding check box is activated, and the Dataflow tab appears on the
Runtime Gateway and is automatically selected.
The same right-click options available from the Workflow tab can be accessed using
the Dataflow tab. For more information on these options, see “Setting Workflow

Saving Results 119
Saving Results
You can save the results generated by the currently loaded job (basically the
information on the Runtime Gateway History tab) to a results file or a text file,
depending on how you want to use the saved file. This section is divided into the
following topics:
“Saving Results to a Results File” on this page. This option allows you to save the
results generated by the currently loaded job to a file, which can then be used with
a different Isight database.
“Saving Results to a Text File,” on page 120. This option allows you to save the
results generated by the currently loaded job to a specified directory. Results saved
in this manner are only for use outside of Isight.
Saving Results to a Results File

You can save the job results currently loaded in the Runtime Gateway to a file, which
can then be used in a different Isight database.
You can also export multiple jobs from your Isight database. These jobs do not have to
be loaded into the Runtime Gateway. They can then be exported directly from your
database. For more information, see “Exporting Jobs,” on page 70.
To save the currently loaded job results to a file:
1. Verify that the correct job is currently loaded in the Runtime Gateway.
2. Select Save Results... from the File menu. A dialog box appears, allowing you to
save the results file to the desired location. Job results are saved as a *.zrf file.
Once the results are saved, the corresponding file can be opened in either the
Design Gateway or the Runtime Gateway. The file can also be imported directly
into an Isight database as described in “Importing Jobs,” on page 69.

Saving Results to a Text File

You can save all of the results generated by the currently loaded job (basically the
information on the Runtime Gateway History tab) to a specified directory. For each
component in the model, a file of runs (a row for each run) is generated, and if that
component contains file parameters a directory is created and populated with a version
of the file for each run.
Important: Results saved in this manner are only for use outside of Isight; they cannot
be read back into the Runtime Gateway for later review or post-processing. To save
results that can be read back into the Runtime Gateway at a later time, set the Local
Results Database setting in the Preferences dialog box. For more information, see
“Setting Preferences,” on page 41. Once results are saved to a database, you can reload
each job you execute and view the results. For more information, see “Searching For a
Job in the Database,” on page 58.
To save results to your local disk:
Click the button on the Runtime Gateway toolbar.

Select Save Results as Text... from the Runtime Gateway File menu.

Saving Results 121
The Select a Directory for the Result Files dialog box appears.
2. Navigate to the parent directory that contains the directory where you’d like the
results saved using the Save In drop-down list. All available directories, based on
your navigation, are displayed below the drop-down list. Do not navigate into the
directory that will store the information.
3. Click the directory to select it.

In the following example, the applications directory (under the models parent
directory) has been selected.
4. Click the Save file parameters check box if you want your file parameters saved.
If this option is not checked, only non-file parameters are saved.
5. Use the Parameters drop-down list to specify if All Parameters or Parameters
shown on History Tab will be saved.
6. Set the delimiter (how the parameter values will be separated in the saved files)
using the corresponding drop-down list. You can select tab or comma delimiters.
7. Click the Select Directory button. Your information is saved in a subdirectory in
the directory you specified. The name of the subdirectory is based on the current
job name. You are returned to the Runtime Gateway.

Importing Data From a File 123
Importing Data From a File

The Runtime Gateway allows you to import a data set from a text file or an Excel
spreadsheet. Once imported, you can use a subset of the Runtime Gateway’s features to
analyze and visualize the data including graphs, approximations, and Engineering Data
Mining (EDM). You can import any of the following file types: *.txt, *.csv, *.db
(including iSIGHT database files), *.xls, *.dat, and *.xlsx.
The data file being used must have the following characteristics:
Data must be in tabular form.

The rows must be oriented so that there is one line per data point with an unlimited
number of columns. The data does not need to start on the first row.
The columns must be delimited. You are given the option to specify the type of
delimiter used from a list or you can specify a custom delimiter.
Parameter names may be inferred from a row of column names preceding the
initial data row. If there is no such row, or it is not selected, default parameter
names are created.
Note: You do not have to import all of the data (columns) in your file. You can specify
only a preferred subset of columns, as described in the following procedure.
To import the data:

1. Select Import from Data File... from the Runtime Gateway File menu.
2. Navigate to the file you want to import; then, click Open.

3. (Excel spreadsheets only) Specify which sheet on the spreadsheet you want to
import; then, click OK. The Import Data From File wizard appears.
The file’s data is displayed on this dialog box. The dialog box attempts to
determine information about the data, including which row the data starts, which
row (if any) contains the column names, and the number of input columns in the
file (based on the first line in the file). However, you can alter these settings, as
well as others, to better specify the data that will be used.
4. Alter any of the following settings, as necessary, to specify which data points will
be imported:
Delimiter. Specify a pre-set delimiter character using the corresponding

drop-down list. If you want to use a delimiter that is not provided, select the
Other option; then, type the delimiter character in the text box below the
drop-down list. When the delimiter is changed, the data table shows the
resulting columns.
Note: If the Space delimiter is used, contiguous instances of a space count as a

single delimiter. For all other delimiters, contiguous instances count as distinct
delimiters.
Initial Data Row. Specify the row that contains the first line of parameter
data. The wizard attempts to determine this setting automatically. Once set,
this row appears in red.
Parameter Names Row. Specify the row that contains the column names.
This row, if specified, must precede the initial data row. The wizard attempts
to determine this setting automatically. Once set, this row appears in yellow.

This row may contain index expressions (in which case it is assumed that the
corresponding parameters are arrays) or periods (in which case it is assumed
that the corresponding parameters are aggregates. If column names are not
present in the data file, the inferred parameters are automatically named based
on their column position (for example, Column0, Column1, etc.).
Number of Inputs. Specify how many input columns will be extracted from
the file, not the number of input parameters. These two amounts are not the
same when arrays and aggregates are being imported. The wizard attempts to
determine this setting automatically, by halving the total number of columns.
During this process, the wizard assumes that all inputs precede all outputs.
Skip Bad Rows. Specify if you want the wizard to skip rows that contain bad
data during the import. Bad data can occur legitimately in imported data files
for several reasons. For example:
• The data file may contain harmless blank lines between or following the
data rows. More broadly, the data rows may be only a portion of a larger
body of general text.
• The data type of each column is determined from only the top 100 data
rows. Rows that follow the 100th row may invalidate this determination
(for example, a column of “real” values where the first 100 appear as
“integer” values).
• The delimiter may be chosen incorrectly, causing the data rows to not all
split into the same number of columns.
5. Click Next. The Configure the Parameters screen appears.

The input and output parameters extracted from the data file are listed. By default,
all of the parameters are selected for importing (a check mark appears in the
Import column).
Note: Sometimes the splitting of the column names row yields column headers
which cannot be used as parameter names, or which appear over more than one
column. When this situation occurs, column-position names are used instead, and
the affected parameters are (initially) not selected for importing.
6. Perform any of the following steps, as desired:
Customize the displayed parameter information using the following buttons

(this feature is for editing convenience only; it does not affect the import):
• . This button removes any filtering that has been done to the table, and
returns it to its original state.
• . This button allows you to apply filtering to the table. When clicked, the
Table Filters dialog box appears, which allows you to filter based on a
parameter’s name, mode, or type.
• . This button allows you to display or hide certain columns. The Name
column is always displayed.
Alter which parameters will be imported by checking or clearing (unchecking)
the check boxes in the Import column.
Change the name, mode, or type setting of any parameter using the
corresponding columns.

7. Click Finish. The data is imported into the Runtime Gateway.
Notice that the Runtime Gateway interface has been slightly altered. The Model
Explorer is no longer visible (on the left side of the interface), only a subset of the
normally displayed tabs are available, and several options (including the Run
button) have been removed from the toolbar. Since you are viewing raw data
instead of an Isight model, all model-related options have been hidden.
8. Analyze and visualize the data using any of the following options:
View parameter values on a per-row basis using the Parameters tab. For more
information, see “Viewing Parameter Information,” on page 88.
View parameter information for multiple rows using the History tab. For more
information, see “Using the History Tab,” on page 103.
Use the Engineering Data Mining Tool on the Data Analysis tab to view many
designs (inputs and corresponding outputs) and view the relationships and

trends among those designs. For more information, see “Using the Engineering
Data Mining Tool,” on page 267.
Use the Correlation Map on the Data Analysis tab to see a bird’s eye view of
the parameters and their relations to one another. For more information, see
“Using the Correlation Map,” on page 273.
Use the 2D Scatter Plots on the Data Analysis tab to view your results via
two-dimensional scatter plots, which are based on your Engineering Data
Mining (EDM) settings. For more information, see “Using the
Two-dimensional (2D) Scatter Plots,” on page 279.
Use the Visual Design tab to create approximations based on your imported
data. For more information, see Chapter 2 “Visual Design with
Approximations”.
Use the Graphs tab to create graphs and tables of the imported data. For more
information, see “Using Graphs,” on page 227 and “Using Tables,” on
page 251.
Note: You can also create graphs using the Graphs Overview area. For more
information, see “Understanding the Graphs Overview Area,” on page 226.
9. Repeat the above steps to import multiple data files. You can switch between files
by selecting the file from the Jobs menu. The data file will be given an
example_ext name (where example is the name of the file and ext is the extension).
Generating Reports
You can generate a report that contains information about the currently loaded model.
The type of data presented in the report depends on the task that was executed. For
example, an optimization report produces parameter history plots, whereas a Design of
Experiments report produces Pareto plots.

Generating Reports 129
However, the following sections are typical of most reports:
Title page
Process Component Details
Description
Parameters
Problem Formulation
Summary (Job Only)
Graphs (Job Only)
Important: In order to generate a Word report, you must have Microsoft .NET
Framework Version 2.0 or greater installed on your system. You can verify that you
have this feature installed by clicking Start / Control Panel / Add or Remove
Programs; then, verify that Microsoft .NET Framework Version 2.0 appears in the
list of currently installed programs. If you do not have this feature installed, you should
visit Microsoft’s website (www.microsoft.com/downloads) and download it. The
download is free.
For Microsoft Word generated reports, all plots are Excel objects. You can
double-click any plot to edit it or access the data in Excel (Excel 2000 or higher is
required). If Excel is not installed, the graphs are included as images. For HTML and
Text generated reports, an image is produced in addition to a text file of the data.
Note: You can only generate Word-based reports if the system running Isight has
Word installed. If you select this option on a non-compatible system (one that doesn’t
have Word installed or is a UNIX/Linux system), an HTML report is created by
default.

“Creating a Report Automatically,” on page 130
“Creating a Report Manually,” on page 130

Creating a Report Automatically

You can set up Isight to automatically generate a report following execution. This
process involves the following steps:
1. Activate the Generate report after execution from Gateway option on the
Model Properties dialog box. This step must be performed from the Design
Gateway. For more information, refer to the Isight User’s Guide. Be sure to save
the model once you activate this option. This option “turns on” the feature, but you
still have to allow it to occur after execution.
If you do not have access to the model via the Design Gateway, you can still
generate a report as described in “Creating a Report Manually,” on page 130.
2. Open the Runtime Gateway; then, activate the Allow automatic generation of
report after model execution Gateway preference option. For more information,
see “Setting Additional Preferences,” on page 51. This option allows the report
generation to occur.
3. Verify that the other Report Generation preferences are correctly defined,
including the location where the report will be saved as well as the default file type
(Word, text, or HTML).
4. Execute the model. Your report is automatically generated in the format and saved
in the location specified in the Runtime Gateway preferences.
Creating a Report Manually

If you have not set up automatic report generation for a model, or simply want to
manually create a report, you can do so directly from the Runtime Gateway.
Note: You can also create reports manually using the Design Gateway. These reports
are identical to those generated from the Runtime Gateway except that no results or
graphs are included. For more information, refer to the Isight User’s Guide.

Generating Reports 131
To generate a report manually:
1. Verify that the correct model is loaded into the Runtime Gateway.
2. Click the button on the Runtime Gateway toolbar. The Generate Report screen
appears.
3. Navigate to the location where you want the report saved.
4. Specify the format of the report using the Files of type drop-down list. You can
create a text file, an HTML file, or a Microsoft Word file (if Word is installed on
the system that is running Isight).
Note: You can also define default settings for the location and file type using the
Runtime Gateway preferences. For more information, see “Setting Additional
5. Type a name in the File name text box. For text and HTML files, this name
represents the directory that will contain the report and image files. For Word files,
this name represents the name of the Word file itself.
6. Click Save. Depending on your report preference settings, the Display Report
dialog box may appear, asking if you want to automatically open the report after
saving it. You can bypass this dialog box using the After manually generating
the report option in the Runtime Gateway preferences. For more information, see
“Setting Additional Preferences,” on page 51.
7. Click Yes to display the report or No to simply save the report for later viewing.

Note: The Save preference, and do not prompt again check box refers to the
ability to set a default post-generation option and bypass the Display Report dialog
box described in step 6 above.
UNIX/Linux: If you have not previously defined an external viewer to view the
type of file you created, you will be prompted to enter a command identifying the
viewer. For more information about setting the viewer, see “Setting Preferences,”
on page 41.
Your report is created. If you model contains any graphs, you may see some
Exporting Graphs dialog boxes appear. This behavior is normal. A maximum of
five graphs are created, and the graph type is determined by the kind of process
components as follows:
DOE - Pareto plots for response variables
SDI and Monte Carlo - probability graphs for response variables

Optimization - history graphs for objective variables
Six Sigma - no graphs are created
Loop - history graph for the condition parameter
Searching for a Component, Parameter, or

File in a Model
There are times when you may be working with a large and complex model and you
want to find a specific component, parameter, or file. Rather than manually looking
through the model for the item, you can use the Find or Advanced Find option. While
both search options will help you find the item, the Advanced Find option allows you
to limit your search by defining additional criteria such as parameters that are mapped
or saved to the database.

Searching for a Component, Parameter, or File in a Model 133
To use the Basic Find feature:
1. Select Find from the Edit menu. A Find text box and search icons appear on the
right side of the Design Gateway toolbar as shown below.
2. Enter the text for which you want to search in the Find text box; then, click the
. The first occurrence of your search item that is found will be highlighted in
the model explorer and the appropriate tab (i.e., Workflow, Parameter, or File tabs)
will display in the workflow area with the item selected. Use the or to move
to the next occurrence of the item.
You can modify the search criteria by clicking the button. Select Match Case to
match the capitalization of your search text. You can use the Match Whole Word
option to ensure that the search returns items that have the entire search text

included in their name. You may also use the “*” as a wildcard. For example, if
you enter “param*5”, then “param” and “parameter55” will appear as matches.
Select whether you want to search only for components, parameters, or files. All
are selected by default.
3. Click the button to close the Search option.
Using the Advanced Find Option

1. Select Advanced Find from the Edit menu. If this is the first time you have
opened the Advanced Find dialog box, the Components tab appears as shown
below.
2. Select the tab that corresponds to the item for which you want to search.
All components, parameters, and files are searched by default. You can change the
default search by accessing each tab and de-selecting Include Components, Include
Parameters, or Include Files.
3. Broaden or narrow your search results by selecting Match any or Match all from
the drop-down list. Match any will broaden your search because the results will
show all items that match at least one of the items you select. Match all will

Searching for a Component, Parameter, or File in a Model 135
narrow your search because the results will show only items that match all your
selected criteria.
4. Set the following additional criteria depending on the tab selected:
Components
• Term should match. Determine if the text you enter should match the
Component’s Name and/or Runtime directory path.
Parameters
Parameter’s Name and/or Value.
• Save to DB. Determine if the parameters searched should be set to Save to
the Database. For more information on the Save to DB option, refer to the
Isight User’s Guide. Determine if you want to search through mapped
parameters by selecting Yes or No from the Is Mapped drop-down list.
Files
File’s Name and/or Value (Unresolved Path).
• Save to DB. Determine if the files searched should be set to Save to the
Database. For more information on the Save to DB option, refer to the
• Is mapped. Determine if the files searched are mapped.
• Pass parallel safe test. Determine if the file name changes for every run.
Therefore, no files will be overwritten by files from another run.
5. Enter the text in the Term text box. You may also use the “*” as a wildcard. For
example, if you enter “param*5”, then “param” and “parameter55” will appear as
matches.
6. (optional) Select Match Case to match the capitalization of your search text. You
can use the Match Whole Word option to ensure that the search returns items that
have the entire search text included in their name.
7. Click the button. The search results appear in the list area. If components,
parameters, and files were all searched, then the results are sorted first by type,
then by name. All selections in the list are shown in the Design Gateway.

Creating an ACS Connection Profile

You need to create a connection profile if you are connecting to an ACS in the Fiper
environment. If you are running Isight in the Standalone (Desktop) environment, this
connection profile is included in your installation and does not need to be created.
To create the connection profile file:
1. Access the Profile Editor using one of the following methods:
Execute the editcpr command from a command prompt/terminal window.

This file is located in one of the following directories, based on your operating
system:
• Windows: <Isight_install_directory>\bin\win32
• UNIX/Linux: <Isight_install_directory>/bin
If you have already started Isight and are currently viewing the Logon dialog
box, you can click the button to create a new profile. This dialog box does
not appear unless you have specified at least one ACS connection profile.
Click the New Profile... button, which is available from the Preferences dialog
box under the Logon option. For more information, see “Setting Gateway
Note: If you are using the Windows operating system and have installed a Fiper
Station on the system that is executing Isight, you can click the Start button; then,
point to All Programs / Fiper 3.5 and click the Edit Logon Profile option.
The Profile Editor appears.

Creating an ACS Connection Profile 137
2. Type the name of the profile in the Profile name text box. This name will appear
on the Connection profile drop-down list when connecting to the Fiper ACS.
3. Select the type of application server you are using from the Server type
drop-down list. Additional options appear when one of these two options is
selected.
4. Specify the name of the machine running the ACS in the Server name text box.
Important: If you will be using LSF with Isight, do not specify the server using its
fully qualified domain name. For example, you should type acsmachine, not
acsmachine.yourcompany.com.
5. (optional) Change the port number in the corresponding text box. The port number
provided is the default port number for the application server selected. However,
based on your network or system configuration, you may need to change this
number. Contact your local system administrator for more information.
6. (optional) Check the Prompt for extended grid credentials check box, if desired.
The Prompt for extended grid credentials option is used in Fiper systems with
multiple security domains (e.g., the ACS server and the Fiper Stations use different
security infrastructures). Extended credentials are not requested at logon time and
all parts of the Fiper environment are assumed to exist in the same security domain
by default. If this is not the case, enable this check box and you will be prompted
for credentials for all systems at logon time. Check with your Fiper system
administrator to determine if you should enable this option. For more information,
refer to the Fiper Installation and Configuration Guide that matches your ACS
combination.

7. Select Save As... from the File menu; then, name and save the connection profile.
Connection profiles can be stored in either the top level of the Isight installation
directory or in the user’s home directory. When stored in either of these two
locations, the connection profiles appear in the Connection profile drop-down list
on the Logon dialog box.
8. Close the Profile Editor dialog box.

139
2 Visual Design with

Approximations
This chapter discusses using the Runtime Gateway approximations options, which are
similar to the approximations options available using the Design Gateway. The chapter
is divided into the following topics:
“Overview,” on page 140
“Accessing Approximations of a Component,” on page 141

“Creating an Approximation Using System-Determined Default Settings,” on
page 142
“Creating an Approximation Using the Approximation Wizard,” on page 145
“Editing an Existing Approximation,” on page 175
“Using Approximations at Runtime,” on page 177

“Initializing an Approximation,” on page 179
“Visualizing an Approximation,” on page 182
“Searching the Design Using Specified Criteria,” on page 203
“Setting Component Input Values from the Visual Design Tab,” on page 209
“Comparing Actual and Approximation Outputs,” on page 209
“Analyzing Approximation Errors,” on page 211

140 Chapter 2 Visual Design with Approximations
“Saving an Approximation,” on page 220
“Deleting an Approximation,” on page 221
Overview
The Runtime Gateway provides access to approximations as a means to visualize the
design space and to perform simplified, quick design studies. In accordance with the
intended usage of approximations, their access tools are located on the Visual Design
tab of the Runtime Gateway. Whether the intended usage is design space visualization
or reducing the execution time of a design study, the mechanics of creating and
initializing an approximation are the same. Therefore, most of the interface tools for
working with approximations in the Runtime Gateway are the same or very similar to
those found in the Design Gateway.
Approximations in Isight serve to replace a specific component during runtime

execution of a model. Approximations can also be used to gain an insight into the
behavior of the component which they approximate by examining the two-dimensional
and three-dimensional graphs. Approximations work by building a simplified
mathematical model for the selected component using multiple data points.
If an approximation is created in the Design Gateway and initialized before accessing

the Visual Design page of the Runtime Gateway, it will be immediately available for
viewing. Otherwise, the approximation must be initialized before the Visual Design tab
can show its visuals (graphs) and internal data.
In the Runtime Gateway, the data points for approximations can be obtained using any
of the following methods:
Executing the approximated component multiple times
Reading a data file with previously analyzed points

Using the execution history data from any component’s execution
The process of building the mathematical model using data points is called
initialization. After an approximation is initialized, it can be used for design space
visualization. Multiple approximations can be created, initialized, and viewed for any
Isight component.

Accessing Approximations of a Component 141
When an approximation is created for a process component (i.e., DOE, Loop, Monte
Carlo, Optimization, SDI, Six Sigma, Taguchi, Task), the subflow of the component is
approximated, such that when the process component executes the subflow, the active
approximation is executed instead. If there are multiple components in the subflow
(i.e., multiple simcodes, calculations, etc.), they all are replaced by one approximation.
All approximations for the selected component can be accessed via the Visual Design
tab on the Runtime Gateway. Approximations are created and edited using the
Approximation Wizard. Details about all of the above actions are described in the
remaining sections of this chapter.
Once you save a model that contains the approximations created using the Runtime
Gateway, you can access these approximations by either directly accessing the
Runtime Gateway or by accessing the Runtime Gateway through the Design Gateway.
These approximations are also viewable and fully manipulated directly from the
Design Gateway.
Isight has a separate component called the Approximation component, which should
not be confused with the regular approximations that are “attached” to another
component. The Approximation component is based on using an approximation that is
not attached to any other component, but rather is constructed from a data file. An
Approximation component is therefore a self-contained unit, which can be used
anywhere within the Isight model, contrary to the regular approximations, which are
always attached to a specific component. For the purpose of design space visualization,
the Approximation component is exactly the same as regular approximations. Many of
the described actions in the following sections also apply to the Approximation
component, with some exceptions.
Accessing Approximations of a Component

As mentioned in the previous topic, all approximations are created for a specific
component, either an activity or a process component. To access existing
approximations of a component or to create new approximations, you should first
select the component from the left side of the Runtime Gateway. Once selected, click
the Visual Design tab. You can also switch between components after accessing the
Visual Design tab, if desired. This feature allows you to quickly view the
approximations for multiple components.

Any existing approximations for the selected component are displayed on the tab. If
multiple approximations have been created, a drop-down list appears adjacent to the
component name at the top of the tab. The Visual Design tab allows you to create, edit,
delete, view error analysis, visualize an approximation, and perform additional design
searches.
The Visual Design tab itself is divided into four subtabs. Each subtab provides access
to a specific approximation feature. For more information on any of these subtabs,
refer to the following topics:
Visualization subtab. For more information, see “Visualizing an Approximation,”

on page 182.
Design Search subtab. For more information, see “Searching the Design Using
Specified Criteria,” on page 203.
Error Analysis subtab. For more information, see “Analyzing Approximation

Errors,” on page 211.
View Data subtab. For more information, see “Viewing Approximation Data After
Initialization,” on page 218.
You can also alter an existing approximation. For more information, see “Editing an
Existing Approximation,” on page 175.
Creating an Approximation Using

System-Determined Default Settings
When creating the first approximation for a component, you can quickly perform this
action using the system-determined default settings. This option is recommended if
you don’t have much experience working with approximations.
Important: This option is only available when creating the first approximation for a
component. If you have already created an approximation for the component you are
working with, proceed to “Creating an Approximation Using the Approximation
Wizard,” on page 145 for information on how to create additional approximations.

Creating an Approximation Using System-Determined Default Settings 143
To create an approximation using system-determined default settings:
1. Select a component on the left side of the Runtime Gateway.
2. Verify that the Visual Design tab is selected on the right side of the Runtime
Gateway. The tab should appear similar to the following example.
Note: If the Create Approximation... button does not appear on your Visual Design
tab, and instead you see an existing approximation, you cannot use the option
described in this section. Proceed to “Creating an Approximation Using the
Approximation Wizard,” on page 145 for details on how to create another
approximation for the selected component.
3. Click the Create Approximation... button in the middle of the tab. An

approximation is created using the history data that was gathered during the
execution of the model and its components.

The Visual Design tab is updated to show the approximation information.
Note: If no history data is available for the selected component, a message to that
effect is displayed instead of the Create Approximation... button.
Note: The button (at the top of the tab adjacent to the component name) can
also be used to create an approximation using the Approximation Wizard. For
more information, see “Creating an Approximation Using the Approximation
Wizard,” on page 145.
4. Proceed to one of the following topics:
“Visualizing an Approximation,” on page 182
“Viewing Approximation Data After Initialization,” on page 218

Creating an Approximation Using the Approximation Wizard 145
Creating an Approximation Using the

Approximation Wizard
You can create an approximation using the Approximation Wizard, which allows you
to specify certain settings for the approximation. This option is recommended if you
want to have control over any of the approximation settings. If you want to simply use
the system-determined default settings provided by Isight, see “Creating an
Approximation Using System-Determined Default Settings,” on page 142 for details.
Important: If you have already created an approximation for the component you are
working with, you must use the Approximation Wizard to create additional
approximation.
Proceed to one of the following topics:
“Creating an Automatic Approximation” on this page. When this option is used,

the approximation algorithm is automatically selected (RSM with Quadratic
polynomial). However, you are given the opportunity to define many other
options.
“Creating a User-Defined Approximation,” on page 149. When this option is used,

you must define all approximation options, including which approximation
algorithm to use.
“Creating an Approximation Using a Previously Saved File,” on page 169. When

this option is used, you can create an approximation using a previously saved file
that contains coefficient data.
Creating an Automatic Approximation

Isight has two approximation algorithms (or techniques): Response Surface Model and
RBF Model. Either one of these techniques can be used when creating an
approximation. If you do not want to learn the details of these approximation
techniques, you can create an Automatic approximation. When this option is selected,
Isight will use a preconfigured Response Surface Model with most of the options set to
the appropriate values. Only input and output parameters and their properties will have
to be configured manually.

Note: Automatic approximation creation requires the execution of a set of random

design points for initialization. If you want to use the history data for initializing an
approximation, or an external data file, you must create a user-defined approximation
(page 149) or use a previously saved data file (page 169).
To create a model using the RBF Model technique, see “Creating a User-Defined
Approximation,” on page 149.
To create a new approximation automatically:
Gateway.
3. Click the button at the top of the tab adjacent to the component name. The
Approximation Wizard appears.
4. Type a custom name for the approximation in the Name of approximation text
box, if you want to change the default name.

5. Verify that the Automatic radio button is selected; then, click Next. The Input and
Output Parameters screen appears.
If the approximation is created for an activity component, all parameters of the

component are displayed on the page. If the approximation is created for a process
component, all parameters mapped to the subflow are displayed, along with all
parameters from the subflow that are still not mapped to the parent. Selecting the
latter parameters will result in automatic creation of corresponding parameters in
the process component.
6. Determine which parameters you want to use for your approximation. You can
select or deselect individual parameters by clicking the check box in the first
column in both the Inputs and Outputs area, or you can click the Check or
Uncheck buttons to automatically select (or deselect) all of the listed parameters.
Note: For any inputs that are not selected, the values for these inputs will have no
effect on the outputs evaluated from the approximation. Similarly, if you do not
select one of the output parameters, its value will remain constant during execution
of the approximation.

7. Click Next. The Sampling Options screen appears.
These options let you determine the number of random sampling points that will be
used. The following options are available:
Specify a number of point in the sample points text box. This number must be
at or above the minimum required number of points specified in the text
message above the entry box.
Have Isight use a time limit for determining the number of points. Isight will
keep executing for the specified duration of time.
Note: If less than the minimum required number of points is executed, Isight will
continue executing sampling points until the requirement is met.
Click the Use a fixed random seed check box and specify a seed value to use
for the random number generator when determining the set of sample points to
be executed. This option allows you to reproduce the approximation with the
same set of points later, if desired.
Click the Execute design points in parallel if you want to execute your
initialization points in parallel. This option should only be used if you are
using a multi-CPU system or if you are connected to an ACS in the Fiper
environment.

8. Click Next. The Sampling Range screen appears.
9. Alter the Lower and Upper values for the listed input parameters, as desired.
These bounds will determine the design space where the random points will be
generated by Isight.
10. Click Finish. A message appears prompting you to initialize the approximation.
Click Yes to initialize the approximation. Proceed to “Initializing an

Click No to return to the Visual Design tab.
Creating a User-Defined Approximation

Isight has two approximation techniques: Response Surface Model and RBF Model.
When creating a user-defined approximation, you can pick the technique that you want
to use and control all options used by the approximation technique. If you want to
create an approximation automatically (where Isight specifies many of these options
for you), proceed to “Creating an Automatic Approximation,” on page 145. You can
also create an approximation based on a previously saved data file. For more

information on using a coefficient file, proceed to “Creating an Approximation Using a

Previously Saved File,” on page 169.
To create a new user-defined approximation using the wizard:
Gateway.

5. Click the User Defined radio button; then, click Next. The Approximation
Technique screen appears.
6. Select the technique you want to use from the Approximation technique
drop-down list. The following options are available:
RBF Model. Radial Basis Functions (RBF) are a type of neural network
employing a hidden layer of radial units and an output layer of linear units, and
characterized by reasonably fast training and reasonably compact networks.
For more information, see “RBF Model,” on page 312.
Response Surface Model. Response Surface Models (RSM) in Isight use
polynomials of low order (from 1 to 4) to approximate response of an actual
analysis code. For more information, see “Response Surface Model,” on
page 319.
Note: These techniques are plug-ins that have been created by Engineous and
included with your Isight installation. You can create your own approximation
technique plug-ins using the Generator. For more information, refer to the Isight
Development Guide.

7. Click Next. The Input and Output Parameters screen appears.
8. Determine which parameters you want to use for your approximation. You can
select or deselect individual parameters by clicking the check box in the first
column in both the Inputs and Outputs area, or you can click the Check or
Uncheck buttons to automatically select (or deselect) all of the listed parameters.
9. Click Next; then, perform one of the following actions, based on the
approximation technique you are using:
RBF Model: Proceed to step 10.
Response Surface Model: Proceed to “Setting Response Surface Model

Technique Options,” on page 157.
10. Set the Smoothing Filter option. This option allows you to relax the requirement
that the RBF approximation pass through every single data point. Its primary
purpose is to smooth out noisy data. By not going through every point, Isight can
effectively smooth noisy functions and provide an approximation that may be
easier to optimize. The value specified by this option averages the output values of
points that are clustered in the normalized filter domain.
The filter operates in normalized Euclidian space, in normalized domains ranging

from 0 to 1. Clustering is performed with respect to that range. For example,
consider that you have a single domain x, where 0<x<10. For a value of x=7.2, you
set a smoothing filter value of 0.001, then the procedure clusters and averages all

points in the range of 0.719<x<0.721 (remember that the space is normalized over
the range 10).
The maximum allowed value for the smoothing filter is 0.1. Mathematically, this
means you have a maximum of 10 clustered sample points across. (Through
research, it has been determined that at higher values it does not make sense to
perform an RBF.) With 10 clustered sample points, you can do a maximum of four
local minima (sine wave) across one dimension. With quartic RSM you can do
three local minima across one dimension. Therefore, if you have to smooth more
than 0.1 it is better to switch to the RSM technique.
Note that there is no theoretical basis to distinguish between signal and noise in the
data used for approximation. We recommend that you evaluate the resultant RBF
to determine if this option is appropriate for your application.
11. Click Next. The Sampling Options screen appears.

12. Select one of the following options from the Sampling method drop-down list:
Random Points. Isight generates the required number of random points

around the current point and executes an analysis at every point. Proceed to
“Using the Random Points Sampling Method,” on page 161 for more
information.
Data File. The model uses a data file to get data for model construction.
Proceed to “Using the Data File Sampling Method,” on page 163 for more
information.
DOE Matrix. Isight uses Design of Experiments (DOE) to determine the set
of points to evaluate. Proceed to “Using the DOE Matrix Sampling Method,”
on page 165 for more information.
Component History Data. Isight uses the History data (execution data) of the
selected component for initializing your approximation. You must have a
sufficient number of data points displayed on the Runtime Gateway History
tab to avoid initialization errors. If you are using the Response Surface Model
technique, the number of required design points is calculated on the RSM
Technique Option screen (click the Back button). Proceed to step 13.
13. Click Next. The Error Analysis Method screen appears.

14. Determine the error analysis method for the approximation:
Separate data set. This method compares exact and approximate output
values for each data point of the second (additional) data set. Proceed to
step 15.
Cross-validation. This method selects a subset of points from the main data
set, removes each point one at a time, re-calculates coefficients, and compares
exact and approximate output values at each removed point. Proceed to
step 19.
No error analysis. Proceed to step 22.

15. Click Next. The Error Analysis Sampling Options screen appears.
around the current point and executes an analysis at every point.
of points to evaluate.
17. Set the options for the selection you made in step 16. Depending on your choice, a
different set of options appears. These options are similar to the options set on the

Sampling Options screen. For more information about the Sampling methods, see
“Using the Sampling Methods Options,” on page 160.
18. Proceed to step 22.
19. Click Next. The Cross-Validation Options screen appears.
20. In the first text box, type the number of points from the total number of sampling
points that you want to use for cross-validation error analysis.
21. Click the Use a fixed random seed for selecting points check box and specify a
seed value to use for the random number generator when determining the set of
sample points selected for cross-validation. This option allows you to reproduce
the approximation with the same set of points later, if desired.

Click No if you want to save the approximation and wait until later to
initialize. You are returned to the Visual Design tab on the Runtime Gateway.

Setting Response Surface Model Technique Options

Several technique options can be configured when using the Response Surface Model
Approximation technique.
To set Response Surface Model technique options:
1. Access the Technique Options screen as described in “Creating a User-Defined

Approximation,” on page 149. The screen appears as shown below.
2. Select the polynomial order of the model using the corresponding drop-down list.
Linear. This option is the recommended value when the outputs are known to
be linear with respect to the inputs. This option requires the smallest number of
design points for initialization, but it will produce larger errors for non-linear
output functions.
Quadratic. This option is the recommended value for most cases and provides
the best approximation performance to cost ratio. Quadratic RSM provides the
best optimization performance for smooth exact functions.
Cubic. If this option is selected, the model polynomial will have all quadratic
terms, and only pure cubic terms (i.e., no mixed interaction terms of 3rd order
are included).

This option is recommended when the outputs are highly non-linear functions
of the inputs. This option requires more design points for initialization than
Quadratic.
Quartic. If this option is selected, the model polynomials will have all
quadratic terms, only pure and cubic terms, and only pure 4th order terms (i.e.,
no interaction terms of 3rd and 4th order are included).
The same recommendations listed under Cubic apply to Quartic

approximations. Be aware that using Quartic polynomials in optimization may
create undesired local minima.
3. You can use Term Selection to remove some polynomial terms with low
significance, which can improve reliability for your approximation and reduce the
number of required design points. Perform one of the following actions:
To use Term Selection: Click the Use term selection to select the most
significant terms from the polynomial check box.
To skip Term Selection: Proceed to step 6.
4. Select one of the following options from the Term selection method drop-down
list:
Sequential Replacement. This method of polynomial term selection starts

with the constant and then adds polynomial terms one at a time so that the
fitting errors of the Response Surface Model are minimized at every step. After
adding a new polynomial term, Isight will try to find a replacement for each of
the selected terms that can reduce the fitting errors further. The fitting errors
are checked using the Residual Sum of Squares (sum of squared errors at all
design points):
Here are exact output values, are approximate output values, n is the
number of design points used for the Response Surface Model.
Stepwise (Efroymson). This method of polynomial term selection starts with
the constant and then adds polynomial terms one at a time so that the fitting

errors of the RSM are minimized at every step. A new term is added if the
following condition is satisfied:
After adding a new term, Isight will examine all selected terms and will delete
one or more terms for which the following condition is satisfied:
In these formulae, p is the number of polynomial terms, n is the number of

designs used for the Response Surface Model, is the F-ratio to add a
term, and is the F-ratio to drop a term. These terms can be controlled
using the text boxes that appear under the Term selection method drop-down
list when Stepwise (Efroymson) is selected:
• F-ratio to drop term. This is the maximum value of F-ratio to drop a
polynomial term from RSM.
• F-ratio to add term. This is the minimum value of F-ratio to add a new
polynomial term to RSM.
Two-At-A-Time Replacement. This method of polynomial term selection
starts with the constant and then adds polynomial terms one at a time so that
the fitting errors of the Response Surface Model are minimized at every step.
After adding a new polynomial term, Isight will consider all possible
replacements for 1 or 2 of the selected terms that can reduce the fitting errors
further. Then the best replacement combination is found and the terms are
replaced and the next best term is selected and added. The process is repeated
at every step until the maximum number of terms is selected. This method has
a better chance of finding the best model than the two previous methods, but it
is more expensive computationally.
Exhaustive Search. This method generates all possible combinations of
polynomial terms and then finds the best combination that produces the
minimum fitting errors. This method is the most expensive computationally
and can take a very long time for a large number of design points and large

numbers of inputs and outputs. This method is only recommended for

approximations with very few inputs and very few coefficients.
5. Perform one of the following actions, based on your term selection method:
Click the Specify number of selected terms check box; then, enter the
number you want selected in the corresponding text box.
(Stepwise (Efroymson) only) Click the Specify maximum number of selected

terms check box; then, enter the maximum number you want selected in the
corresponding text box.
Note: The reason for the different option names specified above is that the
Stepwise algorithm may not select the maximum number of term and instead stops
after selecting a smaller number of terms.
6. Return to step 11 in “Creating a User-Defined Approximation,” on page 149.
Using the Sampling Methods Options

This section discusses the various sampling methods that are available when creating
an approximation. Proceed to one of the following topics for more information:
“Using the Random Points Sampling Method,” on page 161
“Using the Data File Sampling Method,” on page 163
“Using the DOE Matrix Sampling Method,” on page 165

Using the Random Points Sampling Method

To define options for the Random Points sampling method:
1. Access the Random Points options as described in “Creating a User-Defined

Approximation,” on page 149. The options appear as shown below.
2. Select the number of points for the approximation. The following options are
available:
Specify a number of points in the sample points text box. This number must
be at or above the minimum required number of points specified in the text
message above the entry box.
Specify a time limit using the As many points as possible in option. You can
set a time limit (in second, minutes, or hours) that Isight will use for
determining the number of points. Isight will keep executing for the specified
duration of time.
Note: If less than the minimum required number of points is executed, Isight will
continue executing sampling points until the requirement is met.
3. Click the Use a fixed random seed check box and specify a seed value to use for
the random number generator when determining the set of sample points to be
executed. This option allows you to reproduce the approximation with the same set
of points later, if desired.

4. Click the Execute design points in parallel if you want to execute your
initialization points in parallel. This option should only be used if you are using a
multi-CPU system or if you are connected to an ACS in the Fiper environment.
5. Click Next. The Sampling Range screen appears.
6. Determine how you want to define the sampling region using one of the following
options:
Absolute Values. This option defines the region by using absolute bounds for
each inputs parameter. You need to specify the Lower and Upper values for
each parameter in the corresponding columns.
Relative to Baseline. This option defines the region by applying relative move
limits to the baseline values in both directions. You need to specify the
baseline, move limit percentage, and minimum move limit for each parameter
in the corresponding columns.

7. Alter the Lower and Upper values for the listed parameters, as desired. If you
selected the Relative to Baseline option in step 6, you can also alter the Baseline
value.
8. Perform one of the following steps, based on your current task:
To complete a User Defined approximation after setting options on the

Sampling Options screen: Return to step 13 on page 154.
To complete a User Defined approximation after setting options on the Error

Analysis Sampling Options screen: Click Finish; then, return to step 23 on
page 156.
To complete an approximation that use a coefficient file: Click Finish; then,
return to step 19 on page 174.
Using the Data File Sampling Method

To define options for the Data File sampling method:
1. Access the Data File options as described in “Creating a User-Defined

2. Click the Browse... button to locate the file you want to use. The Select File dialog
box appears.

3. Locate the file; then, click the Select button. You are returned to the Sampling
Options screen, and your file appears in the large text box adjacent to the Browse...
button.
4. Specify the type of file you selected using the following options:
Static file. Select this option if the data in the file never changes. The file will
be read once and saved in memory for future use.
Note: If you later access the Approximation Wizard to view the approximation
you are creating, the Re-read File button is activated. Clicking this button
allows the wizard to scan the file for changes since it was first read and placed
into memory.
Dynamic file. Select this option if the data in the file can change. The file will
be read prior to every initialization. If you are executing on an ACS in the
Fiper environment, the file must be accessible via the absolute path or shared
file system. For more information, refer to the Isight User’s Guide.
File parameter. Isight will create a pre-configured file parameter named

“Initialization Data for <Approx_Name>” in the component. You can map
this file parameter to receive data from another component at run time. The
approximation will then use this data for initialization.

page 156.


Using the DOE Matrix Sampling Method

To define options for the DOE Matrix sampling method:
1. Access the DOE Matrix options as described in “Creating a User-Defined

2. Select the DOE technique you want to use from the Technique drop-down list.
The technique’s options appear at the bottom of the screen.
3. Proceed to one of the following topics for more information on the technique
options (no options exist for the Central Composite or Full Factorial options):
“Setting Data File Technique Options,” on page 325
“Setting Latin Hypercube Technique Options,” on page 326
“Setting Optimal Latin Hypercube Options,” on page 327
“Setting Orthogonal Array Technique Options,” on page 327
“Setting Parameter Study Technique Options,” on page 328
4. Click the Execute design points in parallel if you want to execute your
initialization points in parallel. This option should only be used if you are using a
multi-CPU system or if you are connected to an ACS in the Fiper environment.

5. Click Next. The DOE Factor Attributes screen appears.
Although each technique defines the appropriate set of attributes for a factor, the
following set of attributes are common among many (but not all) of the techniques.
# Levels. This attribute is the number of levels at which you wish to study the
factors. A change to this attribute will automatically readjust the Levels for
this factor.
Levels. This attribute is a space-separated list of the levels at which to study
the factor. The related attributes are updated once you click in a different cell.
Lower/Upper. These attributes are lower/upper levels for the factor. A change
to one of these attributes will automatically calculate new levels evenly
distributed between the Lower and Upper values.
Relation. This attribute specifies whether the Levels should be interpreted as

values or as %/difference (diff.) from a specified Baseline.
Baseline. This attribute is the value to be used for converting Levels into
values when the Relation is “%” or “diff.”
Alpha. The Lower and Upper levels specify the two levels at which a 2-level
full-factorial study is performed. The center point is also studied. The Alpha
option is a ratio defining two other points (also known as “star points”) at
which to study the given factor. For example, Alpha set to 0.25 indicates the

factor is to be studied at points 1/4 of the way from the baseline to the lower
and upper levels. Alpha set to 1.6 indicates the factor is to be studied 50%
beyond the lower and upper levels. For example, Lower = 5, Upper = 20,
Baseline = 10, and Alpha = 0.25 results in Levels = {5, 8.75, 10, 12.5, 20}.
6. Click Next. The DOE Design Matrix screen appears.
This screen displays the design matrix generated for the technique selected
(specified in step 2) and the factors selected and attributes specified.
7. (Optimal Latin Hypercube technique only). Click the Generate button to create
your design matrix. This ability to manually generate your matrix is present since
this process can take a significant amount of time. The Design Matrix Generation
Status dialog box appears, showing you how the matrix generation is progressing.
Note: If you do not manually generate the design matrix in the component editor, it
will automatically be generated as part of the execution.

8. (Optimal Latin Hypercube technique only) Examine the information displayed on

the Status dialog box; then, click the Close button once the matrix has been
created. If you click the Stop button before the optimization of the design matrix is
complete, the resulting design matrix will be the last one generated during the
optimization process.
9. Select how you want the design matrix displayed using the Show drop-down list.
You can display the design matrix as values (the actual values to be set at
execution) or levels (the level number as generated by the technique algorithm).
10. Perform any of the following actions, as desired, to manipulate the design matrix:
Deactivate a single design point. Click any row number to deactivate that
design point so that it will not be executed (the icon appears). You can
also click the button at the top of the design matrix, or right-click the
design matrix and select the Skip selected design point(s) option from the
menu that appears.
Deactivate all design points. To deactivate all design points in the design
matrix, highlight all of the design points and click the button. You can
also right-click the design matrix and select Skip all design points from the
menu that appears.
Note: Deactivating design points is useful when it is known that a specific set
of values in the design matrix represents a design that cannot be evaluated for
whatever reason.
Activate a design point. To activate a design point that has been set to be
skipped, click the icon that represents the design point. The row number
reappears. You can also click the button at the top of the design
matrix, or right-click the design point and select Activate selected design
point(s) from the menu that appears.
Activate all design points. To activate all of the design points in the design
matrix, highlight all of the design points and click the button. You can
also right-click the design matrix and select Activate all design points from
the menu that appears.

Copy the design matrix. This option copies the design matrix to the clipboard
so that is can be pasted elsewhere (for example, in a text file). This option can
be accessed using the Copy button above the design matrix or by

right-clicking the design matrix and selecting Copy design matrix from the
menu that appears.
Save the design matrix. Saves the design matrix to a file. This option can be
accessed by clicking the Save button above the design matrix or by

right-clicking the design matrix and selecting Save... from the menu that
appears.
page 156.

Creating an Approximation Using a Previously

Saved File
You can create an approximation using a previously saved file with coefficient data.
For more information on how to save coefficient data from another approximation, see
one of the following topics:
If your approximation is not yet initialized, see “Initializing an Approximation,”

on page 179.
If you approximation is already initialized, see “Viewing Approximation Data

After Initialization,” on page 218.

To create an approximation using a coefficient data file:
Gateway.
5. Click the Previously Saved radio button; then, click the Browse... button to locate
the file you want to use. The Select File dialog box appears.
6. Locate the file; then, click the Select button. You are returned to the
Approximation Wizard, and your file appears in the large text box adjacent to the
Browse... button.

7. Click Next. The Approximation Technique screen appears.
This screen shows the technique that was used in the original approximation.
Note: You cannot change the technique. If you change the technique, then the
coefficient data file is not used. Instead, a “User Defined” approximation is
created.
8. Click Next. The Input and Output Parameters screen appears.

This screen shows the input and output parameters that were used in the original
approximation.
Note: You cannot change the Input and Output parameters. If you change the
parameters, then the coefficient file is not used. Instead, a “User Defined”
approximation is created.
9. Click Next. The Error Analysis Method screen appears.
10. Determine the error analysis method for the approximation:
Separate data set. This method compares exact and approximate output
values for each data point. Proceed to step 11.
Cross-validation. This method selects a subset of points from the main data
set, removes each point one at a time, re-calculates coefficients, and compares
exact and approximate output values at each removed point. Proceed to
step 15.
No error analysis. Proceed to step 18.

11. Click Next. The Error Analysis Sampling Options screen appears.

around the current point and executes an analysis at every point.
of points to evaluate.
13. Set the options for the selection you made in step 12. Depending on your choice, a
different set of options appear. These options are similar to the options set on the
Sampling Options screen. For more information about the Sampling methods, see
“Using the Sampling Methods Options,” on page 160.
14. Proceed to step 18.

15. Click Next. The Cross-Validation Options screen appears.
16. In the first text box, type the number of points from the total number of sampling
points that you want to use for cross-validation error analysis.
17. Click the Use a fixed random seed for selecting points check box and specify a
seed value to use for the random number generator when determining the set of
sample points selected for cross-validation. This option allows you to reproduce
the approximation with the same set of points later, if desired.


Editing an Existing Approximation 175
Editing an Existing Approximation

Once an approximation has been created, you can alter it, as necessary, using the
Approximation Wizard.
To edit an existing approximation using the wizard:
Gateway.
3. If more than one approximation exists for the component, select the correct
approximation from the drop-down list at the top of the tab adjacent to the
component name.
4. Click the button at the top of the tab. The Approximation Wizard appears.
The wizard allows you to change any of the approximation information originally
set when the approximation was created.
Note: You can change the name and creation mode of the approximation by
clicking the Back button.

5. Proceed to one of the following topics for more information on all of the available
options, based on the creation mode of the approximation:
Automatic option: “Creating an Automatic Approximation,” on page 145
User Defined option: “Creating a User-Defined Approximation,” on page 149
Previously Saved option: “Creating an Approximation Using a Previously

Saved File,” on page 169
Important: The rest of this section discusses screens that only appear on the
Approximation Wizard when editing an existing approximation. All of the screens
that appear both when creating and editing an approximation are discussed in one
of the previously listed topics.
6. (Initialized approximations only) If the approximation you are editing has already
been initialized, and you have not changed any parameter settings on the Input and
Output Parameters screen, then a Sampling Data Set screen appears (in addition to
the screens expected for the creation mode selected).
This screen allows you to preserve or remove existing sampling data.

Using Approximations at Runtime 177
7. Choose one of the following options:
Use existing sampling data. This option is disabled if the approximation is

changed in such a way that more points are required.
Preserve existing sampling data and generate additional points.

Delete existing sampling data and generate a new data set.
8. Click Next. Several more screens appear in the wizard. Each one is described in
one of the topics listed in step 5.
9. Click Finish once you have viewed the remaining wizard screens. A screen
appears allowing you to initialize the approximation.
10. If you decided to not use the existing sampling data in step 7 or you made changes
that require calculating new coefficients, you’ll need to re-initialize the
approximation. Perform one of the following actions:
Click Yes to initialize the approximation. Continue to “Initializing an

Otherwise, the approximation data is re-displayed on the Visual Design tab.
Using Approximations at Runtime

If you have created one or more approximations for a component, you can activate one
of the approximations to specify that it be used at runtime by Isight. You can have
multiple approximations defined for a component. However, only one of these
approximations can be “active” at any one time. The active component is the one that
is used during model execution. You can still edit, visualize, or analyze errors for any
defined approximation. Furthermore, changing from one active approximation to
another does not delete the previously active approximation, it simply “turns it off” as
far as model execution is concerned.
You can easily change the active approximation that is currently being used during
model execution using the Approximations dialog box.

Note: By default, approximations are not activated when created in the Runtime
Gateway. You need to activate them manually as described in the following procedure.
To define which approximation model should be active:
Click the Workflow tab on the Runtime Gateway; then, right-click the
component that you want to configure and select Approximations from the
menu that appears.
Right-click the component on the left side of the Runtime Gateway; then,
select Approximations from the menu that appears.
Click the Workflow tab; then, click a component to select it and click the
button at the top of the tab adjacent to the component name.
Note: If the component has no approximations, then the button is disabled.

The Approximations dialog box appears.
A list of existing approximations for the selected component is displayed.
If an approximation is currently activated, a check mark appears in the Activated

column on the left side of the dialog box. If no check marks appear, the
approximations are all deactivated.

Initializing an Approximation 179
2. Click the check box in the Activated column that corresponds to the
approximation you want to activate. If a different approximation was selected, it is
automatically unselected.
Note: You can also clear all of the check boxes in the Activated column to
deactivate all of the defined approximations. In this case, Isight will not use any
approximation at runtime and will execute the component.
3. Click Close to return to the Runtime Gateway.
If you deactivated an approximation, notice that the approximation icon is now

grayed-out on the Workflow tab. This change is your visual cue that the approximation
will not be used during execution.
Initializing an Approximation
You can initialize your approximation immediately after creating it, or you can
initialize it after it has been created. Approximations can also be initialized
automatically at runtime when you submit a model for execution.
To initialize an approximation manually:

Gateway.

component name. The “No Data To Display” message appears on the Visual
Design tab.
4. Click the Initialize Now... button. The initialization process is started and status
information appears on the tab.

Initializing an Approximation 181
When initialization is complete, the tab appears as shown below.
5. Proceed to one of the following topics, as desired:
“Visualizing an Approximation,” on page 182.

“Viewing Approximation Data After Initialization,” on page 218
“Editing an Existing Approximation,” on page 175

Visualizing an Approximation
You can manually alter your approximation using the options on the Visual Design
tab’s Visualization subtab. This subtab is shown below.
The options on this tab allow you to manually interact with an initialized
approximation model and observe, graphically, how changing the input values affects
the output values and the shape of the output function. For more information on how to
automatically explore the design space for specified criteria, see “Searching the Design
Using Specified Criteria,” on page 203.
Note: If the model is not initialized, the visualization interface cannot be accessed. You
must first initialize the approximation to visualize it. For more information on this
process, see “Initializing an Approximation,” on page 179.
Gateway.

Visualizing an Approximation 183
component name. The approximation information is displayed on the Visualization
subtab, which is selected by default.
This subtab is divided into two panels: a panel on the left that presents the inputs
and outputs of the approximation with their corresponding values, and a panel on
the right that contains the graphs for visualizing the approximation. These panels
are described in more detail below.
The left side of the subtab displays the following information:
Slider View tab. Sliders for each approximation input parameter. You can
move the slider bars to change the input values. The unit associated with the
input parameter appears to the right of the slider bar, if applicable.
Slider View tab. Value bars showing approximation output values. These
values change according to the input values you enter. The unit associated with
the output parameter appears to the right of the value bar, if applicable.

Table View tab. This tab allows you to view input and output information in a
table.
Modify Range button. You can change the input range (lower/upper limits) by
typing a new number directly in the dialog box that appears. The number
represents a percentage modification from the original range for each input.
Reset Range button. This button allows you to reset the input values and the
input range to their original values.
The right side of the subtab displays the following information:
Tabs for viewing and selecting two-dimensional (2D), three-dimensional (3D),

Contour Graphs, or Local Effects and Global Effects graphs.
Thumbnail images of all graphs created at a given time. The selected graph has
a border around it.
When a thumbnail image of a graph is expanded to full-size mode, this side

displays the graph in a larger view, and provides graph controls for easier
interaction. These options change according to the type of graph selected
(two-dimensional, three-dimensional, contour, or effects). For more
information, see “Viewing the Approximation Graphs,” on page 188.
Drop-down lists to modify the parameters being displayed in the main graph
(three-dimensional, contour, and effects graphs only), when a graph is
expanded to full-size mode.

“Adjusting Input and Output Values Using the Slider View,” on page 185
“Adjusting Input and Output Values Using the Table View,” on page 186
“Viewing the Approximation Graphs,” on page 188
“Creating New Approximation Graphs,” on page 194
“Exporting a Graph,” on page 195
“Setting Graph Options,” on page 196

“Removing Graphs,” on page 199
“Setting Graph Preferences,” on page 201

Adjusting Input and Output Values Using the

Slider View
The Slider View allows you to select and modify different input values by moving the
input sliders to the left or to the right. The output value bars will change based on the
input values changed using the sliders. At the same time, changing the input values will
cause the main graph and thumbnail graphs on the right side of the interface to change.
This view is recommended for beginner users who want to observe how the graph
changes over a range of input values.
To adjust input and output values using the Slider View:

1. Verify that the Slider View tab is selected from the bottom left corner of the
Visualization subtab. The interface appears as shown below.

2. Change any input value to see the effects on the output values of the model using
one of the following methods:
Move the slider for the corresponding input. The value changes in the text box
directly above the slider.
Change the input value directly in the text box that corresponds to the desired
input. You can only change the input based on the lower/upper limits defined
in the approximation. If you want to set a value outside of the defined range,
click the Modify Range... button at the bottom of the Slider View tab. For
more information about the Modify Range... button, see “Visualizing an
3. Observe how the output values on the value bars change. The actual values of the
output parameters are displayed next to their names. When you change an input
value (either using the slider or directly typing a value), the selected point on the
graph corresponding to the value (highlighted blue point in 2D graphs) also
changes.
4. (optional) Click the Set component parameters button to transfer the updated
parameter values to their corresponding parameters in the Isight component for
which the approximation was created. For more information, see “Setting
Component Input Values from the Visual Design Tab,” on page 209.
5. (optional) Click the Compare with actual... button to see how the approximate
design compares with the actual design. For more information, see “Comparing
Actual and Approximation Outputs,” on page 209.
6. (optional) Manipulate the graphs on the right side of the subtab. For more
information, proceed to one of the following topics:
“Viewing the Approximation Graphs,” on page 188
Adjusting Input and Output Values Using the

Table View
The Table View allows you to modify the input values, which, in turn, changes the
resulting output values and graphs. This option is recommended for experienced users
who want to look at the graph created from specific input/output combinations. It

allows you to enter different specific input points quickly and observe the behavior.
You can also sort the table rows and easily find the largest and smallest output
parameters for a given design point.
To adjust input and output values using the Table View:
1. Verify that the Table View tab is selected from the bottom left corner of the
Visualization subtab. The interface appears as shown below.
2. Change any input value by entering a new value directly in the Value column of
the Inputs table. The output values will automatically change accordingly. The
values in the Name, Min, and Max columns cannot be edited.
3. (optional) Sort the columns. You can sort the data by clicking any of the column
headings. For example, clicking the Value heading will sort based on the value
data. An arrow appears in the heading that you click. Clicking the arrow allows
you to switch the sorting type between increasing and decreasing sorts.
4. (optional) Click the Set component parameters button to transfer the updated
parameter values to their corresponding parameters in the Isight component for

which the approximation was created. For more information, see “Setting
Component Input Values from the Visual Design Tab,” on page 209.
5. (optional) Click the Compare with actual... button to see how the approximate
design compares with the actual design. For more information, see “Comparing
6. (optional) Manipulate the graphs on the right side of the subtab. For more
information, proceed to one of the following topics:
“Viewing the Approximation Graphs” on this page
Viewing the Approximation Graphs

You can create two-dimensional (2D), three-dimensional (3D), Contour, and Local and
Global Effects graphs for your approximation. The two-dimensional and
three-dimensional graphs are created by evaluating the approximation at multiple
points and show the behavior of the approximated output parameters with respect to
the input parameters. You can observe the relative effects of the inputs on the outputs
using the graphs.
Contour graphs show the various levels of the selected output parameter with respect to
the two selected input parameters. Contour graphs are in essence a 3D surface plot
viewed from above, and are similar to a map with colored elevation levels.
When Local Effects graphs are created, a DOE study is performed and the normalized
effects are calculated from regression results. The DOE is performed within a local
region of the approximation (+/-10% of the total range centered around the current
selected point). The Local Effects graphs are only updated (a new DOE study
executed) when a new design point is selected.
To create Global Effects graphs, a series of local DOE studies is executed at multiple
points throughout the entire sampling region of the approximation model. The absolute
values of local normalized effects are then averaged over all of the locations where
local DOE studies were performed and displayed on the Global Effects graphs.
Two-dimensional (2D) graphs are color-coded to show the feasibility and infeasibility
of design points. Feasible design points are black, while infeasible design points are
red. Also, input bounds are displayed, if the bounds are within the sampling range. For

more information on specifying these bounds, see “Searching the Design Using
Specified Criteria,” on page 203.
Graphs are displayed on the right side of the Visualization subtab in a small, thumbnail
view. They provide a visual representation of your approximation. They can be viewed
in a number of ways, can be altered by changing input values on the left side of the
interface, and can be changed by selecting different parameter combinations to display
and modifying various graph options.
Note: Remember that the graphs are created using values from the approximation, not
actual values from executing the component. The actual behavior of the output
parameters of the component will be different to some degree, depending on the errors
of the approximation. To assess this difference, see “Comparing Actual and
Approximation Outputs,” on page 209.
Note: Two-dimensional (2D) thumbnail graphs are displayed in a table, with input and
output names shown as the column and row names. When adding or deleting
two-dimensional graphs, only an entire row or column can be added or removed.
Three-dimensional (3D) graphs can be added and removed one at a time.
When available, the drop-down lists under the main graph allow you to change the
selected parameters for the displayed graph. You can also create new graphs at any
time and delete existing ones.
To view the approximation graphs:
1. Determine the type of graph you want to view using the tabs on the right side of the
Visualization tab. The following options are available:
2D. This type of graph represents a “slice” (cross-section) of the

multidimensional surface of the selected output function. It is obtained by
fixing all input values at their baseline values, and varying the selected input
parameter across its entire range.
3D. This type of graph is a three-dimensional view of the surface that shows
the values of the output parameter depending on the values of any two input
parameters. All input parameters except the selected two on the graph are held
constant at their current values.
Contour. This type of graph is a two-dimensional view of the surface, similar

to a color map showing surface elevation levels. All input parameters except
the selected two on the graph are held constant at their current values.

Local Effects. This graph is similar to a DOE Pareto Plot, and shows the
relative effects of each input on an output.
Global Effects. This graph is similar to a DOE Pareto Plot, except it shows
average absolute values of relative effects of inputs on an output.
Once you select a tab, the available graphs are displayed. If you do not see the type
of graph you wish to view, you can create it. For more information, see “Creating
New Approximation Graphs,” on page 194.
2. Access the graph you want to view using one of the following methods:
Double-click the graph.
Click the graph; then, click the button on the right side of the tab.
If you do not see the type of graph you wish to view, you can create it. For more
information, see “Creating New Approximation Graphs,” on page 194.
The full-size (large) version of the graph appears on the right side of the
Visualization tab, along with options for manipulating the graph.

By default, the following graphs are created:
a three-row, three-column table of two-dimensional graphs

two three-dimensional graphs
two Contour graphs
three Local Effects graphs
three Global Effects graphs
If the number of inputs or outputs is less than two, these numbers are adjusted. If
only one input parameter exists, three-dimensional, contour, and effects graphs are
not created.
Note: If you wish to select a graph other than the one you initially selected, simply
double-click the large graph or click the button to return to the thumbnail
view.
3. (3D, Contour, and Effects graphs only) Select the input(s) and output you wish to
view on the main graph using the Input and Output drop-down lists below the
main graph area. The type and number of drop-down lists that appear is based on
the type of graph selected. For example, if you select an Effects graph, only a
single Output drop-down list appears. No input drop-down list is available.
The main graph is automatically updated when you change the value of one of the
inputs using the sliders. The vertical dashed line on the graph marks the current
value of the input parameter in the X axis for 2D graphs. The range of all axes is
set automatically based on the minimum and maximum values of the
approximation inputs.
Note: The Y-Axis for a three-dimensional graph displays input values whereas the
Y-Axis for a two-dimensional graph displays output values.
4. (2D graphs only) Place your mouse pointer on any infeasible (red) point to view
the first ten violated parameters for that point. Also, the number of violated
constraints is shown at the bottom of the tab, next to the point coordinates.
5. (2D graphs only) Right-click on the graph, select Overlay Data Points...; then,
enter the name of the file with data points that you want to overlay on top of the 2D
graph. Labels are generated from the first column of the data file.

6. (2D and 3D graphs only) Use any of the following controls to manipulate the
graph directly:
. This button resets the ranges of input parameters and

returns the graph to its original configuration and appearance.
. This button allows you to select a point on the graph and

then view the values of input and output parameters by clicking on the graph.
The coordinates of the selected point are displayed directly below the graph
itself (the coordinates appear no matter what cursor mode you are using). Also,
when a point is selected, the input sliders and output value bars on the left side
of the interface are updated.
. This button allows you to zoom in on any area of a

two-dimensional or three-dimensional chart. You can click and drag to select a
specific area for the zoom action. This will zoom in on that zone or part of the
graph which allows you to observe (concentrate or narrow down) on a certain
zone.
. This button allows you to pan a graph. Once selected,

simply click the graph and move your mouse. The graph is moved in a similar
manner. This functionality is only supported for two-dimensional graphs.
. This button allows you to rotate a three-dimensional graph.

Once selected, simply click a graph and move your mouse. The graph is
rotated in a similar manner. By rotating the graph, X, Y, and Z rotation axes
values also change. These values are displayed in the text boxes in the
Rotation area.
Rotation text boxes. These settings allow you to optimize the rotation by
either entering values into the X, Y, and Z text boxes, or by clicking the
buttons to increase or decrease the values of a particular axis. By changing
these values (using either method described above), the graph rotates
accordingly.
Scale text box. Scaling allows you to limit the area of the graph to a smaller
fraction of the total space defined by the minimum and maximum values of the
inputs.

7. (2D and 3D graphs only) Click the Auto-fit z-axis check box to change the
behavior of the graph when you scale the graph. When this option is selected, the
Z-Axis range of the main graph will always match the range of the displayed data.
If not selected, the graph’s Z-Axis is not modified when it is scaled.
8. (Contour graphs only) Overlay Constraint Violations Data on Contour Graph.

If constraints were defined in the Approximation Viewer Design Search tab,
contour graphs can be enhanced by selecting this option to overlay the constraint
violation data. Selecting this option overlays the existing contour plot with
different shades of grey color to show the areas of the plot where any constraints
are violated, from totally transparent (no grey color) for areas without constraint
violations, to totally black color for areas with 4 or more constraints violated, and
three shades of grey for areas with 1…3 violated constraints. If the entire area of
the contour plot does not have any violated constraints, selecting this option will
have no effect. If the entire area of the contour plot has more than 4 constraints
violated, the entire area will be colored black.
When this option is selected, a Relax Constraint Bounds… button becomes

visible. Clicking this button displays a Relax Constraint Bounds dialog box
where you can enter a relaxation value for all constraint bounds. This dialog gives
you a quick way of performing a “what-if” study to see what effect constraints
have on the feasible domain. To restore original constraint bounds, click the
Restore original constraint bounds checkbox; then, click OK.
9. (Effects graphs only) Use the Output drop-down list below the main graph to
switch between graphs. This option allows you to change graphs without
re-accessing the thumbnail view.
10. (Effects graphs only) Compare Local and Global effects. This option places two
effects graphs, Local and Global, next to each other, allowing you to see the
difference between the local and global effects of inputs on a selected output.
11. Proceed to any of the following topics for more information on using the
Visualization subtab:
“Exporting a Graph,” on page 195
“Setting Graph Options,” on page 196
“Removing Graphs,” on page 199

“Setting Graph Preferences,” on page 201
“Setting Component Input Values from the Visual Design Tab,” on page 209
“Comparing Actual and Approximation Outputs,” on page 209
Creating New Approximation Graphs

By default, several graphs are created on the Visualization subtab. However, you can
create as many additional graphs as you wish.
To add a new graph:
1. Verify that you are viewing the graphs in the thumbnail format. If you are viewing
a graph in the large format, double-click the graph or click the button to return
to the thumbnail format.
2. Click the button on the right side of the Visualization subtab. The Add/
Remove Graphs dialog box appears.
3. Choose the type of graph you want to create (2D, 3D, Contour, Local Effects, or
Global Effects) using the tabs near the top of the dialog box. The graph will
automatically be added to the corresponding tab on the Visualization subtab.

4. Perform one of the following actions, based on the type of graph you are creating:
2D and 3D Graphs. Select the parameters that will represent each axis from
the Axis lists. Selecting multiple parameters for a single axis will create
multiple graphs. You can also click the Select All button to create a graph for
each listed parameter.
Since two-dimensional (2D) graphs are displayed in a table, only an entire

column or row can be added. Selecting an additional input or output parameter
adds a new column or row to the 2D graph table.
Important: When working with 2D graphs, if you wish to keep all of the
selected parameters highlighted when you alter the selected parameters, hold
down the CTRL key on your keyboard when you click additional parameters.
Otherwise, all of the parameters in the area will be de-selected.
Note: You can also remove 2D graphs using this dialog box. For more
information, see “Removing Two-Dimensional (2D) Graphs,” on page 200.
Contour Graph. Select the parameters that will represent each axis from the
Axis lists. Selecting multiple parameters for a single axis will create multiple
graphs. You can also click the Select All button to create a graph for each
listed parameter.
Local or Global Effects Graph. Select the output parameter(s) that will be
included on the graph. You can select multiple parameters. You can also click
the Select All button to create multiple graphs simultaneously (one for each
output selected).
5. Click OK. The graph is added to the selected tab in the Graph Palette.
Exporting a Graph
You can use graphs created in Isight in another application using the exporting and
copy functions.

To exporting or copy a graph:
1. Right-click the main graph.
2. Select one of the following options from the menu that appears:
Export / Export to Image. This option exports the graph to an image file
(*.jpeg, *.jpg, *.png). You will be prompted to select the file to which you
want the graph exported.
Export / Export to Text File. This option exports the graph data file to a text
file (*.txt). You will be prompted to select the text file to which you want the
graph data to be exported.
Export/ Export to Excel. (Windows platforms only) This option exports the
graph image and data to an Excel file.
Copy / Copy Image. This option copies the graph image to the system
clipboard. Once copied, you can paste the graph in another document or
imaging software by right-clicking and selecting Paste from the menu that
appears.
Copy / Copy Data. This option copies the data in the graph to the system
clipboard. Once copied, you can paste the data in another software application
by right-clicking and selecting Paste from the menu that appears.
Setting Graph Options

There are several options available to change the look of a graph.
To specify graph appearance options:
1. Right-click on the main graph; then, select Options from the menu that appears.
The Graph Options dialog box appears.

If you are working with a three-dimensional graph, proceed to “Setting
Two-Dimensional Graph Options,” on page 197.
If you are working with a two-dimensional graph, proceed to “Setting

Two-Dimensional Graph Options,” on page 197.

If you are working with a contour graph, proceed to “Setting Contour Graph
If you are working with a Local or Global Effects graph, proceed to “Setting
Local and Global Effects Graph Options,” on page 199.
Setting Two-Dimensional Graph Options

If you’re working with a two-dimensional graph, the following dialog box appears:
Set the following options, as desired:
The Data Series tab allows you to change the default settings for the shape, size,
and color of the graph ticks. The following options are available:
Symbol Shape. Changes all of the ticks on the graph. The default is a circle.
Shape Size. Changes the size of the ticks. The default is 5 pixels.
Current Point Symbol Shape. Changes the current point symbol shape. The
default is a circle.
Current Point Symbol Size. Changes the size of the current point symbol.
The default is 5 pixels.
Line Width. Changes the line width. The default is 1 pixel.
The Axes tab allows you to set options for the axis (X, Y) currently selected from
the list on the left side of the tab. There are no XY and XZ grid lines for
two-dimensional graphs.

Setting Three-Dimensional Graph Options

If you are working with a three-dimensional graph, the following dialog box appears.
The Chart Surface tab allows you to specify different combinations of options.
Select different combinations until you find one that best suits your needs.
The Chart Projection tab allows you to set Contoured and Zoned options for the
floor and ceiling of the graph.
The Axes tab allows you to set options for the axis (X, Y, Z) currently selected
from the list on the left side of the tab.
The Legend tab allows you to show the legend for the graph. If selected, the
legend appears to the right of the graph.
Setting Contour Graph Options

If you are working with a contour graph, the following dialog box appears:

The General Options tab allows you to change the default settings for showing
the legend, grid, and contour lines. You can also set the number of contour levels
on this tab.
The Axis Options tab allows you to set options for the axis (X, Y) currently
selected from the list on the left side of the tab.
Setting Local and Global Effects Graph Options

If you are working a Local or Global Effects graph, the following dialog box appears:
Enter the Maximum number of bars you want displayed in the text box.
Removing Graphs
The method for removing a graph varies based on the type of graph you are removing.
Two-dimensional (2D) thumbnail graphs are displayed in a table, with input and output
names shown as the column and row names. When deleting two-dimensional graphs,
only an entire row or column can be removed. Three-dimensional (3D) graphs can be
removed one at a time.

“Removing Two-Dimensional (2D) Graphs,” on page 200
“Removing Three-Dimensional (3D), Contour, and Effects Graphs,” on page 201

Removing Two-Dimensional (2D) Graphs

Two-dimensional (2D) graphs are created as a table. For this reason, you cannot simply
remove a single graph. Instead, you must remove an entire row of column at a time.
To remove a 2D graph:
2. Click the button on the right side of the Visualization subtab. The Add/
Remove Graphs dialog box appears.
3. Verify that the 2D tab is selected on the Add/Remove Graphs dialog box. The
parameters that are currently being used to create the table of 2D graphs are
highlighted.
4. De-select any of the highlighted parameters to remove graphs that use that
parameter from the 2D tab on the Visualization subtab.
Note: If you wish to keep all of the other parameters in the area selected when you
de-select a parameter, hold down the CTRL key on your keyboard when you click
a parameter to de-select it. Otherwise, all of the parameters in the area will be
de-selected.
5. Click OK. Your two-dimensional graphs are updated, and the graphs that used the
parameter you de-selected in step 4 are removed.

Removing Three-Dimensional (3D), Contour, and Effects

Graphs
Three-dimensional (3D), Contour, and Effects graphs can be removed using either of
the following methods:
Select the thumbnail image; then, click the button.
Right-click on the graph; then, select Remove Graph from the menu that appears.
Note: Three-dimensional (3D), Contour, and Effects graphs cannot be removed using
the Add/Remove Graphs dialog box. However, you can use this interface to remove
two-dimensional (2D) graphs. For more information, see “Removing
Two-Dimensional (2D) Graphs,” on page 200.
Setting Graph Preferences

The Visualization subtab preferences allow you to change certain graph preferences
such as default input/output displays, default graph resolution for three-dimensional/
two-dimensional graphs, and three-dimensional graph default settings. Changing these
preferences automatically changes the settings the next time you open the
Visualization subtab. By using these preference options, you won’t have to manually
change the settings every time you open the interface. For example, if you only want to
use the Table View, then setting this option as the default will cause the interface to
open with the Table View tab selected each time it is opened.
To set Graph preferences:
2. Click the button on the right side of the Visualization subtab.

The Global Preferences dialog box appears.
3. You can change the following preference settings, as desired:
Use the Default input/output display drop-down list to determine if the

Slider View tab or Table View tab will be selected when the Visualization
subtab is accessed.
Set the Graph resolution (2D) options. The default for the large
two-dimensional graph resolution is 50. Similarly, you can change the
thumbnail image (Small) resolution.
Important: Increasing the resolution may slow down performance.
Set the Graph resolution (3D) options. The default for the large
three-dimensional graph resolution is 16. Similarly, you can change the
thumbnail image (Small) resolution.
Important: Increasing the resolution may slow down performance.

Three-dimensional graph default options. This set of options allows you to
choose mesh surface and/or contours as well as the contour levels.
4. Click OK to save your changes and close the dialog box.

Searching the Design Using Specified Criteria 203
Searching the Design Using Specified Criteria

A “search” capability exists that assists you in finding a design meeting specified
criteria. You set these criteria using the Design Search subtab on the Runtime Gateway
Visual Design tab. If you wish to examine your design by manually changing
parameter values, see “Visualizing an Approximation,” on page 182 for details.
For more information on this feature, see one of the following topics:
“Setting Your Criteria and Searching the Design” on this page

“Setting the Design Search Options,” on page 208
Setting Your Criteria and Searching the Design

You can search your design for certain criteria. The Design Search subtab allows you
to determine which objectives and constraints to use in the search, as well as settings
for these parameters that should be used.
To automatically search your design:
Gateway.
component name.

4. Click the Design Search subtab. The search options are displayed.
5. Select objectives or constraints for your design search using the tabs at the top of
the interface. Once selected, you can manually set the following information for
your design search:
Note: The Design Search subtab automatically uses information (constraints and
objectives) set on the Design Gateway Formulation tab for the corresponding
component. These settings can be altered, as desired. Any changes made on this
subtab are propagated to the Parameters tab and are reflected on the History tab
(with the run grading information being updated for the new bounds). For more
information on run grading and the History tab, see “Understanding Color Usage
(Run Grading),” on page 105. For more information on the Formulation tab, refer
to the Isight User’s Guide.
Objectives:
• Direction. You can set whether you want to maximize or minimize the
selected objective.
• Target. You can specify a desired target value for your objective
parameter.

• Scale Factor. This value is used to equalize the magnitude of objectives

when several parameters of vastly different magnitudes are selected.
• Weight Factor. This value is used to add importance to one of the selected
objectives.
Constraints:
• Lower Bound. This setting is represented by a red line in the graphs at the
bottom of the interface.
• Upper Bound. This setting is represented by a red line in the graphs at the
• Target. This setting is represented by a green line in the graphs at the
Any changes made to the objectives or constraints are automatically propagated to
the Runtime Gateway Parameters tab, with the bound and objectives being updated
accordingly. Furthermore, the grading of design points on the Runtime Gateway
History tab will also be automatically updated.
By default, all of the design variables are selected. However, you can alter this
setting using the Design Variables tab. The initial settings are based on the range
displayed on the Visualization subtab. Any changes made using the Design
Variables tab are transferred to the Visualization tab.
6. (optional) Set the search options as described in “Setting the Design Search
Options,” on page 208. These options allow you to set the Optimization technique
(and options) for the search as well as graph update options.
Note: When approximations are created on Optimization components, the

Optimization technique and options defined within the Optimization component
are used for the design search. Otherwise, a default optimization plan is created.

7. Click the Search button. The search is performed, and the interface is updated to
show the results of the search.
8. Once the search is complete, perform any of the following options, as desired:
Update the constraints and objectives criteria to refine your search.
Examine the graphs created during the design search. These graphs are
color-coded and show bounds (if the bounds are within the sampling range).
The colors are used to represent the following information:
• Black represents a feasible design point.

• Red represents an infeasible design point.
• Green represents the best design point (based on calculated objective). This
point is always a feasible point (i.e., no violated constraints).
• Yellow represents the best design point but a point that is infeasible. This
color is used when there is at least one objective defined and either there
are no feasible points found, or the best feasible point (colored green) has a
worse calculated objective and penalty. In short, this point might be a better
design even though it is slightly infeasible.

Rearrange the graphs at the bottom of the interface to focus on a particular

input or output. You can move a particular graph by clicking it and using the
buttons.
Click any point in a graph to view the corresponding point in all of the other
graphs.
Manually update the value of any design variable and add it to the existing
graphs by changing the setting in the Value column on the Design Variables
tab; then, click the Add point button. The new point you defined is added to
the graphs. You can also change the values for the Design Variables using the
sliders on the Visualization subtab.
This feature is useful if you want to examine how a specific known set of input
values affects the objectives and constraints.
Note: To clear all points from the graph and return the graphs to their original
form, click the button.
If you’ve updated any of the search criteria, re-execute the search using the
Search button.
Click the Set component parameters button to transfer the updated parameter
values to their corresponding parameters in the model. For more information,
see “Setting Component Input Values from the Visual Design Tab,” on
page 209.
Click the Compare with actual... button to see how the approximate design
compares with the actual design. For more information, see “Comparing

Setting the Design Search Options

You can specify optimization and graph options when using the design search feature.
To set the design search options:
1. Click the Options... button on the right side of the interface. The Design Search
Options dialog box appears, showing the Technique tab.
2. Select the optimization technique that will be used for the design search from the
Technique drop-down list; then, set the technique’s tuning parameters. For more
information on selecting optimization techniques and setting their tuning
parameters, refer to the Isight Component Guide.
Note: When approximations are created on Optimization components, the

Optimization technique and options defined within the Optimization component
are used for the design search by default (this setting can be modified). For all
other components, a default optimization plan is created.
3. Click the General tab; then, set the Update design space graphs during
optimization option on the General tab. If this option is selected, all graphs on the
Visualization subtab are updated at each new point during the design search
(optimization). Using this option slows down the process, but it can be very useful
in tracking the path of the search through the design space as opposed to just
viewing the history of values (i.e., the graphs shown on the Design Search subtab).
4. Click OK to close the dialog box and return to the Design search subtab.

Setting Component Input Values from the Visual Design Tab 209
Setting Component Input Values from the

Visual Design Tab
The Visual Design tab provides a way to take the current set of input values and set
them as the values for the input parameters of the component that the approximation
represents.
To set the component input values:
1. Click the Set component parameters button at the bottom of the Visual Design
tab. The Set Parameters dialog box appears, informing you that the component
parameter (input) values have been updated.
2. Click OK.
You can verify that the values for the component that the approximation represents
have been modified using the Parameters tab on the Design Gateway. For more
information on using this tab, refer to the Isight User’s Guide.
Comparing Actual and Approximation

Outputs
The Visual Design tab can take the current set of inputs values and run the exact
analysis that the approximation represents. This feature allows you to see a comparison
of output values in order to check for accuracy.

To compare outputs:
1. Click the Compare with actual... button. After executing the actual analysis
(which may take some time), the Approximate vs. Actual dialog box appears.
2. View the data and verify the accuracy of the output values.
3. (optional) Sort the data by clicking either the Approximate or Actual column
headers.
4. Click Close to return to the Visual Design tab.

Analyzing Approximation Errors 211
Analyzing Approximation Errors

The Isight approximation error analysis feature provides a visual representation of the
quality of an approximation model for each response. The total error is calculated for
each response using one of four different approaches (average error, maximum error,
root mean square error, R2), and is presented visually for each response using four
different visuals:
Actual vs. predicted fit

Residual scatter
Residual frequency
Total Error bar chart
The error is calculated based on a number of sample points specifically allocated for
error analysis. These points are defined in the Approximation Wizard. For more
information, see “Creating an Automatic Approximation,” on page 145, “Creating a
User-Defined Approximation,” on page 149, or “Creating an Approximation Using a
Previously Saved File,” on page 169 depending on how you created your
approximation.

“Using the Error Analysis Feature” on this page
“Understanding the Results,” on page 217
Using the Error Analysis Feature

To analyze approximation errors:
Gateway.
component name.

4. Click the Error Analysis subtab. The error analysis options are displayed.
If the “No data to display” message is displayed, then your approximation does not
have error analysis data. You can click the Run Error Analysis... button to start
the an error analysis process using the Cross-Validation method within ten design
points. To configure error analysis options, click the button to access the
approximation’s settings. For more information on setting error analysis options on
existing approximations, see “Editing an Existing Approximation,” on page 175.
The subtab displays the following information:

A table of error values for each output parameter, with a drop-down list of
error types, and an entry box for setting the acceptable level of error for the
selected error type. Outputs with errors exceeding the acceptable level are
highlighted in red.
A tabbed notebook panel with graphical representation of error information for

one or more output parameters (responses).
Note: Changing the selected error type or acceptance level on the left side of the
dialog box does not change the information displayed on the right side of the

dialog box, except for possibly highlighting the graphs of those responses that
violate the acceptance level.
5. Select the desired error type from the Error Type drop-down list. Error analysis
types are implemented as “plug-ins”. As such, they are extendable by creating new
plug-ins for new error analysis techniques. For more information on creating
plug-ins, refer to the Isight Development Guide.
The error analysis plug-ins currently available in Isight are the following:
Average. The differences between the actual (workflow execution) and

predicted (approximation model execution) values for all errors samples are
averaged and then normalized by the range of the actual values for each
response. The value is thus a fraction of the response data range for the error
sample points. Normalizing the error value allows the error level of different
responses with different magnitudes to be compared with respect to
approximation model quality of predictions.
Maximum. The maximum difference between the actual (workflow

execution) and predicted (approximation model execution) values for all error
samples is taken for this error type, and normalized by the range of the actual
values for each response. The value is thus a fraction of the response data
range for the error sample points. Normalizing the error value allows the error
level of different responses with different magnitudes to be compared with
respect to approximation model quality of predictions.
Root Mean Square. The squared differences between the actual (workflow
execution) and predicted (approximation model execution) values for all error
samples are averaged. The square root is then taken and the result is
normalized by the range of the actual values for each response. The value is
thus a fraction of the response data range for the error sample points.
Normalizing the error value allows the error level of different responses with
different magnitudes to be compared with respect to approximation model
quality of predictions.
R-Squared. The coefficient of determination is calculated based on the error

samples. The coefficient of determination always ranges between 0 and 1,
where 1 represents a perfect fit (or no prediction error).
6. Specify the acceptance level for the selected error type in the Acceptance Level
text box. The acceptance level defines the cutoff value for the selected error type

that distinguishes a response with acceptable fit (acceptable approximation quality)

versus a response with unacceptable fit (unacceptable approximation quality).
For the Average, Maximum, and Root Mean Square error types, low values are
desired, and so the Acceptance Level is an upper limit; reported error values
greater than the acceptance level will be flagged in red in the table of responses
and in the plots as unacceptable approximation quality. The default Acceptance
Level is 0.2 for Average and Root Mean Square, and 0.3 for Maximum.
For R-Squared, high values are desired, and so the Acceptance Level is a lower
limit; reported error values less than the acceptance level will be flagged in red in
the table of response and in the plots as unacceptable approximation quality. The
default Acceptance Level for R-Squared is 0.9.
7. Verify that the Response Fit tab is selected on the right side of the subtab. The
response fit plots present actual versus predicted response values for each
response. The diagonal line represents a perfect fit (predicted = actual). If all points
fall on or close to the diagonal line, the approximation model predicts well based
on the error points. If the plot background is colored red, the response error is
unacceptable based on the defined acceptance level.
The blue horizontal line shows the mean response value determined using the
actual error sample data.
8. Perform any of the following actions to view individual plot information:
To view one response fit plot in greater detail, select the response from the
drop-down list that appears when the Show button above the plots is selected.
To return to all response plots, select All Responses from Show drop-down
list.
Double-click a response plot to enlarge that single plot, and double-click again
to return to all response plots.

9. Click the Residual tab. Additional plots appear.
10. Review the residual plots for each response. The residual plots present the
difference between the actual and predicted values for all error sample points for
each response. The horizontal blue line at 0 represents 0 residual or 0 prediction
error (predicted = actual). These plots can be used to identify outliers (points
significantly further from the blue 0 residual line) or trends in the residuals (ideally
residuals should be random, not increasing or decreasing or following a discernible
shape with increasing response values).
To view one response residual plot in greater detail, select the response from
the drop-down list that appears when the Show button above the plots is
selected. To return to all response plots, select All Responses from Show
drop-down list.

12. Click the Residual Frequency tab. Additional plots appear.
13. Review the residual frequency plots for each response. The residual frequency
plots present the residuals (the difference between the actual and predicted values
for all error sample points for each response) as a frequency of occurrence, from 0
to the maximum residual. These plots allow the distribution of the residuals to be
reviewed (are more of the residuals close to 0 or closer to the maximum residual,
constant across the range of residuals or is there a peak, etc.).
To view one response residual frequency plot in greater detail, select the
response from the drop-down list that appears when the Show button above the
plots is selected. To return to all response plots, select All Responses from
Show drop-down list.

15. Click the Total Error tab. Some bar charts appear.
16. Review the total error bar charts. This tab displays the total error for all responses
in the form of a bar chart. The data in the top graph is the same as the data
presented numerically in the response table to the left. The second bar chart
(bottom) displays the standard deviation of the errors (standard deviation of the
differences between the actual and predicted values) for all error sample points.
This plot gives an indication of the spread of the error across the sample range for
each response.
For more information on the results displayed in this subtab, see “Understanding
the Results” on this page.
Understanding the Results

The results presented on the Error Analysis subtab - the numerical error values from
the error plug-ins and the visual representations of the approximation error - are used to
review the approximation prediction capabilities and assess the usability of the
approximation model as a surrogate for the component(s) which it approximates.

If the approximation quality is deemed unacceptable for one or more responses, a new
approximation can be created using the following suggestions:
Higher order RSM, or change to RBF approximation model type. The design space
may be more nonlinear than the selected approximation model type.
Increased number of sample points. A highly nonlinear design space may require a
larger number of points than the default or previously selected number of sampling
points to approximate the space accurately.
Decreased range of inputs. A highly nonlinear and high dimensional space may be
very difficult to approximate over a large range (or may require an impractical
number of sample points). Reducing the sample range can improve the ability to
approximate the space with sufficient accuracy.
Viewing Approximation Data After

Initialization
Once you have defined an approximation and initialized it, you have the ability to
access the information that appears immediately following the initialization. This
information includes data points, error analysis points, coefficient data, as well as
additional options. You can also export data to create another approximation.
To view approximation data:
Gateway.
If the “No Data To Display” message is displayed, then your approximation has
not been initialized. For more information, see “Initializing an Approximation,” on
page 179.
component name.

Viewing Approximation Data After Initialization 219
4. Click the View Data subtab. The approximation information is displayed.
5. Perform any of the following actions, as desired:
Click the Data Points subtab to view the values for input and output
parameters for each sample point.
Click the Error Analysis Points subtab to view the values for input and output
parameters for each error analysis point. For more information, see “Analyzing
Approximation Errors,” on page 211.
Click the Log Messages subtab to view all log messages associated with the
initialization. You can filter the log messages using the Log Filter drop-down
list. For more information on the different log levels, see “Setting Gateway
Note: Log messages are only available immediately after initialization.

Click the Coefficients Data subtab to view the resulting coefficients
calculated from generating the approximation.

Click the Export... button to save either your data points, error points, data and
error points combined, or coefficient data to a text file for viewing in another
program. You can also save the information as a separate Approximation
component. When you select this option, you save the component as a model
(*.zmf) file and the coefficients data as a text file. This text file is then used as
the data file for the Approximation component. For more information on using
this component, refer to the Isight Component Guide.
You can only save one set of points at a time. If you save the coefficient data,
you can also use it when creating another approximation. For more
information, see “Creating an Approximation Using a Previously Saved File,”
on page 169.
Click the Clear Data button (and confirm the operation by clicking Yes on the
warning message that appears) to delete the current initialization data.
Saving an Approximation
Approximations created in the Runtime Gateway are not automatically saved to the
Isight model. You must manually save the model using the save features on the
Runtime Gateway menu and toolbar. For more information, see “Saving a Model,” on
page 27.
Once you save a model that contains the approximations created using the Runtime
Gateway, you can access these approximations by either directly accessing the
Runtime Gateway or by accessing the Runtime Gateway through the Design Gateway.
These approximations are also viewable and fully manipulated directly from the
Design Gateway.

Deleting an Approximation 221
Deleting an Approximation
If you no longer have need for an approximation that is attached to a component, you
can permanently remove it from Isight.
Note: If you want to disable an approximation and prevent it from executing at

runtime, you can simply deactivate that approximation. For more information on this
option, see “Using Approximations at Runtime,” on page 177.
To delete an approximation using the wizard:

Gateway.
component name. The approximation information is displayed.

name of the approximation (as it appears in the list) is defined when the
approximation is created. A warning message appears.
5. Click OK. The approximation is deleted, and is no longer accessible from the
Approximations dialog box.
Note: You can also delete approximations created in the Runtime Gateway using
the Design Gateway. For more information, refer to the Isight User’s Guide.

223
3 Using Graphs, Tables, and Other

Data Analysis Tools
This chapter discusses using the Runtime Gateway graph and table options, as well as
other data analysis tools that are available. Collectively, these items are known as
visuals. The Engineering Data Mining, Correlation Map, two-dimensional Scatter
Plots, and Taguchi Main Effects Viewer tools are also discussed. The chapter is divided
into the following topics:

“Using Data Sampling with Graphs, EDM, and 2D Scatter Plots,” on page 224
“Understanding the Graphs Overview Area,” on page 226
“Using Graphs,” on page 227
“Using Tables,” on page 251
“Using the Engineering Data Mining Tool,” on page 267
“Using the Correlation Map,” on page 273

“Using the Two-dimensional (2D) Scatter Plots,” on page 279
“Using the Taguchi Main Effects Viewer,” on page 283

224 Chapter 3 Using Graphs, Tables, and Other Data Analysis Tools
Introduction
This section describes the graph and table options available in the Runtime Gateway.
Graphs and tables are collectively known as visuals. It also describes special visual
including Engineering Data Mining (EDM), which can be used to view results
information for models that use the NSGA-II optimization technique, as well as the
Correlation Map tool, two-dimensional (2D) scatter plots, and the Taguchi Main
Effects Viewer.
Graphs and tables can be viewed and created using the Graphs Overview area or the
Graphs tab. You can also detach the Graphs tab as a separate window by selecting
Graphs/Graphs Popout from the View menu.
Using Data Sampling with Graphs, EDM, and

2D Scatter Plots
If you are working with a complex model that has many runs, you can limit the number
of runs that display in graphs, the EDM, and 2D scatter plots. Therefore, if the number
of runs available to display exceeds the limit specified, the graph will begin uniform
sampling of the data to stay within the limit. For more information on this Preference
option, see “Setting Gateway Preferences,” on page 43.

Using Data Sampling with Graphs, EDM, and 2D Scatter Plots 225
If you have set a limit for the number of runs included in a graph, the graph will appear
with a yellow background as shown below.
Clicking the Sampled data button in the left top corner of the graph allows you to
change the number of runs appearing in the graph. The number you enter in the
Sampled data dialog box resets the Preference option. Your graphs will be
automatically updated and the Preference option will reflect the value you just entered.
Similarly, if you are viewing the EDM and/or 2D scatter plots, they will also have a
yellow background and Sampled data button.
Note: Each point in multiline/overlay graphs (e.g., EDM and history graphs with
overlay), counts against the limit. Therefore, data sampling begins much sooner than
with more simple graphs. For example, a history graph showing 10 parameters on one

graph, when there are 100 runs requires the points in the graph to be 1000 or higher to
not begin data sampling.
Understanding the Graphs Overview Area

The Graphs Overview area, which appears on the right side of the Runtime Gateway
when certain tabs are being viewed, provides the following two functions:
Automatically generates preview graphs when parameters are selected. Parameters

can be selected either directly on the Parameters tab or by using the Model
Explorer area on the left side of the Runtime Gateway. The type of graph used as
the preview graph is appropriate to the currently selected tab, and in some cases the
number of parameters selected.
Allows you to create customized graphs and tables while viewing the data on other
tabs. When you create a graph or table, it appears below the preview graph. These
graphs are also added to the Graphs tab.
In general, this feature allows you to view data and graphs and tables at the same time.
Parameter information selected on the History tab is highlighted on the preview graph
or on any created graph or table.
Note: You can close this feature by clicking the button. It can be re-opened by
selecting Graphs/Graphs Overview from the Runtime Gateway View menu.
When working with the Taguchi Robust Design component, you also have access to
the Taguchi Main Effects View from the Graphs Preview area. For more information,
see “Using the Taguchi Main Effects Viewer,” on page 283.

Using Graphs 227
Using Graphs
Graphs can be created prior to execution on the Design Gateway (refer to the Isight
User’s Guide) or following execution (as described in this section). Graphs are updated
periodically during execution. However, it is only after execution is complete that all
relevant information is displayed in a graph.
Graphs created on the Design Gateway Graphs Templates tab are saved with the
model. Graphs created on the Runtime Gateway Graphs tab are not saved with the
model. You can save the model on the Runtime Gateway after creating graphs.
“Creating a Graph for a Component,” on page 228

“Using Specialized Graphs,” on page 235
“Updating an Existing Graph,” on page 238
“Changing Graph Options,” on page 239
“Viewing Graph Information,” on page 240
“Exporting Graph Data,” on page 249
“Copying a Graph,” on page 250

“Normalizing a Graph,” on page 250
“Deleting Graphs,” on page 251

Creating a Graph for a Component

Graphs are created using the Graphs tab on the Runtime Gateway.
To create a graph:
1. Select the component you want to graph on the left side of the Runtime Gateway;
then, click the Graphs tab.
The contents of the tab appear with the selected component’s name displayed at
the top of the tab. The example displays the Copy to Arrays component in the
I-Beam model.
Important: You must select the proper component on the left side of the Runtime
Gateway (the Model Explorer section) prior to creating a graph.
2. Verify that the proper page is selected at the bottom of the tab. By default, Page 1 is
used. However, you can create multiple pages using the <New> tab.

Using Graphs 229
3. Click the Graph button . The Graph Creation Wizard appears.
In this example, we will choose the Contour Graph option.
Note: Components such as DOE, Optimization, and Monte Carlo have specialized
graphs options in addition to a list of general graphs. If you are graphing one of
these components, you may select a component-specific graph or general graph
using the embedded tabs. For more information on these component-specific
graphs, see “Using Specialized Graphs,” on page 235.
4. Select the type of graph you want to use. The following options are available on
the General tab:
Area Graph. Creates a two-dimensional area graph using two or more

parameters. Plots one X value against one or more Y values.
Array Graph. Creates a two-dimensional graph using two or more array

parameters. Plots one X array against one or more Y arrays.
Contour Graph. Creates a three-dimensional contour graph using three

parameters. Displays color-coded isosurfaces or isobars.
Correlation Graph. Creates a bar graph using one parameter. The bars
represent the correlation value of another parameter to the selection parameter.
This graph provides a quick look at the most influential/influenced parameters
surrounding the selected parameter.
Cumulative Frequency. Creates a cumulative frequency using one parameter.

The parameter is analyzed over its range and a cumulative frequency

distribution is calculated. This value is similar to the probability except that

there is no guarantee that the data represents the probability distribution.
Frequency Graph. Creates a frequency graph using one parameter. The data
is analyzed over its range and divided into frequency bars. This value is similar
to probability except that there is no guarantee that the data represents the
probability distribution.
History Graph. Creates a history graph using one or more parameters. The Y
axis displays one or more parameters, and the X axis is a monotonically
increasing integer value representing the chronological order.
Image Graph. Allows you to view file parameters which contain *.gif, *.bmp,
*.jpg, *.jpeg, or *.png files. In other words, models which produce image files
that represent the design can be viewed in the Runtime Gateway.
Line Graph. Creates a two-dimensional line graph using two or more

parameters. Plots one X value against one or more Y values.
Parallel Coordinate Graph. Creates a parallel coordinate graph using one or

more parameters. Along the X axis each variable is assigned a position, each
value of that parameter is displayed on a logic axis above that point. Along the
Y axis the values of a given run are strung together with a line connecting all
the dots above each parameter value.
Scatter Plot 2D Graph. Creates a two-dimensional scatter plot graph using

two or more parameters. Plots with no connecting lines.
Scatter Plot 3D Graph. Creates a three-dimensional scatter plot graph using

three or more parameters. Plots with no connecting lines.
Surface Graph. Creates a three-dimensional surface graph using three

parameters. Used to show the topology relationship between the parameters
chosen.
Value Graph. Creates a value graph using one or more parameters. The Y axis
shows the value of one or more parameters, while the X axis displays a value's
rank in the overall group of values. The values are sorted in order of increasing
value, and show the distribution of the sampling over a range.
Note: Additional graphs are available with some components. For information on
these component-specific graphs, see “Using Specialized Graphs,” on page 235.

Using Graphs 231
5. Click Next. The Choose Parameters information appears.
6. Click the parameters that you want to graph. You can select parameters
individually or in groups using the Select drop-down list, which allows you to
automatically select all input parameters, output parameters, local parameters, or
every listed parameter.
7. Click the Overlay (Multi-line) check box if you want to create a single graph with
multiple data sets (one for each parameter). If this option is not selected, a separate
graph is created for each selected parameter. This option is not available for all
graphs.
8. Click Next. The graph options information appears.

9. Alter any of the following options in the Options area, as desired:
Logarithmic X Axis and Logarithmic Y Axis. These options allow you to

change the numeric scaling of either axis to be logarithmic (i.e., in magnitudes
of 10). Using these options may assist you in seeing all the data points when
the data in the graph is displayed in varying degrees of magnitude.
Show grid lines. When selected, this option allows the graph to display grid
lines.
Note: These options will vary depending on the type of graph you selected. They
will also not appear for some graph types.
10. In the Legend Options area, click the Show Legend check button if you’d like a
legend displayed with your graph; then, select the legend’s location with respect to
the graph.
11. Set the Include Failed Runs check box. When selected, any failed runs are
included in the graph.
12. Click Next. The Creation Summary information appears.
Note: Some specialized graphs have additional options. For more information on
these options, see “Using Specialized Graphs,” on page 235.
13. Review the information on the Summary tab.

Using Graphs 233
14. Click the Job Selection tab. The contents of the tab appear.
15. Determine which job information will be used to create the graph. You can use the
recently executed job (Active Job) or all jobs that are loaded in the current session
(All Loaded Jobs). For more information on using jobs, see “Working With Jobs,”
on page 56.

16. Click Finish. Your graph(s) is added to the Runtime Gateway.
Note: If your graph appears with a yellow background and a button in the top
left corner, then only a limited number of runs have been included in the graph. For
more information, see “Using Data Sampling with Graphs, EDM, and 2D Scatter
Plots,” on page 224.

Using Graphs 235
Using Specialized Graphs

The following sections list the specialized graphs available in the Runtime Gateway.
Monte Carlo
Cumulative Distribution. Creates a Cumulative Distribution Graph for the
specified Random Variables and/or Responses.
Pareto Plot. Creates a graph that shows the effect of a random variable or set of
random variables on a response by plotting the relationship as determined by
regression analysis of the data set. It is an ordered bar chart that displays the effects
of each random variable on a selected response, where the random variables are
listed in order of largest effect to smallest effect. Blue bars indicate positive effects
on responses, while red bars indicate negative effects. Therefore, this plot can be
used to identify the random variables with the most significant effects on, or largest
contribution to, the variability of the responses. The graph wizard allows you to set
the following additional options for this type of graph:
Regression Analysis Order. You can set this option to either Linear or
Quadratic (if the data allows for this setting).
Show bars as. You can set the bars in the graph to show either absolute values
or actual values.
Terms to show. You can specify the terms to show by either selecting all
terms, those within a certain range, or those in relation to a specific percentage.
For Pareto plot reference information, see “Pareto Plot Reference Information,” on
page 331.
Probability Distribution. Creates a Probability Distribution Graph for the

specified Random Variables and/or Responses.
Scatter Plot 2D. Creates a two-dimensional Scatter Plot Graph using two
parameters. No lines connect the values.
Scatter Plot 3D. Creates a three-dimensional Scatter Plot Graph using three
parameters. No lines connect the values.

Design of Experiments (DOE)

Interaction Graph. Creates a graph that is a plot showing the main effect of a
given factor on a response at each level of another factor. Lines that are parallel
indicate that the two factors have no interaction effect on the response (the more
non-parallel, the greater the interaction).
Main Effects Graph. Creates a graph that shows the effect of a factor or set of
factors on a response by plotting the relationship as determined by regression
analysis of the data set. The graph wizard allows you to set the following
additional options for this type of graph:
Fit type. Specify this option as either Continuous or Piecewise.

Main Effect Style. If multiple factors are selected, and the Overlay
(multi-line) option is selected on the parameter selection page, click the Side
by side factor effects to view the effect of the factors on the response along
side each other in the same graph. If not selected, the lines representing the
effects will be overlaid on top of each other.
Pareto Plot. Creates a graph that shows the relative effects of the factors on a
response as determined by regression analysis of the data set. It is an ordered bar
chart that displays the effects of each factor on a selected response, where the
factors are listed in order of largest effect to smallest effect. Blue bars indicate
positive effects on responses, while red bars indicate negative effects. Therefore,
this plot can be used to identify the factors with the most significant effects on, or
largest contribution to the responses. The graph wizard allows you to set the
following additional options for this type of graph:
or actual values.
page 331.

Using Graphs 237
SDI
SDI Scatter Plot. Creates a two-dimensional Scatter Plot Graph using two SDI
parameters. Each SDI iteration is shown in a different color. No lines connect the
values.
Six Sigma
Pareto Plot. Creates a graph that shows the effect of a random variable or set of
random variables on a response. It is an ordered bar chart that displays the effects
of each random variable on a selected response, where the random variables (or
factors if DOE analysis is used) are listed in order of largest effect to smallest
effect. Blue bars indicate positive effects on responses, while red bars indicate
negative effects. Therefore, this plot can be used to identify the random variables
with the most significant effects on, or largest contribution to, the variability of the
responses. The graph wizard allows you to set the following additional options for
Pareto Plots:
or actual values.
When Reliability Analysis technique is used in Six Sigma, the random variable
effects shown in the pareto plot are based on gradients of the random variables
with respect to the selected response. For Monte Carlo simulation and DOE, the
relationship is determined by regression analysis of the Six Sigma data set.
page 331.
Six Sigma Graph. For selected Six Sigma responses, this graph displays a normal
distribution. This distribution is generated using the calculated mean and standard
deviation values for this response and displays, the lower and/or upper bound
values, the number of standard deviations between the bounds and the mean value
(if the response has bounds defined), and the total quality level. The Six Sigma

graph is available before and after execution; however, it will be empty before
execution, and is updated after execution.
Note: All Monte Carlo and DOE graphs are available if Monte Carlo Sampling or DOE
analysis is used.

Taguchi Dynamic Response Graph. This graph applies to a single selected
dynamic response, and to a single design point (control experiment). The control
run number is specified on the graph itself using the drop-down menu under the
graph. The graph displays the relationship between a response/metric and the
signal factor. A linear fit to the noise/signal data is shown, along with the actual
data, for the selected control experiment.
Taguchi Main Effects Graph. This graph displays the average effect on the
selected response of each factor level for each factor selected, and for the Taguchi
metric selected. You can also view main effects data interactively as described in
“Using the Taguchi Main Effects Viewer,” on page 283.
Updating an Existing Graph

Once a graph has been created, you can update it, including changing the parameters
used to create the graph, general options, legend options, and job selection information.
To update an existing graph:
1. Right-click the graph you want to update; then, select Reconfigure from the menu
that appears. The Graph Reconfigure Wizard appears.
2. Update any of the following settings, as desired:
Parameters used by the graph

Options such as logarithmic axes, grid lines, and legends
Which jobs to use for data to display in the graph (if multiple jobs have been
executed)
For more information on these options, see “Creating a Graph for a Component,”
on page 228.

Using Graphs 239
You can also use the filtering options available at the bottom of the tab. For more
information on these options, see “Filtering Data,” on page 92.
Changing Graph Options

Once a graph is created, you can adjust certain options without recreating the graph,
including the legend, its location, and the way parameter names are displayed.
To update an existing graph:
1. Right-click the graph you want to update; then, select Edit Options from the menu
that appears. The Options Editor dialog box appears.
2. Alter any of the following options in the Options area, as desired (not all options
are available for all graphs):
Logarithmic X Axis and Logarithmic Y Axis. These options allow you to

change the numeric scaling of either axis to be logarithmic (i.e., in magnitudes
of 10). Using these options may assist you in seeing all the data points when
the data in the graph is displayed in varying degrees of magnitude.
Show grid lines. When selected, this option allows the graph to display grid
lines.
Note: These options will vary depending on the type of graph you selected. The
area containing these options is not displayed in the previous example (since they
are not available for a Contour Graph).

3. In the Legend Options area, click the Show Legend check box if you’d like a
legend displayed with your graph; then, select the legend’s location with respect to
the graph.
4. Set the Include Failed Runs check box. When selected, any failed runs are
included in the graph.
5. Click OK to save your changes and update the graph.
Viewing Graph Information

The following information concerning the customizing options for graphs is contained
in this section:
“Manipulating Graphs,” on page 241
“Viewing Graph Data Based on Run Number,” on page 241
“Viewing Data Set Information,” on page 243

“Understanding Run Grading in Graphs,” on page 245
“Selecting Points in Graphs,” on page 246
“Viewing File Parameters From a Graph,” on page 247
“Using Zooming Options,” on page 247
“Resizing and Aligning Graphs,” on page 248
“Rotating Graphs,” on page 248

Using Graphs 241
Manipulating Graphs
You can move graphs around, display them in separate windows, and enlarge them. To
manipulate graphs in this manner:
To move a graph: Click the graph and drag your mouse. You can move the graph to
any location on the current page.
To display a graph in a separate window: Click the button on the graph. A new
window, which is independent of the Runtime Gateway, is created.
To enlarge a graph: Click any edge of the graph window, and drag it with your
mouse.
Viewing Graph Data Based on Run Number

You can scroll through the graph information based on individual run numbers using
the Run Number scroll bar. This scroll bar is located at the bottom of the Runtime
Gateway, beneath the graph visualization area.

An example of the Run Number scroll bar is shown below.
You can perform any of the following actions with the scroll bar and its associated
options, as desired:
Use the and buttons to move forward or backward by one run

number.
Determine the behavior of the scroll bar when using the control. When the
icon is displayed, the displayed run number is not updated until the control is
clicked, moved, and released. When the icon is displayed, the displayed run
number is updated as the control is moved. Clicking the current icon changes
the setting to the other option.

Using Graphs 243
Use the text box to the right of the scroll bar to determine a specific run number to
display.
Click the button to have the Runtime Gateway automatically scroll

through each run number, starting with the one currently selected for viewing. You
can stop this automation at any time using the button.
Click in the box to automatically scroll as new data arrives. This option is
turned off by default. This is useful when you want to look at one particular run’s
data.
Viewing Data Set Information

When a component executes within multiple nested process components, there are
multiple Data Sets that can be used to present the results for that component. For
example, consider a model that executes a DOE (100 runs) study around 5 different
baseline points (managed by a Loop) as shown below.
When reviewing the history of the Simcode results, typically you will want to see the
results relative to each execution of the DOE (a set of 100 runs). In this case, “Data

Set” controls are provided for selecting and navigating through the multiple data sets (5
different sets in this example).
As mentioned, Data Sets are created when a process component (Optimization, DOE,
etc.) is placed within another process component’s workflow. Each run of the outer
process component produces a different Data Set for each run of the inner process
component. It should be noted that all graphs for DOE and Monte Carlo are only valid
for a given single Data Set.
You can scroll through the available Data Sets using the Data Set scroll bar, which
appears below the graph visualization area, and above the Run Number scroll bar. This
area also tells you the number of total Data Sets available, and lets you easily change
the displayed Data Set(s).
Note: The Data Set scroll bar is not visible if only one Data Set exists.
An example of the Data Set scroll bar is shown below.

Using Graphs 245
Use the and buttons to move forward or backward by one Data

Set.
Use the text box to the right of the scroll bar to determine a specific Data Set
number to display.
Use the button to the right of the scroll bar to determine which Data Set to display.
All. This option shows all Data Sets simultaneously. Some graphs ignore this
setting because they are only capable of showing the data for one Data Set.
Particular Data Set. This option shows only data from the selected Data Set.
Choose. This option allows you to manually select a Data Set by directly
entering the number is the text box that appears when the option is selected.
You can lock and unlock the postprocessing graphs, which impacts which Data
Sets are displayed. When the graphs are locked (the icon is displayed), graphs
that are capable of displaying all Data Sets simultaneously will ignore additional
Data Set selections. When unlocked (the icon is displayed), the graphs display
the selected Data Set. You can change between locked and unlocked graphs by
clicking the currently displayed icon.

through each Data Set, starting with the one currently selected for viewing. You
Understanding Run Grading in Graphs

If you have used the problem formulation feature with your model (either when the
model was created in the Design Gateway or directly in the Runtime Gateway), the
graphs use specific colors to display the run grading for the graphed points, as
appropriate.

The following colors are used for grading runs displayed in the graphs:
Red represents an infeasible design point. Keep in mind that the infeasibility might
be due to violated bounds on parameters other than those shown in the given graph.
Green represents the best design point (based on calculated objective). This point
is always a feasible point (i.e., no violated constraints).
Yellow represents the best design point but a point that is infeasible. This color is
used when there is at least one objective defined and either there are no feasible
points found, or the best feasible point (colored green) has a worse calculated
objective and penalty. In short, this point might be a better design even though it is
slightly infeasible.
If the parameter being graphed has lower/upper bounds defined for it, blue/red
lines will be drawn to represent these bounds (for appropriate graph types) so that
the design points can be visually evaluated with respect to those bounds.
For more information on setting problem formulation options using the Runtime
Gateway, see “Viewing and Editing Problem Formulation Settings,” on page 91.
Selecting Points in Graphs

Numerous options are available for selecting points on a graph. These options are
displayed to the left of the graph display area (between the graphs and the Model
Explorer). Selecting a point or points on one graph automatically highlights the same
point on all other graphs and corresponding rows on tables (when applicable).
Note: Not all options are available with each type of graph. If the options are not
available with the currently selected graph, the buttons are disabled.
. This option allows you to highlight a specific point with crosshairs.
. This option allows you to highlight a specific point with a color. You can
specify the color by clicking the button.
. This option allows you to highlight a range of points with a color. You can
specify the color by clicking the button.

Using Graphs 247
. This option allows you to pan a graph. Once selected, simply click a graph and
move your mouse. The graph is moved in a similar manner.
. This option allows you to zoom in on a selection within a graph. Once this
button is clicked, clicking and dragging within a graph creates a subarea, which is
outlined. Releasing the mouse button zooms in on the specified area. You can reset
any zoom using the button.
. This option allows you to rotate a three-dimensional graph. Once selected,

simply click a graph and move your mouse. The graph is rotated in a similar
manner.
. This option, when active, allows you to use the buttons described above while
keeping graphs opened in separate dialog boxes in the foreground.
Viewing File Parameters From a Graph

If a File parameter is associated with a point on a graph, you can view the File
parameter directly from the graph. Right-click the point; then, select Files from the
menu that appears. A list of File parameters associated with the point are shown. Select
the file you want to view. The File parameter contents are displayed in a separate
dialog box. If more than five File parameters are associated with the point, you can also
select the More... option to view all of the associated File parameters.
Using Zooming Options

Some graphs give you the ability to focus on sections of data using zoom options.
These zoom options are not available with all graphs. If the options are not available
with the currently selected graph, the buttons are grayed out.
The following zoom options are available with some graphs:
. This option zooms in on the currently selected graph.
. This option zooms out on the currently selected graph.
. This option resets a graph zoom to its original orientation. You can also
right-click the graph; then, select Reset from the menu that appears.

Resizing and Aligning Graphs

You can automatically resize all graphs currently created. You can also automatically
align graphs based on the tiled layout. To resize and align graphs:
. This option allows you to increase the size of every graph displayed on the
current tab. Any tables are also increased.
. This option allows you to decrease the size of every graph displayed on the
current tab. Any tables are also decreased.
. This option allows you to reset all graphs to their default size. Any tables are
also reset.
. This option allows you to align graphs in a tiled layout. For example, if you
create two graphs, and one graph is placed slightly below the other graph, this
button brings the top of both graphs into line. Any tables are also aligned.
Rotating Graphs
You can rotate three-dimensional graphs to view them from different angles. To rotate
a three-dimensional graph:
. This option allows you to rotate along the x-axis. The number in the
corresponding text box represents the current position of the axis in degrees.
. This option allows you to rotate along the y-axis. The number in the
. This option allows you to rotate along the z-axis. The number in the
. This option resets any custom rotation to the original orientation.

Using Graphs 249
Exporting Graph Data

You can export graph data from the Runtime Gateway to an image file, a text file, or to
Microsoft Excel.
To export graph data:

1. Right-click the graph whose data you want to export. A menu appears.
2. Click the Export option; then, select one of the following options:
Export to Image. This option allows you to save the graph as an *.jpeg, *.jpg,
or *.png file, based on the extension you provide along with the file name.
Simply navigate to the directory that will store the image file, and type a file
name, with proper extension, in the File Name text box; then, click Save. The
file is saved and can be accessed with any image viewing software.
Export to Text File. This option allows you to save the graph data as
numerous types of text files, based on the extension you provide along with the
file name. Simply navigate to the directory that will store the text file, and type
a file name, with proper extension, in the File Name text box; then, click Save.
The file is saved and can be accessed with the text editor of your choice.
Export to Excel. This option immediately exports the graph to an Excel

spreadsheet and displays it. From this point, you can manipulate the graph, as
desired, using Excel. However, it should be noted that there are some
limitations with regard to exporting graph data to Excel. These limitations are
as follows:
• Excel has a 64 kilobyte row limit which may impact your ability to export a
graph.
• Array Graphs: Excel evenly spaces the data points on the x axis for this
graph type.
• 3D Scatter Plots: Excel does not support this graph type. If attempted, the
data points are exported, but a graph is not created.

Copying a Graph
You can copy both the image of a graph and the data contained within a graph, and use
either in an application outside of the Runtime Gateway.
To copy a graph:
1. Right-click the graph you want to copy. A menu appears.
2. Click Copy; then, select one of the following options:
Copy Image. This option allows you to copy the graph exactly as it appears in
Copy Data. This option allows you to copy the data displayed in the graph and
then use it in another application (such as Excel), where it is presented in its
raw format.
Normalizing a Graph
You have the option of normalizing a Parallel Coordinate graph. This feature scales all
of the parameter ranges from 0...1.
For example, if you have two variables, one whose value range is 700 to 2000 and
another that is -3.1 to -5.2, you can see these values as a percentage of the range. When
this feature is not used, the graph range is from -5.2 to 2000, and all of the first
parameter’s lines will be near the top of the graph, at the same time, the second
parameter value appears to be a single point at the bottom of that scale.
To normalize a Parallel Coordinate graph:
1. Right-click the graph you want to normalize. A menu appears.
2. Click the Normalize option. The graph is updated.
3. (optional) Return the graph to its previous state by right-clicking it; then, select
Denormalize from the menu that appears.

Using Tables 251
Deleting Graphs
To delete a graph, simply click the button on the graph itself. You can also use
the button to the left of the graph display area to delete the currently selected graph
or multiple graphs.
Using Tables
Tables can be created prior to execution on the Design Gateway (refer to the Isight
User’s Guide) or following execution (as described in this section). Tables are updated
periodically during execution. However, it is only after execution is complete that all
relevant information is displayed in a table.
Tables created on the Design Gateway Graphs Templates tab are saved with the model.
Tables created on the Runtime Gateway Graphs tab are not saved with the model.
“Creating a Table for a Component,” on page 252

“Updating an Existing Table,” on page 258
“Viewing Table Information,” on page 259
“Customizing a Table,” on page 264
“Exporting Table Data,” on page 266
“Copying Table Data,” on page 266
“Deleting Tables,” on page 267

Creating a Table for a Component

Tables are created using the Graphs tab on the Runtime Gateway.
To create a table:
1. Select the component whose data you want to add to a table on the left side of the
Runtime Gateway; then, click the Graph tab. The contents of the tab appear, with
the selected component’s name displayed at the top of the tab.
Important: You must select the proper component on the left side of the Runtime
Gateway (the Model Explorer section) prior to creating a table.
2. Verify that the proper page is selected at the bottom of the tab. By default, Page 1
is used. However, you can create multiple pages using the <New> tab.

Using Tables 253
3. Click the Table button . If you have chosen a component that has the
specialized tables option, the Table Creation Wizard appears, and the Table
Chooser information is displayed. If no specialized tables are available, the
component parameters are displayed. You should continue to step 6. In the
following example, Monte Carlo tables are displayed.
4. Select the type of table you want to create. Depending on the type of component
selected, the following options are available:
All Components
Parameters Table. This table is available for all components, and is created
by default if no other table options are available. It creates a table for the
selected parameters.
DOE
Coefficients Table. A table is created showing the coefficients calculated from

regression analysis on the data set for a given response.
Note: This table is also available for the Six Sigma component if DOE analysis
is used. For more information on configuring the Six Sigma component, refer
to the Isight Component Guide.

Monte Carlo
• Correlation Coefficients Table. A table is created containing linear

correlation coefficients for the Monte Carlo random variables and
responses.
Note: This table is also available for the Six Sigma component if Monte
Carlo Sampling is used. For more information on configuring the Six
Sigma component, refer to the Isight Component Guide.
• Probability Table. A Probability Table is created for the Monte Carlo
responses with limits specified.
• Response Percentiles Table. A table of response values at specified
percentiles for the reliability responses is created.
• Statistics Table. A Statistics Table for the Monte Carlo parameters is
created. The table includes mean standard deviation, variance, skewness,
kurtosis, range, minimum and maximum.
Six Sigma
• Reliability Table. This table is only available when the Six Sigma
component uses a Reliability Analysis technique. It displays the reliability
analysis results, along with a summary of the defining characteristics of the
reliability constraints. Included are: the reliability constraint parameter
name, the value of the constraint parameter at the point being analyzed (this
is the mean value of the constraint parameter), the bound type (lower bound
or upper bound), the value of the bound (constraint value), the reliability
index, and the actual reliability calculated during the reliability analysis.
If any reliability constraint has a lower and upper bound defined, the
combined reliability is also calculated and reported in both the results file
and in this table.

Using Tables 255
• Six Sigma Table. This table displays the Six Sigma plan results obtained
for output constraints. For each output constraint parameter, the table
includes the following: sigma level, probability of success, probability of
failure, and number of defects per million. The table is available only after
execution.
• Taguchi Response Summary Table. This table displays estimated
best/worst factor levels and Taguchi metric value for the selected
response/metric combination. Metric selections include S/N ratio,
sensitivity (nominal-is-best responses only), loss, mean, or variance for
static systems, S/N ratio or sensitivity for dynamic systems, and S/N ratio,
beta 1, beta 2, or beta 3 for dynamic-standardized systems. It displays the
estimated Taguchi metric value, if the best/worst factor levels were not a
control experiment point, and it also displays that actual value if
confirmation runs were specified as part of the Taguchi plan setup and
executed with the experiment points. The table also includes the best and
worst point included in the control matrix. The relative benefit/loss,
compared to the baseline design, is also displayed if the baseline design
was included in the Taguchi plan setup and executed with the experiment
points.
• Taguchi Results Table. This table displays the Taguchi metric results for
each control run for the specified response. For static system type, the
results include S/N ratio, sensitivity (nominal-is-best responses only), loss,
mean, and variance. For dynamic system type, the results include S/N ratio,
sensitivity, slope, total sum of squares due to linearity, sum of squares due
to error, and the error variance. For dynamic-standardized system type, the
results include S/N ratio, the three polynomial fit coefficients, beta 1, beta
2, and beta 3, the total sum of squares, the sum of squares due to the
proportional effect, the sum of squares caused by the interaction effect, the
sum of squares due to error, the error variance, and the noise error variance.
If the baseline design was executed, results are also displayed for the
baseline.

5. Click Next. The component parameters are displayed. If the Table Chooser screen
does not appear (as in step 3), this information is shown immediately after clicking
the Table button.
6. Verify that the desired parameters are visible. You can change the displayed
parameters using the Show Parameters For drop-down list.
7. Determine if you want file parameters included in your parameter selection (if you
use the Select drop-down list) using the Include Files check box.
8. Click the parameters that you want to include in the table. You can select
parameters individually or in groups using the Select drop-down list, which allows
you to automatically select all input parameters, output parameters, local
parameters, or every listed parameter.
Note: Which parameters are selected may be impacted by how you set the Include
Files option in step 7. For example, if you clear (unselect) this check box and select
All from the Select drop-down list, all parameter except displayed file parameter
are highlighted.

Using Tables 257
9. Click Next. The Creation Summary information is displayed.
10. Review the information on the Summary tab.

11. Click the Job Selection tab. The contents of the tab appear.

12. Determine which job information will be used to create the table. You can use the
recently executed job (Active Job) or all jobs that are loaded in the current session
(All Loaded Jobs). For more information on using jobs, see “Working With Jobs,”
on page 56.
13. Click Finish. Your table is added to the Runtime Gateway.
Updating an Existing Table

Once a table has been created, you can update it, including changing the parameters
used to create the table and job selection information.

Using Tables 259
To update an existing table:
1. Right-click the table you want to update; then, select Reconfigure from the menu
that appears. The Table Reconfigure Wizard appears.
2. Update any of the following settings, as desired:

Parameters displayed in the table
Which jobs to use for data to display in the table
For more information on these options, see “Creating a Table for a Component,”
on page 252.
You can also use the filtering options available at the bottom of the tab. For more
information on these options, see “Filtering Data,” on page 92.
Viewing Table Information

Once you create a table, you have several options available for viewing the
information. Proceed to one of the following topics for more details:
“Understanding Displayed Columns” on this page
“Selecting Points in Tables,” on page 260
“Sorting Table Data,” on page 260

“Filtering Table Data,” on page 260
“Viewing Table Data Based on Run Number,” on page 260
“Viewing Data Set Information,” on page 262
Understanding Displayed Columns

The first column in a table indicates if the run was successful. If the run is successful, a
symbol appears in the column. If the run was not successful, a symbol appears in
the column. If an approximation was executed instead of the actual component, a
symbol appears in the column. The next columns (before the parameter values) show
the run for each component. The components are shown in relation to one another. The
root is always run once.

Selecting Points in Tables

Selecting a point or points on one table (clicking a particular row) automatically
highlights the row corresponding to the same point on all other tables and
corresponding points on all other graphs (when applicable).
Sorting Table Data

Once a table has been created, you can sort the data it contains. You can sort in
ascending or descending order for any parameter by clicking that parameter’s column
header. The first click sorts in Ascending order. The second click sorts in Descending
order. A third click returns you to the original non-sorted option. The small arrow icons
to the right of the column headings shows you the current sorting option selected.
Filtering Table Data

If you are working with a large number of parameters in a table, and only want to view
certain subsets of those parameters, you can use the filter options to change the
displayed parameters. For more information on using this feature, see “Filtering the
Data,” on page 110.
Viewing Table Data Based on Run Number

You can scroll through the table information based on individual run numbers using the
Run Number scroll bar. This scroll bar is located at the bottom of the Runtime
Gateway, beneath the table visualization area.

Using Tables 261
An example of the Run Number scroll bar is shown below.
Use the and buttons to move forward or backward by one run

number.
Determine the behavior of the scroll bar when using the control. When the
icon is displayed, the displayed run number is not updated until the control is
clicked, moved, and released. When the icon is displayed, the displayed run
number is updated as the control is moved. Clicking the current icon changes
the setting to the other option.

Use the text box to the right of the scroll bar to determine a specific run number to
display.

through each run number, starting with the one currently selected for viewing. You
Click in the box to automatically scroll as new data arrives. This option is
turned off by default. This is useful when you want to look at one particular run’s
data.
Viewing Data Set Information

When a component executes within multiple nested process components, there are
multiple Data Sets that can be used to present the results for that component. For
example, consider a model that executes a DOE (100 runs) study around 5 different
baseline points (managed by a Loop) as shown below.
When reviewing the history of the Simcode results, typically you will want to see the
results relative to each execution of the DOE (a set of 100 runs). In this case, “Data

Using Tables 263
Set” controls are provided for selecting and navigating through the multiple data sets (5
different sets in this example).
As mentioned, Data Sets are created when a process component (Optimization, DOE,
etc.) is placed within another process component’s workflow. Each run of the outer
process component produces a different Data Set for each run of the inner process
component. It should be noted that all graphs for DOE and Monte Carlo are only valid
for a given single Data Set.
You can scroll through the available Data Sets using the Data Set scroll bar, which
appears below the graph visualization area, and above the Run Number scroll bar. This
area also tells you the number of total Data Sets available, and lets you easily change
the displayed Data Set(s).
Note: The Data Set scroll bar is not visible if only one Data Set exists.
An example of the Data Set scroll bar is shown below.

Use the and buttons to move forward or backward by one Data

Set.
Use the text box to the right of the scroll bar to determine a specific Data Set
number to display.
Use the button to the right of the scroll bar to determine which Data Set to display.
All. This option shows all Data Sets simultaneously. Some tables ignore this
setting because they are only capable of showing the data for one Data Set.
Particular Data Set. This option shows only data from the selected Data Set.
Choose. This option allows you to manually select a Data Set by directly
entering the number is the text box that appears when the option is selected.
You can lock and unlock postprocessing tables, which impacts which Data Sets are
displayed. When the tables are locked (the icon is displayed), tables that are
capable of displaying all Data Sets simultaneously will ignore additional Data Set
selections. When unlocked (the icon is displayed), the tables display the
selected Data Set. You can change between locked and unlocked tables by clicking
the currently displayed icon.

through each Data Set, starting with the one currently selected for viewing. You
Customizing a Table
The following information concerning the customizing options for tables is contained
in this section:
“Manipulating Tables,” on page 265
“Resizing and Aligning Tables,” on page 265

Using Tables 265
Manipulating Tables
You can move tables around, display them in separate windows, and enlarge them. To
manipulate tables in this manner:
To move a table: Click the table and drag your mouse. You can move the table to
any location on the current page.
To display a table in a separate window: Click the button on the table. A new
window, which is independent of the Runtime Gateway, is created.
To enlarge a table: Click any edge of the table window, and drag it with your
mouse.
Resizing and Aligning Tables

You can automatically resize all tables currently created. You can also automatically
align tables based on the tiled layout. To resize and align tables:
. This option allows you to increase the size of every table displayed on the
current tab. Any graphs are also increased.
. This option allows you to decrease the size of every table displayed on the
current tab. Any graphs are also decreased.
. This option allows you to reset all tables to their default size. Any graphs are
also reset.
. This option allows you to align tables in a tiled layout. For example, if you
create two tables, and one table is placed slightly below the other table, this button
brings the top of both tables into line. Any graphs are also aligned.

Exporting Table Data

You can export table data from the Runtime Gateway to either a text file or to
Microsoft Excel.
To export table data:

1. Right-click the table whose data you want to export. A menu appears.
2. Click the Export option; then, select one of the following options:
Export to Text File. This option allows you to save the table data as numerous
types of text files, based on the extension you provide along with the file name.
Simply navigate to the directory that will store the text file, and type a file
name, with proper extension, in the File Name text box; then, click Save. The
file is saved and can be accessed with the text editor of your choice.
Export to Excel. This option immediately exports the table to an Excel

spreadsheet and displays it. From this point, you can manipulate the table, as
desired, using Excel.
Copying Table Data

You can copy either portions of a table or the entire contents of a table for use in an
application outside of the Runtime Gateway.
To copy table data:

To copy the entire contents of the table; proceed to step 3.
To copy portions of the table; proceed to step 2.

2. Select the table row(s) that you want to copy.

Using the Engineering Data Mining Tool 267
3. Right-click the table whose data you want to copy. A menu appears.
4. Click Copy; then, select one of the following options, based on your choice in
step 1:
Copy Selected. This option allows you to copy only specified rows in the
table.
Copy All. This option allows you to copy all of the data in the selected table.
Once copied, table data can be used in another application (such as Excel), where it
is presented in its raw format.
Deleting Tables
To delete a table, simply click the button on the table itself. You can also use the
button to the left of the table display area to delete the currently selected table or
multiple tables.
Using the Engineering Data Mining Tool

The Isight Engineering Data Mining (EDM) tool provides an effective way to view
many designs (inputs and corresponding outputs) and view the relationships and trends
among those designs. More specifically, the tool provides post-processing
functionality for multi-objective optimization by analyzing the results and effectively
visualizing Pareto solutions and sorting (screening) the data interactively. The
multi-objective techniques provided in Isight are AMGA, NSGA-II, and NCGA. For
more information on these techniques, refer to the Isight Component Guide.
The tool allows you to create and manipulate two main types of graphs:
Multi-variable and multi-response plots, also called parallel coordinate graphs.

These plots facilitate Multi-Criteria Decision Making. All of the responses can be
compared on one graph.
Two-dimensional scatter plots. These plots show two-dimensional correlations

between inputs and outputs (on the 2D Scatter Plots subtab). In both types of

graphs, Pareto solutions are highlighted (when they exist) by using the information
in the Pareto File parameter created during execution of one of the multi-object
optimization techniques.
Proceed to one of the following topics for more information on using this tool:
“Accessing the Tool” on this page
“Changing the Selected Parameters,” on page 270
“Viewing the Data,” on page 271
Accessing the Tool

When accessed from the Runtime Gateway, the necessary data is loaded from the
selected parameters.
Note: If your graph appears with a yellow background and a button in the top
To access Engineering Data Mining from the Runtime Gateway:
1. Access the Runtime Gateway. Typically, the Runtime Gateway appears

automatically after you execute a model using the Design Gateway. For
information on other ways to start the Runtime Gateway, see “Using the Runtime
Gateway,” on page 20.
2. Select the component you want to examine on the left side of the Runtime
Gateway; then, click the Data Analysis tab.

The contents of the tab appear with the selected component’s name displayed at the
top of the tab.
This tab is divided into three subtabs.
3. Verify that the EDM subtab is selected. It should be selected by default. The EDM
information is displayed on the subtab. By default, information for all of the
parameters in the selected component is displayed.
4. Proceed to one of the following topics, based on how you would like to use the
EDM tool:
To change the parameters that are being used by the EDM tool, proceed to
“Changing the Selected Parameters,” on page 270.
To view information for all of the parameters in your component, proceed to

“Viewing the Data,” on page 271.

Changing the Selected Parameters

By default, all of the parameters in the selected component are used to create the
information displayed in the EDM tool. If the selected component has more than 30
inputs or outputs, only the first 30 will be included. However, you can change which
parameters are used by the tool.
Note: All changes to parameter selections made in the EDM panel will also be
reflected in the History table.
To change the parameters used by the EDM tool:

1. Click the Configure button near the top of the EDM subtab. The Select
Parameters for Viewing dialog box appears.
2. Click the parameters that you want to use in the graphs. You can select parameters
individually or you can select every listed parameter using the Select All button.
The Mode column shows you the parameter type (input, output, etc.).
3. Click OK. The EDM graphs are updated accordingly.
4. Proceed to “Viewing the Data,” on page 271 for more information on how to read
the data displayed on the lower portion of the EDM subtab.

Viewing the Data

The two parallel coordinate graphs on the Engineering Data Mining Tool dialog box
display your input and output parameter information for each run of the selected
component.
The graph consists of all inputs and outputs (depending on the graph you are viewing)
displayed across the x-axis, with each value for each variable displayed in increasing
order above that variable. Variable values for each input or output are linked by a
sequential line graph to represent each design point. By default, each parameter is
displayed on an individual scale, taking the full range of the graph (normalized).
Several options appear at the bottom of the dialog box and allow you to manipulate the
order of the displayed parameters.
To view the data displayed on the Engineering Data Mining Tool:
1. Run your mouse pointer over items in either the Inputs area or the Outputs area.
Information that corresponds to the selected point is displayed in all other areas of
2. Verify that the Normalize Data check box is selected.
Based on your selection, the following actions occur:
If checked, the data for each input and output is normalized by the range of the
data. The data for all input and outputs is then displayed across the full vertical
range of the graphs.
If not checked, the resulting range of the graphs is based on the smallest and
largest values of all the input or output parameters. In this case, if one
parameter range is between 1 and 100, and another parameter range is 1 to 10,
the second parameter is displayed over only 10 percent of the vertical range of
the graph. This option allows the inputs or outputs to be compared by
magnitude and range.
3. Set the Show Pareto Points Only check button at the top of the dialog box (if
available). By default, the graphs display all points of the selected component. If a
Pareto file is available, the View Pareto Data Only check button is displayed.
Activating this check button filters out all non-Pareto data points so that graphs
only display the Pareto solutions. This option is only available when using the
Optimization component in conjunction with the AMGA, NCGA, and NSGA-II

techniques, or when analyzing an imported data file. In the latter case, an imported
Pareto file can be selected via the button. For more information on importing a
data file, see “Importing Data From a File,” on page 123.
Note: Pareto file parameters are not shown by default. If the Pareto file does not
appear, click the Configure button and select the Pareto file. A preference option
can be set to display File parameters automatically. For more information about
setting this option, see “Setting Additional Preferences,” on page 51.
4. Alter the sort order of the points displayed in the graphs using any of the following
options:
Set the sort options for the data in the tables by clicking the Sort by drop-down
list and selecting which responses to base the sort on; then, click the
button to determine the order of your sort. You can sort in

ascending or descending order.
Use the buttons to move between runs. The text box shows you the run
whose data is currently being displayed.
You can use the Global Data filters to reduce the number of points displayed
on the EDM (and other tabs on the Runtime Gateway). For more information
on these options, see “Filtering Data,” on page 92.
(optional) Click the Reset Sort button to return the values in the graphs to their
default setting.
5. Save a data point by clicking the point (line) in either of the two graphs (you can
also use the button to select the currently highlighted point); then, click the
button on the toolbar.

Once you specify the name and location, the parameter information for the selected
point is saved in a text file (in a <name>:<value> format).

Using the Correlation Map 273
Using the Correlation Map

Given the large sets of data that Isight can work with, it can be very time consuming to
sort the relevance of particular parameters. The Correlation Map is a post-processing
aid that calculates the rank and linear correlation values of every pair of parameters in
a given model. The Correlation Map can provide a bird’s eye view of the parameters
and their relations to one another.
This tool provides several benefits including:
Illustrates how the system works via its data flow
Identifies areas of redundancy
Identifies weak points
Identifies the rules that govern the performance of the system
The Correlation Map allows you to make decisions to focus the efforts of your design
team on the parameters that have the most effect on a desired outcome.
“Accessing the Correlation Map,” on page 274
“Viewing the Data,” on page 275
“Using the Graphing Options,” on page 277
“Working with the Filter Options,” on page 277
For reference information about the Correlation Map, see “Correlation Map Reference
Information,” on page 330

Accessing the Correlation Map

To access the Correlation Map from the Runtime Gateway:

Gateway; then, click the Data Analysis tab. The contents of the tab appear with
the selected component’s name displayed at the top of the tab.
This tab is divided into three subtabs.*

3. Click the Correlation Map subtab. The Correlation Map information (based on
the results of the previously run model) is displayed on the subtab.
“Viewing the Data” on this page discusses how to read the data displayed on
the subtab.
“Using the Graphing Options,” on page 277 discusses how to create graphs
based on the Correlation Map using the Graphs Overview area.
“Working with the Filter Options,” on page 277 discusses how to use the filter
options at the bottom of the tab.
Viewing the Data

The graph in the center of the subtab is the heart of the Correlation Map. The labeled
nodes down the diagonal are the parameters used by the model. The inputs are located
in the upper left half and the outputs are located in the lower right. Connecting pairs of
these parameters together are the edges that represent a correlation. If the edge is in the

upper right half then there is a positive correlation; while the edges in the lower left
indicate a negative correlation. The lines are further subdivided, with the strongest half
of the currently displayed lines represented as a solid line and the weaker half as a
dashed line.
Note: The icons are the same as used in the Design Gateway. For more information
about the Design Gateway, refer to the Isight User’s Guide.
To select a parameter, simply click it. To select multiple parameters, click a parameter;
then, hold down the <shift> or <ctrl> keys while selecting other parameters.
The toolbar on the left side of the interface provides the main controls for viewing the
data. The following buttons are available:
. This option zooms in on the Correlation Map.
. This option zooms out on the Correlation Map.
. This option fits the Correlation Map in the window.
. This option copies the map image to the clipboard.
. This option saves the Correlation Map as an image file (JPEG).
Right-clicking on the Correlation Map displays a menu with the following options:
Toggle Pan Mode. This option provides an easy way to navigate the Correlation
Map using the mouse (click and drag).
Toggle Labels. This option shows and hides the parameter labels.
Center Graph. This option centers the Correlation Map in the window.
Fit to window. This option fits the Correlation Map in the window.
Note: Large Correlation Maps may not fit in the window.

Copy. This option copies the Correlation Map to the clipboard as an image.
Export Image to File. This option saves the Correlation Map to a JPEG (image)
file.
Export Data to File. This option saves the data generated in the current
Correlation Map to a text file.

Using the Graphing Options

When the Graph Overview area is active, clicking portions of the Correlation Map
automatically displays preview graphs. If a parameter icon is clicked, a Frequency
graph is generated. If a connecting edge is clicked, a scatter plot of the two connected
parameters is generated. If desired, you can permanently add these preview graphs to
your Graph Overview area or Graphs tab. For more information on using this area, see
“Understanding the Graphs Overview Area,” on page 226.
Working with the Filter Options

Changing the cutoff value changes the correlations that are displayed. The correlations
are ranked from -1 to 1. The sign of the value indicates whether the correlations are
direct (+) or indirect (-); while the value indicates the strengths (0 is the lowest, +/-1 is
the highest). The cutoff value indicates the minimum absolute value of the correlations
to display. For example, a cutoff value of 0.5 will display all the correlations greater
than 0.5 and less than -0.5.
You can change the Cutoff Value by updating the value in the Cutoff Value text box.
You can also use the slider adjacent to the box to adjust the value. The Redraw While
Sliding check box allows you to view your changes while sliding the ruler. If Redraw
While Sliding is not selected, then your changes won’t appear until after you release
the mouse button. The check box is not selected by default.
Note: You can also filter the displayed parameters using the options at the bottom of
the tab. For more information on these options, see “Filtering Data,” on page 92.
The advanced filter options allow you to filter parameters and includes an option that
aids readability.

To access the advanced filter options:
1. Click the Advanced Filter Options button at the bottom of the interface. The
Advanced Filter Options dialog box appears.
From here, you can do one of the following:
Show only those Parameters that have some relation. While the final two
options are mutually exclusive (you must choose one or the other); this option
applies to all situations. If selected, the Correlation Map draws the parameters
that have no correlations above that cutoff value. This option is enabled by
default.
Hide Output to Output Relations. While the final two options are mutually
exclusive (you must choose one or the other); this option applies to all
situations. If selected, the Correlation Map only shows the lines of correlation
that connect an input to an output. This option allows you to focus on what you
can directly control (the inputs) and how it effects the results.
Restrict to only this Parameter and those related to it. This option takes the
parameters you select from the drop-down list and the cutoff value into
account. The Correlation Map displays all the correlations that involved your
selection and are greater than the cutoff value.
Permit only these Parameters to be displayed. This option takes the

parameters you select from the list below this option and the cutoff value into
account. The Correlation Map shows only the correlations that involve the

Using the Two-dimensional (2D) Scatter Plots 279
parameters that were selected and greater than the cutoff value. All parameters
are selected by default.
2. Click OK to save your filtering options. The Correlation Map changes based on
the parameters selected.
Using the Two-dimensional (2D) Scatter Plots

You can select numerous combinations of scatter plots to display your results. The
scatter plots that are displayed are based upon the parameters you selected on the EDM
subtab (using the Engineering Data Mining tool). For more information on selecting
parameters using the Engineering Data Mining tool, see “Changing the Selected
Parameters,” on page 270.

Gateway; then, click the Data Analysis tab.

The contents of the tab appear with the selected component’s name displayed at
the top of the tab.
This tab is divided into three subtabs.
3. Click the 2D Scatter Plots subtab.

Using the Two-dimensional (2D) Scatter Plots 281
The scatter plots are displayed on the subtab.
Note: If your plot appears with a yellow background and a button in the top
This subtab shows scatter plots for all combinations of two outputs as defined on
the EDM subtab.
Note: All data points found in the database file are displayed in all graphs unless
the Show Pareto Points Only check box is activated on the EDM subtab, in which
case only the Pareto solution data points are displayed.
This subtab also:
Provides a single view of all of the combinations of outputs

(If the Graphs Overview area is open) Provides a preview graph appropriate to
the currently selected graph, a History graph for single parameter (frequency
graphs) and a Line graph for two parameters (scatter plots). For more

information on this area and how to use it, see “Understanding the Graphs
Overview Area,” on page 226.
Allows you to add any displayed graph to the Graphs tab.
Allows you to expand any displayed graph to view it in a larger size.
Lets you alter the parameters used to create the scatter plots.
4. Perform any of the following actions, as desired, using the buttons on the right side
of the subtab:
Add a scatter plot to the Graphs tab. If you select an individual scatter plot and
click the button, the graph is added to the Runtime Gateway Graphs tab
and the Graphs Overview area (if it is visible). This feature allows you to
examine the selected graph more closely. For more information on using the
Graphs tab, see “Using Graphs,” on page 227. For more information on using
the Graphs Overview area, see “Understanding the Graphs Overview Area,”
on page 226.
View a single scatter plot on the subtab. You can use the button to enlarge
a single scatter plot so that it is easier to view. All other scatter plots are
temporarily hidden while the single scatter plot is being viewed. To return to
original view that showed many scatter plots, click the button.
Alter the parameters that are being used to create the scatter plots. You can
click the button to view the parameters that are currently being used to
create the scatter plots. When you click OK, you are returned to the 2D Scatter
Plots subtab, and the scatter plots are updated.
Note: The parameters contained in this list may represent only a subset of all
the available parameters. This subset contains all the parameters selected on
the EDM subtab.
For a zoomed in graph there are controls to left that are just like the popped out
graphs - which are related to the graphs tab. Common buttons include Select,
Pan, Rectangle Zoom, Zoom In, Out, Reset, and Zoom.
Filter the displayed parameters using the options at the bottom of the tab. For
more information on these options, see “Filtering Data,” on page 92.

Using the Taguchi Main Effects Viewer 283
5. Perform any of the following actions on an individual plot:
Run your mouse pointer over items in the plot. A design point is highlighted in
all scatter plots and in any graph displayed in the Graphs Overview area.
Note: Clicking a point on either graph on the EDM subtab also highlights the
design in all of your scatter plots.
Export a scatter plot by right-clicking the plot; then, select the Export option
from the menu that appears. Additional options appear. For more information
on these options, see “Exporting Graph Data,” on page 249.
Copy a scatter plot by right-clicking the plot; then, select the Copy option
from the menu that appears. Additional options appear. For more information
on these options, see “Copying a Graph,” on page 250.
Edit a scatter plot’s options including its general options and legend options.
To access these options, right-click the plot; then, select Edit Options from the
menu that appears. For more information on the available options, see
“Changing Graph Options,” on page 239.
Reset a scatter plot to its original settings by right-clicking the plot; then, select
Reset from the menu that appears. The graph is returned to its original form.
Using the Taguchi Main Effects Viewer

The Main Effects Viewer allows you to visualize the results of a Taguchi Robust
Design component. It offers an interactive way to examine the resulting signal-to-noise
ratio (S/N) and sensitivity (where appropriate) for any selected combination of factor
levels and shows the benefit/deficit in those metrics from the baseline design. For
factor level combinations that have not yet been executed, this tool presents an
estimate of S/N ratio and sensitivity and offers a means of executing a set of
confirmation runs in Isight to obtain actual values for the metrics.
For dynamic-standardized systems, S/N ratio and the three polynomial expansion
coefficients, Beta 1, Beta 2, and Beta 3, are included in the Main Effects Viewer.
Note: You must select the desired Taguchi Robust Design component on the
Workflow tab or the Model Explorer in order for this option to be available.

To access the Main Effects Viewer:
1. Click a Taguchi Robust Design component which has completed execution on the
Workflow tab or the Model Explorer.
2. Click the Graphs tab; then, click the button.
Note: You can also access this tool using the Graphs Overview area. For more
information, see “Understanding the Graphs Overview Area,” on page 226.
The Main Effects Viewer dialog box appears.
The results from the Taguchi Robust Design component are loaded into the
interface. The Main Effects Viewer is organized into a few primary panels.

3. Proceed to one of the following topics to learn more about the panels:
“Viewing the Graphs” on this page
“Viewing the Tables,” on page 290
4. Click the Close button at the bottom of the Main Effects Viewer to close the Main
Effects Viewer at any time. Note that any selections or settings you have chosen
will not be saved and will need to be re-established if you open the Main Effects
Viewer again.
Viewing the Graphs

The center panel of the Main Effects Viewer contains a tab for each response, with
each of these response tabs containing two sub-tabs to present Graphs or Tables. This
section describes how to interpret the information on the Graphs tab and how to
interactively manipulate the information displayed. This section is divided into the
following topics:
“Graph Contents” on this page
“Setting the Selected Point,” on page 286
“Setting the Overlay Symbols,” on page 287
“Filtering the Factors,” on page 288
“Viewing the Metric Values and Benefit,” on page 288
Graph Contents
For each response, a Signal-to-Noise (S/N) Ratio graph is presented along with the
following graphs, depending on the system type:
Static System. Sensitivity graph for all nominal-is-best type responses
Dynamic System. Sensitivity graph
Dynamic-Standardized System. A graph for each of the three polynomial

expansion coefficients: Beta 1, Beta 2, and Beta 3

The graphs show the values for these Taguchi response metrics at each level of the
factors. The graphs display a current point and can optionally have various symbols
overlaid to indicate other points of interest, all of which are described in the following
topics.
Note: For a more detailed description of S/N ratios, sensitivity, and the
dynamic-standardized polynomial expansion coefficients, as they relate to the Taguchi
robust design process, refer to the Taguchi reference section of the Isight Component
Guide.
Setting the Selected Point

The Main Effects Viewer allows you to set a selected point for which to calculate the
Taguchi response metrics, allowing for a determination of the benefit of that selected
point over an optionally specified baseline design.
To set the selected point, click the appropriate radio button in the Selected Point area in
the upper left portion of viewer:
Select the Best Levels radio button to set the selected point to the combination of
factor levels that provides the estimated best metric values.
Select the Worst Levels radio button to set the selected point to the combination of
factor levels that provides the estimated worst metric values.
Select any combination of factor levels by clicking the graph on the desired level
for any factor. Notice that the User selected levels radio button is automatically
selected for this case.
Click the Based on drop-down arrow to set the selected point on each graph
independently for Each Metric (default), or to set the selected point on both graphs
to the same point based on the best or worst levels for the selected metric (S/N
Ratio, Sensitivity, Beta 1, Beta 2, or Beta 3). This option is not available when only
the S/N Ratio graph is displayed or when the selected point is set to User selected
levels.
The selected point in all cases will be represented by a green filled circle symbol on the
corresponding level for each factor.
If you select specific user selected levels and then switch to the Best Levels or Worst
Levels option, the user selected levels are retained so that if you select this option

again you do not lose your selection. This behavior allows you to interactively select
levels and compare the benefit at those levels with the benefit at the best/worst levels in
an iterative fashion. However, if you select the best or worst levels option and then
click in the graph on a new level for any factor, this set of levels (best/worst levels
modified by the manual selection for one of the factors) is now considered the new set
of user selected levels.
Setting the Overlay Symbols

There are a number of specific sets of factor levels that have significant meaning
relative to the Taguchi response metrics. The set of toggle buttons at the top of the
Main Effects Viewer allow you to identify those various sets of levels using distinct
symbols on the graphs. The available sets of levels that can be depicted are as follows:
Best Levels. The set of factor levels that provides the estimated best metric value
(determined separately for each metric).
Worst Levels. The set of factor levels that provides the estimated worst metric
value.
Best Point. The set of factor levels that represents an actual point run in the set of
experiments that resulted in the best metric value.
Worst Point. The set of factor levels that represents an actual point run in the set
of experiments that resulted in the worst metric value.
Baseline (if available). The set of factor levels that represents the baseline design
point from which the benefit of new metric values is determined. It is possible that
the baseline design is comprised of values that are not represented by the factor
levels; in this case, a symbol will be displayed for only those values that
correspond to factor levels. Note that a baseline point may not always be provided,
in which case benefit cannot be determined.

Filtering the Factors

The Main Effects Viewer allows you to filter the factors that are shown in the graph in
order to focus on specific factor effects. The Factors area on the left side of the
interface provides check boxes next to each factor to specify whether or not it should
be included (shown).
To filter the factors:

1. Click the appropriate checkbox in the Show column to select or deselect any of the
factors. You can also click the Select All or Deselect All buttons below the table to
select or deselect all of the factors at once.
2. (optional) Click in the Factor column header to sort the factors alphabetically. You
can click the header a second time to sort the column in reverse. A third click
returns it to the original order.
Note that with each of the above actions, the graphs adjust to show only the
selected factors in the order specified.
Viewing the Metric Values and Benefit

The primary use of the Main Effects Viewer is to determine the benefit relative to
metric values that can be achieved by setting factor values in different combinations.
For information on selecting factor levels, see “Filtering the Factors,” on page 288. For
the currently selected point (set of factor levels), the relevant values for the metrics that
correspond to that point are displayed in the panels on the right side of the Main Effects
Viewer.
These values include:

Baseline. If a baseline design was included in the Taguchi plan execution, the
values for the Taguchi response metrics at that baseline design are displayed.
Estimated. This value represents the estimated value of the Taguchi response
metric at the selected point (it is estimated since, in most cases, this combination of
factor levels was not actually executed).
Actual. This value represents the actual value of the Taguchi response metric at the
selected point, provided that this combination of factor levels was executed. If this
combination has not yet been executed, the button appears, which

will execute a set of confirmation runs for this combination of factor levels to
determine the Taguchi response metric values.
Benefit. This value represents the amount of improvement (in terms of Taguchi
response metric values) that is achieved at the selected point relative to the
baseline design. If the Actual value is provided, the benefit is calculated as
Actual-Baseline; if no Actual value is available, the benefit is calculated as
Estimated-Baseline.
Note: If no baseline design is available, the benefit is not calculated.
If a Baseline design is provided (so that a benefit can be calculated), a Benefit Meter is
displayed on the right side of the Main Effects Viewer for each Taguchi response
metric. The black line in the meter indicates the value for the Baseline design, and it is
positioned within the meter based on the total known range of values for the response
metric (determined by the higher of the Best Point or Best Levels design and the lower
of the Worst Point or Worst Levels design). The meter is colored in to indicate the
value of the response metric relative to the baseline, with green indicating a positive
benefit and red indicating a negative benefit (or deficit). As you select different points,
you can watch the meter change, giving you a graphical representation of the benefit
without needing to focus on the specific numbers.

Viewing the Tables

The Main Effects Viewer also provides tables of the Taguchi response metric values
for the various significant factor level combinations for each response. Select the
Tables subtab on any response tab (near the bottom of the interface) to view these
tables.
The response metric tables each have the same structure. Columns exist for the primary
significant sets of factor levels: Baseline (if available), Best Levels, Worst Levels, Best
Point, and Worst Point. For more information about the levels, see “Viewing the
Graphs,” on page 285. A row is provided for each factor to specify its values for the
corresponding sets of levels, and the Estimated and Actual metric values are provided
for each set of levels along with the Benefit determined relative to the Baseline. For
sets of levels that correspond to an actual experiment number that was executed, that
experiment number is also listed.

291
A Runtime Gateway Reference

Information
This appendix provides reference information related to the Runtime Gateway

interface. It is divided into the following topics:
“Menu Options,” on page 292
“Toolbar Buttons and Other Features,” on page 299

“Setting Runtime Gateway Options Using Environment Variables,” on page 300
“Keyboard Shortcuts,” on page 302
“Command Line Options,” on page 305

292 Appendix A Runtime Gateway Reference Information
Introduction
This section contains reference information about menu options, toolbar buttons, and
command line options. Some sections (mainly the menu and toolbar sections) are only
as a quick reference, and does not necessarily describe how to use the options.
“Menu Options” on this page
“Toolbar Buttons and Other Features,” on page 299
“Setting Runtime Gateway Options Using Environment Variables,” on page 300
“Keyboard Shortcuts,” on page 302
“Command Line Options,” on page 305
Menu Options
The following tables describe the options available from each menu on the Runtime
Gateway, including the menu option name, the icon that represents the action (if one
exists), the toolbar button that performs the same action (if one exists), and the action
description. Proceed to one of the following topics:
“File Menu,” on page 293
“Edit Menu,” on page 294
“Run Menu,” on page 295
“View Menu,” on page 296
“Jobs Menu,” on page 297
“Help Menu,” on page 298

Menu Options 293
File Menu
The following table (Table A-1) describes options available from the Runtime
Gateway File menu.
Table A-1. File Menu Options
Option Icon Toolba Action

r
Button
Open... Allows you to open a job from your
computer’s hard drive. For more
information see “Opening a Model From the
Disk,” on page 24.
Open Model from Allows you to open a job from the current
Library... Library. For more information, see
“Opening a Model From a Library,” on
page 24.
Open Results from Job Allows you to open a job from the local or
Database... ACS database (depending on your
connection) using the Select Job dialog box.
For more information, see “Working With
Jobs,” on page 56.
Close Current Model Closes the model you are currently viewing
on the Runtime Gateway.
Close All Models Closes all models that are currently open.
Save Model Saves the current model, with the same file
name, to the local disk as a *.zmf file. For
more information, see “Saving Models and
Components,” on page 27.
Save Model As... Allows you to save the current model (*.zmf
file) with a new file name.
Save Results... Allows you to save your job results to a file.
For more information, see “Saving Results
to a Results File,” on page 119.
Save Results As Text... Allows you to save the job results to a text
file for viewing in a third-party product. For
more information, see “Saving Results to a
Text File,” on page 120.

Table A-1. File Menu Options (cont.)

r
Button
Import Data from File... Allows you to import a data set from a text
file or an Excel spreadsheet and use a subset
of the Runtime Gateway’s features to
analyze and visualize the data. For more
information, see “Importing Data From a
File,” on page 123.
Publish... Allows you to publish a model to the
Library. For more information, refer to the
(Recently Used Files) A list of recently used models is displayed,
which allows quick access to these files.
Close Window Closes the Runtime Gateway.
Exit Closes all Isight interfaces.
Edit Menu
Gateway Edit menu.
Table A-2. Edit Menu Options
Option Icon Action

Find Displays a Find text box on the Design Gateway where you
can search for components, parameters, or files in your
model. For more information, see “Searching for a
Component, Parameter, or File in a Model,” on page 132.

Menu Options 295
Table A-2. Edit Menu Options (cont.)
Option Icon Action

Advanced Find Displays an Advanced Find dialog box where you can
specify search criteria to find components, parameters, or
files in your model. For more information, see “Using the
Advanced Find Option,” on page 134.
Preferences Allows you to set options for different Isight interfaces and
some components. For more information on using
preferences, see “Setting Preferences,” on page 41. The
preferences accessed are the same as those accessed using
the Design Gateway.
Run Menu
Gateway Run menu.
Table A-3. Run Menu Options

r
Button
Run Model This action executes the entire model.
The action is automatically performed if
only the Run button is clicked (instead of
the associated menu).
Run Component (Selected This action executes only the selected
Component) component.
Configure and Run Model This action executes the entire model,
but offers additional options prior to
execution. For more information, see
“Using the Configure and Run Options,”
on page 32.

Table A-3. Run Menu Options (cont.)

r
Button
Configure and Run This action executes the selected
Component (Selected component, but offers additional options
Component) prior to execution. For more information,
see “Using the Configure and Run
Test Locally If you are connected to an ACS in the
Fiper environment, this option opens a
submenu that allows you to execute a
model locally using options similar to
those described above.
View Menu
Gateway View menu.
Table A-4. View Menu Options
Option Icon Action

Design Opens the Design Gateway interface with the default model or the
Gateway last model loaded, depending on your preference settings. For more
information on using this interface, refer to the Isight User’s
Guide.
Job Database Opens the Job Database dialog box, which allows you to work with
previously executed jobs. For more information, see “Working
With Jobs,” on page 56.
Dataflow When activated, displays the Dataflow tab on the Runtime
Gateway. By default, this option is deactivated. For more
information, see “Viewing the Dataflow,” on page 118.

Menu Options 297
Table A-4. View Menu Options (cont.)
Option Icon Action

Data Analysis When activated, displays the Data Analysis tab on the Runtime
Gateway. By default, this option is activated. For more
information, see Chapter 3 “Using Graphs, Tables, and Other Data
Analysis Tools”.
Visual Design When activated, displays the Visual Design (Approximations) tab
on the Runtime Gateway. By default, this option is activated. For
more information, see Chapter 2 “Visual Design with
Approximations”.
Summary When activated, displays the Summary tab on the Runtime
Gateway. By default, this option is activated. For more
information, see “Viewing the Summary,” on page 111.
Log When activated, displays the Log tab on the Runtime Gateway. By
default, this option is activated. For more information, see “Using
the Logs,” on page 113.
Graphs/Popout Allows you to control how the graph tab is viewed.
Graphs/Graphs When activated, displays the Graphs tab on the Runtime Gateway.
Tab By default, this option is activated. For more information, see
“Using Graphs,” on page 227.
Graphs/Graphs When activated, displays the Graphs Overview area on the

Overview Runtime Gateway. By default, this option is activated. For more
information, see “Understanding the Graphs Overview Area,” on
page 226.

Jobs Menu
Gateway Jobs menu.
Table A-5. Jobs Menu Options
Option Icon Action

View Job Opens the Job Database dialog box, which allows you to work
Database with previously executed jobs. For more information, see
“Working With Jobs,” on page 56.
(Current Jobs) This list shows all currently open jobs in the Runtime Gateway.
You can use this menu to move between different jobs.
(Current Data This list shows all currently open data files in the Runtime
File) Gateway. You can use this menu to move between different
files.
Unload Jobs... This option allows you to remove jobs from your system’s
memory. For more information, see “Removing Jobs From
Memory,” on page 72.
Help Menu
Gateway Help menu.
Table A-6. Help Menu Options
Option Icon Action

Contents Opens the Isight Runtime Gateway online help. If you have any
trouble accessing the online help, refer to the Isight User’s Guide for
information on supported help platforms.
About Displays information about Isight, as well as contact information.

Toolbar Buttons and Other Features 299
Toolbar Buttons and Other Features

The following table (Table A-7) describes buttons and other features available from the
Runtime Gateway Toolbar.
Table A-7. Toolbar Buttons and Other Features
Button/Feature Action/Usage
Allows you to open a job from your computer’s
hard drive.
Allows you to open a job from the local or ACS
database (depending on your connection) using
the Select Job dialog box. For more information,
see “Searching For a Job in the Database,” on
page 58.
Allows you to save the current job with a new
file name.
Allows you to save your job results to a file. For
more information, see “Saving Results,” on
page 119.
Opens the Generate Report dialog box, which
allows you details for creating a report on your
model. For more information, see “Creating a
Report Manually,” on page 130.
Allows you to determine how many significant
digits are displayed for real values within the
Runtime Gateway.
Allows you to view the best design point (when
problem formulation is used) and set feasibility
options. These feasibility options are also
available near the bottom of certain tabs on the
Runtime Gateway. For more information, see
“Filtering Data,” on page 92.
This button runs the job using the ACS or in
Standalone mode, based on the type of
connection. Clicking the down arrow to the right
of the button accesses additional execution
options. For more information, see “Controlling
Execution,” on page 31.

Table A-7. Toolbar Buttons and Other Features (cont.)
Button/Feature Action/Usage
The Current Job drop-down list. It allows you to
select a specific job.
Execution Status. It displays the status of your
current execution. It also displays a Run
Counter, which specifies how many runs have
been executed (left side number), and how many
runs will be executed (right side number)
This button stops the currently executing job.
This button pauses the currently executing job.

This button allows you to re-execute a job that
failed during execution. For more information,
see “Re-running Failed Jobs,” on page 66.
Setting Runtime Gateway Options Using

Environment Variables
The following options are similar to the command line options. However, they are set
in the FIPER_JVMPARMS environment variable and are automatically used when the
Runtime Gateway is accessed. These options may be particularly useful if you always
log in using the same connection profile, user name, and password.
For more information on setting environment variables on your system, contact your
local systems administrator.
Note: Some of these options have matching command line arguments, while some do
not. All of these options can be used (as they appear below) on the command line in
conjunction with the rt_gateway command. For more information on command
line arguments, see “Command Line Options,” on page 305.

Setting Runtime Gateway Options Using Environment Variables 301
Important: Be sure to leave a space between this argument and the last one currently
listed in the environment variable definition.
-Dfiper.gateway.modelToLoad=MODEL.zmf. This setting allows you to

define a model that will be loaded with the Runtime Gateway.
-Dfiper.logging.maxSizeKB=99. This setting specifies the maximum

size of log files (in kilobytes) created by the Runtime Gateway. Once the
maximum size of the file is reached, the original log file is saved and a new file is
created.
-Dfiper.logging.numBackups=2. This setting determines the number of

backup (old) log files to keep. A new log file is created when it’s maximum size is
reached. This size can be specified using the -Dfiper.logging.maxSizeKB
option previously described. By default, one backup log and one active log are
created.
-Dfiper.logon.profile=PROFILE. This setting allows you to specify the

connection profile.
-Dfiper.logon.prop.user=USER. This setting allows you to specify the

user name.
-Dfiper.logon.prop.pw=PASSWORD. This setting allows you to specify

the password.
-Dfiper.logon.prompt=yes|no. This setting allows you to specify

whether or not the Logon dialog box appears when the Runtime Gateway is
started.
-Dfiper.gateway.executeModel=. This setting allows you to tell the

Runtime Gateway where to execute the loaded model. Two options are available:
local and remote.
-Dfiper.gateway.quitAfterExecution=true. This setting allows

you to have the Runtime Gateway close automatically following execution.
You can also customize the directory that will be used for all temporary files using the
FIPER_TEMP environment variable.

Keyboard Shortcuts
This section describes keyboard shortcuts available when using the Runtime Gateway.
“Runtime Gateway Keyboard Shortcuts” on this page
“Using Keyboard Shortcuts on HP-UX,” on page 304
Runtime Gateway Keyboard Shortcuts

The following table lists the keyboard shortcuts available from the Runtime Gateway.
The shortcuts work when the Runtime Gateway is the active window.
Table A-8. Runtime Gateway Keyboard Shortcuts
Menu Text Mnemonic Accelerator

File F
Open... O Ctrl+O
Open Model from Library... L Ctrl+Shift+O
Open Results from Job Database... J Ctrl+J
Save Model S Ctrl+S
Save Model As... A F12
Save Results... V
Save Results as Text... R Ctrl-D
Import Data from File... G Ctrl-G
Publish... U Ctrl-U
Close Window W Ctrl-W
Exit x
Edit
Find Ctrl+F
Advanced Find Ctrl+Alt+F
Preferences P Alt+N

Keyboard Shortcuts 303
Table A-8. Runtime Gateway Keyboard Shortcuts (cont.)
Menu Text Mnemonic Accelerator
Run R
Run Model (Local) L F4
Run Model (ACS) M F5
Run Component (Local) N Shift+F4
Run Component (ACS) U Shift+F5
Config and Run Model (Local) G Alt+Shift+F4
Config and Run Model (ACS) F Alt+Shift+F5
Config and Run Component O Ctrl+Shift+F4
(Local)
Config and Run Component I Ctrl+Shift+F5
(ACS)
View V
Design Gateway G
Job Database J Ctrl+J
Dataflow D
Data Analysis Y
Visual Design A
Summary S
Log L
Graphs Popout P
Graphs Tab T
Graphs Overview O
Jobs J
View Job Database J Ctrl+J
Unload Jobs... U
Help H
Contents C F1
About A

Using Keyboard Shortcuts on HP-UX

Several keyboard shortcuts do not work on the HP-UX operating system without
making some modifications to the default key mappings. In general, you must modify
the key mappings so that Alt_L and Alt_R are no longer synonymous with Meta_L and
Meta_R.
To update the key mappings to work with Isight:
1. Open a terminal window.
2. Execute the following commands, using the xmodmap command to change the
key mappings:
xmodmap -e "keysym Alt_L = Alt_L"
xmodmap -e "keysym Alt_R = Alt_R"
xmodmap -e "clear Mod1"
xmodmap -e "add Mod1 = Alt_L"
xmodmap -e "add Mod1 = Alt_R"
3. Close the terminal window; then, verify that the shortcuts listed below function
properly:
Alt-F opens the File menu.

Alt-E opens the Edit menu.
Alt-R opens the Run menu.
Alt-V opens the View menu.
Alt-J opens the Jobs menu.
Alt-H opens the Help menu.

Command Line Options 305
Command Line Options

Several command line options can be used in conjunction with the rt_gateway
command at the command prompt:
Note: Arguments with a value may be specified using either of the following methods
(tag is case-insensitive):
tag:VALUE. For example: rt_gateway model:i_beam.zmf
-tag VALUE. For example: rt_gateway -model i_beam.zmf
Arguments without a value may be specified in either format also:
-tag. Turns on the feature.
tag:y. Turns on the feature (same as above). The y is required.
If you use more than one command line argument, and two are in conflict with each
other, the later argument overrides earlier one.
If an argument contains spaces, enclose it in single quotes or double quotes on the

UNIX command line or in interactive mode. On the Windows command line, always
use double quotes. For example:
start file:'model test.zmf'

fipercmd start file: "C:\documents and settings\user\mymodel.zmf"
The following commands are available:
<no_argument>. Not specifying an argument with the rt_gateway command

simply opens the Runtime Gateway with no model loaded.
-config. This argument prompts you to configure your model before executing,
allowing you to do such things as update parameter values or customize the job
name. The argument must be used with the run option. For more information, see
“Using the Configure and Run Options,” on page 32.
configfile:<file_name>. This argument is interchangeable with the

@FILENAME argument. For more information, see the entry for @FILENAME
below. However, the syntax is slightly different as shown below:
rt_gateway configfile:acs.txt

@FILENAME. This argument allows you to read a set of command line arguments
from a specified file. The file must be a text file containing command line
arguments as they would normally appear on a command line.
For example, if you had a file acs.txt in your home directory that contained the
following entries:
profile:acs1 logonprompt:no
# provide user name and password to connect
user:fiperacs pw:fiperacs
Then you could start the Runtime Gateway connected to ACS1 with the following
command (which assumes that the acs.txt file is located in the current working
directory):
rt_gateway @acs.txt
You can also specify an absolute path to the directory containing the acs.txt
file:
rt_gateway "@c:\documents and settings\user\acs.txt"
Furthermore, you can mix and match the contents of the file with the actual
command line option at the command prompt. For example:
rt_gateway @acs.txt logonprompt:yes
Using the contents of the file created earlier, this argument would show the logon
dialog box (logonprompt command) even though the file provided everything
necessary and also instructed the logon dialog box to not appear.
The file you create can contain one or more lines. Each line can contain one or
more command line argument. Arguments with spaces must be quoted with single
or double quotes. Comments lines are allowed (any line starting with # is ignored
completely). Empty lines are also ignored.
Note: This command automatically creates Runtime Gateway log files. By default,
two log files are created, with the second log file being used once the first log file
reaches its maximum size. You can specify the name and location of these log files
using the logfile command described below. Additionally, you can set the size
of the log files as well as the number of log files that can be created using the
-Dfiper.logging commands described in “Setting Runtime Gateway Options
Using Environment Variables,” on page 300.
This argument is interchangeable with the configfile argument.

-help. This argument prints information about the available command line
arguments and then exits.
import:<job_name>.zrf. This argument allows you to import the specified job as

soon as the Runtime Gateway opens.
importJob:<job_name>.zrf. This argument allows you to load the specified job

as soon as the Runtime Gateway opens. You can also simply specify a file name.
You can also use the shorter version of this argument: -j.
input:<nv_file>. This argument allows you to configure model inputs from the
specified name-value file. The argument must be used with the run option.
jobID. This argument allows you to specify a job that will be automatically
loaded from the Isight database when the Runtime Gateway is started. You must
specify the Job ID string, not the job name. The Job ID string can be located using
the Job Database dialog box (in the Job Details area at the bottom of the dialog
box). For more information on the Job Database dialog box, see “Working With
Jobs,” on page 56. When using this command, the Job ID string is not
case-sensitive.
lfd. This argument saves execution log messages in the specified directory in a
file named by the Job ID string. It is only usable in conjunction with the run
argument. For example, the following command executes a model locally and
saves the execution log messages in the c:\temp directory:
rt_gateway sample.zmf run:local lfd:c:\temp
locale. This argument sets the local (language environment) for the current
session. It is useful only when testing support for a language. For example, typing
rt_gateway -1 de_DE displays all messages in German. You can also use the
shorter version of this argument: -1.
logfile. This argument allows you to specify a file name and location for the
Isight log file. By default, one log file is created. However, once it reaches its
maximum size, the old file is saved and a new log file is created. By default, only
two log files are created. If a third log file is necessary, the currently active log file
is saved but the original backup file (the first log file created) is deleted. You can
adjust the maximum size of the log files and the number of backup (old) log files
saved using the -Dfiper.logging commands described in “Setting Runtime
Gateway Options Using Environment Variables,” on page 300.

loglevel. This argument allows you to determine what information is sent to

your Isight log file. Components create different levels of log messages. You can
define the minimum log information setting (debug), and you will receive
information on that particular level, and all other levels above it. For more
information on log levels, see “Setting Gateway Preferences,” on page 43. The
following log levels are available:
syserror
error
warning
info
debug
logonprompt:[yes|no]. This argument allows you to specify if the Logon
dialog box appears when the Runtime Gateway is executed. If you use this
argument to stop the Logon dialog box from appearing (the no option), you must
specify a profile name, user name and password using the arguments in this list.
Failure to specify this information will cause the Runtime Gateway to cancel the
logon and exit due to the error.
<model_name>.zmf. This argument allows you to specify a particular model that

will be loaded into the Runtime Gateway. You can also use the shorter version of
this argument: -m.
profile:<connection_profile_file_name>. This argument allows you to specify
the connection profile that the Runtime Gateway will use. If you only specify this
argument, the Logon dialog box will appear, and you’ll have to specify the name
and password for the connection profile. If you receive an error that the connection
profile cannot be found, use a full path to the profile. For example:
rt_gateway profile:\SIMULIA\Isight\3.5-1\
standalone.cpr
pw:<password>. This argument allows you to specify the password of the user
that will log into the Runtime Gateway when connecting to an ACS in the Fiper
environment. It is not used for the desktop (Standalone) connections. If you only
specify this argument, the Logon dialog box will appear, but the password will
already be defined.
run:[local|remote]. This argument allows you to execute the specified model

either locally (the local option) or on an ACS in the Fiper environment (the
remote option).

tab. This argument allows you to specify which tab is selected when the Runtime
Gateway appears.
tree. This argument allows you to specify which component is selected on the
model explorer (on the left side of the interface) when the Runtime Gateway
appears. For example, the following would show the Aerodynamics Simcode
component in the Airplane Sizing model.
rt_gateway model:AirplaneSizingDOE.zmf tab:History

"tree:SizingDOE.Aerodynamics"
user:<user_id>. This argument allows you to specify the user that will log on to
use the Runtime Gateway when connecting to an ACS in the Fiper environment. It
is not used for the desktop (Standalone) connections. If you only specify this
argument, the Logon dialog box will appear, but the user name will already be
defined.


311
B Approximation Reference
Information
This appendix provides information that may be helpful when using the
Approximation Wizard. This information is not necessary in order to use the wizard,
but may prove helpful in better understanding how the wizard functions. The appendix
is divided into the following topics:
“Available Approximation Models,” on page 312
“DOE Technique Options,” on page 324

312 Appendix B Approximation Reference Information
Available Approximation Models

The following two approximation models are available in Isight:
“RBF Model” on this page

“Response Surface Model,” on page 319
RBF Model
Radial Basis Functions are a type of neural network employing a hidden layer of radial
units and an output layer of linear units, and characterized by reasonably fast training
and reasonably compact networks.
Weissinger (1947) was the first to use numerical potential flow to calculate the flow
around wings. The potential flow equations are a radial basis function. R. Hardy(1971)
realized that the same concept could be used to fit geophysical data to geophysical
phenomena. Broomhead, D. S., and D. Lowe (1988) renamed this technology “neural
nets” and it was subsequently used to approximate all types of behavior.

Available Approximation Models 313
Usage in Isight
In Isight we follow the Hardy (1972) method as described by Kansa (1999):
Figure B-1. Isight’s RBF Method

Obviously, as the type of physics that are models varies a different type of basis
function would be needed to provide a good fit. The response surface goes through all
the given interpolation data.
For the Isight implementation, the following variable power spline radial basis
function is used:
Variable power spline || x - xj || c

Where: || x - xj || is the Euclidean distance, and
Where: c is a shape function variable between 0.2 < c < 3
The reason for choosing this radial basis function is its ability to model extreme
functions within a narrow range of values of c.
For a value c = 1.15, a good approximation of a step function can be achieved with just
seven interpolation points. For a value of c = 2, a good approximation of a linear
function can be achieved with just three interpolation points, as shown below.

Figure B-2. Step Function and Linear Function

For a value c = 3, a good approximation of a harmonic function is achieved with about

seven points per harmonic period.
Figure B-3. Harmonic Function
Picking c = 3 for the step function example would produce an approximation that
would go through the seven data points, but it would more resemble a single sine wave
than a step function. There are obviously an infinite number of solutions that will go
through any given set of data points.
In most of the literature this problem is solved by splitting the interpolation data into
two groups. One group is used to create the radial basis function approximation and
one is used to compute the error between the radial basis function approximation for
those points and the actual function values. The shape function is optimized to
minimize the summed errors. This is a valid approach when a lot of data points are
available for the interpolation, but in our practice we deal mostly with very sparse data
sets and it seems inefficient to use only half the data to create the actual response
surface.
So we adopted a different approach. We define a good fit as one whereby the shape of
the curve does not change when a point is subtracted. We optimize the value of c for a
minimum sum of the errors N-1 data points.

This approach can be illustrated by going back to the picture of the straight line
approximation, we approximate the first point (circle) from the two top points (square).
The center point is approximated from the two extreme points and the top point is
approximated from the two bottom points. For c = 2 the sum of the errors for the
“missing points” is low.
Figure B-4. Straight Line Approximations

For c = 0.2, the sum of the errors of the “missing points” is extremely high.
Figure B-5. Straight Line Approximations - Part 2
Since the shape function optimization is given a limited number of iterations to

converge, higher accuracy can be achieved by splitting up a large problem into coupled
smaller ones. For instance, one approximation of five inputs and two outputs and one
approximation of six inputs and one output; instead of a single approximation of eleven
inputs and three outputs.
Note: We would like to thank Dr. Kansa for getting us started with the development of
this method.

References
J. Weissinger. “The lift distribution of swept-back wings”. NACA TM 1120, 1947.
Hardy. “Multiquadratic equations of topography and other irregular surfaces”. J.

Geophysics Res. 76, 1905-15 (1971).)
Broomhead, D. S., and D. Lowe. “Multivariable functional interpolation and adaptive

networks”. Complex Systems, 1988, Vol. 2, pp. 321-355.
Kansa, E.J. “Motivation for using radial basis functions to solve PDE's”. 1999.
(Unpublished paper: author kansa@IrisINTERNET.net).
Response Surface Model

Response Surface Models (RSM) in Isight use polynomials of low order (from 1 to 4)
to approximate response of an actual analysis code. A number of exact analyses using
the simulation code(s) have to be performed initially to construct a model, or
alternatively a datafile with a set of analyzed design points can be used. The model
then can be used in optimization and sensitivity studies with a very small
computational expense, since evaluation only involves calculating the value of a
polynomial for a given set of input values. Accuracy of the model is highly dependent
on the amount of data used for its construction (number of data points), the shape of the
exact response function which is approximated, and the volume of the design space in
which the model is constructed. In a sufficiently small volume of the design space, any
smooth function can be approximated by a quadratic polynomial with good accuracy.
For highly non-linear functions, polynomials of 3rd or 4th order can be used. If the
model is used outside of the design space where it was constructed, its accuracy is
impaired, and refining of the model is required.
A maximum order model (4th order or Quartic model) is represented by a polynomial

of the following form:

Where:
N is the number of model inputs
xi is the set of model inputs
a, b, c, d, e are the polynomial coefficients
A lower order model (Linear, Quadratic, Cubic) includes only lower order polynomial
terms (only linear, quadratic, or cubic terms correspondingly). Notice that 3rd and 4th
order models in Isight do not have any mixed polynomial terms (interactions) of order
3 and 4. Only pure cubic and quartic terms are included to reduce the amount of data
required for model construction.
Coefficients of the polynomial (a, b, c, d, e) are determined by solving a linear system

of equations (one equation for each analyzed design point).
The Response Surface Model construction is controlled by the following options:
The order of the model polynomial (referred to as Polynomial Order).

Polynomial term selection.
This option allows you to select a sub-set of polynomial terms using one of the
four available term selection methods (Sequential Replacement, Stepwise
Regression (Efroymson's algorithm), Two-at-a-time Replacement, or Exhaustive
Search). For more information about term selection, see “Polynomial Term
Selection in RSM,” on page 321.
The number of design points (if Random Designs is used for initialization).
The size of the design space around the baseline point in which the initial random
designs are generated (if Random Designs option is used for initialization).
The size of the design space can be set individually for each input parameter. The
bounds of the design sub-space can be entered directly (absolute values) or
calculated by Isight by applying lower and upper bounds to the baseline value of
each parameter (relative to baseline).
Sampling data points needed for initialization of the Response Surface Model
approximations can be obtained using one of the available sampling methods in Isight.
Typical initialization mode for a Response Surface Model, if no previous data is
available, is Random Designs. In this case, Isight will generate the required number of
random designs inside the specified boundaries, and then run exact analysis for each of

those designs. Obtained data then are used for calculating polynomial coefficients of
the model. Least squares fit is used to calculate the coefficients.
The recommended number of sampling points for initialization is twice the number of
polynomial coefficients, which for a linear polynomial is (N+1), for a quadratic
polynomial is (N+1)(N+2)/2, for a cubic polynomial is (N+1)(N+2)/2 + N, and for a
quartic polynomial is (N+1)(N+2)/2 + 2N, where N is the number of input variables.
Proceed to one of the following topics:
“Polynomial Term Selection in RSM” on this page
“R2 Analysis of Response Surface Models,” on page 324
Polynomial Term Selection in RSM

Polynomial term selection in RSM has several benefits:
Improves prediction reliability of the model
Eliminates predictor variables with little or no effect on the output
Reduces variance of the model
Selects the best model when a limited number of design points are available

The basic idea of the polynomial term selection is as follows:
Given a set of k predictor variables X1, X2, X3,…,Xk, select a subset of p (p<k)
predictor variables that minimizes the Residual Sum of Squares:
In the case of RSM term selection, predictor variables are the polynomial terms, X1,
X2,…, X1^2, X2^2, …, X1*X2, etc. The best combination of the polynomial terms is
selected so that the Residual Sum of Squares is minimized. Since the residuals can be
non-zero only when the model has at least one degree of freedom, minimization of the
RSS implies that the maximum number of polynomial terms selected must be lower
than the number of design points used for the RSM. Otherwise the RSS will be exactly
zero and no term selection will be possible.
The four term selection methods available in Isight have the following features:
Sequential Replacement. This method is a variation of the Forward selection

algorithm and has the following steps:
start with the constant term, select the next best term
at every step of the forward selection, for every previously selected term find
the best replacement that will decrease the RSS and swap the variables
select the next best term and add it to the model
repeat the procedure until maximum allowed number of terms selected.
The Sequential Replacement algorithm does not guarantee the best model.
Stepwise Regression (Efroymson's algorithm). This method is a variation of the

Forward selection with the following steps:
at every step of the forward selection, add the next best term if it sufficiently
decreases the RSS using the following criterion

at every step of the forward selection, check if one of the selected terms can be
dropped without appreciably increasing the RSS using the following criterion
repeat the process until no more terms satisfy the first criterion or until the
maximum desired number of terms is selected
The values of “F-ratio-to-add-term” and “F-ratio-to-delete-term” are 4.0 by default

and can be controlled from the graphical user interface when creating a new RSM.
These values will affect the selection process. The Stepwise Regression algorithm
does not guarantee the best model.
Two-at-a-time Replacement. This method is a variation of the Forward selection

with the following steps:
at every step of the forward selection, consider all possible replacements of 1

or 2 terms from the previously selected terms
find the best replacement combination that will decrease the RSS and swap the
variables
select the next best term and add it to the model

repeat the procedure until maximum allowed number of terms selected
The Two-at-a-time Replacement algorithm is more expensive than the two

previous algorithms and has a much better chance of finding the best model.
Exhaustive Search. This method is a systematic approach to finding the best

combination of terms from all possible combinations. It has the following basic
steps:
generate all possible combinations of terms up to the maximum allowed
number of terms
calculate RSS values for all polynomials
select the best combination of terms to minimize the RSS
The Exhaustive Search algorithm is the most expensive one from the four
available. It guarantees finding the best model at the cost of a high computational

time. The number of design points and the number of selected terms will greatly
affect the computational cost, and can make this algorithm a non-viable option for
large data sets and a large number of inputs.
R2 Analysis of Response Surface Models

R2 analysis is a measure of how well the model polynomial approximates the actual
function at the design points used for its construction. The Response Surface Model
module of Isight will automatically perform R2 analysis of the approximated
functions, when the number of distinct designs used for the response surface model is
greater than the number of model coefficients. The R2 value of 1.00 indicates that
values of the model polynomial, and values of the response function, are identical at all
of the design points. Remember that it is always possible to perfectly fit N points using
a polynomial with N+1 coefficients. Thus, a perfect value of the R2 coefficient does
not necessarily indicate that the actual function will match the model polynomial
everywhere in the design space, unless the number of points used for analysis is
considerably greater (3 -10 times) than the number of polynomial coefficients.
Information about R2 analysis is reported inside the coefficients data for each output
polynomial.
DOE Technique Options

DOE technique options are available in the Approximation Wizard when the DOE
Matrix Sampling method is selected. Proceed to one of the following topics for more
information:
“Setting Data File Technique Options,” on page 325
“Setting Latin Hypercube Technique Options,” on page 326

“Setting Optimal Latin Hypercube Options,” on page 327
“Setting Orthogonal Array Technique Options,” on page 327
“Setting Parameter Study Technique Options,” on page 328

DOE Technique Options 325
Setting Data File Technique Options

The following options are available when the Data File technique is selected:
File. The first step in setting Data File technique options is to select the file that
you want to use with the technique. Click the Browse... button to specify the file
that contains the values you want to use. The Configure File Parameter dialog box
appears. Select the file to be used.
Note: A file parameter will be added to the component to represent this file,
allowing you to map in a completely new file at runtime.
Use Header Row. Select this check box if your data file has a header row
containing the factor names. Specify which row contains the names of your factors
by entering its corresponding number.
Data Starts on Row. Specify the row in your file where the data begins by
entering its corresponding number. If you are using a header row, the specified row
must be greater than the header row.
Format. Select Levels or Values. If Levels is selected, additional factor attributes

will be available (Lower, Upper, Relation, Baseline) to define how to calculate
values from the levels.
Store in model. Click this check box if you want the current file’s contents to be
stored in the model for use when the component executes. If this is not selected,
the component will attempt to access the specified file on the computer on which it
executes.

File contains responses. (Advanced Options...) Select this option if you do not
want the DOE component to actually execute an Isight subflow for each design
point, but to instead read the response values for each design point from a specified
file. The format of the file must be a first row with parameter names and each
subsequent row containing the values for the parameters for that design point. This
feature is useful for when you have a complete data set (input and output values)
already compiled and simply want to use DOE as a post-processing tool.
Data is transposed. (Advanced Options...) Select this check box if you want to
use a data file in which each row represents a set of values for the parameter whose
name is the first item in that row (thus, the file is “transposed” from the standard
format in which each column represents a parameter and its values). A transposed
data file must have the parameter name as the first item in the row (enclosed in
quotes if spaces exist), and each row must have the same number of values in it.
Setting Latin Hypercube Technique Options

The following options are available when the Optimal Latin Hypercube technique is
selected:
Number of Points. Enter the number of points that you want to study. For each
defined factor, the levels are defined by uniformly distributing this number of
points between specified lower and upper values. These levels are then randomly
combined with levels of the other factors to define each design point to execute.
Use a fixed seed. The seed can be fixed by clicking this check box and specifying
the seed manually in the corresponding text box. If this check box is not activated,
the seed is determined randomly.
Note: A fixed seed can also be set and used for the entire model. If a fixed seed is
set for the model and also defined separately in DOE, then the one in DOE will be
used. If a fixed seed is set for the model and this option is not selected, then the
sequence of random numbers will be based on the model’s random seed (and thus
is still reproducible). For information on setting a fixed seed, see “Using the
Configure and Run Options,” on page 32.

DOE Technique Options 327
Setting Optimal Latin Hypercube Options

The following options are available when the Optimal Latin Hypercube technique is
selected:
Number of Points. Enter the number of points that you want to study. For each
defined factor, the levels are defined by uniformly distributing this number of
points between specified lower and upper values. These levels are then randomly
combined with levels of the other factors to define each design point to execute.
Max Time to Optimize (minutes). Enter the maximum amount of time (in
minutes) that the component can optimize. Once this time limit is reached, the
optimization stops.
Use a fixed seed. The seed can be fixed by clicking this check box and specifying
the seed manually in the corresponding text box. If this check box is not activated,
the seed is determined randomly.
Note: A fixed seed can also be set and used for the entire model. If a fixed seed is
set for the model and also defined separately in DOE, then the one in DOE will be
used. If a fixed seed is set for the model and this option is not selected, then the
sequence of random numbers will be based on the model’s random seed (and thus
is still reproducible). For information on setting a fixed seed, see “Using the
Configure and Run Options,” on page 32.
Setting Orthogonal Array Technique Options

The following option is available when the Orthogonal Array technique is selected:
The Orthogonal Array technique allows you to select one of the following options from
the Array drop-down list to specify the array size (and thus, the resolution) to use for
the experiment:
2-Level: L8, L16, L32, L64, L128, L256
3-Level: L27, L81, L243
Mixed: L12, L18, L36, L54
Plackett-Burman: PB12, PB20, PB24, PB36

Only those arrays that are appropriate for the current number of factors (and number of
levels) will appear in this list.
Note: The Orthogonal Array technique will allow you to specify a mixed number of
levels for the factors, and will automatically use the appropriate array to accommodate
your settings, possibly modifying the basic structure of the array to ensure
orthogonality. You can always manually choose a larger array, if desired.
Setting Parameter Study Technique Options

The following option is available when the Parameter Study technique is selected:
Run baseline point. Select this option if you want an additional point to be executed in
which all factors are set to their Baseline values. Including a baseline design point
allows for the Parameter Study technique to be used exactly as a simple finite
differencing technique for sensitivity calculations (i.e., the effective difference caused
by each factor is independently varied by some small difference from a baseline
design).

329
C Correlation Map and Pareto Plot

Reference Information
This appendix provides information that may be helpful when using the Correlation
Map and Pareto plot. The appendix is divided into the following topics:
“Correlation Map Reference Information,” on page 330
“Pareto Plot Reference Information,” on page 331

330 Appendix C Correlation Map and Pareto Plot Reference Information
Correlation Map Reference Information

After executing a workflow, the Correlation Map tool will provide a graphical
representation of how the parameters for a selected component are related.
Using the data for any two parameters, two kinds of statistical correlations can be
calculated - the Pearson and Spearman correlations (also called linear and rank
correlations respectively). The Pearson, or linear, correlation is calculated as follows
for parameters X and Y:
The values of r will be between -1 (representing a perfect inverse linear correlation)

and 1 (representing a perfect direct linear correlation). Values of 0 or close to zero
signify a lack of correlation between the parameters.
For the Spearman, or rank, correlation, slight nonlinearity is removed by ranking the
parameter values from 1 to N for N values and replacing the parameter values with
their rank value. The ranking can be based on highest to lowest parameter values or
lowest to highest. The same correlation formulation is then applied to the ranked
parameter values, R and S, substituted for X and Y:
The Spearman correlation values are again between -1 and 1.
The Correlation Map displays correlations between parameters that are above a
selected/defined cutoff value. For more information, see “Working with the Filter
Options,” on page 277. The actual value for the Pearson linear correlation and
Spearman rank correlation is also displayed for each set of correlated parameters.

Pareto Plot Reference Information 331
Pareto Plot Reference Information

The ranking of effects presented in the Pareto plot is determined by ordering the scaled
and normalized coefficients of a standard least-squares 2nd-order polynomial fit to the
component's data. If sufficient data is available - at least (N+1)(N+2)/2 points, where N
is the number of inputs - and each input has at least three distinct levels/values, a full
2nd-order polynomial model, including all two-way interactions, is fit to the data. The
minimum number of points required is (N+1), resulting in a linear polynomial fit. If the
number of data points is between (N+1) and (N+1)(N+2)/2, a partial 2nd-order
polynomial is constructed (quadratic, two-way interaction terms added until no degrees
of freedom remain).
Before fitting the polynomial model, the input data is first scaled to range from -1 to 1
and the least squares fit is performed on this data. The scaling is performed so that the
contributions can be compared more fairly since both the magnitude of the factors and
the amount they were varied affect the data used in constructing the response surface
model. The model coefficients resulting from the least squares regression applied to the
scaled data are normalized by summing the coefficients and dividing each coefficient
by this sum of all coefficients. The Pareto plot is then an ordered bar chart of these
normalized coefficients, which represent the percent total effect on the response.

332 Appendix C Correlation Map and Pareto Plot Reference Information

333
Index
Numerics visual design tab 40

visualizing 182
32-bit vs. 64-bit 22, 57
3D graph options 198
B
A bit type, specifying 22, 57
accessing 21
approximations
actual vs. approximations outputs 209
C
analyzing errors 211
coefficient file 169 command line options 305
components 141 component info area 36
creating component title bar 30
automatic 145 configure and run options
default settings 142 name-value file format 37
previously saved file 169 using 32
user-defined 149 connection profiles
wizard 145 creating 136
deleting 221 overview 22
design search 203 types 23
editing 175 Contour graphs 188
graphs 188 copying
initializing 179 graphs 250
RBF model 312 tables 266
response surface model 319 correlation map
saving 220 accessing 274
symbol 104, 259 benefits 273
usage in Runtime Gateway 140 filtering 277
using at runtime 177 overview 273
viewing data 218

334 Index
reference 330 parameters, changing 270

viewing data 275 Pareto data 271
current job list 29 scatter plots 279
customizing graphs 240 viewing data 271
environment variables
FIPER_JVMPARMS 300
FIPER_TEMP 301
D execution
buttons 38
data analysis tab configure and run options 32
correlation map 273 controlling 31
engineering data mining tool 267 customizing options 32
overview 40 using the Runtime Gateway 32
two-dimensional scatter plots 279 exporting
data analysis tools 110 graph data 249
data file (DOE) technique 325 jobs 70
data sampling 224 parameter values 97
data sets 243, 262 table data 266
database lookup 34
dataflow tab 118
overview 39
using 118 F
design of experiments (DOE)
data file options 325 filtering 92
graphs 236 filtering data 110
latin hypercube options 326 FIPER_JVMPARMS variable 300
optimal latin hypercube options 327 FIPER_TEMP variable 301
orthogonal arrays options 327
parameter study options 328
parameters 99
tables 253 G
dynamic arrays 108
graphs
copying 250
creating 228
E customizing 240
data sets 243, 262
EDM see engineering data mining deleting 251
engineering data mining design of experiments (DOE) 236
accessing 268 exporting data 249
graph types 267 file parameters, viewing 247
introduction 267 Monte Carlo 235

Index 335
normalizing 250
options, changing 239
J
run grading 245
run number scroll bar 241 Job Database dialog box
SDI 237 opening 57
selecting points 246 standalone mode 57
six sigma 237 job details area 115
tab 41 jobs
Taguchi robust design 238 accessing the database 57
types available 229 columns on job list 79
updating 238 custom names, creating 33, 69
graphs overview 30 database tabs 80
graphs overview area 226 definition 31, 56
Grouping parameters (in component deleting 77
editors) 47 details area 115
exporting 70
importing 69
local database, defining 56
location of database 56
H opening 62
overview 56
history tab permissions (ACS only) 55, 73
color usage 105 re-execution criteria 68
dynamic arrays 108 removing from memory 72
features 104 re-running failed jobs 66
filtering data 110 Save to DB option 66
initializing from a prior run 107 searching for 58
overview 40, 103 selecting 72
sorting 110 stopping 64
stopping jobs that are running 64
I
K
importing
data from a file 123 keyboard shortcuts 302
jobs 69
parameter values 96
initializing a model from a prior run 107
interface layout 28 L
latin hypercube (DOE) technique 326
log button 30

336 Index
log file
accessing 115
P
copying contents 116
e-mailing 116 parameter study (DOE) technique 328
log filter 115 parameters
log tab 114 DOE 99
logging level button 33 exporting 97
LSF DRM history tab 103
enabling advanced options 50 importing 96
Monte Carlo 100
optimization 99
SDI 101
six sigma 101
M Taguchi robust design 102
parameters tab 40
menu bar 29, 292 filtering 92
model explorer 30 problem formulation 91
models usage 88
changes 20 viewing parameters 90
loading from command line 26 parameters, grouping/sorting in component
opening 23 editors 47
saving 27 pareto plots
Monte Carlo reference information 331
graphs 235 pause button 38
parameters 100 permissions for jobs (ACS only) 73
tables 254 preferences 41
problem formulation 91
purpose of interface 20
N
name-value file format 37 R
normalizing graphs 250
RBF model
in Isight 313
introduction 312
O re-executing a failed job
overview 66
optimal latin hypercube (DOE) technique 327 purpose and limitations 66
optimization parameters 99 runtime gateway 38
orthogonal array (DOE) technique 327 select job dialog box 67

Index 337
reports
automatic 130
T
manual 130
overview 128 tables
rerun (re-execute) button 38, 67 columns 259
resizable arrays 108 copying 266
response surface model creating 252
introduction 319 customizing 265
R2 analysis of response surface models 324 deleting 267
right-click options 85 design of experiments (DOE) 253
run grading 105, 245 exporting data 266
run number scroll bar 241, 260 filtering data 260
Monte Carlo 254
run number scroll bar 260
selecting points 260
six sigma 254
S sorting data 260
specialty types 253
saving results Taguchi robust design 255
to a results file 119 types 253
to a text file 120 updating 258
SDI Taguchi main effects viewer 283
graphs 237 Taguchi robust design
parameters 101 graphs 238
Searching in a Model 132 main effect viewers 283
Advanced 134 parameters 102
server information button 30 tables 255
shortcuts, keyboard 302 toolbar 29, 299
six sigma two-dimensional scatter plots 279
graphs 237
parameters 101
tables 254
sorting 110
Sorting parameters (in component editors) 47
U
stop button 38
summary tab 41, 111 updating graphs
accessing options 239
logarithmic axis options 232, 239
show grid lines option 232, 239

338 Index
V W
view run button 89 workflow options
viewing parameters 90 annotations 85
visual design tab 40 changing components 83
overview 82
process components 83
right-click menu 85
saving as image 85
workflow tab 39

Runtime Gateway

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Runtime Gateway

Uploaded by

Copyright:

Available Formats

Trademarks and Legal Notices

© Dassault Systèmes, 2009

Printed in the United States of America.

Offices and Representatives

Sales, Support, and Services

China Representative Offices

Complete contact information is available at http://www.simulia.com/locations/locations.html

Isight Runtime Gateway Guide

Isight Runtime Gateway Guide

Support for Academic Institutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

1 Using the Runtime Gateway Interface . . . . . . . . . . . . . . . . . . . . . . 19

Isight Runtime Gateway Guide

Saving Models and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Working With Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Understanding Graph, Table, and Other Data Analysis Options . . . . . . . . . . . . . . 87

Isight Runtime Gateway Guide

Using the Data Analysis Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Viewing the Dataflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118

Searching for a Component, Parameter, or File in a Model . . . . . . . . . . . . . . . . . . .132

2 Visual Design with Approximations . . . . . . . . . . . . . . . . . . . . . . . . 139

Editing an Existing Approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175

Isight Runtime Gateway Guide

Creating New Approximation Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Searching the Design Using Specified Criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Viewing Approximation Data After Initialization. . . . . . . . . . . . . . . . . . . . . . . . . . 218

3 Using Graphs, Tables, and Other Data Analysis Tools . . . . . . . . . 223

Isight Runtime Gateway Guide

Viewing Table Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259

Using the Engineering Data Mining Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267

Using the Correlation Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273

Using the Two-dimensional (2D) Scatter Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . .279

A Runtime Gateway Reference Information . . . . . . . . . . . . . . . . . . . 291

Toolbar Buttons and Other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299

Isight Runtime Gateway Guide

Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Command Line Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

B Approximation Reference Information . . . . . . . . . . . . . . . . . . . . . 311

DOE Technique Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

C Correlation Map and Pareto Plot Reference Information . . . . . . 329

Isight Runtime Gateway Guide

When used in conjunction with Fiper, an internet-based distributed framework is

Isight Runtime Gateway Guide

 Isight Development Guide

 Isight Getting Started Guide

 Isight Runtime Gateway Guide

 Fiper Installation and Configuration Guide - WebSphere and DB2

 Fiper Installation and Configuration Guide - WebSphere and Oracle

 Fiper Express Installation Guide

 Fiper Federation (B2B) Guide - WebSphere

 Fiper WebTop Guide

Conventions Used in This Book

Isight Runtime Gateway Guide

Isight Runtime Gateway Guide

Isight Runtime Gateway Guide

SIMULIA Online Support System

 Link to the SOSS

Isight Runtime Gateway Guide

Technical Engineering Support

 The type of computer on which you are running Isight.

 Any log files associated with the error.

 Workarounds or tests that you have already tried.

Isight Runtime Gateway Guide

Anonymous FTP Site

Contacting Technical Support

Isight Development Guide

Isight Getting Started Guide

Isight Runtime Gateway Guide

Fiper Installation and Configuration Guide - WebSphere and DB2

Fiper Installation and Configuration Guide - WebSphere and Oracle

Fiper Express Installation Guide

Fiper Federation (B2B) Guide - WebSphere

Fiper WebTop Guide

Link to the SOSS

The type of computer on which you are running Isight.

Any log files associated with the error.

Workarounds or tests that you have already tried.

“Using the Runtime Gateway,” on page 20

“Working With Jobs,” on page 56

“Understanding Graph, Table, and Other Data Analysis Options,” on page 87

“Viewing Parameter Information,” on page 88

“Using the Logs,” on page 113

“Viewing the Dataflow,” on page 118

“Saving Results,” on page 119

“Importing Data From a File,” on page 123

“Generating Reports,” on page 128

“Searching for a Component, Parameter, or File in a Model,” on page 132

“Creating an ACS Connection Profile,” on page 136

It automatically appears when a model is executed from the Design Gateway.

“Accessing the Runtime Gateway” on this page

“Understanding Connection Profiles,” on page 22

“Loading a Model From the Interface,” on page 23

“Loading a Model From the Command Line,” on page 26

“Understanding the Runtime Gateway Layout,” on page 28

“Controlling Execution,” on page 31

“Viewing Tabs in Separate Windows,” on page 41

“Setting Preferences,” on page 41

Execute the rt_gateway.exe file (or rt_gateway file on UNIX/Linux

“Opening a Model From the Disk” on this page

“Opening a Model From a Library” on this page