Statistics on Structures Tutorials

ANSYS, Inc. Release 2022 R2

Southpointe July 2022
2600 Ansys Drive
Canonsburg, PA 15317 ANSYS, Inc. and
ansysinfo@[Link] ANSYS Europe,
Ltd. are UL
[Link] registered ISO
(T) 724-746-3304 9001: 2015
(F) 724-514-9494 companies.
Copyright and Trademark Information

© 2022 ANSYS, Inc. Unauthorized use, distribution or duplication is prohibited.

ANSYS, Ansys Workbench, AUTODYN, CFX, FLUENT and any and all ANSYS, Inc. brand, product, service and feature
names, logos and slogans are registered trademarks or trademarks of ANSYS, Inc. or its subsidiaries located in the
United States or other countries. ICEM CFD is a trademark used by ANSYS, Inc. under license. CFX is a trademark
of Sony Corporation in Japan. All other brand, product, service and feature names or trademarks are the property
of their respective owners. FLEXlm and FLEXnet are trademarks of Flexera Software LLC.

Disclaimer Notice

THIS ANSYS SOFTWARE PRODUCT AND PROGRAM DOCUMENTATION INCLUDE TRADE SECRETS AND ARE
CONFIDENTIAL AND PROPRIETARY PRODUCTS OF ANSYS, INC., ITS SUBSIDIARIES, OR LICENSORS. The software
products and documentation are furnished by ANSYS, Inc., its subsidiaries, or affiliates under a software license
agreement that contains provisions concerning non-disclosure, copying, length and nature of use, compliance
with exporting laws, warranties, disclaimers, limitations of liability, and remedies, and other provisions. The software
products and documentation may be used, disclosed, transferred, or copied only in accordance with the terms
and conditions of that software license agreement.

ANSYS, Inc. and ANSYS Europe, Ltd. are UL registered ISO 9001: 2015 companies.

U.S. Government Rights

For U.S. Government users, except as specifically granted by the ANSYS, Inc. software license agreement, the use,
duplication, or disclosure by the United States Government is subject to restrictions stated in the ANSYS, Inc.
software license agreement and FAR 12.212 (for non-DOD licenses).

Third-Party Software

See the legal information in the product help files for the complete Legal Notice for ANSYS proprietary software
and third-party software. If you are unable to access the Legal Notice, contact ANSYS, Inc.

Published in the U.S.A.

Table of Contents
SoS Tutorials Overview ............................................................................................................................... 1
SoS Example Files ................................................................................................................................... 1
Basic SoS Tutorials ...................................................................................................................................... 3
Importing and Visualizing an FEM Mesh .................................................................................................. 3
Starting a New Project ...................................................................................................................... 3
Visualizing the Reference Mesh ......................................................................................................... 4
Importing Field and Scalar Data .............................................................................................................. 6
Importing Field Designs .................................................................................................................... 6
Inspecting Imported Field Data Samples ........................................................................................... 8
Importing Scalar Parameters ........................................................................................................... 10
Analyzing Imported Field Data .............................................................................................................. 11
Deactivating Designs with Eroded Elements .................................................................................... 12
Calculating Standard Statistical Estimators ...................................................................................... 12
Visualizing the Resulting Statistical Measures .................................................................................. 13
Creating and Analyzing Random Fields ................................................................................................. 14
Creating an Empirical Random Field Model ..................................................................................... 14
Creating a Synthetic Random Field Model ....................................................................................... 17
Creating a Synthetic Random Field Model When No Field Designs are Available ......................... 17
Creating a Synthetic Random Field Model When One to Five Field Designs are Available ............ 20
Creating and Analyzing Field-MOPs ....................................................................................................... 23
Creating a Field-MOP ...................................................................................................................... 23
Visualizing Field-CoP Results ........................................................................................................... 25
Visualizing a Field-MOP's Output Field Based on Any Input Parameter Set ........................................ 28
Analyzing a Field-MOP with optiSLang Postprocessing .................................................................... 28
Building a Field-MOP with a MOP Backend ................................................................................ 29
Opening a Field-MOP in optiSLang Postprocessing .................................................................... 29
Detecting and Deactivating Outliers in optiSLang Postprocessing ............................................. 30
Deactivating Outliers in SoS ............................................................................................................ 31
Exporting Scalar and Field Data ............................................................................................................. 31
Exporting Scalar Data to optiSLang ................................................................................................. 31
Exporting Scalar Data in CSV Format ............................................................................................... 33
Exporting Field Data Objects in CSV Format .................................................................................... 34
How-To SoS Tutorials ................................................................................................................................ 37
Importing Field Data from Ansys Mechanical ......................................................................................... 37
Setting Up the SoS Extension in Mechanical .................................................................................... 37
Preparing Data for Export in Mechanical .......................................................................................... 38
Preparing the Thermal Model .................................................................................................... 39
Preparing the Mechanical Model ............................................................................................... 40
Selecting Output Files Saved to optiSLang Design Directories .................................................... 42
Performing a DOE in optiSLang ....................................................................................................... 43
Setting Up a DOE in optiSLang .................................................................................................. 44
Preparing the DOE Data for SoS Import ..................................................................................... 45
Importing DOE Data into SoS .......................................................................................................... 46
Importing Scalar Data from a Third-Party DOE ....................................................................................... 48
Importing Scalar Data from an optiSLang DOE ...................................................................................... 48
Importing Field Data from an Unsupported Solver ................................................................................. 49
Using a Field as a Field-MOP Input to Generate RF Amplitudes in SoS ..................................................... 49
Generating Amplitudes from Random Field Data ............................................................................. 50
Verifying Random Field Approximation ........................................................................................... 50

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. iii
Statistics on Structures Tutorials

Using a Field as a Field-MOP Input to Generate RF Amplitudes in optiSLang ........................................... 50

Exporting the Data Needed to Run from the "AmplitudesFromField_SoS" Node in optiSLang ........... 51
Calculating and Using Random Field Amplitudes in a Field-MOP Evaluation Workflow ...................... 51
Performing Hot Spot Analysis ............................................................................................................... 52
Preparing the Database .................................................................................................................. 52
Identifying Hot Spots ...................................................................................................................... 53
Exporting Created Scalars to optiSLang ........................................................................................... 54
Performing Robustness Analysis in optiSLang Postprocessing .......................................................... 55
Identifying Maximum Likelihood in SoS .......................................................................................... 56
Identifying the Maximum of Selected Nodes and Elements .............................................................. 57
Synchronizing Selected Nodes and Elements .................................................................................. 58
Ansys Workbench Integration Tutorials ................................................................................................... 59
Exporting Field Data from Ansys Mechanical for Use in SoS and optiSLang ............................................. 59
Adding an Export results (SoS) Node ............................................................................................... 59
Configuring the Export results (SoS) Node ....................................................................................... 60
Using Exported Files in optiSLang ................................................................................................... 61
Creating Geometric Imperfections from a Synthetic Random Field in Ansys Mechanical ........................ 63
Creating a Synthetic Random Field .................................................................................................. 63
Configuring the Synthetic random field (SoS) Node ......................................................................... 64
Generating and Visualizing the Synthetic Random Field .................................................................. 65
Setting Advanced Options .............................................................................................................. 66
Configuring the Generate variations (SoS) Node .............................................................................. 66
Performing a Robustness Analysis in optiSLang ............................................................................... 68
Creating Geometric Imperfections from a Free-form Variation Field in Ansys Mechanical ....................... 69
Creating a Free-form Variation Field ................................................................................................ 69
Configuring the Free-form variation (SoS) Node .............................................................................. 70
Generating and Visualizing the Free-form Variation Field ................................................................. 71
optiSLang Integration Tutorials ............................................................................................................... 73
Analyzing 1D Signal Data Using a Signal-MOP in optiSLang ................................................................... 73
Reviewing the Simulation Model Description for the Wedge Splitting Test ....................................... 74
Setting Up the Simulation Solver Chain in optiSLang ....................................................................... 75
Parsing Input Parameters ................................................................................................................ 75
Defining Input Parameter Ranges .................................................................................................... 76
Defining Output and Reference Signals ........................................................................................... 77
Defining the Output Signal (Part 1) ........................................................................................... 77
Defining the Output Signal (Part 2) ........................................................................................... 77
Defining the Reference Signal (Part 1) ....................................................................................... 78
Defining the Reference Signal (Part 2) ....................................................................................... 79
Defining Signal Functions ............................................................................................................... 80
Defining Signal Functions (Part 1) ............................................................................................. 80
Defining Signal Functions (Part 2) ............................................................................................. 81
Defining the Optimization Objective ............................................................................................... 82
Defining the Solver Call ................................................................................................................... 82
Creating a Signal-MOP in optiSLang ................................................................................................ 84
Performing a Sensitivity Analysis ............................................................................................... 84
Viewing Sensitivity Analysis Results ........................................................................................... 86
Viewing Additional Sensitivity Results ....................................................................................... 89
Optimizing the Signal-MOP ............................................................................................................. 92
Adding the Optimization .......................................................................................................... 92
Setting Up and Running the Optimization ................................................................................. 93
Analyzing an Ansys Mechanical Project in optiSLang ............................................................................. 96

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
iv of ANSYS, Inc. and its subsidiaries and affiliates.
 Statistics on Structures Tutorials

Evaluating Field-MOPs in optiSLang ...................................................................................................... 98

Exporting the Field-MOP for Simulation .......................................................................................... 98
Using the "Generate_SoS" Node in optiSLang .................................................................................. 99
Analyzing 2D Performance Maps in optiSLang ..................................................................................... 101
Understanding the Valve Model .................................................................................................... 102
Creating a Nested DOE in optiSLang .............................................................................................. 103
Creating a 2D Performance Map Field-MOP ................................................................................... 107
Visualizing and Analyzing a 2D Performance Map Field-MOP ......................................................... 109
Advanced Field-MOP Tutorials ............................................................................................................... 113
Tuning Field-MOP Settings .................................................................................................................. 113
Improving the Field-MOP's Forecast Quality ........................................................................................ 115
Using Fields or Signals as Field-MOP Inputs ......................................................................................... 118
Creating an Empirical Random Field Model of a Temperature Field ................................................. 118
Creating a Field-MOP for a Stress Field with a Temperature Field as an Input ................................... 119
Using Named Selections ..................................................................................................................... 120
Setting Named Selections Imported Within the Reference Mesh .................................................... 120
Importing Named Selections from a CSV File ................................................................................. 122
Setting a Fixed Boundary for Mesh Morphing ................................................................................ 124
Exporting a Field-MOP as an FMU ........................................................................................................ 126
Exporting a Field-MOP as an FMU .................................................................................................. 126
Importing the FMU into optiSLang Using the "FMU_SoS" Integration Node .................................... 131
Performing a Sensitivity Analysis with the FMU .............................................................................. 132
Evaluating Gasket Tightness ................................................................................................................ 134
Identifying the Contact Tightness Algorithm ................................................................................. 135
Importing Simulation Data and Creating Field-MOPs ..................................................................... 135
Exporting the Custom Analysis Workflow as an FMU ...................................................................... 138
Executing the Exported FMU ......................................................................................................... 141
Measurements and Noise Tutorials ........................................................................................................ 143
Using RPCA (Robust Principal Component Analysis) to Filter Noise ...................................................... 143
Importing and Analyzing Measured Geometries .................................................................................. 147
Importing Measurements ............................................................................................................. 148
Analyzing Measurements .............................................................................................................. 152
Creating Imperfect Geometries ........................................................................................................... 153
Preparing Statistical Shape Models ................................................................................................ 153
Configuring SoS as a Solver ........................................................................................................... 154
Performing Uncertainty Quantification Based on Measured Geometries ............................................... 157
Summary of the Solution Steps for the Uncertainty Quantification ................................................. 158
Preparing the Mesh of the Nominal CAD Geometry ....................................................................... 159
Importing the Mesh Data File and STL Scan File into SoS ................................................................ 162
Using the Morphing Script in a Mechanical Solve ........................................................................... 165
Observing Differences Between the Nominal Geometry and Real Geometry .................................. 168
Aligning the STL and CAD Geometry Files in SpaceClaim ............................................................... 169
Applying Displacement of Nodes of a Mesh by Measurement on Another Geometry ............................ 170
Setting Up the Workbench Project and Loading the ACT Plugin ..................................................... 170
Editing the Mechanical Model and Generating the New "Geometry" .............................................. 171

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. v
 Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
vi of ANSYS, Inc. and its subsidiaries and affiliates.
SoS Tutorials Overview
Tutorials for SoS are organized into these categories:

• Basic SoS Tutorials (p. 3)

• How-To SoS Tutorials (p. 37)

• Ansys Workbench Integration Tutorials (p. 59)

• optiSLang Integration Tutorials (p. 73)

• Advanced Field-MOP Tutorials (p. 113)

• Measurements and Noise Tutorials (p. 143)

SoS Example Files

All examples and tutorials assume that you have downloaded and extracted SoS example files.

To download and extract these files:

1. Click here or select Help → Download Example Files to download the file [Link].

2. Use an application such as 7-Zip to extract the files in this ZIP file to whatever location you
prefer.

3. Remember the directory path to these files.

Note:

This guide assumes that you have extracted SoS example files to a root folder named
examples. When you see /examples in a file path, navigate to the root folder to
which you extracted these files.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 1
 Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
2 of ANSYS, Inc. and its subsidiaries and affiliates.
Basic SoS Tutorials
If you are new to SoS, begin with these basic tutorials for learning how to use SoS:
Importing and Visualizing an FEM Mesh
Importing Field and Scalar Data
Analyzing Imported Field Data
Creating and Analyzing Random Fields
Creating and Analyzing Field-MOPs
Exporting Scalar and Field Data

Note:

These tutorials should be completed in the order in which they are listed. They
demonstrate the four fundamental steps of an SoS analysis:

1. Import the mesh.

2. Import the data.

3. Analyze the imported data.

4. Create a field-MOP.

Importing and Visualizing an FEM Mesh

Field data is always defined on a unique reference mesh. Thus, importing and visualizing a mesh are
the mandatory first steps of any data analysis in SoS.

This multi-part basic tutorial consists of procedures for:

Starting a New Project
Visualizing the Reference Mesh

Starting a New Project

To start a new SoS project:

1. Start SoS.

2. In the Welcome to Statistics on Structures window, select Start a new project and click Next.

3. Click the folder icon to select a file.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 3
Basic SoS Tutorials

4. From the list of available mesh file types, select LS-DYNA Dynain files (*k *dynain*).

For information about this file type, see Importing LS-DYNA Input Files in the Statistics on Structures
User's Guide.

5. Navigate to examples\lsdyna\metal_forming__eroded_elements\sampling, select

the mesh file ref-mesh.k, and click Open.

6. In the Welcome to Statistics on Structures window, supply a project name and click Finish.

7. Verify that the FEM mesh is imported successfully.

Note:

SoS supports 1D and 2D grid meshes.

• You use 1D grid meshes to analyze scalar-valued time series signals. For more
information, see Analyzing 1D Signal Data Using a Signal-MOP in
optiSLang (p. 73).

• You use 2D grid meshes to analyze performance maps. For more information,
see Analyzing 2D Performance Maps in optiSLang (p. 101).

You can now visualize the reference mesh.

Visualizing the Reference Mesh

In the 3D visualization, inspect and rotate the reference mesh by dragging it with your mouse cursor.
This image shows the imported mesh and the Manage views inspector selected in the Inspectors
window:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
4 of ANSYS, Inc. and its subsidiaries and affiliates.
 Importing and Visualizing an FEM Mesh

This next image shows a wireframe visualization with topological edges. You can see that Wireframe,
edges has been selected in the Mesh inspector.

You can now import field and scalar data.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 5
Basic SoS Tutorials

Importing Field and Scalar Data

This multi-part basic tutorial assumes that you have imported and visualized an FEM mesh as described
in Importing and Visualizing an FEM Mesh (p. 3) and are now ready for:
Importing Field Designs
Inspecting Imported Field Data Samples
Importing Scalar Parameters

Note:

The source of your field data can be empirical measurements, simulation results, or both.

Importing Field Designs

To import field designs that were created in a design of experiments (DOE):

1. Select File → Process multiple designs → Import field designs.

2. On the Reference design page, click Add file.

3. From the list of available file types, select LS-PrePost output files (*.k *.res *.txt).

For information about this file type, see LS-PrePost Files in the Statistics on Structures User's Guide.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
6 of ANSYS, Inc. and its subsidiaries and affiliates.
 Importing Field and Scalar Data

4. Navigate to
examples\lsdyna\metal_forming__eroded_elements\sampling\Design0001\NW,
select the simulation result files plastic_strain.k and shell_thickness.k, and click
Open.

The files are added to the Files to parse list.

5. Select the Enforce unique idents check box.

6. Ensure the Mesh mapper list is set to Compatible.

7. In the Data to import table, edit the Imported ident values for the two objects, choosing short
but useful name such as pstrain and thickness.

To import multiple field designs at once, SoS expects the following directory structure, with each
design directory containing files of the same name.
.
+-- Design0001 # reference design directory

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 7
Basic SoS Tutorials

| +-- file1 # file containing field or mesh data

| +-- file2
| +-- ...
+-- Design0002
| +-- file1
| +-- file2
| +-- ...
+-- Design0003
...

This is the directory structure that is created when running a DOE in Ansys optiSLang.

Note:

To directly compare field data of different designs, all field data must be defined
on the unique reference mesh. SoS provides mesh morphing and mapping
algorithms to handle geometric variations between designs.

8. Click Next.

The Design directories page appears. SoS automatically detects the number of design directories
based on the design directory format string (a Perl regular expression).

9. Click Filter by optiSLang to exclude failed designs from the import.

The optiSLang BIN file (optislang_bin_file.bin) contains information on which designs

failed.

10. Navigate to examples\lsdyna\metal_forming__eroded_elements\sampling, select

the file optislang_bin_file.bin, and click Open.

11. Click Finish to import the field designs.

Note:

When Number of designs in parallel set to 0, all available CPU cores are used.

You can now inspect the imported field data samples.

Inspecting Imported Field Data Samples

Once the field designs are imported, the data table displays two field quantities of data type element:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
8 of ANSYS, Inc. and its subsidiaries and affiliates.
 Importing Field and Scalar Data

To inspect field data samples:

1. If the data table is not currently displayed, select Window → Data table.

2. From the Data objects toggles, click the Fields button.

3. In the list of individual samples, select any entry.

4. Note the associated data object information and observe the number of missing items.

Individual samples displayed with a green dot have zero missing items.

5. Press the Enter key to visualize the selected sample.

In this example, missing items are cracks due to large plastic strain and small shell thickness. SoS can
handle missing items, using an interpolated value based on the nearest neighbors if necessary.

This image shows pstrain for design 6. Plastic strain displays in color. Missing items (cracks) display
in black.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 9
Basic SoS Tutorials

You can now import scalar parameters.

Importing Scalar Parameters

During the DOE, each field design is simulated with a set of varying scalar input parameters and an
optiSLang BIN file is created. For more information, see Importing Scalar Data from an optiSLang
DOE (p. 48).

To import the scalar parameters associated with each field design from the optiSLang BIN file:

1. Select File → Import data → Import scalars from optiSLang .bin.

2. Click the folder icon to select a file.

3. In the dialog box that opens, navigate to

examples\lsdyna\metal_forming__eroded_elements\sampling, select the file
optislang_bin_file.bin, and click Open.

