ANSYS Mechanical APDL 2016 - Advanced Analysis Guide

ANSYS Mechanical APDL Advanced Analysis
Guide
ANSYS, Inc. Release 17.0

Southpointe January 2016
2600 ANSYS Drive
Canonsburg, PA 15317 ANSYS, Inc. is
ansysinfo@ansys.com certified to ISO
9001:2008.
http://www.ansys.com
(T) 724-746-3304
(F) 724-514-9494
Copyright and Trademark Information
© 2015 SAS IP, Inc. All rights reserved. Unauthorized use, distribution or duplication is prohibited.
ANSYS, ANSYS Workbench, Ansoft, AUTODYN, EKM, Engineering Knowledge Manager, CFX, FLUENT, HFSS, AIM
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 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.
Disclaimer Notice
THIS ANSYS SOFTWARE PRODUCT AND PROGRAM DOCUMENTATION INCLUDE TRADE SECRETS AND ARE CONFID-
ENTIAL 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. is certified to ISO 9001:2008.
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
1. Variational Technology ........................................................................................................................... 1
1.1. Harmonic Sweep Using VT Accelerator .............................................................................................. 1
1.1.1. Structural Elements Supporting Frequency-Dependent Properties ............................................ 2
1.1.2. Harmonic Sweep for Structural Analysis with Frequency-Dependent Material Properties ........... 2
1.1.2.1. Beam Example ................................................................................................................ 3
2. Rezoning ................................................................................................................................................. 5
2.1. Benefits and Limitations of Rezoning ................................................................................................. 5
2.1.1. Rezoning Limitations ............................................................................................................... 7
2.2. Rezoning Requirements .................................................................................................................... 8
2.3. Understanding the Rezoning Process .............................................................................................. 11
2.3.1. Overview of the Rezoning Process Flow .................................................................................. 11
2.3.2. Key Commands Used in Rezoning .......................................................................................... 14
2.4. Step 1: Determine the Substep to Initiate Rezoning .......................................................................... 15
2.5. Step 2. Initiate Rezoning .................................................................................................................. 16
2.6. Step 3: Select a Region to Remesh ................................................................................................... 16
2.7. Step 4: Perform the Remeshing Operation ....................................................................................... 17
2.7.1. Choosing a Remeshing Method .............................................................................................. 17
2.7.1.1. Remeshing Using a Program-Generated New Mesh (2-D) ................................................ 18
2.7.1.1.1. Creating an Area to Remesh .................................................................................. 18
2.7.1.1.2. Using Nodes From the Old Mesh ........................................................................... 18
2.7.1.1.3. Hints for Remeshing Multiple Regions .................................................................. 19
2.7.1.1.4. Generating a New Mesh ....................................................................................... 19
2.7.1.2. Remeshing Using a Generic New Mesh (2-D and 3-D) ..................................................... 19
2.7.1.2.1. Using the REMESH Command with a Generic New Mesh ........................................ 20
2.7.1.2.2. Requirements for the Generic New Mesh ............................................................... 20
2.7.1.2.3. Using the REGE and KEEP Remeshing Options ....................................................... 21
2.7.1.3. Remeshing Using Manual Mesh Splitting (2-D and 3-D) .................................................. 23
2.7.1.3.1. Understanding Mesh Splitting ............................................................................... 23
2.7.1.3.2. Geometry Details for Mesh Splitting ..................................................................... 23
2.7.1.3.3. Using the REMESH Command for Mesh Splitting .................................................... 26
2.7.1.3.4. Mesh-Transition Options for 2-D Mesh Splitting ..................................................... 26
2.7.1.3.5. Mesh-Transition Options for 3-D Mesh Splitting ..................................................... 28
2.7.1.3.6. Improving the Local Topology of Tetrahedral Meshes via Edge and Face Swap-
ping ................................................................................................................................... 30
2.7.1.3.7. Improving Tetrahedral Element Quality via Mesh Morphing .................................. 31
2.7.2. Mesh Control ......................................................................................................................... 32
2.7.3. Remeshing Multiple Regions at the Same Substep .................................................................. 33
2.8. Step 5: Verify Applied Contact Boundaries, Surface-Effect Elements, Loads, and Boundary Condi-
tions ..................................................................................................................................................... 34
2.8.1. Contact Boundaries ................................................................................................................ 34
2.8.2. Surface-Effect Elements ......................................................................................................... 34
2.8.3. Pressure and Contiguous Displacements ................................................................................ 34
2.8.4. Forces and Isolated Applied Displacements ............................................................................ 35
2.8.5. Nodal Temperatures ............................................................................................................... 35
2.8.6. Other Boundary Conditions and Loads ................................................................................... 35
2.9. Step 6: Automatically Map Variables and Balance Residuals .............................................................. 36
2.9.1. Mapping Solution Variables .................................................................................................... 36
2.9.2. Balancing Residual Forces ....................................................................................................... 36
2.9.3. Interpreting Mapped Results .................................................................................................. 37
2.9.4. Handling Convergence Difficulties .......................................................................................... 38
Release 17.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. v
Advanced Analysis Guide
2.10. Step 7: Perform a Multiframe Restart .............................................................................................. 38

2.11. Repeating the Rezoning Process if Necessary ................................................................................. 38
2.11.1. File Structures for Repeated Rezonings ................................................................................. 39
2.12. Postprocessing Rezoning Results ................................................................................................... 39
2.12.1. Using the Database Postprocessor (POST1) ........................................................................... 39
2.12.1.1. Listing the Rezoning Results File Summary ................................................................... 40
2.12.1.2. Animating the Rezoning Results ................................................................................... 40
2.12.2. Using the Time-History Postprocessor (POST26) .................................................................... 40
2.13. Rezoning Restrictions .................................................................................................................... 41
2.14. Rezoning Examples ....................................................................................................................... 41
2.14.1. Example: Rezoning Using a Program-Generated New Mesh ................................................... 42
2.14.1.1. Initial Input for the Analysis .......................................................................................... 42
2.14.1.2. Rezoning Input for the Analysis .................................................................................... 44
2.14.2. Example: Rezoning Using a Generic New Mesh ...................................................................... 45
2.14.2.1. Initial Input for the Analysis .......................................................................................... 45
2.14.2.2. Exporting the Distorted Mesh as a CDB File .................................................................. 47
2.14.2.3. Importing the File into ANSYS ICEM CFD and Generating a New Mesh .......................... 48
2.14.2.4. Rezoning Using the New CDB Mesh ............................................................................. 49
3. Mesh Nonlinear Adaptivity ................................................................................................................... 51
3.1. Mesh Nonlinear Adaptivity Benefits ................................................................................................. 51
3.1.1. Rubber Seal Simulation .......................................................................................................... 52
3.1.2. Crack Simulation .................................................................................................................... 55
3.1.3. 3-D Metal Forging Simulation ................................................................................................. 58
3.1.4. 2-D Metal Extrusion Simulation ............................................................................................... 61
3.2. Mesh Nonlinear Adaptivity Usage Considerations ............................................................................ 63
3.2.1. Mesh Nonlinear Adaptivity Requirements and Limitations ....................................................... 64
3.3. Understanding the Mesh Nonlinear Adaptivity Process .................................................................... 64
3.3.1. Checking Nonlinear Adaptivity Criteria ................................................................................... 65
3.3.1.1. Defining Element Components ...................................................................................... 65
3.3.1.2. Defining Nonlinear Adaptivity Criteria ............................................................................ 66
3.3.1.3. Defining Criteria-Checking Frequency ............................................................................ 66
3.4. Mesh Nonlinear Adaptivity Criteria .................................................................................................. 66
3.4.1. Energy-Based Criterion ........................................................................................................... 66
3.4.2. Position-Based Criterion ......................................................................................................... 67
3.4.3. Contact-Based Criterion ......................................................................................................... 67
3.4.3.1. Number of Contacting Elements .................................................................................... 67
3.4.3.2. Contact Surface Wear .................................................................................................... 67
3.4.4. Mesh-Quality-Based Criterion ................................................................................................. 68
3.4.4.1. SHAPE Option ............................................................................................................... 68
3.4.4.2. SKEWNESS Option ......................................................................................................... 68
3.5. Specifying Criteria-Checking Frequency .......................................................................................... 69
3.6. Generating the New Mesh ............................................................................................................... 69
3.6.1. Generating a New Mesh via Splitting and Morphing ................................................................ 70
3.6.2. Generating a New Mesh via General Remeshing ..................................................................... 73
3.6.2.1. Understanding Remeshing Regions and Domains .......................................................... 74
3.6.2.2. Optional Remeshing Controls ........................................................................................ 77
3.6.2.2.1. Boundary-Angle and Edge-Angle Control .............................................................. 77
3.6.2.2.2. Sculpting Layers Control ....................................................................................... 78
3.6.2.2.3. Global Sizing Control ............................................................................................ 80
3.6.2.2.4. Local Sizing and Gradient Control .......................................................................... 81
3.6.2.2.4.1. 2-D Size Gradient Control ............................................................................. 81
3.6.2.2.4.2. 3-D Local Sizing ............................................................................................ 84
vi of ANSYS, Inc. and its subsidiaries and affiliates.
3.6.2.2.5. Understanding the Remesh Log ........................................................................... 85

3.6.2.2.6. Known Remeshing Limitations ............................................................................. 87
3.6.2.2.6.1. Non-manifold Mesh Geometry ..................................................................... 87
3.6.2.2.6.2. Region Self-Contact Penetration .................................................................. 87
3.6.2.2.7. Dealing with Remeshing Failure ............................................................................ 88
3.6.2.2.7.1. Direct Remeshing Failure .............................................................................. 89
3.6.2.2.7.2.Your Expectation of Target Mesh Quality Is Not Met ....................................... 89
3.7. Convergence at Substeps with the New Mesh .................................................................................. 90
3.8. Controlling Mesh Nonlinear Adaptivity ............................................................................................ 90
3.9. Postprocessing Mesh Nonlinear Adaptivity Results .......................................................................... 91
3.10. Mesh Nonlinear Adaptivity Examples ............................................................................................. 91
3.10.1. Example: Rubber Seal Simulation .......................................................................................... 91
3.10.2. Example: Crack Simulation .................................................................................................... 93
3.10.3. Example: 3-D Metal Forging Simulation ................................................................................. 95
3.10.4. Example: 2-D Metal Extrusion Simulation .............................................................................. 96
4. 2-D to 3-D Analysis ................................................................................................................................ 99
4.1. Benefits of 2-D to 3-D Analysis ......................................................................................................... 99
4.2. Requirements for a 2-D to 3-D Analysis ............................................................................................ 99
4.3. Overview of the 2-D to 3-D Analysis Process .................................................................................. 101
4.3.1. Overview of the 2-D to 3-D Analysis Process Flow .................................................................. 101
4.3.2. Key Commands Used in 2-D to 3-D Analysis .......................................................................... 102
4.4. Performing a 2-D to 3-D Analysis ................................................................................................... 103
4.4.1. Step 1: Determine the Substep to Initiate .............................................................................. 103
4.4.2. Step 2: Initiate the 2-D to 3-D Analysis ................................................................................... 104
4.4.3. Step 3: Extrude the 2-D Mesh to the New 3-D Mesh .............................................................. 104
4.4.4. Step 4: Map Solution Variables from 2-D to 3-D Mesh ............................................................. 105
4.4.5. Step 5: Perform an Initial-State-Based 3-D Analysis ................................................................ 105
4.5. 2-D to 3-D Analysis Restrictions ..................................................................................................... 105
5. Initial State .......................................................................................................................................... 107
5.1. Specifying and Editing Initial State Values ...................................................................................... 107
5.1.1. Node-Based Initial State ....................................................................................................... 108
5.2. Initial State Application ................................................................................................................. 108
5.2.1. Initial Stress Application ....................................................................................................... 108
5.2.2. Initial Strain Application ....................................................................................................... 109
5.2.3. Initial Plastic Strain Application ............................................................................................. 110
5.2.4. Initial Creep Strain Application .............................................................................................. 110
5.2.5. Initial State with State Variables Application .......................................................................... 111
5.2.6. Node-Based Initial Strain Application .................................................................................... 111
5.2.7. Initial Pore Pressure and Void Ratio Application ..................................................................... 111
5.2.8. Function-Based Initial State .................................................................................................. 111
5.3. Initial State File Format .................................................................................................................. 112
5.4. Using Coordinate Systems with Initial State ................................................................................... 113
5.5. Initial State Limitations .................................................................................................................. 113
5.6. Example Problems Using Initial State ............................................................................................. 115
5.6.1. Example: Initial Stress (IST File) .............................................................................................. 115
5.6.2. Example: Initial Stress (INISTATE Command) .......................................................................... 116
5.6.3. Example: Initial Strain ........................................................................................................... 116
5.6.4. Example: Initial Plastic Strain ................................................................................................. 117
5.6.5. Example: Initial Creep Strain .................................................................................................. 118
5.6.6. Example: Initial Plastic Strain with State Variables .................................................................. 120
5.6.7. Example: Node-Based Initial Strain ........................................................................................ 123
5.6.8. Example: Initial Pore Pressure and Void Ratio ......................................................................... 124
of ANSYS, Inc. and its subsidiaries and affiliates. vii
5.6.9. Example: Function-Based Initial State .................................................................................... 126

5.7. Writing Initial State Values ............................................................................................................. 127
5.7.1. Example: Output From the INISTATE Command's WRITE Option ............................................. 127
6. Rotating Structure Analysis ................................................................................................................ 129
6.1. Understanding Rotating Structure Dynamics ................................................................................. 129
6.2. Using a Stationary Reference Frame ............................................................................................... 130
6.2.1. Campbell Diagram ............................................................................................................... 131
6.2.2. Harmonic Analysis for Unbalance or General Rotating Asynchronous Forces .......................... 133
6.2.3. Orbits ................................................................................................................................... 133
6.3. Using a Rotating Reference Frame ................................................................................................. 134
6.4. Choosing the Appropriate Reference Frame Option ....................................................................... 136
6.5. Example Campbell Diagram Analysis ............................................................................................. 137
6.5.1. Problem Description ............................................................................................................. 137
6.5.2. Problem Specifications ......................................................................................................... 137
6.5.3. Input for the Analysis ............................................................................................................ 137
6.5.4. Analysis Steps ...................................................................................................................... 138
6.6. Example Coriolis Analysis .............................................................................................................. 139
6.6.4. Analysis Steps ...................................................................................................................... 141
6.7. Example Unbalance Harmonic Analysis ......................................................................................... 142
6.7.4. Analysis Steps ...................................................................................................................... 145
7. Submodeling ....................................................................................................................................... 151
7.1. Understanding Submodeling ........................................................................................................ 151
7.1.1. Nonlinear Submodeling ....................................................................................................... 152
7.2. Using Submodeling ...................................................................................................................... 152
7.2.1. Create and Analyze the Coarse Model ................................................................................... 153
7.2.2. Create the Submodel ............................................................................................................ 154
7.2.3. Perform Cut-Boundary Interpolation ..................................................................................... 155
7.2.4. Analyze the Submodel ......................................................................................................... 156
7.2.5. Verify the Distance Between the Cut Boundaries and the Stress Concentration ...................... 158
7.3. Example Submodeling Analysis Input ............................................................................................ 159
7.3.1. Submodeling Analysis Input: No Load-History Dependency ................................................... 159
7.3.2. Submodeling Analysis Input: Load-History Dependency ........................................................ 160
7.4. Shell-to-Solid Submodels .............................................................................................................. 165
7.5. Where to Find Examples ................................................................................................................ 167
8. Element Birth and Death ..................................................................................................................... 169
8.1. Elements Supporting Birth and Death ........................................................................................... 169
8.2. Understanding Element Birth and Death ....................................................................................... 169
8.3. Element Birth and Death Usage Hints ............................................................................................ 170
8.3.1. Changing Material Properties ............................................................................................... 171
8.4. Using Birth and Death ................................................................................................................... 171
8.4.1. Build the Model .................................................................................................................... 171
8.4.2. Apply Loads and Obtain the Solution .................................................................................... 171
8.4.2.1. Define the First Load Step ............................................................................................ 171
8.4.2.1.1. Sample Input for First Load Step .......................................................................... 172
8.4.2.2. Define Subsequent Load Steps ..................................................................................... 172
8.4.2.2.1. Sample Input for Subsequent Load Steps ............................................................. 172
viii of ANSYS, Inc. and its subsidiaries and affiliates.
8.4.3. Review the Results ............................................................................................................... 172

8.4.4. Use Analysis Results to Control Birth and Death .................................................................... 173
8.4.4.1. Sample Input for Deactivating Elements ....................................................................... 173
8.5. Where to Find Examples ................................................................................................................ 173
9. User-Programmable Features and Nonstandard Uses ....................................................................... 175
9.1. User-Programmable Features (UPFs) .............................................................................................. 175
9.1.1. Understanding UPFs ............................................................................................................. 175
9.1.2. Types of UPFs Available ........................................................................................................ 176
9.2. Nonstandard Uses of the Program ................................................................................................. 177
9.2.1. What Are Nonstandard Uses? ................................................................................................ 177
9.2.2. Hints for Nonstandard Use .................................................................................................... 178
10. State-Space Matrices Export ............................................................................................................. 179
10.1. State-Space Matrices Based on Modal Analysis ............................................................................. 179
10.1.1. Examples of SPMWRITE Command Usage .......................................................................... 179
10.1.2. Example of Reduced Model Generation in ANSYS and Usage in Simplorer ........................... 180
10.1.2.1. Problem Description .................................................................................................. 180
10.1.2.2. Problem Specifications ............................................................................................... 181
10.1.2.3. Input File for the Analysis ........................................................................................... 181
11. Soil-Pile-Structure Analysis ............................................................................................................... 185
12. Coupling to External Aeroelastic Analysis of Wind Turbines ............................................................ 187
12.1. Sequential Coupled Wind Turbine Solution in Mechanical APDL ................................................... 187
12.1.1. Procedure for a Sequentially Coupled Wind Turbine Analysis ............................................... 187
12.1.2. Output from the OUTAERO Command ................................................................................ 188
12.1.3. Example Substructuring Analysis to Write Out Aeroelastic Analysis Input Data ..................... 189
13. Applying Ocean Loading from a Hydrodynamic Analysis ................................................................ 193
13.1. How Hydrodynamic Analysis Data Is Used .................................................................................... 193
13.2. Hydrodynamic Load Transfer with Forward Speed ........................................................................ 194
13.3. Hydrodynamic Data File Format .................................................................................................. 194
13.3.1. Comment (Optional) .......................................................................................................... 194
13.3.2. General Model Data ............................................................................................................ 195
13.3.3. Hydrodynamic Surface Geometry ....................................................................................... 195
13.3.4. Wave Periods ...................................................................................................................... 196
13.3.5. Wave Directions .................................................................................................................. 196
13.3.6. Panel Pressures ................................................................................................................... 197
13.3.7. Morison Element Hydrodynamic Definition ......................................................................... 197
13.3.8. Morison Element Wave Kinematics Definition ...................................................................... 198
13.3.9. RAO Definition ................................................................................................................... 199
13.3.10. Mass Properties ................................................................................................................ 200
13.4. Example Analysis Using Results from a Hydrodynamic Diffraction Analysis ................................... 200
Index ........................................................................................................................................................ 205
of ANSYS, Inc. and its subsidiaries and affiliates. ix
x of ANSYS, Inc. and its subsidiaries and affiliates.
List of Figures
1.1. Y-Displacement Difference at End of Beam .............................................................................................. 4
2.1. Rezoning Using a Program-Generated New Mesh .................................................................................. 11
2.2. Rezoning Using a Generic New Mesh Generated by Another Application ............................................... 12
2.3. Rezoning Using Manual Splitting of an Existing Mesh ............................................................................ 13
2.4. Boundary Geometry of a Generic (CDB) New Mesh ................................................................................ 21
2.5. Remeshing Options when Using a Generic (CDB) New Mesh .................................................................. 21
2.6. Splitting Quadrilateral and Degenerate Linear Elements (PLANE182) ...................................................... 24
2.7. Splitting Quadrilateral, Degenerate and Triangular Quadratic Elements (PLANE183) ............................... 25
2.8. Splitting Tetrahedral Linear Elements (SOLID285)) ................................................................................. 26
2.9.Transition Element Generation Methods for 2-D ..................................................................................... 27
2.10. Phase 1 Transition Creation: Tetrahedra with One and Two Nodes Selected for Splitting ........................ 29
2.11. Phase 2(a) Transition Creation: Prism (Wedge) Element Is Split into Three Tetrahedra ............................ 30
2.12. Phase 2(b) Transition Creation: Pyramid Element Is Split into Two Tetrahedra ....................................... 30
2.13. Edge/Face Swapping for Tetrahedral Elements ..................................................................................... 31
2.14. Mesh Morphing Using Cotangent-Weighted Laplacian Equation .......................................................... 32
2.15. /PREP7 Mesh-Control Commands Available in Rezoning ...................................................................... 32
3.1. Rubber Seal with Coarse Mesh .............................................................................................................. 52
3.2. Deformed Rubber Seal with Coarse Mesh .............................................................................................. 52
3.3. Rubber Seal Model with Initial Mesh Refinement ................................................................................... 53
3.4. Rubber Seal Model with Second Mesh Refinement ................................................................................ 54
3.5. Deformed Rubber Seal with Mesh Refinements ..................................................................................... 55
3.6. Crack Simulation Model with Coarse Mesh ............................................................................................ 55
3.7. Crack Simulation Solution with Coarse Mesh ......................................................................................... 56
3.8. Crack Simulation Solution with Three Mesh Refinements ....................................................................... 57
3.9. Crack Simulation Solution with Fine Mesh and No Mesh Nonlinear Adaptivity ........................................ 58
3.10. Metal Block Ready to Be Forged Showing Initial Mesh .......................................................................... 59
3.11. View of Block on X-Y Plane After Diverging (No Nonlinear Adaptivity) ................................................... 60
3.12. Final Solution After Converging Using Nonlinear Adaptivity ................................................................. 61
3.13. Metal Block Ready to Be Extruded Showing Initial Mesh ....................................................................... 61
3.14. Deformed Shape of Metal Block After Diverging (No Nonlinear Adaptivity) ........................................... 62
3.15. Shape of Metal Block After Converging (Using Nonlinear Adaptivity) .................................................... 63
3.16. Mesh Nonlinear Adaptivity During Solution ......................................................................................... 65
3.17. Rigid Target-Contact Interface ............................................................................................................. 70
3.18. Gap Reduction with Successive Mesh Refinement by Element Splitting ................................................ 72
3.19. Contact-Status-Based Determination for Splitting ................................................................................ 72
3.20. Effect of Transitional Element Generation on Size and Numbering Criteria ............................................ 73
3.21. NLAD Regions and Remeshing Regions ............................................................................................... 74
3.22. Understanding 3-D Domains ............................................................................................................... 75
3.23. Understanding 2-D Domains ............................................................................................................... 75
3.24. Understanding 3-D Regions ................................................................................................................ 76
3.25. Understanding 2-D Regions ................................................................................................................ 76
3.26. 3-D Boundary Angle Between Two Adjacent Faces on an Exterior Surface ............................................. 77
3.27. 2-D Boundary Angle Between Two Adjacent Edges on an Exterior Surface ............................................ 78
3.28. 3-D Edge Angle in a Segment .............................................................................................................. 78
3.29. Partial Remesh: Sculpting Remesh Regions .......................................................................................... 79
3.30. Global Sizing ....................................................................................................................................... 80
3.31. 2-D Mesh-Size Gradient Control Options .............................................................................................. 82
3.32. 3-D Local Sizing Control ...................................................................................................................... 84
3.33. Example FEA Remesh Log File (2-D) ..................................................................................................... 85
3.34. Example FEA Remesh Log File (3-D) ..................................................................................................... 86
of ANSYS, Inc. and its subsidiaries and affiliates. xi
3.35. 2-D Self-Contact .................................................................................................................................. 87

3.36. Workaround for 3-D Self-Contact Penetration ..................................................................................... 88
4.1. 2-D to 3-D Process Flow ....................................................................................................................... 102
4.2. 2-D Plane Strain to 3-D Solid Extrusion ................................................................................................. 104
4.3. Axisymmetric to 3-D Solid Extrusion .................................................................................................... 104
7.1. Submodeling of a Pulley ..................................................................................................................... 151
7.2. Coarse Model ...................................................................................................................................... 153
7.3. Submodel Superimposed Over Coarse Model ...................................................................................... 154
7.4. Cut Boundaries on the Submodel ........................................................................................................ 155
7.5. Loads on the Submodel ...................................................................................................................... 157
7.6. Data Flow Diagram for Submodeling (Without Temperature Interpolation) .......................................... 158
7.7. Contour Plots to Compare Results ....................................................................................................... 159
7.8. Path Plots to Compare Results ............................................................................................................. 159
7.9. Coarse-Mesh Model, Submodel, and Fine-Mesh Model ......................................................................... 162
7.10. Equivalent Plastic Strain Through Various Cut-Boundary Conditions and Load Steps ........................... 163
7.11. Equivalent Plastic Strain Distributions in a Submodeling Analysis with Load-History Dependency ....... 164
7.12. 3-D Solid Submodel Superimposed on Coarse Shell Model ................................................................. 166
7.13. Node Rotations ................................................................................................................................. 167
10.1. Simulation Schematic ........................................................................................................................ 183
10.2. Evolution of Spring Force .................................................................................................................. 183
13.1. Hydrodynamic Diffraction Analysis Pressure Results ........................................................................... 201
13.2. Analysis Results Using Pressure Data from a Hydrodynamic Diffraction Analysis ................................. 203
xii of ANSYS, Inc. and its subsidiaries and affiliates.
List of Tables
3.1. Mesh Nonlinear Adaptivity Limitations .................................................................................................. 64
of ANSYS, Inc. and its subsidiaries and affiliates. xiii
xiv of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 1: Variational Technology
Variational Technology for Improved Solver Performance
The Variational Technology implementation speeds up the solution itself and has been applied to two
distinct types of mathematical problems: Nonlinear solutions for structural and thermal analyses, and
harmonic analysis. These capabilities are referred to as VT Accelerator. VT Accelerator provides a 2X to
5X performance improvement for the initial solutions depending on the hardware, model, and type of
analysis. VT Accelerator makes re-solves 3X to 10X faster for parameter changes, allowing for effective
simulation driven parametric studies of nonlinear and transient analyses in a cost-effective manner. You
can make the following types of changes to the model before a VT Accelerator re-solve:
• Modify, add, or remove loads (constraints may not be changed, although their value may be modified)
• Change materials and material properties
• Change section data and real constants
• Change geometry, although the mesh connectivity must remain the same (i.e., the mesh must be
morphed)
VT Accelerator for Nonlinear Solution Speedup VT Accelerator for nonlinear solutions speeds up
the solution of applicable nonlinear analysis types by reducing the total number of iterations. Examples
include:
• Nonlinear structural static or transient analyses not involving contact or plasticity
• Nonlinear thermal static or transient analyses
VT Accelerator for Harmonic Analysis The harmonic sweep feature of VT Accelerator provides a
high-performance solution for forced-frequency simulations in structural analyses.
For a structural harmonic analysis, VT Accelerator provides a harmonic analysis over a range of user-
defined frequencies. The structural material may have frequency dependent elasticity or damping.
The following Variational Technology topics are available:

1.1. Harmonic Sweep Using VT Accelerator
1.1. Harmonic Sweep Using VT Accelerator

The harmonic sweep feature of VT Accelerator provides a high-performance solution for a structural
analysis where the material properties are frequency-dependent and no modal responses can be used.
The harmonic sweep feature of VT Accelerator completes one normal ANSYS run at the mid-frequency
of the specified frequency range.
The harmonic sweep interpolates the stiffness, damping, mass, and loading on the whole range to give
an approximation of the results across the frequency range. The harmonic sweep evaluates these values
of ANSYS, Inc. and its subsidiaries and affiliates. 1
Variational Technology
for different frequencies (between 2 and 6) across the frequency range, and then it computes a polyno-
mial approximation of the values.
The harmonic sweep performs accurate approximations of the results across the frequency range in
user-specified steps.
If the loading, material properties, or real constants defined with a data table (BF ,TBFIELD command,
or COMBIN14) are frequency-dependent and too few data points exist in the table, the polynomial in-
terpolation of the values will be poor. In case of abrupt variations for a given frequency f2, ANSYS, Inc.
recommends splitting the frequency range [f1 f3] into two ranges (e.g., [f1 f2] ; [f2 f3] ) and performing
separate analyses on each range.
The following Variational Technology topics are available for harmonic sweep:
1.1.1. Structural Elements Supporting Frequency-Dependent Properties
1.1.2. Harmonic Sweep for Structural Analysis with Frequency-Dependent Material Properties
1.1.1. Structural Elements Supporting Frequency-Dependent Properties

Frequency-dependent property structural elements can be used with the following elements:
Frequency-Dependent Material Properties

Element (defined using TB,ELAS and TB,SDAMP,,,,STRU
commands)
PLANE182 EX, STRU
PLANE183 EX, STRU
SOLID185 EX, STRU
SOLID186 EX, STRU
SOLID187 EX, STRU
SOLID272 EX, STRU
SOLID273 EX, STRU
SOLID285 EX, STRU
1.1.2. Harmonic Sweep for Structural Analysis with Frequency-Dependent

Material Properties
The harmonic sweep feature of the VT Accelerator module allows you to define the material elastic
properties as frequency-dependent and efficiently compute the frequency response over an entire fre-
quency range. For more information, see the documentation for the TB,ELAS and TB,SDAMP,,,,STRU
commands. To use this formulation, use the hysteretic damping formulation with the HROPT command.
If you define the damping ratio (TB,SDAMP,,,,STRU) as a linear function of the frequency, the damping
exhibits behavior similar to that of viscous damping. See the Mechanical APDL Theory Reference for more
information about the hysteretic and structural damping formulations.
Limitations
• The frequency-dependent tables (defined by the TB,ELAS and TB,SDAMP commands) define piecewise linear
functions. These are used to define the stiffness and damping matrices, which in turn are fitted with a
polynomial over the entire frequency range to compute their derivatives as a function of frequency; therefore,
if the piecewise linear approximation of the material properties is too coarse, the results will be poor.
2 of ANSYS, Inc. and its subsidiaries and affiliates.
Harmonic Sweep Using VT Accelerator
1.1.2.1. Beam Example

Consider a cantilever beam, with a Young's modulus of 20e6 psi for static condictions and 30e6 for
500Hz.
ETYPE=186
LF = 10 ! STARTING FREQUENCY
UF = 500 ! ENDING FREQUENCY
N = 50 ! NUMBER OF SUBSTEP
/PREP7
!*
ET,1,ETYPE
/com, * ==============================================
/com, *
/com, * Frequency dependent material properties
/com, *
/com, * ==============================================
TB,ELASTIC,1,,2 ! Elastic data table
TBFIELD , FREQ,1 ! First frequency value
TBDATA,1,20e6,0.3 ! E and m
TBFIELD ,FREQ,500 ! Fifth frequency value
TBDATA,1,30e6,0.3
TB,SDAMP,1, ,1 ! damping data table
TBFIELD , FREQ,1 ! First frequency value
TBDATA,1, 0.02 ! Damping co.
TBFIELD ,FREQ,500 ! Fifth frequency value
TBDATA,1, 0.01
MP,DENS,1,.10
BLOCK,0,10,0,2,0,2
LSEL,S,LOC,X,-.5,0.5
LESIZE,ALL,,,2
LSEL,S,LOC,X,9.5,10.5
LESIZE,ALL,,,2
LSEL,S,LOC,X,2,8
LESIZE,ALL,,,5
VMESH,ALL
FINISH
/SOL
LSEL,S,LOC,X,-.5,0.5
DL,all,,all
KSEL,S,LOC,X,8,12
KSEL,R,LOC,Y,-.5,.5
FK,ALL,FY,1000
ASEL,S,LOC,Y,1.8,2.2
SFA,ALL,,PRES,1000,
allsel
FINI
/com, * ==============================================
/com, *
/com, * VT Harmonic Analysis
/com, *
/com, * ==============================================
/SOLU
ANTY,HARM
HROUT,OFF ! Print complex displacements as amplitude and phase angle
KBC,1
HROPT,VT,,,,HYST
harfrq,LF,UF
nsubst,N
Solve
FINISH
/post26
nsol,10,57,u,y,d1
prvar,10
The following figure shows the difference in the Y displacement at the end of the beam, taking constant
material properties for 0Hz, constant properties for 500 Hz, and variable properties:
Variational Technology
Figure 1.1: Y-Displacement Difference at End of Beam
Because of the frequency step used to create the frequency response, the first peak is higher on the
variable curve than the other two.
Chapter 2: Rezoning
In a finite large-deformation analysis, mesh distortion reduces simulation accuracy, causes convergence
difficulties, and can eventually terminate an analysis. Rezoning allows you to repair the distorted mesh
and continue the simulation.
The program's manual rezoning capability allows you to decide when to use rezoning, what region(s)
to rezone, and what remeshing method to use on the selected region(s).
During the rezoning process, the program updates the database as necessary, generates contact elements
if needed, transfers boundary conditions and loads from the original mesh, and maps all solved variables
(node and element solutions) to the new mesh automatically. Afterwards, with equilibrium achieved
based on the mapped variables, you can continue solving using the new mesh.
The following rezoning topics are available:

2.1. Benefits and Limitations of Rezoning
2.2. Rezoning Requirements
2.3. Understanding the Rezoning Process
2.4. Step 1: Determine the Substep to Initiate Rezoning
2.5. Step 2. Initiate Rezoning
2.6. Step 3: Select a Region to Remesh
2.7. Step 4: Perform the Remeshing Operation
2.8. Step 5: Verify Applied Contact Boundaries, Surface-Effect Elements, Loads, and Boundary Conditions
2.9. Step 6: Automatically Map Variables and Balance Residuals
2.10. Step 7: Perform a Multiframe Restart
2.11. Repeating the Rezoning Process if Necessary
2.12. Postprocessing Rezoning Results
2.13. Rezoning Restrictions
2.14. Rezoning Examples
For related information, see Mesh Nonlinear Adaptivity.
2.1. Benefits and Limitations of Rezoning

Even when an analysis terminates due to severe mesh distortion, rezoning allows you to continue the
analysis and complete the simulation. You can also use rezoning to improve analysis accuracy and
convergence when the mesh is distorted but does not terminate the analysis.
To illustrate how rezoning works in a case where the analysis terminates, assume that the following
initial mesh and boundary conditions exist:
Rezoning
The simulation terminates at TIME = 0.44. Rezoning begins on the deformed mesh at substep 7 (TIME
= 0.40):
After remeshing the selected region, an acceptable new mesh is ready:
Benefits and Limitations of Rezoning
Based on the new mesh, the simulation concludes successfully at TIME = 1.0:
For a more detailed example, see Rezoning Examples (p. 41).
2.1.1. Rezoning Limitations

The purpose of rezoning is to repair a distorted mesh in order to overcome convergence problems
caused by the distortion.
Rezoning is effective only when the mesh distortion is caused by a large, nonuniform deformation.
Rezoning cannot help if divergence occurs for any other reason such as unstable material, unstable
structures, or numerical instabilities.
Unstable Material
Most nonlinear material models, especially those employing hyperelastic materials, have
their own applicable ranges. When a deformation is too large or a stress state exceeds
the applicable range, the material may become unstable. The instability can manifest
itself as a mesh distortion, but rezoning cannot help in such cases. While it is sometimes
Rezoning
difficult to determine when material is unstable, you can check the strain values, stress
states, and convergence patterns. A sudden convergence difficulty could mean that
material is no longer stable. The program also issues a warning at the beginning of the
solution indicating when hyperelastic material could be unstable, although such a
warning is very preliminary and applies only to cases involving simple stress states.
Unstable Structures
For some geometries and loads, a deformation may cause a "snap-through," or local
buckling. Such behavior can also manifest itself as a mesh distortion, but one that
rezoning cannot repair. The effect is usually easy to detect by closely checking the de-
formed region or the load-versus- time (displacement) curve.
Numerical Instabilities
A condition of numerical instability can occur when a problem is nearly overconstrained.

The constraints can include kinematic constraints such as applied displacements, CP,
and CE, and volumetric constraints introduced by fully incompressible material in mixed
u-P elements. In many cases, numerical instability is apparent even in the early stages
of an analysis.
For a successful rezoning, the new mesh must be of a higher quality than the old mesh. If the new
mesh is not better than the original mesh, rezoning cannot improve convergence, and can even worsen
convergence problems.
2.2. Rezoning Requirements

Rezoning is available for 2-D and 3-D analyses. All multiframe restart files must be available.
Following are the supported analysis types, elements, materials, loads, boundary conditions, and other
rezoning requirements:
Support Category Support Details

Solid elements • PLANE182 -- B-bar method only (KEYOPT(1) = 0).
• PLANE183
• For both PLANE182 and PLANE183, all stress states (KEYOPT(3)) are
allowed: plane strain, plane stress, axisymmetric, and generalized plane
strain. Pure displacement formulation (KEYOPT(6) = 0) or mixed u-P
formulation (KEYOPT(6) = 1) is allowed.
• SOLID185 -- B-bar method only (KEYOPT(1) = 0). Pure displacement

formulation (KEYOPT(6) = 0) or mixed u-P formulation (KEYOPT(6) = 1) is
allowed in a nonlayered configuration (KEYOPT(3) = 0). Works with
REMESH,READ only.
• SOLID186 -- Works with REMESH,READ only.
• SOLID187 -- Works with REMESH,READ only.
• SOLID285
Rezoning Requirements

Contact • Pair-based contact only. (General contact not supported.)
elements
• TARGE169
• CONTA171 and CONTA172 with any of the following valid KEYOPT settings:
KEYOPT (1) = 0
KEYOPT (2) = 0, 1, 3, 4
KEYOPT (3) = 0
KEYOPT (4) = 0, 1, 2, 3
KEYOPT (4) = 0, 1, 2
KEYOPT (5) = 0, 1, 2, 3, 4
KEYOPT (7) = 0, 1, 2, 3
KEYOPT (8) = 0
KEYOPT (9) = 0, 1, 2, 3, 4
KEYOPT (10) = 0, 2
KEYOPT (11) = 0
KEYOPT (12) = 0, 1, 2, 3, 4, 5, 6
KEYOPT(14) = 0
• TARGE170
KEYOPT (1) = 0
KEYOPT (2) = 0, 1
KEYOPT (4) = 0, 2, 3
KEYOPT (5) = 0, 1, 2, 3, 4
KEYOPT (7) = 0, 1, 2, 3
KEYOPT (8) = 0
KEYOPT (9) = 0, 1, 2, 3, 4
KEYOPT (10) = 0, 2
KEYOPT (11) = 0
KEYOPT (12) = 0, 1, 2, 3, 4, 5, 6
KEYOPT(14) = 0
• Supported for pair-based contact only.
Contact pair • Rigid-flexible -- Target elements and pilot node cannot be remeshed.
behavior
• Flexible-flexible contact.
• Self-contact.
Surface-effect • SURF153 and SURF154

elements
Only normal and tangential pressures applied on SURF153 and
SURF154 are supported. (That is, rezoning support is available only
for pressure on faces 1 and 2 for SURF153 and pressure on faces 1,
2 and 3 for SURF154.)
Materials • Most structural materials are supported. The exceptions are:
Rezoning

- CAST (cast iron)
- CDM (Mullins Effect)
- CONCR (concrete)
- CZM (cohesive zone)
- DMGE and DMGI (damage),
- MPLANE (microplane)
- SMA (shape memory alloy)
- SWELL (swelling)
• For materials associated with user-defined state variables (TB,STATE), it

may be necessary to issue the MAPVAR command.
Analysis types • Static analysis with geometric nonlinearity (NLGEOM,ON).
Loads and • Displacements, forces, pressures, and nodal temperatures (applied via a
boundary BF,TEMP command).
conditions
(BCs) • Tabular displacements, forces, and pressures that are functions of time
only are supported.
• Fluid-penetration loads applied to contact elements (CONTA171,

CONTA172, CONTA173, CONTA174) via SF or SFE commands are
supported.
• Do not remove nodal constraints (DDELE) during solution before rezoning

or remeshing.
Region to be • The selected nodes inside the region must have the same nodal coordinate
remeshed system.
• Boundary nodes can have different nodal coordinate systems.
• Elements must be of the same element type, material, element coordinate

system, and real constant.
• If two regions with different attributes require remeshing, you must remesh
the regions separately. For more information, see Hints for Remeshing
Multiple Regions (p. 19).
• All node and element components defined in remesh regions are lost
during remeshing, except those associated with nonlinear adaptive criteria.
• Nonlinear stabilization is not supported.
Files • .rst, .rdb, .rdnn, .rxxx (where xxx is the substep (p. 15) in which
rezoning is initiated), .ldhi, and .cdb
The conditions specified apply only to the region to be remeshed. No limitations exist for other regions,
although the analysis type itself must support rezoning.
Understanding the Rezoning Process
2.3. Understanding the Rezoning Process

The rezoning process involves the following general steps:
1. Determine the load step and substep (p. 15) at which the region must be remeshed.
2. Initiate (p. 16) the rezoning process.
3. Select the region to remesh (p. 16).
4. Remesh (p. 17) the region with a mesh of better quality than the distorted mesh in the original domain.
5. Verify (p. 34) boundary conditions, loads, temperatures, and fluid-penetration parameters applied to
the new mesh (from the old, distorted mesh).
6. Automatically map (p. 36) displacements and state variables from the old (distorted) mesh to the new
mesh and rebalance (p. 36) the resulting residual forces.
7. Use the restart capability (p. 38) to continue the analysis.
You can select one or more parts, or regions, of the mesh to repair at the same time (p. 33). You can
also perform rezoning multiple times (p. 38) in an analysis.
The following topics related to understanding the general rezoning process are also available:
2.3.1. Overview of the Rezoning Process Flow
2.3.2. Key Commands Used in Rezoning
2.3.1. Overview of the Rezoning Process Flow

The following flowcharts illustrate the general rezoning process according to the remeshing method
used (p. 17):
• Figure 2.1: Rezoning Using a Program-Generated New Mesh
• Figure 2.2: Rezoning Using a Generic New Mesh Generated by Another Application
• Figure 2.3: Rezoning Using Manual Splitting of an Existing Mesh
Some mesh-generation methods are limited to 2-D analyses only.
For information about the commands shown in the flowcharts, see Key Commands Used in Rezoning
(p. 14)or the documentation for a given command in the Command Reference.
Figure 2.1: Rezoning Using a Program-Generated New Mesh
This flowchart shows a process for 2-D rezoning using a new mesh generated internally
by the program (p. 18) (AREMESH and AMESH):
Rezoning
Figure 2.2: Rezoning Using a Generic New Mesh Generated by Another Application
This flowchart shows a process for both 2-D and 3-D rezoning using a generic (.cdb
format) new mesh generated by a third-party application (p. 19):
Understanding the Rezoning Process
Figure 2.3: Rezoning Using Manual Splitting of an Existing Mesh
This flowchart shows a process for 2-D rezoning by splitting an existing mesh (p. 23):
Rezoning
For 3-D mesh splitting (p. 28), command-driven transition element control (ESEL) is not used. The
program generates the transitions automatically.
2.3.2. Key Commands Used in Rezoning

Following is a description of key commands used in the rezoning process and provides supplemental
information to the rezoning process flowcharts (p. 11).
Command Description Rezoning Comments

/CLEAR Clears the Always clear the database first, before reentering the
database solution processor (/SOLU) and starting the rezoning
process.
REZONE Initiates When you initiate rezoning, the program verifies that the
rezoning necessary files (.rdb, .rst, .rxxx, and .ldhi) exist for
the specified substep and rebuilds the data environment
at that substep.
All nodes are updated to the deformed geometry in

preparation for remeshing (p. 17).
Step 1: Determine the Substep to Initiate Rezoning
Command Description Rezoning Comments

REMESH Generates or You can remesh more than one region (p. 33) at the same
obtains the new specified substep during the rezoning process.
mesh required
for rezoning After remeshing (REMESH,FINISH), the program
generates contact elements (if any) and transfers loads
and boundary conditions automatically.
For more information, see Step 4: Perform the

Remeshing Operation (p. 17).
MAPSOLVE Maps node and After remeshing, this command maps the solved nodal and
element element solutions from the original (distorted) mesh to the
solutions new mesh and achieves equilibrium on the new mesh.
2.4. Step 1: Determine the Substep to Initiate Rezoning
Determining Why the Solution Terminated
To investigate the reason(s) why a solution terminated, enter the POST1 general postprocessor
(/POST1) to review analysis results.
You can also use the GUI to select a substep for which restart files are available but results are
not saved in a results file, generate the results for the selected substep, then review the results
in POST1.
If the solution terminated because of a mesh distortion, it is a candidate for rezoning.
It is important to select a suitable substep at which to start rezoning. You must select a converged
substep where the restart files are available.
The last converged substep is often a natural choice for initiating rezoning because there is typically
less of a remaining load to apply. However, the last converged substep may have more severely distorted
elements which can cause larger errors when mapping solution variables (MAPSOLVE), in turn requiring
more mapping substeps to balance residual forces (p. 36) or convergence failures. Rezoning from a
substep with an extremely distorted mesh may also reduce the accuracy of the final solution, and can
even cause the automatic transfer of boundary conditions after remeshing (REMESH,FINISH) to fail.
Typically, the best choice is the first, second, or third converged substep preceding the last converged
substep. To determine the best possible substep to initiate rezoning, you may need to enter the POST1
general postprocessor (/POST1) to examine the deformed element shapes, and stress and strain distri-
butions.
If no results data exists for a substep in the results file, you can use program restart features to generate
results data for the substep, and then enter POST1 to examine the deformed shape; afterwards, you
can reenter the solution processor and initiate rezoning as usual.
Hints for selecting the best substep to initiate rezoning:
• The substep should have an obvious mesh distortion but should contain no element
having an internal angle too closely approaching, equal to, or exceeding 180 degrees.
Rezoning
• The substep should have minimal penetration in contact. Try to avoid substeps where
contact status has changed suddenly from previous substeps.
• If an error occurs when the program transfers boundary conditions and loads after
remeshing (REMESH,FINISH) and the old mesh is severely distorted, try the substep
preceding the one most recently chosen.
• The best substep is often not the last converged substep, but rather one of the several
preceding the last one.
• If the last few converged substeps are separated by very small time increments and
you have already tried one or more of those substeps unsuccessfully, select a
converged substep that is separated from the others by a larger time increment.
• If you are still having difficulty obtaining a mesh of reasonable quality because the
old mesh is too distorted, try the substep preceding the one most recently chosen.
• If the mapping operation (MAPSOLVE) fails to converge even if you allow up to 500
substeps, try the substep preceding the one most recently chosen.
When you have determined the substep at which to initiate rezoning, proceed to Step 2. Initiate
Rezoning (p. 16).
2.5. Step 2. Initiate Rezoning

Rezoning is based on an existing solution, so the initial solution must have terminated.
Because the simulation terminated, the rezoning process must begin with a clean database.
To start rezoning:
1. Clear the database (/CLEAR).
2. Reenter the solution processor (/SOLU).
3. Initiate rezoning, specifying the load step and substep (p. 15) at which rezoning should occur
(REZONE,MANUAL,LDSTEP,SBSTEP).
Proceed to Step 3: Select a Region to Remesh (p. 16).
2.6. Step 3: Select a Region to Remesh

A region that you select (ESEL) for remeshing (p. 17) can contain the entire deformed domain or a
portion of it. A selected region should consist of the same:
• Material type
• Element type (including the coordinate system and KEYOPT settings)
• Thickness (real constant) for plane stress
• Nodal coordinate system (except for boundary nodes which can have different nodal coordinate systems).
Step 4: Perform the Remeshing Operation
A selected region should contain all of the highly distorted elements. It is a good practice to select a
group of elements slightly larger than the target group of distorted elements so that the new mesh
can be assured of a fairly good distribution of nodes on the interface boundary.
If the boundary nodes are distributed too unevenly, the elements attached to the nodes should also
be included. The selected region's boundary can have any shape.
A selected region that is too large may require more processing time and more subsequent remeshings.
If the selected region is too small to contain all of the highly distorted mesh areas, the new model after
rezoning may not be of sufficient quality to achieve convergence.
Using the GUI to Select a Region to Remesh
Select a region to remesh using either of the following methods available via the ANSYS Main Menu:
• In the SOLU solution processor: Solution>Manual Rezoning>Select Rezone Elements
• In the POST1 postprocessor: General Postproc>Manual Rezoning>Create Rezone Component
Select elements and group them into a component. During rezoning, import the component after
remeshing starts (REMESH,START).
This component can be imported into the program or exported to a third-party tool to create a new
mesh for the selected region.
If more than one region requires rezoning, see Remeshing Multiple Regions at the Same Substep (p. 33).
After you have selected the region(s) to remesh, proceed to Step 4: Perform the Remeshing Opera-
tion (p. 17).
2.7. Step 4: Perform the Remeshing Operation

Issue the REMESH,START command to begin the remeshing operation.
When remeshing begins, your analysis temporarily exits the solution processor and enters a special
mode of the PREP7 preprocessor, where a limited number of preprocessing commands are avail-
able (p. 32) for mesh control.
The following topics concerning the remeshing operation are available:

2.7.1. Choosing a Remeshing Method
2.7.2. Mesh Control
2.7.3. Remeshing Multiple Regions at the Same Substep
To exit the special preprocessing mode and reenter the solution processor, issue a REMESH,FINISH
command.
After remeshing, proceed to Step 5: Verify Applied Contact Boundaries, Surface-Effect Elements, Loads,
and Boundary Conditions (p. 34).
2.7.1. Choosing a Remeshing Method

To generate a new mesh for a selected region, you can use the program's native capabilities, import a
generic new mesh from a third-party application, or manually split an existing mesh:
2.7.1.1. Remeshing Using a Program-Generated New Mesh (2-D)
Rezoning
2.7.1.2. Remeshing Using a Generic New Mesh (2-D and 3-D)

2.7.1.3. Remeshing Using Manual Mesh Splitting (2-D and 3-D)
2.7.1.1. Remeshing Using a Program-Generated New Mesh (2-D)

This remeshing method requires the AREMESH and AMESH commands, as shown in Figure 2.1: Rezoning
Using a Program-Generated New Mesh (p. 11). Remeshing using a program-generated mesh is available
for 2-D analyses only.
The following topics are available if you intend to remesh with a program-generated mesh:
2.7.1.1.1. Creating an Area to Remesh
2.7.1.1.2. Using Nodes From the Old Mesh
2.7.1.1.3. Hints for Remeshing Multiple Regions
2.7.1.1.4. Generating a New Mesh
To study a sample problem, see Example: Rezoning Using a Program-Generated New Mesh (p. 42).
2.7.1.1.1. Creating an Area to Remesh

Based on the selected region, the AREMESH command creates an area to generate the new mesh. The
program validates the selected region and creates an area on that region for the new mesh. The program
maintains compatibility with neighboring regions, and nodes with applied loads and boundary conditions
remain intact.
How the program creates the boundary lines affects the new mesh quality and mesh density on the
area; therefore, specify AREMESH command options carefully. The boundary lines are based on the
element edges on the boundary of the selected region, as follows:
• Line combining (AREMESH,0) allows you to redistribute the new nodes on the boundary and provides more
control over the new element size. New elements can be larger or smaller. If the boundary is highly curved,
however, the new element edges may constitute a slightly different boundary.
• If line segments are not combined (AREMESH,-1), the new boundary will match the old one. In this case,
you cannot control the positions of old nodes on the boundary (which may result in an unacceptable new
mesh), and elements on the boundary can only be the same size or smaller.
To maintain compatibility, the program does not combine line segments connected to elements outside
the selected remeshing region (even if you specify line combining). Also, two segments are not combined
if an old node is located between them and that node:
• Has applied force or displacements, or
• Is the starting and ending point of applied pressures, distributed displacements, or contact boundaries.
2.7.1.1.2. Using Nodes From the Old Mesh

It is best to avoid using nodes from the old mesh whenever possible. Retaining old nodes introduces
more constraints when generating the new mesh and makes it more difficult to create a new mesh of
better quality.
If necessary, you can retain some old nodes on the boundaries of the selected region to use on the
new mesh. To do so, select the nodes that you want to keep and group them into a nodal component
named _ndnocmb_rzn (CM,_ndnocmb_rzn,NODE) before issuing the AREMESH command.
2.7.1.1.3. Hints for Remeshing Multiple Regions

When remeshing using a program-generated new mesh, you can remesh multiple regions at a given
substep (referred to as horizontal rezoning) as follows:
1. After starting the remeshing operation (REMESH,START), select a region to remesh.
2. Generate the area for the new mesh (AREMESH).
3. Create the new mesh (AMESH).
4. Select another region (being careful not to overlap regions), generate the area for its new mesh, and create
the new mesh on that region.
Repeat the process for as many regions as you wish, but only after issuing the REMESH,START command
and before issuing a REMESH,FINISH command (as shown in Understanding the Rezoning Process (p. 11)).
When remeshing two regions or areas that connect to each other, it is best to select them as a single
region. If two connected regions must be treated separately, create the mesh for the first region before
remeshing the second one.
2.7.1.1.4. Generating a New Mesh

After generating the area (AREMESH) for the selected region, issue the AMESH command to generate
the new mesh.
Several preprocessing (/PREP7) commands are available to help you create a good mesh on the selected
region. For more information, see Mesh Control (p. 32).
The mesh-control commands are available at any point after issuing a REMESH,START command and
before issuing a REMESH,FINISH command.
2.7.1.2. Remeshing Using a Generic New Mesh (2-D and 3-D)

You can remesh using a generic new mesh created by another application. This remeshing method is
available for both 2-D and 3-D analyses.
As shown in Figure 2.2: Rezoning Using a Generic New Mesh Generated by Another Application (p. 12),
using a generic mesh for the remeshing operation requires the REMESH,READ command, used in place
of the commands required for other meshing methods.
To use a new third-party mesh, the mesh file must have a .cdb file format. The .cdb file must have
mesh information, but an IGES file (geometry information) is not required. Typically, the new .cdb
mesh is generated from a faceted geometry representation of the boundary of the region to be rezoned.
The element types supported for remeshing with a generic new mesh are given in Rezoning Require-
ments (p. 8).
The following additional topics related to using a generic new mesh are available:
2.7.1.2.1. Using the REMESH Command with a Generic New Mesh
2.7.1.2.2. Requirements for the Generic New Mesh
2.7.1.2.3. Using the REGE and KEEP Remeshing Options
To study a sample problem, see Example: Rezoning Using a Generic New Mesh (p. 45).
Rezoning
2.7.1.2.1. Using the REMESH Command with a Generic New Mesh

The commands used for reading in a generic new mesh are shown in Figure 2.2: Rezoning Using a
Generic New Mesh Generated by Another Application (p. 12).
Because the REMESH command's READ option reads only generic meshes, all properties of the solid
elements in the new mesh are inherited internally from the corresponding underlying solid elements
in the old mesh. The program ignores the solid element properties of the new mesh in the .cdb file
and calculates them internally depending upon their location in the model; therefore, only the NBLOCK
and EBLOCK records of the .cdb file (which define the nodal coordinates and element connectivity,
respectively) are read in after issuing a REMESH,READ command.
You can issue multiple REMESH,READ commands for various parts of the mesh in the same rezoning
problem (referred to as horizontal rezoning). These multiple regions can be isolated or can touch each
other at the boundary, but they cannot overlap. The new mesh, representing multiple regions, can also
reside in a single .cdb file.
2.7.1.2.2. Requirements for the Generic New Mesh

The following general requirements must be met by the generic mesh if it is to be a candidate for a
new mesh for rezoning:
• The space that the new mesh space occupies, as well as its topology, must conform to that of the old mesh.
• Locations of concentrated forces in the old mesh (usually a node) must be present in the new mesh.
• Limit locations for pressure loads and boundary conditions in the old mesh must be present in the new
mesh.
• Limit locations for contact and contact/target element descriptions (in rigid-flex contact and flex-flex contact,
respectively) in the old mesh must be present in the new mesh.
The locations of the limits are marked by single nodes in 2-D analyses and by a line of connected nodes
in 3-D analyses.
It is not necessary to specify loads, boundary conditions, material properties, etc. on the generic mesh's
.cdb file. The program assigns those values to the new mesh from the model automatically and ignores
any specified values. If necessary, you can add new loads later via additional load steps or a restart.
ANSYS, Inc. recommends exporting the deformed old mesh with all discretized boundary information
to a suitable third-party application and, when generating the new mesh, verifying that the node positions
of concentrated loads, contact/target region limits, boundary condition and distributed load limits are
retained. If these key nodes are not retained, you will be unable to proceed with the analysis.
The new mesh is acceptable even if the smoothed boundary geometry of the new mesh does not cor-
respond exactly to the faceted geometry of the old mesh, as shown in Figure 2.4: Boundary Geometry
of a Generic (CDB) New Mesh (p. 21); however, the offset must be very small.
In a 3-D analysis involving contact, the difference of the recovered boundary geometry from the faceted
boundary of the old mesh affects mapping results much more so than in a 2-D analysis. Accurate geo-
metry extraction is therefore essential in 3-D rezoning.
Figure 2.4: Boundary Geometry of a Generic (CDB) New Mesh
If the rezoned part has contact/target elements, the program generates those elements automatically
for the new mesh, depending on whether the underlying old mesh had the same type of contact/target
elements. Isolated rigid target elements in the model remain the same throughout the analysis and
cannot be remeshed; however, all contact and target elements associated with solid elements are can-
didates for remeshing. While it is possible to read in the new contact/target elements of the new mesh
from the .cdb file, it is faster and more reliable to read in only the remeshed solid elements and allow
the program to generate the new contact/target elements.
The .cdb file of the new mesh must have no line breaks in the NBLOCK and EBLOCK records. Also,
while writing the mesh .cdb file, a block file format is necessary (CDWRITE,,,,,,,Fmat, where Fmat =
BLOCKED).
2.7.1.2.3. Using the REGE and KEEP Remeshing Options

The REMESH command's REGE option regenerates all node and element numbers on the new mesh
using an offset of the highest existing node and element numbers. The KEEP option keeps the similarly
numbered nodes and elements in the new and the old meshes unchanged.
Apply Option = KEEP carefully. It assumes that either the new mesh node and element numbers are
already offset by the maximum node and element number of the old mesh or that the common node
and element numbers in the new mesh and the old mesh match geometrically.
The following figure illustrates how the REMESH command's REGE and KEEP options work:
Figure 2.5: Remeshing Options when Using a Generic (CDB) New Mesh
In this example, a meshed domain with 24 nodes and 15 elements is remeshed using
the REMESH command's REGE (default) option. The .cdb file for the new mesh has
nodes 1 through 16 and element numbers 1 through 9. After remeshing, these node
and element numbers are suitably offset by the maximum node and element numbers
(that is, 15 and 24, respectively) of the old mesh.
Rezoning
The same problem appears in this example. However, the .cdb file for the new mesh
has node numbers defined from 28 through 43 and element numbers defined from 17
through 25. In this case, remeshing occurs using the REMESH command's KEEP option,
so the node and element numbers are not offset.
For more information, see the REMESH command documentation as it applies to remeshing using a
generic mesh created by another application.
2.7.1.3. Remeshing Using Manual Mesh Splitting (2-D and 3-D)

You can manually split an existing mesh to obtain the solution of a nonlinear analysis which cannot
otherwise converge, or to improve its accuracy.
Mesh splitting increases the number of degrees of freedom of the model by enriching the existing
mesh. It is a useful option for rezoning if the number of degrees of freedom must be increased in contact
gaps, or if a new program-generated mesh (p. 18) or generic third-party mesh (p. 19) does not fully
satisfy your requirements.
As shown in Figure 2.3: Rezoning Using Manual Splitting of an Existing Mesh (p. 13), the mesh-splitting
remeshing method requires the REMESH,SPLIT command, used in place of commands required for
other meshing methods.
Elements that have had midside nodes added or dropped (EMID) cannot be split.
The following topics related to manual mesh-splitting are available:

2.7.1.3.1. Understanding Mesh Splitting
2.7.1.3.2. Geometry Details for Mesh Splitting
2.7.1.3.3. Using the REMESH Command for Mesh Splitting
2.7.1.3.4. Mesh-Transition Options for 2-D Mesh Splitting
2.7.1.3.6. Improving the Local Topology of Tetrahedral Meshes via Edge and Face Swapping
2.7.1.3.7. Improving Tetrahedral Element Quality via Mesh Morphing
2.7.1.3.1. Understanding Mesh Splitting

Splitting occurs on selected solid elements in the mesh. If no solid elements are explicitly selected, the
program splits all solid elements in the mesh. The mesh-splitting capability generally applies to
remeshing cases in mesh-rezoning problems using the elements listed in Rezoning Requirements (p. 8).
The program splits parent elements into child elements, as follows:
• A parent quadrilateral element into four child quadrilateral elements
• A parent 2-D degenerate element into three child quadrilateral elements
• A parent triangular element into four child triangular elements
• A parent tetrahedral element into eight child tetrahedral elements
For more information, see Geometry Details for Mesh Splitting (p. 23).
Child elements inherit all shape characteristics of the parent element. Therefore, if a particular element
is badly distorted and is causing convergence difficulties, simply subdividing the element by splitting
it does not improve convergence.
2.7.1.3.2. Geometry Details for Mesh Splitting

The REMESH command's SPLIT option uses no geometry information; instead, it uses only information
about the mesh itself (that is, nodal connectivity and nodal coordinates).
All child elements automatically inherit all attributes of the parent element from which they were gen-
erated. Quadrilateral parent elements are split into four child elements, 2-D degenerate parent elements
Rezoning
are split into three quadrilateral child elements, and triangular parent elements are split into four trian-
gular child elements, as shown in the following figures:
Figure 2.6: Splitting Quadrilateral and Degenerate Linear Elements (PLANE182)
Figure 2.7: Splitting Quadrilateral, Degenerate and Triangular Quadratic Elements (PLANE183)
Rezoning
Figure 2.8: Splitting Tetrahedral Linear Elements (SOLID285))
2.7.1.3.3. Using the REMESH Command for Mesh Splitting

To perform mesh-splitting, select the region to be rezoned (via the GUI or the ESEL command). After
you have selected the target region, issue a REMESH,SPLIT command.
You can issue multiple REMESH,SPLIT commands for various parts of the mesh in the same rezoning
problem (referred to as horizontal rezoning). These multiple zones can overlap or they can be isolated;
however, a large number of overlaps can cause badly shaped transition elements to develop.
If the rezoned part has contact/target elements, the program generates those elements automatically
for the new mesh (according to whether the underlying old mesh had the same type of contact/target
elements). Isolated rigid target elements in the model remain the same throughout the analysis and
cannot be remeshed; however, all contact and target elements associated with solid elements are can-
didates for remeshing. When you split a solid element that is associated to contact/target elements,
the program deletes these associated contact/target elements. The program generates the correct
contact/target elements for the new child elements automatically at the end of the remeshing operation
(REMESH,FINISH).
Because splitting refinement is mesh-based and not geometry-based, it cannot be undone after it has
occurred. To create a different or new splitting scheme, or to revert to the original mesh, you must
create a new rezoning environment (REZONE,MANUAL,LDSTEP,SBSTEP).
For more information about using the REMESH,SPLIT command, see Mesh-Transition Options for 2-D
Mesh Splitting (p. 26) and Mesh-Transition Options for 3-D Mesh Splitting (p. 28).

The default REMESH,SPLIT command forces the transition elements to be mostly quadrilateral and
minimizes the number of degenerated elements. The command can also be issued as:
REMESH,SPLIT,,,TRAN,QUAD
Issuing the REMESH command using the transition and quadrilateral options helps with convergence
because non-degenerate elements are less prone to locking behavior.
Generating a More Localized Mesh
If you desire a more localized mesh after splitting, issue the following command:
REMESH,SPLIT,,,TRAN,DEGE
In this case, the program creates the degenerate elements in the transition zone, and the split
and the unsplit regions are connected within a single element layer.
It is possible that transition elements designed in such a way can disturb the localization of the mesh.
The element subdivision that occurs when transitioning from the split zone can traverse several element
layers.
The following figure illustrates the options for transition element generation:
Figure 2.9: Transition Element Generation Methods for 2-D
Elements selected for splitting (ESEL) are marked as shown.
Rezoning
Default splitting algorithm with all-quadrilateral transition elements and

no degenerate elements.
Regions of non-localization are shown. Either the REMESH,SPLIT command

or the REMESH,SPLIT,,,TRAN,QUAD command can apply here.
Splitting with single-layer transition and degenerate elements.
In this case, the REMESH,SPLIT,,,TRAN,DEGE command applies.

Unlike in 2-D splitting, command-driven transition element control is not supported in 3-D splitting.
The program generates the transitions automatically.
For tetrahedral meshes, transitions are generated for horizontal rezoning and partial remeshing.
For any tetrahedral element, if all four or any three nodes are selected by the program as candidates
for splitting, the entire element is split into eight child tetrahedra (as shown in Figure 2.8: Splitting
Tetrahedral Linear Elements (SOLID285)) (p. 26)). However, different transition element schemes are
developed for cases when only one or two nodes in a tetrahedron are selected for splitting.
The transition process is a two-phase operation: the first phase usually creates one or more tetrahedral
elements and pyramids and /or prisms (depending on the splitting template), and the second phase
further decomposes the pyramids and/or prisms into child tetrahedra.
The following figure shows the first phase of the transitions for parent tetrahedra when one and two
nodes are selected for splitting:
Figure 2.10: Phase 1 Transition Creation: Tetrahedra with One and Two Nodes Selected for Splitting
In the first case, the selected node is 1. From the parent tetrahedron (1-2-3-4), one child tetrahedron
(1-5-6-7) and one child prism (5-6-7-2-3-4) are created. In the second case, nodes 1 and 4 are selected
for splitting, creating two child tetrahedra (1-5-6-7 and 4-8-9-4), one child pyramid (5-8-9-6-7), and one
child prism (2-5-8-3-9-6).
In the second phase of transition creation, the prisms and pyramids are further split into tetrahedra, as
shown in the following two figures:
Rezoning
Figure 2.11: Phase 2(a) Transition Creation: Prism (Wedge) Element Is Split into Three Tetrahedra
The prism (1-2-6-4-3-5) is split into three tetrahedra (1-2-6-4, 2-4-3-6, and 3-4-5-6). No new nodes are
created. The diagonals are created to maintain compatibility with the neighboring elements and are
selected on the basis of best element shape metrics of the child elements.
Figure 2.12: Phase 2(b) Transition Creation: Pyramid Element Is Split into Two Tetrahedra
The pyramid (1-2-3-4-5) is split into tetrahedra (1-2-3-5 and 1-3-4-5). No new nodes are created. The
diagonal is created to maintain compatibility with the neighboring elements and are selected on the
basis of best element shape metrics of the child elements.
2.7.1.3.6. Improving the Local Topology of Tetrahedral Meshes via Edge and Face Swapping
Splitting a mesh ensures that child elements inherit all properties from parent elements. For 3-D splitting,
a deformed parent tetrahedral element produces eight distorted child tetrahedra. If high deformation
exists at the solution substep at which splitting occurs, the mapping operation (MAPSOLVE) may not
converge. It is also possible that the solution may not proceed much further after the analysis restart,
as the child elements themselves are distorted.
To improve tetrahedral element quality, the program modifies the local topography of the elements
automatically when the REMESH,SPLIT command executes. The modifications use edge- and face-swap
operators to change the connectivity of a group of contiguous tetrahedral elements to improve the
shape metrics of the elements.
The swap operations are usually referred to as i-j swapping, where i is the number of tetrahedrons before
swapping and j is the number of tetrahedrons after swapping. Support is available for 2-2, 2-3, 3-2, and
4-4 swaps.
The following figure shows an example of 2-3 and 2-2 swapping:
Figure 2.13: Edge/Face Swapping for Tetrahedral Elements
2.7.1.3.7. Improving Tetrahedral Element Quality via Mesh Morphing

In addition to swapping, the program also performs mesh morphing to improve tetrahedral element
quality after splitting occurs. As with swapping, morphing occurs automatically on the split elements
when the REMESH,SPLIT command executes.
The mesh-morphing operation maintains the mesh connectivity but moves the nodes to improve element
shape metrics. The operation uses the following cotangent-weighted Laplacian operator to perform an
iterative node-wise morphing:
where:
L(v) = Node movement vector

N = Number of elements adjacent to patch node i
V = Position vector of node
W = Weight function (given by )
The weight function is based on the cotangent of the face angles of the tetrahedral elements sharing
the node i, shown in the following figure:
Rezoning
Figure 2.14: Mesh Morphing Using Cotangent-Weighted Laplacian Equation
The mesh-morphing process stops when the node movement no longer improves shape metrics or the
magnitude of the node movement becomes negligibly small.
2.7.2. Mesh Control

Creating a better mesh is the key to successful rezoning. The new mesh must be better than the old
mesh; otherwise, rezoning cannot improve convergence, and can even result in nonconvergence if the
new mesh is worse.
Generally, a good mesh has these characteristics:
• The element internal angles do not approach 180 degrees or 0 degrees.
• The opposite edges or faces of quadrilaterals have less cross angle (that is, they are closer to parallel with
each other).
• Boundary nodes are more evenly distributed.
• The elements have a better aspect ratio.
For creating a good mesh, satisfactory internal angles are a more important consideration than whether
aspect ratios may be too high or too low. For 2-D meshes, avoid triangle elements as much as possible;
however, if quadrilateral elements have very large internal angles, it is preferable to accept some triangle
elements with more acceptable internal angles instead.
The quality of the new mesh is fully dependent on the shape of the selected region, neighboring ele-
ments, and boundary nodes with applied loads and boundary conditions. It may sometimes be necessary
to edit or modify the new mesh prior to the mapping operation (MAPSOLVE); in such cases, several
preprocessing (/PREP7) commands are available to help you create a good mesh on the selected region:
Figure 2.15: /PREP7 Mesh-Control Commands Available in Rezoning
Type of Mesh Applicable Commands

Control Desired
Element size AESIZE, DESIZE, ESIZE, KESIZE, LESIZE, and SMRTSIZE
Element shape MOPT, MSHAPE, and MSHKEY
Type of Mesh Applicable Commands

Control Desired
Element internal SHPP,MODIFY to reset the shape parameter limits. Specify input values of
angles 11~14 and 17~18 depending on the element type.
Boundary node Boundary nodes require special attention. Use the LESIZE command to
distribution space the nodes as uniformly as possible without disturbing other
characteristics of the mesh.
Refining AREFINE, EREFINE, KREFINE, LREFINE, NREFINE,
Other ACLEAR, AMESH, KSCON, LCCALC, MSHMID
If you remesh using a generic new mesh (p. 19) (rather than a
program-generated mesh (p. 18)), the N and EN commands are also
available.
The ACLEAR command applies only to the area generated via the
AREMESH command (that is, when remeshing using a
program-generated new mesh).
The mesh-control commands are available at any point after issuing a REMESH,START command and
before issuing a REMESH,FINISH command.
Nodes at which force or isolated displacements are applied must remain during remeshing, as do nodes
at the boundaries of distributed displacements, pressures, or contact/target surfaces. The new elements
must have the same attributes as the old elements, such as element type, material, real constant, and
element coordinate system. The program rotates the new nodes to the same angles as the old nodes
in the region or on the boundary, as the case may be.
After creating the new mesh, verify that the new elements cover the entire selected region and are
compatible with neighboring regions. (If another region requires remeshing, you can do so, but do not
issue another REMESH,START command.
2.7.3. Remeshing Multiple Regions at the Same Substep

You can create a new mesh for more than one region in the same deformed domain. Remeshing two
or more regions at the same specified substep is called horizontal rezoning.
You must use horizontal rezoning if you intend to remesh:
• Two regions with different materials, element coordinate systems, nodal coordinate systems, or real constants.
• The elements on both sides of a contact boundary.
• Two groups of highly distorted, noncontiguous elements.
Horizontal rezoning using a program-generated new mesh (p. 18) or a generic new mesh (p. 19) is
possible only when the remeshed areas are isolated from each other or, at most, share an interface;
however, the remeshed areas may not intersect. This restriction does not exist for manual mesh split-
ting (p. 23).
Rezoning
2.8. Step 5: Verify Applied Contact Boundaries, Surface-Effect Elements,

Loads, and Boundary Conditions
The program automatically generates the target/contact elements and supported surface-effect elements
if the underlying solid elements are remeshed, then transfers all applied boundary conditions (BCs) and
loads to the new mesh. Use plot or list commands to verify that the newly generated target/contact
elements, surface-effect elements, and the transferred BCs and loads, are complete and correct.
For further information, the following related topics are available:

2.8.1. Contact Boundaries
2.8.2. Surface-Effect Elements
2.8.3. Pressure and Contiguous Displacements
2.8.4. Forces and Isolated Applied Displacements
2.8.5. Nodal Temperatures
2.8.6. Other Boundary Conditions and Loads
After the contact boundaries, surface-effect elements, loads, and boundary conditions have been applied
and verified, proceed to Step 6: Automatically Map Variables and Balance Residuals (p. 36).
2.8.1. Contact Boundaries

Rigid target elements cannot be remeshed. They are automatically transferred from the original mesh
to the new mesh.
Deformable target elements and all contact elements are always attached to solid elements; therefore,
provided that the underlying solid elements are remeshed, the program creates the target/contact
elements automatically after exiting remeshing (REMESH,FINISH). the program passes all specified element
options, real constants, and materials from the old target/contact elements to the new ones automatically.
Verify that the new elements on the contact boundary are complete and correct.
2.8.2. Surface-Effect Elements

Surface-effect elements (SURF153 and SURF154) are always attached to solid elements; therefore,
provided that the underlying solid elements are remeshed, the program creates the surface-effect ele-
ments automatically after exiting remeshing (REMESH,FINISH). The program passes all specified element
options from the old surface-effect elements to the new ones automatically.
Verify that the new surface-effect elements on the boundary, and the transferred BCs and loads, are
complete and correct.
Only normal and tangential pressures applied on SURF153 and SURF154 are supported. (That is,
rezoning support is available only for pressure on faces 1 and 2 for SURF153 and pressure on faces 1,
2 and 3 for SURF154.)
2.8.3. Pressure and Contiguous Displacements

During remeshing, if you are using a program-generated new mesh (p. 18), the program maintains the
nodes on the boundary of the region where pressures or contiguous displacements are applied. If you
are using a generic new mesh created by another application (p. 19), you must maintain the nodes
manually.
Step 5: Verify Applied Contact Boundaries, Surface-Effect Elements, Loads, and
Boundary Conditions
In 2-D problems, the boundary consists of only the starting and ending points. In 3-D problems, the
boundary can be a line of ordered nodes representing a line bounding a set of facets.
You can redistribute nodes inside the region (between starting and ending points). If you do so, the
program uses linear interpolation to apply the pressures and displacements at the new node locations.
If the starting and ending points are rotated, the new nodes are also rotated with the angle determined
by linear interpolation of the angles of the old nodes. If the original distribution is not linear, the inter-
polation may introduce a small degree of error, although the error should not be significant if both the
original mesh and the new mesh are sufficiently dense.
The following illustration shows how the displacements are applied before and after remeshing.
Change in load
Applied
displacements
+ +
+ +
+
+
+
+
old mesh
new mesh
2.8.4. Forces and Isolated Applied Displacements

If a force or isolated (applied only at one node) displacement is applied at a node, the program maintains
that node, its rotation angle (if any), and the applied forces and displacements, during rezoning.
2.8.5. Nodal Temperatures

The program transfers only nodal temperatures applied via the BF command to the new nodes (by in-
terpolation with shape functions) from the old nodes.
If the remeshed region crosses the boundary where one side has old nodes with applied temperatures
and the other side does not, the interpolation may cause different temperature distributions at the new
nodes close to the boundary. Therefore, avoid remeshing the region crossing the boundary and use
horizontal rezoning (p. 19) instead.
When higher-order elements are used, the interpolated temperatures can exceed the maximum value
or fall below the minimum value. The behavior is due to the nature of the shape functions of the
higher-order elements. The effects of this limitation are minimized when both the old and new meshes
are sufficiently refined.
2.8.6. Other Boundary Conditions and Loads

Any other loads and boundary conditions (such as acceleration, coupling, and constraint equations) are
not valid in the remeshed region and are lost during rezoning, which may result in a solution that does
not converge or a solution that is very different from the one expected.
Rezoning
2.9. Step 6: Automatically Map Variables and Balance Residuals

Issue the MAPSOLVE command to map the solved node and element solutions automatically from the
original mesh to the new mesh. The mapping operation also introduces extra substeps to balance the
residuals and achieve equilibrium.
Assuming that you intend to continue the solution, MAPSOLVE is required and is the only rezoning
command that you can issue after remeshing (REMESH,FINISH).
For further information, the following mapping topics are available:

2.9.1. Mapping Solution Variables
2.9.2. Balancing Residual Forces
2.9.3. Interpreting Mapped Results
2.9.4. Handling Convergence Difficulties
When the mapping operation has completed, proceed to Step 7: Perform a Multiframe Restart (p. 38).
2.9.1. Mapping Solution Variables

The program maps the solution variables (such as nodal displacements, and element stresses and strains)
from the old mesh to the new mesh at the rezoned substep. The mapped variables must satisfy the
strain-displacement relationships, constitutive laws, and the equilibrium equations. Algorithms inherent
in the mapping scheme handle the first two conditions, but the mapped stress field is usually not in
equilibrium due to the different mesh. Therefore, the out-of-balance forces (the residual forces) must
be balanced. Balancing occurs via additional substeps.
2.9.2. Balancing Residual Forces

Additional substeps are introduced automatically to reduce residuals to zero. During this stage, the
time is increased by only a tiny amount (TIME * 10-6, where TIME = the time of the current load step).
Therefore, you can consider external loading to be unchanged.
The program always attempts to balance the residual forces within one substep. If it cannot, the program
uses bisection logic (automatically, regardless of any manual settings) to use more substeps. A rebalance
factor measures the balanced residuals and acts as the control factor during bisection (unlike a standard
solution where time is the control factor.) A rebalance factor of zero means that no residuals are balanced
yet, and a factor of 1 means that all residuals are balanced and the stress field is in equilibrium.
You can specify the maximum number of substeps--the default is five--to use during mapping (MAP-
SOLVE). Most problems should achieve balanced residual forces within a few substeps. If contact is in-
cluded, more substeps may be necessary.
Output File
In the output file, the program presents MAPSOLVE command data as shown:
S O L U T I O N O P T I O N S
PROBLEM DIMENSIONALITY. . . . . . . . . . . . .2-D

DEGREES OF FREEDOM. . . . . . UX UY ROTZ
ANALYSIS TYPE . . . . . . . . . . . . . . . . .STATIC (STEADY-STATE)
MAPSOLVE FOR REZONING. . . . . . . . . . . .YES
NONLINEAR GEOMETRIC EFFECTS . . . . . . . . . .ON
STRESS-STIFFENING . . . . . . . . . . . . . . .ON
EQUATION SOLVER OPTION. . . . . . . . . . . . .SPARSE
NEWTON-RAPHSON OPTION . . . . . . . . . . . . .PROGRAM CHOSEN
Step 6: Automatically Map Variables and Balance Residuals
GLOBALLY ASSEMBLED MATRIX . . . . . . . . . . .SYMMETRIC
L O A D S T E P O P T I O N S
LOAD STEP NUMBER. . . . . . . . . . . . . . . . 1

TIME AT END OF THE LOAD STEP. . . . . . . . . . 1.0000
AUTOMATIC TIME STEPPING . . . . . . . . . . . . ON
INITIAL NUMBER OF SUBSTEPS . . . . . . . . . 10
MAXIMUM NUMBER OF SUBSTEPS . . . . . . . . . 100
MINIMUM NUMBER OF SUBSTEPS . . . . . . . . . 5
MAXIMUM NUMBER OF SUBSTEPS FOR MAPSOLVE. . . 50
MAXIMUM NUMBER OF EQUILIBRIUM ITERATIONS. . . . 15
STEP CHANGE BOUNDARY CONDITIONS . . . . . . . . NO
STRESS-STIFFENING . . . . . . . . . . . . . . . ON
TERMINATE ANALYSIS IF NOT CONVERGED . . . . . .YES (EXIT)
CONVERGENCE CONTROLS. . . . . . . . . . . . . .USE DEFAULTS
PRINT OUTPUT CONTROLS . . . . . . . . . . . . .NO PRINTOUT
DATABASE OUTPUT CONTROLS
ITEM FREQUENCY COMPONENT
ALL ALL
Mapping Substeps
The number of substeps used for mapping appears as follows:

*** LOAD STEP 1 SUBSTEP 10 COMPLETED. CUM ITER = 101
*** TIME = 0.399110 REBALANCE FACTOR = 1.00000
*** ANSYS BINARY FILE STATISTICS

BUFFER SIZE USED= 16384
0.375 MB WRITTEN ON ELEMENT SAVED DATA FILE: RznExample.esav
0.125 MB WRITTEN ON ASSEMBLED MATRIX FILE: RznExample.full
0.375 MB WRITTEN ON RESULTS FILE: RznExample.rst
MAPSOLVE IS DONE SUCCESSFULLY IN 3 SUBSTEPS FOR MANUAL REZONING.
Monitor File
The 6th and 7th columns of the monitor file indicate the rebalance factor (rather than the time) for
each mapping substep, as shown:
SOLUTION HISTORY INFORMATION FOR JOB: RznExample.mntr
13:06:16 09/20/2004
LOAD SUB- NO. NO. TOTL INCREMENT TOTAL VARIAB 1 VARIAB 2 VARIAB 3
STEP STEP ATTMP ITER ITER REBALANCE REBALANCE MONITOR MONITOR MONITOR
FACTOR FACTOR Wall MxDs MxPl
1 8 2 7 93 0.35000 0.35000 5.4300 -.64291 0.78886E-30

1 9 1 4 97 0.35000 0.70000 8.0600 -.81383 0.78886E-30
1 10 1 4 101 0.30000 1.0000 11.260 -.93615 0.78886E-30
Although multiple substeps may be necessary to balance all residuals, the program generates the restart
file and saves the result in a results file for only the last converged mapping substep. (Only the last
substep gives the balanced solution.) The program ignores any preexisting output specifications (set
via OUTRES or RESCONTROL commands, for example).
2.9.3. Interpreting Mapped Results

The mapped (p. 36) results are not simply the solution variables interpolated from the old mesh, but
balanced (p. 36) results mapped from the old mesh. If the new mesh topology or density is very different
from the old mesh, the mapped results may also be very different.
Rezoning
The reported stresses and strains represent the total stresses and strains from TIME = 0. However, the
reported displacements are from the rezoned time or substep (when the element coordinates were
updated via the REZONE command).
After the MAPSOLVE command has executed, the new mesh may be somewhat distorted, and the
distortion may be even more significant if the residual forces are large. In such a case, more careful region
selection and better remeshing (p. 17) are necessary.
2.9.4. Handling Convergence Difficulties

If the rezoning process encounters convergence difficulties during the mapping (p. 36) (MAPSOLVE)
stage of the rezoning process, try the following:
• Specify a larger maximum number of mapping substeps (although no more than 500) via the MAPSOLVE
command.
• Minimize the differences in mesh density and topology between the old and new mesh, especially in the
elements on boundaries.
• Rezone from an earlier substep (so that you can start with a slightly less distorted original mesh).
• Enhance the quality of the new mesh.
2.10. Step 7: Perform a Multiframe Restart

After successfully mapping (p. 36) (MAPSOLVE) solved variables from the old mesh to the new mesh
and checking the mapped results (p. 37), continue the solution based on the new mesh via a standard
multiframe restart from the last mapping substep (that is, the substep at which you initiated rezoning
plus the number of substeps required by the mapping operation).
Even if you have rezoned several times in the same domain (p. 38), you can still perform a standard
multiframe restart.
You can restart from any substep at which the .rxxx file, .rdb file, and .ldhi load history file exist.
You need only specify the substep to restart; the program detects the necessary .rdb file, and the
.rst file to modify, then finds the corresponding load history information from the .ldhi file.
After the restart, the program deletes all .rdb, .rst, and .rxxx files on the substeps subsequent to
the specified restart substep.
This step concludes the rezoning process. At this point, you can repeat the rezoning process (p. 38)
if you wish, or perform postprocessing (p. 39) on the rezoned analysis results.
2.11. Repeating the Rezoning Process if Necessary

More than one rezoning may be necessary if a mesh distortion still exists in the domain despite a pre-
vious rezoning. You can rezone a domain that you have already rezoned by selecting a region (p. 16)
(or regions) in the same domain at a different time and substep (p. 15) than that of the initial rezoning.
To rezone again, a region that you select for remeshing (p. 17) can be the same region that you selected
in a previous rezoning or a different region. As in the initial rezoning, you can use horizontal rezon-
ing (p. 19) to select more than one region for remeshing.
Postprocessing Rezoning Results
Although no theoretical limit on the number of allowable rezonings in the same domain exists, the
program allows up to 99 rezonings in a single job. In practice, two or three rezonings in a given domain
should be sufficient.
To perform another rezoning, simply repeat the rezoning process (p. 11). No special command is neces-
sary, and the rezoning process remains the same.
2.11.1. File Structures for Repeated Rezonings

When multiple rezonings occur in the same domain during the same analysis, each creates a different
finite element model. To make restarting and rezoning from any substep possible, the program saves
the .rdb files for the initial model and for each rezoned model. However, only one result .rst file is
created for postprocessing.
Following is the file structure after more than one rezoning has occurred:
File type Rezone 0 Rezone 1 Rezone 2 ... Rezone 11 ... Rezone nn

(standard
run)
.rdb .rdb .rd01 .rd02 ... .rd11 ... .rdnn
.rxxx .rxxx .rxxx .rxxx ... .rxxx ... .rxxx
.ldhi .ldhi
.rst .rst
The maximum number of .rdb files is 99. The .ldhi load history file contains information for all
models created as a result of multiple rezonings.
2.12. Postprocessing Rezoning Results

For rezoning, the POST1 postprocessor (/POST1) is the primary postprocessing tool and most of its
capability is available. Animation is also available via the ANDATA macro.
Each time rezoning occurs, the mesh changes, so new .rdb files are necessary. For example, if you
have used rezoning twice during the same analysis, the program writes the following database files:
.rdb, .rd01, and .rd02. (For more information, see File Structures for Repeated Rezonings (p. 39).)
Most POST1 postprocessing operations proceed seamlessly from one database file to the next automat-
ically; therefore, do not delete the .rst or .rdb file, nor any .rdnn files, until you have completed
postprocessing.
Displacement output for the rezoned model reports values as of the most recent rezoning, so the dis-
placement will not seem to be continuous over multiple rezonings.
2.12.1. Using the Database Postprocessor (POST1)

Keep all .rdb and .rdnn database files until all desired postprocessing work has been completed.
The POST1 postprocessor is dependent on the .rst results file, and on the .rdb and .rdnn files. If
all or some of the database files are lost, the program uses the .rst file to recover as much data as
possible. In such cases, however, data that exists only in database files may no longer be available,
causing some postprocessing operations to behave unexpectedly. For example, information about
defined components (CM), body force loads on nodes (BFLIST), and surface loads (SFLIST) may be
missing.
Rezoning
If you exited the program after the solution phase of the analysis and now want to perform POST1
postprocessing on your rezoning results, issue the /FILNAME command to specify the appropriate
jobname before entering the POST1 processor. This is the preferred method for postprocessing
rezoning results.
2.12.1.1. Listing the Rezoning Results File Summary

After entering the POST1 processor, it is helpful to issue the SET,LIST command.
For rezoning, the output list generated by the command indicates when a mesh change (and corres-
ponding database file change) occurs due to rezoning, as shown in this example output list (SET,LIST):
***** INDEX OF DATA SETS ON RESULTS FILE *****
SET TIME/FREQ LOAD STEP SUBSTEP CUMULATIVE
1 0.1000000 1 1 2
2 0.2000000 1 2 4
3 0.3500000 1 3 6
4 0.5500000 1 4 8
5 0.7500000 1 5 10
6 0.7500010 1 6 13 mesh changed
7 0.8750000 1 7 15
8 1.000000 1 8 17
...
The output from a SET,LIST command is also useful for simply determining what information is available.
For non-rezoning runs, for example, you can select substeps for further study by load step and substep
number, time, set number, and the set for which a different mesh is used.
2.12.1.2. Animating the Rezoning Results

Animation for rezoning is available via the ANDATA macro.
Assuming that the appropriate jobname is already specified, the program proceeds from one mesh to
the next automatically, using the data in each to generate the animation.
During the macro's initial scan, the program stores the view location and size of every saved substep.
The program then combines the information to provide one fixed view (by internally setting the /FOCUS
and /DIST commands to fixed values).
2.12.2. Using the Time-History Postprocessor (POST26)

When using the POST26 time-history postprocessor (/POST26) on a model that you have rezoned, all
of the usual information is available. Access it as follows:
1. Reset (RESET) the postprocessor specifications to initial defaults, erase all defined variables, and clear the
data storage space.
2. Resume (RESUME) the appropriate .rdnn database file (generally the one corresponding to the most re-
cently created mesh).
3. Issue a FILE command to open the .rst results file.
Only the output information available is fetched from the results file, as elements and nodes that exist
in one mesh do not always exist in another.
Rezoning Examples
2.13. Rezoning Restrictions

After you initiate the rezoning process (REZONE), and until you map the solved variables from the old
mesh to the new mesh (MAPSOLVE) at the conclusion of the rezoning process, you will lose your
rezoning work if you exit the solution processor (/SOLU) prematurely. This condition applies even if
you save (SAVE) before exiting and then resume (RESUME) after returning to the solution processor.
Issuing a REMESH,READ command (to import a generic new mesh (p. 19)) or a REMESH,SPLIT command
(to split an existing mesh (p. 23)) causes the mesh to lose associativity with its corresponding geometry.
It is therefore not possible to issue commands that perform geometry-based operations. (You can issue
commands that perform mesh-based operations, however.)
When using a generic new mesh (p. 19) created by a third-party application (REMESH,READ):
• Mesh regions cannot intersect.
• If multiple regions are read in (REMESH,READ) via a single .cdb file, the nodes of these regions must be
encapsulated in a single NBLOCK environment, and the elements must be encapsulated in a single EBLOCK
environment.
For a 2-D analysis, you can issue the following remeshing commands in the same session on multiple
regions:
AREMESH,AMESH (to create a program-generated new mesh (p. 18))

REMESH,READ (to import a generic new mesh (p. 19))
REMESH,SPLIT (to split an existing mesh (p. 23))
For a 3-D analysis, remeshing is possible only by importing a new mesh created by another application
(REMESH,READ) or by splitting an existing mesh (REMESH,SPLIT).
Components are not passed through the rezoning operation.
Rezoning does not support:
• POST1 load-case combination commands (such as LCASE, LCDEF, LCOPER, and LCSEL)
• Initial state loading (INISTATE)
• Dropped midside nodes for higher-order elements (EMID)
• Coupling (CP) and constraint equations (CE)
• Cyclic symmetry boundary conditions
• Distributed ANSYS
2.14. Rezoning Examples

The following example simulations introduce you to rezoning (p. 5):
2.14.1. Example: Rezoning Using a Program-Generated New Mesh
2.14.2. Example: Rezoning Using a Generic New Mesh
Also see Nonlinear Analysis of a 2-D Hyperelastic Seal Using Rezoning, Ring-Gear Forging Simulation
with Rezoning, and Hot-Rolling Structural Steel Analysis with 3-D Rezoning in the Technology Demon-
stration Guide.
Rezoning
2.14.1. Example: Rezoning Using a Program-Generated New Mesh

Following is an example simulation involving a sealing assembly problem. The example uses a program-
generated new mesh (p. 11) for the remeshing operation.
A rubber seal has an initial rectangular shape and consists of a hyperelastic material modeled with two
parameters as a Mooney-Rivlin model. A shaft has a circular cross section and is assumed to be rigid.
The shaft moves down vertically. The simulation plots the element strain in the y direction.
Given the initial input (p. 42), the simulation terminates at substep 10 (TIME = 0.44) because of a mesh
distortion. After rezoning (p. 44), which occurs at substep 7, the simulation concludes successfully with
the new mesh.
2.14.1.1. Initial Input for the Analysis

This input results in a deformed mesh and causes the analysis to terminate:
/batch,list
/filname,RznExample1
/prep7
/com define parameters

h=20
b=10
el=b/8
xc=17.5
yc=32.99038
rc=15
PilotMove= -13
c10=62.3584129
c01=-37.8485452
dd=1e-4
/com define element types, material, etc.

et,1,182
keyopt,1,3,2
keyopt,1,6,1
et,2,169
et,3,172
keyopt,3,9,0
keyopt,3,10,1
Rezoning Examples
et,4,169
et,5,172
keyopt,5,9,0
keyopt,5,10,1
tb,hyper,1,,2,mooney
tbdata,1,c10,c01,dd
mp,mu,2,0.0
r,3
r,4
/com define geometry

k,1,xc,yc
k,2,xc,yc,yc
k,3,xc-rc,yc
k,4,0.0,0.0
k,5,2*rc,0.0
rect,0,b,0,h
circle,1,rc,2,3,360,1
/pnum,line,1
lplot
l,4,5
lplot
aplot
/com create solid elements

esize,el
mat,1
type,1
real,1
amesh,1
/com generate the 1st contact pair

mat,2
real,3
type,2
esize,h
lmesh,5,7
*get,PilotID,node,,num,max
PilotID=PilotID+1
nkpt,PilotID,1
tshap, pilo
e,PilotID
type,3
lsel,,,,2,3
nsll,,1
esln,,0
esurf
alls
/com generate the 2nd contact pair

real,4
type,4
lmesh,8
lsel,,,,8
esll
esurf,,reverse
alls
type,5
lsel,,,,1,2
nsll,,1
esln,,0
esurf
alls
Rezoning
/com apply boundary conditions and loads

d,PilotID,ux,0.0
d,PilotID,uy,PilotMove
d,PilotID,rotz,0.0
lsel,,,,4
nsll,,1
d,all,ux,0.0
alls
lsel,,,,8
nsll,,1
d,all,uy,0.0
alls
nlist
elist
dlist
/com check the contact definition

cncheck
finish
/solution
rescontrol,,all,1
pred,off
nlgeom,on
time,1
NSUBST,10,100,5
outres,all,all
solve
finish
/post1
set,1,6
prns,u,comp
prns,s,comp
prns, cont
finish
2.14.1.2. Rezoning Input for the Analysis

This input uses rezoning to remesh the deformed region and allow the analysis to proceed using the
new mesh:
/batch,list
/clear,nostart
/solution
rezone,manual,1,6 ! specify the substep to rezone
remesh,start ! start remeshing operation

esel,,,,65,128 ! select region to remesh
aremesh ! create area for new mesh
lesize,10,,,8
lesize,31,,,10
lesize,18,,,6
amesh,2 ! create the new mesh
esel,all
nsel,all
remesh,fini ! finish remeshing operation
elist ! check the new model, BC and loads

dlist
mapsolve,50 ! map solutions
finish
Rezoning Examples
/solution ! restart
antype,,restart
solve
finish
2.14.2. Example: Rezoning Using a Generic New Mesh

Following is an example simulation involving a heading assembly problem. The example uses an imported
generic mesh generated by another application (p. 12) for the remeshing operation.
The model represents an axisymmetric hollow hemisphere that pushes down a cylindrical workpiece.
The spherical ball and the grip die are modeled as rigid surfaces. Due to element distortion, the initial
run stops at t = 0.7875. Rezoning is applied at this time to achieve complete loading. The entire deformed
model at substep 4 is imported into ANSYS ICEM CFD, which generates a new mesh. After reading the
new mesh back in, the program creates the contact automatically when you issue the REMESH,FINISH
command.
The solid element used in the model is PLANE182 (using the B-Bar method with mixed u-P formulation).
CONTA171 and TARGE169 elements are also used. The material model used is a hyperelastic material
with a three-parameter OGDEN option.
2.14.2.1. Initial Input for the Analysis

This is the initial mesh:
This input results in a deformed mesh and causes the analysis to terminate at t = 0.7875 seconds:
/batch, list
/prep7
h=4.6295
b=1.5
el=b/4
xc=0
yc=2.6295
rc=2.5
PilotMove= -yc
! ogden parameters
TB,HYPE,1,1,3,OGDE
TBTEMP,0
TBDATA,1,3.2084E-009,7.281,0.035198,3.0149,6.3712,2.0493
Rezoning
et,1,182
keyopt,1,3,0
keyopt,1,6,1
et,2,169
et,3,171
keyopt,3,9,0
keyopt,3,10,1
et,4,169
et,5,171
keyopt,5,9,0
keyopt,5,10,1
mp,mu,2,0.0
r,3
r,4
k,1,xc,yc
k,2,xc,yc,yc
k,3,rc,yc
k,4,0.0,0.0
k,5,rc+1,0.0
rect,0,b,0,h
circle,1,rc,2,3,90,1
/pnum,line,1
lplot
l,4,5
lplot
aplot
esize,el
mat,1
type,1
real,1
amesh,1
/pnum,elem,1
/pnum,node,1
/com the 1st contact pair
mat,2
real,3
type,2
esize,h
lmesh,5
lsel,,,,5
esll
esurf,,reverse
alls
*get,PilotID,node,,num,max
PilotID=PilotID+1
nkpt,PilotID,1
tshap, pilo
e,PilotID
type,3
lsel,,,,2,3
nsll,,1
esln,,0
esurf
alls
/com the 2nd contact pair
real,4
type,4
lmesh,6
lsel,,,,6
esll
esurf,,reverse
alls
type,5
lsel,,,,1,2
nsll,,1
esln,,0
esurf
alls
d,PilotID,ux,0.0
d,PilotID,uy,PilotMove
d,PilotID,rotz,0.0
lsel,,,,4
Rezoning Examples
nsll,,1
d,all,ux,0.0
alls
lsel,,,,6
nsll,,1
d,all,uy,0.0
alls
/solution
pred,off
rescontrol,,all,1,
eresx,no
nlgeom,on
time,1
NSUBST,10,100,5
outres,all,all
solve
finish
Following is the total elastic strain along the Y axis at t = 0.7875. The element distortion is apparent
and causes the problem to diverge.
2.14.2.2. Exporting the Distorted Mesh as a CDB File

When the nonlinear analysis stops, reload the database at load step 1 and substep 4. Select all solid
elements and write out to a .cdb file. (Only solid elements can be read in later when you are ready to
generate the new mesh.)
/clear,nostart
/solu ! enter solution environment
rezone,manual,1,4 ! start rezoning at load step1, substep 4
eplot ! plot the elements
etlist ! list the element types
ESEL,S,TYPE,,1 ! select only the elements of type ‘1’(solids)
cdwrite,db,RznExample2,cdb ! write out the selected elements to a CDB file
finish
Rezoning
With the deformed mesh corresponding to load step 1, substep 4 is shown next. ANSYS ICEM CFD uses
the boundary segments of this mesh next to generate the new mesh. The nodal discretization at the
boundary remains same for both the old and the new mesh.
Next, the total elastic strain along the Y axis for this mesh is shown. This is one of the state variables
which is transferred to the new mesh when mapping solved node and element solutions from the ori-
ginal mesh to the new mesh (MAPSOLVE).
2.14.2.3. Importing the File into ANSYS ICEM CFD and Generating a New Mesh
At this stage of the rezoning process, start ANSYS ICEM CFD and read in the .cdb file. (Reminder: As
indicated in Exporting the Distorted Mesh as a CDB File (p. 47), only solid elements can be read in.)
Generate the new .cdb file as follows:
1. Import the .cdb file in ANSYS ICEM CFD as mesh (File Menu> Import Mesh> From Ansys).
Rezoning Examples
2. Extract triangulated (STL) geometry from the mesh (Edit Menu> Mesh to Facets)
3. Set the global maximum element size in the order of the element size that you require (Mesh> Global
Mesh Setup> Global Mesh Size> Max Element).
4. Build the topology (Geometry> Repair geometry> Build topology)
5. Select the “Respect line elements” and “Protect given line elements” options (Mesh> Global Mesh Setup>
Shell Meshing Params).
6. Compute the new mesh (Mesh> Compute mesh> Surface mesh only> Mesh type: All Quad > Compute).
7. Select the Solve Options tab and write the input file. Do not include the bar elements.
8. Rename the new input file as a .cdb file.
The new mesh obtained from ANSYS ICEM CFD is shown here. Notice that the boundary discretization
remains the same as that of the old mesh.
2.14.2.4. Rezoning Using the New CDB Mesh

Continue rezoning with the new mesh (.cdb file) and restart the analysis, as follows:
/clear,nostart
rezone,manual,1,4 ! start rezoning from load step 1, substep 4
remesh,start ! start remeshing
remesh,read,RznExample2,cdb,rege ! read in the new mesh (CDB file)
remesh,finish ! finish remeshing, autogenerate contacts
mapsolve,500,pause ! do state variable mapping and equilibriation
finish
After the MAPSOLVE command has executed (mapping the solved node and element solutions from
the original mesh to the new mesh), the total elastic strains along Y for the new mesh appears. Notice
that some expected nodal realignment has occurred in the new mesh.
Rezoning
Restart the problem. The solution to progresses to t = 1s.

/clear,nostart
antype,,restart ! multiframe restart
solve ! solve the problem
finish
Allow the analysis to complete. Following is a plot of the total elastic strain along the Y direction:
Chapter 3: Mesh Nonlinear Adaptivity
Use mesh nonlinear adaptivity to modify the mesh (according to specified criteria) during solution,
either to simulate some problem which otherwise cannot be simulated or to improve the accuracy of
simulation results. Unlike rezoning, mesh nonlinear adaptivity is completely automatic, requiring no
user input during solution. While only one of the nonlinear adaptivities, mesh nonlinear adaptivity is
arguably the most powerful.
Mesh nonlinear adaptivity is available for 2-D and 3-D analyses.
Mesh nonlinear adaptivity criteria are the rules used to determine whether the mesh needs to be
modified and, if so, what parts of the mesh should be modified. Several criteria types (p. 66) are available.
You determine how frequently (p. 69) the criteria should be checked.
When the defined criteria are met, mesh modification occurs either by splitting (p. 70) or by general
remeshing (p. 73):
• Splitting applies to contact-based (p. 67), energy-based (p. 66) and position-based (p. 67) criteria.
During splitting, the current elements are divided into elements having a half-edge length. Some
transition layers are created automatically to connect the refined regions to the unrefined regions.
Some topology changes and morphing occur during 3-D tetrahedral element splitting to improve the
quality of the new mesh; for 2-D meshes, only morphing is done after the element-splitting operation.
• General remeshing applies to the mesh-quality-based (p. 68) criteria, used with either the 2-D lower-
order quad element PLANE182 or 3-D linear tetrahedral element SOLID285. During remeshing, the se-
lected region is completely remeshed to obtain a high-quality mesh.
The following topics related to mesh nonlinear adaptivity are available:

3.1. Mesh Nonlinear Adaptivity Benefits
3.2. Mesh Nonlinear Adaptivity Usage Considerations
3.3. Understanding the Mesh Nonlinear Adaptivity Process
3.4. Mesh Nonlinear Adaptivity Criteria
3.5. Specifying Criteria-Checking Frequency
3.6. Generating the New Mesh
3.7. Convergence at Substeps with the New Mesh
3.8. Controlling Mesh Nonlinear Adaptivity
3.9. Postprocessing Mesh Nonlinear Adaptivity Results
3.10. Mesh Nonlinear Adaptivity Examples
For related information, see Rezoning.
3.1. Mesh Nonlinear Adaptivity Benefits

These example problems highlight the benefits of mesh nonlinear adaptivity:
3.1.1. Rubber Seal Simulation
3.1.2. Crack Simulation
3.1.3. 3-D Metal Forging Simulation
3.1.4. 2-D Metal Extrusion Simulation
Mesh Nonlinear Adaptivity
3.1.1. Rubber Seal Simulation

To demonstrate the benefits of mesh nonlinear adaptivity, consider a rubber seal simulation, with an
initial geometry and mesh as shown in the following figure:
Figure 3.1: Rubber Seal with Coarse Mesh
Downward displacement is applied to the rigid surface on the top of the seal. The following figure
shows the program output for the deformed seal:
Figure 3.2: Deformed Rubber Seal with Coarse Mesh
The shape of the deformed material in the gap is not realistic because the mesh is too coarse. To create
a more accurate simulation, nonlinear adaptivity with position-based criteria is used to refine the mesh
of the elements which will fill the gap. Two mesh refinements are performed automatically during the
solution to create a more detailed mesh in the model. The following figure shows the first mesh refine-
ment:
Mesh Nonlinear Adaptivity Benefits
Figure 3.3: Rubber Seal Model with Initial Mesh Refinement
The following figure shows the second refinement of the part of the rubber seal model that will fill the
gap:
Figure 3.4: Rubber Seal Model with Second Mesh Refinement
When the full load is applied in the simulation, the program outputs the following deformed seal:
Figure 3.5: Deformed Rubber Seal with Mesh Refinements
With nonlinear adaptivity, the accuracy of the simulation of this type of rubber seal problem is greatly
increased.
To examine the input for this problem, see Example: Rubber Seal Simulation (p. 91).
3.1.2. Crack Simulation

Another example of the increased accuracy achieved with mesh nonlinear adaptivity involves mesh
refinements in regions with high stress concentrations. For example, consider this material cracking
model:
Figure 3.6: Crack Simulation Model with Coarse Mesh
The following figure shows the program output for the crack simulation:
Figure 3.7: Crack Simulation Solution with Coarse Mesh
The solution and solution time are:
σx σy τxy σ_VM Elapsed

Time
214113 91103.2 91641.2 244606 12.00
For a more accurate solution at the crack tip, nonlinear adaptivity is applied using energy-based criteria.
When three refinements are applied during solution, the program outputs the following:
Figure 3.8: Crack Simulation Solution with Three Mesh Refinements

Time
262713 291816 164471 361413 64
If the same simulation is performed with a fine mesh and no mesh nonlinear adaptivity, the program
outputs the following:
Figure 3.9: Crack Simulation Solution with Fine Mesh and No Mesh Nonlinear Adaptivity

Time
293992 274278 160033 365929 190
As demonstrated, nonlinear adaptivity provides sufficient accuracy, yet with drastically reduced simulation
time.
To examine the full input for this problem, see Example: Crack Simulation (p. 93).
3.1.3. 3-D Metal Forging Simulation

This example problem demonstrates how to apply mesh nonlinear adaptivity to remove mesh distortion
and solve problems associated with high deformation. Unlike the two prior problems, general remeshing
is necessary with the mesh-quality-based criterion applied in this problem.
Consider a metal forging simulation, with an initial geometry and mesh, as shown in this figure:
Figure 3.10: Metal Block Ready to Be Forged Showing Initial Mesh
The flexible block has symmetry boundary conditions on three facets. A rigid die is placed on the top
of the block with applied displacement in the Y direction. It is intended to compress the block to 80
percent. Without nonlinear adaptivity, the simulation cannot converge because of high mesh distortion,
as shown in this figure:
Figure 3.11: View of Block on X-Y Plane After Diverging (No Nonlinear Adaptivity)
The solution diverges at approximately 40 percent load with the following error:
Nonlinear adaptivity with a mesh-quality-based criterion corrects the mesh shape caused by high dis-
tortion. To check the mesh quality at every substep, skewness is set to 0.9 (NLADAPTIVE,,,MESH,SKEW-
NESS,0.9). With several remeshings, the full load is successfully applied, as shown with deformation in
this figure:
Figure 3.12: Final Solution After Converging Using Nonlinear Adaptivity
To examine the input file for this example, see Example: 3-D Metal Forging Simulation (p. 95).
3.1.4. 2-D Metal Extrusion Simulation

This example problem demonstrates the benefits of mesh nonlinear adaptivity for simulating cases with
very high deformation. This 2-D problem uses a generalized plane strain extrusion model.
The flexible block of height = 19.5 in this figure will be compressed on the right side by a rigid die
(where applied displacements = 30) to reduce its height to 6.5:
Figure 3.13: Metal Block Ready to Be Extruded Showing Initial Mesh
The bottom of the block has a symmetric boundary condition, the die is a frictionless rigid, and the
material is elasto-plastic.
Without nonlinear adaptivity, the solution diverges at approximately 80 percent load due to mesh dis-
tortion, generating the following error message:
Figure 3.14: Deformed Shape of Metal Block After Diverging (No Nonlinear Adaptivity)
Nonlinear adaptivity with a mesh-quality-based criterion corrects a highly deformed mesh shape. To
check the mesh quality at every substep, the maximum corner angle of the mesh shape is set to 155
(NLADAPTIVE,,,MESH,SHAPE,155). With several remeshings (depending on the platform), the full load
is successfully applied, as shown with deformation in this figure:
Mesh Nonlinear Adaptivity Usage Considerations
Figure 3.15: Shape of Metal Block After Converging (Using Nonlinear Adaptivity)
To examine the input file for this problem, see Example: 2-D Metal Extrusion Simulation (p. 96).
3.2. Mesh Nonlinear Adaptivity Usage Considerations

Mesh adaptivity through refinement can improve solution accuracy in general. It can help to capture
local deformations in more detail, useful in applications such as rubber sealing for small cavities, diffuse
or local necking, and local buckling. Without a sufficiently fine mesh, these phenomena are difficult to
simulate, yet it is often infeasible to start with a very fine mesh.
Typically, mesh nonlinear adaptivity via splitting or refinement cannot repair a distorted mesh. In some
cases, it can exacerbate mesh distortion by creating smaller elements. To reduce the effect, the program’s
mesh nonlinear adaptivity capability uses built-in morphing and topology repair after splitting; even
so, mesh quality improvement is slight. Avoid splitting or refinement in highly distorted regions,
therefore, as doing so may lead to convergence problems.
Mesh nonlinear adaptivity via the general remeshing (p. 73) method removes mesh-distortion problems.
Use general remeshing with the mesh-quality-based (p. 68) criterion when a problem cannot be solved
due to mesh distortion. General remeshing cannot occur at the same time as mesh splitting. The gen-
eral remeshing method supports self-contact in 2-D analyses only. Also, the character string "_NLAD"
cannot appear in component names, in the job name, or in the main title of input defined via the /TITLE
command.
Mesh nonlinear adaptivity does not require restart files. (Issuing a RESCONTROL,,NONE command,
however, is neither necessary nor allowed.) It supports analyses with large-deflection effects enabled
(NLGEOM,ON). Nonlinear adaptivity shares the remaining basic requirements and element support ne-
cessary for rezoning.
Nonlinear adaptivity criteria are applied on element components. Those components must be defined
and selected before issuing first SOLVE command.
3.2.1. Mesh Nonlinear Adaptivity Requirements and Limitations

The same requirements for a rezoning analysis apply to a mesh nonlinear adaptivity analysis. For more
information, see Rezoning Requirements (p. 8).
Some limitations apply, however, based on the specified mesh nonlinear adaptivity criterion and option
(NLADAPTIVE):
Table 3.1: Mesh Nonlinear Adaptivity Limitations
NLADAPTIVE, , Cri- Limitations

terion, Option
CONTACT, NUMELEM Elements SOLID185, SOLID186, and
SOLID187 are not supported.
CONTACT, WEAR Elements SOLID185 and SOLID186 are not
supported
ENERGY, MEAN Elements SOLID185, SOLID186, and
BOX, XYZRANGE Elements SOLID185, SOLID186, and
MESH, SKEWNESS Only SOLID285 is supported.
Self-contact is not supported.
Fluid-penetration loads are not

supported.
MESH, SHAPE Only PLANE182 is supported.
3.3. Understanding the Mesh Nonlinear Adaptivity Process

Use mesh nonlinear adaptivity to control the mesh quality during a nonlinear solution. The process is
defined by nonlinear adaptivity criteria in three additional inputs before the solution. When the solution
begins, the process is automatic and requires no further input.
The following flowchart shows the general process during solution when mesh nonlinear adaptivity is
activated:
Understanding the Mesh Nonlinear Adaptivity Process
Figure 3.16: Mesh Nonlinear Adaptivity During Solution
3.3.1. Checking Nonlinear Adaptivity Criteria

Nonlinear adaptivity criteria checking is performed at the end of each specified substep (according to
the specified checking frequency) after it converges. (The frequency of criteria checking is set via VAL1
and Action = ON on the NLADAPTIVE command.) After generating a new mesh, the program moves
to the next substep. If a particular substep is the last of a load step, the mesh remains unchanged.
The following topics related to checking nonlinear adaptivity criteria are available:
3.3.1.1. Defining Element Components
3.3.1.2. Defining Nonlinear Adaptivity Criteria
3.3.1.3. Defining Criteria-Checking Frequency
3.3.1.1. Defining Element Components

This part of the mesh nonlinear adaptivity process defines regions of the model for which nonlinear
adaptivity is to be applied.
Contact and target element components can have only contact-based criteria applied. Solid elements
can have all other criteria applied, but mesh-quality-based criteria cannot be combined with them. If
an element has unsupported nonlinear criteria, or the analysis type is not supported, the criteria or the
element’s contribution in nonlinear adaptivity is ignored.
You can define all solid, contact, and target elements in the whole domain under one component so
that the mesh nonlinear adaptivity criteria is applied to the entire model. Elements in the same region
can have different component names so that the same type of criteria with the same options but different
values (NLADAPTIVE) can be applied. The components must be defined and selected before issuing
the first SOLVE command.
3.3.1.2. Defining Nonlinear Adaptivity Criteria

During solution, the mesh nonlinear adaptivity criteria are checked for each component to determine
if elements need to be split or remeshed. Based on the criteria, the program splits or remeshes solid
elements. Surface, target, and contact elements are regenerated when solid elements underneath are
split or remeshed. Nonlinear adaptivity criteria remain active until overwritten by a new command. The
criteria can be modified between load steps and upon restart. Defined criteria can also be deleted or
listed. For more information, see the NLADAPTIVE command.
3.3.1.3. Defining Criteria-Checking Frequency

This part of the mesh nonlinear adaptivity process defines the frequency at which mesh nonlinear ad-
aptivity criteria are checked during solution.
The frequency is problem- and criterion-dependent. Too-frequent checking can slow the simulation,
but checking too infrequently can result in local deformations being missed during solution or
remeshing to occur later than needed to solve the problem.
For more information, see Specifying Criteria-Checking Frequency (p. 69).
3.4. Mesh Nonlinear Adaptivity Criteria

Several nonlinear adaptivity criteria can be defined to control the mesh during nonlinear solutions:
3.4.1. Energy-Based Criterion
3.4.2. Position-Based Criterion
3.4.3. Contact-Based Criterion
3.4.4. Mesh-Quality-Based Criterion
Also see Specifying Criteria-Checking Frequency (p. 69).
3.4.1. Energy-Based Criterion

This criterion is defined for current-technology structural 2-D and 3-D solid elements, and is based on
the magnitude of strain energy applied to the element compared to the mean strain energy of compon-
ents to which the element belongs. During the substep at which mesh nonlinear adaptivity criteria are
checked, if the element’s strain energy is greater than or equal to the mean strain energy of its compon-
ents times the user-defined VAL1 (set via the NLADAPTIVE,,ADD command), then the element is split
and remeshed.
This criterion is used to refine the mesh to achieve high-accuracy simulation in regions where a high
concentration of stress exists and elements are too large. It can also be used to refine the mesh at certain
intervals of substeps if a very small value or 0 is input for VAL1.
Mesh Nonlinear Adaptivity Criteria
3.4.2. Position-Based Criterion

This criterion is defined for current-technology structural 2-D and 3-D solid elements. A region is defined
in the global Cartesian coordinates. During the substep at which mesh nonlinear adaptivity criteria are
checked, if all nodes of an element are within the defined region, the element is split and remeshed.
The criterion is used to refine the mesh in regions where it is difficult to predict which elements of the
model will be present, or move in to. It is commonly used in rubber seal analysis where small cavities
are filled by the deformation of a compressed seal.
If some elements could potentially move into two different regions, define two different components
for the same elements so that one component can be associated with each region.
3.4.3. Contact-Based Criterion

Two types of contact-based criteria are available for nonlinear adaptivity:
3.4.3.1. Number of Contacting Elements
3.4.3.2. Contact Surface Wear
3.4.3.1. Number of Contacting Elements

This criterion is defined for target elements only (as the component that bears the criterion consists of
target elements), but defines how solid elements underneath corresponding contact elements should
be split and remeshed. This criterion is defined by the number of contact elements which should be in
contact with each target element of a component. During the substep at which mesh nonlinear criteria
are checked, if the number of contact elements in contact with the target element is less than the
defined value, the solid element underneath the contact element is split and remeshed. Because the
solid elements are split, contact elements on the faces of the solid elements are regenerated as well.
This criterion is used to allow a contact region to follow the geometry of targets more accurately. If a
target has a large number of small fillets or round angles, or if it forms small cavities, splitting and mesh
refinement could make convergence more difficult. The desired number of elements may not be reached
when the solution is complete if the checking frequency is set too low. If the program detects that a
contact element is detaching from a target surface, the underlying solid elements will no longer be
split and refined, even if the desired number of elements has not been reached. Target elements with
this criterion applied are taken as reference elements and therefore cannot be split or refined. Exercise
caution when applying contact-based criteria on flexible-flexible boundaries and self-contact boundaries.
Should a particular target element have multiple contact-based criteria defined through different
components, the program uses the most strict criterion. For example, if the desired number of elements
is defined as 5 in component A and 7 in component B, the program uses 7 as the criterion for a target
element present in both components.
3.4.3.2. Contact Surface Wear

This criterion is defined for contact elements having surface wear, specified via the TB,WEAR command.
With this option, you define the critical ratio of magnitude of wear at the contact element to the average
depth of the solid element underlying the contact element (input as VAL1 on NLADAPTIVE). When
the amount of wear at a contact element exceeds this critical value, the nonlinear adaptivity criterion
is met and the mesh is morphed to improve the quality of the mesh.
During the mesh morphing process, the wear accumulated thus far is first applied and the nodal co-
ordinates are updated to reflect the material loss due to wear. Next, the mesh is morphed to improve
the quality. At the start of the subsequent analysis, the wear is initialized to zero and starts accumulating
anew.
Should a particular contact element have multiple contact wear-based criteria defined through different
components, the program uses the strictest criterion. For example, if the critical ratio of wear to under-
lying solid element depth is defined as 0.25 in component A and 0.5 in components B, the program
uses 0.25 as the criterion for a contact element present in both components.
The wear criterion for mesh nonlinear adaptivity cannot be combined with any other mesh nonlinear
adaptivity criterion.
For more information about using the wear-based criterion, see Improving Mesh Quality During Wear
in the Contact Technology Guide.
3.4.4. Mesh-Quality-Based Criterion

The element components chosen to define a mesh-quality-based criterion should include only the ele-
ments falling into the large-deformation region; otherwise, the criterion may cause a larger region than
necessary to be remeshed. Because the boundaries of the components cannot be remeshed, it is good
practice to make the boundaries as smooth as possible, like the boundaries of the model, materials,
element types, etc.
The mesh-quality-based criterion (NLADAPTIVE,,,MESH) has two options:

3.4.4.1. SHAPE Option
3.4.4.2. SKEWNESS Option
3.4.4.1. SHAPE Option

This criterion applies to structural 2-D plane element PLANE182. Mesh quality is defined by element
shape (NLADAPTIVE,,,MESH,SHAPE,Value). It works for all stress states options: plane stress, plane
strain, axisymmetric, and generalized plane strain. The mesh quality value is defined by the element's
maximum corner angle: when the angle equals or exceeds the specified threshold (set via NLADAPTIVE),
the element is identified as a seed element to be remeshed.
The recommended maximum corner angle is 150 to 175, although any positive value between 90 and
180 is valid. A larger value results in fewer remeshings but enables remeshing from a more distorted
original mesh. A maximum corner angle that is too large can introduce mapping errors, leading to re-
sidual forces that cannot be balanced in later substeps. A value that is too small causes unnecessary
meshing, or a new mesh that is not much better than the original mesh.
3.4.4.2. SKEWNESS Option

This criterion applies to structural 3-D solid element SOLID285, a linear tetrahedral element. Mesh
quality is defined by element skewness (NLADAPTIVE,,,MESH,SKEWNESS,Value) as:
where is the volume of the element under calculation and is the volume of the standard tetra-
hedral linear element inscribed in the same sphere as the element under calculation.
When the element under calculation has an ideal shape (that of a standard tetrahedral element),
and skewness = 0. When the element under calculation has the least ideal shape (that of a flat element),
Generating the New Mesh
and skewness =1. For the linear tetrahedral element, therefore, skewness is always between 0
and 1, with 1 being a flat element.
The skewness value serves as the threshold value for detecting an element to remesh. When an element’s
skewness is >= the specified threshold, that element is identified as a seed element to be remeshed.
The recommended skewness value is approximately 0.9 to 0.95. An excessively small skewness value
may lead to many unnecessary remeshings, and an excessively large value may cause remeshing to
occur too late for the subsequent substep to converge.
3.5. Specifying Criteria-Checking Frequency

Specify the frequency at which criteria (p. 66) for each component are checked during solution via the
NLADAPTIVE,,ON command.
The VAL1 parameter controls the checking frequency. If VAL1 is set to a positive value, the program
checks the mesh nonlinear adaptivity criteria every VAL1 substeps. If VAL1 is set to a negative value,
the program checks VAL1 number of times distributed evenly throughout the load step or defined
time interval. For the mesh-quality-based criterion and the contact-based criterion, it is good practice
to check the criteria at every two substeps. For other criteria, a negative value is suggested to avoid
over-refinement, as each splitting enlarges the model four or eight times for 2-D and 3-D, respectively.
Too many splittings, therefore, can hugely enlarge a model.
To modify the time range at which criteria checking occurs, use the VAL2 and VAL3 arguments.
Criteria checking does not guarantee that splitting and remeshing occurs in a given substep. A new
mesh is generated only if any element meets the criteria assigned to it. When splitting and remeshing
occurs, the new mesh is used in the subsequent substep.
Splitting or Remeshing Points

Because nonlinear adaptivity does not control the substep length (solution points), it cannot accurately
control the number of splitting or remeshing points.
When issuing defining frequency checking via an NLADAPTIVE,,ON,,,-n,StartTime,EndTime

command, splitting or remeshing may not occur between StartTime and EndTime if no solution
point falls between them. Fewer splits or remeshings may occur, even fewer than n, if the number
of solution points is less than n.
Conversely, the program may split or remesh n + 1 times if the solution has one point close to
StartTime and another close to EndTime. (More than n + 1 splits should not occur.) Splitting n
+ 1 times is more likely to occur when n is a small value.
When a new mesh is created due to nonlinear adaptivity, the following message (or similar) is issued
in the output file:
**** REGENERATE MESH AT SUBSTEP 7 OF LOAD STEP 1 BECAUSE OF NONLINEAR ADAPTIVE CRITERIA
**** NEW MESH HAS BEEN CREATED SUCCESSFULLY. CONTINUE TO SOLVE.
Loads and boundary conditions are mapped from the old mesh to the new mesh automatically.
3.6. Generating the New Mesh

The following methods are available for generating a new mesh:
3.6.1. Generating a New Mesh via Splitting and Morphing
3.6.2. Generating a New Mesh via General Remeshing
3.6.1. Generating a New Mesh via Splitting and Morphing

This method for generating a new mesh supports both 2-D and 3-D elements. Splitting occurs first for
mesh refinement (although for the contact-based criterion with wearing, only morphing is needed).
In 2-D meshes, mesh morphing occurs after mesh splitting. The morphing operation can also modify
elements that have not been split. The morphing process attempts to improve the element distortion
metrics by optimizing the metrics immediately following splitting. If the shape metrics of specific elements
cannot be improved without sacrificing the quality of the neighboring elements, then the element is
not changed via morphing. The morphing process is iterative and converges when a maximum number
of iterations (set automatically depending on problem size and element type) are reached or no further
element shape quality enhancement is possible. Morphing works by moving the nodes in the mesh
(except for the nodes on the boundary).
In 3-D tetrahedron splitting, cotangent-weighted Laplacian mesh smoothing and topology correction
(by 2-3, 3-2, 2-2, and 4-4 face swaps) occur automatically after splitting. 3-D mesh refinement is more
tolerant of large deformation and mesh distortion than the same 2-D process because of the additional
topology-correction step. As in the 2-D case, morphing in 3-D does not change node locations on the
boundary; however, topology correction may modify elements on the boundary.
When energy- and position-based criteria are used, solid elements are split directly and appropriate
transitional elements are generated around a split region to ensure compatible transition with the unsplit
regions. In such cases, parent elements within a component are split and the child elements are auto-
matically made part of the component. Parent elements are dissociated from the component and removed
from the simulation database during the splitting procedure. In this way, component information is
automatically transferred from parent to child elements during the splitting procedure. For more inform-
ation, see Geometry Details for Mesh Splitting (p. 23).
Elements supporting contact-based criteria are TARGE169, TARGE170, CONTA171, CONTA172, CONTA173,
and CONTA174. Mesh nonlinear adaptivity has the same restrictions for contact and target elements as
for rezoning.
For contact-based criteria that use the NUMELEM criterion option (NLADAPTIVE,,,NUMELEM), the can-
didate solid elements for splitting are selected indirectly. Nonlinear adaptivity criteria are applied to
components of target elements and the decision to split the corresponding contacts is dependent on
solution-based quantities at the specific substep at which criteria checking occurs. For example, consider
the following figure, showing a 2-D target-contact interface at a subset on which contact-based mesh
nonlinear adaptivity criteria are checked:
Figure 3.17: Rigid Target-Contact Interface
The mesh nonlinear adaptivity algorithm associates contact and target elements with each other using
pinball radius values. For two components, CM1 and CM2 (where CM1 is consists of target element T1,
and CM2 consists of both target elements T2 and T3), the following associations are made:
C1 C2 C3 C4 C5 C6
T1 Y Y Y Y - -
(CM1)
T2 - - - Y Y -
(CM2)
T3 - - - - Y Y
(CM2)
The program’s decision to split contact elements is determined by checking the total number of contact
elements associated with a single target element of a particular target component, and the user-defined
number of desired contact elements (NLADAPTIVE). The following commands assign the desired
number of contact elements to be 3 and 5 for individual target elements of CM1 and CM2, respectively:
nladaptive,CM1,add,contact,numelem,3
If the total number of contact elements assigned to a target element is smaller than the user-defined
desired number during a substep where mesh nonlinear adaptivity criteria are checked, splitting occurs.
If the total number of contact elements is greater than the user-defined desired number, no further
refinement is done.
A size check also exists for contact-based criteria that use the NUMELEM criterion option. The desired
size of contact elements associated with a particular target component is calculated by dividing the
size of the target element by the user-defined desired number of elements. For example, the desired
size for component CM1 in the previous example is (size of T1) / 3. If the individual contact element
size for elements associated with a target element during a substep where mesh nonlinear adaptivity
is checked is smaller than the desired size, no more refinement is done.
The NUMELEM criterion option for contact-based mesh nonlinear adaptivity is used primary for gap
filling simulation, such as a rubber seal simulations. As shown in the following figure, successive refine-
ments of a mesh reduces the maximum gap significantly.
Figure 3.18: Gap Reduction with Successive Mesh Refinement by Element Splitting
Besides size and number requirements, the decision to split an underlying solid element at a given
substep also depends on the relative penetration or gap status of the corresponding contact element
with respect to a previous reference substep, as shown in the following figure:
Figure 3.19: Contact-Status-Based Determination for Splitting
If the penetration increases (gap reduces), the contact element is moving toward the target, and
therefore the underlying solid element is split to estimate a smaller pinball radius and improve gap re-
duction. In other cases, the underlying solid element is not split.
Should the splitting violate the size or number criteria, it does not occur. For a split to occur, all three
criteria must be met in a substep where criteria checking occurs.
In certain cases, transitional elements can affect the size and number criteria. One such case occurs
when neighboring target elements belong to different components with different size criteria defined
via the NLADAPTIVE command. Consider the following simulation:
Figure 3.20: Effect of Transitional Element Generation on Size and Numbering Criteria
In this case, CM1 and CM2 are the two defined components. CM1 consists of target element T1, and
CM2 consists of both target elements T2 and T3. The following mesh nonlinear adaptivity commands
are issued:
Because T2 and T3 are of a much smaller size than T1, the size allowance of contact elements scoped
to CM2 is much smaller than that of CM1. In substep 1, contact elements scoped to both CM1 and CM2
are candidates for refinement. In substep 2, however, only contact elements scoped to CM2 are candid-
ates, while contact elements scoped to CM1 are not refined. Because transitional elements are generated
for compatibility, some contact elements scoped to CM1 may be refined as an indirect consequence of
refinements to the CM2 contacts. The program allows a small tolerance for the size criteria so that
transition regions do not become over-refined during splitting.
3.6.2. Generating a New Mesh via General Remeshing

For the mesh-quality-based criterion (NLADAPTIVE,,,MESH), general remeshing is applied to repair the
mesh quality. The regions to remesh are initialized by seed elements. For 3-D models, seed elements
have a skewness >= a specified threshold (NLADAPTIVE,,,MESH,SKEWNESS). For 2-D models, seed ele-
ments have a shape metric of maximum corner angle >= a specified threshold (NLADAPT-
IVE,,,MESH,SHAPE).
When the mesh-quality-based criterion threshold is reached at a particular substep of a loadstep during
a nonlinear adaptive solution, the program creates a source mesh (based on the deformed mesh) for
use by the remesher. The source mesh contains the seed elements, with additional elements included
based on the specified number of sculpting layers (p. 78). Using the source mesh, the remesher attempts
to generate a new mesh, or target mesh, of better quality. If the target mesh is better than the source
mesh, the solution continues using the new mesh.
Depending on the seed elements and sculpting layers, it is possible that the remeshing domains cover
the whole mesh or some partial mesh of the source model.
The following topics related to general remeshing are available:

3.6.2.1. Understanding Remeshing Regions and Domains
3.6.2.2. Optional Remeshing Controls
3.6.2.1. Understanding Remeshing Regions and Domains

A nonlinear adaptivity (NLAD) region is a group of elements which you can select or assign from geometry
parts or bodies.
A remeshing region is a group of elements from the source mesh, where the elements have unique
material- and element-component properties. The remeshing region is the atomic 2-D or 3-D remeshing
volume in the remeshing process; the interface surfaces between regions are enforced to a conformal
mesh.
An element in a remeshing region may belong to multiple NLAD regions, as shown in this figure:
Figure 3.21: NLAD Regions and Remeshing Regions
Remeshing regions are driven by your defined NLAD regions. Understanding the relationship between
NLAD regions and remesh regions is useful when modeling workarounds for self-contact penetra-
tion (p. 87) in 3-D models.
A remeshing domain is a grouping of elements, each connected by at least one element face in a 3-D
model, or by at least one element edge in a 2-D model.
For a 3-D model, no face connection exists between domains, but node or edge connections can exist.
For a 2-D model, no edge connection exists between domains, but node connections can exist.
A domain can contain multiple regions, composed of a grouping of elements, each connected by at
least an element face but having unique material- and element-component properties.
The following figure shows a 3-D model composed of six parts, naturally decomposed to six domains:
Figure 3.22: Understanding 3-D Domains
The two cubes in the figure have edge connections only, so they decompose into two domains for
remeshing because they have no face connection.
The following figure is a 2-D model composed of four domains, where interfaces between the domains
can be in contact, but no mesh connections (no conforming meshes) exist. Part 4 (P4) is composed of
4 regions (P4R1 through P4R4).
Figure 3.23: Understanding 2-D Domains
Remeshing domains are logical 2-D/3-D geometries composed of parts to remesh, whereas remeshing
regions are the effective and specific 2-D/3-D geometry parts to remesh. The program maintains the
interfaces between regions so that the source mesh material and element components are maintained.
Partial model remeshing is an option for minimizing the solution time. The meshing algorithm ensures
a conformal mesh between the remeshed regions and untouched regions.
Figure 3.24: Understanding 3-D Regions (p. 76) shows one 3-D domain consisting of three regions, and
Figure 3.25: Understanding 2-D Regions (p. 76) shows one 2-D domain consisting of four regions:
Figure 3.24: Understanding 3-D Regions
Figure 3.25: Understanding 2-D Regions
The program detects remeshing regions and domains according to the seed elements and the specified
number of sculpting layers. The elements to be remeshed will thus have the same element and mater-
ial properties as the seed elements. Depending on these seed elements and the specified number of
sculpting layers, it is possible that the remeshing domains cover the whole mesh or some partial mesh
of the deformed model during solution.
Partial model remeshing is an option for minimizing the solution time. The meshing algorithm ensures
a conformal mesh between the remeshed regions and untouched regions.
3.6.2.2. Optional Remeshing Controls

If desired, more granular control of the source mesh geometry is available via the NLMESH command.
The command's remeshing controls are global and apply to every remeshing throughout a loadstep of
the nonlinear analysis. For even more control of the remeshings within a loadstep, you can perform a
restart analysis by modifying the remeshing controls.
The following remeshing-control topics are available:

3.6.2.2.1. Boundary-Angle and Edge-Angle Control
3.6.2.2.2. Sculpting Layers Control
3.6.2.2.3. Global Sizing Control
3.6.2.2.4. Local Sizing and Gradient Control
3.6.2.2.5. Understanding the Remesh Log
3.6.2.2.6. Known Remeshing Limitations
3.6.2.2.7. Dealing with Remeshing Failure
3.6.2.2.1. Boundary-Angle and Edge-Angle Control

User-specified boundary-angle and edge-angle thresholds are available (NLMESH,BDRA and
NLMESH,AEDG, respectively).
The program detects the most appropriate mesh segmentations and remeshes specific 2-D or 3-D mesh
entities using a systematic bottom-up approach. Conformal mesh interfaces between regions are
guaranteed, and new nodes on exterior surface are guaranteed to be located on the exterior facets of
the source mesh.
The boundary angle (NLMESH,BDRA) is the outer normal vector angle from two adjacent facets, where
a facet is an element face (3-D) or an element edge (2-D).
Figure 3.26: 3-D Boundary Angle Between Two Adjacent Faces on an Exterior Surface
Figure 3.27: 2-D Boundary Angle Between Two Adjacent Edges on an Exterior Surface
For 3-D models, the edge angle (NLMESH,AEDG) is the outer normal vector angle from two adjacent
boundary edges in a 3-D patch.
Consider the following example 3-D model:
Figure 3.28: 3-D Edge Angle in a Segment
When the specified threshold value for the edge angle (NLMESH,AEDG) exceeds 25 degrees, the
remesher has more freedom to remesh. In this case, the highlighted feature may be lost after remeshing,
as it is no longer necessary for the node to be retained based on your input. The same applies to
boundary angles (NLMESH,BDRA). Too large a value (typically > 40) can result in a loss of certain features
that you had expected to retain after remeshing, and may affect solution convergence adversely.
3.6.2.2.2. Sculpting Layers Control

Use sculpting layers to detect remeshing regions starting from detected seed elements. Specifying la
arger number of layers results in relatively large regions containing more elements and causes segregated
regions to be merged. If the specified number of layers is large enough, the entire domain is remeshed
if it has at least a seed element detected. Using this control helps to avoid many tiny cavities in the
remeshing regions.
The following figure shows the relationship between the remeshing region, the seed elements, and the
specified number of sculpting layers:
Figure 3.29: Partial Remesh: Sculpting Remesh Regions
A generic approach to partial remeshing begins with one or two seed elements (usually highly distorted
elements). When layer = 0, the remeshing region is composed of seed elements only. By increasing the
number of sculpting layers (NLMESH,NLAY), the remeshing region becomes larger until it applies to
the entire model. The FEA meshing engine remeshes the regions and guarantees a mesh interface
conforming to untouched regions.
Partial remeshing enables:
• Remeshing as needed on the fly (that is, remeshing regions as necessary to reduce the solver’s compu-
tational overhead, and to reduce accuracy loss caused by mesh modifications).
• Adaptively changing local mesh sizing in different time phases of the simulation workflow.
3.6.2.2.3. Global Sizing Control

During remeshing, the average mesh size of the source model is detected and then applied to the target
mesh by default; as such, the target mesh has a uniform size by default without change in average
mesh density. The entire mesh nonlinear adaptivity process benefits, as it is unnecessary to add a signi-
ficant number of elements (requiring, in turn, more computational resources). It is possible, however,
to specify a global refining/coarsening factor (NLMESH,SRAT) to adjust mesh density in each remeshing
.
The program writes the average and worst element mesh-quality metrics to the log file, where
remeshing statistical data are available to help you make additional adjustments to the remeshing
control parameters.
The following figure illustrates the global sizing factor:
Figure 3.30: Global Sizing
A factor >1 coarsens the model source mesh, and <1 refines the source mesh.
The factor is the ratio of the average target mesh length over the average source mesh length. A specified
value of 0.5 refines the mesh and results in 8x the number of elements in the target mesh as compared
to the source mesh for 3-D. In actual usage, the final element number is also affected by remesh con-
straints such as specified boundary or edge angles, number of element or material components, contact
elements, boundary conditions or loads, and other factors.
Because the specified global sizing factor that you specify applies to all remeshings of a nonlinear
analysis within a loadstep, a small value (< 0.7) may eventually lead to an unnecessarily refined mesh
towards the end of the solution (depending on the initial 2-D/3-D model, the number of triggered
remeshings, and the physics of the nonlinear deformation during solution). To avoid unreasonable solve
times, therefore, carefully choose what value you specify for global sizing.
Typically, there is no need to coarsen the mesh during the analysis; however, if you wish to do so,
specify a value between 1 and 1.3. (A value > 1.3 can corrupt the target model due to excessive
coarsening and may cause errors during or after remeshing.)
3.6.2.2.4. Local Sizing and Gradient Control

As described in the following topics, 2-D remeshing enables more flexible mesh sizing and gradient
control than does 3-D remeshing:
3.6.2.2.4.1. 2-D Size Gradient Control
3.6.2.2.4.2. 3-D Local Sizing
3.6.2.2.4.1. 2-D Size Gradient Control
Options are available for 2-D remeshing to retain the size gradient from the source mesh (NLMESH,GRAD):
VAL1 = 0 does not maintain the mesh-size gradient but generates a uniform mesh in the
remeshing regions.
VAL1 = 1 generates a new mesh and retains the same local size as the source mesh.
VAL1 = 2 generates a new mesh and retains the same local size as the source mesh, but with
additional sizing compensation based on the element-size change during solution due to large-
deformation effects.
Considerations for specifying 2-D size gradient control:
Specify VAL1 = 0 with initial meshes which are not graded and have uniform sizing
throughout the nonlinear adaptivity remeshing component. This value induces slight
coarsening effects during large deformation. Therefore, using this option with global sizing
control (p. 80) to slightly refine the mesh for every remeshing gives better results.
Specify VAL1 = 1 when VAL1 = 2 cannot achieve better convergence for initial meshes that
are graded. In such cases, slight coarsening effects may be observed for high-deformation
regions, and global sizing control may be necessary. Avoid this option for uniform initial
meshes.
VAL1 = 2 is the default and recommended value for all initial meshes that are graded.
Typically, there is no need to use global sizing control with this option.
Figure 3.31: 2-D Mesh-Size Gradient Control Options
3.6.2.2.4.2. 3-D Local Sizing
In certain 3-D models, some surface feature edges (edges representing the geometric characteristics of
the deformed model) may have a much smaller length than average for the whole model. These retained
small feature edges generally lead to poor surface mesh quality in the new mesh.
If the source model has a surface mesh with very irregular edge lengths and the edges are used for
feature edges, you can use local sizing (NLMESH,LSRT) to try to improve the quality of the new mesh.
The following figure shows the mesh of a source (input) model where local sizing may be indicated:
Figure 3.32: 3-D Local Sizing Control
Without local sizing, the target mesh retains the original poor-quality facets or edges and eventually
impairs target-mesh quality. With local sizing enabled, the program generates a surface mesh based on
the local smallest edge length, as shown in (c). The gradient size is centered from the small edge of the
surface patch of interest. The local sizing ratio controls the gradient changes.
A value of 1 (default) disables local sizing during remeshing. The recommended value for implementing
local sizing is 1 < value < 2, depending on the initial model. A value very close to 1 (for example, 1.01)
may cause too much refinement on the surface facets. A suggested starting value to implement local
sizing, if needed, is 1.3.
3.6.2.2.5. Understanding the Remesh Log

Each remeshing operation generates a corresponding remeshing log in the solver output. The log
contains the input and output statistics for that remeshing. The statistical data can help you to make
any additional adjustments (if needed) to the remeshing controls (NLMESH).
Figure 3.33: Example FEA Remesh Log File (2-D)
Figure 3.34: Example FEA Remesh Log File (3-D)
The Source and Target columns contain the corresponding data before and after remeshing. For
example, in the 3-D remesh log, the worst element quality is shown based on element volume skewness
and element aspect ratio; the worst element IDs for the corresponding mesh quality metric appear in
parentheses (for example, e6497 indicates that the element ID is 6497). Skewness(Vol) is the element
volume skewness, ranging between 0 (perfect element) and 1 (highly distorted element). The Aspect
Ratio ranges from 1 (perfect element) to infinity (highly distorted element).
Skewness (Volume) is the element volume skewness, ranging between 0 (perfect element) and 1
(highly distorted element). The Aspect Ratio ranges from 1 (perfect element) to infinite (highly
distorted element).
The Remeshing result statistics section summarizes the remeshing domain/ or region de-
composition data, as follows:
nNode[New] -- New nodes generated in all remeshed regions

nElem[New] -- New elements generated in all remeshed regions
nElem[Eff] -- Effective source elements that are now remeshed (that is, deleted and replaced)
nElem[Src] -- Number of elements available to remesh from the source mesh
A partial remesh is indicated by nElem[Eff] < nElem[Src]. A whole-model remesh is indicated by

nElem[Eff] = nElem[Src].
The remesh log also shows the peak memory used and the elapsed time for the remeshing process.
3.6.2.2.6. Known Remeshing Limitations

Remeshing typically fails in either of the following cases:
3.6.2.2.6.1. Non-manifold Mesh Geometry
3.6.2.2.6.2. Region Self-Contact Penetration
3.6.2.2.6.1. Non-manifold Mesh Geometry
Arbitrary element selection in the remeshing region and partial remeshing with a decomposed element
group may create non-manifold FEA geometry, especially for 3-D cases where:
• An external edge may be shared by three or more external faces.
• An exterior node may have two or more shared loops. In 2-D models, an exterior node may be shared
by three or more external edges.
The following approaches are useful when dealing with non-manifold geometry:
• Modifying any of the remeshing control options (NLMESH). This approach may help remove the non-
manifold geometry issue in source meshes.
• Remeshing the whole NLAD model, body, or part (rather than just a portion of the model, body, or part)
• Redefining material or element components (insofar as possible)
3.6.2.2.6.2. Region Self-Contact Penetration
Self-contact penetration means that volume intersections exist in an atomic remeshing region (p. 74).
For 2-D remeshing, the program handles self-contact automatically.
Figure 3.35: 2-D Self-Contact
3-D remeshing failure occurs if this conditions exists at any time during the nonlinear adaptivity simu-
lation process. To prevent self-contact penetration, split the original NLAD region (a) into multiple regions
(b), as shown in this figure:
Figure 3.36: Workaround for 3-D Self-Contact Penetration
3.6.2.2.7. Dealing with Remeshing Failure

Remeshing failure at a given substep may occur in some nonlinear adaptivity problems, most often
because the mesh metrics of the worst element in the target mesh are worse than those of the worst
element in the source mesh.
In nonlinear FEA, even a single target element of poor quality in a critical region can cause the solution
to diverge. To ensure that convergence is not adversely affected in such cases, the program continues
solving using the old mesh and rejects the target mesh, as indicated in the output file at the remeshing
substep:
Although the program automates the solution process in the event of remeshing failure and lends it
some degree of fault tolerance, it is not an ideal situation. If many remeshing attempts in a nonlinear
solution process are rejected, the solution may diverge, especially when additional loads make the mesh
quality worse as the solution progresses. In such cases, a restart may be required with more relaxed
shape and/or skewness options (NLADAPTIVE,,,,SHAPE or SKEWNESS, respectively). To a lesser extent,
using the remeshing controls (NLMESH) to increase the number of sculpting layers, for example, may
also help to achieve successful remeshings after restart.
FEA automatic local remeshing is a complex operation. There may be several reasons why a remeshing
failure may be triggered. Two categories of remeshing failure exist:
3.6.2.2.7.1. Direct Remeshing Failure
3.6.2.2.7.2.Your Expectation of Target Mesh Quality Is Not Met
3.6.2.2.7.1. Direct Remeshing Failure
Direct remeshing failures include cases where the remesher fails to generate a new target mesh based
on the source mesh, indicated by errors in the remeshing log in the solver output. The errors can be
caused by:
• Unacceptable source mesh due to initial model setup
This situation occurs rarely, but is possible when any of the following conditions exist:
– Inconsistent element node orientations
– Invalid element-node ID references
– Invalid component-element ID references
• Complicated non-manifold FEA geometry (p. 87)
Due to the generic nature of the FEA local remeshing approach, non-manifold FEA geometry in
remeshing regions may occur often. The remesher can handle non-manifold FEA geometry, but may
have difficulty in exceptional cases where the source mesh has overly complicated non-manifold
geometry, especially in 3-D models.
3.6.2.2.7.2. Your Expectation of Target Mesh Quality Is Not Met
You may deem a given remeshing to be a failure because target mesh quality does not meet your ex-
pectations. In this case, consider the following:
• The quality of the source mesh at the remeshing substep may already be of sufficient quality.
In this case, perhaps no remeshing is required after all.
• Your remeshing requirements (specified via the mesh criterion options) may be too strict.
For most 2-D models, try defining a maximum corner angle threshold of 155 to 175. For most 3-D
models, try defining a skewness threshold of 0.87 to 0.97. These recommendations assume that you
check the mesh quality at every substep during the solution.
• The program may not be capable of generating a better quality mesh.
Various factors may constrain the remesher's ability to generate a better quality mesh: many material
or element components in the source mesh, tiny remeshing regions, boundary conditions or loads
in the remeshing regions, or contact elements in the remeshing regions. One or more of these con-
straints may adversely affect the quality of the new mesh, even though they may be required by the
physics in the model. In this case, try increasing the number of sculpting layers for remeshing
(NLMESH).
• More mesh-control refinement may be necessary.
In some cases, the target mesh quality may not improve even when using recommended thresholds
for the mesh criterion options. In such cases, try modifying other remeshing control parameters
(NLMESH) to obtain a better mesh. For example, if a coarse mesh suddenly starts to fill a narrow gap
with high element distortion, try to control the element sizing and achieve local remeshing control
by specifying fewer sculpting layers for remeshing, eventually improving mesh quality.
3.7. Convergence at Substeps with the New Mesh

After mesh splitting or general remeshing, solutions from the previous mesh are mapped to the new
mesh on the next substep after splitting or remeshing. Residual forces due to differences in the mesh
are applied along with the load increments of the substep. If there is convergence difficulty, the program
may first reduce the time increment for the substep in order to scale back the load to achieve conver-
gence. Then, if the minimum time increment for a substep is reached and the program still cannot
achieve convergence, it attempts to balance the residuals across two or more substeps. (The process
is the same as that described in Balancing Residual Forces (p. 36) for rezoning; however, it cannot be
controlled via the MAPSOLVE command.)
If a substep is introduced solely to balance residual forces, the following message (or similar) is written
to the output file:
*** LOAD STEP 1 SUBSTEP 26 NOT COMPLETED. CUM ITER = 84
*** BEGIN BISECTION NUMBER 2 NEW REBALANCE FACTOR INCREMENT= 0.50000
Substep information (rebalancing only) is not included in the monitor file (Jobname.mntr). Also,
nonlinear adaptivity criteria are not checked at the end of each substep during rebalancing; therefore,
the mesh remains unchanged.
Following the solution, the number of remeshings (if any) is reported in the output file. For example:
FINISH SOLUTION PROCESSING WITH 2 SUCCESSFUL REMESHING(S)
3.8. Controlling Mesh Nonlinear Adaptivity

When mesh nonlinear adaptivity is applied to problems which do not converge because of mesh distor-
tion, the mesh-quality-based (p. 68) criterion is necessary. The defined components for the criterion
should include all elements that undergo large deformations. The component boundaries should be as
smooth as possible, like the interfaces of various materials, element types and parts. The defined
skewness should be >= 0.9, and the defined maximum corner angle should range from 150 to 170 (al-
though other values are allowed). The checking frequency should generally be set to every two substeps.
If the applied loads or materials are very nonlinear, increase the checking frequency to every substep.
When using mesh nonlinear adaptivity to improve solution accuracy, the energy-based criteria is often
the best selection for general simulations. If you are unsure which parts of the model are critical regions
for mesh refinement, simply define an energy-based criterion for all solid elements in the model. A
default value of 1.0 for the energy criterion should improve most problems.
If you know which regions are critical and require refinement, define the solid elements in those regions
as components and create energy-based (p. 66) criteria for them, or use position-based (p. 67) criteria.
When mesh nonlinear adaptivity is applied to problems which would otherwise be unsolvable but where
the deformed mesh is not so distorted (for example, local deformations in buckling/bifuraction or rubber
seal problems), combinations of criteria are often required. The contact-based (p. 67) criterion should
Mesh Nonlinear Adaptivity Examples
be used only when solid elements touch target elements and more elements/nodes are necessary to
simulate details of contact boundaries and filling. The position-based (p. 67) criterion should be used
for refining elements moving in to particular regions (for example, small cavities). Without a fine enough
mesh and a sufficient number of degrees of freedom, the simulation might not accurately predict the
behavior of material moving into such regions. The energy-based (p. 66) criterion can be used to refine
elements at specific intervals by specifying a very low value or 0 as the minimum energy for splitting.
In any case, do not attempt refinement on a very distorted mesh, as the resulting mesh quality may be
worse than that of the original mesh. Morphing and/or topology correction can adjust for mesh distortion
to only a very limited extent.
3.9. Postprocessing Mesh Nonlinear Adaptivity Results

Mesh nonlinear adaptivity solution results should be processed as they are for rezoning results.
The displacements listed or plotted are not the total displacements from the beginning of the loading,
but the displacements from the last splitting or remeshing.
When listing solution results (SET,LIST), each substep starts with a new mesh and is marked MESH
CHANGED.
3.10. Mesh Nonlinear Adaptivity Examples

The following example problems are provided to help you understand how to apply mesh nonlinear
adaptivity:
3.10.1. Example: Rubber Seal Simulation
3.10.2. Example: Crack Simulation
3.10.3. Example: 3-D Metal Forging Simulation
3.10.4. Example: 2-D Metal Extrusion Simulation
3.10.1. Example: Rubber Seal Simulation

Following is the input for the problem discussed in Rubber Seal Simulation (p. 52):
/batch,list
/prep7
/com geometry paratmeters

rf = 1
yd = 6
yf = 12
xc = 0
yc = 12
disp = -4.0
w = 3
/com element types and size

el = w
et,1,182
keyopt,1,3,2
!keyopt,1,6,1
et,2,169
et,3,171
keyopt,3,9,0
keyopt,3,10,1
!keyopt,3,2,3
/com materials
c10=62.3584129
c01=-37.8485452
dd=1.E-03
tb,hyper,1,,2,mooney
tbdata,1,c10,c01,dd
mp,mu,2,0.0
r,2
/com create the model

k,1,xc,yc
k,2,xc+3*w,yc
k,3,w,0.0
k,4,w,yd
k,5,3*w,yd
rect,0,w,0,yd
rect,0,w,yd,yf
/pnum,line,1
l,1,2
l,3,4
l,4,5
lfillt,10,11,rf
/com create mesh

esize,el
mat,1
type,1
real,1
amesh,1,2
/pnum,elem,1
/pnum,node,1
nummrg,node
numcmp,node
/replot
/com the 1st contact paires

mat,2
real,2
type,2
esize,yf
lmesh,9
allsel,all
type,3
lsel,,,,6,7
nsll,,1
esln,,0
esurf
alls
/com the 2nd contact paires

real,3
type,2
lplot
esize,yf
lmesh,9,12
lsel,s,line, ,10,12
esll,s,1
esurf, ,reverse
allsel,all
lplot
type,3
lsel,,,,6
lsel,a,,,2
nsll,,1
esln,,0
esurf
alls
/com boundary condition
/com rigid punch

lsel,,,,9
nsll,,1
d,all,uy,disp
d,all,ux,0.0
alls
/com rigid die face

lsel,,,,10,12
nsll,,1
d,all,uy,0.0
d,all,ux,0.0
alls
/com left side

nsel,,loc,x,0
d,all,ux,0.0
alls
/com bottom
nsel,,loc,y,0
d,all,uy,0.0
alls
/com check the contact definition

cncheck
elist
finish
/solution
/com define nonlinear adaptive criterion

esel,,ename,,182
cm,solid,elem
allsel
nlad,solid,add,box,xyzr,-0.0,9,5,12
nlad,solid,on,,,-2
pred,off
rescontrol,,all,1,20
eresx,no
nlgeom,on
time,1
NSUBST,50,500,5
outres,all,all
solv
finish
3.10.2. Example: Crack Simulation

Following is the input for the problem discussed in Crack Simulation (p. 55):
/batch,list
/prep7
! MATERIAL PROPERTIES
et,1,183
keyopt,1,1,0
keyopt,1,6,1
MP,PRXY,1,0.3
MPTEMP,1,0,500 ! Define temperatures for Young's modulus
MP,EX,1,12E6,-8E3 ! C0 and C1 terms for Young's modulus
TB,BKIN,1,2 ! Activate a data table
TBTEMP,0.0 ! Temperature = 0.0
TBDATA,1,44E3,1.2E6 ! Yield = 44,000; Tangent modulus = 1.2E6
TBTEMP,500 ! Temperature = 500
TBDATA,1,29.33E3,0.8E6 ! Yield = 29,330; Tangent modulus = 0.8E6
TBLIST,BKIN,1 ! List the data table
/XRANGE,0,0.01 ! X-axis of TBPLOT to extend from varepsilon=0 to 0.01

TBPLOT,BKIN,1 ! Display the data table
! GEOMETRY
blc4,0,0,10,0.5
blc4,0,0,10,-0.5
lsel,s,loc,y,0
lsel,a,loc,y,0.5
lsel,a,loc,y,-0.5
lesize,all,,,20
lsel,inve
lesize,all,,,5
amesh,all
elist
allsel,all
nsel,s,loc,y,0
nsel,r,loc,x,0,7
nummrg,node
allsel,all
! COMPONENT
esel,all
cm,cm1,elem
allsel,all
esel,all
cm,cm2,elem
allsel,all
! LOADS
nsel,s,loc,x,0
d,all,all
allsel,all
nsel,s,loc,y,0.5
nsel,r,loc,x,10
f,all,fy,5500
allsel,all
nsel,s,loc,y,-0.5
nsel,r,loc,x,10
f,all,fy,-5500
allsel,all
nplot
finish
/solu
nlgeom,on ! large displacement analysis ON
outres,all,all ! all solutions are written
rescontrol,define,all,all ! write every substeps in a file
eresx,no ! no interpolation for the point of integration
time,1
nsubst,50,100,20
/nerr,,,,1 ! prevent the GUI for closing if no convergence
! NON LINEAR ADAPTIVITY
nlad,cm2,add,energy,mean,1
nlad,cm2,on,,,-3
allsel,all
solve
finish
! POSTPROCESSING
/post1
/out
set,last
nsel,s,loc,y,0
nsel,r,loc,x,0,7
esln,s,0,all
presol,s,eqv
finish
/exit
3.10.3. Example: 3-D Metal Forging Simulation

Following is the input for the problem discussed in 3-D Metal Forging Simulation (p. 58).
/batch,list
/config,nproc,1
/PREP7
!-----------geometry parameters--------------- !mm
cylinder_radius = 500
cylinder_offset = 1000
block_height = 1000
radius_fillet = 33
!---------inital meshing parameters------------
block_esize = 200
cylinder_esize = 200
!------------loading parameters----------------
cylinder_disp = -800
!------------NLAD parameters------------------
skw_ = 0.9 !skewness threshold
freq = 1 !NLAD frequency (1 means check every substep)
start_time = 0 !beginning time for NLAD interval
end_time = 0.95 !end time for NLAD interval
!------------remeshing parameters---------------
sculpt_layers = 4 !no. of sculpting layers
!******************material properties*****************
MP,EX,1,70e3 !aluminium material properties
MP,NUXY,1,0.33 !poisson's ratio
MP,MU,1,0 !coefficient of friction
TB,BISO,1,1 !bilinear isotropic material
TBDATA,1,20 !yield stress in MPa
TBDATA,2,7e3 !tangent modulus in MPa
!------------geometry creation-------------------
blc4,0,0,block_height,block_height,block_height
k,9,0,cylinder_offset,0
k,10,0,cylinder_offset,cylinder_radius
k,11,0,cylinder_offset+cylinder_offset,cylinder_radius
k,12,0,cylinder_offset+cylinder_offset,0
l,9,10
l,10,11
l,11,12
l,12,9
lfil,13,14,radius_fillet
al,13,17,14,15,16
vrotat,7,,,,,,9,12,90
!---------element types & settings-----------

et,1,285
et,2,170
et,3,173
keyo,3,10,2 !update contact stiffness every iteration
!-------------general meshing----------------
type,1
mat,1
real,1
esize,block_esize
vmesh,1
!-------------contact pair 1----------------
real,2
!---------------target elements--------------
type,2
mat,2
asel,s,area,,8,10
aesize,all,cylinder_esize
amesh,all
alls
!---------------contact elements-----------
type,3
mat,1
asel,s,area,,4
nsla,s,1
esln
esurf
alls
!--------------create components-----------
esel,s,ename,,285
cm,comp1,elem !create NLAD component
alls
!-----boundary conditions & loading-------
asel,s,area,,5,6
nsla,s,1
d,all,ux,0.0
alls
asel,s,area,,1,2
nsla,s,1
d,all,uz,0.0
alls
asel,s,area,,3
nsla,s,1
d,all,uy,0.0
alls
asel,s,area,,7,12
nsla,s,1
d,all,uz,0.0
d,all,ux,0.0
d,all,uy,cylinder_disp
alls
fini
/SOLU
!--------------general solution settings--------
nlgeom,on
eresx,no
outres,all,all
!---------------NLAD settings-------------------!check NLAD parameters section above for values
nlad,comp1,add,mesh,skew,skw_ !nlad with mesh-quality-based criterion
nlad,comp1,on,,,freq,start_time,end_time
!------------remeshing settings--------------- !check remeshing parameters section above for values
nlmesh,nlay,sculpt_layers
!---------------step settings-------------------
time,1
nsubst,100,10000,10
alls
solve
fini
!---------------POSTPROCESSING-------------------------
/POST1
set,list
fini
/exit
3.10.4. Example: 2-D Metal Extrusion Simulation

Following is the input for the problem discussed in 2-D Metal Extrusion Simulation (p. 61).
/batch,list
/config,nproc,1
/PREP7
h1=19.5
b1=45
h2=6.5
b2=22.5
b3=5
h3=17
el=h1/8
et,1,182
keyopt,1,3,5
keyopt,1,6,1
mp,ex,1,1.0e+6
mp,nuxy,1,0.3
tb,biso,1,
tbmodif,2,1,8.0e2
tbmodif,3,1,1.0e4
/com --- Rigid target

k,1,0,h1
k,2,b1,h1
k,3,b1+b2,h2
k,4,b1+b2+b3,h2
k,5,b1+b2+b3,h3
l,1,2
l,2,3
l,3,4
l,4,5
LFILLT,1,2,5, ,
LFILLT,2,3,5, ,
/pnum,line,1
/com --- Rectangular block

k,10,0,0
k,11,b1,0
k,12,b1,h1
k,13,0,h1
l,10,11
l,11,12
l,12,13
l,13,10
lfillt,8,9,el
al,7,8,11,9,10
esize,el
real, 1
mat, 1
type, 1
amesh, 1
/com --- Element type definitions for contact pair

mp,mu,2,0.0
r,2
et,2,169
et,3,171
keyopt,3,9,0
keyopt,3,10,2
/com --- Mesh target surface

mat, 2
real, 2
type, 2
lmesh,1,6
/com --- Create contact elements

type,3
real, 2
lsel, s, line, , 8,9
lsel, a, line, , 11
nsll,,1
esln,,0
esurf
alls
/com --- Apply Constraints
nsel,s,loc,y
d,all,uy,0.0
alls
lsel,s,line,,1,6
nsll,,1
d,all,all,0.0
alls
nsel,s,loc,x
d,all,ux,30
alls
esel,s,ename,,182
cm,c1,elem !create NLAD component
alls
fini
/SOLU
nlgeom,on
eresx,no
pred,off
outres,all,all
time,1
NSUBST,20,1000,5
alls
gsgdata,2,0,0,0,0
gsbdata,lfiber,0,rotx,0,roty,0
gslist,geometry
gslist,bc
alls
!-----Nonlinear Adaptive Region

cmsel,all
nlad,c1,add,mesh,shape,155 !nlad with mesh-quality-based criterion
nlad,c1,on,,,1
nlmesh,nlay,100 !no. of sculpting layers

nlmesh,grad,0 !option for mesh gradient control
nlmesh,srat,0.9 !control global sizing of new mesh
nlad,all,list,all
nlmesh,list
alls
SOLVE
fini
/POST1
set,list
fini
/exit
Chapter 4: 2-D to 3-D Analysis
It is sometimes necessary to extend 2-D nonlinear finite element results to a corresponding extruded
3-D body such that the solution can continue based on the 3-D model.
For example, in a tire analysis, the 2-D axisymmetric tire-inflation results must be extended to an extruded
3-D tire model before a footprint analysis can be performed.
The 2-D to 3-D analysis capability extrudes (EEXTRUDE) a 2-D deformed mesh to a new 3-D mesh. The
program updates the database as necessary, generates contact elements if needed, and transfers
boundary conditions, loads and nodal temperatures from the 2-D mesh to the extruded 3-D mesh. All
solved variables (node and element solutions) are then mapped (MAP2DTO3D) to the new 3-D mesh
automatically.
The following topics related to 2-D to 3-D analysis are available:

4.1. Benefits of 2-D to 3-D Analysis
4.2. Requirements for a 2-D to 3-D Analysis
4.3. Overview of the 2-D to 3-D Analysis Process
4.4. Performing a 2-D to 3-D Analysis
4.5. 2-D to 3-D Analysis Restrictions
4.1. Benefits of 2-D to 3-D Analysis

Mapping solution variables from a 2-D mesh to an extruded 3-D mesh allows you to perform a multistage
nonlinear analysis. For example, in a tire analysis, 2-D axisymmetric inflation results are required for a
subsequent 3-D footprint analysis.
In effect, you can continue with a 3-D analysis on the extruded body after mapping solution results
from the 2-D body.
4.2. Requirements for a 2-D to 3-D Analysis

All multiframe restart files must be available.
Following are the 2-D elements and the materials, loads, and boundary conditions that can be used for
2-D to 3-D analysis:
Support Category Requirements

Solid elements • PLANE182 -- Plane strain and axisymmetric states of stress only
• PLANE183 -- Plane strain and axisymmetric states of stress only
Enhanced strain formulation is not supported.

Reinforcing • REINF263 -- Plane strain and axisymmetric states of stress only
elements
2-D to 3-D Analysis

Contact • TARGE169
elements
KEYOPT (1) = 0
KEYOPT (2) = 0, 1, 3, 4
KEYOPT (3) = 0
KEYOPT (4) = 0, 1, 2, 3
KEYOPT (5) = 0, 1, 2, 3, 4
KEYOPT (7) = 0, 1, 2, 3
KEYOPT (8) = 0
KEYOPT (9) = 0, 1, 2, 3, 4
KEYOPT (10) = 0, 2
KEYOPT (11) = 0
KEYOPT (12) = 0, 1, 2, 3, 4, 5, 6
KEYOPT(14) = 0
• TARGE170
KEYOPT (1) = 0
KEYOPT (2) = 0, 1
KEYOPT (4) = 0, 2, 3
KEYOPT (5) = 0, 1, 2, 3, 4
KEYOPT (7) = 0, 1, 2, 3
KEYOPT (8) = 0
KEYOPT (9) = 0, 1, 2, 3, 4
KEYOPT (10) = 0, 2
KEYOPT (11) = 0
KEYOPT (12) = 0, 1, 2, 3, 4, 5, 6
KEYOPT(14) = 0
Contact pair • Rigid-flexible -- 2-D target elements (line) are extruded in 3-D as tangent
behavior planes or as annuli in axisymmetric extrusion. The extrusion is always
planar in plane strain extrusion.
• Pilot nodes in 2-D are retained as pilot nodes in 3-D.
• Flexible-flexible contact.
• Self-contact.
Materials • Most structural materials are supported. Exceptions are: CAST (cast iron),
CONCR (concrete), MPLANE (microplane), SMA (shape memory alloy),
PRONY (viscoelastic materials) and SWELL (swelling).
• For materials associated with user-defined state variables (TB,STATE), it

may be necessary to issue the MAPVAR command. The defined size of
state variables must be such that full 3-D descriptions of stress and strain
tensors can be accommodated (that is, the defined stress and strain tensors
must be able to possess six independent components).
Overview of the 2-D to 3-D Analysis Process

Loads and • Displacements, forces, pressures, and nodal temperatures (BF,TEMP).
boundary
conditions • Loads applied on surface-effect elements (such as SURF153) are not
(BCs) supported.
• Tabular displacements and forces are supported.
• Tabular pressures that are functions of time only are supported.
Files • .rdb, .rst, .ldhi, .ist, and .cdb.
The EEXTRUDE command documentation shows the topological mapping of 2-D elements (solid, contact,
and target) into specific 3-D elements.
4.3. Overview of the 2-D to 3-D Analysis Process

The 2-D to 3-D analysis process involves the following general tasks:
1. Determine the load step and substep (p. 103) in the 2-D model at which extrusion should occur.
2. Initiate the 2-D to 3-D analysis process (p. 104).
3. Perform the extrusion (p. 104) and map boundary conditions and load.
4. Map displacements and solution variables (p. 105) automatically from the 2-D mesh to the new 3-D
mesh.
5. Continue the 3-D analysis (p. 105) using the data in the .ist files (INISTATE,READ) along with new
applied loads and boundary conditions (if applicable) on the deformed mesh.
The entire 2-D mesh is used for the extrusion process; therefore, only one MAP2DTO3D command
block can be used at a given loadstep and substep.
The following topics related to understanding the general 2-D to 3-D analysis process are available:
4.3.1. Overview of the 2-D to 3-D Analysis Process Flow
4.3.2. Key Commands Used in 2-D to 3-D Analysis
4.3.1. Overview of the 2-D to 3-D Analysis Process Flow

The following flowchart illustrates the general 2-D to 3-D analysis process:
2-D to 3-D Analysis
Figure 4.1: 2-D to 3-D Process Flow
For information about the commands shown in the flowchart, see Key Commands Used in 2-D to 3-D
Analysis (p. 102)or the documentation for a given command in the Command Reference.
4.3.2. Key Commands Used in 2-D to 3-D Analysis

Following is a description of key commands used in the 2-D to 3-D analysis process and provides sup-
plemental information to the 2-D to 3-D analysis process flowchart (p. 102).
Command Description 2-D to 3-D Analysis Comments

/CLEAR Clears the Always clear the database first, before reentering the
database solution processor (/SOLU) and starting the 2-D to 3-D
analysis process.
MAP2DTO3D,START
Initiates the When you initiate 2-D to 3-D analysis, the program verifies
2-D to 3-D that the necessary files (.rdb, .rst, .rxxx, and .ldhi)
analysis exist for the specified substep and rebuilds the data
environment at that substep.
All nodes are updated to the deformed geometry in

preparation for extrusion.
Performing a 2-D to 3-D Analysis
Command Description 2-D to 3-D Analysis Comments

To prevent the loads and boundary conditions from
being generated on the 3-D model, specify the
MAP2DTO3D command’s NOBC option.
EEXTRUDE Extrudes The entire 2-D mesh is selected automatically for
the 2-D extrusion. Partial mesh extrusion is not supported.
mesh to a
3-D mesh. In the extrusion phase of a 2-D to 3-D analysis, the
Deletes the command generates the 3-D contact elements. The
2-D rigid command also regenerates the loads, boundary
targets and conditions, and temperatures for the extruded 3-D
regenerates mesh.
the 3-D
rigid
targets.
Maps the
loads,
temperatures,
and
boundary
conditions
from the
2-D mesh
to the
corresponding
3-D mesh.
MAP2DTO3D,FINISH
Maps node and After extrusion, this command maps the solved nodal and
element element solutions from the 2-D (distorted) mesh to the
solutions extruded 3-D mesh.
4.4. Performing a 2-D to 3-D Analysis

The following steps describe the general process for performing a 2-D to 3-D analysis:
4.4.1. Step 1: Determine the Substep to Initiate
4.4.2. Step 2: Initiate the 2-D to 3-D Analysis
4.4.3. Step 3: Extrude the 2-D Mesh to the New 3-D Mesh
4.4.4. Step 4: Map Solution Variables from 2-D to 3-D Mesh
4.4.5. Step 5: Perform an Initial-State-Based 3-D Analysis
4.4.1. Step 1: Determine the Substep to Initiate

It is typical in a 2-D to 3-D analysis to use the results at the end of the 2-D analysis as the starting point
for the 3-D extrusion. You can, however, choose any substep to initiate the 2-D to 3-D analysis process
if the restart files for that substep exist.
When you have determined a suitable substep, proceed to Step 2: Initiate the 2-D to 3-D Analysis (p. 104).
2-D to 3-D Analysis
4.4.2. Step 2: Initiate the 2-D to 3-D Analysis

2-D to 3-D analysis is based on a new model with a higher dimension (3-D), extruded from a specific
substep of a lower dimensional (2-D) model solution; therefore, the 2-D to 3-D analysis process must
begin with a clean database.
To initiate a 2-D to 3-D analysis:
1. Clear the database (/CLEAR,NOSTART).
2. Reenter the solution processor (/SOLU).
3. Initiate 2-D to 3-D analysis, specifying the load step and substep (p. 103) at which 2-D to 3-D analysis should
occur (MAP2DTO3D,START,LDSTEP,SBSTEP or MAP2DTO3D,START,LDSTEP,SBSTEP,NOBC).
Proceed to Step 3: Extrude the 2-D Mesh to the New 3-D Mesh (p. 104).
4.4.3. Step 3: Extrude the 2-D Mesh to the New 3-D Mesh
Extrude the 2-D mesh to the 3-D mesh (EEXTRUDE).
The following figures illustrate how extrusion generates 3-D meshes from a plane strain and an
axisymmetric 2-D mesh, respectively:
Figure 4.2: 2-D Plane Strain to 3-D Solid Extrusion
Figure 4.3: Axisymmetric to 3-D Solid Extrusion
Extrusion preserves the 2-D mesh topology on the generating plane and replicates it through the depth
of the extruded body.
2-D to 3-D Analysis Restrictions
Contacts, Targets, and Boundary Conditions
The extrusion process generates the 3-D contact and target elements with the solid elements. All
2-D rigid target elements are deleted, and corresponding 3-D rigid target elements are generated.
When you issue the MAP2DTO3D,START,LDSTEP,SBSTEP command followed by the EEXTRUDE

command, boundary conditions, pressure loads, applied nodal forces, applied nodal displacements,
and applied nodal temperatures are transferred automatically from the 2-D mesh to the corresponding
entities in the extruded 3-D mesh. (If you specify the MAP2DTO3D command’s NOBC option, none
of those attributes except for the nodal temperatures transfer to the extruded 3-D mesh.)
After extrusion, proceed to Step 4: Map Solution Variables from 2-D to 3-D Mesh (p. 105).
4.4.4. Step 4: Map Solution Variables from 2-D to 3-D Mesh

Issue the MAP2DTO3D,FINISH command to map the solved node and element solutions automatically
from the original 2-D mesh to the new 3-D mesh.
No residual balancing is done and only the solution variables are mapped from the 2-D mesh to the
extruded 3-D mesh.
After mapping solution variables to the 3-D mesh, proceed to Step 5: Perform an Initial-State-Based 3-
D Analysis (p. 105).
4.4.5. Step 5: Perform an Initial-State-Based 3-D Analysis

After successfully mapping the solved variables from the old 2-D mesh to the new 3-D mesh, you can
continue your 3-D analysis by reading in the 2-D to 3-D results as initial state conditions (INISTATE,READ)
and adding new loads for the 3-D analysis.
For more information, see Initial State in the Mechanical APDL Advanced Analysis Guide.
4.5. 2-D to 3-D Analysis Restrictions

The following limitations apply to a 2-D to 3-D analysis:
• You cannot use remeshing commands within the 2-D to 3-D analysis environment (after MAP2DTO3D,START
and before MAP2DTO3D,FINISH). The incompatible commands include REMESH,READ, REMESH,SPLIT, and
AREMESH.
• Axisymmetric extrusion with zero offset of nodes about the Y axis is not supported.
• 2-D plane stress (KEYOPT(3) = 0 or KEYOPT(3) = 3) and generalized plane strain (KEYOPT(3) = 5) elements
are not supported.
• Layered solid elements are not supported.
• Enhanced strain element technology is not supported.
• 2-D to 3-D analysis is not available in Distributed ANSYS.
Chapter 5: Initial State
The term initial state refers to the state of a structure at the start of an analysis. Typically, the assumption
is that the initial state of a structure is undeformed and unstressed; however, such ideal conditions are
not always realistic.
The initial state capability allows you to define a nontrivial state from which to start an analysis. For
example, you can specify an initial stress or strain state for a structure.
The data types supported by initial state are:
• Initial stress (p. 108)

• Initial strain (p. 109)
• Initial plastic strain (p. 110)
• Initial creep strain (p. 110)
• Initial void ratio and pore pressure (p. 111)
Initial state support is also available in Distributed ANSYS.
The following topics concerning initial state are available:

5.1. Specifying and Editing Initial State Values
5.2. Initial State Application
5.3. Initial State File Format
5.4. Using Coordinate Systems with Initial State
5.5. Initial State Limitations
5.6. Example Problems Using Initial State
5.7. Writing Initial State Values
5.1. Specifying and Editing Initial State Values

The initial state capability is based on the INISTATE command. The command allows you to specify
and edit your initial state data. You can also use it to read externally supplied initial state values from
a comma-delimited file, or to export existing values (p. 127) in the same format.
Initial state application is element-based and available only for current-technology elements. Initial state
is applied to the elements as either an integration-point or material-based load, as follows:
• Layered elements
You can apply initial state to any combination of layer, section integration point and/or element in-
tegration points.
• Beam elements
You can apply initial state to combinations of cell number, section integration and element integration
points.
• All other elements
Initial State
Applying initial state is based on the element integration point only.
You can also apply an initial state to elements based on the material ID number (for the entire element).
5.1.1. Node-Based Initial State

Initial state application can also be node-based, a capability available in current-technology elements
only.
• Layered elements
You can apply an initial state to each layer at every node within the element. Initial state values applied
at nodal positions are interpolated within each layer to the corresponding element integration points.
• Beam elements
You can apply an initial state to each cell number at every node within the element. Initial state values
applied at nodal positions are interpolated within each cell to the corresponding element integration
points.
• All other elements
For all other element types, the initial state is applied at each node within the element.
Node-based initial state with user-defined data types can be used with field-dependent material prop-
erties. For more information, see Understanding Field Variables in the Material Reference.
For more information, see Node-Based Initial Strain Application (p. 111) and Example: Node-Based Initial
Strain (p. 123).
5.2. Initial State Application

This section provides typical cases for applying an initial state, as follows:
5.2.1. Initial Stress Application
5.2.2. Initial Strain Application
5.2.3. Initial Plastic Strain Application
5.2.4. Initial Creep Strain Application
5.2.5. Initial State with State Variables Application
5.2.6. Node-Based Initial Strain Application
5.2.7. Initial Pore Pressure and Void Ratio Application
5.2.8. Function-Based Initial State
5.2.1. Initial Stress Application

Although initial stress is element-based, the structure of the INISTATE command is element-type-inde-
pendent.
For continuum or link elements, apply initial stress according to the specific element integration point.
For layered elements, apply initial stress based on the layer number, the layer integration point or the
element integration point. Beams allow you to apply initial stress based on the cell number, the section
integration point, and/or the element integration point.
Initial State Application
For reinforced elements, you can assign different values of initial stress to different reinforcings within
the same element.
For coupled-field elements CPT212, CPT213, CPT215, CPT216, and CPT217, the initial stresses to be applied
are Biot’s effective stress. They are automatically written out when the output stress option is specified
(INISTATE, WRITE, , , , , ,S).
The following example input shows how initial stress can be applied in such cases:
Constant Initial Stress on the Whole Model
inistate,defi,,,,,100,200,300,400,500,600
Apply Constant Stress of SX=100 On Beam Element 1

inistate,defi,1,,,,100
Apply a Stress of SX=33.333 at Elem Integration Pt 3 within Element 2

inistate,defi,2,3,,,33.3333
Apply Constant Stress Of SX=200 in Cell 2 For All Selected Beam Elements
inistate,defi,,,2,,200
Apply Constant Stress Of SX=200 For All Beams In A Model

And Wherever There Is Material=3
inistate,set,mat,3
inistate,defi,,,,,200
Apply a Stress of SX=100,SY=200,SXY=150 for Layers 1,3,5 and

SX=200,SY=0 for Layers 2,4,6 in a Layered Shell Element. Layer
1,3,5 have material 1 and Layer 2,4,6 have material 2.
inistate,defi,,,1,,100,200,150
OR
inistate,set,mat,1
inistate,defi,,,,,100,200,150
inistate,set,mat,2
Apply a Stress of SX=33.333 at Reinf 1 for all elements

inistate,defi,,,1,,33.3333
Also see Example: Initial Stress (IST File) (p. 115) and Example: Initial Stress (INISTATE Command) (p. 116).
5.2.2. Initial Strain Application

The initial stress application (p. 108) example can be extended for initial strain by simply changing the
data type to EPEL, as shown:
! Constant Initial Strain on the Whole Model
inistate,set,dtyp,epel
inistate,defi,,,,,0.1,-0.01,-0.01
!Apply a Constant Strain of EPEL X=0.01 On Beam Element 1

inistate,defi,1,,,,0.01
!Apply a Strain of EPEL X=0.01 at Elem Integration Pt 3 within Element 2

!Apply a Constant Strain Of EPEL X = 1E-6 in Cell 2 For All Selected Beam Elements
inistate,defi,,,2,,1E-6
!Apply a Constant Strain Of EPEL X=1E-3 For All Beams In A Model
Initial State
!And Wherever There Is Material=3

inistate,set,mat,3
inistate,defi,,,,,1E-3
! Apply EPS X = 0.1, EPS Y = -0.02, EPS Z = -0.02, for Layers 1,3,5 and
! EPS X = 0.2, for Layers 2,4,6
! Layer 1,3,5 have material 1 and Layer 2,4,6 have material 2.
inistate,set,mat,1
inistate,defi,,,,,0.1,-0.02,-0.02
inistate,set,mat,2
inistate,defi,,,,,0.2
Also see Example: Initial Strain (p. 116).
5.2.3. Initial Plastic Strain Application

The initial stress application (p. 108) example can be extended for initial plastic strain by simply changing
the data type to EPPL, as shown:
! Constant Initial Plastic Strain and Stress on the Whole Model
inistate,set,dtyp,eppl
inistate,set,dtype,s
! Apply a Strain of EPEL X=0.01 at Elem Integration Pt 3 within Element 2.

! Here it is assumed that the initial stress is zero.
! Apply accumulated equivalent plastic strain.

inistate,set,dtyp,pleq
! Apply EPS X = 0.1, EPS Y = -0.02, EPS Z = -0.02, for Layers 1,3,5 and
! EPS X = 0.2, for Layers 2,4,6
! Layer 1,3,5 have material 1 and Layer 2,4,6 have material 2.
inistate,set,dtype,eppl
inistate,set,mat,1
inistate,set,mat,2
Also see Example: Initial Plastic Strain (p. 117).
5.2.4. Initial Creep Strain Application

The initial stress application (p. 108) example can be extended for initial creep strain by simply changing
the data type to EPCR, as shown:
! Apply creep strain, plastic strain, accumulated equivalent plastic strain, stress on
! all the selected elements
inistate,set,dtyp,epcr
inistate,set,dtyp,epeq
inistate,set,dtype,s
Also see Example: Initial Creep Strain (p. 118).
Initial State Application
5.2.5. Initial State with State Variables Application

To use the initial state capability with state variables via the INISTATE command, simply change the
data type to SVAR, as shown:
! Apply initial state – state variables.
! This fictitious svar example contains 7 components:
! The 1st component is accumulated equivalent plastic strain.
! Components 2-7 are plastic strains values.
! at all the selected elements
inistate,set,dtyp,svar
inistate,defi,,,,,0.005,0.1,-0.02,0.02,0,0,0
The INISTATE command does not consider the coordinate systems of quantities stored within the state
variables. It is therefore your responsibility to account for the transformations.
Also see Example: Initial Plastic Strain with State Variables (p. 120).
5.2.6. Node-Based Initial Strain Application

As shown below, a node-based initial state can be applied to all nodes or to a selected subset of nodes.
Layer numbers can also be specified.
! Enable Node-Based Initial State
inis,set,node,1
! Apply elastic strains at all nodes in layer 1 and 3
inistate,defi,all,,1,,0.005
! Apply a different elastic strain at all nodes in layer 2
! Apply zero elastic strain at node 10
inistate,defi,10,,all,,0.000
! Apply zero elastic strain at node selection
nsel,s,loc,x,0
inistate,defi,all,,all,,0.000
Also see Example: Node-Based Initial Strain (p. 123).
5.2.7. Initial Pore Pressure and Void Ratio Application

Initial pore pressure and void ratio are available for the coupled pore-pressure elements (CPTnnn) only:
CPT212, CPT213, CPT215, CPT216, and CPT217. Apply initial pore pressure and void ratio on coupled
pore-pressure elements by changing the data type to PPRE.
! Apply to all the selected elements
porepr=69
inistate,set,dtyp,ppre
inistate,defi,,,,,porepr
! Apply to all the selected elements

vratio=0.4
inistate,set,dtyp,void
inistate,defi,,,,,vratio
Also see Example: Initial Pore Pressure and Void Ratio (p. 124).
5.2.8. Function-Based Initial State

Function-based initial state is a method for applying data as a function of internal variables. Three options
are available: a linear function in X coordinates (LINX), a linear function in Y coordinates (LINX), or a
Initial State
linear function in Z coordinates. The method is available for both node-based and element integration-
point-based initial state.
The coordinates used to evaluate the value at a given location are based on initial coordinates in the
load step. For user-defined field variables, the coordinates are the initial ones queried via the NLIST (or
*GET) command. For a rezoning or linear perturbation model (or after issuing an UPGEOM command
after a load step) where the coordinates change, the coordinates used in the subsequent load step are
the updated coordinates (which become the initial coordinates for the current load step). As before, the
coordinates used can be queried if necessary (NLIST or *GET). For other non-user-defined field variables
(such as initial stress or strain), function-based initial state is evaluated only at the first substep in the
first load step, and only the initial coordinates are used.
For higher-order elements, the initial state values at the midside nodes are evaluated by averaging the
coefficients of the function applied at the corner nodes. A single element must have the same function
type at all nodes in the element.
Function-based initial state can also be applied if needed in a user-defined coordinate system. The co-
ordinates needed to evaluate the initial state data are transformed to the user-defined coordinate system
before the evaluation process.
Example 5.1: Function-Based Initial State in a User-Defined oordinate System

! Apply linearly varying porepressure in the Y direction
p0=1e3
psl=1.3
inis,set,data,func
inis,set,dtyp,ppre
! Select a subset of elements
esel,s,elem,,1,100
local,11,0,0,0,0,0,0,30
! Change coordinate system if needed
inis,set,csys,11
inis,defi,all,,,,LINY,p0,ps1
Also see Example: Function-Based Initial State (p. 126).
5.3. Initial State File Format

Although you can use the INISTATE command repeatedly to assign explicit values to various items,
creating an external file simplifies the process.
You can create a standalone initial state file to be read into your analysis via an INISTATE,READ command.
The file format must be comma-delimited ASCII, consisting of individual rows for each stress item. Each
of the rows consists of columns separated by commas. Your columns delineate the integration point(s)
for the specific elements.
See Integration Point Locations in the Mechanical APDL Theory Reference for more information about
the number and location of available element integration points. Also see Element Library in the
Mechanical APDL Theory Reference for a listing of the integration points for each specific element.
The number of section integration points for beams and cells is dependent upon the associated user
input. One element ID number can be repeated on successive lines to specify different stresses at dif-
ferent integration points.
Each line of the initial stress file has 10 columns, as follows:
• The element ID Number
Initial State Limitations
• The element integration point (for standard elements)
• The layer (for layered elements) or the cell number (for beams)
• The section integration point (for beams and shells only)
• The six stress/strain components
Any of the parameters for element ID, element integration point, layer number, cell number, or section
integration point can be set to ALL. For example,
1,all,all,all, 100, 0, 0, 0, 0, 0
applies an equal stress of SX = 100 to all integration points or layers of the element ID = 1.
This input line

all,all,all,all, 100, 0, 0, 0, 0, 0
applies an equal stress of SX = 100 to all integration points or layers to all of the selected elements.
You can provide additional parameters via the /ATTR,VALUE line in the .IST file. Supported parameters
are /CSYS and /DTYP.
Specify /CSYS,VALUE to set the coordinate system to be used for the subsequent data supplied in your
.IST file. The default coordinate system is the global Cartesian system.
You can apply initial strain in a similar manner by including /DTYP,EPEL before the actual initial-
state/initial-strain date. For example,
/dtyp,epel
all,all,all,all, 0.1, 0, 0, 0, 0, 0
applies an initial strain of ex = 0.1 for all elements in the database.
You can insert comments and other non-analysis information in the .IST file by preceding them with
an exclamation mark (!).
5.4. Using Coordinate Systems with Initial State

The INISTATE command provides options for specifying data in coordinate systems other than the
material and element coordinate systems. To define the coordinate system, issue this command:
INISTATE,SET,CSYS,CSID
Valid values for CSID are MAT (material) or ELEM (element), or any user-created coordinate system.
Shell elements support only material and element coordinate systems. Link elements support only element
coordinate systems.
The default coordinate systems are 0 (global Cartesian) for solid elements, and ELEM for shell, beam
and link elements.
5.5. Initial State Limitations

The following initial state element limitations apply:
Initial State
• It is available only for current-technology elements. Initial state supported for a given element is indicated
in the documentation for the element under “Special Features.”
• Node-based initial state (p. 108) is not supported for the following current-technology elements: REINF263,
REINF264, REINF265, SOLID272, SOLID273, ELBOW290.
For user-defined data types, however, support for node-based initial state is available for these ele-
ments: SOLID272, SOLID273, ELBOW290.
• Initial state datatypes "void volume ratio" (VRAT) and "pore pressure" (PPRE) are available only for the coupled
pore-pressure elements CPT212, CPT213, CPT215, CPT216 and CPT217.
The following initial state material limitations apply:
• It is not supported for use with kinematic hardening material properties (TB,BKIN, TB,PLAS,,,,KINH).
• It is not supported for use with the shape memory alloy material model (TB,SMA).
• Initial state with initial stress alone is not supported for gasket materials (TB,GASK).
• Initial state with initial elastic strain alone is not supported for gasket materials (TB,GASK) and hyperelastic
materials (TB,HYPER, TB,BB, TB,AHYPER, TB,CDM, TB,EXPE).
• Initial state with plastic strain (which must include initial strain or stress, plastic strain, and accumulated
plastic strain) does not support gasket materials (TB,GASK), porous media (TB,PM), rate-dependent plasticity
(TB,RATE), and viscoplasticity (TB,PRONY, TB,SHIFT).
• Initial state with field variables is not supported for fracture calculations initiated via the CINT command.
• Some elements have displacement functions that are incompatible with one another when those elements
are adjacent and share element faces or edges. When different types of lower- and higher-order elements
with displacement shape functions (such as SOLID185 with SOLID186 or SOLID187) are used in a model and
share common faces or edges, a full Newton-Raphson procedure (NROPT,FULL) is necessary to obtain a
correct solution for a linear problem.
• For higher-order elements, values at the midside nodes are estimated by averaging the values at the corner
nodes.
• Initial state can be applied only as node-based, element-based, or material-ID-based. For example, one data
type cannot be applied as node-based, another as element-based, and another as material-ID-based.
• User-defined field variables are available for node-based initial state only.
• Function-based (p. 111) initial state has these limitations:
– With higher-order elements, initial state values at the midside nodes are evaluated by averaging the
coefficients of the function applied at the corner nodes. A single element must have the same function
type at all nodes in the element.
– Discrete initial state (when initial state is not defined as a function of internal variables) cannot be used
at the same time in an element.
– Sections are not supported.
Example Problems Using Initial State
5.6. Example Problems Using Initial State

This section provides examples of typical initial state problems, as follows:
5.6.1. Example: Initial Stress (IST File)
5.6.2. Example: Initial Stress (INISTATE Command)
5.6.3. Example: Initial Strain
5.6.4. Example: Initial Plastic Strain
5.6.5. Example: Initial Creep Strain
5.6.6. Example: Initial Plastic Strain with State Variables
5.6.7. Example: Node-Based Initial Strain
5.6.8. Example: Initial Pore Pressure and Void Ratio
5.6.9. Example: Function-Based Initial State
5.6.1. Example: Initial Stress (IST File)

The following example initial stress problem shows how to define an initial stress file and use the
INISTATE,READ command to read the data into your analysis.
The following file contains the initial stresses to be read into ANSYS. Each element has eight integration
points in the domain of the element.
/CSYS,0
! ELEM ID ELEM INTG LAY/CELL SECT INTG SX SY SZ SXY SYZ SXZ
1 , 1, 1 1 100, 0, 0, 0, 0, 0
1 , 2, 1 1 100, 0, 0, 0, 0, 0
1 , 3, 1 1 100, 0, 0, 0, 0, 0
1 , 4, 1 1 100, 0, 0, 0, 0, 0
1 , 5, 1 1 100, 0, 0, 0, 0, 0
1 , 6, 1 1 100, 0, 0, 0, 0, 0
1 , 7, 1 1 100, 0, 0, 0, 0, 0
1 , 8, 1 1 100, 0, 0, 0, 0, 0
In the following input listing, initial stress loading data is read in from a file. The data is read in during
the first load step, and establishes a preliminary deflection corresponding to a tip loaded cantilever
beam with a tip load of 100.
/prep7
/title, Example of Initial stress import into ANSYS
et,1,182
! Plane stress PLANE182 element
mp,ex,1,1.0e9
mp,nuxy,1,0.3
!
! Define the nodes
!
n,1
n,2,2.0
n,3,4.0
n,4,6.0
n,5,8.0
n,6,10.0
n,7,,1.0
n,8,2.0,1.0
n,9,4.0,1.0
n,10,6.0,1.0
n,11,8.0,1.0
n,12,10.0,1.0
!
! Define the 5 elements
!
e,1,2,8,7
e,2,3,9,8
e,3,4,10,9
Initial State
e,4,5,11,10
e,5,6,12,11
! Constrain all dofs on all nodes at x=0 to be zero
nsel,s,loc,x,
d,all,all
nall
finish
!
/solu
! Read in the initial stresses from istress.ist file
! as loading in the 1st load step.
! Input stresses correspond to the element integration
! point location.
!
inistate,read,istress,ist
! List the initial stresses

inistate,list
outres,all,all
solve
finish
!
/post1
set,last
prnsol,u
finish
The INISTATE,WRITE command specifies the coordinate system into which the data is to be written.
5.6.2. Example: Initial Stress (INISTATE Command)

You can apply constant stresses to all selected elements by issuing a INISTATE,DEFI,ALL command. The
INISTATE command can also delete stress from individual elements after the stress is applied. The
INISTATE,LIST command lists the applied stresses. The following input listing shows how these commands
are used.
solution
!
! Apply a constant state of the initial stresses.
!
inistate,defi,all,,,,1322.34,2022.21,302.43,4040.32,5076.32,6021.456
!
! Verify the applied stresses then delete those of element #1
!
inistate,list
inistate,dele, 1
!
! Set the boundary conditions and then solve
!
inistate,list
solve
finish
5.6.3. Example: Initial Strain

This example initial strain problem is a simple uniaxial test. A displacement of 0.05 is applied to this
single element. An additional 0.05 initial strain is applied. The calculated results include the effects of
both initial strain field and the applied displacement.
delta = 0.05
ndiv=1
/prep7
! Define the material

mp,ex,1,20E3
mp,nuxy,1,0.3
mp,dens,1,7850 ! kg/m3
et,1,185
block,0,1,0,1,0,1
lesize,all,,,ndiv
vmesh,all,all
finish
/solu
nsel,s,loc,x
d,all,ux
nsel,s,loc,y
d,all,uy
nsel,s,loc,z
d,all,uz
inistate,defi,,,,,0.05,
nsel,s,loc,x,1
d,all,ux,delta
allsel,all
solve
/post1
set,last
presol,s
presol,epto
presol,epel
finish
5.6.4. Example: Initial Plastic Strain

This initial plastic strain example is a simple 3-D problem where the cross section has three layers. An
initial plastic strain and stress are applied to one of the layers. One end of the block (shaped like a
beam) is fixed and the stresses are allowed to redistribute. The following input listing shows how to
apply initial plastic strain to one layer within a cross section and check the redistributed stresses.
/prep7
et,1,185,,2,1
keyopt,1,8,1 ! store data for all layers (can be excessive)
mp, ex, 11, 20.0e6 ! psi (lbf/in^2)

mp, prxy, 11, 0.25 ! unitless
mp, ex, 12, 20.0e6 ! psi (lbf/in^2)
mp, ex, 13, 20.0e6 ! psi (lbf/in^2)
! MISO material model

tb,plas,11,,3,miso
tbpt,,0.0,1e3
tbpt,,0.6,1e3
! BISO material model
tb,biso,12,,1
tbdata,define,100,100000
! Plastic material model
tb,plas,13,,7,miso
tbpt,,0.0000,30000
tbpt,,4.00e-3,32000
tbpt,,8.10e-3,33800
tbpt,,1.25e-2,35000
tbpt,,2.18e-2,36500
tbpt,,3.10e-2,38000
Initial State
tbpt,,4.05e-2,39000
sectype,1,shell,,my3ply ! 3-ply laminate

secdata, 0.30, 11, , 3 ! 1st layer THICK, MAT, ANG, Int. Pts.
secdata, 0.30, 12, , 3 ! 2nd layer THICK, MAT, ANG, Int. Pts.
secdata, 0.30, 13, , 3 ! 3rd layer THICK, MAT, ANG, Int. Pts.
! align esys with the global system
block,0,1,0,0.1,0,0.1
type,1
secnum,1
esize,0.1
vmesh,1
finish
/solu
antype,static
outres,all,all
! Uniaxial State Initial plastic Strain.
inistate,set,mat,13
inistate,defi,all,all,all,all,0.1,,,
inistate,set,dtyp,pleq
inistate,defi,all,all,all,all,0.1,,,
inistate,set,dtyp,stress
inistate,define,all,all,all,all,1000
inistate,set,dtyp,,
inistate,list,all
nsel,s,loc,x,0
d,all,all,0.0 ! Fix one end
nsel,all
solve
save
finish
/post1
set,last
esel,s,elem,,1
/com -----------------------------------------------------------------------------
/com, Expected result: You should see newly redistributed stresses and strains in
/com, all layers
/com -----------------------------------------------------------------------------
layer,1
presol,s,comp
presol,eppl,comp
layer,2
presol,s,comp
presol,eppl,comp
layer,3
presol,s,comp
presol,eppl,comp
finish
5.6.5. Example: Initial Creep Strain

This initial creep strain example demonstrates how you can use initial creep strain from one analysis,
then continue the problem to perform a second step.
In Analysis 1, creep strains are calculated up to TIME = 100 in the first step, and then the analysis is
continued up to TIME = 200 in the second step.
In Analysis 2, initial state data generated at TIME = 100 is used as the starting point, and the creep
analysis is performed only for TIME = 100 to TIME = 200.
The two analyses generate the same results, validating the use of initial creep strain.
!***************************************************************
! Analysis 1: Multiple Steps *without* INISTATE
!***************************************************************
! Read the FE Model from the CDB File. FE Model has both Plasticity and Creep Material Models Defined.
/prep7
CDREAD,ALL,geom,cdb
! Perform a two-step sample creep problem

/SOLU
RATE,OFF
/OUT, scratch
TOFFST,273,
TIME,1E-6
AUTOTS,0
NSUBST,1
KBC,0
SOLVE
! Step 1: Generate initial state information

RESCONTROL,,2,10
RATE,ON,ON
TIME,100 ! Reduced time for faster solution run time.
AUTOTS,1
NSUBST,1000,1000,10
KBC,0
OUTRES,ALL,10,
inistate,write,1,,,,-1,s
inistate,write,1,,,,-1,eppl
inistate,write,1,,,,-1,pleq
inistate,write,1,,,,-1,epcr
SOLVE
inistate,write,0,,,,-1,s
inistate,write,0,,,,-1,eppl
inistate,write,0,,,,-1,pleq
inistate,write,0,,,,-1,epcr
! Step 2: Perform Step 2 of the creep problem

TIME,200
SOLVE
FINISH
! Print out the results

/POST26
/OUT
/com -------------------------------------------------------------------------
/com | The deflections in y direction of nozzle top from continuous solution|
/com -------------------------------------------------------------------------
/OUT,scratch
NSOL,2,453,U,Y,Etype181
/OUT
PRVAR,2
FINISH
/post1
presol,epcr,comp
finish
! Clear the database

/clear
Initial State
!***************************************************************
! Analysis 2: Multiple Steps *with* INISTATE
!***************************************************************
! Resume old cdb file
/prep7
CDREAD,ALL,geom,cdb
! Step 1: Read in INISTATE data with creep strain from the IST
! file with rate off and solve
/SOLU
RATE,OFF
/OUT, scratch
TOFFST,273,
TIME,100
AUTOTS,0
NSUBST,10,10,10
KBC,0
inistate,read,filename ist
SOLVE
! Step 2: Continue and generate the same results as Analysis 1

RESCONTROL,,2,10
RATE,ON,ON
TIME,200
AUTOTS,1
NSUBST,10,100,10
KBC,0
OUTRES,ALL,10,
pred,off
SOLVE
FINISH
/POST26
/OUT
/com -------------------------------------------------------------------------
/com | The deflections in y direction of nozzle top from continuous solution|
/com -------------------------------------------------------------------------
/OUT,scratch
NSOL,2,453,U,Y,Etype181
/OUT
PRVAR,2
FINISH
/post1
presol,epcr,comp
finish
5.6.6. Example: Initial Plastic Strain with State Variables

This initial state example shows how you can use initial state data (as state variables) from one analysis,
then continue the problem in a subsequent analysis.
To continue an isotropic hardening plasticity analysis, plastic strain, accumulated equivalent plastic
strain, and stress are needed. In this problem, the accumulated equivalent plastic strain is saved from
the UserMat routine as state variables, which are then used as initial-state data for the initial accumu-
lated equivalent plastic strain applied in the subsequent analysis.
Analysis 1: Adisplacement of ux = 0.3 is applied in load step 1, unloaded to ux = 0.2 in

load step 2, and an additional displacement of ux = 0.2 is applied in load step 3. Initial
state data is generated at the end of load step 2. Plastic strain, stress and accumulated
equivalent plastic strain are saved in the .ist file.
Analysis 2: The initial state data generated previously is used as the starting point. An
additional displacement of 0.2--the difference between the displacement in load step 3
and load step 2 in the prior analysis--is applied in load step 2 in this analysis.
The two analyses generate the same results, validating the use of initial state with state
variables.
/filname,tutor-bag06s
/prep7
et,1,185
keyopt,1,3,1
! Define
tb,user,1,2,4
tbdata,1,19e5, 0.3, 1e4,2000, ! E, posn, sigy, H
tb,state,mat2,,10
tbdata,1,0.0,0.0,0.0,0.0,0.0,0.0 ! initialize state variables
tbdata,7,0.0 ! initialize state variables
type,1
real,1
mat,1
sectype,1,shell
secdata, 0.125, 1, 0.0,1
secdata, 0.125, 1, 30.0,1
secdata, 0.125, 1, 60.0,1
secdata, 0.125, 1, 90.0,1
block,0,1,0,1,0,1
esize,0.5
vmesh,all
nsel,s,loc,x,0
d,all,ux
nsel,s,loc,y,0
d,all,uy
nsel,s,loc,z,0
d,all,uz
allsel,all
cdwrite,comb,tutor-bag06s,cdb
finish
/solu
outres,all,all
time,0.5
eresx,no
nsel,s,loc,x,1
d,all,ux,0.03 ! First load step,displacement on x-axis
allsel,all
solve
time,1
nsel,s,loc,x,1
d,all,ux,0.02
allsel,all
! Save Plastic Strain, Elastic Strain and State Variables.
inis,write,1,,,,-2,s
inis,write,1,,,,-2,eppl
inis,write,1,,,,-2,svar
solve
inis,write,0,,,,-2,s
inis,write,0,,,,-2,eppl
inis,write,0,,,,-2,svar
Initial State
time,2
nsel,s,loc,x,1 ! Second load step , displacement on x-axis
d,all,ux,0.04
allsel,all
solve
finish
/post1
/com
/com +**************************************************************
/com Results fron the analysis without INIS command
/com ***************************************************************
rsys,solu
set,2
esel,s,elem,,1
etable,epplx_2r,eppl,x
etable,epply_2r,eppl,y
etable,epplz_2r,eppl,z
set,last
allsel,all
pretab,epplx_2r,epply_2r,epplz_2r,epplx_3r,epply_3r,epplz_3r
fini
/clear,nostart
/delet,tutor-bag06s,rst
/filname,tutor-bag06s
cdread,comb,tutor-bag06s,cdb
/com ***********************************************************************
/com Second case: analysis with INISTATE command
/com ***********************************************************************
/solu
outres,all,all
time,0.1
inis,read,tutor-bag06s,ist ! First load step, reading back initial strain datas
ddele,all,all
nsel,s,loc,x,0
d,all,ux
nsel,s,loc,y,0
d,all,uy
allsel,all
nsel,s,loc,x,1 ! First load step ,no displacement on x-axis

d,all,ux,0.0
allsel,all
inis,set,dtyp
inis,list,1
solve
time,2
nsel,s,loc,x,1 ! Second load step , displacement on x-axis

d,all,ux,0.02
allsel,all
solve
finish
/post1
/com
/com ***************************************************************
/com Results fron the analysis with the INIS command
/com ***************************************************************
rsys,solu
set,1
esel,s,elem,,1
set,last
allsel,all
pretab,epplx_2r,epply_2r,epplz_2r,epplx_3r,epply_3r,epplz_3r
fini
5.6.7. Example: Node-Based Initial Strain

This example node-based initial state problem describes how to generate a node-based initial state file
from another analysis and then apply that data to a modal analysis.
In step 1, a node-based initial state files is generated. In step 2, the file is read in and a static solution
is generated. In step 3, the modal analysis is done.
/prep7
!********** Define the material **********
mp,ex,1,210e9 ! Pa
mp,nuxy,1,.29 ! No units
mp,dens,1,7850 ! kg/m3
et,1,182
rectng,0,10,0,2,
esize,0.5
amesh,all
nsel,s,loc,x
d,all,ux
nsel,s,loc,y,0
d,all,uy
nsel,s,loc,x,10
d,all,ux,0.1
nall
finish
/solu
antype,static
time,1
nsubst,10,10,10
solve ! Solve for Sample Prestress Loads
fini
/post1
*get,mxnid,node,,num,max
nsel,s,node,,mxnid
prnsol,s,comp
nsel,all,all
*vget,nl,node,,nlist
*vget,sx,node,,s,x
*vget,sy,node,,s,y
*vget,sz,node,,s,z
*cfopen,tutor-bag07s-ist.dat ! Generate Ist File
*vwrite
('INIS,SET,NODE,1')
*vwrite,nl(1),sx(1),sy(1),sz(1)
('INIS,DEFI,',F4.0,' , , , , ',E,' , ',E,' , ',E,',0.0,0.0,0.0')
*cfclos
/solu
ddele,all,all
d,all,all
nall
Initial State
antype,static
time,1
nsubst,10,10,10
/inp,tutor-bag07s-ist.dat ! Read in Node Based IST Data
esel,s,elem,,1,80,5
inis,list
allsel,all
rescontrol,linear,all,1
solve
finish
!********** Perform a perturbed modal analysis **********

/solu
antype,static,restart,,,perturb
perturb,modal,,,nokeep
solve,elform
nsel,s,loc,x
nsel,a,loc,x,10.0
d,all,ux
nsel,s,loc,y,0
d,all,uy
nall
modopt,lanb,5
mxpand,5
solve
fini
/post1
file,,rstp
set,list
fini
5.6.8. Example: Initial Pore Pressure and Void Ratio

This example shows how to apply and use initial pore pressure and void ratio on coupled pore-pressure
elements (CPTnnn).
/PREP7
ET,1,212
KEYO,1,3,1
R,1
!-------------------------------------------------------------------------------
!---- MATERIAL PROPERTY DEFINITION
! SET MATERIAL DENSITY
DENS,1,1.2 !
! ELASTIC MATERIAL LAW

KAPPA=0.054 !
NU0=0.35 ! NU0=(3*P0*(1+E0)/KAPPA-2*MU0)/(2*(3*P0*(1+E0)/KAPPA)-MU0)
E0=0.34 ! VOID RATIO E0=N_F0_F/N_S0_S
A0=20 ! INITIAL SIZE OF THE YIELD SURFACE

AH_MIN=0.01*A0
EM=1440
K0=EM/(1-2*NU0) ! FOOTING PROBLEM: K0=EM/(1-2*NU0)
PT_EL=K0*KAPPA/(1+E0) ! FOOTING PROBLEM: K0=EM/(1-2*NU0)
!PARAMETER TO VON MISES PLASTICITY

BETA_DRY=1.0 ! SHAPE OF THE YIELD SURFACE IN DRY PART [-]
BETA_WET=1.0 ! SHAPE OF THE YIELD SURFACE IN WETTING PART [-]
LAMBDA_F=0.37 ! PLASTIC SLOPE (STIFFNESS) [M^2/KN] >KAPPA (2-3 TIME OF KAPPA)
KS=1.0 ! SHAPE OF THE YIELD SURFACE IN THE OCTAHEDRAL STRESS PLANE
MC=1.4 ! SLOPE OF THE CSL IN THE HYDROSTATIC STRESS PLANE 6*SIN(PHI)/(3+SIN(PHI)->PHI: STRESS FRICTION ANGLE
!TBDATA,8, KAPPA, NU0, E0, PT_EL

TB,PELAS,1,,,POISSON
TBDATA,1, KAPPA, PT_EL, NU0, E0
!---- POROUS MATERIAL DEFINITION

FPX=8.62E-3
ONE=1.0
TB,PM,1,,,PERM
TBDATA,1,FPX,FPX,FPX
TB,PM,1,,,BIOT
TBDATA,1,ONE
ALLSEL
!-------------------------------------------------------------------------------
W=3 ! WIDTH
RECTNG,0,6*W,0,-9*W
TYPE,1
REAL,1
MAT,1
MSHAP,0,2D
ESIZE,W/4
AMESH,1
NSEL,S,LOC,Y,-9*W
D,ALL,UX,0
D,ALL,UY,0
ALLSEL
NSEL,S,LOC,X,0
NSEL,A,LOC,X,6*W
D,ALL,UX,0
ALLSEL
NSEL,S,LOC,Y,0
D,ALL,UX,0
D,ALL,PRES,0
NSEL,R,LOC,X,0,W
SF,ALL,PRES,1E3
ALLSEL
FINI
/SOLU
! SET AN INITIAL PORE PRESSURE OF P0
P0=69
INISTATE,SET,DTYP,PPRE
INISTATE,DEFI,ALL,,,,P0
! Override the void ratio defined in the TB,PELAS with 0.4

newvratio=0.4
INISTATE,SET,DTYP,VOID
INISTATE,DEFI,ALL,,,,newvratio
ANTYPE,STATIC
NROPT,UNSYM!FULL
NEQIT,30
TIME,1E3
NSUBST,100,1000,20
OUTRES,ALL,ALL
KBC,1
SOLVE
FINI
/POST1
/OUT,
ESEL,S,ELEM,,1
!Output Pore Pressure in element 1
PRES,PMSV
PRES,EPTO
/COM, EXPECTED RESULTS: EVOID=E0+VCE+(1+E0)=0.3453

FINISH
Initial State
5.6.9. Example: Function-Based Initial State

This example shows how to apply and use initial pore pressure and void ratio as a function of location.
/PREP7
ET,1,212
KEYO,1,3,1
R,1
!-------------------------------------------------------------------------------
!---- MATERIAL PROPERTY DEFINITION
! SET MATERIAL DENSITY
DENS,1,1.2 !
! ELASTIC MATERIAL LAW

KAPPA=0.054 !
NU0=0.35 ! NU0=(3*P0*(1+E0)/KAPPA-2*MU0)/(2*(3*P0*(1+E0)/KAPPA)-MU0)
E0=0.34 ! VOID RATIO E0=N_F0_F/N_S0_S
A0=20 ! INITIAL SIZE OF THE YIELD SURFACE

AH_MIN=0.01*A0
EM=1440
K0=EM/(1-2*NU0) ! FOOTING PROBLEM: K0=EM/(1-2*NU0)
PT_EL=K0*KAPPA/(1+E0) ! FOOTING PROBLEM: K0=EM/(1-2*NU0)
!PARAMETER TO VON MISES PLASTICITY

BETA_DRY=1.0 ! SHAPE OF THE YIELD SURFACE IN DRY PART [-]
BETA_WET=1.0 ! SHAPE OF THE YIELD SURFACE IN WETTING PART [-]
LAMBDA_F=0.37 ! PLASTIC SLOPE (STIFFNESS) [M^2/KN] >KAPPA (2-3 TIME OF KAPPA)
KS=1.0 ! SHAPE OF THE YIELD SURFACE IN THE OCTAHEDRAL STRESS PLANE
MC=1.4 ! SLOPE OF THE CSL IN THE HYDROSTATIC STRESS PLANE 6*SIN(PHI)/(3+SIN(PHI)->PHI: STRESS FRICTION ANGLE
!TBDATA,8, KAPPA, NU0, E0, PT_EL

TB,PELAS,1,,,POISSON
TBDATA,1, KAPPA, PT_EL, NU0, E0
!---- POROUS MATERIAL DEFINITION

FPX=8.62E-3
ONE=1.0
TB,PM,1,,,PERM
TBDATA,1,FPX,FPX,FPX
TB,PM,1,,,BIOT
TBDATA,1,ONE
ALLSEL
!-------------------------------------------------------------------------------
W=3 ! WIDTH
RECTNG,0,6*W,0,-9*W
TYPE,1
REAL,1
MAT,1
MSHAP,0,2D
ESIZE,W/4
AMESH,1
NSEL,S,LOC,Y,-9*W
D,ALL,UX,0
D,ALL,UY,0
ALLSEL
NSEL,S,LOC,X,0
NSEL,A,LOC,X,6*W
D,ALL,UX,0
ALLSEL
NSEL,S,LOC,Y,0
D,ALL,UX,0
D,ALL,PRES,0
NSEL,R,LOC,X,0,W
Writing Initial State Values
SF,ALL,PRES,1E3
ALLSEL
FINI
/SOLU
! SET AN INITIAL PORE PRESSURE OF P0 AND INCREASES WITH DEPTH
P0=69
SL=0.1
INIS,SET,DATA,FUNC
INISTATE,SET,DTYP,PPRE
INISTATE,DEFI,ALL,,,,LINY,P0,SL
! OVERRIDE THE VOID RATIO DEFINED IN THE TB,PELAS WITH 0.4

NEWVRATIO=0.4
INISTATE,SET,DTYP,VOID
INISTATE,DEFI,ALL,,,,LINY,NEWVRATIO,0
ANTYPE,STATIC
NROPT,UNSYM!FULL
NEQIT,30
TIME,1E-2
NSUBST,100,1000,20
OUTRES,ALL,ALL
KBC,1
SOLVE
FINI
/POST1
/OUT,
ESEL,S,ELEM,,1
!OUTPUT PORE PRESSURE IN ELEMENT 1
PRES,PMSV
PRES,EPTO
/COM, EXPECTED RESULTS: EVOID=E0+VCE+(1+E0)=0.3453

FINISH
5.7. Writing Initial State Values

Issue an INISTATE,WRITE command (available in the solution processor only) to write a set of initial
state values to a file. You can issue the command multiple times to modify or overwrite your initial
state values.
5.7.1. Example: Output From the INISTATE Command's WRITE Option

The initial stress file written by the INISTATE,WRITE command has the same format as that of the input
file. The stresses in the file are those calculated at the integration points when the convergence occurs
in a nonlinear analysis. If the analysis type is linear, the stresses are those calculated when the solution
is finished. An example initial stress file resulting from this command follows:
!*********************************** INITIAL STRESS FILE *************************
!*********************************** t.ist *************************
!*********************************** HEADER INFORMATION *************************
/ETYP,DEFA
/COLINF,ELEM,ELIN,,,SX,SY,SZ,SXY,SYZ,SXZ
/ETYP,LAYE
/COLINF,ELEM,ELIN,LAYE,SECT,SX,SY,SZ,SXY,SYZ,SXZ
/ETYP,BEAM
/COLINF,ELEM,ELIN,CELL,SECT,SX,SY,SZ,SXY,SYZ,SXZ
!**************************** INITIAL STRESS DATA ********************************
!ELEM ID ELEM INTG LAY/CELL SECT INTG SX SY SZ SXY SYZ SXZ
/csys,0
1, 1, 1, 1, -3.50063 , -23.2768 , 0.00000 , -2.04204
1, 2, 1, 1, 3.50063 , 0.607255E-01, 0.0000 , -2.04204
1, 3, 1, 1, 3.50063 , 0.607255E-01, 0.00000 , 2.04204
1, 4, 1, 1, -3.50063 , -23.2768 , 0.00000 , 2.04204
/csys,0
Initial State
2, 1, 1, 1, 0.791614 , 5.26355 , 0.00000 , 0.461775

2, 2, 1, 1, -0.791614 , -0.138827E-01, 0.00000 , 0.461775
2, 3, 1, 1, -0.791614 , -0.138827E-01, 0.00000 , -0.461775
2, 4, 1, 1, 0.791614 , 5.26355 , 0.00000 , -0.461775
/csys,0
3, 1, 1, 1, -0.179107 , -1.19024 , 0.00000 , -0.104479
3, 2, 1, 1, 0.179107 , 0.380702E-02, 0.00000 , -0.104479
3, 3, 1, 1, 0.179107 , 0.380702E-02, 0.00000 , 0.104479
3, 4, 1, 1, -0.179107 , -1.19024 , 0.00000 , 0.104479
/csys,0
4, 1, 1, 1, 0.409451E-01, 0.269154 , 0.00000 , 0.238847E-01
4, 2, 1, 1, -0.409451E-01, -0.381382E-02, 0.00000 , 0.238847E-01
4, 3, 1, 1, -0.409451E-01, -0.381382E-02, 0.00000 , -0.238847E-01
4, 4, 1, 1, 0.409451E-01, 0.269154 , 0.00000 , -0.238847E-01
/csys,0
5, 1, 1, 1, -0.112228E-01, -0.608972E-01, 0.00000 , -0.654661E-02
5, 2, 1, 1, 0.112228E-01, 0.139211E-01, 0.00000 , -0.654661E-02
5, 3, 1, 1, 0.112228E-01, 0.139211E-01, 0.00000 , 0.654661E-02
5, 4, 1, 1, -0.112228E-01, -0.608972E-01, 0.00000 , 0.654661E-02
Chapter 6: Rotating Structure Analysis
In a dynamic analysis involving a rotating structure, ANSYS can take inertia effects into account. The
following topics related to rotating structure analysis are available:
6.1. Understanding Rotating Structure Dynamics
6.2. Using a Stationary Reference Frame
6.3. Using a Rotating Reference Frame
6.4. Choosing the Appropriate Reference Frame Option
6.5. Example Campbell Diagram Analysis
6.6. Example Coriolis Analysis
6.7. Example Unbalance Harmonic Analysis
For additional information, see Coriolis Matrix and Coriolis Force in a Rotating Reference Frame in the
Mechanical APDL Theory Reference.
6.1. Understanding Rotating Structure Dynamics

You can observe inertia effects, applied via the CORIOLIS command, in either a stationary reference
frame (p. 130) or a rotating reference frame (p. 134). In both cases, you specify angular velocity by issuing
an OMEGA or CMOMEGA command.
The dynamic equation incorporating the effect of rotation is given by
where [M], [C] and [K] are the structural mass, damping, and stiffness matrices, respectively.
[Kc] is the spin softening matrix due to the rotation of the structure. It changes the apparent stiffness
of the structure in a rotating reference frame (described in Rotating Structures in the Mechanical APDL
Theory Reference).
[G] is a “damping” matrix contribution due to the rotation of the structure. It is usually called Coriolis
matrix in a rotating reference frame, and gyroscopic matrix in a stationary reference frame (described
in Rotating Structures in the Mechanical APDL Theory Reference).
{F} is the external force vector in the stationary reference frame. In a rotating reference frame, it is the
sum of the external force and the effect of the angular rotational velocity force (as described in Accel-
eration Effect in the Mechanical APDL Theory Reference).
Without the inertia effect applied via the CORIOLIS command, ANSYS does not generate the [G] matrix,
and the usual effect of the angular rotation velocity specified by the OMEGA or CMOMEGA command
applies (as described in Acceleration Effect in the Mechanical APDL Theory Reference). An exception exists,
however, involving a nonlinear transient analysis using element MASS21; in this case, the inertia effect
due to rotation applied via an IC command (or a D command over an incremental time) is included
without having to issue the CORIOLIS and OMEGA or CMOMEGA commands.
Rotating Structure Analysis
6.2. Using a Stationary Reference Frame

The primary application for a stationary (rather than a rotating (p. 134)) frame of reference is in the field
of rotordynamics where a rotating structure (rotor) is modeled along with a stationary support structure.
Examples of such an application include a gas turbine engine rotor-stator assembly or an electric turbo
generator, where the rotor spins inside a specially designed housing.
The rotating part of the structure to be modeled must be axisymmetric. The gyroscopic damping matrix
generated is valid only for a linear analysis.
ANSYS computes the displacement field with respect to the global coordinate system (CORIOLIS,Option
= ON,,,RefFrame = ON), referred to as the stationary reference frame.
Elements Supported
Elements that are part of the rotating structure generate the gyroscopic matrix that arises due to the
rotational angular velocity. The gyroscopic matrix is available for the elements listed in the notes section
of the CORIOLIS command.
For a beam element, the angular velocity vector is aligned along the length and the point mass is
aligned along one of the principal axes. The rotating structure must be axisymmetric about the spin
axis.
For SHELL281 and other triangular-shaped elements with midside nodes, modeling a shell structure
with the gyroscopic matrix turned on (CORIOLIS,ON, , ,ON) may yield anomalies with the QRDAMP ei-
gensolver. This is especially true when only a limited number of modes are extracted. In this case, use
the damped eigensolver (MODOPT, DAMP).
Analysis Types Supported

The following analysis types support rotating structure analysis using a stationary reference frame:
• Modal (ANTYPE,MODAL)
• Transient (ANTYPE,TRANS)
• Harmonic (ANTYPE,HARMIC)
For transient and harmonic analyses, the mode-superposition method (TRNOPT, MSUP, or HROPT,MSUP)
is supported for instances where the gyroscopic matrix does not need updating (see below). For the
mode-superposition method, only the QR Damp mode-extraction method (MODOPT,QRDAMP) is sup-
ported.
For a varying rotational velocity, mode-superposition analysis (transient or harmonic) is not supported,
since the modal gyroscopic matrix is not updated. This is especially true for cases where:
• an unbalance or asynchronous rotating force exists in a harmonic analysis (SYNCHRO command)
• a start-up or stop simulation is performed in a transient analysis (use the KBC command to ramp the rota-
tional velocity within one loadstep).
To include unbalance or general asynchronous rotating forces (p. 133) in a harmonic analysis, use the
SYNCHRO command.
Using a Stationary Reference Frame
For a transient analysis involving a rotating structure with a stationary reference frame, support for a
start or stop simulation is available. Issue the KBC command to ramp the rotational velocity.
For a prestressed analysis that includes gyroscopic effects, issue the CORIOLIS, ON,,,ON command in
the static prestress portion of the analysis.
Postprocessing
Besides general results, the following specific outputs are available:
• Campbell diagram (p. 131) (PRCAMP and PLCAMP) see Campbell Diagram (p. 131)
Note
For a prestressed structure, set the Campbell key (CAMPBELL,RSTP) in the first solution
pass. Doing so allows a Campbell diagram analysis.
• Orbits (p. 133) (PRORB and PLORB) see Orbits (p. 133)
• Animation of the whirl (ANHARM)
6.2.1. Campbell Diagram

In a modal analysis with multiple load steps corresponding to different angular velocities ω, a Campbell
diagram (PLCAMP or PRCAMP) shows the evolution of the natural frequencies.
ANSYS determines eigenfrequencies at each load step. The plot showing the variation of eigenfrequency
with respect to rotational speed may not be readily apparent. For example, if the gyroscopic effect is
significant on an eigenmode, its frequency tends to split so much that it crosses the other frequency
curves as the speed increases. For more information, see Generating a Successful Campbell Diagram
below.
Critical Speeds
The PRCAMP command also prints out the critical speeds for a rotating synchronous (unbalanced) or
asynchronous force. The critical speeds correspond to the intersection points between frequency curves
and the added line F=s.ω (where s represents SLOPE > 0 as specified via PRCAMP). Because the critical
speeds are determined graphically, their accuracy depends upon the quality of the Campbell diagram.
To retrieve and store critical speeds as parameters, use the *GET command.
Whirls and Stability

As eigenfrequencies split with increasing spin velocity, ANSYS identifies forward (FW) and backward
(BW) whirls, and unstable frequencies. To obtain more information to help you determine how a partic-
ular frequency becomes unstable, issue the PLCAMP or PRCAMP command and specify a stability value
(STABVAL) of 1. You can also view the logarithmic decrements by specifying STABVAL = 2 or 3. For
more information about complex eigenvalues and corresponding logarithmic decrements, see Complex
Eigensolutions in the Mechanical APDL Theory Reference.
Note
For a rotating structure meshed in shell elements lying in a plane perpendicular to the rota-
tional velocity axis - such as a thin disk - the whirl effects are not plotted or printed by the
PRCAMP or PLCAMP commands. However, they can be visualized using the ANHARM
command.
To retrieve and store frequencies and whirls as parameters, use the *GET command.
Generating a Successful Campbell Diagram

To help you obtain a good Campbell diagram plot or printout, the sorting option is active by default
(PLCAMP,ON or PRCAMP,ON). ANSYS compares complex mode shapes and pairs similar mode shapes.
(Because eigenmodes at zero velocity are real modes, ANSYS does not pair them with complex modes.)
If the plot is unsatisfactory even with sorting enabled, try the following:
• Start the Campbell analysis with a non-zero rotational velocity.
Modes at zero rotational velocity are real modes and may be difficult to pair with complex modes
obtained at non-zero rotational velocity.
• Increase the number of load steps.
It helps if the mode shapes change significantly as the spin velocity increases.
• Change the frequency window.
To do so, use the shift option (PLCAMP,,,FREQB or PRCAMP,,,FREQB). It helps if some modes fall
outside the default frequency window.
Overcoming Memory Problems

To run the Campbell analysis (PRCAMP or PLCAMP), the scratch memory needed may be important as
complex mode shapes are read from the result file for two consecutive load steps. If your computer
has insufficient scratch memory, try the following:
• Decrease the number of extracted modes (MODOPT,,NMODE)
• Generate the result file for a reduced set of selected nodes (for example, nodes on the axis of rotation). Issue
OUTRES,ALL,NONE and then OUTRES,Item,Freq,Cname where Item=NSOL, Freq=ALL and Cname is
the name of a node-based component.
For the sorting process and whirl calculation to be successful, the set of selected nodes must represent
the dynamics of the structure. In general, nodes on the spin axis contribute to the bending mode
shapes that are needed in the Campbell analysis.
Example Analysis
For an example of a rotating structure analysis using a stationary reference frame, see Example Campbell
Diagram Analysis (p. 137).
Using a Stationary Reference Frame
6.2.2. Harmonic Analysis for Unbalance or General Rotating Asynchronous

Forces
Some forces may rotate synchronously (for example, unbalance) or asynchronously with the structure.
In such cases, use the SYNCHRO command to update the amplitude of the rotational velocity vector
with the frequency of excitation at each frequency step of the harmonic analysis.
Forces are defined as static (F), as shown in this example where X is the assumed spin axis:
Force Real (VALUE) Imaginary (VALUE2)

FY F0cosα -F0sinα
FZ -F0sinα -F0cosα
where:
F0 is the amplitude of the force. For unbalance, the amplitude is equal to the mass times
the distance of the unbalance mass to the spin axis.
α is the phase of the force, needed only when several such forces, each with a different
relative phase, are defined.
If the forces are caused by an unbalance mass, multiplication of the amplitude of the static forces (F)
by the square of the spin velocity is unnecessary. ANSYS performs the calculation automatically at each
frequency step.
Because the rotational velocity commands (OMEGA and CMOMEGA) define only the orientation of the
spin axis, a harmonic analysis using the SYNCHRO command requires that you define the frequency
of excitation (HARFRQ) instead. For example, if the frequency of excitation is f, then:
ω = 2πf/RATIO
where:
ω is the new magnitude of the rotational velocity vector used to calculate the gyroscopic
matrices.
RATIO is the ratio between the frequency of excitation and the frequency of the rota-
tional velocity of the structure, as specified via the SYNCHRO command. If no RATIO
value is specified, an unbalance force is assumed; in all other cases, a general rotating
force is assumed.
Example Analysis
For an example of a harmonic analysis for unbalance forces, see Example Unbalance Harmonic Analys-
is (p. 142).
6.2.3. Orbits
When a structure is rotating about an axis and undergoes vibration motion, the trajectory of a node
executed around the axis is generally an ellipse designated as a whirl orbit.
In a local coordinate system xyz where x is the spin axis, the ellipse at node I is defined by semi-major
axis A, semi-minor axis B, and phase ψ (PSI), as shown:
Angle ϕ (PHI) defines the initial position of the node (at t = 0). To compare the phases
of two nodes of the structure, you can examine the sum ψ + ϕ.
Values YMAX and ZMAX are the maximum displacements along y and z axes, respectively.
You can print out the A, B, PSI, PHI, YMAX, and ZMAX values via a PRORB (print orbits)
command. Angles are in degrees and within the range of -180 through +180. The position
vector of local axis y in the global coordinate system is printed out along with the ellipt-
ical orbit characteristics. You can also animate the orbit (ANHARM) for further examina-
tion. For a typical usage example of these commands, see Example Unbalance Harmonic
Analysis (p. 142).
To retrieve and store orbits characteristics as parameters, use the *GET command after issuing the
PRORB command.
6.3. Using a Rotating Reference Frame

The primary application for a rotating (rather than a stationary (p. 130)) frame of reference is in the field
of flexible body dynamics where, generally, the structure has no stationary parts and the entire structure
is rotating. Analyses of this type, therefore, consider only the Coriolis force.
Note
The gyroscopic effect is not included in the dynamics equations expressed in a rotating ref-
erence frame. Therefore, if the structure contains a part with large inertia - such as a large
disk - the results obtained in the rotating reference frame may not compare well with sta-
tionary reference frame results.
ANSYS computes the displacement field with respect to the coordinate system attached to the structure
and rotating with it at the specified angular velocity (CORIOLIS,Option = ON,,,RefFrame = OFF).
Elements Supported
The Coriolis matrix and forces are available for the structural elements listed in the notes section of the
CORIOLIS command.
Analysis Types Supported

The following analysis types support rotating structure analysis using a rotating reference frame:
• Static (ANTYPE,STATIC)
Using a Rotating Reference Frame
Inertia effects are forces computed by multiplying the Coriolis damping matrix by the velocity of the
structure.
If you issue the CORIOLIS command in a prestressed analysis, ANSYS does not take the Coriolis force
into account in the static portion of the analysis.
– In a large-deflection prestressed analysis (NLGEOM,ON and PSTRES,ON), ANSYS generates the Coriolis
matrix and uses it in the subsequent prestressed modal, harmonic, or transient analysis.
– In a small-deflection prestressed analysis (PSTRES,ON only), ANSYS does not generate the Coriolis matrix
but still takes the Coriolis force into account in the subsequent prestressed modal, harmonic, or transient
analysis.
• Modal (ANTYPE,MODAL)
Support is also available for prestressed modal analysis.
• Transient (ANTYPE,TRANS)
• Harmonic (ANTYPE,HARMIC)
Spin Softening
In a dynamic analysis, the Coriolis matrix and the spin-softening matrix contribute to the gyroscopic
moment in the rotating reference frame; therefore, ANSYS includes the spin-softening effect by default
in dynamic analyses whenever you apply the Coriolis effect in the rotating reference frame (CORIOLIS,ON).
Supercritical Spin Softening
As shown by equations (3-77) through (3-79) in the Mechanical APDL Theory Reference,
the diagonal coefficients in the stiffness matrix become negative when the rotational
velocity is larger than the resonant frequency.
In such cases, the solver may be unable to properly handle the negative definite stiffness
matrix. Additional details follow:
• In a static (ANTYPE,STATIC) or a full transient (ANTYPE,TRANS with TRNOPT,FULL), the spin-

softening effect is more accurately accounted for by large deflections (NLGEOM,ON). If the
stiffness matrix becomes negative definite, ANSYS issues a warning message about the
negative pivot.
• In a modal analysis (ANTYPE,MODAL), apply a negative shift (MODOPT,,, FREQB) to extract

the possible negative eigenfrequencies.
• If negative frequencies exist, mode-superposition transient and harmonic analyses are not
supported .
Coriolis Effect in a Nonlinear Transient Analysis

In a nonlinear transient analysis with large deflection effects (NLGEOM, ON ), rotation
motion imparted through either the IC command or the D command contributes the
Coriolis effect as part of the nonlinear transient algorithm. The CORIOLIS command
should not be activated in this case. However, beam elements (BEAM188 and BEAM189),
and pipe elements (PIPE288 and PIPE289 ) may produce approximate results when sim-
ulating Coriolis effect as above, due to the approximations involved in their inertia cal-
culations.
Campbell Diagram
Because natural frequencies are subject to sudden changes around critical speeds in a
rotating frame, ANSYS, Inc. recommends using a stationary reference frame (p. 130) to
create a Campbell diagram (PRCAMP or PLCAMP).
Example Analysis
For examples of a rotating structure analysis using a rotating reference frame, see Example Coriolis
Analysis (p. 139), and Example: Piezoelectric Analysis with Coriolis Effect in the Coupled-Field Analysis
Guide.
6.4. Choosing the Appropriate Reference Frame Option

The rotating (p. 134) and stationary (p. 130) reference frame approaches have their benefits and limitations.
Use this table to choose the best option for your application:
Reference Frame Considerations

Stationary (p. 130) Reference Frame Rotating (p. 134) Reference Frame
Not applicable to a static analysis (ANTYPE,STATIC). In a static analysis, a Coriolis force vector is
given by:
where represents the nodal velocity

vector (specified via the IC command).
You can generate Campbell plots (p. 131) for Campbell plots are not applicable for computing
computing rotor critical speeds. rotor critical speeds.
Structure must be axisymmetric about the spin axis. Structure need not be axisymmetric about the
spin axis.
Rotating structure can be part of a stationary structure Rotating structure must be the only part of an
in an analysis model (such as a gas turbine engine analysis model (such as a gas turbine engine
rotor-stator assembly). The stationary structure and rotor).
supports (such as bearings) need not be axisymmetric.
Supports more than one rotating structure spinning Supports only a single rotating structure (such as
at different rotational speeds about different axes of a single-spool gas turbine engine).
rotation (such as a multi-spool gas turbine engine).
See the CORIOLIS command for the list of elements See the CORIOLIS command for the list of
supported in the Stationary Reference Frame. elements supported in the Rotating Reference
Frame.
Natural Frequencies
Natural frequencies differ according to the reference frame type. In most cases, natural frequencies are
known in a stationary reference frame through analytical expressions or experiment, for example. ANSYS
therefore recommends using the stationary reference frame for modal analyses.
Example Campbell Diagram Analysis
6.5. Example Campbell Diagram Analysis

Following is a modal analysis of a rotating structure using a stationary reference frame (p. 130). The
analysis generates a Campbell diagram (PLCAMP).
6.5.1. Problem Description

The model is a simply supported beam spinning at up to 30,000 rd/s.
6.5.2. Problem Specifications

The geometric properties for this analysis are as follows:
Length: 8m
Diameter: 0.2m
The material properties for this analysis are as follows:
Young's modulus (E) = 2e+11 N/m2

Poisson's ratio (υ) = 0.3
Density = 7800 kg/m3
6.5.3. Input for the Analysis

Use this input file to perform the example modal analysis of a rotating structure using a stationary ref-
erence frame (p. 130).
/batch,list
/title, Spinning Simply Supported Beam
!* Parameters
lx=8 ! length
dia=0.2 ! diameter
/PREP7 ! -----
ET,1,16
R,1, dia, dia/2
MP,EX,1,2e+11
MP,DENS,1,7800
MP,PRXY,1,0.3
n,1
n,9,lx
fill,1,9
e,1,2
egen,8,1,-1
d,1,uy,,, ,,uz ! simply supported left end
d,9,uy,,, ,,uz ! simply supported right end
d,all,ux ! supress axial motion
d,all,rotx ! supress torsion
finish
/SOLU ! -----
antype,modal
! Use the QRDAMP eigensolver, request 8 modes,
! get complex eigensolutions
modopt,qrdamp,8,,,on
! Reuse the block Lanczos eigenvectors from the first loadstep
qrdopt,on
! Write 8 modes to the result file, calculate
! element results
mxpand,8,,,yes
! Apply Coriolis effect and specify
! stationary reference frame
coriolis,on,,,on
! Solve 2 loadsteps with rotational velocity
omega,0.
solve
omega,30000.
solve
finish
/POST1 ! -----
! Plot Campbell Diagram
plcamp
! Print Campbell Diagram
prcamp
finish
6.5.4. Analysis Steps

The following table describes the input listing and the general process involved in the example analysis
in more detail:
Step Description ANSYS Command(s)

1. Set parameters. lx=8
dia=0.2
2. Define nodes, elements, and material properties. ET,…
R,…
MP,...
N,…
E,…
3. Set boundary conditions. D,...
4. Set the analysis type (modal in this case). Use the QRDAMP ANTYPE,MODAL
eigensolver, request 8 modes, and specify complex
eigensolutions. MODOPT,QRDAMP,8,,,ON
MXPAND,...
5. Include the Coriolis effect in a stationary reference frame (p. 130).CORIOLIS,ON,,,ON
6. For each load step, define the rotation velocity, and then solve. OMEGA,…
SOLVE
7. Plot and print the Campbell diagram. PLCAMP
PRCAMP
The results of your analysis should be similar to those shown here:
Example Coriolis Analysis
The printout (PRCAMP) should yield the following data:

PRINT CAMPBELL DIAGRAM
Sorting : ON
X axis unit : rd/s
***** FREQUENCIES (Hz) FROM CAMPBELL (sorting on) *****
Spin(rd/s) 0.000 30000.000
1 BW 6.207 4.639
2 FW 6.207 8.305
3 BW 24.750 18.547
4 FW 24.750 33.027
5 BW 55.461 41.735
6 FW 55.461 73.701
7 BW 98.248 74.337
8 FW 98.248 129.852
6.6. Example Coriolis Analysis

Following is an example modal analysis with Coriolis force applied (CORIOLIS) in a rotating reference
frame (p. 134).

The model is a thick cylindrical shell rotating about its center axis at an angular velocity ω = 50 Hz.

The geometric properties for this analysis are as follows:
Length: 0.254m
Radius: 0.09525m
Thickness: 0.0381m.
The material properties for this analysis are as follows:
Young's modulus (E) = 2.07 x 1011 N/m2

Poisson's ratio (υ) = 0.28
Density = 7.86 x 103 Kg/m3

Use this input file to perform the example modal analysis of a rotating structure using a rotating reference
frame (p. 134).
/batch,list
/PREP7
!*
et,1,185
keyopt,1,2,2
mp,ex,1,2.07e11
mp,nuxy,1,0.28
mp,dens,1,7860
!* Parameters
thick1 = 0.03810
thick = thick1
hthick = thick/2.0
radius = 0.09525
inradius = radius - hthick
outradius = radius + hthick
length = 0.254
!*
cylind,inradius,outradius,0,length,0,90
nummrg,kp
esize,thick
vmesh,all
nsel,all
finish
!*
Example Coriolis Analysis
/SOLU
antype,modal
modopt,qrdamp,20
omega,0,0,314.16,1
!
! Apply Coriolis effect and use default
! rotating reference frame
coriolis,on
!
solve
finish

in more detail.

1. Define elements and material properties. ET,…
MP,…
2. Set parameters. thick1 = 0.03810
thick = thick1
hthick = thick/2.0
radius = 0.09525
inradius = radius
- hthick
outradius =
radius + hthick
length = 0.254
3. Set boundary conditions. CYLIND,...
NUMMRG,...
ESIZE,...
VMESH,...
NSEL,...
4. Set the analysis type (modal in this case) and use the QRDAMP ANTYPE,MODAL
eigensolver. Get 20 complex eigensolutions.
MODOPT,QRDAMP,20
6. Define the angular rotation velocity and the number of modes OMEGA,…
expanded.
MXPAND,…
5. Include the Coriolis effect in a rotating reference frame (p. 134). CORIOLIS,ON
7. Solve. SOLVE
The non-zero complex frequencies should match the following:
With Coriolis Without Coriolis

Effect Applied Effect Applied
----------------------------------------------------------
0.0000000 2661.9384 2700.8924 j
0.0000000 2740.4150 2700.8924 j
0.0000000 3043.0948 3078.1392 j
0.0000000 3113.5872 3078.1392 j
0.0000000 6342.7190 6362.7716 j
0.0000000 6365.8292 6362.7716 j
0.0000000 6382.8876 6366.7082 j
0.0000000 6593.8155 6626.0560 j
0.0000000 6658.4573 6626.0560 j
0.0000000 7183.0372 7216.0329 j
6.7. Example Unbalance Harmonic Analysis

Following is an example harmonic analysis with unbalance force (p. 133). It illustrates the use of the
SYNCHRO command and the following postprocessing capabilities:
• Orbits plotting (PLORB)
• Whirl animation (ANHARM)

The structure is a two-spool rotor on symmetric bearings. Both spools have two rigid disks. The inner
spool rotates at up to 14,000 RPM and the outer spool rotates 1.5 times faster.
Disks are not visible in the plot because they are MASS21 elements.

The unbalance is located on the second disk of the inner spool and harmonic response is calculated.
Outputs are as follows:
• Amplitude at nodes 7 and 12 as a function of the frequency
• Orbit plot at a given frequency
• Animation of the whirl at a given frequency
Example Unbalance Harmonic Analysis

Use this input file to perform the example unbalance harmonic analysis of rotating structure using a
stationary reference frame (p. 130).
/batch,list
/title, twin spools - unbalance (inner spool) response
/PREP7
mp,EX ,1,2.1e+11
mp,DENS,1,7800
mp,PRXY,1,0.3
! shaft
et,1,188,,,2
sectype,1,beam,csolid
secdata,0.01524,32
sectype,2,beam,ctube
secdata,0.0254,0.03048,32
! disks
et,2,21
r,3,10.51,10.51,10.51,8.59e-2,4.295e-2,4.295e-2
r,4,7.01 ,7.01 ,7.01 ,4.29e-2,2.145e-2,2.145e-2
r,5,3.5 ,3.5 ,3.5 ,2.71e-2,1.355e-2,1.355e-2
r,6,7.01 ,7.01 ,7.01 ,6.78e-2,3.390e-2,3.390e-2
! bearings
et,3,214,,1
r,7 ,2.63e+7 ,2.63e+7
r,8 ,1.75e+7 ,1.75e+7
r,9 ,0.875e+7,0.875e+7
r,10,1.75e+7 ,1.75e+7
! nodes
n,1
n,2 ,0.0762
n,3 ,0.1524
n,4 ,0.2413
n,5 ,0.32385
n,6 ,0.4064
n,7 ,0.4572
n,8 ,0.508
n,9 ,0.1524
n,10,0.2032
n,11,0.2794
n,12,0.3556
n,13,0.4064
! bearings second nodes
n,101, ,0.05
n,108,0.508 ,0.05
n,109,0.1524,0.05
! components elements
type,1
secn,1
e,1,2
egen,7,1,1
type,2
real,3
e,2
real,6
e,7
cm,inSpool,elem
type,1
secn,2
e,9,10
egen,4,1,10
type,2
real,4
e,10
real,5
e,12
esel,u,,,inSpool
cm,outSpool,elem
allsel
! bearings
type,3
real,7
e,1,101
real,8
e,9,109
real,9
e,6,13
real,10
e,8,108
! boundary conditions
d,all,ux,,,,,rotx
d,101,all
d,108,all
d,109,all
! unbalance forces (eccentric mass * radius)
f0 = 70e-6
f,7,fy,f0
f,7,fz,,-f0
fini
/SOLU
antype,harmic
synchro,,inSpool
nsubst,500
harfrq,,14000/60 ! implicitly defines OMEGA for Coriolis calculation
kbc,1
dmpstr,0.01
cmomega,inSpool,100.
cmomega,outSpool,150.
coriolis,on,,,on
solve
fini
! output: amplitude at nodes 7 and 12 as a function of the frequency
/POST26
nsol,2,7,U,Y,UY
nsol,3,7,U,Z,UZ
realvar,4,2,,,UYR
realvar,5,3,,,UZR
prod,6,4,4,,UYR_2
prod,7,5,5,,UZR_2
add,8,6,7,,UYR_2+UZR_2
sqrt,9,8,,,AMPL7
!
nsol,2,12,U,Y,UY
nsol,3,12,U,Z,UZ
realvar,4,2,,,UYR
realvar,5,3,,,UZR
prod,6,4,4,,UYR_2
prod,7,5,5,,UZR_2
add,8,6,7,,UYR_2+UZR_2
sqrt,10,8,,,AMPL12
!
/gropt,logy,1
/yrange,1.e-7,1.e-3
plvar,9,10
fini
! output: orbit plot at the given frequency
/POST1
set,1,262
/view,,1,1,1
plorb
! output: animation of the whirl at the given frequency
SET,1,500
!reset for subsequent post processing
/eshape,1
/gline,,-1
plnsol,u,sum
anharm

in more detail.

1. Define material properties. MP,EX,1,2.1e+11
MP,DENS,1,7800
MP,PRXY,1,0.3
2. Define element types, sections, real and nodes. ET,…
SECTYPE,…
SECDATA,…
R,…
N,…
3. Define first component named inSpool. TYPE,1
SECNUM,1
E,1,2
EGEN,7,1,1
TYPE,2
REAL,3
E,2
REAL,6
E,7
CM,inSpool,ELEM
4. Define second component named outSpool. TYPE,1
SECNUM,2
E,9,10
EGEN,4,1,10
TYPE,2
REAL,4
E,10
REAL,5

E,12
ESEL,u,,,inSpool
CM,outSpool,ELEM
ALLSEL
6. Define bearing elements. TYPE,3
REAL,7
E,1,101
REAL,8
E,9,109
REAL,9
E,6,13
REAL,10
E,8,108
5. Set boundary conditions. D,...
7. Define the unbalance forces (eccentric mass * radius) f0 = 70e-6
at node 7.
F,7,FY,f0
F,7,FZ,,-f0
8. Set the solution options. ANTYPE,HARMIC
• Harmonic analysis SYNCHRO,,inSpool
• Unbalance on component inSpool NSUBST,500
• 500 substeps HARFRQ,,14000/60
• Frequency at end of range is 14000/60 Hz KBC,1
• Step loading DMPSTR,0.01
• Damping ratio is 1% CMOMEGA,inSpool,100.
• Rotational velocity of component inSpool CMOMEGA,outSpool,150.
• Rotational velocity of component outSpool CORIOLIS,ON,,,ON
SOLVE

• Coriolis force in stationary reference frame (p. 130)
Note
The rotational velocities (CMOMEGA) are

not applied in the usual way. Rather,
ANSYS considers only their direction
cosines and the velocity ratio between
spools. For more information, see the
documentation for the SYNCHRO
command.
9. First output (in POST26). /POST26
• The maximum amplitude of the displacement of nodes NSOL,2,7,U,Y,UY

7 (AMPL7) is calculated in variable 9.
NSOL,3,7,U,Z,UZ
• The maximum amplitude of the displacement of nodes
12 (AMPL12) is calculated in variable 10. REALVAR,4,2,,,UYR
• Set logY scale. REALVAR,5,3,,,UZR
• Set a specific scale range in Y. PROD,6,4,4,,UYR_2
• Plot variables 9 and 10. PROD,7,5,5,,UZR_2
ADD,8,6,7,,UYR_2+UZR_2
SQRT,9,8,,,AMPL7
NSOL,2,12,U,Y,UY
NSOL,3,12,U,Z,UZ
REALVAR,4,2,,,UYR
REALVAR,5,3,,,UZR
PROD,6,4,4,,UYR_2
PROD,7,5,5,,UZR_2
ADD,8,6,7,,UYR_2+UZR_2
SQRT,10,8,,,AMPL12
/GROPT,LOGY,1
/YRANGE,1.e-7,1.e-3

PLVAR,9,10
10. Second output (in POST1). /POST1
• Read load step 1 and substep 262 from results file. SET,1,262
• Change the view. /VIEW,,1,1,1
• Plot the orbits at each rotating node. PLORB
11. Third output. /ESHAPE,1
• Display takes dimensions into account. /GLINE,,-1
• No element outline. PLNSOL,U,SUM
• Display the displacements as contours. ANHARM
• Animate the displays (defined by the last set command

and last display command).
The outputs of your analysis should match those shown here:
You can obtain the two critical frequencies (at which the amplitudes are largest) via
PRCAMP with SLOPE = 1.0.
Orbits are represented in different colors. Orbits from the inner spool appear in sky blue,
and from the outer spool in purple. Spool lines appear in dark blue.
The following demo is presented as an animated GIF. View online if you are reading the PDF version of the
help. Interface names and other components shown in the demo may differ from those in the released
product.
The animation of the whirls shown here is the third output resulting from the example
harmonic analysis with unbalance.
Chapter 7: Submodeling
Submodeling is a finite element technique that you can use to obtain more accurate results in a partic-
ular region of a model. A finite element mesh may be too coarse to produce satisfactory results in a
given region of interest. The results away from this region, however, may be satisfactory.
Reanalyzing the entire model using a greater mesh refinement in order to obtain more accurate results
in one particular region is time-consuming and costly. Instead, you can use submodeling to generate
an independent, more finely meshed model of only the region (submodel) of interest and then analyze
it.
The following submodeling topics are available:

7.1. Understanding Submodeling
7.2. Using Submodeling
7.3. Example Submodeling Analysis Input
7.4. Shell-to-Solid Submodels
7.5. Where to Find Examples
7.1. Understanding Submodeling

In finite element analysis, the finite element mesh is sometimes too coarse to produce satisfactory results
in a specific region of interest, such as a stress concentration region in a stress analysis as shown in
Figure 7.1: Submodeling of a Pulley (p. 151). The figure illustrates how to deal with the problem by using
submodeling to create a finer mesh on the region (submodel) of interest.
Figure 7.1: Submodeling of a Pulley
Submodeling of a pulley hub and spokes: (a) coarsely meshed model, and (b) finely
meshed submodel (shown superimposed over coarse model)
Submodeling is also known as the cut-boundary displacement method (also known as the specified
boundary displacement method). The cut boundary is the boundary of the submodel which represents
Submodeling
a cut through the coarse model. Displacements calculated on the cut boundary of the coarse model
are specified as boundary conditions for the submodel.
Submodeling is based on St. Venant's principle, which states that if an actual distribution of forces is
replaced by a statically equivalent system, the distribution of stress and strain is altered only near the
regions of load application. The principle implies that stress concentration effects are localized around
the concentration; therefore, if the boundaries of the submodel are far enough away from the stress
concentration, reasonably accurate results can be calculated in the submodel.
The program does not restrict submodeling to structural (stress) analyses only. Submodeling is effective
in other disciplines as well. For example, in a magnetic field analysis, you can use submodeling to cal-
culate more accurate magnetic forces in a region of interest.
Aside from the obvious benefit of yielding more accurate results in a region of your model, the submod-
eling technique has other advantages:
• It reduces, or even eliminates, the need for complicated transition regions in solid finite element
models.
• It enables you to experiment with different designs for the region of interest (different fillet radii, for
example).
• It helps you in demonstrating the adequacy of mesh refinements.
The following restrictions apply to submodeling:
• It is valid only for solid elements and shell elements.
• The principle behind submodeling assumes that the cut boundaries are far enough away from the
stress concentration region. You must verify that this assumption is adequately satisfied.
7.1.1. Nonlinear Submodeling

For load-history-dependent problems (for example, when plastic materials exist), you must cut boundary
conditions from the coarse model at multiple substeps to simulate the load history dependency in the
fine-mesh model analysis.
In a fine-mesh-model analysis, the cut boundary conditions must be applied as loads at multiple load
steps. The more boundary cutting you do, the more accurate are the results of the fine-mesh-model
analysis.
7.2. Using Submodeling

The process for using submodeling is as follows:
1. Create and analyze the coarse model (p. 153).
2. Create the submodel (p. 154).
3. Perform cut-boundary interpolation (p. 155).
4. Analyze the submodel (p. 156).
5. Verify that the distance between the cut boundaries and the stress concentration is adequate (p. 158).
Using Submodeling
The steps are explained in detail next.
7.2.1. Create and Analyze the Coarse Model

The first step is to model the entire structure and analyze it.
To easily identify this initial model, it is referred to as the coarse model. This does not mean that the
mesh refinement is coarse, only that it is relatively coarse compared to the submodel.
The analysis type may be static (steady-state) or transient and follows the same procedure as described
in the individual analysis guides. Some additional points to keep in mind are listed below.
Jobname - Use different job names for the coarse model and the submodel as a precaution against
overwriting files, and to easily refer to files from the coarse model during cut-boundary interpolation.
To specify a job name, use one of these methods:
Command(s): /FILNAME
GUI: Utility Menu> File> Change Jobname
Element Types -- Only solid and shell elements support the submodeling technique. Your analysis may
include other element types (such as beams added as stiffeners), but the cut boundary should only
pass through the solids or shells.
A special technique called shell-to-solid submodeling (p. 165) allows you to build your coarse model with
shell elements and your submodel with 3-D solid elements. This technique is discussed in Shell-to-Solid
Submodels (p. 165).
Modeling -- In many cases, the coarse model need not include local details such as fillet radii, as shown
in the following figure. However, the finite element mesh must be fine enough to produce a reasonably
accurate degree of freedom solution. This is important because the results of the submodel are almost
entirely based on interpolated degree of freedom results at the cut boundary.
Figure 7.2: Coarse Model
Initial, coarse model may not need to include many details
Files - Both the results file (Jobname.RST, Jobname.RMG, etc.) and the database file (Jobname.DB,
containing the model geometry) are required from the coarse-model analysis. Be sure to save the
database after solving the coarse model, but before going on to create the submodel. To save the
database, use either of these methods:
Command(s): SAVE
Submodeling
GUI: Utility Menu> File> Save as

Utility Menu> File> Save as Jobname.db
7.2.2. Create the Submodel

The submodel is completely independent of the coarse model; therefore, the first step after the initial
analysis is to clear the database at the Begin level. To clear the database at the Begin level, use one of
these methods:
Command(s): /CLEAR
GUI: Utility Menu> File> Clear & Start New
Also, be sure to use a different job name for the submodel so that the coarse-model files are not over-
written. To specify a job name, use one of these methods:
Command(s): /FILNAME
GUI: Utility Menu> File> Change Jobname
Then enter PREP7 and build the submodel. Some points to remember are:
• Use the same element type (solid or shell) that was used in the coarse model. Also, specify the same
element real constants (such as shell thickness) and material properties. (Shell-to-solid submodel-
ing (p. 165) allows you to switch from shell elements in the coarse model to 3-D solid elements in the
submodel.)
• The location of the submodel (with respect to the global origin) must be the same as the corresponding
portion of the coarse model, as shown in Figure 7.3: Submodel Superimposed Over Coarse Model (p. 154).
Figure 7.3: Submodel Superimposed Over Coarse Model
• Specify appropriate node rotations. Node rotation angles on cut boundary nodes should not be changed
after they have been written to the node file in interpolation step 1 (see Perform Cut-Boundary Inter-
polation (p. 155)). To specify node rotations, use one of these methods:
Command(s): NROTAT
GUI: Main Menu> Preprocessor> Modeling> Create> Nodes> Rotate Node CS> To Active CS
Main Menu> Preprocessor> Modeling> Move/Modify> Rotate Node CS> To Active CS
Be aware that node rotation angles might be changed by application of nodal constraints (DSYM), by
transfer of line constraints (SFL), or by transfer of area constraints (SFA), as well as by more obvious
methods (NROTAT and NMODIF).
The presence or absence of node rotation angles in the coarse model has no effect upon the submodel.
Using Submodeling
Loads and boundary conditions for the submodel are covered in subsequent steps.
7.2.3. Perform Cut-Boundary Interpolation

This is the key step in submodeling. You identify the nodes along the cut boundaries, and the program
calculates the degree-of-freedom values (displacements, potentials, etc.) at those nodes by interpolating
results from the full (coarse) model. For each node of the submodel along the cut boundary, the program
uses the appropriate element from the coarse mesh to determine the degree-of-freedom values. These
values are then interpolated onto the cut-boundary nodes using the element shape functions.
The following tasks are involved in performing the cut-boundary interpolation:
1. Identify and write the cut-boundary nodes of the submodel to a file (Jobname.NODE by default).
You can do this in PREP7 by selecting nodes along the cut boundaries and then using one of these
methods to write the nodes to a file:
Command(s): NWRITE
GUI: Main Menu> Preprocessor> Modeling> Create> Nodes> Write Node File
Here is an example of issuing the NWRITE command:

NSEL,... ! Select nodes along cut boundaries
NWRITE ! Writes all selected nodes to Jobname.NODE
Figure 7.4: Cut Boundaries on the Submodel
At this point, it is worthwhile to discuss temperature interpolation. In an analysis with temperature-

dependent material properties, or in a thermal-stress analysis, the temperature distribution
must be the same between the coarse model and the submodel. For such cases, you must also
interpolate the temperatures from the coarse model to all nodes in the submodel. To do so,
select all submodel nodes and write them to a different file using NWRITE,Filename,Ext.
Specify a file name; otherwise, your file of cut-boundary nodes will be overwritten. Step 7 shows
the command to do temperature interpolation.
2. Restore the full set of nodes, write the database to Jobname.DB, and leave PREP7. You must write
the database to Jobname.DB because you need to continue with the submodel later.
To restore the full set of nodes, use one of these methods:

Command(s): ALLSEL
GUI: Utility Menu> Select> Everything
To write the database to Jobname.DB, use one of these methods:

Command(s): SAVE
GUI: Utility Menu> File> Save as Jobname.db
3. To do the cut-boundary interpolation (and the temperature interpolation), the database must contain
the geometry for the coarse model. Therefore, you must resume the database using one of the
methods shown below, making sure to identify the name of the coarse-model database file:
Command(s): RESUME
GUI: Utility Menu> File> Resume from
Submodeling
For example, if the job name for the coarse-model analysis was COARSE, issue the command
RESUME,COARSE,DB.
4. Enter POST1, which is the general postprocessor (/POST1 or menu path Main Menu> General Post-
proc). Interpolation can only be performed in POST1.
5. Point to the coarse results file (FILE or menu path Main Menu> General Postproc> Data & File Opts).
6. Read in the desired set of data from the results file (SET or menu path Main Menu> General Postproc>
Read Results> option).
7. Initiate cut-boundary interpolation. To do so, use one of these methods:

Command(s): CBDOF
GUI: Main Menu> General Postproc> Submodeling> Interpolate DOF
By default, the CBDOF command assumes that the cut-boundary nodes are on file Job-
name.NODE. The program then calculates the cut-boundary degree-of-freedom values and
write them in the form of D commands to the file Jobname.CBDO.
To do temperature interpolation, use one of these methods, being sure to identify the name
of the file containing all submodel nodes:
Command(s): BFINT
GUI: Main Menu> General Postproc> Submodeling> Interp Body Forc
Interpolated temperatures are written in the form of BF commands to the file Jobname.BFIN.
If real and imaginary data are involved, steps 6 and 7 must be performed twice. Issue the SET
command to get the real data, followed by the interpolation step (CBDOF and/or BFINT). Issue
the SET command with the field set to 1 to get the imaginary data, and repeat the interpolation
step, this time writing the interpolated imaginary data to a different file.
For load-history-dependent problems, steps 6 and 7 can be performed multiple times at different
data sets or substeps. The cut-boundary degree-of-freedom values of each data set will reside
in the same file but in different data blocks, separated by a :CBnn label (where nn is the cu-
mulative iteration number of the results set used).
8. All interpolation work is now done, so leave POST1 (FINISH) and restore the submodel database (RE-
SUME or menu path Utility Menu> File> Resume from). (Be sure to use the submodel database job
name.)
7.2.4. Analyze the Submodel

In this step, you define the analysis type and analysis options, apply the interpolated degree-of-freedom
values (and temperatures), define other loads and boundary conditions, specify load step options, and
obtain the submodel solution.
The first step is to enter the solution processor (/SOLU or menu path Main Menu> Solution).
Then define the appropriate analysis type (usually static) and analysis options.
To apply the cut-boundary degree-of-freedom constraints, simply read in the file of D commands (created
by CBDOF) using one of these methods (for example, /INPUT,,CBDO):
Command(s): /INPUT
GUI: Utility Menu> File> Read Input from
Using Submodeling
Similarly, to apply the interpolated temperatures, read in the file of BF commands (created by BFINT)
using one of these methods (for example, /INPUT,,BFIN):
Command(s): /INPUT
If real and imaginary data are involved, first read in the file(s) containing the real data, specify whether
degree-of-freedom constraint values and/or nodal body force loads are to be accumulated, and then
read in the file containing the imaginary data.
Specify that degree-of-freedom constraint values are to be accumulated:

Command(s): DCUM,ADD
GUI: Main Menu> Preprocessor> Loads> Define Loads> Settings> Replace vs Add> Constraints
Main Menu> Solution> Define Loads> Settings> Replace vs Add> Constraints
Specify that nodal body force loads are to be accumulated:

Command(s): BFCUM,,ADD
GUI: Main Menu> Preprocessor> Loads> Define Loads> Settings> Replace vs Add> Nodal Body
Ld
Main Menu> Solution> Define Loads> Settings> Replace vs Add> Nodal Body Ld
Be sure to reset the DCUM and BFCUM commands to their default status before proceeding.
It is important that you duplicate on the submodel any other loads and boundary conditions that existed
on the coarse model. Examples are symmetry boundary conditions, surface loads, inertia forces (such
as gravity), concentrated force loads, etc. (see Figure 7.5: Loads on the Submodel (p. 157)).
Then specify load step options (such as output controls) and initiate solution calculations using one of
these methods:
Command(s): SOLVE
GUI: Main Menu> Solution> Solve> Current LS
For most problems, exit the solution processor (FINISH) after the solution has completed.
For load-history-dependent problems, apply the cut-boundary degree-of-freedom constraints in the

next data block in the file created by cut-boundary interpolation (CBDOF), and solve (SOLVE) as a new
load step. Because it is a new load step, for any rate-dependent materials and transient analysis, the
time value must match the time when cut-boundary interpolation occurred. This step can be repeated
until all cut-boundary degree-of-freedom constraints are applied. Then, exit the solution processor.
The overall data flow for submodeling (without temperature interpolation) is shown in Figure 7.6: Data
Flow Diagram for Submodeling (Without Temperature Interpolation) (p. 158).
Figure 7.5: Loads on the Submodel
Submodeling
Figure 7.6: Data Flow Diagram for Submodeling (Without Temperature Interpolation)
7.2.5.Verify the Distance Between the Cut Boundaries and the Stress Concen-
tration
The final step is to verify that the cut boundaries of the submodel are far enough away from the con-
centration. You can do this by comparing results (stresses, magnetic flux density, etc.) along the cut
boundaries with those along the corresponding locations of the coarse model. If the results are in good
agreement, it indicates that proper cut boundaries have been chosen; otherwise, you will need to recreate
and reanalyze the submodel with different cut boundaries further away from the region of interest.
An effective way to compare results is to obtain contour displays and path plots, as shown in Fig-
ure 7.7: Contour Plots to Compare Results (p. 159) and Figure 7.8: Path Plots to Compare Results (p. 159).
Example Submodeling Analysis Input
Figure 7.7: Contour Plots to Compare Results
Figure 7.8: Path Plots to Compare Results
7.3. Example Submodeling Analysis Input

The following example submodeling analysis input listings are available:
7.3.1. Submodeling Analysis Input: No Load-History Dependency
7.3.2. Submodeling Analysis Input: Load-History Dependency
7.3.1. Submodeling Analysis Input: No Load-History Dependency

The following example submodeling input does not include load-history dependency:
! Start with coarse model analysis:
/FILNAME,coarse ! Jobname = coarse
/PREP7 ! Enter PREP7
...
... ! Generate coarse model
...
FINISH
Submodeling
/SOLU ! Enter SOLUTION

ANTYPE,... ! Analysis type and analysis options
...
D,... ! Loads and load step options
DSYMM,...
ACEL,...
...
SOLVE ! Coarse model solution
! Results are on coarse.rst (or rmg, etc.)
SAVE ! Coarse model database file coarse.db
FINISH
! Create submodel:
/CLEAR ! Clear the database (or exit program and re-enter)
/FILNAME,submod ! New jobname = submod
/PREP7 ! Re-enter PREP7
...
... ! Generate submodel
...
! Perform cut-boundary interpolation:

NSEL,... ! Select nodes on cut boundaries
NWRITE ! Write those nodes to submod.node
ALLSEL ! Restore full sets of all entities
NWRITE,temps,node ! Write all nodes to temps.node (for
! temperature interpolation)
SAVE ! Submodel database file submod.db
FINISH
RESUME,coarse,db ! Resume coarse model database (coarse.db)

/POST1 ! Enter POST1
FILE,coarse,rst ! Use coarse model results file
SET,... ! Read in desired results data
CBDOF ! Reads cut-boundary nodes from submod.node and
! writes D commands to submod.cbdo
BFINT,temps,node ! Reads all submodel nodes from temps.node and
! writes BF commands to submod.bfin (for
FINISH ! End of interpolation
RESUME ! Resume submodel database (submod.db)

ANTYPE,... ! Analysis type and options
...
/INPUT,submod,cbdo ! Cut-boundary DOF specifications
/INPUT,submod,bfin ! Interpolated temperature specifications
DSYMM,... ! Other loads and load step options
ACEL,...
...
SOLVE ! Submodel solution
FINISH

...
... ! Verify submodel results
...
FINISH
7.3.2. Submodeling Analysis Input: Load-History Dependency

The following example submodeling input includes load-history dependency:
! Start with coarse model analysis:
/FILNAME,coarse ! Jobname = coarse
/PREP7 ! Enter PREP7
...
... ! Generate coarse model
...
FINISH
ANTYPE,... ! Analysis type and analysis options
...
D,... ! Loads and load step options

DSYMM,...
ACEL,...
...
SOLVE ! Coarse model solution
! Results are on coarse.rst (or rmg, etc.)
SAVE ! Coarse model database file coarse.db
FINISH
! Create submodel:
/CLEAR ! Clear the database (or exit program and re-enter)
/FILNAME,submod ! New jobname = submod
/PREP7 ! Re-enter PREP7
...
... ! Generate submodel
...
! Perform cut-boundary interpolation:
NSEL,... ! Select nodes on cut boundaries
NWRITE ! Write those nodes to submod.node
ALLSEL ! Restore full sets of all entities
NWRITE,temps,node ! Write all nodes to temps.node (for
SAVE ! Submodel database file submod.db
FINISH
RESUME,coarse,db ! Resume coarse model database (coarse.db)
FILE,coarse,rst ! Use coarse model results file
SET,... ! Read in desired results data
SET,... ! Read in another desired results data
... This(SET,CBDOF,BFINT)can be repeated many time
FINISH ! End of interpolation
RESUME ! Resume submodel database (submod.db)
ANTYPE,... ! Analysis type and options
...
/INPUT,submod,cbdo ! Cut-boundary DOF specifications
/INPUT,submod,bfin ! Interpolated temperature specifications
DSYMM,... ! Other loads and load step options
ACEL,...
...
TIME
SOLVE ! Submodel solution of first steps
/INPUT,submod,cbdo ! Cut-boundary DOF from another set
/INPUT,submod,bfin ! Interpolated temperature from another set
TIME
SOLVE SOLVE as another load step
….. This (/INPUT..SOLVE) can be repeated many time
FINISH
...
... ! Verify submodel results
...
FINISH
Following is a simple model of a plate with a hole in its middle, with applied displacements in the x
direction. To simulate load-history dependency, cut boundary conditions are done at different substeps
of the coarse-mesh analysis, then applied as different load steps in the submodeling analysis. The ma-
terial is assumed to be rate-dependent anisotropic plastic with isotropic hardening.
The problem is solved via the coarse-mesh model, the submodel, and the fine-mesh model, as shown
in this figure:
Submodeling
Figure 7.9: Coarse-Mesh Model, Submodel, and Fine-Mesh Model
Both the coarse-mesh model and the fine-mesh model are solved in 20 substeps. The fine-mesh model
yields a benchmark solution for comparison purposes.
The submodel analysis is performed in four solutions, as follows:
1. With cut-boundary conditions at only the last substep of the coarse-mesh analysis, solved in one load
step with 20 substeps.
2. With cut-boundary conditions at five substeps (that is, at every four substeps) of the coarse-mesh
analysis, solved in five load steps each with about four substeps.
3. With cut-boundary conditions at 10 substeps (that is, at every two substeps) of the coarse-mesh ana-
lysis, solved in 10 load steps, each with about two substeps.
4. With cut-boundary conditions at all 20 substeps of the coarse-mesh analysis, solved in 20 load steps,
each with about two substeps.
The specified load steps and substeps make the size of the substep in submodel solutions close to
those in whole-model solutions.
The following figure shows the equivalent plastic strains at point P in each solution:
Figure 7.10: Equivalent Plastic Strain Through Various Cut-Boundary Conditions and Load Steps
When boundary conditions are cut at more substeps, the results are closer to the fine mesh (the correct
solution).
The following figure shows the contour plots of equivalent plastic strain at the end of loading for each
of the four solutions:
Submodeling
Figure 7.11: Equivalent Plastic Strain Distributions in a Submodeling Analysis with Load-History
Dependency
Shell-to-Solid Submodels
The results with 20 boundary-condition cuttings most resemble the fine-mesh model.
As the example indicates, boundary conditions should be cut from more substeps of the coarse solution
to reflect load-history dependency more accurately.
7.4. Shell-to-Solid Submodels

In the shell-to-solid submodeling technique, the coarse model is a shell model, and the submodel is a
3-D solid model, as shown in this example:
Submodeling
Figure 7.12: 3-D Solid Submodel Superimposed on Coarse Shell Model
The procedure for shell-to-solid submodeling is essentially the same as that for solid-to-solid submod-
eling, with these exceptions:
• Shell-to-solid submodeling is activated by setting KSHS to 1 on the CBDOF command (Main Menu>
General Postproc> Submodeling> Interpolate DOF) and the BFINT command (Main Menu> General
Postproc> Submodeling> Interp Body Forc). This feature is not applicable to offsets used with
SHELL181 (SECOFFSET), or SHELL281 (SECOFFSET).
• Cut boundaries on the submodel are the end planes that are normal to the shell plane (see Fig-
ure 7.13: Node Rotations (p. 167)). Nodes on these cut boundaries are written to the node file (NWRITE)
(Main Menu> Preprocessor> Modeling> Create> Nodes> Write Node File).
• To determine the degree-of-freedom values at a cut-boundary node (CBDOF), the program first projects
the node onto the nearest element in the shell plane. The degree-of-freedom values of this projected
point are then calculated by interpolation and assigned to the corresponding node. Interpolated tem-
peratures (BFINT) are calculated based on the average temperature at the midplane of the nearest
shell element.
Note
The nodes on the cut boundary must lie within a distance of 0.75 times the average
thickness of the nearest shell element, as shown in Figure 7.13: Node Rotations (p. 167).
That is, the submodel should be approximately centered on the coarse model.
• In a structural analysis, only translational displacements are calculated for the cut-boundary nodes, but
their values are based on both the translations and rotations of the projected point. Also, the node is
rotated such that the nodal UY direction is always perpendicular to the shell plane, as shown in Fig-
Where to Find Examples
ure 7.13: Node Rotations (p. 167). A UY constraint is calculated only for nodes that are within 10 percent
of the average shell element thickness from the shell plane, preventing overconstraint of the submodel
in the transverse direction.
Figure 7.13: Node Rotations
Node rotations: (a) before CBDOF command, (b) after CBDOF command
• The .CBDO file written by the CBDOF command consists of two blocks:
– a block of NMODIF commands (indicating node rotation angles) and DDELE commands (to delete
UY constraints)
– a block of D commands (to apply the interpolated degree-of-freedom values).
The two blocks are separated by a /EOF command and a :CBnn label (where nn is the cumulative iter-
ation number of the results set used).
• You must read in the .CBDO file in PREP7, because the NMODIF command is only valid in PREP7. To
do so, enter the preprocessor, then use one of these methods:
Command(s): /INPUT
Because the two blocks of commands are separated by a /EOF command, it is necessary to read in the
.CBDO file twice. The second time you read in the file, use the LINE field on /INPUT ("Optional line
number or label" in the GUI) to instruct the program to read the file starting with the :CBnn label, as
shown below:
/PREP7! The .CBDO file must be read in PREP7
/INPUT,,cbdo ! Reads Jobname.cbdo up to the /EOF command
/INPUT,,cbdo,,:cb1 ! Reads same file from the label :cb1

The Mechanical APDL Verification Manual consists of test case analyses demonstrating the analysis cap-
abilities of the program. While these test cases demonstrate solutions to realistic analysis problems, the
Mechanical APDL Verification Manual does not present them as step-by-step examples with lengthy data
input instructions and printouts. However, most users who have at least limited finite element experience
should be able to fill in the missing details by reviewing each test case's finite element model and input
data with accompanying comments.
Submodeling
The Mechanical APDL Verification Manual contains the following submodeling test case:
VM142 - Stress Concentration at a Hole in a Plate
Chapter 8: Element Birth and Death
If material is added to or removed from a system, certain elements in your model may become come
into existence or cease to exist. In such cases, you can use element birth and death options to activate
or deactivate selected elements, respectively.
The element birth and death feature is useful for analyzing excavation (as in mining and tunneling),
staged construction (as in shored bridge erection), sequential assembly (as in fabrication of layered
computer chips), and many other applications in which you can easily identify activated or deactivated
elements by their known locations.
The birth and death feature is available in the ANSYS Mechanical Enterprise product.
The following additional element birth and death topics are available:
8.1. Elements Supporting Birth and Death
8.2. Understanding Element Birth and Death
8.3. Element Birth and Death Usage Hints
8.4. Using Birth and Death
8.1. Elements Supporting Birth and Death

If an element supports birth and death, it is indicated in the “Special Features” section of the document-
ation for that element.
User-defined elements can also be given the birth and death capability.
In some circumstances, an element's birth and death status depend upon a program-calculated quantity,
such as temperature, stress, and strain. You can issue commands such as ETABLE and ESEL to determine
the value of such quantities in selected elements, and to change the status (melted, solidified, ruptured,
etc.) of those elements accordingly. This capability is useful for modeling effects due to phase changes
(as in welding processes, when structurally inactive molten material solidifies and becomes structurally
active), failure-surface propagation, and other analysis-dependent element changes.
8.2. Understanding Element Birth and Death

To achieve the "element death" effect, the program does not actually remove "killed" elements. Instead,
it deactivates them by multiplying their stiffness (or conductivity, or other analogous quantity) by a
severe reduction factor (ESTIF). This factor is set to 1.0E-6 by default, but can be given other values.
(For more information, see Apply Loads and Obtain the Solution (p. 171).)
Element loads associated with deactivated elements are zeroed out of the load vector, however, they
still appear in element-load lists. Similarly, mass, damping, specific heat, and other such effects are set
to zero for deactivated elements. The mass and energy of deactivated elements are not included in the
summations over the model. An element's strain is also set to zero as soon as that element is killed.
In like manner, when elements are "born," they are not actually added to the model; they are simply
reactivated. You must create all elements, including those to be born in later stages of your analysis,
Element Birth and Death
while in PREP7. You cannot create new elements in SOLUTION. To "add" an element, you first deactivate
it, then reactivate it at the proper load step.
When an element is reactivated, its stiffness, mass, element loads, etc. return to their full original values.
Elements are reactivated with no record of strain history (or heat storage, etc.); that is, a reactivated
element is generally strain-free. Initial strain defined as a real constant, however, is not be affected by
birth and death operations.
Unless large-deformation effects are activated (NLGEOM,ON), some element types will be reactivated
in their originally specified geometric configuration. (Large-deformation effects should be included to
obtain meaningful results.)
Thermal strains are computed for newly-activated elements based on the current load step temperature
and the reference temperature. Thus, newborn elements with thermal loads may not be stress-free as
intended. The material property REFT can be used instead of the global TREF to specify material-depend-
ent reference temperatures, allowing you to specify the activation temperature as a stress-free temper-
ature.
8.3. Element Birth and Death Usage Hints

The following guidelines apply to analyses using the element birth and death capability:
• Constraint equations (CE, CEINTF, etc.) cannot be applied to inactive DOFs. Inactive DOFs occur when a
node has no active ("alive") elements attached to it.
• You can model stress-relieving operations (such as annealing) by deactivating and then reactivating elements.
• In nonlinear analyses, be careful not to deactivate or reactivate elements in such a way as to create singular-
ities (such as sharp re-entrant corners in a structural analysis) or sudden large changes in stiffness. Such
situations are likely to cause convergence difficulties.
• Killing contact/target elements or their underlying elements will cause the status of the contact pair to
change to far field contact (open and not near contact), even for bonded contact. You may need to kill both
the contact/target elements and their underlying elements to reestablish the pre-death contact status when
the elements are later reactivated.
• The full Newton-Raphson option with adaptive descent activated (NROPT,FULL,,ON) often yields good results
in analyses employing element birth and death.
• You can retrieve a parameter whose value will indicate the status (active or inactive) of an element
(*GET,Par,ELEM, n, ATTR, LIVE) This parameter could be used in APDL logical branching (*IF, etc.) or in other
applications for which you need to monitor the birth-and-death status of an element.
• Since a Multiframe restart will recreate the database using the *.rdb file, the elements selected in /POST1
can not be killed in a multiframe restart.
• The load-step file method (LSWRITE) for solving multiple load steps cannot be used with the birth-death
option, because it will not write the status of deactivated or reactivated elements to the load step file. Birth
and death analyses having multiple load steps must therefore be performed using a series of explicit SOLVE
commands.
Using Birth and Death
8.3.1. Changing Material Properties

You might be tempted to deactivate or reactivate elements by changing their material properties via
the MPCHG command.
You must proceed cautiously if you attempt such a procedure. The safeguards and restrictions applying
to "killed" elements do not apply to elements that have had their material properties changed in the
solution phase of the analysis. (Element forces will not be automatically zeroed out; nor will strains,
mass, specific heat, etc.) Many problems can result from careless use of the MPCHG command. For ex-
ample, if you reduce an element's stiffness to almost zero, but retain its mass, it could result in a singu-
larity if subjected to acceleration or inertial effects.
One application of the MPCHG command would be in modeling construction sequences in which the
strain history of a "born" element is maintained. Using MPCHG in such cases will enable you to capture
the initial strain experienced by elements as they are fitted into the displaced nodal configuration.
8.4. Using Birth and Death

You can apply element birth and death behavior to most static and nonlinear transient analyses using
the same basic procedures described in the various analysis guides.
Modify your basic analysis procedure as follows to incorporate the element birth and death feature:
8.4.1. Build the Model

While in the PREP7 preprocessor (/PREP7), create all elements, even those that will not be activated
until later load steps. You cannot create new elements after preprocessing.
8.4.2. Apply Loads and Obtain the Solution

For all analyses employing element birth and death, perform the following actions in the solution (SOLU)
phase:
8.4.2.1. Define the First Load Step

In the first load step, choose the analysis type and all appropriate analysis options (ANTYPE).
For a structural analysis, activate large-deflection effects (NLGEOM,ON).
For all birth and death applications, set the Newton-Raphson option to full explicitly in the first load
step (NROPT). (The program cannot predict the presence of an EKILL command in a subsequent load
step.) Deactivate (EKILL) all of the initially inactive elements that you intend to add (reactivate) in later
load steps.
Elements are deactivated (or activated) in the first substep of the load step, and maintain that status
through the rest of the load step. The default reduction factor used as a stiffness multiplier might not
suffice for some problems; sometimes, you may need to use a more severe reduction factor. To provide
a new value for the reduction factor, issue the ESTIF command.
Nodes not connected to any active elements may "float," or pick up stray degree-of-freedom (DOF) re-
sponses. You may want to constrain inactive DOFs (D, CP, etc.) in some cases to reduce the number of
equations to be solved and to avoid ill-conditioning. Constraining inactive DOFs can become more
important for cases in which you want to reactivate elements with a specific shape (or temperature,
etc.). If so, remove the artificial constraints when you reactivate elements, and remove nodal loads from
inactive DOFs (that is, at nodes not connected to any active elements). Similarly, you must specifically
add nodal loads (if any) to reactivated DOFs.
8.4.2.1.1. Sample Input for First Load Step

Part of your input listing could look like this for your first load step:
! First load step
TIME,... ! Sets TIME value (optional for static analyses)
NLGEOM,ON ! Turns large-deflection effects on
NROPT,FULL ! You must explicitly set the Newton-Raphson option
ESTIF,... ! Sets non-default reduction factor (optional)
ESEL,... ! Selects elements to be deactivated in this load step
EKILL,... ! Deactivates selected elements
ESEL,S,LIVE ! Selects all active elements
NSLE,S ! Selects all active nodes
NSEL,INVE ! Selects all inactive nodes (those not attached to any
! active elements)
D,ALL,ALL,0 ! Constrains all inactive DOFs (optional)
NSEL,ALL ! Selects ALL nodes
ESEL,ALL ! Selects ALL elements
D,... ! Adds constraints as appropriate
F,... ! Adds nodal loads to active DOFs as appropriate
SF,... ! Adds element loads as appropriate
BF,... ! Adds body loads as appropriate
SAVE
SOLVE
8.4.2.2. Define Subsequent Load Steps

In the remaining load steps, you can deactivate and reactivate elements as desired. As before, be sure
to apply and delete constraints and nodal loads as appropriate.
To deactivate and reactivate elements, issue the EKILL and EALIVE commands, respectively.
8.4.2.2.1. Sample Input for Subsequent Load Steps

The following simplified input listing demonstrates how you might deactivate and reactivate elements:
! Second (or subsequent) load step:
TIME,...
ESEL,...
EKILL,... ! Deactivates selected elements
ESEL,...
EALIVE,... ! Reactivates selected elements
...
FDELE,... ! Deletes nodal loads at inactive DOFs
D,... ! Constrains inactive DOFs
...
F,... ! Adds nodal loads as appropriate to active DOFs
DDELE,... ! Deletes constraints from reactivated DOFs
SAVE
SOLVE
8.4.3. Review the Results

Typically, you will follow standard procedures when postprocessing an analysis containing deactivated
or reactivated elements.
Be aware that "killed" elements are still present in your model, even though they make an insignificant
contribution to the stiffness (conductivity, etc.) matrix; therefore, they are included in element displays,
output listings, etc. For example, deactivated elements are included in nodal results averaging (via the
Where to Find Examples
PLNSOL command) and will "smear" the results. Ignore the entire element printout for deactivated
elements because many items computed make little physical sense.
To remove deactivated elements for element displays and other postprocessing operations, issue the
ESEL command.
8.4.4. Use Analysis Results to Control Birth and Death

At times, you will not explicitly know the location of elements that you need to deactivate or reactivate.
For example, if you want to "kill" melted elements in a thermal analysis (that is, to model the removal
of melted material), you will not know the location of those elements beforehand and will need to
identify them on the basis of their program-calculated temperatures. When the decision to deactivate
or reactivate an element depends on the value of a result item (such as temperature, stress, strain, etc.),
you can use commands to identify and select the critical elements.
To identify the critical elements, issue the ETABLE command. To select the critical elements, issue the
ESEL command.
You could then deactivate or reactivate the selected elements. To deactivate the selected elements, issue
the EKILL,ALL command. To reactivate the selected elements, issue the EALIVE,ALL command.
Note
You can also use the ANSYS Parametric Design Language to write a macro to perform such
an operation. See the ANSYS Parametric Design Language Guide for more information.
8.4.4.1. Sample Input for Deactivating Elements

The following simplified input listing demonstrates how you might deactivate elements that rupture
when their total strain has exceeded some critical value:
.. ! Typical solution procedure
SOLVE
FINISH
!
SET,...
ETABLE,STRAIN,EPTO,EQV ! Store total equivalent strain in ETABLE
ESEL,S,ETAB,STRAIN,0.20 ! Select all elements with total equivalent strain
! greater than or equal to 0.20
FINISH
!
/SOLU ! Re-enter SOLUTION
ANTYPE,,REST
EKILL,ALL ! Deactivate selected (overstrained) elements
ESEL,ALL ! Restore full element set
... ! Continue with solution

The Mechanical APDL Verification Manual consists of test case analyses demonstrating various analysis
capabilities, including element birth and death.
While the test cases demonstrate solutions to realistic analysis problems, the Mechanical APDL Verification
Manual does not present them as step-by-step examples with lengthy data input instructions and
printouts; however, if you have some finite-element experience, you should have no trouble understand-
ing the problems by reviewing each test case's finite-element model, input data and accompanying
comments.
Chapter 9: User-Programmable Features and Nonstandard Uses
The open architecture allows you to link it to your own Fortran routines and subroutines. In fact, some
standard features began as user-programmed features.
Typically, you can obtain good results when you exercise documented features using standard, recom-
mended procedures. In some cases, however, you may need to use nonstandard procedures that ANSYS,
Inc. Quality Assurance has not or cannot fully test.
The following topics concerning the program's open architecture are available:
9.1. User-Programmable Features (UPFs)
9.2. Nonstandard Uses of the Program
9.1. User-Programmable Features (UPFs)

User-programmable features (UPFs) are for which you can write your own Fortran routines. UPFs allow
you to customize the program to your needs, which may be a user-defined material-behavior option,
element, failure criterion (for composites), and so on. You can even write your own design-optimization
algorithm that calls the entire program as a subroutine. UPFs are available in the ANSYS Mechanical
Enterprise family of products. For detailed information, see the Guide to User-Programmable Features.
Caution
By linking in your own Fortran routines, you are creating a custom, site-specific version of
the program. When you use UPFs, you are using the program in a nonstandard way (p. 177),
one that ANSYS, Inc. verification testing does not cover. You are responsible for verifying that
the results produced are accurate and that the routines you link do not adversely affect
other, standard areas of the program.
Exercise care when using UPFs on parallel systems. Do not use the /CONFIG command or a
config.ans file to activate parallelism on a system with UPFs.
The following topics concerning UPFs are available:

9.1.1. Understanding UPFs
9.1.2.Types of UPFs Available
9.1.1. Understanding UPFs

UPFs can range from a simple element output routine for custom output to a much more complex user
element or user-optimization algorithm; therefore, it is difficult to present the process without describing
specific programming details. This section presents a general sequence of steps to follow. The Guide to
User-Programmable Features contains more detail on UPFs.
A typical UPF involves the following steps:
1. Design and program the desired user routine in Fortran. For more information on Fortran compilers
please refer to either the ANSYS, Inc. Windows Installation Guide or the ANSYS, Inc. Linux Installation
User-Programmable Features and Nonstandard Uses
Guide for details specific to your platform or operating system. The source codes for all user routines
are available on your ANSYS, Inc. distribution medium. Most of them demonstrate at least simple
functionality.
2. Compile and link your user routine into the program. The Guide to User-Programmable Features describes
how to do this on your system.
3. Verify that the changes you have made do not affect other, standard features. (One way to do so is
by running a set of Mechanical APDL Verification Manual problems.)
4. Verify the user routine using whatever procedures you feel are adequate.
The program activates some UPFs (such as user elements) automatically when you use them. For example,
to activate a user element, all you need to do is specify it as one of the element types in the model (via
the ET command), set the element type attribute pointer (via the TYPE command) ), and define elements
using the solid modeling (AMESH, VMESH, etc.) or direct generation (ET, etc.) method.
For other UPFs, you must issue the USRCAL command to activate them. If you do not issue the command,
standard program logic applies by default.
For example, when you apply a convection load, the default is to use standard program logic even if
you have linked a user convection routine. You must activate the appropriate user routine with the USRCAL
command if you want the user convection routine to be used. Refer to the USRCAL command description
for a list of user routines affected by the command. Use the NSVR command to define the number of
extra variables that need to be saved for such user-programmable element options as user plasticity.
(The NSVR command has no equivalent GUI path.)
Another useful command is /UCMD, which allows you to create your own command from a user routine.
Suppose you link in a user routine for a parabolic distribution of pressure. If you name the routine
USERnn (where nn = 01 to 10), you can create your own command to call the routine:
/UCMD,PARAB,1
PARAB now becomes a valid command that simply calls the user routine USER01. You can call up to
ten such user routines as commands. By including /UCMD commands in your start-up file (start.ans),
you can make the user routines available in all of your sessions.
9.1.2. Types of UPFs Available

Many UPFs are available in the program. Following is a brief description of each:
User-Programmable Features
User-defined elements Allows you to define your own element type. You can add it to the element
library and use it as you would any other element. See User-Defined Elements
in the Element Reference, and Creating a New Element in the Guide to
User-Programmable Features.
User-defined materials Allows you to define your own material model. See Custom Material Models
and Subroutines for Customizing Material Behavior in the Programmer's
Reference.
User-defined contact The contact elements (CONTA171 to CONTA178) allow you to define your own
interfacial behaviors interfacial behaviors between surfaces. See Subroutines for Customizing Contact
Interfacial Behavior in the Guide to User-Programmable Features.
Nonstandard Uses of the Program
User-Programmable Features
User real constants Elements COMBIN37, CONTA171, CONTA172, CONTA173, CONTA174, CONTA175,
CONTA176, CONTA177, and CONTA178 allow the input real constants to be
modified based upon your own nonlinear function.
User thickness Available for SHELL181, SHELL208, SHELL209, and SHELL281.
User stresses Available for LINK180, SHELL181, PLANE182, PLANE183, SOLID185, SOLID186,
SOLID187, SOLSH190, BEAM188, BEAM189, SHELL208, SHELL209, REINF264,
SHELL281, and SOLID285.
User plasticity law Allows you to calculate plastic strains and form the tangent stress-strain matrix
at an integration point based on your own plasticity law.
User creep equation Allows you to specify your own creep equation.
User swelling law If you need to account for swelling in an analysis (due to neutron
bombardment, for example), you must write the appropriate swelling law as
a user routine. No built-in swelling laws are available.
User failure criteria Available for the layered elements (such as SOLID185 Layered Structural Solid,
SOLID186 Layered Structural Solid, and SHELL281). Up to nine user-defined
failure criteria can be supplied.
User loads Body loads such as temperatures, heat generations, and fluences (such as
neutron flux), as well as surface loads such as pressures, convections, heat
fluxes and charge density may be defined by way of user-written logic.
Mechanical APDL as a You can call the entire Mechanical APDL program as a subroutine in your own
subroutine program, such as a user-written design optimization algorithm.
User access at the Allows you to evaluate results and perform any desired calculations during
beginning and end of solution.
each run solution, load
step, substep, and
equilibrium iteration
USRSURF116 Allows you to modify SURF151 and SURF152 film coefficients and bulk
temperatures based on information from FLUID116.
9.2. Nonstandard Uses of the Program

The program endures a rigorous verification testing plan before its release. You can be reasonably assured
of obtaining good results when you exercise documented features using standard, recommended pro-
cedures. In some situations, however, you may need to employ nonstandard procedures or techniques
that have not been or cannot be fully tested by ANSYS, Inc. because of their very nature. (An example
is employing user-programmable features (p. 175).) Be aware that verifying the results in such cases is
your responsibility.
The following related topics are available:

9.2.1. What Are Nonstandard Uses?
9.2.2. Hints for Nonstandard Use
9.2.1. What Are Nonstandard Uses?

The results of nonstandard uses of the program cannot be predicted; therefore, ANSYS, Inc.'s testing
cannot fully cover such uses. Although ANSYS, Inc. does not discourage nonstandard uses, you must
exercise caution and use your engineering judgment when doing so. For example, if you program your
own element and use it in an analysis, the results depend primarily on how well you programmed the
User-Programmable Features and Nonstandard Uses
element. In such cases, you must verify the results and ensure that other, standard areas of the program
are not adversely affected.
Following is a partial list of nonstandard features and uses:
• User programmable features (UPFs) -- Writing your own user routines, linking them into the program
executable, and using them in an analysis.
• Reading an external file into the program (for example, a results file or a superelement file created by
you or by another program).
• High-risk capabilities such as the following:
– Changing element real constants or section data during the solution phase in between load steps.
Depending on the element type being used, the element may not properly use the updated real
constant or section data values.
– Disabling the cross-checking of the solid model with the finite element model (MODMSH,NOCHECK).
– Disabling element shape-checking (SHPP,OFF).
• Using undocumented features, such as an element option not documented in the Element Reference
or a command argument not mentioned in the Command Reference. Undocumented features are, by
definition, unsupported and unverified; use them with caution.
If the program can detect the use of a nonstandard feature, it may issue a warning to that effect.
9.2.2. Hints for Nonstandard Use

Follow these guidelines when you need to use the program in a nonstandard manner:
• Use your engineering judgment and carefully review the analysis results.
• Do not assume that other, standard areas of the program are not affected. Run a few test problems to
verify.
• If you need to contact ANSYS, Inc. Technical Support concerning an analysis involving nonstandard use
of the program, be sure to mention the nature and extent of the nonstandard feature that you employed.
For detailed information on UPFs, see the Guide to User-Programmable Features.
Chapter 10: State-Space Matrices Export
The goal of reduced-order modeling based on state-space matrices is to generate a model using fewer
equations while still showing the same dynamics characteristics. The state-space matrices formulation
is an easy way to define this reduced model as a function of the inputs and the outputs. It is used in
multi-domain simulation software like Simplorer.
The following state-space matrices export topic is available:

10.1. State-Space Matrices Based on Modal Analysis
10.1. State-Space Matrices Based on Modal Analysis

The SPMWRITE command can be used to export state-space matrices based on a modal analysis when:
• The damping is proportional (e.g., no element damping).
• The mass and stiffness matrices are symmetric.
Prior to calculating the state-space matrices, you need to perform a modal analysis using the LANB,
LANPCG, SNODE, or SUBSP eigensolver (MODOPT command). When obtaining the modal solution,
consider the following:
• Modes do not need to be expanded.
• If you are applying nodal loads (forces or torques), you may specify them directly through table parameter
input (inputs on the SPMWRITE command). For other types of loads (e.g. pressure) you must define the
loads in the modal analysis and use the MODCONT command to generate the corresponding load vectors.
• If you need an initial condition for your reduced model, you must define the load in the modal analysis to
generate the corresponding load vector (NIC on the SPMWRITE command).
• Damping must be specified (see DMPRAT, MDAMP, BETAD, or ALPHAD command).
State-space matrices are calculated in postprocessing using the file Jobname.MODE. They are written
to the file Jobname.SPM using the requested format (FileFormat on the SPMWRITE command).
10.1.1. Examples of SPMWRITE Command Usage

This section describes how to use SPMWRITE to export state-space matrices based on two sets of
model criteria.
1. The first set of model criteria for export to Simplorer are as follows:
• 10 modes are taken into account.
• There are 2 inputs specified in the array parameter ‘inputTab’.
• The inputs labels are defined in the character array parameter ‘inputLab’.
State-Space Matrices Export
• There is 1 output specified in the array parameter ‘outputTab’.
• The output label is defined in the character array parameter ‘outputLab’.
• The initial condition is calculated from the first load vector.
• Velocity and acceleration results are not included.
• The SML format for Simplorer is used to printout the state-space matrices.
If your model can be described by this first set of criteria, issue the following to export the state-
space matrices:
! ** inputs definition
*dim,inputTab,,2,2
*dim,inputLab,CHAR,2
inputTab(1,1) = 413 ! node 413
inputTab(1,2) = 1 ! ux
inputLab(1) = ‘n413_ux’
inputTab(2,1) = node(50e-2,0,45e-2) ! node @(.5,0,.45)
inputTab(2,2) = 4 ! rotx
inputLab(2) = ‘n01_rotx’
! ** outputs definition
*dim,outputTab,,1,2
*dim,outputLab,CHAR,1
outputTab(1,1) = 1022 ! node 1022
outputTab(1,2) = 1 ! ux
outputLab(1) = ‘n1022_ux’
spmwrite,modal,10,inputTab,inputLab,outputTab,outputLab,1
2. The second set of model criteria are as follows:
• All modes are taken into account.
• The inputs are based on all existing load vectors from the modal analysis.
• The outputs are equal to the inputs.
• There is no initial condition.
• Velocity and acceleration results are not included.
• The dense format is used to printout the state-space matrices.
If your model can be described by this second set of criteria, issue the following to export the state-
space matrices:
spmwrite,modal, ,, ,, ,, ,0
10.1.2. Example of Reduced Model Generation in ANSYS and Usage in Sim-

plorer
10.1.2.1. Problem Description
The model in this example is a basic representation of a disk drive suspension as described in Hatch[1].
It is a clamped-free beam with a mass and spring at tip. The mass represents the recording head. The
State-Space Matrices Based on Modal Analysis
reduced model is generated in ANSYS and imported into Simplorer where global half-sine acceleration
is applied in a transient analysis.
10.1.2.2. Problem Specifications

Material
Young Modulus: 190e+6 mN/mm2
Density: 7.83e-6 kg/mm3
Poisson ratio: 0.293
Beam
Length: 20 mm
Area: 0.15 mm2
Cross section inertia IYY: 0.05 mm4
Cross Section inertia IZZ: 0.00007031 mm4
Spring
Stiffness: 1.e+7 N/mm
Mass at tip
Mass: 1.e-6 kg
10.1.2.3. Input File for the Analysis

Use the input below to generate the state-space matrices file (file.spm) based on the first 3 modes
plus the residual vector.
/title, Beam on Shaker (ACEL) - SPMWRITE 3 modes + resvec
/prep7
! ** Parameters
num_elem = 16
nummodes = 2*num_elem
! ** Material
ex,1,190e6
dens,1,7.83e-6
nuxy,1,0.293
! ** Properties
r,1,0.15,0.05,0.00007031,0.075,0.2
r,2,1000000
r,3,0.00002349,0.00002349,0.00002349
! Nodes
n,1,0,0,0
n,num_elem+1,20,0,0
fill,1,num_elem+1
n,num_elem+2,20,0,-3
nall
! ** Beam
et,1,4
type,1
mat,1
real,1
State-Space Matrices Export
e,1,2
egen,num_elem,1,-1
! ** Spring
et,2,14
type,2
real,2
e,num_elem+1,num_elem+2
! ** Mass
et,3,21
type,3
real,3
e,num_elem+1
! ** Constraints
d,1,all,0
d,num_elem+2,all,0
nsel,s,node,,2,num_elem+1
d,all,ux
d,all,uy
d,all,rotx
d,all,rotz
nsel,all
fini
! ** Modal analysis
/solu
antype,modal
modopt,lanb,3 ! << 3 modes
mxpand,3
resvec,on ! << residual vector
acel,,,1.0 ! << load vector definition
dmprat,0.02 ! << modal damping
solve
fini
/post1
/eshape,1
! ** Definition of the output
*dim,output,,1,2
output(1,1) = num_elem+1 ! << node at tip
output(1,2) = 3 ! << UZ
*dim,outputLab,CHAR,1
outputLab(1) = 'UZtip'
! ** Write SPM file: input = load vector

spmwrite, modal, ,,, output, outputLab
*list,,spm
fini
The state-space matrices file can be imported in Simplorer using: Simplorer Circuit > SubCircuit >
Add Mechanical Component
A transient analysis is performed in Simplorer for the 3 following reduced models:
• All 32 modes are used.
• First 3 modes are used.
• First 3 modes plus residual vector are used (ANSYS input is listed above).
The schematic of the simulation is shown on the figure below:
State-Space Matrices Based on Modal Analysis
Figure 10.1: Simulation Schematic
A zoom on the graph showing the evolution of the spring force is given below:
Figure 10.2: Evolution of Spring Force
The reduced model based on the first 3 modes (red curve) is not accurate. When the residual vector is
included (purple curve), the spring force is similar to the reference given by the 32 modes reduced
model (dotted curve).
Chapter 11: Soil-Pile-Structure Analysis
You can analyze the interaction of an offshore structure supported on one or more piles, with an
elastic or inelastic soil. The analysis can take into account the lateral force displacement, and the end-
bearing and skin-friction responses of the soil layers occurring at the pile location. It is not necessary
for all piles in the analysis to be situated in identical geological strata.
Customized macros are used to model the soil-pile interaction, with the soil data defined in additional
text files. Piles are modeled using PIPE288 and the surrounding soil environment is modeled using
COMBIN39 elements.
The macros, along with accompanying documentation, can be found in the Offshore extension in the
ACT Extension library in the downloads area on the Customer Portal: https://support.ansys.com/Ansy-
sCustomerPortal/en_us/Downloads/Extension+Library.
Chapter 12: Coupling to External Aeroelastic Analysis of Wind
Turbines
This chapter describes the facilities available within Mechanical APDL that enable it to perform integrated
wind and wave load analyses for offshore wind turbines with a specialized wind loading software
package. The purpose of using Mechanical APDL is to provide a realistic foundation model that can
accurately model the foundation structural behavior under the influence of wave loading. Note that
foundation here refers to the whole substructure that is under the influence of wave loading, i.e. from
the sea surface down.
Two different methods of analysis to support a coupled aeroelastic-structural analysis can be used with
Mechanical APDL to enable the design of the structures upon which wind turbines are positioned. Each
method has advantages and disadvantages depending upon the data and resources available. The se-
quentially coupled solution is found in the following section and uses standard Mechanical APDL. There
is an example of implementing a fully coupled solution that can be found in Fully Coupled Wind Turbine
Example in Mechanical APDL in the Mechanical APDL Programmer's Reference. This requires programmer
knowledge, software compilation tools, and customization to enable the coupling to an aeroelastic
analysis.
12.1. Sequential Coupled Wind Turbine Solution in Mechanical APDL

In the sequential wind coupling method, the aeroelastic analysis is performed by the aeroelastic code
with the effects of the supporting structure incorporated as a superelement to the solution. Mechanical
APDL provides the supporting structure substructure matrices and loading data that are required as
input to the aeroelastic code. After the aeroelastic analysis, the results can be fed back to Mechanical
APDL to recover the element forces inside the supporting structure.
12.1.1. Procedure for a Sequentially Coupled Wind Turbine Analysis

The procedure for carrying out an integrated wind and wave load analysis is described as follows:
1. The wind turbine supporting structure is modelled in Mechanical APDL. A substructure model is created
with the top node (i.e. the connection point between the wind turbine and the supporting structure)
set as the master node. This master node must have 6 freedoms: UX, UY, UZ, ROTX, ROTY, and ROTZ.
A substructure generation run is performed with the supporting structure model subjected to ocean
wave and other external loadings. The solution times for this run should tie in with the times of the
solution that will be attempted in the following aeroelastic run.
2. The command OUTAERO can be called after the solution from 1 is obtained to produce the generalized
mass, damping, and stiffness matrices of the supporting structure, together with a time series of the
generalized foundation external loading (due to wave loading etc.). The generalized matrices are
written to 3 separate files (mass, damping, and stiffness) and the generalized load time series is written
to another file. See Output from the OUTAERO Command (p. 188).
3. An aeroelastic solution is then carried out with the foundation effects included through utilizing the
generalized matrices and loading vector derived above. The forces and/or displacements at the sup-
porting structure top node at each solution time are written to a file.
Coupling to External Aeroelastic Analysis of Wind Turbines
4. Another Mechanical APDL run is performed to recover the member forces in the foundation structure
by applying the supporting structure top node force or displacement time series obtained from the
aeroelastic analysis together with the foundation external loading as specified in step 1. The analysis
can be carried out statically or dynamically.
Note
The following points should be noted for the sequential solution approach:
• The generalized matrices (stiffness, etc.) are computed based on the initial undeformed geometry
and assuming small displacement, linear behavior. It is thus implicitly assumed that the foundation
is linear with small deformations throughout the entire solution.
• Likewise, when computing the generalized foundation external load time history in the substruc-
ture generation pass, it is assumed that the structural displacement and velocity are zero since
such information is not available when the loading is generated.
• The hydrodynamic mass for the supporting structure is formed based on the water elevation at
the first time at which the solution is attempted.
• If the supporting structure internal forces are recovered statically in step 4, the dynamic forces
(e.g. inertial force) in the foundation will be ignored. The dynamic effects can be accounted for
by running this step as a transient job. However, it should be noted that the following points
may affect the accuracy of the solution:
– The generalized mass used in the aeroelastic analysis is only an approximation to the true mass
matrix (static reduction is exact but not dynamic).
– Different time integration schemes may be adopted by aeroelastic code and Mechanical APDL.
Hence, while the displacement time histories are identical in both runs (for the prescribed
displacement case), it may not be the case for the velocity and acceleration time histories.
• There should be little difference between applying forces or displacements to recover the
foundation forces. The two methods should yield identical results in a linear static analysis.
• This approach should be much more efficient than the fully coupled approach as there is no need
to keep both the aeroelastic code and Mechanical APDL running simultaneously and keep ex-
changing information every time step.
12.1.2. Output from the OUTAERO Command

Four formatted ASCII files will be generated by specifying the OUTAERO command macro. These are:
Jobname.gnm - generalized mass matrix file
Jobname.gnc - generalized damping matrix file
Jobname.gnk - generalized stiffness matrix file
Jobname.gnf - generalized external force time series file
where Jobname is the current job name.
Sequential Coupled Wind Turbine Solution in Mechanical APDL
The generalized mass, damping, and stiffness matrices are formed based on the information at the very
first load step and are written to 3 separate files. These are formatted ASCII files with the full 6 x 6
matrix included. The files are written with the following format:
ngenfr (1x, I6)
(val(i,1), i = 1,ngenfr) (6(1x, E12.5))
(val(i,2), i = 1,ngenfr) (6(1x, E12.5))
.
.
(val(i,ngenfr), i = 1,ngenfr) (6(1x, E12.5))
where ngenfr is the number of generalized freedoms, which is always 6 at present, and val is the
generalized matrix.
The row and column order in the generalized matrix corresponds to the order UX, UY, UZ, ROTX, ROTY,
ROTZ.
A time series of the generalized foundation external loading vector is written to another file. At each
solution time, the time (t) and the associated generalized load vector (f ) will be output to this file. The
force file has the following format:
ngenfr (1x, I6)
t1 (1x, E12.5)
(f1(i), i = 1,ngenfr) (6(1x, E12.5))
t2 (1x, E12.5)
(f2(i), i = 1,ngenfr) (6(1x, E12.5))
.
.
tn (1x, E12.5)
(fn(i), i = 1,ngenfr) (6(1x, E12.5))
The load values are ordered in the same way as the generalized matrices.
12.1.3. Example Substructuring Analysis to Write Out Aeroelastic Analysis

Input Data
This is an example of the sequential aeroelastic analysis process. This first analysis is run to create the
matrices/loading. These are generated by the OUTAERO macro near the end of the analysis.
The master node is set as node 9, which will be the interface point to the aeroelastic structure.
/verify,airysublarge
/FILNAME,airysublarge
/prep7
/TITLE,airysublarge, WAVE ON MONOPILE
/com **************************************************************************
/com Substructure with Airy wave
/com use time to determine phase at each step
/com includes current
/com CREATED 08/03/11
/com **************************************************************************
antype,substr
seopt,monopile,3,1
nlgeom,off
et,1,pipe288
keyopt,1,3,3
keyopt,1,12,1
type,1
mat,1
! Define pipe section
secnum,1
sectype,1,pipe
secdata,1.0,0.1
! Define ocean
matwat=2
Coupling to External Aeroelastic Analysis of Wind Turbines
idwat=2
idcur=3
idwav=4
depth=30.0
offset = 1.5
! Ocean basic
octype,basic,ocean1
ocdata,depth,matwat
octable,,,0.7,0.7,,2.0
mp,dens,matwat,1000.0
! Ocean current
octype,curr
octable,0.0,1.0
octable,-depth,0.0
! Define geometry of vertical tube

n, 1, offset, 0.0, -30.0000
n, 2, offset, 0.0, -25.0000
n, 3, offset, 0.0, -20.0000
n, 4, offset, 0.0, -15.0000
n, 5, offset, 0.0, -10.0000
n, 6, offset, 0.0, -5.0000
n, 7, offset, 0.0, 0.0000
n, 8, offset, 0.0, 5.0000
n, 9, offset, 0.0, 10.0000
n, 900, offset, -20.0000, 0.0000
en, 1, 1, 3, 900
en, 3, 3, 5, 900
en, 5, 5, 7, 900
en, 7, 7, 9, 900
MP,EX, 1,2.0e11
MP,PRXY,1,0.3
MP,ALPX,1,0.0
MP,DENS,1,7850.0
! Damping factors
alphad,0.1
betad,0.01
! Suppressions
d,1,all
! Master freedoms
m,9,all
finish
! Increase limit of time values to 5000
/config,numsublv,5000
/SOLU
acel,0,0,9.81
wper=10.0
phs=0.0
! Ocean wave (Airy in this case)

octype,wave
ocdata,0,0.0,0,1,1
octable,2.0,wper,phs
tm_1=1.0e-8
tm_2=1000.0
tm_inc=0.2
*do,tm,tm_1,tm_2,tm_inc
time,tm
solve
*enddo
! Print substructure matrices
! outaero,'monopile',tm_1,tm_inc ! This version uses the time defined by tm_1 & tm_inc
outaero,'monopile' ! This version reads the time off the .sub file
finish
At this point the aeroelastic analysis can be run, using the output from the above analysis. Once complete,
a second Mechanical APDL analysis is run with a time series of forces and/or displacements at the inter-
face node. These need to be converted from the aeroelastic output to Mechanical APDL compatible
Sequential Coupled Wind Turbine Solution in Mechanical APDL
output by the user (for example, using Excel) or the aeroelastic analysis program. Any ocean loading
or extra loading included in the substructured analysis should also be applied in the subsequent ana-
lysis.
Chapter 13: Applying Ocean Loading from a Hydrodynamic Analysis
Pressures and motion effects of a rigid body modeled by hydrodynamic analysis can be imported for
further analysis using ocean commands. For this type of analysis, the wave type in the ocean wave
OCDATA command should be set to diffracted wave (KWAVE = 8). The hydrodynamic data is read in
via the OCREAD command.
This topic does not describe wave-theory-derived ocean loading (implemented via KWAVE = 0 through
7 on the OCDATA command).
The following topics related to using hydrodynamic analysis data to apply ocean loading are available:
13.1. How Hydrodynamic Analysis Data Is Used
13.2. Hydrodynamic Load Transfer with Forward Speed
13.3. Hydrodynamic Data File Format
13.4. Example Analysis Using Results from a Hydrodynamic Diffraction Analysis
13.1. How Hydrodynamic Analysis Data Is Used

Pressures and motions due to the waves, current, and forward speed at a given phase are extracted
from a hydrodynamic data file. The hydrodynamic data file information is translated either into surface
element pressures or into line element pressures based on Morison’s equation.
The hydrodynamic data (.ahd) file must be prepared in a specific format (p. 194) for it to be read during
the ocean loading procedure. If the Hydrodynamic Diffraction System (AQWA) has been used for the
hydrodynamic diffraction/radiation analysis, a utility program is available to translate the results database
into this format automatically.
To apply the ocean loads, an ocean environment and loading data need to be defined using the ocean
family of commands (specifically, OCTYPE, OCZONE, OCDATA, and OCTABLE).
For line elements (BEAM188, BEAM189, PIPE288, PIPE289, and LINK180), the ocean loading is applied
automatically if it is defined.
For shells or solids, the hydrodynamic loading is applied via SURF154 elements with KEYOPT(8) = KEY,
where KEY activates or deactivates ocean effects. If KEYOPT(8) = 0, the ocean load is not applied to
SURF154 elements even if the ocean environment exists.
For loads applied to shells or solids only, the hydrodynamic load components are included. Hydrostatic
loading can be included on SURF154 using face 4 with PL = -(gravity acceleration) * (water density) and
by setting KEYOPT(6) = 1. For loads applied to pipe elements, hydrostatic loading is included automat-
ically.
It is not necessary for the hydrodynamic and structural meshes to be identical, and the loading is
mapped automatically from one to the other; however, it is assumed that the hydrodynamic axis system
is identical to that used for the structural analysis. Small displacements are assumed in the load-mapping
process, and mapping may not be accurate if this condition is not met.
Applying Ocean Loading from a Hydrodynamic Analysis
The .ahd file contains data indicating which side of a panel is the wetted side. The program uses the
data to adjust which direction to apply the hydrodynamic pressure on the SURF154 elements.
Each structural integration point is located in its nearest hydrodynamic panel. The program then calculates
the corner pressures of the panel based on a weighted averaging of that panel and its neighboring
panels. Finally, using a bilinear fit across the panel, the program calculates the hydrodynamic pressure
at the structural integration point.
13.2. Hydrodynamic Load Transfer with Forward Speed

Ocean loading analysis does not allow input of forward speed explicitly. To account for forward speed,
it is necessary to specify an opposite current. If forward speed and a current are required, the specified
current must represent the resultant of the two effects. This current is used only for the calculation of
Morison loads following the diffraction calculation.
If the panel pressures and motions are obtained from AQWA, it is also possible to define a forward
speed in the diffraction calculation, causing the hydrodynamic coefficients to be corrected for the effect
of forward speed. The following restrictions apply:
• Forward speed can be along the global X axis only.
• Only one wave direction can be specified in a diffraction calculation with forward speed.
It is your responsibility to ensure that forward speed in the diffraction calculation and current in the
load transfer are consistent.
13.3. Hydrodynamic Data File Format

The hydrodynamic data file comprises a number of sections which represent all of the required input
to the ocean wave command:
13.3.1. Comment (Optional)
13.3.2. General Model Data
13.3.3. Hydrodynamic Surface Geometry
13.3.4. Wave Periods
13.3.5. Wave Directions
13.3.6. Panel Pressures
13.3.7. Morison Element Hydrodynamic Definition
13.3.8. Morison Element Wave Kinematics Definition
13.3.9. RAO Definition
13.3.10. Mass Properties
13.3.1. Comment (Optional)

The comment section contains descriptive text for the model.
* text
where
* keyword to signify that this is a comment line

text description of the model
Hydrodynamic Data File Format
13.3.2. General Model Data

This section defines some general data for the model.
GENE
depth density gravity symxy
where
GENE keyword to denote the start of the general model data

depth water depth
density water density
gravity acceleration of gravity
symxy symmetry integer
0: no symmetry
1: symmetry about x axis
2: symmetry about y axis
3:symmetry about both x and y axes
Example 13.1: General Model Data

GENE
2.500000E+02 1.025000E+03 9.800000E+00 3
13.3.3. Hydrodynamic Surface Geometry

The hydrodynamic surface geometry provides information related to the panel definition of the model.
Allowance can be made for symmetric models; that is, only one half of the model must be defined for
one plane of symmetry, and only a quarter of the model must be defined for double symmetry.
HYDR
npan
x1(1) y1(1) z1(1) x2(1) y2(1) z2(1) x3(1) y3(1) z3(1) x4(1) y4(1) z4(1)
.
.
x1(npan) y1(npan) z1(npan) x2(1) … x4(npan) y4(npan) z4(npan)
where
HYDR keyword to denote start of hydrodynamic panel description

npan number of panels to be defined
xk(j) X coordinate for panel j, node k
yk(j) Y coordinate for panel j, node k
zk(j) Z coordinate for panel j, node k
The nodes must be arranged in counterclockwise order when viewing the panel from the wetted side.
To define a triangular panel, specify the same coordinates for nodes 3 and 4.
Example 13.2: Hydrodynamic Surface Geometry

HYDR
12
15.0 -15.0 0.0 7.5 -15.0 0.0 7.5 -15.0 -7.5 15.0 -15.0 -7.5
15.0 -15.0 -7.5 7.5 -15.0 -7.5 7.5 -15.0 -15.0 15.0 -15.0 -15.0
15.0 -15.0 -15.0 7.5 -15.0 -15.0 7.5 -7.5 -15.0 15.0 -7.5 -15.0
15.0 -7.5 -15.0 7.5 -7.5 -15.0 7.5 0.0 -15.0 15.0 0.0 -15.0
7.5 -15.0 0.0 0.0 -15.0 0.0 0.0 -15.0 -7.5 7.5 -15.0 -7.5
7.5 -15.0 -7.5 0.0 -15.0 -7.5 0.0 -15.0 -15.0 7.5 -15.0 -15.0
7.5 -15.0 -15.0 0.0 -15.0 -15.0 0.0 -7.5 -15.0 7.5 -7.5 -15.0
7.5 -7.5 -15.0 0.0 -7.5 -15.0 0.0 0.0 -15.0 7.5 0.0 -15.0
15.0 -15.0 0.0 15.0 -15.0 -7.5 15.0 -7.5 -7.5 15.0 -7.5 0.0
15.0 -15.0 -7.5 15.0 -15.0 -15.0 15.0 -7.5 -15.0 15.0 -7.5 -7.5
15.0 -7.5 0.0 15.0 -7.5 -7.5 15.0 0.0 -7.5 15.0 0.0 0.0
15.0 -7.5 -7.5 15.0 -7.5 -15.0 15.0 0.0 -15.0 15.0 0.0 -7.5
13.3.4. Wave Periods

This section defines the wave periods where hydrodynamic pressures have been computed.
PERD
nperd
period(1) period(2) ... period(i)
period(i+1) period(i+2) ... period(nperd)
where
PERD keyword to denote start of wave period data

nperd number of wave periods
period(i) the ith wave period (s)
The data may be specified in one or more lines until all the periods are entered.
Example 13.3: Wave Periods

perd
1
18.0
13.3.5. Wave Directions

This section defines the wave directions where hydrodynamic pressures have been computed.
DIRN
ndirn
heading(1) heading(2) ... heading(i)
heading(i+1) heading(i+2) ... heading(ndirn)
where
DIRN keyword to denote start of wave direction data

ndirn number of wave directions
heading(i) the ith wave direction (in degrees, between -180 and +180)
The data may be specified in one or more lines until all the directions are entered.
Example 13.4: Wave Directions

dirn
2
0.0 90.0
13.3.6. Panel Pressures

This section defines the wave directions where hydrodynamic pressures have been computed.
PRES
iperiod iheading region panel magnitude phase
where
PRES keyword to denote the start of hydrodynamic pressure values

iperiod period number (position in the period list)
iheading wave direction number (position in the direction list)
region • If two planes of symmetry (symxy set to 3)
region 1 corresponds to modelled elements
region 2 corresponds to reflection in x-z plane
region 3 corresponds to reflection in y-z plane
region 4 corresponds to reflection in x-z and y-z plans
• If one plane of symmetry (symxy set to 1 or 2)
region 1 corresponds to modelled elements
region 2 corresponds to reflected elements
panel panel number (must be between 1 and npan)

mag- pressure amplitude
nitude
phase associated phase angle in degrees (with respect to the wave at the center of gravity of the
vessel)
The associated phase angle (phase) determines the horizontal location of the loading. The magnitude
and phase together define the shape of the harmonic loading curve.
Pressure is positive when acting from the wetted surface towards the inner surface.
If no input pressure is given to a panel at a particular period and direction, the pressure on the panel
is assumed to be zero. If more than one set of pressures are defined, their effects are accumulative; that
is, the real and imaginary parts of each set are summed together.
Example 13.5: Panel Pressures

PRES
1 1 1 1 25.0 0.0
1 1 1 2 75.0 0.0
1 1 1 3 100.0 0.0
1 1 1 4 100.0 0.0
1 1 1 5 25.0 0.0
1 1 1 6 75.0 0.0
13.3.7. Morison Element Hydrodynamic Definition

The data in this section describes the line elements used to provide slender body loading.
MORI
nmori
x1(1) y1(1) z1(1) x2(1) y2(1) z2(1)
.
.
x1(nmori) y1(nmori) z1(nmori) x2(nmori) y2(nmori) z2(nmori)
where
MORI keyword to denote start of Morison hydrodynamic element description

Nmori number of Morison elements defined
xk(j) X coordinate for line element j, node k
yk(j) Y coordinate for line element j, node k
zk(j) Z coordinate for line element j, node k
Example 13.6: Morison Element Hydrodynamic Definition

MORI
1
10 0 0 20 0 0
13.3.8. Morison Element Wave Kinematics Definition

The data in this section defines the wave kinematics at the nodes of the Morison elements defined
above (p. 197).
WKIN
iperiod iheading node element pmag pphs zsmag zsphs
vxmag vxphs vymag vyphs vzmag vzphs
axmag axphs aymag ayphs azmag azphs
where
WKIN keyword to denote start of Morison element wave kinematics definition

iperiod wave period number (position in period list)
iheading wave direction number (position in direction list)
node local node number on Morison element (1 or 2)
element element number referencing the Morison element list
pmag hydrodynamic pressure amplitude
pphs associated phase angle (degrees)
zsmag surface elevation amplitude
zsphs associated phase angle (degrees)
vxmag x velocity amplitude
vxphs associated phase angle (degrees)
vymag y velocity amplitude
vyphs associated phase angle (degrees)
vzmag z velocity amplitude
vzphs associated phase angle (degrees)
axmag x acceleration amplitude
axphs associated phase angle (degrees)
aymag y acceleration amplitude

ayphs associated phase angle (degrees)
azmag z acceleration amplitude
azphs associated phase angle (degrees)
Note that the data is defined for X, Y and Z in the global directions.
If no input is given to a Morison element at a particular period and direction, the kinematics data on
this element are assumed to be zero.
Example 13.7: Morison Element Wave Kinematics Definition

WKIN
1 1 1 134 0.1 15 1.2 15
2.2 15 2.2 15 2.3 15
0.2 15 1.5 15 4.3 15
13.3.9. RAO Definition

This section data defines the RAO data. The first line defines the RAO reference position, followed by
blocks of data defining RAOs in various periods and directions.
RAOS
xr yr zr
iperiod iheading xmag xphs ymag yphs zmag zphs
rxmag rxphs rymag ryphs rzmag rzphs
where
RAOS keyword to denote start of RAO definition

xr yr zr X, Y and Z coordinate of the RAO reference position
iperiod wave period number (position in period list)
iheading wave direction number (position in direction list)
xmag x RAO amplitude
xphs associated phase angle (degrees)
ymag y RAO amplitude
yphs associated phase angle (degrees)
zmag z RAO amplitude
zphs associated phase angle (degrees)
rxmag rx RAO amplitudee (degrees)
rxphs associated phase angle (degrees)
rymag ry RAO amplitude (degrees)
ryphs associated phase angle (degrees)
rzmag rz RAO amplitude (degrees)
rzphs associated phase angle (degrees)
Example 13.8: RAO Definition

RAOS
0.000000E+00 0.000000E+00 -5.000000E+00
1 1 8.972334E-01 8.999010E+01 6.241512E-08 -1.799247E+02 1.042555E+00 4.346394E-02
7.862426E-09 0.000000E+00 7.524462E-01 -9.000951E+01 2.027182E-07 0.000000E+00
1 2 6.357081E-01 8.999005E+01 6.357080E-01 8.999005E+01 1.042556E+00 4.340762E-02

5.293267E-01 8.999037E+01 5.293267E-01 -9.000961E+01 1.605987E-07 0.000000E+00
13.3.10. Mass Properties

This section defines the mass properties of the hydrodynamic model but is currently unused.
MASS
xcg ycg zcg
Mass(1,1) mass(1,2) .. mass(1,6)
.
.
Mass(6,1) mass(6,2) .. mass(6,6)
where
MASS keyword to denote start of mass information

xcg ycg zcg X, Y and Z coordinate of CoG
mass(j,k) mass matrix term
Example 13.9: Mass Properties

MASS
0.000000E+00 0.000000E+00 -5.000000E+00
1.383750E+07 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 1.383750E+07 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 1.383750E+07 0.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 0.000000E+00 7.780000E+08 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 7.780000E+08 0.000000E+00
0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 7.780000E+08
13.4. Example Analysis Using Results from a Hydrodynamic Diffraction

Analysis
In this example, a 30m x 30m x 22.5m box with 7.5m above the water level (z = 0m) was modeled in
a hydrodynamic diffraction analysis.
The following conditions exist:
• The diffracting elements are 3m x 3m.
• Waves are defined in eight directions and four frequencies (0.031, 0.5, 0.97, and 1.43 rad/s).
• Forward speed and hydrostatic pressures are not included.
The pressure results from the hydrodynamic diffraction analysis are 45°, 1.43 rad / s, t / T = 0, as shown
in the following figure:
Example Analysis Using Results from a Hydrodynamic Diffraction Analysis
Figure 13.1: Hydrodynamic Diffraction Analysis Pressure Results
An .ahd file named analysis_1, which contains the data from the hydrodynamic diffraction analysis,
was generated via the AQWA product's AQWA2NEUT utility, as follows:
aqwa2neut analysis 1
The diffracted wave loading data in the analysis_1.ahd file is imported (OCREAD) and applied to
the structural model for further analysis, as shown in the following example input:
/verify,difwaveeg
/FILNAME,difwaveg
/prep7
/TITLE,difwaveeg, EXAMPLE FOR AQWA LOADING
/com **************************************************************************
/com SHELL MODEL OF A HOLLOW BOX TUBE
/com CREATED 20/05/10
/com **************************************************************************
antype,static
nlgeom,off
! define shell section
sectype,11,shell
secdata,0.1
! define ocean
matwat=2
idwat=2
idcur=3
idwav=4
depth=250.0
! define geometry
/prep7
!wpoff,,,-15
k,,-15,-15,-15
k,,15,-15,-15
k,,15,15,-15
k,,-15,15,-15
l,1,2
l,2,3
l,3,4
l,4,1
k,,-15,-15,0
l,1,5
k,,-15,-15,7.5
l,5,6
adrag,1,2,3,4,,,5,6
a,1,2,3,4
! Mesh
et,1,181
type,1
mat,1
secnum,11
esize,1
amesh,all
et,2,154
keyopt,2,4,1
keyopt,2,8,idwat
r,2
rmore,0.0001
type,2
mat,1
real,2
esurf
! steel material properties
MP,EX, 1,2.1e11
MP,PRXY,1,0.3
MP,ALPX,1,0.0
MP,DENS,1,7800.0
! water density
mp,dens,matwat,1025.0
! supports
d, 1,ux
d, 2,ux
d,977,ux
d,497,ux
d, 1,uy
d, 2,uy
d,977,uy
d,497,uy
d, 1,uz
d, 2,uz
d,977,uz
d,497,uz
finish
!
/SOLU
! CASE 4 H=1 T=4.384199 PH=0 D=45
acel,0,0,9.8
! ocean
octype,basic,ocean1
ocdata,depth,matwat
!! diffracted wave
octype,wave
ocdata,8,45.0
octable,1.0,200,0.0
!
!! ocread to read in external data file
ocread,analysis_1,ahd
!
! list all
slist,all
oclist,all
!! apply inertia relief
!! irlf,1
NSUBST,1,1 ! 1 SUBSTEPS
Example Analysis Using Results from a Hydrodynamic Diffraction Analysis
TIME,1.0
OUTPR,all,1
OUTRES,all,1
solve
finish
/post1
etable,x,smisc,13
pletab,x,avg
The following figure shows the analysis results using the pressures from the diffracted wave:
Figure 13.2: Analysis Results Using Pressure Data from a Hydrodynamic Diffraction Analysis
D
Index diffracted wave, 193
Symbols E
2-D to 3-D analysis elements
benefits, 99 birth and death of, 169
initial-state-based analysis, 105
introduction to, 99 F
key commands, 102 files
map solution variables, 105 Jobname.NODE, 155
performing, 103 flexible body dynamics (see rotating structure analysis)
requirements, 99
restrictions, 105 H
selecting a region for remeshing, 104 hydrodynamic analysis, 193
starting, 104
substep at which to initiate, 103 I
supported analyses, 99
initial state
understanding the process, 101
application, 108
coordinate systems, 113
A example problems, 115
aeroelastic analysis, 187 file format, 112
automatic rezoning, 51 limitations, 113
overview, 107
B specifying and editing values, 107
birth and death of elements writing values to a file, 127
applying loads and solving, 171
building the model, 171 J
constraint equations, 170 Jobname
controlled by analysis results, 173 in a submodeling analysis, 153
example problems, 173
first load step: defining, 171 M
in linear models, 170
manual rezoning, 5
initial strain, 170-171
material properties
material properties: changing, 171
changing to deactivate or reactivate elements, 171
multiple load steps, 170
mesh nonlinear adaptivity, 51
Newton-Raphson option, 170
nodal constraints and loads, 171
overview of, 169
N
reviewing results, 172 natural frequencies, 136
sample input, 172-173 Newton-Raphson
status of an element: determining, 170 birth and death analysis, 170
strain, 169 nonstandard uses, 177
subsequent load steps: defining, 172
supported elements, 169 O
usage guidelines, 170 ocean loading, 193
using in an analysis, 171
P
C pile analysis, 185
Campbell diagram, 131
CDB generic mesh file, 19 R
Coriolis effect, 129 rezoning
cut boundary displacement method (see submodeling) automatic (see mesh nonlinear adaptivity)
Index
balancing residual forces, 36 analyzing the submodel, 156

benefits, 5 coarse model: creating and analyzing, 153
contract boundaries, 34 creating the submodel, 154
convergence difficulties during mapping operation, cut-boundary interpolation: performing, 155
38 distance between cut boundaries and stress concen-
example, 42, 45 tration: verifying, 158
file structures for repeating, 39 example input, 159
forces and isolated applied displacements, 34 example problems, 167
horizontal rezoning, 19 introduction, 151
introduction to, 5 shell-to-solid, 165
key commands, 14 understanding, 151
limitations, 7 Submodeling
mapping variables, 36 process involved, 152
mesh control during, 32
multiframe restart after, 38 U
multiple regions remeshed at the same substep, 19 UPFs (see user-programmable features)
nodal temperatures, 34 user-programmable features
postprocessing results, 39 available types, 176
pressure and contiguous displacements, 34 overview of, 175
remeshing, 17 process involved, 175
repeating as needed, 38
requirements, 8 V
restrictions, 41 Variational Technology, 1
selecting a region for remeshing, 16
starting, 16 W
substep at which to initiate, 15
wind turbine analysis, 187
supported analyses, 8
sequentially coupled, 187
understanding the process, 11
using a generic (third-party) mesh, 19
using manual mesh splitting, 23
variable mapping, 36
rotating structure analysis
Campbell diagram, 131
Campbell diagram analysis example, 137
choosing the appropriate reference frame option,
136
Coriolis analysis example, 139
flexible body dynamics, 134
harmonic analysis for unbalance forces example,142
introduction to, 129
natural frequencies, 136
rotating reference frame, 134
rotordynamics, 130
stationary reference frame, 130
understanding, 129
rotordynamics (see rotating structure analysis)
S
soil-pile-structure analysis, 185
State-Space Matrices
Export of, 179
submodeling, 151

ANSYS Mechanical APDL 2016 - Advanced Analysis Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ANSYS Mechanical APDL 2016 - Advanced Analysis Guide

Uploaded by

Copyright:

Available Formats

ANSYS Mechanical APDL Advanced Analysis

ANSYS, Inc. Release 17.0

ANSYS, Inc. is certified to ISO 9001:2008.

U.S. Government Rights

Published in the U.S.A.

2.10. Step 7: Perform a Multiframe Restart .............................................................................................. 38

3.6.2.2.5. Understanding the Remesh Log ........................................................................... 85

5.6.9. Example: Function-Based Initial State .................................................................................... 126

8.4.3. Review the Results ............................................................................................................... 172

3.35. 2-D Self-Contact .................................................................................................................................. 87

• Change materials and material properties

• Change section data and real constants

• Nonlinear structural static or transient analyses not involving contact or plasticity

• Nonlinear thermal static or transient analyses

The following Variational Technology topics are available:

1.1. Harmonic Sweep Using VT Accelerator

1.1.1. Structural Elements Supporting Frequency-Dependent Properties

Frequency-Dependent Material Properties

1.1.2. Harmonic Sweep for Structural Analysis with Frequency-Dependent

1.1.2.1. Beam Example

Figure 1.1: Y-Displacement Difference at End of Beam

The following rezoning topics are available:

For related information, see Mesh Nonlinear Adaptivity.

2.1. Benefits and Limitations of Rezoning

After remeshing the selected region, an acceptable new mesh is ready:

For a more detailed example, see Rezoning Examples (p. 41).

2.1.1. Rezoning Limitations

A condition of numerical instability can occur when a problem is nearly overconstrained.

2.2. Rezoning Requirements

Support Category Support Details

• SOLID185 -- B-bar method only (KEYOPT(1) = 0). Pure displacement

• SOLID186 -- Works with REMESH,READ only.

• SOLID187 -- Works with REMESH,READ only.

Support Category Support Details

• Supported for pair-based contact only.

Surface-effect • SURF153 and SURF154

Materials • Most structural materials are supported. The exceptions are:

Support Category Support Details

• For materials associated with user-defined state variables (TB,STATE), it

Analysis types • Static analysis with geometric nonlinearity (NLGEOM,ON).

• Fluid-penetration loads applied to contact elements (CONTA171,

• Do not remove nodal constraints (DDELE) during solution before rezoning

• Boundary nodes can have different nodal coordinate systems.

• Elements must be of the same element type, material, element coordinate

• Nonlinear stabilization is not supported.

2.3. Understanding the Rezoning Process

2. Initiate (p. 16) the rezoning process.

3. Select the region to remesh (p. 16).

7. Use the restart capability (p. 38) to continue the analysis.

2.3.1. Overview of the Rezoning Process Flow

• Figure 2.1: Rezoning Using a Program-Generated New Mesh

• Figure 2.3: Rezoning Using Manual Splitting of an Existing Mesh

Some mesh-generation methods are limited to 2-D analyses only.

Figure 2.1: Rezoning Using a Program-Generated New Mesh

Figure 2.3: Rezoning Using Manual Splitting of an Existing Mesh

2.3.2. Key Commands Used in Rezoning

Command Description Rezoning Comments

All nodes are updated to the deformed geometry in

Command Description Rezoning Comments

For more information, see Step 4: Perform the

2.4. Step 1: Determine the Substep to Initiate Rezoning

Determining Why the Solution Terminated

If the solution terminated because of a mesh distortion, it is a candidate for rezoning.