About the Isight Examples

The section describes the Isight examples and explains how to access them.

Isight includes a set of examples that show many of the Isight components and how to combine the components in useful ways.

Several of the examples include one or more Isight Simcode components and demonstrate how Isight can execute external programs and manage their input and output.

In some cases, the examples includes components that must be configured before execution. For example, if a model contains a Mail component, the address information must be entered or the component will not execute. You will need to open the component editor to configure the options. For more information about working with components, see the Isight Component Guide.

The complete set of files to run each example (model files, associated simulation codes, and data files) is installed when you install Isight. The example files are located in the following directory:

<Isight_install_directory>\<operating_system>\examples\models\

The examples are grouped into subdirectories according to the technique they illustrate.

Applications

The applications subdirectory contains models that show the usage of multiple components to form complete applications.

Examples are provided for the following applications:

  • AirplaneSizingDOE

  • I_Beam

  • SpectralAnalysis

  • SpringSamples

  • TestDataMatch

These examples have been fully annotated. In addition, complete explanations can be found in the component’s description properties. Each root component describes the example as a whole, while each child component describes the purpose and function of that component in the example.

Approximations

The approximations subdirectory contains a directory for each SIMULIA approximation technique, with at least one model in each directory to illustrate the technique.

Examples are provided for the following approximation techniques:

  • Cantilever Beam Automatic Approximation

  • Cantilever Beam Radial Basis Function (RBF) and Elliptical Basis Function (EBF) Approximation

  • Cantilever Beam Response Surface Approximation

  • Cantilever Beam Kriging Approximation

  • Cantilever Beam Chebyshev Orthogonal Polynomial Approximation

  • Approximation / Optimization Updating Loop

Components

The components subdirectory contains a directory for each SIMULIA-supplied component that has an example to demonstrate the component’s use.

Examples are provided for the following components:

  • Abaqus

  • ANSA

  • Calculator

  • CATIA V5

  • COM

  • Data Matching

  • DOE

  • Dymola

  • Excel

  • Exploration

  • Grid

  • GT-POWER

  • LS-DYNA

  • Mathcad

  • MATLAB

  • MSCPatran

  • Noise Analysis

  • Optimization

  • Pause

  • Script

  • Six Sigma

  • Taguchi

  • Target Solver

  • XML Parser

Features

The features subdirectory contains models that demonstrate specific features of Isight.

Examples are provided for the following features:

  • Model Comparison

  • Dynamic Modeling – Customization Scripts, Files, and Prologue

  • Database Lookup

  • Dynamic Arrays

  • Fastflow Tiered Execution

  • Subflow Parameter History – storing a history of a subflow parameter in a resizable array

  • Units

Postprocessing

The postprocessing subdirectory contains examples that demonstrate specific postprocessing capabilities.

Examples are provided for the following postprocessing capabilities:

  • Data Import

  • Visuals

Simcodes

The simcodes subdirectory contains all external programs used by the examples in the other subdirectories under the models directory.

The simcodes\src directory contains the source codes (in Fortran, C, and etc.) for these programs. The simcodes\bin directory contains a subdirectory named for each operating environment on which Isight is supported. Each subdirectory contains the actual executables for these programs for that operating environment.

Note: When an Isight example model is loaded into the Design Gateway from the installed examples directory, the path to the executables is added to your %PATH% automatically. If these executables are moved, the new location must be added to your %PATH%.