4. Select the check boxes for importing both input parameters and scalar responses and click
OK.

SoS imports the field and scalar data.

5. If the data table is not currently displayed, select Window → Data table.

6. From the Data objects toggles, click the Results and Fields buttons to turn these views off
(buttons are gray) and click the Scalars button to turn the view on (button is blue).

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
10 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing Imported Field Data

7. Select a quantity from the Scalar quantities list.

8. Observe the values displayed in the list of individual objects for this scalar value.

For example, when E_Modul is selected, values like these are shown:

You can now analyze imported field data. You can save the data to an SoS database (SDB) by selecting
File → Save database and entering a database file name.

Analyzing Imported Field Data

This multi-part basic tutorial assumes that you have imported field data defined on a unique mesh as
described in Importing Field and Scalar Data (p. 6) and are now ready for:
Deactivating Designs with Eroded Elements
Calculating Standard Statistical Estimators

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 11
Basic SoS Tutorials

Visualizing the Resulting Statistical Measures

Note:

Statistical measures across multiple field designs are themselves fields. For example, the
mean field indicates the average of all field designs at every point in space.

Deactivating Designs with Eroded Elements

Designs with too many eroded elements can lead to questionable results. To exclude designs above
a certain threshold from further analysis:

1. Select Edit → Deactivate designs with eroded elements.

2. Set Largest acceptable number of eroded data to 80 and click OK.

3. Verify the log message indicating the number of deactivated designs.

4. If the data table is not currently displayed, select Window → Data table.

5. From the Data objects toggles, ensure the Scalars view is toggled on (button is blue) and
the Results and Fields views are off (buttons are gray).

6. In the list of individual scalar data objects, observe which check boxes are now cleared.

You are now ready to calculate standard statistical estimators.

Calculating Standard Statistical Estimators

Statistical measures are calculated using active samples only.

To calculate standard statistical estimators:

1. If the data table is not currently displayed, select Window → Data table.

2. From the Field quanties list, select any number of field quantities for analysis.

For example, select both pstrain and thickness.

3. Select Statistics → Standard estimators → Mean.

4. Select Statistics → Standard estimators → Standard deviation.

5. Select Statistics → Standard estimators → Coefficient of Variation (CoV).

6. From the Data objects toggles, click the Scalars button to turn this view off (button is gray)
and click the Results button to turn the view on (button is blue).

The data table now contains the resulting field data objects for the field quantities that you selected.
The statistical measures are themselves fields. Every single mesh element in space is evaluated
separately across all active field designs. This evaluation is valid because all field designs are defined
on the unique reference mesh.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
12 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing Imported Field Data

You can now visualize the resulting statistical measures.

Visualizing the Resulting Statistical Measures

To extract all information, visualize the resulting statistical measures:

1. From the list of data objects, select the resulting statistical measures and press the Enter key.

SoS adds stamps in the gray area of the visualization.

2. In the Manage views inspector, click the icon for showing two scenes at one time ( ),
splitting the scenes horizontally.

3. Drag a scene from the ribbon at the bottom into the Empty scene pane.

4. Rotate the view to your liking.

5. In the Manage views inspector, click Sync camera.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 13
Basic SoS Tutorials

Differences in plastic strain between field designs are strongly localized in space. Any meaningful
analysis of the reliability for the deep drawing process would be impossible from single-value measures
alone. With this visualization of the resulting fields of statistical measures, identifying specific locations
of interest to look at for optimizing the deep drawing process is straightforward.

You can now create and analyze random fields (p. 14) and field-MOPs (p. 23). If desired, you can first
select File → Save database to save your data to your SoS database.

Creating and Analyzing Random Fields

This multi-part basic tutorial assumes that you have imported field and scalar data as described in
Importing Field and Scalar Data (p. 6) and learned more about statistical analysis and result visualization
as described in Analyzing Imported Field Data (p. 11). You are now ready for:
Creating an Empirical Random Field Model
Creating a Synthetic Random Field Model

Creating an Empirical Random Field Model

In the DOE, 100 field designs have been calculated with a set of varying input parameters. An empirical
random field model captures as much of the variation observed in the 100 field designs as possible
with the smallest number of scalar random field amplitudes.

To create an empirical random field model:

1. Select Field data models → Random fields → Create empirical random field model.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
14 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating and Analyzing Random Fields

While this example has you accept the defaults shown, to get a more accurate random field
model, you would increase the values for Desired explained variation (%) and Maximum
number of shapes.

Random field decomposition is cut off when reaching the value specified for Maximum
number of shapes, without achieving the desired explained variation percentage. In the
worst case, if the field designs are entirely uncorrelated, 100 shapes are required to represent
the 100 field designs with 100% accuracy.

2. Click OK to accept the defaults.

In the data table, SoS adds new data objects to the database:

• SoS adds one field data object for each shape and the total explained variation.

• SoS adds a scalar quantity for each random field amplitude.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 15
Basic SoS Tutorials

3. If the data table is not currently displayed, select Window → Data table.

4. From the list of data objects, select shape[1] and variation and press the Enter key to
visualize.

The following image shows a strongly localized effect. Of the variation observed in the field designs,
approximately 55% is explained by the first shape of the empirical random field.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
16 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating and Analyzing Random Fields

This next image shows the variation explained by the empirical random field. Comparing this plot to
the variance plot of all field designs allows you to see that the explained variation is low only at
locations where the variance is low. This is typical for empirical random fields and acceptable behavior.

Creating a Synthetic Random Field Model

The options for creating a synthetic random field model depends on whether field designs are available:
Creating a Synthetic Random Field Model When No Field Designs are Available
Creating a Synthetic Random Field Model When One to Five Field Designs are Available

Creating a Synthetic Random Field Model When No Field Designs are Available
To create a synthetic random field model when no field designs are available:

1. If the data table is not currently displayed, select Window → Data table.

2. In the data table, select the field quantity pstrain.

3. Select Field data models → Random fields → Create synthetic random field model.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 17
Basic SoS Tutorials

4. In the dialog box that opens, for Ident, type synthetic_rf:

5.

6. For Correlation length, select relative and then decrease the absolute value to 20.00 %
to create a larger number of more localized shapes.

A relative correlation length of 20.00 % is a good starting value.

7. Click OK.

SoS adds one field data object for each shape and the total explained variation.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
18 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating and Analyzing Random Fields

8. From the list of data objects, select the synthetic_rf values for shape[1] and variation
and then press the Enter key to visualize.

The following image shows the general shape that is created when there is no prior knowledge
from field designs.

This next image shows the variation explained by the synthetic random field declines near the
edges of the structure.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 19
Basic SoS Tutorials

Creating a Synthetic Random Field Model When One to Five Field Designs are
Available
To create a synthetic random field model when one to five field designs are available:

1. If the data table is not currently displayed, select Window → Data table.

2. In the data table, select the field quantity pstrain.

3. Select Field data models → Random fields → Create synthetic random field model.

4. In the dialog box that opens:

a. For Ident, type synthetic_rf_1design.

b. For Data type, select Element.

c. For Correlation length, select relative and set the absolute value to 20.00 %.

d. For Mean value, select Use database object and select the first field design as if
only one measurement or simulation was performed.

Note:

If a small number of field designs is available, you can estimate the

standard deviation and provide additional information to the
synthetic random field model.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
20 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating and Analyzing Random Fields

The dialog box should now look like this:

5. Click OK.

SoS adds one field data object for each shape and the total explained variation.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 21
Basic SoS Tutorials

6. In the Choose visible data window for the 3D visualization, select Element data, synthet-
ic_fr_1design, and Random field.

7. Click Add & apply to new scene.

In the following image, the mean value for the synthetic random field is modeled after the single
available field design. If you move the sliders, you can see that the shapes of the empirical random
field are still general because no variation can be inferred from a single design.

Assume that you created a synthetic random field with the mean and standard deviation estimated
from five field designs:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
22 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating and Analyzing Field-MOPs

This next image shows that with more field designs available to provide mean and standard deviation
estimates, shapes reflecting the observed variation can be created.

If desired, you can select File → Save database to save your data to your SoS database.

Creating and Analyzing Field-MOPs

This multi-part basic tutorial assumes that you have imported field and scalar data as described in
Importing Field and Scalar Data (p. 6) and learned more about statistical analysis and result visualization
in Analyzing Imported Field Data (p. 11). You are now ready for:
Creating a Field-MOP
Visualizing Field-CoP Results
Visualizing a Field-MOP's Output Field Based on Any Input Parameter Set
Analyzing a Field-MOP with optiSLang Postprocessing
Deactivating Outliers in SoS

Creating a Field-MOP
In the DOE, 100 field designs have been calculated with a set of varying input parameters. A field-MOP
is a reduced order model (ROM) for predicting the resulting field quantity for a new set of input

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 23
Basic SoS Tutorials

parameters. During field-MOP creation, SoS calculates Field-CoP[Total] (Coefficient of Prognosis),

indicating the model's forecast quality.

Note:

To ensure that the Field-MOP is created, deactivate incomplete designs. Select Edit →
Deactivate incomplete designs.

To create a field-MOP:

1. Select Field data models → Field-MOP → Create Field-MOP.

In the dialog box that opens, the Select training data tab is active by default.

2. Drag and drop the following quantity identifiers into the Input (selectable) area:

• E_Modul

• blank_thickness_1

• plastic_failure

• poisson_ratio

• real_mat_abs_1

• real_mat_ord_1

• rho

• yield_stress

3. Drag and drop the following quantity identifiers into the Output area:

• pstrain

• thickness

Because this example uses all default settings, no changes are necessary on the Settings tab.

4. Click OK.

Once SoS completes the calculations, it adds new result field quantities to the data table.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
24 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating and Analyzing Field-MOPs

F-CoP[Total]

The percentage value representing a variance-weighted average of the field model's forecast
quality. Values above 80% are acceptable, and values above 90% are good. When the value for
Field-CoP[Total] is low, the level of prediction might be good locally. However, you should
carefully analyze the Field-CoP's distribution in space.

F-CoP[input parameter]

The percentage value representing a variance-weighted average of the input parameter's explained
variance of the resulting output field. Higher values indicate a higher sensitivity of the field model
with respect to the input parameter.

most sensitive inputs

The most sensitive input parameter at each node or element on the mesh. If the value is unknown,
the value for Field-CoP[Total] is too low to make a valid prediction. If the value is undefined,
multiple inputs have exactly the same sensitivities.

mean[FMOP]

The local average of the output field when varying the field model's input parameters.

sigma[FMOP]

The local standard deviation of the output field when varying the field model's input parameters.

You can now visualize the field-CoP results.

Visualizing Field-CoP Results

To visualize field-CoP results:

1. If the data table is not currently displayed, select Window → Data table.

2. For the field quantity pstrain, select the most sensitive inputs result and press the Enter key to
visualize.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 25
Basic SoS Tutorials

The plot of the most sensitive inputs provides a good overview of the Field-MOP's behavior,
allowing you to identify:

• Areas of importance for each input parameter

• Areas with low values for Field-CoP[Total], indicating little confidence in the field-MOP's
ability to make a valid prediction

For example, if you select the result Field-CoP[Total] and press the Enter key, you can see the
most sensitive inputs for the field quantity pstrain.

3. Select result field quantities from the data table and press the Enter key to visualize.

You can change the palette bounds in the visualization toolbox by clicking Decoration inspector

. In the following plot for the result Field-CoP[Total], the minimum for Field-CoP[Total] is set to

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
26 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating and Analyzing Field-MOPs

80%. The plot now clearly shows significant local variations, depicting areas of acceptable Field-
CoP[Total].

This next plot of the standard deviation of the field-MOP shows where the largest changes occur
when the input parameters are varied. A good field-MOP has high values for F-CoP[Total] at the
same points in space.

In this tutorial, Field-CoP[Total] shows significant local variation. Depending on the mesh areas of
interest, the field model may be useable or require further refinement. The tutorial in Analyzing
Imported Field Data (p. 11), you excluded field designs with too many eroded elements, reducing

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 27
Basic SoS Tutorials

the number of field designs from which to build the Field-MOP to 70. In cases like this, the preferred
solution is to add more designs to the DOE and rebuild the Field-MOP from the larger dataset.

Note:

While F-CoP values clearly identify one material parameter dominating the field model's
output on average, the plot of most sensitive inputs tells a much more nuanced
story, taking local variations into account.

You can visualize a field-MOP's output field based on any input parameter set.

Visualizing a Field-MOP's Output Field Based on Any Input Parameter Set

To visualize a field-MOP's output field based on any input parameter set:

1. In the Choose visible data window in the 3D visualization, select Element data, pstrain,
and Field-MOP.

2. Click Add & apply to new scene.

3. In the Field data model inspector, set the values for the input parameters by adjusting the
sliders.

Analyzing a Field-MOP with optiSLang Postprocessing

Field-MOPs can be analyzed with optiSLang postprocessing. Because outlier detection is a particularly
useful feature, it is the focus in these topics:
Building a Field-MOP with a MOP Backend
Opening a Field-MOP in optiSLang Postprocessing

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
28 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating and Analyzing Field-MOPs

Detecting and Deactivating Outliers in optiSLang Postprocessing

Note:

The file extension *.ombd must be associated with the optiSLang postprocessing
executable ([Link])

Building a Field-MOP with a MOP Backend

To build a field-MOP with a MOP backend:

1. Select Edit → Activate all objects.

2. Select Field data models → Field-MOP → Create Field-MOP.

In the dialog box that opens, the Select training data tab is active by default.

3. Drag and drop the desired quantity identifiers into the Input (selectable) area.

4. Drag and drop the quantity identifier pstrain into the Output area.

5. On the Settings tab, select Use MOP backend and accept the default MOP settings.

6. Click OK.

7. To indicate that existing field-MOPs can be overwritten, click OK.

Once SoS completes the calculations, you can open the field-MOP in optiSLang postprocessing.

Opening a Field-MOP in optiSLang Postprocessing

To open a field-MOP in optiSLang postprocessing:

1. If the data table is not currently displayed, select Window → Data table.

2. In the data table, select a field quantity with an existing field-MOP.

3. To generate a CoP matrix, select Field data models → Field-MOP → Show Field-MOP
subspace interpolation in optiSLang.

4. If prompted, select the optiSLang postprocessing app in which to open the file.

This CoP matrix shows that the first few random field amplitudes contribute the most to the
field-MOP's variation. Any deviation from this pattern is an indication of model failure.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 29
Basic SoS Tutorials

You can now detect outliers.

Detecting and Deactivating Outliers in optiSLang Postprocessing

To detect and deactivate outliers in optiSLang postprocessing:

1. In the residual plot, select the outliers.

2. Right-click and select Deactivate.

3. To rebuild the MOP with an improved CoP value, select MOP → Create and update
database → Create and update database.

You can now deactivate outliers in SoS

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
30 of ANSYS, Inc. and its subsidiaries and affiliates.
 Exporting Scalar and Field Data

Deactivating Outliers in SoS

To deactivate outliers in SoS:

1. In the list of available objects, clear the check boxes for the respective field data objects.

2. Select Edit → Deactivate incomplete designs.

3. After deactivating the outliers, repeat all statistical analysis.

If desired, you can select File → Save database to save your data to your SoS database.

Exporting Scalar and Field Data

This multi-part basic tutorial can be completed independently. You can use the SoS database that you
created by following the previous basic tutorials or load the SoS database sos_demo.sdb in the
Examples folder. This tutorial consists of procedures for:
Exporting Scalar Data to optiSLang
Exporting Scalar Data in CSV Format
Exporting Field Data Objects in CSV Format

Exporting Scalar Data to optiSLang

To export scalar data to optiSLang:

1. Select the scalar quantities to export.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 31
Basic SoS Tutorials

2. Select File → Export data → Export scalars to optiSLang.

3. For Input file, open the file optislang_bin_file.bin in

examples\lsdyna\metal_forming__eroded_elements\sampling

Note:

SoS modifies an existing optiSLang BIN file because it is not aware of all
features of this file and cannot create one from start to finish.

4. For Output file, specify the file path and name to which to save the file and click Save.

Descriptions follow for the three check boxes:

Export generated scalars only

Selecting this check box excludes exporting once again scalar data produced by a
DOE in optiSLang previously imported from a BIN file. For more information, see
Importing Field and Scalar Data (p. 6).

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
32 of ANSYS, Inc. and its subsidiaries and affiliates.
 Exporting Scalar and Field Data

Export only active samples

Selecting this check box excludes exporting deactivated scalar data objects, such as
having deactivated designs with too many eroded elements. You use the central
data table to activate and deactivate individual data objects.

Test compatibility of input file

Selecting this check box checks whether previously imported scalar data objects are
compatible with the selected input BIN file.

5. Once settings are finalized, click OK.

6. Use a Postprocessing node in optiSLang to open the output BIN file and analyze the exported
scalar data.

Exporting Scalar Data in CSV Format

To export scalar data in CSV format:

1. Select the scalar quantities to export.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 33
Basic SoS Tutorials

2. Select File → Export selected scalar quantities to CSV.

3. For Output file, supply the file path and name to which to save the file and click Save.

For this example, you can accept the defaults for all other options.

4. Click OK.

The image shows CSV output of scalar data opened in Excel. There is one column for each scalar data
quantity. The first column denotes the design identifier.

Exporting Field Data Objects in CSV Format

To export field data objects in CSV format:

1. Select the field data objects to export.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
34 of ANSYS, Inc. and its subsidiaries and affiliates.
 Exporting Scalar and Field Data

2. Select File → Export data → Export selected field data objects to CSV.

3. For Output file, supply the file path and name to which to save the file and click Save.

4. Click OK.

The image shows CSV output of field data objects opened in Excel. There is one column for each field
data object. The first header row denotes the quantity identifier, and the second header row denotes
the design identifier.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 35
 Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
36 of ANSYS, Inc. and its subsidiaries and affiliates.
How-To SoS Tutorials
The tutorials in this section show how to accomplish these tasks in SoS:
Importing Field Data from Ansys Mechanical
Importing Scalar Data from a Third-Party DOE
Importing Scalar Data from an optiSLang DOE
Importing Field Data from an Unsupported Solver
Using a Field as a Field-MOP Input to Generate RF Amplitudes in SoS
Using a Field as a Field-MOP Input to Generate RF Amplitudes in optiSLang
Performing Hot Spot Analysis

How-to tutorials assume that you are already familiar with the SoS interface and have completed the
basic tutorials (p. 3).

Importing Field Data from Ansys Mechanical

This multi-part tutorial shows how to import field data from Ansys Mechanical:
Setting Up the SoS Extension in Mechanical
Preparing Data for Export in Mechanical
Performing a DOE in optiSLang
Importing DOE Data into SoS

Note:

This tutorial requires installations of both Ansys optiSLang and Mechanical.

Setting Up the SoS Extension in Mechanical

To set up data export in Mechanical using the SoS extension:

1. Open Ansys Workbench.

2. From the ACT Start Page, open the graphic-based version of the Extension Manager. For
more information, see Extension Manager in the ACT Developer's Guide.

3. Ensure that the SoS and optiSLang extensions are installed and loaded.

4. Close the ACT Start Page.

You can now prepare data for export in Mechanical.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 37
How-To SoS Tutorials

Preparing Data for Export in Mechanical

To prepare data for export in Mechanical:

