Work solution for the model update solution process

The work solution for the model update solution process is a SOL 200 Model Update solution. This solution is a modified version of the SOL 200 Design Optimization solution.

Before you solve the SOL 200 Model Update solution, you must do the following:

• Select the model reduction method.

• Create a DOF set for model reduction.

• Create design variables.

Model reduction methods

Unless your finite element model is very small, you need to reduce it in size to allow the model update solution process to optimize efficiently. You can use either the physical (Guyan) reduction method or the modal reduction method.

• In the physical (Guyan) reduction method, the FE model is reduced to physical degrees-of-freedom specified by the Analysis Set (ASET).

• In the modal reduction method, the FE model is reduced to n modal coordinates where n is the number of modes specified in the Lanczos method modeling object. You must also specify the Degree of Freedom Set (USET,U2) to limit the size of eigenvectors used in the Model Update solution process.

See Model reduction in a SOL 200 Model Update solution for more information.

DOF sets for model reduction

The model update solution process requires sensitivity matrices from the SOL 200 Model Update solution. Because this can be a large amount of data, it is therefore essential to operate on a reduced set of degrees of freedom. Typically, the size of the DOF set should not exceed a few thousand DOF. When you use fewer DOF, the amount of data is smaller and the optimization process is faster.

Ideally, the work DOF set to be used for model reduction contains the same DOFs as the test model's sensors. To obtain this DOF set, you can:

• Automatically create a matching DOF set from a modal correlation solution process between a work solution and a reference solution.

• Automatically create a matching DOF set from a pre-test solution process sensor selection configuration.

• Manually create the DOF set. This DOF set should include all of the test model's sensor DOF in order to use all information available.

When the work and sensor DOFs differ in a Model Update solution process, differences may exist between the MAC mode shape metric reported under the Mode Pairs and Errors nodes. This happens because model update errors are computed using the intersection of work and sensor DOFs, whereas the MAC mode shapes are computed using the sensor DOFs.

For more information, see:

• Correlation workflows and Generate a DOF set matching the node map

• Pre-test workflows and Generate a DOF set that matches the sensor location

• Create a DOF set

Design Variable modeling objects

Design variables are independent quantities that the solver can vary to achieve the optimum design. Upper and lower limits define the allowable range of variation. The design variables for the SOL 200 Model Update solution are defined in Design Variable modeling objects. Of the four types of the design variables that exist, the Model Update solution process supports only the physical property or material property types.

The Model Update solution process gets the design variables from the SOL 200 Model Update solution.

For more information, see:

• Design variables

• Supported design variables for model update solution process

Where do I find it?

Application	Pre/Post
Prerequisite	An active model update solution process
Command Finder	Solve Work Solution
Menu	Tools→Model Update→Solve Work Solution

How do I

Create design variables for the model update solution process

Create multiple physical design variables

Create the work solution for the model update solution process

Solve the work solution for the model update solution process

Learn more

Create Multiple Design Variables

Look up more details

Supported design variables for model update solution process

Quick links

Command reference

Pre/Post video examples

Bulk Entry Descriptions

Simcenter 3D tutorials

Browse Simcenter 3D help by product area

Work solution for the model update solution process, Simcenter 3D 2021.1 Series

© 2020 Siemens

window.mainLanguage="en_US"

window.delivId=""

window.projectId=""

MathJax.Hub.Config({ TeX: { extensions: ["autoload-all.js"] }, tex2jax: { displayMath: [ ] }, "SVG": { scale: 125 } });