1. In Ansys Workbench, open the archive file [Link] in examples\ansys\circuit.

2. Rename the project to circuit_to_sos and save it as a project file in the same folder.

3. If you see a message indicating that the SoS extension will be upgraded permanently when
you save the project, click OK.

4. Open the Parameter Set bar and verify the parameters.

• The mechanical simulation has three input parameters.

• The thermal simulation has three input parameters.

• The static structural simulation has one output parameter: Equivalent Stress Maximum.

5. Close the Parameter Set bar.

• The mechanical simulation has three input parameters.

• The thermal simulation has three input parameters.

• There is one output parameter: Equivalent Stress Maximum.

You can now complete these preparation procedures:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
38 of ANSYS, Inc. and its subsidiaries and affiliates.
 Importing Field Data from Ansys Mechanical

Preparing the Thermal Model

Preparing the Mechanical Model
Selecting Output Files Saved to optiSLang Design Directories

Preparing the Thermal Model

To prepare the thermal model:

1. Open the thermal model, solve it, and check the solution.

2. On the SoS tab for the extension, select Export → Thermal results.

An Export results (SoS) node is added to the Solution block.

3. Use the box select method to select all bodies in the model view.

4. Configure the Export results (SoS) node:

a. Save all 23 bodies for the mesh part.

b. Export all 23 bodies to SoS

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 39
How-To SoS Tutorials

5. Generate the data of the Export results (SoS) node.

6. In the Outline view, right-click the Solution node and select Open Solver Files Directory
to see the files that have been created.

7. In the generated SoS_Export folder, verify the export of the mesh and field data:

• The file sos_mesh.cdb contains the exported mesh part.

• The file sos_results.k is the LS-PrePost output file contains the exported field
data. For information on supported LS-PrePost keywords, see LS-PrePost Files in the
Statistics on Structures User's Guide.

Preparing the Mechanical Model

To prepare the Mechanical model:

1. Open the Mechanical model, solve it, and check the solutions for Total Deformation and
Equivalent Stress.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
40 of ANSYS, Inc. and its subsidiaries and affiliates.
 Importing Field Data from Ansys Mechanical

2. On the SoS tab for the extension, select Export → Mechanical results.

An Export results (SoS) node is added under Solution.

3. Use the box select method to select all bodies in the model view.

4. Configure the Export results (SoS) node:

a. Save all 23 bodies for the mesh part.

b. Export all 23 bodies to SoS

c. Export Displacements, Stress (principal), and Stress (von Mises) as node values.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 41
How-To SoS Tutorials

5. Save the project and close Workbench.

In the folder for the project:

• dp0\SYS-1\MECH\SoS_Export contains the thermal results.

• dp0\SYS-2\MECH\SoS_Export contains the mechanical results.

You can now select output files that are saved to optiSLang design directories.

Selecting Output Files Saved to optiSLang Design Directories

To select output files that are saved to optiSLang design directories:

1. From under optiSLang Integrations in the Workbench Toolbox, insert a Data Send system
in the Project Schematic.

2. Connect the Solution cell in the Static Structural system to the Setup cell in the Data
Send system.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
42 of ANSYS, Inc. and its subsidiaries and affiliates.
 Importing Field Data from Ansys Mechanical

3. In the Data Send system, double-click the Setup cell.

4. Select the files sos_mesh.cdb and sos_results.k files for export:

5. Click OK.

You can now perform a DOE in optiSLang.

Performing a DOE in optiSLang

This multi-part tutorial shows how to perform a DOE in optiSLang:
Setting Up a DOE in optiSLang
Preparing the DOE Data for SoS Import

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 43
How-To SoS Tutorials

Setting Up a DOE in optiSLang

To set up a DOE in optiSLang:

1. Start a new project in optiSLang and start the Solver wizard.

2. Under Integrations, select Ansys Workbench.

3. On the Ansys Workbench connection page, open the Workbench project file
circuit_to_sos.wbpj that you saved previously, making sure that the correct
Workbench executable is used.

4. Click Next.

5. On the Integrated Solver Settings page:

a. Drag all inputs to the Parameter list.

b. Drag the output variable Equivalent Stress Maximum to the Response list.

6. Set the parameter ranges as shown in this image:

Tip:

For quicker entry, you can type the range in the format min:max. For
example, you would type -10:40 for the first entry.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
44 of ANSYS, Inc. and its subsidiaries and affiliates.
 Importing Field Data from Ansys Mechanical

7. Complete the Solver wizard.

8. Save and run the optiSLang project.

9. Drag the Sensitivity wizard onto the solver chain's title bar.

10. In the Sensitivity wizard, do the following:

a. Set Sampling method to Advanced Latin Hypercube Sampling.

b. On the Additional options page, clear the Create MOP check box.

You will create a field-MOP with SoS later.

c. Complete the Sensitivity wizard.

11. Save and run the optiSLang project.

Running the DOE takes some time. Once the DOE is complete, postprocessing opens so that you
can check the results for plausibility.

You are now ready to prepare the DOE data for SoS import.

Preparing the DOE Data for SoS Import

To prepare the DOE data for SoS import:

1. Drag a Convert_OMDB_to_BIN_SoS add-in node onto the optiSLang workbench.

2. Connect the Postprocessing node's OMDBPath output to the Convert_OMDB_to_BIN_SoS

node's IPath input.

3. Save and run the optiSLang project.

A BIN file is created in the optiSLang project directory, next to the OMDB file. This BIN file
can be imported with SoS.

4. Save and close the optiSLang project.

You can now import the prepared DOE data into SoS.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 45
How-To SoS Tutorials

Importing DOE Data into SoS

To import DOE data prepared in optiSLang into SoS:

1. Start a new SoS project.

2. Set the file sos_mesh.cdb as the reference mesh:

a. Select File → Mesh → Set reference mesh.

b. For the file format, select Ansys Mechanical input files.

c. Open the file sos_mesh.cdb in the optiSLang project directory

(circuit_doe.opd\Sensitivity\Design0001\dp0\SYS-1\MECH\SoS_Export).

3. Set a named selection:

a. Select File → Mesh → Set reference named selection.

b. Set nodes used for statistics/models to SOS_DATA_NODES.

c. Set elements used for statistics/models to SOS_ELEMENT_NODES.

These named selections contain the nodes and elements on the printed circuit board's surface
only. Subsequent analysis in SoS is performed on these named selections.

4. Select File → Process multiple designs → Import field designs.

5. In the Import designs wizard, do the following:

a. Add the result files of the mechanical and thermal simulation.

b. Set the file format to LS-PrePost output files:

• circuit_doe.opd\Sensitivity\Design0001\dp0\SYS-1\MECH\SoS_Export\sos_results

• circuit_doe.opd\Sensitivity\Design0001\dp0\SYS-2\MECH\SoS_Export\sos_results

c. Set Path of reference design to circuit_doe.opd\Sensitivity\Design0001.

d. Select all field data quantities for import and complete the Import designs wizard:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
46 of ANSYS, Inc. and its subsidiaries and affiliates.
 Importing Field Data from Ansys Mechanical

6. Select File → Import data → Import scalars from optiSLang.

7. Open circuit_doe.opd\[Link] and import the input parameters.

8. Verify successful import of all field designs and scalar input parameters.

9. To support the tutorials in Advanced Field-MOP Tutorials (p. 113), execute the script for
calculating logarithmic equivalent stress and adding it as a new field quantity identifier
LOGSEQV:

a. Copy this script.

local inputs = [Link]([Link]():nodeData()):
filterByQuantityIdent("SEQV"):samples():active() -- get all active designs of SEQV
for i=1,inputs:size() do -- loop over all selected data objects
local seqv = inputs[i-1] -- get the i-th data object
local design = seqv:identRef():design() -- get the design ident of the current object
local seqv_data = seqv:getData() -- get the data vector of the current object
local logseqv_data = seqv_data:CW():Log(); -- apply the logarithm to all entries in the dat
local logseqv = [Link](
[Link](), logseqv_data, true) -- create a new data object (true=is sample)
local new_ident = [Link](design, "LOGSEQV") -- define the ident of the new object
[Link]():nodeDataRef():insert( new_ident, logseqv) -- insert new object into database
end

b. Paste the script into the SoS command line as shown.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 47
How-To SoS Tutorials

c. Press the Enter key.

You have finished the DOE data import. You can either move on to the next tutorial or jump to the
tutorials in Advanced Field-MOP Tutorials (p. 113).

Importing Scalar Data from a Third-Party DOE

You can import scalar data from text files in CSV format into SoS. For more information, see CSV Files
in the Statistics on Structures User's Guide.

To import scalar data in CSV format:

1. In an SoS project with a loaded reference mesh, select File → Import data → Import scalars
from CSV.

2. Open the CSV or TXT file containing your scalar data.

SoS attempts to automatically detect the delimiter, adjusting it as necessary.

An example of scalar data in CSV format follows. The design number column (#) is optional.
#,MyParameter,MySecondParameter
1,3.14,6.62e-34
2,2.718,137.035999

Importing Scalar Data from an optiSLang DOE

To extract scalar input parameters and responses from an optiSLang postprocessing OMBD database
file and import them into SoS:

1. Connect the OMDBPath slot of a DOE to the IPath slot of a Convert_OMDB_to_BIN_SoS node
and run the project.

2. In an SoS project with a loaded reference mesh, select File → Import data → Import scalars from
optiSLang .bin.

3. Open the BIN file created in step 1, which is located in the optiSLang project's working directory.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
48 of ANSYS, Inc. and its subsidiaries and affiliates.
 Using a Field as a Field-MOP Input to Generate RF Amplitudes in SoS

Importing Field Data from an Unsupported Solver

SoS supports numerous file formats. For a list of supported formats, see SoS File Format Specifications
in the Statistics on Structures User's Guide.

To import multiple field designs at once:

1. Select File → Process multiple designs → Import field designs.

2. Supply SoS with:

• The mesh for the connectivity description

• An optional list of nodes and elements defining named selections

• The actual field data associated to node or element identifiers

For more information, see Importing Multiple Field Designs in the Statistics on Structures User's Guide.

If your solver's native file format is unsupported, consider converting your files to a supported format
or to text-based CSV files. Many solver programs support conversion to a solver format that SoS supports.
SoS also supports multiple text-based formats for importing field data. For more information, see
Importing Field Data from CSV Files in the Statistics on Structures User's Guide.

An example follows of a CSV file with field data.

#MyFieldData,MyOtherFieldData,MyThirdField
,,
1,0.1,314
5,0.1,-512

Note that to import multiple field designs at once, SoS requires the following folder structure: .
+-- Design0001 # reference design directory
| +-- file1 # file containing field or mesh data
| +-- file2
| +-- ...
+-- Design0002
| +-- file1
| +-- file2
| +-- ...
+-- Design0003
...

Using a Field as a Field-MOP Input to Generate RF Amplitudes in SoS

A field or signal quantity of interest may depend on other fields or signals. For the field of interest, you
can create a field-MOP that takes a field as an input.

With a random field model of the input field, you can represent a particular realization of the input field
with a small number of scalar random field amplitude parameters. You can then use these parameters
directly as field-MOP inputs.

Note:

A field quantity with an existing random field is required.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 49
How-To SoS Tutorials

This multi-part tutorial consists of procedures for:

Generating Amplitudes from Random Field Data
Verifying Random Field Approximation

Generating Amplitudes from Random Field Data

To generate amplitudes from random field data:

1. Import field designs for a field quantity with an existing random field model.

2. From the list of field quantities, select this quantity.

3. Select Field data models → Approximate from imported data → Amplitudes from random
field data.

SoS adds new scalar random field amplitude to the database that you can use as scalar inputs for
field-MOP creation or evaluation.

• To create a field-MOP, select Field data models Field-MOP Create Field-MOP.

• To evaluate a field-MOP, select Field data models → Approximate from imported data →
Field-MOP from inputs.

Once a field-MOP is created or evaluated, you can verify random field approximation.

Verifying Random Field Approximation

If the random field model's total explained variation is below 100%, the reduction from field design
to random field amplitudes is an approximation. Consequently, you should verify the accuracy of the
reverse conversion, from random field amplitudes to field design.

To verify random field approximation:

1. Select all random field amplitudes created previously.

2. Select Field data models → Approximate from imported data → Random field from
amplitudes.

SoS adds the following field data objects to the database:

• Imported field designs, for which random field amplitudes have been calculated

• Approximated field designs, which were calculated during the reverse conversion

3. Select individual field data objects for direct comparison and then select Statistics → Errors
and differences → Compute relative error.

Using a Field as a Field-MOP Input to Generate RF Amplitudes in optiSLang

A field or signal quantity of interest may depend on other fields or signals. For the field of interest, you
can create a field-MOP that takes a field as an input.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
50 of ANSYS, Inc. and its subsidiaries and affiliates.
 Using a Field as a Field-MOP Input to Generate RF Amplitudes in optiSLang

With a random field model of the input field, you can represent a particular realization of the input field
with a small number of scalar random field amplitude parameters. You can then use these parameters
directly as field-MOP inputs.

The AmplitudesFromField_SoS optiSLang node allows you to calculate a field design's scalar random
field amplitudes from within an optiSLang workflow. The node reads the field design's data from a file.
For a list, see SoS File Format Specifications in the Statistics on Structures User's Guide.

Note:

A field quantity with an existing random field is required.

This multi-part tutorial consists of procedures for:

Exporting the Data Needed to Run from the "AmplitudesFromField_SoS" Node in optiSLang
Calculating and Using Random Field Amplitudes in a Field-MOP Evaluation Workflow

Exporting the Data Needed to Run from the "AmplitudesFromField_SoS"

Node in optiSLang
To export the data needed to run from the AmplitudesFromField_SoS node in optiSLang:

1. Select File → Export for simulation → Generate amplitudes from fields in optiSLang.

2. Add the file containing the field data for which to calculate random field amplitudes.

Detected field data objects are shown in the Data to import list.

Note:

The imported identifier must be equal to the identifier of the existing random field
model.

You can now calculate and use random field amplitudes in a field-MOP evaluation workflow.

Calculating and Using Random Field Amplitudes in a Field-MOP Evaluation

Workflow
An image of a field-MOP evaluation workflow follows. This system reads an input field from a file,
takes additional field-MOP input parameters, and writes an output field file.

This workflow accomplishes these steps:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 51
How-To SoS Tutorials

1. Creates a field data file to be read by the AmplitudesFromField_SoS node.

2. The AmplitudesFromField_SoS node:

• Reads the field data file

• Calculates random field amplitudes

• Registers the random field amplitudes areas as output slots

3. The Generate_SoS node:

• Evaluates a field-MOP taking the random field amplitudes (and additional scalar
parameters) as inputs

• Writes the resulting field to a file

• Registers the random field amplitudes areas as input slots and the additional scalar
inputs as parameters

Performing Hot Spot Analysis

Hot spots are mesh locations where the analyzed field quantity eclipses a threshold or reaches an
extremum. This multi-part tutorial shows how to identify and analyze hot spots on a field quantity by:
Preparing the Database
Identifying Hot Spots
Exporting Created Scalars to optiSLang
Performing Robustness Analysis in optiSLang Postprocessing
Identifying Maximum Likelihood in SoS
Identifying the Maximum of Selected Nodes and Elements
Synchronizing Selected Nodes and Elements

Preparing the Database

This topic uses the metal-forming example without any eroded elements that is created in the basic
tutorial Deactivating Designs with Eroded Elements (p. 12). After opening this database, prepare it
as follows:

1. Select File → Mesh → Set reference mesh.

2. In examples\lsdyna\metal_forming\deep_drawing.opd\Robustness, select
the LS-DYNA Dynain file reference_mesh.k.

3. Select File → Process multiple designs → Import field designs.

4. On the Reference design page, click Add file.

5. In
examples\lsdyna\metal_forming\deep_drawing.opd\Robustness\Design0001\out,
select the LS-DYNA Dynain file plastic_strain.k.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
52 of ANSYS, Inc. and its subsidiaries and affiliates.
 Performing Hot Spot Analysis

6. Complete the field design import.

You can now identify hot spots.

Identifying Hot Spots

To identify hot spots:

1. Select the field quantity pstrain.

2. Select Statistics → Quantiles and probabilities → Quantile and calculate the quantile probability
for pstrain at 0.95 (95%).

3. Switch to the visualization view.

4. In the Decoration inspector, set the minimum and maximum palette bounds to 0.38 to visualize
the calculated 95% quantile field.

At the locations in red, 95% of all field designs have a plastic strain higher than 0.38 units.

5. In the Selection inspector, select the five elements with either the largest values or largest values
of all local maxima.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 53
How-To SoS Tutorials

6. Click Create scalars.

SoS adds five scalar quantities to the database that contain the plastic strain values of the selected
elements for each field design.

You can now export the created scalars to optiSLang.

Exporting Created Scalars to optiSLang

To export the created scalars to optiSLang:

1. Select File → Export data → Export scalars to optiSLang.

2. For Input file, select Robustness_osl3.bin in

examples\lsdyna\metal_forming\deep_drawing.opd\Robustness.

3. Select an output file of your choice.

4. Ensure that the Export generated scalars only check box is checked.

5. Click OK.

You can now perform robustness analysis in optiSLang.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
54 of ANSYS, Inc. and its subsidiaries and affiliates.
 Performing Hot Spot Analysis

Performing Robustness Analysis in optiSLang Postprocessing

To perform robust analysis in optiSLang:

1. In optiSLang, open the exported BIN file with an MOP node.

2. Run the project and open the MOP node's postprocessing.

3. Observe the sensitivity of the field pstrain at the five exported elements with respect to the
most important input parameters.

4. At one of the exported elements, view a histogram with fitted probability density function
for the field pstrain.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 55
How-To SoS Tutorials

You can now identify the maximum likelihood in SoS.

Identifying Maximum Likelihood in SoS

To identify the maximum likelihood in SoS:

1. Select Statistics → Quantiles and probabilities → Probability of being maximum.

2. Switch to the visualization view.

3. In the Decoration inspector, set the maximum palette bounds to 0.0001.

When varying input parameters, the maximum plastic strain is observed at entirely different
locations.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
56 of ANSYS, Inc. and its subsidiaries and affiliates.
 Performing Hot Spot Analysis

You can now identify the maximum of selected nodes and elements.

Identifying the Maximum of Selected Nodes and Elements

To identify the maximum of selected nodes and elements:

1. Increase the number of elements to be selected.

2. Press and hold the Ctrl key while clicking and dragging to select elements.

3. Click Extract Max to add to the database a scalar data object that contains the maximum
plastic strain within the selection elements for each field design.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 57
How-To SoS Tutorials

You can now synchronize selected nodes and elements.

Synchronizing Selected Nodes and Elements

To synchronize selected nodes and elements when displaying two or more plots:

1. In the 95% quantile plot, select the maxima.

2. Click Sync selection to select the same elements in the other visible plots.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
58 of ANSYS, Inc. and its subsidiaries and affiliates.
Ansys Workbench Integration Tutorials
The tutorials in this section assume that you are already familiar with the SoS basic tutorials and how-to
tutorials. These tutorials show how to use Ansys integrations and assume that both the SoS and optiSLang
extensions are installed and loaded:
Exporting Field Data from Ansys Mechanical for Use in SoS and optiSLang
Creating Geometric Imperfections from a Synthetic Random Field in Ansys Mechanical
Creating Geometric Imperfections from a Free-form Variation Field in Ansys Mechanical

Exporting Field Data from Ansys Mechanical for Use in SoS and optiSLang
This multi-part tutorial shows how to export field data from Ansys Mechanical for use in SoS and
optiSLang:
Adding an Export results (SoS) Node
Configuring the Export results (SoS) Node
Using Exported Files in optiSLang

Adding an Export results (SoS) Node

To add an Export results (SoS) node:

1. In Ansys Workbench, open the archive file simple_cube.wbpz in

examples\ansys\simple_cube.

2. Rename the project to simple_cube_tutorial and save it as a project file in the same
folder.

3. If you see a message indicating that the SoS extension will be upgraded permanently when
you save the project, click OK.

This project contains a Static Structural system that calculates stress and deformation.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 59
Ansys Workbench Integration Tutorials

4. Open the model in Mechanical by double-clicking the Model cell or right-click the Model
cell and select Edit from the context menu.

Alternatively, you can complete this step using the Setup cell.

5. In the Mechanical application window, complete the analysis using the application's tools
and features.

6. On the Mechanical ribbon, switch to the SoS tab.

7. Select Export → Mechanical results.

The Export results (SoS) node is added to the Solution block.

You can now configure this node.

Configuring the Export results (SoS) Node

To configure the details for the Export results (SoS) node:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
60 of ANSYS, Inc. and its subsidiaries and affiliates.
 Exporting Field Data from Ansys Mechanical for Use in SoS and optiSLang

1. For Data saved for mesh part, set a named selection to define the field data to export.

2. For Mesh part to be exported to SoS, set a named selection to use the mesh of this named
selection as the reference mesh in SoS.

3. To save computation time, partially export the mesh.

The exported mesh part must fully contain the named selection used for data export.

4. For Data to export, select the field data that you want to export.

5. In the Outline view, right-click the Export results (SoS) node and click Generate.

6. To see the files that have been created, right-click the Solution node and select Open Solver
Files Directory.

7. In the generated folder SoS_Export, verify the export of the mesh and field data:

• The file sos_mesh.cdb contains the exported mesh part.

• The file sos_results.k is the LS-PrePost output file containing the exported field
data. For information on supported LS-PrePost keywords, see LS-PrePost Files in the
Statistics on Structures User's Guide.

8. Close the Mechanical model.

You can now use the exported files in optiSLang.

Using Exported Files in optiSLang

You use the Data Send system in the optiSLang Workbench extension to tell optiSLang which files
need to be copied to the design directory when calling and solving the Workbench project from
within optiSLang, such as during a DOE.

To use an exported file in optiSLang:

1. From the optiSlang Integrations group in the Workbench Toolbox, drag a Data Send system
onto the Project Schematic.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 61
Ansys Workbench Integration Tutorials

2. Connect the Solution cell in the Static Structural system to the Setup cell in the Data Send
system:

3. Double-click the Setup cell in the Data Send system.

4. Select the files in the folder SoS_Export:

5. Click OK

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
62 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating Geometric Imperfections from a Synthetic Random Field in Ansys Mechanical

Creating Geometric Imperfections from a Synthetic Random Field in

Ansys Mechanical
This multi-part tutorial, which assumes that you are familiar with Mechanical, shows how to create
geometric imperfections on parts of a model's surface in Ansys Mechanical using the SoS extension.
The tutorial uses a synthetic random field to introduce geometry displacements on a named selection
of surfaces. The variation of the field of geometric imperfections is controlled with a number of scalar
parameters, which are added to the parameter list of the Mechanical model.

This example simulates the stress field in a simple steel cube. The cube is assumed to be permanently
attached to a solid horizontal surface. A constant uniform force acts perpendicular to one side. The
cube's bottom face forms a fixed support. The flat geometry of the surface on which the constant
uniform force acts is modified by the synthetic random field.

This tutorial consists of:

Creating a Synthetic Random Field
Configuring the Synthetic random field (SoS) Node
Generating and Visualizing the Synthetic Random Field
Setting Advanced Options
Configuring the Generate variations (SoS) Node
Performing a Robustness Analysis in optiSLang

Creating a Synthetic Random Field

To create a synthetic random field:

1. In Ansys Workbench, open the archive file simple_cube.wbpz in

examples\ansys\simple_cube.

2. Rename the project file as simple_cube_tutorial2 and save it in the same folder.

3. If you see a message indicating that the SoS extension will be upgraded permanently when
you save the project, click OK.

This project contains a Static Structural system that calculates stress and deformation.

4. Set up and solve the Mechanical model.

This model contains named selections.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 63
Ansys Workbench Integration Tutorials

5. From the SoS tab for the extension, select Create → Synthetic random field for geometry.

A Synthetic random field (SoS) node is added to the system.

You can now configure this node.

Configuring the Synthetic random field (SoS) Node

In the details for the Synthetic random field (SoS) node:

1. Set Boundary to be parametrized to the named selection TopSurf.

Geometric imperfections are created on this surface.

2. Set Fixed boundary to the named selection BottomSurf.

A fixed boundary must be defined as SoS performs mesh or grid morphing in reference to
this fixed part of the mesh or grid.

Note:

Best practice is to ensure that there are free nodes between the fixed and
parametrized boundary. This helps with a smooth transition from the fixed
parts to the morphed parts of the geometry.

3. Set Mesh part to be exported to SoS to the named selection Body.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
64 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating Geometric Imperfections from a Synthetic Random Field in Ansys Mechanical

Geometric imperfections are created on this surface.

Tip:

To save computation time in SoS, export a substructure.

4. Set Correlation length to 0.001 m.

5. Set Standard deviation of geometric variation to 0.002 m.

You can now generate and visualize the synthetic random field.

Generating and Visualizing the Synthetic Random Field

To generate and visualize the synthetic random field:

1. Right-click the Synthetic random field (SoS) node and select Generate.

2. In the details for the Synthetic random field (SoS) node, under Visualization, set Visible
variation shape index (0=mean) to a scatter shape of your choice.

This image shows the first four and mean scatter shapes of the synthetic random field.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 65
Ansys Workbench Integration Tutorials

You can now set some advanced options.

Setting Advanced Options

In the details for the Synthetic random field (SoS) node, set these advanced options:

Use mesh stabilization

Setting this option to True makes the mesh morphing more robust, allowing you to create larger
deformations. The mesh is stabilized iteratively to avoid element distortions that are too large.
Computation time may increase substantially.

Test on mesh distortion

Setting this option to True has SoS perform a strict test for excessive mesh distortion before
calling the Mechanical solver. Using this option avoids starting unnecessary long-running
simulations.

Note:

This test is stricter than Mechanical's test.

Move nodes along

Setting this option to Boundary normal applies mesh morphing perpendicular to the boundary.

You can now configure the Generate variations (SoS) node.

Configuring the Generate variations (SoS) Node

In the details for the Generate variations (SoS) node:

1. Under Input parameters, select the amplitude values of your choice.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
66 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating Geometric Imperfections from a Synthetic Random Field in Ansys Mechanical

The synthetic random field of imperfections calculated are visualized after solving the project.

Caution:

Large amplitude magnitudes (greater than 1) may lead to failed mesh

morphing.

2. Set the check boxes for the first five shape amplitude parameters.

This registers them in the Workbench Parameter Set, making them available for
parametrization in optiSLang.

Note:

Selecting more amplitude parameters leads to a more detailed variation of

geometric imperfections.

3. Solve the model.

This image shows a mesh morphed according to the generated synthetic random field of
distortions.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 67
Ansys Workbench Integration Tutorials

4. Save and close your Workbench project.

You can now perform a robustness analysis in optiSLang.

Performing a Robustness Analysis in optiSLang

To perform a robustness analysis in optiSLang:

1. In an optiSLang project, add a Parametric System and place Ansys Workbench in it:

2. Add parameters and responses:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
68 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating Geometric Imperfections from a Free-form Variation Field in Ansys
Mechanical

Creating Geometric Imperfections from a Free-form Variation Field in

Ansys Mechanical
This multi-part tutorial, which assumes that you are familiar with Mechanical, shows how to create
geometric imperfections on parts of a model's surface in Ansys Mechanical using the SoS extension.
The tutorial uses a free-form variation field to introduce geometry displacements on a named selection
of surfaces. The variation of the field of geometric imperfections is controlled with a number of scalar
parameters, which are added to the parameter list of the Mechanical model.

This example simulates the stress field in a simple steel cube. The cube is assumed to be permanently
attached to a solid horizontal surface. A constant uniform force acts perpendicular to one side. The
cube's bottom face forms a fixed support. The flat geometry of the surface on which the constant
uniform force acts is modified by the synthetic random field.

This tutorial consists of:

Creating a Free-form Variation Field
Configuring the Free-form variation (SoS) Node
Generating and Visualizing the Free-form Variation Field

Creating a Free-form Variation Field

To create a free-form variation field:

1. In Ansys Workbench, open the archive file simple_cube.wbpz in

examples\ansys\simple_cube.

2. Rename the project file as simple_cube_tutorial3 and save it in the same folder.

3. If you see a message indicating that the SoS extension will be upgraded permanently when
you save the project, click OK.

This project contains a Static Structural system that calculates stress and deformation.

4. Set up and solve the Mechanical model.

This model contains named selections:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 69
Ansys Workbench Integration Tutorials

5. From the SoS tab for the extension, select Create → Free-form variation field for geometry.

A Free-form variation (SoS) node is added to the system.

You can now configure this node.

Configuring the Free-form variation (SoS) Node

In the details of the Free-form variation (SoS) node:

1. Set Boundary to be parametrized to the named selection TopSurf.

Geometric imperfections are created on this surface.

2. Set Fixed boundary to the named selection BottomSurf.

A fixed boundary must be defined as SoS performs mesh or grid morphing in reference to
this fixed part of the mesh or grid.

Note:

Best practice is to ensure that there are free nodes between the fixed and
parametrized boundary. This helps with a smooth transition from the fixed
parts to the morphed parts of the geometry.

3. Set Mesh part to be exported to SoS to the named selection Body.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
70 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating Geometric Imperfections from a Free-form Variation Field in Ansys
Mechanical

Geometric imperfections are created on this surface.

Tip:

To save computation time in SoS, export a substructure.

4. Set Magnitude of free variation (if scale factor = 1) to 0.002.

5. Under Advanced options, set these options:

Constant variation

Use a scatter shape with magnitude at every point on the parametrized boundary,
which is useful for inflating or shrinking the geometry.

Use mesh stabilization

Setting this option to True makes the mesh morphing more robust, allowing you to
create larger deformations. The mesh is stabilized iteratively to avoid element
distortions that are too large. Computation time may increase substantially.

Test on mesh distortion

Setting this option to TrueSoS performs a strict test for excessive mesh distortion
before the Mechanical solver is called. Use this for safety to avoid starting unnecessary
long-running simulations.

Note:

This test is stricter than Mechanical's test.

Move nodes along

Setting this option to Boundary normal applies mesh morphing perpendicular to

the boundary.

You can now generate and visualize the free-form variation field.

Generating and Visualizing the Free-form Variation Field

To generate and visualize the free-form variation field:

1. Right-click the Free-form variation (SoS) node and select Generate.

2. Select a scatter shape of your choice for visualization.

This image shows resulting scatter shapes when using a normalized (top row) or isotropic (bottom
row) shape of variation patterns:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 71
Ansys Workbench Integration Tutorials

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
72 of ANSYS, Inc. and its subsidiaries and affiliates.
optiSLang Integration Tutorials
The tutorials in this section assume that you are already familiar with Basic SoS Tutorials (p. 3) and
How-To SoS Tutorials (p. 37) and that you are also familiar with optiSLang.

Note:

Before starting, you must enable beta features in optiSLang by selecting View → Beta
Modules.

These tutorials show how to use optiSLang integrations:

Analyzing 1D Signal Data Using a Signal-MOP in optiSLang
Analyzing an Ansys Mechanical Project in optiSLang
Evaluating Field-MOPs in optiSLang
Analyzing 2D Performance Maps in optiSLang

Analyzing 1D Signal Data Using a Signal-MOP in optiSLang

This multi-part tutorial shows how to analyze 1D signal data using a Signal-MOP in optiSLang:
Reviewing the Simulation Model Description for the Wedge Splitting Test
Setting Up the Simulation Solver Chain in optiSLang
Parsing Input Parameters
Defining Input Parameter Ranges
Defining Output and Reference Signals
Defining Signal Functions
Defining the Optimization Objective
Defining the Solver Call
Creating a Signal-MOP in optiSLang
Optimizing the Signal-MOP

Note:

To complete this tutorial, the optiSLang example files in wedge_splitting_example.zip

must be downloaded and extracted to a root folder. Click here to download this ZIP file and
then extract the files. The file paths shown for these optiSLang example files assume that
you have extracted them to a root folder named wedge_splitting_example. You must
navigate to the folder to which you extracted them.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 73
optiSLang Integration Tutorials

Reviewing the Simulation Model Description for the Wedge Splitting Test
For this example, a wedge splitting test has been conducted, resulting in an empirically measured
normal force vs. crack width curve. A 2D linear elastic finite element simulation model with six scalar
input parameters has been developed. This tutorial shows to calibrate the model's input parameters
so that the model's output signal matches as closely as possible the empirical data.

This image shows the wedge splitting test schematic, with normal force F.

This next image shows a plot of normal force versus crack width. The measured data is from
experiments and simulation output.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
74 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 1D Signal Data Using a Signal-MOP in optiSLang

Model parameters are:

• Young's modulus

• Poisson's ratio

• Tensile strength

• Fracture energy

• Shape parameter

• Shape parameter

This next image shows the bilinear softening model for crack interface elements.

Now that you understand the wedge splitting test, you can set up the simulation solver chain in
optiSLang.

Setting Up the Simulation Solver Chain in optiSLang

To set up the simulation solver chain in optiSLang:

1. Create a new project in optiSLang.

2. Start the Solver wizard and insert a text-based solver.

3. Open the optiSLang example file wedge_splitting.s in

wedge_splitting_example\03_further_examples\wedge_splitting\text_based.

You can now parse input parameters.

Parsing Input Parameters

To parse input parameters:

1. Highlight lines 28 through 33.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 75
optiSLang Integration Tutorials

2. Click AutoParametrize.

All possible values are highlighted.

3. For Name, type the name of the parameter to add.

For example, type Emod to add the first of the six parameters shown in this image.

4. Click Add

5. Repeat steps 3 and 4 to add the five other parameters shown in the image.

6. Click Next.

You can now define input parameter ranges.

Defining Input Parameter Ranges

To define input parameter ranges on the Parametrize Inputs page:

1. Define these input parameter ranges:

Tip:

For quicker entry, you can type the range in the format min:max. For the first
entry, for example, you would type 1:6.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
76 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 1D Signal Data Using a Signal-MOP in optiSLang

2. Click Next.

You can now define output and reference signals.

Defining Output and Reference Signals

To ease setup, defining output and reference signals is broken into these topics:
Defining the Output Signal (Part 1)
Defining the Output Signal (Part 2)
Defining the Reference Signal (Part 1)
Defining the Reference Signal (Part 2)

Defining the Output Signal (Part 1)

To define the output signal:

1. On the ETK tab, open the output file wedge_splitting_output.txt.

2. Set the file format to Plain text file and click OK.

3. Right-click in the data shown for this file and select define location → from begin of file.

Defining the Output Signal (Part 2)

To define the output signal further:

1. Click Show advanced options.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 77
optiSLang Integration Tutorials

2. Set the number of lines to maximum.

3. Increase the maximum number of tokens to 2.

4. Select as signal.

5. Enter a variable name.

6. Select Use as response.

Defining the Reference Signal (Part 1)

To define the reference signal:

1. Click the icon for opening and file and open the output file
wedge_splitting_reference.txt.

2. Set the file format to Plain text file and click OK.

3. Highlight the first number of the first column.

4. Right-click and select define location → from begin of file.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
78 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 1D Signal Data Using a Signal-MOP in optiSLang

Defining the Reference Signal (Part 2)

To define the reference signal further:

1. Click Show advanced options.

2. Set the number of lines to maximum.

3. Increase the maximum number of tokens to 2.

4. Select as signal.

5. Enter a variable name.

6. Change the file path to Absolute.

You must make this change before using the variable as a response.

7. Select Use as response.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 79
optiSLang Integration Tutorials

You can now define signal functions.

Defining Signal Functions

To ease setup, defining signal functions is broken into these topics:
Defining Signal Functions (Part 1)
Defining Signal Functions (Part 2)

Defining Signal Functions (Part 1)

To define signal functions:

1. Click the Variables tab.

2. Click Add variable to add a new variable.

3. Verify the settings of the relative and absolute paths as shown in the following figure.

Caution:

Incorrect file paths are common sources of error.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
80 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 1D Signal Data Using a Signal-MOP in optiSLang

Defining Signal Functions (Part 2)

To define signal functions further:

1. Extract the reference signal's first column as reference displacements:

extract(signal_ref,0)

2. Extract the reference signal's second column as reference displacements:

extract(signal_ref,1)

3. Interpolate the solver's signal at the reference displacements to get the solver's forces at
the same displacement values as the reference signal:

extract(interpolate(signal,disp_ref,LINEAR,0,0),1)

4. Calculate the error norm between the interpolated solver's forces and the reference forces:

euklidnorm(forces_steps-forces_ref)

5. Register forces_steps and error_norm as responses by dragging and dropping them into
the Responses column.

6. Click Next.

You can now define the optimization objective.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 81
optiSLang Integration Tutorials

Defining the Optimization Objective

To define the optimization objective, drag and drop error_norm into the Objectives table, setting
it as a minimization objective:

The goal is to approximate as closely as possible the reference signal obtained from measurement
with the simulation's output signal. The iterative optimization algorithm is used to reduce the
approximation error, which in turn requires an objective function. This example uses the sum of
squared errors between the reference signal and simulation signal as the objective function:

You can now define the solver call.

Defining the Solver Call

To define the solver call:

1. Go to the examples directory and open the file wedge_splitting.bat.

2. Click Import.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
82 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 1D Signal Data Using a Signal-MOP in optiSLang

3. Switch to the Input files tab.

4. In the lower right corner, click the + button and select the file wedge_fem_mesh.s to add
this input file.

5. Complete the Solver Wizard, optionally saving a template for later reuse of the solver chain.

A complete solver chain is added to the optiSLang workbench.

6. Save and run your project to test the newly built solver chain.

You can now create a signal-MOP in optiSLang.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 83
optiSLang Integration Tutorials

Creating a Signal-MOP in optiSLang

optiSLang uses the solver chain that was built in the previous topic to perform a DOE and sensitivity
analysis and to build a signal-MOP in a single step:
Performing a Sensitivity Analysis
Viewing Sensitivity Analysis Results
Viewing Additional Sensitivity Results

Performing a Sensitivity Analysis

To perform a sensitivity analysis:

1. Drag the Sensitivity wizard onto the solver chain.

2. Click through the wizard, setting Sampling Method to Advanced Latin Hypercube Sampling.

A new workflow is added to the scene.

3. Edit the newly added MOP node:

a. Select the Use advanced settings check box.

b. On the Advanced Settings tab, scroll down to Models → External and select the Signal
MOP check box.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
84 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 1D Signal Data Using a Signal-MOP in optiSLang

4. On the Signal MOP Settings tab, specify these settings:

Setting Value
Maximum number of coefficients in Field-MOP 50
Use fast mode for Field-Mop creation Clear check
box
Treat multiple signal channels cross-correlated Select check
box
Minimum point-wise F-CoP for variable filtering [%] 5
Minimum average F-CoP for variable filtering [%] 1
Write algorithm message to log file Select check
box
Show postprocessing Select check
box

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 85
optiSLang Integration Tutorials

5. Save and run your optiSLang project to execute the sensitivity analysis and build the signal-MOP.

When complete, postprocessing opens. You can now view sensitivity analysis results.

Viewing Sensitivity Analysis Results

To view sensitivity analysis results:

1. In postprocessing, add a signal plot.

A plot of the 100 simulated signals shows that the reference signal is sufficiently covered.
You can be confident that the reference signal's parameters are within the parameter
bounds used in the sensitivity analysis. Otherwise, you would have to change the parameter
bounds and run additional simulations.

The signal-MOP can predict the error norm with 90% accuracy. The error norm seems well
suited for optimization, with a single global minimum indicated. Tensile strength , shape

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
86 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 1D Signal Data Using a Signal-MOP in optiSLang

parameter , and fracture energy are the three most important parameters in explaining
the error norm's variance.

2. In the signal plot, select signal_SoS to display the signal's forecast quality (F-CoP[Total])
and the parameter's sensitivities (F-CoP[parameter]).

Forecast quality is excellent along the entire signal, with F-CoP[Total] values consistently
above 90%. Each parameter's sensitivity varies significantly. If you wanted to prevent the
crack from opening at all, the only relevant parameters are Young's modulus (F-CoP[Emod])

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 87
optiSLang Integration Tutorials

and tensile strength (F-CoP[ftc]). The Poisson's ratio (F-CoP[nu]), which is the dashed line,
has been excluded from the signal-MOP because of low sensitivity.

Note:

For some data, even if the average F-CoP[Total] is low, the signal-MOP
might still provide useful information. F-CoP[Total] could still reach
acceptable levels in the particular part of the signal in which you are
interested. Sometimes, F-CoP[Total] is low only in areas where the signal
shows little variation.

3. For Data name, select F-CoP (abs.).

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
88 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 1D Signal Data Using a Signal-MOP in optiSLang

You can view additional sensitivity analysis results.

Viewing Additional Sensitivity Results

To view additional sensitivity analysis results:

1. For Data name, select the result to show.

2. For Number of shown data, indicate the number of values to show.

3. View the results of your signal design space in the single plot.

Signal Statistics
This image shows a plot of eight signal statistics:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 89
optiSLang Integration Tutorials

Signal Correlation
This image shows a plot of five linear correlations. The linear correlation is between each input
parameter and the signal at every point. The Young's modulus (correlation [Emod]) shows a
negative correlation for larger crack widths. A high Young's modulus indicates a hard and brittle
material. While it can withstand large forces initially, the crack will open more easily once a threshold
has been exceeded.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
90 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 1D Signal Data Using a Signal-MOP in optiSLang

Scatter Shapes
This image shows a plot of five scatter shapes, allowing you to view dominant variation patterns.
Each scatter shape represents an individual mechanism in the signal. Every signal from the design
space can be approximated as a superposition of these scatter shapes.

Variability Fraction
This image shows a plot of two scatter shapes:

• Explained variability fraction indicates the total explained variance (ordinate) of each
scatter shape (abscissa).

• Cumulative explained variability fraction indicates the total explained variance (ordinate)
of the first x scatter shapes. Of all signal variance, 96% is captured with a superposition of
three scatter shapes.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 91
optiSLang Integration Tutorials

Optimizing the Signal-MOP

Evaluating the signal-MOP for new input parameters is orders of magnitude faster than solving the
simulation model. Optimization algorithms relying on a large number of iterations, such as an
evolutionary algorithm, can now be run with acceptable computation time. This is advantageous
when trying to find model parameters that produce a signal that matches as closely as possible the
measured reference signal.

Optimizing the signal-MOP consists of:

Adding the Optimization
Setting Up and Running the Optimization

Adding the Optimization

To add the optimization:

1. Drag the Optimization Wizard onto the MOP node and click through the wizard.

2. Set the parameter nue to constant. Because its sensitivity is low, the signal-MOP has
discarded it as an input parameter.

3. Select Evolutionary Algorithm (EA) as the optimization method.

An Evolutionary Algorithm system and a Validator System are added to the scene. The Validator
System is based on the original solver chain.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
92 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 1D Signal Data Using a Signal-MOP in optiSLang

You can now set up the optimization.

Setting Up and Running the Optimization

To set up and run the optimization:

1. Open the Output files node of the original solver chain and do the following on the Variables
tab:

a. Select the four variables that you added previously.

b. Press Ctrl + C to copy the selected variables.

2. Open the MOP Solver node in the Evolutionary Algorithm system and do the following on
the Variables tab:

a. In the list of variables, press Ctrl + V to paste the copied variables.

b. In the window that opens, select Copy.

c. Edit the identifiers of the variables pasted from the signal-MOP.

d. Change the expression for the error norm of the signal-MOP to:

euklidnorm(forces_steps_from_sig-forces_ref)

e. Register the error norm of the signal-MOP as a response.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 93
optiSLang Integration Tutorials

3. Open the settings for the Evolutionary Algorithm system and change the minimization objective
for the error norm of the signal-MOP.

4. Open the settings for the Validator System and do the following:

a. Clear the Prefer criteria from slot check box.

b. Set the objective to error_norm from the original solver chain because you want to
validate with the signal from the simulation.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
94 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 1D Signal Data Using a Signal-MOP in optiSLang

5. Optionally, connect the OBestDesigns slot in the Sensitivity system to the IStartDesigns slot
in the Evolutionary Algorithm system.

This can save optimization algorithm iterations because the optimization can start with a design
closer to the true minimum.

6. Save and run the project.

The postprocessing for the Validator System opens, identifying the following design:

• Simulated error norm: 2560

• Signal-MOP error norm: 1010

• MOP error norm: 5315

The evolutionary algorithm is non-deterministic. The results that you see might vary slightly.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 95
optiSLang Integration Tutorials

The simulated signal with parameters identified by the validator closely matches the measured
reference signal.

Analyzing an Ansys Mechanical Project in optiSLang

The optiSLang node Field_MOP_ANSYSMECH_SoS automates the data handling and field-MOP creation
process. This tutorial builds on a completed DOE. It assumes that optiSLang beta options are enabled
and that you are familiar with these topics:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
96 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing an Ansys Mechanical Project in optiSLang

• Importing Field Data from Ansys Mechanical (p. 37), which describes DOE creation in optiSLang

• Exporting Field Data from Ansys Mechanical for Use in SoS and optiSLang (p. 59), which describes
using the SoS extension for Ansys Mechanical

• Creating and Analyzing Field-MOPs (p. 23) and Advanced Field-MOP Tutorials (p. 113), which
describe the interpretation of field-MOP output

To analyze an Ansys Mechanical project in optiSLang:

1. Load the optiSLang project [Link] in examples\ansys\circuit.

2. If you see a message indicating that the project was created with an older version of optiSLang
and that an older version will not be able to open the project once you save it, click Continue.

When optiSLang beta options are enabled, which is assumed, Field_MOP_ANSYSMECH_SoS

(Beta) is available in the tree view under Modules.

3. Drag a Field_MOP_ANSYSMECH_SoS (Beta) node onto the scene and connect its IPath slot
to the OMDBPath slot in the Sensitivity system.

4. Edit the Field_MOP_ANSYSMECH_SoS (Beta) node:

a. In the area showing additional options, select Distinct working dir.

b. Change settings, selecting the following:

dp0\SYS-1\MECH\SoS_Export: TEMP

dp0\SYS-2\MECH\SoS_Export: UX,UY,UZ,USUM,S1,S2,S3,SEQV

The node detects the sos_result.k LS-PrePost output files exported with the SoS
extension for Ansys Mechanical. The node scans these output files for field variables
and imports field designs of the selected variables.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 97
optiSLang Integration Tutorials

5. On the Field-MOP settings tab, set the path to your SoS executable and click Ok.

You can then evaluate the field-MOP in optiSLang.

Evaluating Field-MOPs in optiSLang

You can evaluate field-MOPs or random field models for new sets of input parameters to quickly
approximate new field designs. You can export any field quantity, including geometric mesh information,
for use in an optiSLang workflow.

This multi-part tutorial shows how to evaluate a field-MOP in optiSLang:

Exporting the Field-MOP for Simulation
Using the "Generate_SoS" Node in optiSLang

Exporting the Field-MOP for Simulation

To export a field-MOP for simulation from SoS:

1. Load the SoS database file circuit_fmop.sdb in examples\ansys\circuit.

2. Select File → Export for simulation → Generate field objects in optiSLang.

3. On the Define reference design directory template page, define a reference design path
of your choice.

All files added or modified are exported relative to this path.

4. Click Create new file and do the following:

a. Select Ansys external data CSV for node data as the file type.

b. Supply a file name of your choice.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
98 of ANSYS, Inc. and its subsidiaries and affiliates.
 Evaluating Field-MOPs in optiSLang

c. Click Save.

5. In the Data to export table, select the quantity identifier to export.

6. Set Design ident to Evaluate Field-MOP.

7. Click Next.

8. On the Define output of simulation data page, set the file to be exported.

9. Click Finish.

The Export to simulation directory contains all files for evaluating the exported field-MOP
and creating a new field design for a set of input parameters. For more information, see the SoS script
file randomfield_simulate_single_design.ssc.

Using the "Generate_SoS" Node in optiSLang

To use the Generate_SoS node in optiSLang:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 99
optiSLang Integration Tutorials

1. In optiSLang, create a Parametric System containing a Generate_SoS node.

2. Edit the Generate_SoS node and open the SIM file exported in the previous tutorial.

The scalar input parameters required by the exported field-MOP are recognized.

3. Add these scalar input parameters to the list of parameters.

4. Click OK.

5. Save and run the project.

The field-MOP is evaluated for default input parameters. Output files are created in the working
directory, including the CSV file defined in the previous section and SoS log output.

6. Use the newly created parametric system to generate new field design for further analysis,
such as an optimization of some objective function derived from the output field.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
100 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 2D Performance Maps in optiSLang

Analyzing 2D Performance Maps in optiSLang

This multi-part tutorial uses a 2D performance map to analyze the performance of a simple valve with
respect to changes in geometry. The analysis is based on data from an Ansys Fluent simulation.

Note:

To run this tutorial, you must have Fluent installed.

A performance map makes more intuitive the analysis of a model with two input parameters and one
output parameter. By varying the two input parameters, you can map the output's response in a
reasonable amount of time.

This image is a performance map of the simple valve with mass flow (mflow) and viscosity (parameter
2_visosity) as input parameters. The valve's performance metric (pressure difference between inlet and
outlet) is shown in color.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 101
optiSLang Integration Tutorials

How does the performance map of the same two input parameters change when you include variations
of additional input parameters? Trying to answer this question can quickly lead to a prohibitive number
of solver calls. However, with SoS, you can treat the performance map as a field depending on these
additional parameters and create a field-MOP for it.

This tutorial first describes the valve model and how to create a nested DOE in optiSLang. It then shows
how to create and analyze a 2D performance map of a field-MOP:
Understanding the Valve Model
Creating a Nested DOE in optiSLang
Creating a 2D Performance Map Field-MOP
Visualizing and Analyzing a 2D Performance Map Field-MOP

Understanding the Valve Model

The schematic of the valve that is being analyzed contains a shutter that diverts the flow to one of
two outlets.

This tutorial focuses on the shutter position with outlet 2 shut off. However, the same principle applies
to both shutter positions.

The analysis setup in Ansys Workbench contains five parameters and one scalar output:

• The five parameters are:

– Radius_upper_chamber

– Radius_lower_chamber

– Position_upper_chamber

– Mass flow

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
102 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 2D Performance Maps in optiSLang

– Viscosity (temperature dependent)

• The one scalar output is pressure loss between inlet and outlet .

This next image of the simplified valve shows the mass flow diverted to outlet 1 and three geometric
parameters.

To see the model definition in a Workbench project, open the project file [Link] in
examples\ansys\valve.

You can create a nested DOE with two levels in optiSLang.

Creating a Nested DOE in optiSLang

This topic shows how to create a nested DOE with two levels.

• With the inner DOE, you vary the performance map parameters (mass flow and viscosity) while
keeping the geometric parameters constant, thereby creating a 2D performance map for a
particular valve geometry.

• With the outer DOE, you keep the performance map parameters constant and vary the
geometric parameters instead.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 103
optiSLang Integration Tutorials

You can think of the inner DOE as a field design for a set of scalar input parameters varied by the
outer DOE. This field design is a 2D performance map.

Note:

For your convenience, in examples\ansys\valve, the optiSLang file

osl_kennfeld.opf already contains the nested DOE created in this section
(including the simulation data). If you open this project and see a message indicating
that it was created with an older version of optiSLang and that an older version will
not be able to open the project once you save it, click Continue. To use
osl_kennfeld.opf directly, you must:

1. Edit the Ansys Workbench node, specifying the path to where the project
file [Link] is located.

2. Set the correct path and version for the Ansys Workbench EXE file.

To create a nested DOE in a new optiSLang project:

1. Set up the outer DOE:

a. Drag the Solver wizard onto the scene.

b. Select Ansys Workbench.

c. Open the Workbench project file [Link] in examples\ansys\valve.

d. Register input and output parameters:

e. Finish the wizard with default settings.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
104 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 2D Performance Maps in optiSLang

2. Set up the inner DOE.

a. Drag the Sensitivity wizard onto the newly created solver system.

b. Set the geometric parameters constant and define the parameter ranges:

c. Select Advanced Latin Hypercube Sampling as the sampling method and set the number
of samples to 20.

d. Clear the Create MOP check box.

e. Finish the wizard and rename the newly created sensitivity system to DoE_working_points.

3. Continue the set up by doing the following:

a. From the Modules box, drag the Sensitivity wizard onto the scene and rename it
to DoE_geometry.

b. While pressing and holding the Shift key, drag the DoE_working_points system
into the DoE_geometry system.

c. Add a Data Mining node to the DoE_geometry system and select Send design
back to parent system.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 105
optiSLang Integration Tutorials

d. Connect the ODesign slot of the DoE_working_points system to a new slot of the
Data Mining node.

e. Right-click the DoE_working_points system and select Design Flow → Receive

reference design.

Your project show now look like this:

4. Edit the Data Mining node and create a dummy response named MeanDeltaP.

5. Edit the outer DoE geometry system and set Number of samples to 30.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
106 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 2D Performance Maps in optiSLang

6. Set the geometric parametric to non-constant and the mass flow and viscosity parameters
to constant. Adjust the geometric parameter's ranges.

7. Run the project.

You can now create a 2D performance map field-MOP.

Creating a 2D Performance Map Field-MOP

To create a 2D performance map field-MOP:

1. Drag a Field_MOP_2D_Nested_DOE_SoS node onto the scene.

2. Connect the OMDPath output slot of the DoE_geometry system to the IPath slot of the
newly added SoS node.

3. Edit the Field_MOP_2D_Nested_DOE_SoS node and click Change settings.

4. On the General settings tab, adjust these settings:

Path to inner OMDB file template

Select the OMDB file created by DoE_working_points system.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 107
optiSLang Integration Tutorials

Considered responses

Click Refill list to automatically extract the responses from the inner OMDB file. You can
change the list manually if needed. The performance maps of multiple responses can be
analyzed at once.

Parameter ident of 1st axis

Select mflow.

Parameter ident of 2nd axis

Select parameter_2_viscosity.

Scale axis

When selected, both axes are scaled so that the performance map fits a unit square.

Resolution

Set the performance map resolution along each axis to 100. The field-MOP created for
the interior DOE is evaluated at each point.

SoS executable

The value of the environment variable SoS_exe is set by default. You can change it if
necessary.

Export PNG images

When selected, PNG files of the most useful plots are exported to the working directory.

5. On the FMOP settings tab, use these settings:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
108 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 2D Performance Maps in optiSLang

For more information on field-MOP settings, see Advanced Field-MOP Tutorials (p. 113).

6. Run the project.

You can now visualize and analyze a 2D performance map field-MOP.

Visualizing and Analyzing a 2D Performance Map Field-MOP

To visualize and analyze a 2D performance map field-MOP:

1. Drag a Viewer_SoS node onto the scene.

2. Edit this node and open the file sos_fmop_field.sdb that the Field_MOP_2D_Nes-
ted_DOE_SoS node created in the previous topic.

3. Run the newly added node.

After a few seconds, an SoS Viewer instance opens. You can now view performance maps.

Analysis of Statistics
In this image, the performance map on the left shows the average pressure difference when varying
the geometry. The performance map on the right shows the standard deviation of the pressure
difference when varying the geometry, indicating working points where the geometry has the high
and low influences on the valve's performance.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 109
optiSLang Integration Tutorials

Analysis of the Geometry's Performance Impact

In this image, the performance map on the left shows the lowest possible pressure difference when
varying the geometry. The performance map on the right shows the highest possible pressure
difference when varying the geometry. Each working point on these plots may correspond to a
different geometry. If the difference between the plots on the left and on the right is larger, the
valve's geometry has a bigger influence on its performance.

Analysis of Sensitivity
In this image, the performance map on the left shows the F-CoP[Total] value, which indicates the
field-MOP's forecast quality. The plot on the right shows the most sensitive input parameter at each
working point. The upper chamber radius has the highest importance at all working points evaluated.
For blue (unknown) areas, the forecast quality is too low to make a valid prediction.

Real-time Approximation
This image shows how to predict the 2D performance map of a particular geometry by adjusting the
sliders of the geometric parameters.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
110 of ANSYS, Inc. and its subsidiaries and affiliates.
 Analyzing 2D Performance Maps in optiSLang

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 111
 Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
112 of ANSYS, Inc. and its subsidiaries and affiliates.
Advanced Field-MOP Tutorials
These tutorials assume that you are already familiar with Basic SoS Tutorials (p. 3):
Tuning Field-MOP Settings
Improving the Field-MOP's Forecast Quality
Using Fields or Signals as Field-MOP Inputs
Using Named Selections
Exporting a Field-MOP as an FMU
Evaluating Gasket Tightness

All but the last tutorial expands on the tutorial Creating and Analyzing Field-MOPs (p. 23). Before
beginning these tutorials, you must load data from either of these SoS database files:

• The SoS database that you created by importing data for the tutorial Importing Field Data from
Ansys Mechanical (p. 37)

• The SoS database file circuit_fmop.sdb in examples\ansys\circuit, which already

contains field-MOPs generated from data imported from a DOE.

The last tutorial expands on the Gasket Tightness example in the Statistics on Structures User's Guide.
The files used in this tutorial are in examples\ansys\gasket. Because the SoS database file
gasket_tightness.sdb already contains imported simulation data, you can skip the importing of
data and creating of field-MOPs.

Tuning Field-MOP Settings

This multi-part tutorial shows how to tune field-MOP settings:

When tuning field-MOP settings, your objectives are to:

• Improve the forecast quality (Field-CoP[Total]) of the field-MOP

• Analyze the accuracy versus speed trade-off in calculating the field-MOP

• Create a cross-correlated field-MOP from correlated field quantities

• Learn more about field-MOP visualization with displacement fields

In the Create Field Metamodel of Optimal Prognosis (Field-MOP) dialog box, the Settings tab allows
you to select a meta model and tune its settings.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 113
Advanced Field-MOP Tutorials

You want to find a meta model and settings with the largest possible F-CoP[Total].

F-CoP[Total] is a measure of the Field-MOP's forecast quality. Values higher than 80% are generally
acceptable. Values higher than 90% are good.

Default Meta Model Settings

SoS's internal meta model:

• Provides a good compromise between speed and accuracy

• Performs excellently for large numbers of input parameters and designs

• Uses a non-linear model tuned for field data

• Performs sensitivity analysis, adding F-CoP[parameter] sensitivity values to the data table

SoS excludes parameters of little importance from the field-MOP.

Customized Settings of Internal Meta Model

You can customize the settings of the internal meta model.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
114 of ANSYS, Inc. and its subsidiaries and affiliates.
 Improving the Field-MOP's Forecast Quality

For example, to get quick first results or if you find the field-mop calculation to be too slow, you can
select the Fast mode for meta model creation check box, keeping in mind these limitations:

• Accuracy is sacrificed for calculation speed.

• Sensitivity values are particularly prone to inaccuracy.

Customized Settings for MOP Backend

You can select the Use custom settings for MOP backend check box if you want to use the MOP
backend that the optiSLang MOP used. optiSLang's MOP backend selects and compares models to find
the most suitable model. There are cases where optiSLang's MOP backend outperforms SoS's internal
meta model, especially for linear but noisy data. However, optiSLang's MOP backend does not perform
sensitivity analysis.

You can now improve the field-MOP's forecast quality.

Improving the Field-MOP's Forecast Quality

To improve the forecast quality (F-CoP[Total]) of the field-MOP:

1. Select Field data models → Field-MOP → Create Field-MOP.

2. On the Select training data tab, do the following:

a. Drag and drop the field quantity LOGSEQV into the Output list.

b. Drag and drop the five scalar parameters into the Input (selectable) list:

• TEMP_env

• TEMP_CPU

• CTE_PCB_xy

• TEMP_MCU

• CTE_CPU

3. Using the default meta model settings, click OK to build the field-MOP.

4. Review results in the Field data models window.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 115
Advanced Field-MOP Tutorials

When the default value of 10 shapes is used for the random field decomposition, the field-MOP
explains 96.9% of the variance observed in the simulated field designs. This limits the achievable
F-CoP[Total] values. Ideally, you want to see values closer to 100%.

5. Re-create the field-MOP using 25 shapes.

With a superposition of 25 shapes, the field-MOP explains 99.4% of the variance observed in
the simulated field designs.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
116 of ANSYS, Inc. and its subsidiaries and affiliates.
 Improving the Field-MOP's Forecast Quality

Note:

Using more shapes, you can boost the average F-CoP[Total] from 86.7% to 88.2%,
with the cost of some computation time.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 117
Advanced Field-MOP Tutorials

6. Now re-create the field-MOP again but drag and drop the field quantity Temp into the Output
list and use the default meta model settings.

Using Fields or Signals as Field-MOP Inputs

With the help of a random field model, you can use fields or signals as inputs to field-MOPs. You can
also use random field amplitudes as input parameters when building a field-MOP. You can reduce a
field design with an existing random field model to its random field amplitudes, which in turn you can
use to evaluate the field-MOP.

This is a particularly useful feature when you are obtaining input field data from measurements or
analyzing output fields depending on geometric variations. You can parametrize the geometric variations
with a random field model and subsequently use it as a field-MOP input.

For more information on geometric variations, see:

• Creating Geometric Imperfections from a Synthetic Random Field in Ansys Mechanical (p. 63)

• Creating Geometric Imperfections from a Free-form Variation Field in Ansys Mechanical (p. 69)

• Setting Named Selections Imported Within the Reference Mesh (p. 120)

This multi-part tutorial uses the printed circuit board example. For the coupled thermo-mechanical
simulation, a field-MOP is built for the stress field, using the temperature field as input. For more
information on how this example was built, see Importing Field Data from Ansys Mechanical (p. 37)
and the earlier tutorials in this section on advanced field-MOP analysis.

This tutorial consists of:

Creating an Empirical Random Field Model of a Temperature Field
Creating a Field-MOP for a Stress Field with a Temperature Field as an Input

Creating an Empirical Random Field Model of a Temperature Field

To create an empirical random field model of a temperature field:

1. Load the SoS database file circuit_fmop.sdb in examples\ansys\circuit.

This database file already contains field-MOPs generated from data that was imported from
a DOE.

2. In the data table, select the field quantity TEMP.

3. Select Field data models → Random fields → Create empirical random field model.

4. Set Desired explained variation (%) to 99.00.

5. Click OK.

Random field amplitudes are added to the list of scalar quantities. The temperature field is the result
of a linear problem. It is perfectly represented with three shapes.

You can now create a field-MOP for a stress field with a temperature field as an input.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
118 of ANSYS, Inc. and its subsidiaries and affiliates.
 Using Fields or Signals as Field-MOP Inputs

Creating a Field-MOP for a Stress Field with a Temperature Field as an Input

To create a field-MOP for a stress field with a temperature field as an input:

1. Select Field data models → Field-MOP → Create Field-MOP.

2. On the Select training data tab:

a. For Input (selectable), select CTE_CPU, CTE_PCB_xy, and the random field
amplitudes.

The quantities CTE_CPU and CTE_PCB_xy are the coefficients of thermal expansion
for the CPU and printed circuit board.

Do not select the temperature input parameters.

b. For Output, select the field quantity LOGSEQV, which is the logarithmic von-Mises
stress field.

3. On the Settings tab, accept the defaults.

4. Click OK.

SoS overwrites the existing field-MOP, which was built using the temperature input parameters. You
can now visualize the field-MOP.

This field-MOP shows a stress field with random field amplitudes of the temperature field as input.
A new temperature field design can be reduced to its random field amplitudes and used as field-MOP
input.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 119
Advanced Field-MOP Tutorials

Using Named Selections

This multi-part tutorial shows how to use named selections in these scenarios:
Setting Named Selections Imported Within the Reference Mesh
Importing Named Selections from a CSV File
Setting a Fixed Boundary for Mesh Morphing

Note:

You cannot change the reference named selection after field data objects are added to
the database. Field data objects are always defined on a reference named selection. By
default, SoS uses the entire reference mesh.

Setting Named Selections Imported Within the Reference Mesh

SoS recognizes and imports named selections within the reference mesh.

To start a new project and set a reference mesh and named selections within the reference mesh:

1. Set up the project:

a. Start a new SoS project.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
120 of ANSYS, Inc. and its subsidiaries and affiliates.
 Using Named Selections

b. For Filename, select the mesh file sos_mesh.cdb in

examples\ansys\simple_cube.

c. For Project name, set a name of your choice.

2. Set the named selection:

a. Select File → Mesh → Set reference named selection.

b. For nodes used for statistics/models, set the named selection SOS_MODEL_NODES.

All field data objects of the node type, such as field designs, models, and statistics
results, are defined on this reference named selection.

c. Click OK.

3. Create a synthetic random field model:

a. Select Field data models → Random fields → Create synthetic random field model.

b. For Ident, set an identifier of your choice.

c. For Data type, select Node.

d. Click OK.

You can now visualize a shape of the newly created random field model.

This image shows a random field model defined on a reference named selection of type node.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 121
Advanced Field-MOP Tutorials

Importing Named Selections from a CSV File

To start a new project, set a reference mesh, and import named selections from a CSV file:

1. Set up the project:

a. Start a new SoS project.

b. For Filename, select the mesh file sos_mesh.cdb in

examples\ansys\simple_cube.

c. For Project name, set a name of your choice.

While this mesh file contains named selections, you can still add your own named
selections from a CSV file.

2. Import the named selection from the CSV file:

a. Select File → Mesh → Import named selection from CSV.

b. Open the file named_selection.csv in

examples\ansys\simple_cube\named_selections.

This file contains a list of element and node identifiers.

c. For Ident, set an identifier of your choice.

d. For Data type, select Element set.

e. Click OK.

SoS interprets the CSV file as a list of element or node Identifiers, depending on selected
data type.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
122 of ANSYS, Inc. and its subsidiaries and affiliates.
 Using Named Selections

3. Set the imported named selection:

a. Select File → Mesh → Set reference named selection.

b. For elements used for statistics/models, set the imported named selection.

All field data objects of the element type, such as field designs, models, and statistics
results, are defined on this reference named selection.

c. Click OK.

4. Create a synthetic random field model:

a. Select Field data models → Random fields → Create synthetic random field model.

b. For Ident, set an identifier of your choice.

c. For Data type, select Element.

d. Click OK.

You can now visualize a shape of the newly created random field model.

This image shows a random field model defined on a reference named selection of type element.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 123
Advanced Field-MOP Tutorials

Setting a Fixed Boundary for Mesh Morphing

To start a new project, import named selections, and set a fixed boundary for mesh morphing:

1. Set up the project:

a. Start a new SoS project.

b. For Filename, select the mesh file sos_mesh.cdb in

examples\ansys\simple_cube.

c. For Project name, set a name of your choice.

While this mesh file contains named selections, you can still add your own named
selections from a CSV file.

2. Import named selections from a CSV file:

a. Select File → Mesh → Import named selection from CSV.

b. Open the file bottom_and_one_side.txt in

examples\ansys\simple_cube\named_selections.

c. For Ident, set an identifier of your choice.

d. For Data type, select Node set.

Click OK.

3. Import and set more named selections:

a. Import named selections from the file top_surface.txt in

examples\ansys\simple_cube\named_selections as a Node set.

b. For nodes used for statistics/models, set the named selection TopSurface.

c. For fixed nodes for mesh morphing, set the named selection BottomAndOneSide.

d. For elements used for statatistics/models, set All elements.

e. Click OK.

4. Create a synthetic random field model:

a. Select Field data models → Random fields → Create synthetic random field model.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
124 of ANSYS, Inc. and its subsidiaries and affiliates.
 Using Named Selections

b. For Ident, set an identifier of your choice.

c. For Data type, select Node

d. For Standard deviation, select Define homogeneous and set the value to 0.002.

e. Click OK.

5. Visualize the morphed mesh:

a. In the Choose visible data toolbar, select Contour plot, Node data, SyntheticField, and
Random field.

b. Click Add.

c. In the Choose visible data toolbar, select Normal displacement, Node data, Synthet-
icField, and Random field.

Click Apply.

d. In the Field data model inspector, use the sliders to adjust the palette bounds as
necessary, observing how the mesh is morphed according to the synthetic random field.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 125
Advanced Field-MOP Tutorials

The mesh is morphed on the fly when adjusting the normal displacements according to the random
field. The nodes of the named selection TopSurface that was set for nodes used for statistics/models
are being morphed while the nodes of the named selection BottomAndOneSide that was set for
fixed nodes for mesh morphing remain in place.

This shows that when these two named selections "touch" each other, morphing partially fails, resulting
in broken mesh elements. Remember to always maintain nodes that are not part of any reference
named selection between the fixed and morphed named selections.

Exporting a Field-MOP as an FMU

This multi-part tutorial shows how to export a field-MOP as an FMU (Functional Mock-up Unit) and
import it into optiSLang, where you can then perform a sensitivity analysis:
Exporting a Field-MOP as an FMU
Importing the FMU into optiSLang Using the "FMU_SoS" Integration Node
Performing a Sensitivity Analysis with the FMU

Exporting a Field-MOP as an FMU

This topic shows how to export a field-MOP with custom evaluation macros as an FMU. You can use
the FMU to automate field-MOP evaluation and analyze the FMU using external tools. The list of
software supporting FMUs includes Ansys Electronics Desktop with Twin Builder and the Python
module FMPy.

To export a field-MOP as an FMU:

1. Start SoS.

2. In the Welcome to Statistics on Structures window, select Load an existing database and
click Next.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
126 of ANSYS, Inc. and its subsidiaries and affiliates.
 Exporting a Field-MOP as an FMU

3. Click the folder icon to select a file.

4. Navigate to examples\ansys\circuit, select the SoS database file circuit_fmop.sdb,

and click Open.

This database file already contains field-MOPs generated from data imported from a DOE.

5. Click Finish.

6. Select File → Export for simulation → Macro-based FMU to start the FMU Export Wizard.

7. In the Custom solver definition window, click Add Macro.

8. Select Evaluate Field-MOP nodeEvaluateFieldMOP.

9. Click Next.

10. In the fieldMOP field, enter TEMP.

11. From the fmopIdent list, select TEMP.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 127
Advanced Field-MOP Tutorials

12. Click Finish.

The macro is added to the custom solver definition.

13. Click Add Macro.

14. Select Maximum value of a field.

15. Click Next.

16. In the nodeIdent field, enter TEMP.

17. From the Named selection list, select SOS_DATA_NODES.

18. In the scalarMax field, enter max[TEMP].

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
128 of ANSYS, Inc. and its subsidiaries and affiliates.
 Exporting a Field-MOP as an FMU

19. Click Finish.

The macro is added to the custom solver definition.

20. Click Next.

21. Click the folder icon.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 129
Advanced Field-MOP Tutorials

22. Select a file name, type, and location for your exported FMU file.

23. Click Save.

The file path is added to the Output file field.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
130 of ANSYS, Inc. and its subsidiaries and affiliates.
 Exporting a Field-MOP as an FMU

24. Click Finish.

You can now import the FMU into optiSLang using the FMU_SoS custom integration node.

Importing the FMU into optiSLang Using the "FMU_SoS" Integration Node
To import the FMU into optiSLang using the FMU_SoS custom integration node:

1. Start optiSLang and add a Parametric System to your project.

2. While pressing the Shift key, drag and drop an FMU_SoS node onto the Parametric System.

3. Right-click the FMU_SoS node and select design flow → receive designs.

4. Right-click the FMU_SoS node and select design flow → send back designs.

5. Edit the FMU_SoS node and open the previously exported FMU file.

6. Add all inputs to the parameter list.

7. Add all outputs to the response list.

8. Click Show advanced options and set Designs per execution to a large number (such as
100000).

For the FMU's solver to run fast and store all result data in the output database, Designs per
execution must be set to a large enough number that all designs are processed at once.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 131
Advanced Field-MOP Tutorials

9. Click OK.

10. Run the project.

You can now perform a sensitivity analysis with the FMU.

Performing a Sensitivity Analysis with the FMU

To perform a sensitivity analysis with the FMU:

1. Drag and drop the Sensitivity Wizard onto the title bar of the Parametric System.

2. Check the input parameters and their ranges.

The correct ranges are provided by the FMU.

3. Click Next.

4. Check parameters and responses.

5. Because you are not performing optimization, click Next.

6. Set Sampling Method to Other (see next page) and click Next.

7. Set the number of samples to 200.

8. Click Next.

9. Clear the Create MOP check box and click Finish.

10. Run the project.

Once the project runs, postprocessing opens. Unsurprisingly, a correlation matrix of the results for
the sensitivity analysis show that the CPU's temperature is the main driver of the maximum temperature
on the entire circuit board. At higher CPU temperatures, there is a linear correlation between CPU
temperature and maximum temperature. MCU temperature shows relevancy only at a low CPU
temperature and high MCU temperature.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
132 of ANSYS, Inc. and its subsidiaries and affiliates.
 Exporting a Field-MOP as an FMU

This image shows a plot of the CPU temperature input parameter versus the maximum temperature.

This next image shows a plot of the MCU temperature input parameter versus the maximum
temperature.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 133
Advanced Field-MOP Tutorials

Evaluating Gasket Tightness

This multi-part tutorial shows how to create an advanced SoS analysis, combining multiple field-MOPs
and a custom algorithm. The SoS analysis is then exported as an FMU, allowing consumption with Ansys
optiSLang or Ansys Twin Builder, which is part of Electronics Desktop.
Identifying the Contact Tightness Algorithm
Importing Simulation Data and Creating Field-MOPs
Exporting the Custom Analysis Workflow as an FMU
Executing the Exported FMU

The objective of this analysis is to determine if the gasket is tight, given a certain bolt pretension and
pressure of the flowing medium.

• For background information, see Gasket Tightness in the Statistics on Structures User's Guide.

• To learn how to create a design of experiments from an Ansys Mechanical project using optiSLang,
see Exporting Field Data from Ansys Mechanical for Use in SoS and optiSLang (p. 59).

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
134 of ANSYS, Inc. and its subsidiaries and affiliates.
 Evaluating Gasket Tightness

The folder examples\ansys\gasket contains the files that are used in this tutorial. Because the
SoS database file gasket_tightness.sdb already contains imported simulation data and field-MOPs,
if you load this file, you can skip to Exporting the Custom Analysis Workflow as an FMU (p. 138). However,
if you want to step through the entire process in a new SoS database file, perform the procedures in
the next two topics.

Identifying the Contact Tightness Algorithm

To identify the contact tightness algorithm.

1. Select File → Macros → Manage macros.

2. In the Manage macros window, select the macro identifyContactTightness and click Edit.

In the Edit chunks / macros window, the Input arguments area displays two scalar parameters
that tune the algorithm (minimumPressure and minimumContactState) and two variables
of type string that set the named selections of the inner and outer closed rings across which
tightness is to be evaluated.

3. After viewing these arguments, close the Edit chunks / macros window and then the Manage
macros window.

Importing Simulation Data and Creating Field-MOPs

In a new SoS project, import the simulation data:

1. To import the reference mesh, select File → Mesh → Set reference mesh and open
sos_mesh.cdb in
examples\ansys\gasket\workflow\[Link]\Sensitivity\Design0002\dp0\SYS-6\MECH\

Note:

Design0001 failed and no mesh was exported during the DOE.

2. To import named selections for the inner and outer edges:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 135
Advanced Field-MOP Tutorials

a. Select File → Mesh → Import named selection from CSV and open
ns_gasket_seal_edge_inner.csv in
examples\ansys\gasket\components.

b. Set the identifier to INNER_EDGE and create a node set.

c. Select File → Mesh → Import named selection from CSV and open
ns_gasket_seal_edge_outer.csv in
examples\ansys\gasket\components.

d. Set the identifier to OUTER_EDGE and create a node set.

Caution:

The identifiers for the named selections must be set precisely to INNER_EDGE and
OUTER_EDGE. Otherwise, the identifyContactTightness algorithm fails.

3. To import field designs:

a. Select File → Process multiple designs → Import field designs.

b. In the Files to parse area, add the LS-PrePost output file sos_results.k in
Design0002\dp0\SYS-6\MECH\SoS_Export.

c. Set Path of reference design to

\examples\ansys\gasket\workflow\[Link]\Sensitivity\Design0002\.

d. Finish the import.

The number of field designs imported should be 45.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
136 of ANSYS, Inc. and its subsidiaries and affiliates.
 Evaluating Gasket Tightness

4. To import scalar input parameters:

a. Select File → Import data → Import scalars from optiSLang .bin and open
[Link] in examples\ansys\gasket\workflow\[Link].

b. Accept the default values in the Import scalar parameters to SoS window.

c. Select Edit → Deactivate incomplete designs.

Note:

During the DOE, some designs have failed to produce results. Designs
without field results must be excluded from field-MOP training.

5. To create field-MOPs:

a. Select Field data models → Field-MOP → Create Field-MOP.

b. Drag and drop all scalar quantities to the Input (selectable) list.

c. Drag and drop the field node quantities STATUS and PRESSURE to the Output list.

d. Click OK to create the field-MOPs with the default settings.

By evaluating the two newly created field-MOPs, you are now ready to approximate the
contact pressure field and contact state field for any given set of input parameters (within
the range of training data).

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 137
Advanced Field-MOP Tutorials

Exporting the Custom Analysis Workflow as an FMU

To determine if the gasket is tight for a given set of input parameters, you can export the macro-based
custom analysis workflow as an FMU.

Note:

If you skipped to this step after loading the SoS database file gasket_tightness.sdb,
you can export the custom analysis workflow in this database file as an FMU.

To export the custom analysis workflow as an FMU:

1. Select File → Export for simulation → Macro-based FMU.

2. In the Custom solver definition window, click Add Macro.

3. Select Evaluate Field-MOP nodeEvaluateFieldMOP.

4. Click Next.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
138 of ANSYS, Inc. and its subsidiaries and affiliates.
 Evaluating Gasket Tightness

5. In the fieldMOP field, enter PRESSURE.

6. From the fmopIdent list, select

PRESSURE.

7. Click Finish.

The macro is added to the custom solver definition.

8. Click Add Macro.

9. Select Evaluate Field-MOP nodeEvaluateFieldMOP.

10. In the fieldMOP field, enter STATUS.

11. From the fmopIdent list, select STATUS.

12. Click Finish.

The macro is added to the custom solver definition.

13. Click Add Macro.

14. Select Identify tightness of a contact area.

15. Enter the following information:

Field Value
pressureField PRESSURE
isTight isTight
contactField STATUS
minimumPressure minimumPressure

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 139
Advanced Field-MOP Tutorials

Field Value
minimumContactState minimumContactState
Named selection ns_gasket_seal_edge_inner
Named selection ns_gasket_seal_edge_outer
tighnessField tightnessField

16. Click Finish.

The macro is added to the custom solver definition.

17. Add additional macros of your choice.

For example, you might add the macro for extracting the maximum value of the PRESSURE field.

18. Click Next.

19. Click the folder icon.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
140 of ANSYS, Inc. and its subsidiaries and affiliates.
 Evaluating Gasket Tightness

20. Select a file name, type, and location for your exported FMU file.

21. Click Save.

The file path is added to the Output file field.

22. Click Finish.

Executing the Exported FMU

In a tool of your choice, execute the exported FMU. The following tools are recommended:

• Ansys optiSLang (FMU_SoS custom integration node (p. 131))

• Ansys Twin Builder

• FMPy in a Python environment

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 141
 Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
142 of ANSYS, Inc. and its subsidiaries and affiliates.
Measurements and Noise Tutorials
These tutorials show how to work with measurements and noise:
Using RPCA (Robust Principal Component Analysis) to Filter Noise
Importing and Analyzing Measured Geometries
Creating Imperfect Geometries
Performing Uncertainty Quantification Based on Measured Geometries
Applying Displacement of Nodes of a Mesh by Measurement on Another Geometry

Using RPCA (Robust Principal Component Analysis) to Filter Noise

When dealing with measurements or noisy simulation results, you often face situations where sensor
data creates noise. Obviously, you do not want to use the noise as input for training a field-MOP or
random field model. This tutorial shows how to use RPCA to filter noise from measurements.

RPCA is a filter for postprocessing field data before doing a statistical analysis or creating a ROM. This
filter can identify noise that typically appears at random positions. In this case, you can deduce the true
value from the noisy data point based on the spatial correlations from the other designs that are not
noisy.

The small example for this tutorial demonstrates the power of the approach and the kind of data that
can be filtered. The example creates a rectangular pixel mesh (regular grid in 2D). You assign data that
is defined by a linear interpolation between the left and the right edges, whereby the actual value at
the left and right edges are chosen randomly. You then assign some "sensor noise" for each design by
choosing a random number of data points to be subject to noise and adding some random value to
the true data points.

The following SoS script creates the mesh and the data. After starting SoS, paste this script into the
command line of the Execute script window and press the Enter key to execute it.
-- Create a pixel mesh within 0<=x<=20 and 0<=y<=10 with resolution 200*100
meta = [Link](200,0,20, 100,0,10);
[Link]([Link](), meta)

-- turn off command logging to improve make the execution of for-loops faster
[Link](false);

-- create 100 designs

for i=1,100 do
local d = "" .. i -- design ident as string
local a = [Link]()*100 -- left value (0..200)
local b = [Link]()*100 -- right value (0..200)
-- create a data vector:
local vec = [Link]([Link]([Link]()),1)
for k=0,200-1 do -- loop over all data points along x axis
for l=0,100-1 do -- loop over all data points along y axis
vec[ k*100 + l ] = (k/200)*a + (1-k/200)*b -- set the field value
end
end

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 143
Measurements and Noise Tutorials

-- create a field data object and insert data to database:

local o = [Link]([Link](), vec)
[Link]():nodeDataRef():insert( [Link](d, "orig"), o)

-- now apply random noise:

local n=[Link](1,100*200 / 20) -- get number of noisy pixels
for k=1,n do -- for each noisy data point do:
local idx = [Link](0,[Link]([Link]())-1) -- random position
vec[idx] = ([Link]())*1000 -- random value between -500 and +500
end
-- insert the noisy data to database
local o = [Link]([Link](), vec)
[Link]():nodeDataRef():insert( [Link](d, "noisy"), o)
end

Now, to use RPCA to filter the data:

1. In the data table, select noisy in the Field quantities list.

2. Select Statistics → Filters → Robust Principal Component Analysis.

3. Keep the default RPCA settings:

4. Click OK to start the iterative RPCA algorithm.

In the Log messages window, you can see the iteration history.

To understand what RPCA is doing, compare the filtered and unfiltered results for a selected
design in the following image. The top left shows the original data, and the top right shows
the noisy data. The bottom shows the filtered designs of the RPCA. RPCA can identify the
random noise and separate it from the data, thereby restoring the noisy data nearly perfectly
to the original data so that it can be used for further analysis.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
144 of ANSYS, Inc. and its subsidiaries and affiliates.
 Using RPCA (Robust Principal Component Analysis) to Filter Noise

5. To show the effect on field data models, create a random field model:

a. From the Field quantities list in the data table, select orig, noisy, and RPCA[noisy],
which are respectively the original data, the noisy data, and the filtered data.

b. Select Field data models → Random fields → Create empirical random field model.

This example uses the default options to compute the variation shapes for all selected
quantities:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 145
Measurements and Noise Tutorials

c. Click OK.

When comparing the variability fractions of the identified random field scatter shapes, you can see that
the filtered quantity has the same properties as the original one.

You can validate this by comparing the first variation shape. Without filtering, the random field contains
the noise and takes it as "true" input data that must be represented by the model. Thus, you need many
more shapes and obtain noisy variation patterns.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
146 of ANSYS, Inc. and its subsidiaries and affiliates.
 Importing and Analyzing Measured Geometries

To examine the filtered data further, you should compare the mean value, the standard deviation, and
the lower and upper value bounds.

Particularly when dealing with measurements in digital twin applications, you can use RPCA to help
filter sensor errors and improve the quality of the input data, which can be signal data or geometric
measurements. If certain sharp features are visible only in individual designs, RPA can remove them.

Importing and Analyzing Measured Geometries

The statistical analysis of measured geometries is typically used for uncertainty quantification or to
analyze the true geometry instead of the CAD0 geometry. Often the measurements are given by 3D
surface scans saved to STL files. STL files define a triangularization of the boundary of the scanned
object.

You typically cannot use STL files originated by a 3D scanner directly. You must usually perform these
steps before using them:

Repair the surface.

Fill holes, remove outlier points, and remove false detections.

Adjust coordinate systems.

Scale all measurements to the same physical unit (such as inches or millimeters) and translate
and rotate them into the same position. SoS supports this process by automated coordinate
alignment strategies, but in most applications a manual approach is more reliable and accurate.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 147
Measurements and Noise Tutorials

Coarsen the mesh.

Try to coarsen the segmentation to a minimum number of surface triangles. Typically, you are
interested in global deformation shapes. Further, the triangulation of the measurements need
not be more accurate than the discretization level of the SoS reference mesh.

This multi-part tutorial consists of procedures for:

Importing Measurements
Analyzing Measurements

Importing Measurements
To import measurements:

1. Select the reference mesh, taking into consideration these guidelines:

• Choose one of the measurement STL files if you are interested in only the statistics of
the measurements.

• Choose a FEM mesh if you also want to quantify the deviation from CAD0.

• Choose the FEM mesh template being used in the simulation model if you also want
to generate new imperfections or apply the measurement to a FEM mesh. In this case,
it is important to mesh the model once (export it to SoS) and keep the mesh untouched
afterwards. SoS will refer to the same mesh topology (node and element identifiers)
when exporting the morphed meshes to the CAE solver.

2. Define carefully the required named selections, taking into consideration these guidelines:

• A fixed node set is the part of the boundary that is not to be modified and must
remain unchanged. If the whole boundary is not part of the reference node set, you
should define a fixed node set to avoid spurious rigid body motion in morphing.

• A reference node set is the part of the boundary that is used to store the relevant
information from the measurements. Relevant information consists of the coordinate
deviations between reference mesh and measurement. This typically excludes boundary
regions where:

– The consideration of geometric deviation is not important

– The deviations are measured erroneous

– Clamps, sensors, fixations, or other devices are located that are part of the scan
but are not part of the considered structure

Note:

The fixed node set should always cover symmetry planes. Between the fixed
node set and the reference node set, it is required to place a number of free
node or element rows that relax the geometric morphing between the directly
changed and unchanged parts.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
148 of ANSYS, Inc. and its subsidiaries and affiliates.
 Importing and Analyzing Measured Geometries

3. Collect all measurements in a design directory structure just as if you are performing a DOE
in optiSLang:
project dir
Design0001/[Link]
Design0002/[Link]
...
Design00xx/[Link]

For more information, see Performing a DOE in optiSLang (p. 43).

Instead of using STL files, you can use FEM mesh file formats. The registration of the geometric
deviations is identical. For this tutorial, in
examples\lsdyna\metal_forming__eroded_elements\sampling, you can use
the LS-DYNA Dynain file ref-mesh.k as the reference mesh and Design0001/NW/mesh.k
as the measurement.

4. To import multiple measurements, select File → Process multiple designs → Import field
designs.

5. On the Reference design page, click Add File to define the template for the import.

6. Select the file format LS-DYNA Dynain and then the file ref-mesh.k.

7. For Path of reference design, select

examples\lsdyna\metal_forming__eroded_elements\sampling\Design0001/NW
to use the measurement mesh file mesh.k.

Once SoS detects a mesh file is among the files to be imported, it provides the options to
import:

• The nodal coordinate deviations along the x, y, z axis

• The nodal coordinate deviation along the normal vector (either as a strictly positive
number or a signed distance with positive being pointing outside of the structure)

• The nodal coordinates of the measurements (with respect to the node numbering of
the reference mesh) along the x, y, z axis

Typically, you are interested in:

• The nodal coordinate deviations along the x, y, z axis, which you use to create a
cross-correlated empirical random field model for the generation of morphed meshes

• The nodal coordinate deviation along the boundary normal, which you use for:

– Analysis of correct data mapping

– Statistical analysis of material wear (removal) or growth (addition)

– Synthetic random field models for generation of morphed meshes and, therefore,
deactivate NodeCoordinates from import

8. Select the mash mapper, which defines by which algorithm the coordinate deviates.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 149
Measurements and Noise Tutorials

Consider these guidelines for selecting the mesh mapper:

• If the FEM meshes are compatible (have identical node and element numbering), you
should select the Compatible mesh mapper. This mapper captures the true deviation
vectors of all nodes, including the interior nodes.

• The default selection, Incompatible (assuming a smooth boundary), creates normal

vectors at each boundary node of the reference mesh and search long this direction
to find a projection point on the measurement surface. If there are holes in the
measurement, they are collected and highlighted as missing items and their values
will be restored in SoS by interpolation. Missing items also include all interior nodes
and the FEM boundary nodes that are located at topological areas like sharp edges
where a nodal normal vector cannot be computed robustly.

• The Incompatible (explicit closest point projection) mapper searches along rays
that are not necessarily parallel to the boundary normal vector to try to find the closest
point on the measurement surface that is closest to each boundary node of the
reference mesh. This mapper may be inefficient for large search distances and find
meshes.

• The User specified direction mapper is a special case. In this mapper, you can define
a direction along which to search the intersection of the ray, starting from each
reference mesh boundary node with the boundary segments of the measurement.
This is interesting when dealing with data that is typically associated with flat surfaces.

• Most other mesh mappers are special mappers for grids (like matrix, image, or signal
data) or for mapping point cloud data without geometric deviations. These mappers
are not applicable here.

9. Click Settings to specify settings for the mesh mapper.

Here are descriptions of some of the important settings:

Maximum search distance

This is the maximum distance of allowed deviation that will be detectable by the
mapping algorithm. If the maximum search distance is smaller than the distance of
a projection point, the projection point will be marked as missing and the
corresponding deviation value will be interpolated in SoS based on the neighboring
values.

If the magnitude of geometric deviation is known, use this value. Otherwise, start
with a large value. You may typically need to import all data twice: First with a large
search distance. Then analyze if any erroneous detections appeared. This can happen
at sharp corners or at the boundaries, but sometimes it can also happen in between
(mostly due to numerical round off errors). To find and resolve erroneous detections:

a. Compute the lower and upper envelope over all designs of CoorDeviation-
Normal by selecting Statistics → Value ranges and then Minimum sample
values and Maximum sample values. For more information, see Calculating
a Range of Minimum Sample Values and Calculating a Range of Maximum
Sample Values in the Statistics on Structures User's Guide.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
150 of ANSYS, Inc. and its subsidiaries and affiliates.
 Importing and Analyzing Measured Geometries

b. Visualize both side by side.

c. For the minimum sample value plot, identify the smallest (negative) value
that is acceptable. For the maximum sample value plot, identify the largest
(positive) value.

d. Delete all imported data.

e. Reimport the data with a modified maximum search distance that cuts off
the erroneous detections.

Adjust coordinate system

For some cases, SoS can align the measurements automatically to the position of
the reference mesh by applying a rigid body motion before the nodal coordinate
deviations are computed and the data mapping is applied. The default is no, but
you can choose from these transformation types:

• Auto translate: Moves the measurement according to center of origin.

• Auto translate and rotate (simple): Moves the measurement according to the
center of origin and rotates by comparing the inertia tensor.

Caution:

For nearly symmetric bodies this approach may lead to the wrong
rotation.

• Auto translate and rotate (best fit): While similar to Auto translate and rotate
(simple), this iterative algorithm minimizes the average coordinate deviation
between the measurement and the reference mesh that is obtained by the closest
point projection. The closest point projection algorithm is applied according to
the selected mesh mapper.

• Auto translate and rotate pre-aligned (best fit): The only difference between
this option and the previous one is that this option does not apply the simplified
move and rotation based on the inertia tensor. This option, which can be used for
pre-aligned data, tries to avoid that the auto-rotation may produce erroneous
results when dealing with symmetric bodies.

If FEM meshes are used for the reference mesh and measurement and nodal named selections
are stored in the mesh files, then you can specify the auto-alignment algorithms in such a
way that they do not align with respect to the whole boundary but only to the boundary
nodes being part of the named selection. You can use this feature to define reference points
or reference areas in the measurements.

10. Click OK to save your settings.

11. Before continuing the statistical analysis, verify that the mapping algorithms are working
properly:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 151
Measurements and Noise Tutorials

a. In the visualization, check the histogram of the value palette for potential outliers (very
small or very large deviation values).

b. If there are missing items, check the distribution for CoorDeviationNormal by selecting
Statistics → Errors and differences → Minimum sample values. The result shows you
the percentage by which a projection could not be found for each FEM node. This may
be acceptable for sharp edges or at free boundary edges or for interior nodes but not for
larger areas, which is a sign for a bad coordinate system. Use the traffic light plot here
and choose a small number such as 0.0001 as the lower bound to highlight areas with
false projections.

c. Identify the designs for which the error appears. Select some nodes in the areas with
erroneous missing items. In the visualization, select the command Create scalars. List in
the data object table all scalar designs. For designs with missing items, no scalar was
created. These need to be checked in more detail for false mesh mapping.

12. Click Next and define the design directory names to be imported and the corresponding
design numbers.

13. Click Finish.

Analyzing Measurements
When dealing with geometric measurements, always consider using RPCA for statistical filtering. You
should compare the means and standard deviations of the original and filtered quantities to check
plausibility of the input data and the filter. If the filtered data is acceptable, continue all analysis based
on the filtered data.

Standard statistical evaluations are for CoorDeviationNormal:

Mean

Gives "average" coordinate deviation in the production process that can indicate some
dangerous trends.

Standard deviation

Shows areas with large variation. These could be areas with an unstable production process.
Areas with nearly zero variation indicate post-production manufacturing steps like polishing.
Always watch for these potentially critical indicators:

• Values with a large mean and small variation

• Values with a zero mean and a large variation

Minimum sample values

Gives the lower bound of deviation among all measurements.

Maximum sample values

Gives the upper bound of deviation among all measurements.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
152 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating Imperfect Geometries

Range of sample values

Gives the actual range of variation among all measurements.

Quantiles

Provide for computing lower and upper bounds based on probabilistic measures, such as
the 0.05 quantile (lower 5% exceedance) and the 0.95 quantile (upper 5% exceedance) values.

Mean + k-sigma values

While equivalent to a quantile computation, this metric can also be applied for small numbers
of measurements.

Standard errors

Indicate if enough measurements were analyzed to have robust estimators for the mean or
variance.

If enough data is available, consider creating an empirical random field model of CoorDeviationNor-
mal. Such a model would show how many different variation patterns (production mechanisms) act
on the structure and give you an idea of independent regions and number of required shape
parameters.

Creating Imperfect Geometries

This multi-part tutorial shows how to create imperfect geometries:
Preparing Statistical Shape Models
Configuring SoS as a Solver

Preparing Statistical Shape Models

For the generation of imperfect geometries, you typically make use of random field models being a
statistical model for spatial data.

Note:

A field MOP can be used if you can predict the geometric changes from other uncertain
parameters. Typically, you use random fields. The workflow with a field MOP is nearly
identical.

SoS provides the following models:

Synthetic random fields

They produce sine-wave-like variation patterns. The goal is to represent as much statistical
variation with the smallest number of parameters. This kind of model is used if there is not
enough information available for estimating the spatial correlation, which is less than 10
measurements for 3 parameters or less than 100 measurements for 10 parameters. Instead,
the correlation structure is defined by engineering assumption using an autocorrelation
model.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 153
Measurements and Noise Tutorials

• If no measurements are available, you typically define a mean of zero and a standard
deviation that is associated with the 95% confidence interval of the desired variation
windows.

• If a single measurement is available, you can use a zero mean and use the measurement
as an indicator of the standard deviation. Or you can use the measurement as the mean
and apply a homogeneous standard deviation.

• If some measurements are available, you can estimate the mean and standard deviation
from the measurement and combine both with an autocorrelation model.

Synthetic fields are typically applied to a single scalar field. For the geometric deviation,
this is the coordinate deviation normal to the boundary CoorDeviationNormal.

Free-form variation models

They are similar to synthetic random field models but instead of minimizing the number of
parameters (and obtaining sine-like global variation patterns), they focus on localizable
variation shapes where each parameter is associated with a limited region on the boundary.
This is realized through support points and RBF functions being centered around the supports.
Use free-form variation models if you are interested in analyzing the relation of the response
fields (such as stresses) with respect to the location of the applied geometric imperfections.

Free-form variation fields are typically applied to a single scalar field. For the geometric
deviation, this is the coordinate deviation normal to the boundary CoorDeviationNormal.

Empirical random fields

They analyze mean, standard deviation, and correlation structure from measurements and
translate them into a parametrization with a minimum number of coefficients. The coefficients
are also computed as scalar numbers for each measurement. When exporting the coefficient
values to optiSLang postprocessing, you can determine the actual random distribution type,
including statistical moments and correlations among parameters. In most cases, however,
it is suitable to assume the central limit theorem and assume uncorrelated standard-normal
distributed coefficients.

Empirical random field models are typically applied to a cross-correlated random field to
improve the representation of the deviation vectors, including statistical rotations. You create
the cross-correlated field by collecting CorrDeviation[1], CoorDeviation[2], and CoorDevi-
ation[3].

Empirical random fields are the most accurate representation of statistical shape models.

After creating the random field model, always visualize the scatter shapes to check model plausibility
and compare statistical metrics such as standard deviation with the original data.

When finished, you can configure SoS as a solver.

Configuring SoS as a Solver

When creating imperfections, you must configure SoS as a solver. Before you start, consider the output
format and how SoS needs to interact with the CAE solver. The goal is to modify an existing process
chain as little as possible. The process also must be one that can be automated, meaning loading

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
154 of ANSYS, Inc. and its subsidiaries and affiliates.
 Creating Imperfect Geometries

conditions shall not be changed due to the applied morphing. To achieve this, you must create one
solver chain template and plug SoS into the solver chain immediately before the solution process
(after applying all loading and boundary conditions). Furthermore, the mesh must be the same as
the one SoS uses as the reference mesh.

• For Ansys Mechanical, a new file is created that contains the APDL commands to be included
into the file [Link].

• For LS-DYNA, the Dynain file is modified directly.

• For Abaqus, the INP file that contains the mesh is modified by SoS. The INP file does not
support part assemblies.

• For Nastran, the BDF file that contains the mesh is modified by SoS.

In SoS, you perform these steps:

1. Select File → Export for simulation → Generate field objects in optiSLang.

2. Set the path to the reference design.

You are setting the template path, which serves as the design directory in optiSLang.

3. Depending on the solver, select either Modify file or Create new file and then select the
file name and the correct file format (such as Ansys Mechanical input files).

4. Depending on the type of model, select how SoS is to generate the geometric deviation:

• If a single scalar field is used, for Export item, select Normal coordinate deviation.
In the column Quantity ident, select the quantity CoorDeviationNormal. In the
column Design ident, select Generate random field or Approximate Field MOP.
SoS will then translate the nodal normal deviation into the x, y, z components according
to the nodal normal vector.

• If a cross-correlated field is used, for Export item, select X/Y/Z coordinate deviation.
In the column Quantity ident, select the quantities CorrDeviation[1], CoorDevi-
ation[2], and CoorDeviation[3] respectively. In the column Design ident, select
Generate random field or Approximate Field MOP. SoS will then directly apply the
generated data for each x, y, and z component individually to the FEM node
coordinates.

5. For testing purposes, click Next to continue.

Note:

For the final workflow, you should always activate mesh smoothening. While
this requires large CPU resources to generate the actual morphed meshes,
mesh smoothening ensures that no negative element volumes are created.

6. Define where all SoS solver data is to be exported.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 155
Measurements and Noise Tutorials

By default, you can create a single simulation archive file. Alternatively, you can export all
data to a directory. Herein you see all binary and SoS script files that are used in solver mode.
You can edit and extend the script files in this mode.

7. Close SoS.

8. For Ansys Mechanical:

a. Open the project.

b. To use the SoS extension for Ansys Mechanical to import the simulation archive
directly, from the extension's toolbar, select Import → Import external model. For
more information, see Importing External Models in the Statistics on Structures User's
Guide.

This creates a Generate variations tree item where you can see the random field
parameters.

c. Either chose fixed numbers or export the random field coefficients as parameters to
the Ansys Workbench parameter table.

In optiSLang, they appear as parameters in the Ansys Workbench node

d. For the robustness study, select standard-normal as the distribution type with mean
set to 0 and standard deviation set to 1.

e. Before starting with the robustness analysis, run and validate the solver chain for a
single design.

9. For other solvers:

a. Create the solver chain in optiSLang for the standard process, splitting it into at least
two nodes if possible.

The first node should copy and prepare all input files. The second node should start
the solving process.

b. Insert the Generate_SoS node just before the solution node.

c. In the Generate_SoS node, chose the simulation archive file or the CSV file from the
simulation directory as inputs.

The node will then automatically provide the random field coefficients and set the
mean and standard deviation.

d. Register them as input parameters in the node.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
156 of ANSYS, Inc. and its subsidiaries and affiliates.
 Performing Uncertainty Quantification Based on Measured Geometries

e. Before starting the robustness analysis, run and validate the solver chain for a single
design.

Note:

When you want to solve the measurements one-to-one, you do not need a random
field model. In this case, you export the imported measurements directly into the
appropriate format:

1. Prepare the output files in the Design directories (even if you want to create
new files).

For example, prepare Design0001/mesh.k, Design0002/mesh.k, and

so on.

2. Select File → Process multiple designs and then either Modify field designs
or Export field designs.

The procedure is very similar to the preparation of SoS as a solver. However, on the
second wizard page, you do not export simulation archives but define the design
numbers and design directories to which the modified geometry data is to be exported.
When importing the APDL snippets into Ansys Mechanical, you use the APDL command
input to read the file created by SoS.

Performing Uncertainty Quantification Based on Measured Geometries

This example demonstrates a workflow for applying the true geometry of a scanned compressor wheel
as obtained from a 3D laser scan to Ansys Mechanical with minimum effort. Further, the technology
can be used to generate new virtual geometries (for Monte Carlo-like studies) that are very close to the
variation patterns and statistics as found in the measurements.

Note:

A CAD0 reference geometry is usually a “perfectly” modelled geometry with no

imperfections, in contrast to a laser-scanned real-world geometry.

Workflow Benefits
The workflow described in this example provides these benefits:

• Easily maps the geometric measurements given in an STL file to a CAD0 reference geometry,
allowing you to work on the FEM mesh, which is meshed only once, rather than on the CAD
model

• Can be automated

• Applies and maps measurements onto the CAD0 FEM mesh and morphs the mesh accordingly

• Creates a statistical shape model that auto-parametrizes the geometric variations as found in
the measurements

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 157
Measurements and Noise Tutorials

• Helps to analyze the statistical properties of the geometric variations

• Helps to analyze the influence of the geometric variations onto the structural performance

• Helps to do a sensitivity analysis identifying the importance of geometric imperfections compared

with other scatter variables in robustness analysis

Workflow Applications
The workflow can be used in scenarios for:

• Statistically analyzing the influence of geometry variations on fatigue behavior, lifetime, quality,
structural performance, efficiency, and more, to assess the robustness and sensitivity of the
structure

• Bringing together CAD0 models and geometric measurements such as those seen in production
tolerances, wear, design for manufacturing, and more

• Identifying allowed tolerance windows to improve quality control after manufacturing

• Analyzing sensitive structural components like compressor wheels, machine housings, molding
parts, and more

This example starts with a measurement after manufacturing (an already preprocessed STL file) and an
Ansys Workbench project containing the structural analysis of a compressor wheel for the CAD0 geometry.

Summary of the Solution Steps for the Uncertainty Quantification

A summary follows of the solution steps for performing uncertainty quantification of the compressor
wheel based on measured geometries:

1. Use 3D scan data of models to represent the actual imperfect shape.

2. Prepare a mesh of the nominal CAD geometry in Ansys Mechanical.

3. Load both the 3D scan data and the mesh into SoS and perform deviation evaluation and
morphing export to Mechanical.

4. Morph the mesh inside Mechanical to represent the imperfect geometry for simulation.

This image shows the workflow:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
158 of ANSYS, Inc. and its subsidiaries and affiliates.
 Performing Uncertainty Quantification Based on Measured Geometries

Preparing the Mesh of the Nominal CAD Geometry

To prepare the mesh of the nominal CAD geometry:

1. In Ansys Workbench, open the archive file named [Link] in

examples\ansys\turbine.

2. Rename the project to TurbineWheel and save it as a project file in the same folder.

3. In the Static Structural system named Static Imperfect, right-click the Model cell and select
Edit to start Ansys Mechanical.

4. In the project tree, right-click Mesh and select Update, either keeping the settings as they
are or changing them per your preference.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 159
Measurements and Noise Tutorials

5. In the project tree under Named Selections, look at those that have been predefined and
optionally define any additional faces that you want to morph.

You can define as many faces to morph as you want, but they must be part of one named
selection because you can select only one named selection inside SoS.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
160 of ANSYS, Inc. and its subsidiaries and affiliates.
 Performing Uncertainty Quantification Based on Measured Geometries

Additionally, you want to define a named selection with nodes that should be fixed later in
SoS. This must be a set of nodes that is not part of the node set that will be morphed. In this
example, the named selection Fixed_Nodes already exists.

6. In the project tree, select Static Structural and either keep the boundary conditions and
loads as they are or change them per your preference.

7. In the project tree, select Morphing.

8. In the code snippet, change the value for the variable prep_mesh to 1.

Note:

Changing prep_mesh to 1 triggers Mechanical to stop before it starts solving

the model. Thus, Mechanical will produce only the Ansys input file ([Link]),
which contains all finite element data of the model. This [Link] file will later
be used to read the FE data into SoS.

9. Change the solver units to millimeters and tons:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 161
Measurements and Noise Tutorials

Caution:

Because the STL file is prepared in millimeter units, you must change the units
in Mechanical to millimeter units before solving. If the scan and the mesh are
not of the same size, the morphing will fail.

10. In the project tree, right-click Solution for this Static Structural system and select Solve.

Mechanical starts solving and will stop with an error, which is fine, because no simulation was run.
Your objective is only to produce the mesh file ([Link]) with all the finite element information and
named selections for import into SoS.

Note:

Aligning the STL file with the CAD geometry file is not required to continue this
example. However, you must align 'fresh' scan data with an STL file. For more
information, see Aligning the STL and CAD Geometry Files in SpaceClaim (p. 169).

Importing the Mesh Data File and STL Scan File into SoS
As indicated in the following image, once you have prepared the mesh data file ([Link]) and
aligned STL scan file, you can import them into SoS.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
162 of ANSYS, Inc. and its subsidiaries and affiliates.
 Performing Uncertainty Quantification Based on Measured Geometries

To import these files into SoS:

1. Start a new SoS project, choosing the [Link] file that was created in
examplesansys\turbine as the reference mesh and naming the project TurbineWheel.

2. Set the reference named selection:

a. Select File → Mesh → Set reference named selection.

b. In the window that opens, make these selections:

3. Import the STL file:

a. Select File → Process multiple designs → Import field designs.

b. In the Import Designs window, click Add file and open the STL file in your working
directory (TurbineWheel_Scan.stl).

SoS reads the STL file and gives you a summary of the imported data:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 163
Measurements and Noise Tutorials

c. Click OK.

In the Import designs window, the file TurbineWheel_Scan.stl is shown in the list
of files to parse.

d. For Mesh mapper, select Incompatible and then click Settings.

e. In the Configure incompatible mesh mapper window, set Maximum search distance
to a reasonable value that corresponds to the maximum deviation observed between the
scan and the nominal CAD geometry.

For this example, set the value to 1.0 mm.

f. Click OK.

In the Data to import area of the Import designs window, select only the CoorDeviation-
Normal check box in the Imported ident column.

g. Click Next.

h. Leave the settings in the Design directories area as they are.

i. Click Finish.

SoS imports the scan and evaluates the deviations compared to the nominal mesh. This
takes about three minutes.

4. Save the SoS database:

a. Select File → Save database as.

b. In the window that opens, enter [Link] as the file name and click Save.

5. Export the morphing script:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
164 of ANSYS, Inc. and its subsidiaries and affiliates.
 Performing Uncertainty Quantification Based on Measured Geometries

a. Select File → Process multiple designs → Modify/export field design.

b. In the Export Designs window, set the path to your reference design to your working
directory (examples\TurbineWheel).

c. Click Create new file.

d. In the window that opens, enter morphing as the file name and click Save.

e. In the Export designs window, for the export item Normal coordinate deviation, select
CoorDeviationNormal in the Quantity ident column.

f. Under the list of items to export, select the Use mesh smoothening check box.

g. Click Next.

h. Leave the settings in the Design directories area as they are.

i. Click Finish.

SoS exports the morphing script. This takes about 10 minutes.

Using the Morphing Script in a Mechanical Solve

To use the exported morphing script in a Mechanical solve:

1. In the project tree, select Morphing.

2. In the code snippet, change the value for the variable prep_mesh to 0.

3. In the project tree, right-click Solution for this Static Structural system and select Solve.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 165
Measurements and Noise Tutorials

4. In the project tree, select Solution for this Static Structural system and, in the Details view, set
Mesh Source (Beta) to Result File.

5. Visualize and observe the results.

The following results are for static with 75000 RPM.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
166 of ANSYS, Inc. and its subsidiaries and affiliates.
 Performing Uncertainty Quantification Based on Measured Geometries

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 167
Measurements and Noise Tutorials

As expected, the compressor blades are longer, leading to lowered eigenfrequencies.

Observing Differences Between the Nominal Geometry and Real Geometry

To observe differences between the nominal geometry and real geometry:

1. Go to the Ansys Workbench folder path: …\TurbineWheel_files\dp0\SYS-1\MECH\

In this folder, two STL files (nominal_geometry.stl and real_geometry.stl) were

saved after solving the Static Structural system using the [Link] APDL macro.

2. Open SpaceClaim and import these files.

3. Observe differences of the geometry before and after morphing.

4. Additionally, import the original STL file (TurbineWheel_Scan.stl) that is in your working
directory (location of the Workbench project).

5. In the Measure ribbon, click Deviations.

6. In the project tree, under Design2 → real_geometry, select TurbineWheel_Scan → Facets

to be the source and then press and hold down the Ctrl key and select real geometry →
real_geometry.

Deviations are shown.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
168 of ANSYS, Inc. and its subsidiaries and affiliates.
 Performing Uncertainty Quantification Based on Measured Geometries

7. In the Options Analysis window, change the evaluated tolerances as preferred.

Aligning the STL and CAD Geometry Files in SpaceClaim

To align an STL file with 'fresh' data to a CAD geometry file in SpaceClaim:

1. Start SpaceClaim and open the STL scan file (TurbineWheel_Scan.stl).

2. Observe the facet density and features of the STL file.

For this example, you want to keep the facet density as it is. The STL file has already been
prepared to have the density needed to cover all features.

STL files with ‘fresh’ scan data must be aligned to fit the position of the nominal CAD geometry.
The number of facets must be dramatically reduced, to have fewer than 100k facets if possible.
To reduce the number of facets on 'fresh' scan data, on the Facets ribbon, you would click
Reduce.

3. Align the scan with the nominal CAD geometry that you used for meshing inside Ansys
Mechanical.

The geometry in this example is already perfectly aligned.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 169
Measurements and Noise Tutorials

Applying Displacement of Nodes of a Mesh by Measurement on Another

Geometry
This tutorial explains how to use the Apply Measurement option in the ACT plugin for Ansys Mechanical
to apply displacement of nodes of a mesh by measurement on another geometry. Once you load the
ACT plugin, the workflow is to edit the Mechanical model in an Ansys Workbench project and generate
a new "geometry":

1. Select the set of moved nodes.

2. Select the set of fixed nodes.

3. Specify the name of the new "geometry'" to create.

4. Select the part or parts to use.

5. Generate the new "geometry" by setting files to call the SoS mapping algorithm that applies
displacement on the input mesh for the solver.

The following topics explain how to use the supplied Workbench project file simple_cube.wbpz to
try out the Apply Measurement option:
Setting Up the Workbench Project and Loading the ACT Plugin
Editing the Mechanical Model and Generating the New "Geometry"

Setting Up the Workbench Project and Loading the ACT Plugin

To set up the Workbench project and load the ACT plugin:

1. In Workbench, open the file simple_cube.wbpz in examples\ansys\simple_cube.

2. Rename the project file as simple_cube_tutorial4 and save it in the same folder.

3. If you see a message indicating that the SoS extension will be upgraded permanently when
you save the project, click OK.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
170 of ANSYS, Inc. and its subsidiaries and affiliates.
 Applying Displacement of Nodes of a Mesh by Measurement on Another Geometry

4. Select Extensions → ACT Start Page and then click Manage Extensions to open the
graphic-based Extension Manager. For more information, see Extension Manager in the ACT
Developer's Guide.

Many ACT extensions are already installed and loaded in this project, including the SoS
extension, which is the ACT plugin for Mechanical.

5. Close the tab for the ACT Start Page.

Editing the Mechanical Model and Generating the New "Geometry"

To edit the Mechanical model and generate the new "geometry":

1. In the Workbench Project Schematic, right-click the Model cell and select Edit to open the
model in Mechanical.

2. In the Outline view, select Mesh.

3. Click the SoS tab in the ribbon.

You can now see the Import, Create, and Export menu options for the SoS extension.

4. Select Create → Apply Measurement.

In the Outline view under Static Structural, an Apply measurement node is added.

5. Select the Apply measurement node.

In the Details view, the properties required are:

• A set of nodes that are moved by the target geometry (geometry selection or named
selection)

• A set of nodes that are fixed on the initial mesh (geometry selection or named selection)

• Mesh part selection (geometry selection or named selection)

• Scan data file (STL, DAT, or CDB) to serve as the target for the moved nodes

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 171
Measurements and Noise Tutorials

• Maximum search distance value for use in the SoS algorithm that detects the geometry
deviations

This image shows how to complete the required properties for this tutorial.

• The set of moved nodes is a named selection: TopSurf_N.

• The set of fixed nodes is a named selection: BottomSurf_N.

• The mesh part is selected by clicking the part.

• The scan data file is sos_mesh.cdb in examples/ansys/simple_cube.

• The maximum search distance value is 10.

6. To define the displacement, in the project tree, right-click Apply measurement and select
Generate.

The following results are generated:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
172 of ANSYS, Inc. and its subsidiaries and affiliates.
 Applying Displacement of Nodes of a Mesh by Measurement on Another Geometry

The STL file shows that the top face is not parallel to the bottom face. The edge is displaced 5 mm.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 173
Measurements and Noise Tutorials

The boundary condition is a pressure on the top surface. This means that the STL geometry creates
a non-null deformation along the axes:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
174 of ANSYS, Inc. and its subsidiaries and affiliates.
 Applying Displacement of Nodes of a Mesh by Measurement on Another Geometry

You can verify this by not using the target geometry in the STL file. The result is that the deformation
along the X axis is constant in the Y direction.

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 175
Measurements and Noise Tutorials

The equivalent stress is constant:

Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
176 of ANSYS, Inc. and its subsidiaries and affiliates.