ANSYS Mechanical APDL Advanced Analysis Guide

Advanced Analysis Guide
ANSYS, Inc. Release 2022 R2

Southpointe July 2022
2600 Ansys Drive
Canonsburg, PA 15317 ANSYS, Inc. and
ansysinfo@ansys.com ANSYS Europe,
Ltd. are UL
http://www.ansys.com registered ISO
(T) 724-746-3304 9001: 2015
(F) 724-514-9494 companies.
Copyright and Trademark Information
© 2022 ANSYS, Inc. Unauthorized use, distribution or duplication is prohibited.
ANSYS, Ansys Workbench, AUTODYN, CFX, FLUENT and any and all ANSYS, Inc. brand, product, service and feature
names, logos and slogans are registered trademarks or trademarks of ANSYS, Inc. or its subsidiaries located in the
United States or other countries. ICEM CFD is a trademark used by ANSYS, Inc. under license. CFX is a trademark
of Sony Corporation in Japan. All other brand, product, service and feature names or trademarks are the property
of their respective owners. FLEXlm and FLEXnet are trademarks of Flexera Software LLC.
Disclaimer Notice
THIS ANSYS SOFTWARE PRODUCT AND PROGRAM DOCUMENTATION INCLUDE TRADE SECRETS AND ARE 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. and ANSYS Europe, Ltd. are UL registered ISO 9001: 2015 companies.
U.S. Government Rights
For U.S. Government users, except as specifically granted by the ANSYS, Inc. software license agreement, the use,
duplication, or disclosure by the United States Government is subject to restrictions stated in the ANSYS, Inc.
software license agreement and FAR 12.212 (for non-DOD licenses).
Third-Party Software
See the legal information in the product help files for the complete Legal Notice for ANSYS proprietary software
and third-party software. If you are unable to access the Legal Notice, contact ANSYS, Inc.
Published in the U.S.A.

Table of Contents
1. 2D to 3D Analysis .................................................................................................................................... 1
1.1. Benefits of 2D to 3D Analysis ............................................................................................................. 1
1.2. 2D to 3D Analysis Requirements and Limitations .............................................................................. 1
1.3. Understanding the 2D to 3D Analysis Process .................................................................................... 3
1.3.1. Understanding the 2D to 3D Analysis Process Flow ................................................................... 4
1.3.2. Key Commands Used in a 2D to 3D Analysis ............................................................................. 5
1.4. Performing a 2D to 3D Analysis ......................................................................................................... 6
1.4.1. Step 1: Determine the Substep to Initiate .................................................................................. 6
1.4.2. Step 2: Initiate the 2D to 3D Analysis ......................................................................................... 7
1.4.3. Step 3: Extrude the 2D Mesh to a New 3D Mesh ........................................................................ 7
1.4.3.1. Adding Contact Pairs ....................................................................................................... 8
1.4.4. Step 4: Map Boundary Conditions and Loads to the New 3D Mesh ............................................. 8
1.4.5. Step 5: Map Solution Results to the New 3D Mesh and Rebalance .............................................. 9
1.4.5.1. Example: Solution Variable Mapping and Rebalancing ...................................................... 9
1.4.5.2. Mapped Solution Results in Axisymmetric Cases ............................................................ 10
1.4.5.3. Mapped Solution Results in Plane Strain Cases ............................................................... 10
1.4.5.4. Rebalancing Considerations ........................................................................................... 11
1.4.5.4.1. Axisymmetric Rebalancing Cases with Reinforcing Elements .................................. 11
1.4.5.4.2. Large Penetration and Rebalancing ....................................................................... 11
1.4.5.5. Adding Contact Pairs ..................................................................................................... 12
1.4.5.6. Reviewing Results After Exiting Mechanical APDL ........................................................... 12
1.4.6. Step 6: Continue Your Analysis on the 3D Model ...................................................................... 12
1.5. Example: 2D to 3D Analysis of a Simple Threaded Connection .......................................................... 12
1.5.1. 2D Axisymmetric Modeling .................................................................................................... 13
1.5.2. 2D Axisymmetric Analysis Results ........................................................................................... 14
1.5.3. Generate the 3D Model from the 2D Model ............................................................................. 15
1.5.4. 2D to 3D Analysis Results ........................................................................................................ 16
1.5.5. Performing a 3D Analysis on the Extruded Model .................................................................... 18
1.5.6. 3D Analysis Results ................................................................................................................. 18
1.5.7. Input File for This Example ...................................................................................................... 18
1.6. 2D to 3D Analysis Restrictions ......................................................................................................... 23
2. Semi-Implicit Method ........................................................................................................................... 25
2.1. Semi-Implicit Basic Procedure ......................................................................................................... 25
2.2. Semi-Implicit Solution Controls ....................................................................................................... 28
2.3. Semi-Implicit Method Recommendations ........................................................................................ 32
2.4. Semi-Implicit Method Limitations .................................................................................................... 33
3. Automatic Transition Between Static and Transient Solutions ............................................................. 37
3.1. Solution Transition Procedure ......................................................................................................... 37
3.2. Solution Transition Method Recommendations ............................................................................... 40
3.3. Solution Transition Method Limitations ........................................................................................... 41
4. Initial State ............................................................................................................................................ 43
4.1. Specifying and Editing Initial-State Values ....................................................................................... 43
4.1.1. Element-Based Initial State ..................................................................................................... 44
4.1.2. Node-Based Initial State ......................................................................................................... 44
4.2. Initial-State Application ................................................................................................................... 44
4.2.1. Applying Initial Stress ............................................................................................................. 45
4.2.2. Converting Initial Stress to Initial Strain ................................................................................... 46
4.2.3. Applying Initial Strain ............................................................................................................. 46
4.2.4. Applying Initial Plastic Strain .................................................................................................. 47
Release 2022 R2 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. iii
4.2.5. Applying Initial Creep Strain ................................................................................................... 47

4.2.6. Applying Initial State with State Variables ............................................................................... 48
4.2.7. Applying Node-Based Initial Strain .......................................................................................... 48
4.2.8. Applying Initial Pore Pressure and Void Ratio ........................................................................... 48
4.2.9. Applying Initial Degree of Saturation and Relative Permeability ............................................... 49
4.2.10. Function-Based Initial State .................................................................................................. 49
4.3. Initial-State (.IST) File ................................................................................................................... 50
4.3.1. Data-Input Types Supported in the .IST File .......................................................................... 50
4.3.2. Specifying Parameter Data in the .IST File ............................................................................ 51
4.4. Using Coordinate Systems with Initial State ..................................................................................... 51
4.5. Initial-State Limitations ................................................................................................................... 52
4.6. Example Problems Using Initial State ............................................................................................... 53
4.6.1. Example: Initial Stress (IST File) ................................................................................................ 53
4.6.2. Example: Convert Initial Stress to Initial Strain (INISTATE Command) ......................................... 54
4.6.3. Example: Initial Stress (INISTATE Command) ............................................................................ 57
4.6.4. Example: Initial Strain ............................................................................................................. 57
4.6.5. Example: Initial Plastic Strain ................................................................................................... 58
4.6.6. Example: Initial Creep Strain ................................................................................................... 59
4.6.7. Example: Initial Plastic Strain with State Variables ................................................................... 61
4.6.8. Example: Node-Based Initial Strain .......................................................................................... 64
4.6.9. Example: Initial Pore Pressure and Void Ratio ........................................................................... 65
4.6.10. Example: Initial Degree of Saturation and Relative Permeability ............................................. 67
4.6.11. Example: Function-Based Initial State .................................................................................... 68
4.7. Writing Initial-State Values ............................................................................................................... 70
4.7.1. Example: Output From the INISTATE Command's WRITE Option ............................................... 70
5. Rotating Structure Analysis .................................................................................................................. 71
5.1. Understanding Rotating Structure Dynamics ................................................................................... 71
5.2. Choosing the Appropriate Reference Frame Option ......................................................................... 72
5.3. Using a Rotating Reference Frame ................................................................................................... 73
5.3.1. Elements Supported .............................................................................................................. 74
5.3.2. Spin-Softening Effect ............................................................................................................. 74
5.3.3. Analysis Types Supported ....................................................................................................... 75
5.3.3.1. Static (ANTYPE,STATIC) ................................................................................................... 75
5.3.3.2. Modal (ANTYPE,MODAL) ................................................................................................ 75
5.3.3.3. Linear Transient (ANTYPE,TRANS) ................................................................................... 75
5.3.3.4. Harmonic (ANTYPE,HARMIC) .......................................................................................... 76
5.4. Rotating Reference Frame Analysis Examples ................................................................................... 76
5.4.1. Example: Campbell Diagram Analysis of a Jeffcott Rotor .......................................................... 76
5.4.1.1. Problem Specifications .................................................................................................. 77
5.4.1.2. Input for the Analysis ..................................................................................................... 77
5.4.1.3. Output for the Analysis .................................................................................................. 79
5.4.2. Example: Campbell Diagram Analysis of a Non-Axisymmetric Beam Model .............................. 82
5.4.3. Example: Campbell Diagram Analysis of a 3D Bladed Shaft-Disk Assembly ............................... 89
5.4.4. Example: Unbalance Response of a Jeffcott Rotor .................................................................... 97
5.4.4.1. Problem Specification .................................................................................................... 97
iv of ANSYS, Inc. and its subsidiaries and affiliates.

5.4.4.3. Output for the Analysis ................................................................................................ 100
6. Cyclic-Loading Analysis and Cycle-Jump Method ............................................................................... 103
6.1. Cyclic-Loading Analysis ................................................................................................................ 103
6.1.1. Step 1: Define the Tabular Array ............................................................................................ 104
6.1.2. Step 2: Fill in the Cyclic-Loading Table Values ......................................................................... 104
6.1.3. Step 3. Apply the Cyclic-Loading Table(s) ............................................................................... 104
6.1.4. Step 4. Define Cyclic-Loading Parameters .............................................................................. 104
6.1.5. Step 5. Define Time-Stepping Parameters .............................................................................. 105
6.1.5.1. Enabling Time-Stepping for Each Time-Point Range ...................................................... 105
6.1.6. Step 6. Select Output Time Points .......................................................................................... 106
6.1.7. Step 7. Solve the Cyclic-Loading Analysis ............................................................................... 106
6.2. Cycle-Jump Analysis ...................................................................................................................... 107
6.2.1. Understanding the Cycle-Jump Method ................................................................................ 108
6.2.1.1. Jump Calculation ......................................................................................................... 109
6.2.1.1.1. Slope-Based Jump Calculation ............................................................................. 109
6.2.1.1.2. Variable-Based Jump Calculation ......................................................................... 109
6.2.1.2. Extrapolation Following a Jump ................................................................................... 109
6.2.2. Performing a Cycle-Jump Analysis ........................................................................................ 110
6.2.2.1. Initiating the Cycle-Jump Analysis ................................................................................ 110
6.2.2.2. Specifying the Intent of the Cycle Jump ........................................................................ 110
6.2.2.3. Other Cycle-Jump Options ........................................................................................... 111
6.2.2.3.1. Setting Minimum, Initial, and Maximum Cycles .................................................... 112
6.2.2.3.2. Empirical Adjustment of Minimum Intermediate Cycles ....................................... 112
6.2.2.3.3. Setting the Relative Time ..................................................................................... 112
6.2.2.3.4. Setting a Control Variable .................................................................................... 113
6.2.2.3.5. Material-ID-Dependent Jump Control .................................................................. 113
6.2.2.3.6. Material-ID- and/or Control-Variable-Dependent Jump Criterion .......................... 114
6.2.2.3.7. Jump-Calculation Option .................................................................................... 114
6.2.2.3.8. Statistical Jump Calculation ................................................................................. 114
6.2.2.4. Understanding Cycle-Jump Solution Output ................................................................ 115
6.2.3. Cycle-Jump Recommendations ............................................................................................. 116
6.2.4. Cycle-Jump Limitations ........................................................................................................ 117
6.2.5. Example: Cycle-Jump Analysis ............................................................................................... 117
6.2.5.1. Input File Used in This Example .................................................................................... 120
7. Submodeling ....................................................................................................................................... 125
7.1. Understanding Submodeling ........................................................................................................ 125
7.1.1. Nonlinear Submodeling ....................................................................................................... 126
7.2. Using Submodeling ...................................................................................................................... 126
7.2.1. Create and Analyze the Coarse Model ................................................................................... 127
7.2.2. Create the Submodel ............................................................................................................ 128
7.2.3. Perform Cut-Boundary Interpolation ..................................................................................... 129
7.2.4. Analyze the Submodel ......................................................................................................... 131
7.2.5. Verify the Distance Between the Cut Boundaries and the Stress Concentration ...................... 133
7.3. Example Submodeling Analysis Input ............................................................................................ 134
7.3.1. Submodeling Analysis Input: No Load-History Dependency ................................................... 134
7.3.2. Submodeling Analysis Input: Load-History Dependency ........................................................ 135
7.4. Shell-to-Solid Submodels .............................................................................................................. 141
7.5. Where to Find Examples ................................................................................................................ 143
8. Element Birth and Death ..................................................................................................................... 145
8.1. Elements Supporting Birth and Death ........................................................................................... 145
of ANSYS, Inc. and its subsidiaries and affiliates. v
8.2. Understanding Element Birth and Death ....................................................................................... 145

8.3. Element Birth and Death Usage Hints ............................................................................................ 146
8.3.1. Changing Material Properties ............................................................................................... 147
8.4. Using Birth and Death ................................................................................................................... 147
8.4.1. Build the Model .................................................................................................................... 147
8.4.2. Apply Loads and Obtain the Solution .................................................................................... 147
8.4.2.1. Define the First Load Step ............................................................................................ 147
8.4.2.1.1. Sample Input for First Load Step .......................................................................... 148
8.4.2.2. Define Subsequent Load Steps ..................................................................................... 148
8.4.2.2.1. Sample Input for Subsequent Load Steps ............................................................. 148
8.4.2.3. Using TABLE Type Array Parameters to Control Birth and Death ..................................... 149
8.4.3. Review the Results ............................................................................................................... 149
8.4.4. Use Analysis Results to Control Birth and Death .................................................................... 150
8.4.4.1. Sample Input for Deactivating Elements ....................................................................... 150
8.5. Where to Find Examples ................................................................................................................ 150
9. User-Programmable Features and Nonstandard Uses ....................................................................... 151
9.1. User-Programmable Features (UPFs) .............................................................................................. 151
9.1.1. Understanding UPFs ............................................................................................................. 151
9.1.2. Types of UPFs Available ........................................................................................................ 152
9.2. Nonstandard Uses of the Program ................................................................................................. 153
9.2.1. What Are Nonstandard Uses? ................................................................................................ 154
9.2.2. Hints for Nonstandard Use .................................................................................................... 154
10. State-Space Matrices Export ............................................................................................................. 157
10.1. State-Space Matrices Based on Modal Analysis ............................................................................. 157
10.1.1. Examples of SPMWRITE Command Usage ........................................................................... 157
10.1.2. Example of Reduced Model Generation in Ansys and Usage in Twin Builder ......................... 159
10.1.2.1. Problem Description .................................................................................................. 159
10.1.2.2. Problem Specifications ............................................................................................... 159
10.1.2.3. Input File for the Analysis ........................................................................................... 159
11. Soil-Pile-Structure Analysis ............................................................................................................... 163
12. Coupling to External Aeroelastic Analysis of Wind Turbines ............................................................ 165
12.1. Sequential Coupled Wind Turbine Solution in Mechanical APDL ................................................... 165
12.1.1. Procedure for a Sequentially Coupled Wind Turbine Analysis ............................................... 165
12.1.2. Output from the OUTAERO Command ................................................................................ 166
12.1.3. Example Substructuring Analysis to Write Out Aeroelastic Analysis Input Data ..................... 167
13. Applying Ocean Loading from a Hydrodynamic Analysis ................................................................ 171
13.1. How Hydrodynamic Analysis Data Is Used .................................................................................... 171
13.2. Hydrodynamic Load Transfer with Forward Speed ........................................................................ 172
13.3. Hydrodynamic Data File Format .................................................................................................. 172
13.3.1. Comment (Optional) .......................................................................................................... 172
13.3.2. General Model Data ............................................................................................................ 173
13.3.3. Hydrodynamic Surface Geometry ....................................................................................... 173
13.3.4. Wave Periods ...................................................................................................................... 174
13.3.5. Wave Directions .................................................................................................................. 174
13.3.6. Panel Pressures ................................................................................................................... 175
13.3.7. Morison Element Hydrodynamic Definition ......................................................................... 176
13.3.8. Morison Element Wave Kinematics Definition ...................................................................... 176
13.3.9. RAO Definition ................................................................................................................... 177
13.3.10. Mass Properties ................................................................................................................ 178
13.4. Example Analysis Using Results from a Hydrodynamic Diffraction Analysis ................................... 179
vi of ANSYS, Inc. and its subsidiaries and affiliates.
List of Figures
1.1. 2D to 3D Process Flow ............................................................................................................................. 5
1.2. Axisymmetric to 3D Solid Extrusion ......................................................................................................... 7
1.3. 2D Plane Strain to 3D Solid Extrusion ....................................................................................................... 7
2.1. Semi-Implicit Example Model ................................................................................................................ 27
3.1. Solution Transition Example Model - Collapse of a Slender Beam ............................................................ 38
5.1. Campbell Diagram for the Jeffcott Rotor - Stationary Reference Frame (SRF) ........................................... 80
5.2. Campbell Diagram for the Jeffcott Rotor - Rotating Reference Frame (RRF) ............................................. 81
5.3. Relationship Between SRF and RRF Frequencies .................................................................................... 81
5.4. Asymmetric Rotor ................................................................................................................................. 82
5.5. Campbell Diagram for the Undamped Model ........................................................................................ 86
5.6. Stability Values for the Undamped Model .............................................................................................. 87
5.7. Campbell Diagram for the Damped Model ............................................................................................ 88
5.8. Stability Values for the Damped Model .................................................................................................. 89
5.9. Bladed Shaft-Disk Assembly (THETA = 0) ............................................................................................... 90
5.10. Bladed Shaft-Disk Assembly (THETA = 90) ............................................................................................ 91
5.11. Campbell Diagram THETA = 0 Degrees ................................................................................................ 96
5.12. Campbell Diagram THETA = 90 Degrees ............................................................................................... 97
5.13. Unbalance Force Response in SRF ..................................................................................................... 100
5.14. Static Response in RRF ....................................................................................................................... 101
6.1. Time Points and Ranges in a Cyclic-Loading Table ................................................................................ 105
6.2. Analysis with Two Standard Solutions Followed by a Cyclic-Loading Analysis ........................................ 107
6.3. Response of a Structure Under Cyclic Loading ..................................................................................... 108
6.4. Analysis with Standard Solutions Preceding the Cyclic-Loading Analysis ............................................... 111
6.5. Plate with Hole ................................................................................................................................... 118
7.1. Submodeling of a Pulley ..................................................................................................................... 125
7.2. Coarse Model ...................................................................................................................................... 127
7.3. Submodel Superimposed Over Coarse Model ...................................................................................... 128
7.4. Cut Boundaries on the Submodel ........................................................................................................ 129
7.5. Loads on the Submodel ...................................................................................................................... 132
7.6. Data Flow Diagram for Submodeling (Without Temperature Interpolation) .......................................... 132
7.7. Contour Plots to Compare Results ....................................................................................................... 133
7.8. Path Plots to Compare Results ............................................................................................................. 133
7.9. Coarse-Mesh Model, Submodel, and Fine-Mesh Model ......................................................................... 137
7.10. Equivalent Plastic Strain Through Various Cut-Boundary Conditions and Load Steps ........................... 138
7.11. Equivalent Plastic Strain Distributions in a Submodeling Analysis with Load-History Dependency ....... 139
7.12. 3D Solid Submodel Superimposed on Coarse Shell Model .................................................................. 141
7.13. Node Rotations ................................................................................................................................. 142
10.1. Simulation Schematic ........................................................................................................................ 161
10.2. Evolution of Spring Force .................................................................................................................. 161
13.1. Hydrodynamic Diffraction Analysis Pressure Results ........................................................................... 179
13.2. Analysis Results Using Pressure Data from a Hydrodynamic Diffraction Analysis ................................. 181
of ANSYS, Inc. and its subsidiaries and affiliates. vii
viii of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 1: 2D to 3D Analysis
It is sometimes necessary to extend 2D nonlinear finite element results to a corresponding extruded
3D body such that the solution can continue based on the 3D model.
For example, in a tire analysis, the 2D axisymmetric tire-inflation results must be extended to an extruded
3D tire model before a footprint analysis can be performed.
The 2D to 3D analysis capability extrudes (EEXTRUDE) a 2D deformed mesh to a new 3D mesh. The
program updates the database as necessary, generates contact elements if needed, and transfers
boundary conditions, loads and nodal temperatures from the 2D mesh to the extruded 3D mesh. All
solved variables (node and element solutions) are then mapped (MAP2DTO3D) to the new 3D mesh,
and the program rebalances solutions for the 3D model automatically.
The following 2D to 3D analysis topics are available:

1.1. Benefits of 2D to 3D Analysis
1.2. 2D to 3D Analysis Requirements and Limitations
1.3. Understanding the 2D to 3D Analysis Process
1.4. Performing a 2D to 3D Analysis
1.5. Example: 2D to 3D Analysis of a Simple Threaded Connection
1.6. 2D to 3D Analysis Restrictions
To study 2D to 3D analysis examples, see Threaded Connection Analysis and Tire Performance Simulation
in the Technology Showcase: Example Problems.
1.1. Benefits of 2D to 3D Analysis

Mapping solution variables from a 2D mesh to an extruded 3D mesh enables you to perform a multistage
nonlinear analysis. For example, in a tire analysis, 2D axisymmetric inflation results are required for a
subsequent 3D footprint analysis.
In effect, you can continue with a 3D analysis on the extruded body after mapping solution results from
the 2D body.
The 2D to 3D method is very efficient for a nonlinear analysis with multiple load steps, as only the last
few load steps cause general 3D deformation. The prior load steps occur within the 2D model.
1.2. 2D to 3D Analysis Requirements and Limitations

All multiframe restart files must be available.
Following are the 2D elements and the materials, loads, and boundary conditions that can be used for
2D to 3D analysis:
of ANSYS, Inc. and its subsidiaries and affiliates. 1
2D to 3D Analysis
Support Category Requirements

Solid elements • PLANE182[a]and PLANE183[a]
Reinforcing • REINF263[a]
elements
Contact • TARGE169
elements
• 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 (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
• CONTA174 with any of the following valid KEYOPT settings:
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-to-flexible[c]

[b]
behavior
• Flexible-to-flexible
• Self-contact
2 of ANSYS, Inc. and its subsidiaries and affiliates.
Understanding the 2D to 3D Analysis Process
Support Category Requirements

Materials • Most structural materials[d][e]
Analysis types • Static analysis with geometric nonlinearity (NLGEOM,ON).
Loads and • Displacements, forces, pressures, and nodal temperatures

boundary (BF,TEMP)[g]
conditions
(BCs)[f ] • Tabular displacements[h]
• Tabular pressures that are functions of time only[h]
• Fluid-penetration loads applied to contact elements (SFE)[h][i]
• SFCONTROL not supported
Files • .rdb, .rst, .ldhi, .ist, and .cdb.
[a] Axisymmetric (with or without torsion) and plane strain states of stress only. For PLANE182,
only the B-Bar method (KEYOPT(1) = 0) is supported. For REINF263 elements, if the fibers
have an orientation angle that causes torsion in an axisymmetric analysis, use the axsiym-
metrixc-with-torsion option (KEYOPT(3) = 6) for the base elements.
[b] Pilot nodes in 2D are retained as pilot nodes in 3D.
[c] 2D target elements (line) are extruded in 3D as tangent planes or as annuli in axisymmetric
extrusion. The extrusion is always planar in plane strain extrusion.
[d] Exceptions are: CAST (cast iron), CDM (Mullins effect), CONCR (concrete), CZM (cohesive
zone), DMGE and DMGI (damage), MPLANE (microplane), SMA (shape memory alloy), and
SWELL (swelling).
[e] 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
3D 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).
[f ] Do not remove nodal constraints (DDELE, FDELE, BFDELE, SFDELE) during solution before
issuing MAP2DTO3D.
[g] Loads applied on surface-effect elements (such as SURF153) are not supported.
[h] The axisymmetric option with torsion is not supported.
[i] CONTA172 and CONTA174
The EEXTRUDE command documentation shows the topological mapping of 2D elements (solid, contact,
and target) into specific 3D elements.
1.3. Understanding the 2D to 3D Analysis Process

Following is the general process for performing a 2D to 3D analysis:
1. Determine the load step and substep (p. 6) in the 2D model at which extrusion should occur.
2. Initiate (p. 7) the 2D to 3D analysis process.
3. Extrude the 2D mesh (p. 7) and generate contact elements (if any) on the new 3D domain.
2D to 3D Analysis
Optional: After the extrusion, you can manually add new contact pairs if necessary.
4. Map boundary conditions and loads (p. 8) from the 2D mesh to the new 3D mesh.
5. Map solution variables (p. 9) from the 2D mesh to the new 3D mesh and rebalance the mapped
solutions (if specified).
6. Continue as a 3D analysis (p. 12) via a multiframe restart.
Note:
Although the preferred method for continuing the 3D analysis is via a multiframe
restart, you can instead initiate a new analysis using the 2D solution as the initial
state (p. 43), requiring the following:
• The initial-state values saved after Step 5 (INISTATE,WRITE).
• The .cdb file that includes the 3D mesh.
Some deformation history variables may not be available in the .ist file. It may be
necessary to include a dummy load step to achieve equilibrium before adding new
loads.
Because the entire 2D mesh is used for the extrusion process, only one MAP2DTO3D command block
can be issued at a given loadstep and substep.
The following topics provide more general information about the 2D to 3D analysis process:
1.3.1. Understanding the 2D to 3D Analysis Process Flow
1.3.2. Key Commands Used in a 2D to 3D Analysis
1.3.1. Understanding the 2D to 3D Analysis Process Flow

The following flowchart illustrates the general 2D to 3D analysis process:
Understanding the 2D to 3D Analysis Process
Figure 1.1: 2D to 3D Process Flow
For information about the commands shown in the flowchart, see Key Commands Used in a 2D to
3D Analysis (p. 5).
1.3.2. Key Commands Used in a 2D to 3D Analysis

Following is a description of the key commands used in a 2D to 3D analysis:
Command Description 2D to 3D Analysis Comments

/CLEAR,NOSTART
Clears the database Always clear the database before reentering the
solution processor (/SOLU) and initiating the 2D to
3D analysis process.
MAP2DTO3D,START
Initiates the 2D to 3D When you initiate a 2D to 3D analysis, the program
analysis verifies that the necessary files (.rdb, .rst,
.rxxx, and .ldhi) exist for the specified substep
and rebuilds the data environment at that substep.
2D to 3D Analysis
Command Description 2D to 3D Analysis Comments

All nodes are updated to the deformed
geometry in preparation for extrusion.
EEXTRUDE Extrudes the 2D mesh The entire 2D mesh is selected automatically
to a 3D mesh and for extrusion. Partial mesh extrusion is not
regenerates contact supported.
pairs on the 3D model
if necessary. This command also controls how
boundary-condition and load-mapping occurs.
After extrusion, you can
manually add new Depending on the arguments specified for this
contact pairs which command, some or all of the new nodes may
have not yet contacted, be rotated to local nodal coordinate systems.
if necessary. Some
limitations apply for
rigid-to-flexible contact
pairs (p. 8).
MAP2DTO3D,FINISH
Maps the loads, Equivalent boundaries and loads on the 3D model
temperatures, and boundary are generated. If necessary, you can control how
conditions from the 2D the equivalent loads and constraints are generated
mesh to the corresponding (EEXTRUDE).
3D mesh.
MAP2DTO3D,SOLVE
Maps node and element Maps the solved nodal and element solutions from
solutions and rebalance the the 2D deformed mesh to the newly extruded 3D
results. mesh and rebalances the mapped solution results
through equilibrium.
Continue with your analysis of the 3D model via a multiframe restart (or by starting a new 3D analysis
using the 2D solution as the initial state (p. 43)).
1.4. Performing a 2D to 3D Analysis

The following steps describe how to perform a 2D to 3D analysis:
1.4.1. Step 1: Determine the Substep to Initiate
1.4.2. Step 2: Initiate the 2D to 3D Analysis
1.4.3. Step 3: Extrude the 2D Mesh to a New 3D Mesh
1.4.4. Step 4: Map Boundary Conditions and Loads to the New 3D Mesh
1.4.5. Step 5: Map Solution Results to the New 3D Mesh and Rebalance
1.4.6. Step 6: Continue Your Analysis on the 3D Model
1.4.1. Step 1: Determine the Substep to Initiate

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

2D to 3D analysis is based on a new model with a higher dimension (3D), extruded from a specific
substep of a lower dimensional (2D) model solution. The analysis process therefore requires a clean
database.
To initiate a 2D to 3D analysis:
1. Clear the database (/CLEAR,NOSTART).
2. Reenter the solution processor (/SOLU).
3. Initiate 2D to 3D analysis, specifying the load step and substep (p. 6) at which 2D to 3D analysis
should occur (MAP2DTO3D,START,VALUE1,VALUE2).
Result: The program updates the geometry to the deformed configuration.
Proceed to Step 3: Extrude the 2D Mesh to a New 3D Mesh (p. 7).
1.4.3. Step 3: Extrude the 2D Mesh to a New 3D Mesh

Issue the EEXTRUDE command to extrude the 2D mesh to the 3D mesh.
The following figures illustrate how extrusion generates 3D meshes from an axisymmetric and a plane
strain 2D mesh, respectively:
Figure 1.2: Axisymmetric to 3D Solid Extrusion
Figure 1.3: 2D Plane Strain to 3D Solid Extrusion
2D to 3D Analysis
Extrusion preserves the 2D mesh topology on the generating plane and replicates it through the
depth of the extruded body.
Extruded elements and nodes have the properties or equivalent properties of the elements and nodes
from which they were created. If a given element or a node belongs to specific components, the ex-
truded elements and nodes belong to the same components. If a given node is rotated on the 2D
modeling plane (global XOY), the extruded nodes are rotated in the radial plane (axisymmetric or tire
option), or rotated in the planes parallel to XOY (plane strain).
For axisymmetric cases (EEXTRUDE,AXIS) and for the tire option (EEXTRUDE,TIRE), you can control
the nodal orientation in the third direction (BCKEY on the EEXTRUDE command).
The extrusion process generates 3D contact and target elements with the solid elements. 2D rigid
target elements are deleted, and corresponding 3D rigid target elements are generated. EEXTRUDE
can control how the contact and target elements are generated in the third direction and the corres-
ponding mesh density.
After extrusion, proceed to Step 4: Map Boundary Conditions and Loads to the New 3D Mesh (p. 8).
1.4.3.1. Adding Contact Pairs

To add contact pairs manually, do so immediately after issuing the EEXTRUDE command.
Newly added contact pairs must be in a pre-contact state or just touching; otherwise, they affect
the equilibrium of (and thereby change the solution of ) the extruded 3D model.
Rigid-to-flexible contact-pair limitations:
• If adding a rigid-to-flexible contact pair to the 3D model, you cannot add a pilot node if the
contact pair in the 2D model does not have one.
• For existing rigid-to-flexible contact pairs in the 3D model, you cannot modify or replace rigid
target surfaces, even if they are in a pre-contact state.
1.4.4. Step 4: Map Boundary Conditions and Loads to the New 3D Mesh
Issue the MAP2DTO3D,FINISH command to transfer boundary conditions, pressure loads, applied
nodal forces, applied nodal displacements, and applied nodal temperatures from the 2D mesh to the
corresponding entities in the extruded 3D model.
Applied nodal displacements in the 2D model X and Y directions transfer to the 3D model in the ra-
dial and axial directions. If applying rotation ROTY via the axisymmetric option with torsion, the pro-
gram applies a displacement constraint in the hoop direction (Uz = 0) on the 3D model. If rotating
only the nodes with loads or displacements to a local Cartesioan coordinate system (BCKEY = 1 on
the EEXTRUDE command), the program resets displacement values so that displacements re-accumu-
late from zero.
Temperatures and pressures transfer to the nodes and elemental facets of the 3D model.
In the same way that pressure is applied, the program redistributes applied forces at nodes in the 2D
model to all extruded nodes in the hoop direction of the 3D model. For the axisymmetric option with
torsion, the program converts applied torsion MY in the 2D model into a concentrated force (by di-
viding it by the current radius [x coordinate]), then redistributes the force to all nodes in the hoop
direction as an applied force.
Constraints and loads applied at nodes not associated with any 2D elements (such as pilot nodes)
remain unchanged during boundary-condition mapping.
After mapping the boundary conditions and loads to the 3D mesh, proceed to Step 5: Map Solution
Results to the New 3D Mesh and Rebalance (p. 9).
1.4.5. Step 5: Map Solution Results to the New 3D Mesh and Rebalance
Issue the MAP2DTO3D,SOLVE command to map the nodal and element solutions to the 3D model
and to initiate rebalancing.
For more information about the solution-mapping phase of the 2D to 3D analysis, see:
1.4.5.1. Example: Solution Variable Mapping and Rebalancing
1.4.5.2. Mapped Solution Results in Axisymmetric Cases
1.4.5.3. Mapped Solution Results in Plane Strain Cases
1.4.5.4. Rebalancing Considerations
1.4.5.6. Reviewing Results After Exiting Mechanical APDL
After mapping the solution results, proceed to Step 6: Continue Your Analysis on the 3D Model (p. 12).
1.4.5.1. Example: Solution Variable Mapping and Rebalancing

After issuing the MAP2DTO3D,SOLVE command, the program displays a message similar to the
following, then performs rebalancing iterations for the mapped solution results:
S O L U T I O N O P T I O N S
PROBLEM DIMENSIONALITY. . . . . . . . . . . . .3D

DEGREES OF FREEDOM. . . . . . UX UY UZ ROTY
ANALYSIS TYPE . . . . . . . . . . . . . . . . .STATIC (STEADY-STATE)
MAP2DTO3D,SOLVE FOR 2D TO 3D MAPPING. . . . .YES
NONLINEAR GEOMETRIC EFFECTS . . . . . . . . . .ON
STRESS-STIFFENING . . . . . . . . . . . . . . .ON
EQUATION SOLVER OPTION. . . . . . . . . . . . .SPARSE
NEWTON-RAPHSON OPTION . . . . . . . . . . . . .PROGRAM CHOSEN
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 . . . . . . . . . 10
MINIMUM NUMBER OF SUBSTEPS . . . . . . . . . 10
MAX. NUMBER OF SUBSTEPS FOR MAP2DTO3D. . .500
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
COPY INTEGRATION POINT VALUES TO NODE . . . . . YES
PRINT OUTPUT CONTROLS . . . . . . . . . . . . .NO PRINTOUT
DATABASE OUTPUT CONTROLS
ITEM FREQUENCY COMPONENT
ALL ALL
2D to 3D Analysis
When rebalancing is complete, the program displays a message similar to the following:
*** LOAD STEP 1 SUBSTEP 11 COMPLETED. CUM ITER = 23
*** TIME = 1.00000 REBALANCE FACTOR = 1.00000
MAP2DTO3D,SOLV IS DONE SUCCESSFULLY IN 1 SUBSTEPS FOR 2D

TO 3D MAPPING.
Results of the analysis on the 3D model after rebalancing are output to the results file regardless
of any prior results file setting. If you have set the postprocessing option to list a summary of each
load step (SET,LIST), the program generates following output:
*** LOAD STEP 1 SUBSTEP 11 COMPLETED. CUM ITER = 23
*** TIME = 1.00000 REBALANCE FACTOR = 1.00000
MAP2DTO3D,SOLV IS DONE SUCCESSFULLY IN 1 SUBSTEPS FOR 2D TO 3D MAPPING.
FINISH SOLUTION PROCESSING WITH 1 SUCCESSFUL REMESHING(S)
***** INDEX OF DATA SETS ON RESULTS FILE *****
SET TIME/FREQ LOAD STEP SUBSTEP CUMULATIVE
1 0.10000 1 1 2
2 0.20000 1 2 4
3 0.30000 1 3 6
4 0.40000 1 4 8
5 0.50000 1 5 10
6 0.60000 1 6 12
7 0.70000 1 7 14
8 0.80000 1 8 16
9 0.90000 1 9 18
10 1.0000 1 10 20
11 1.0000 1 11 23 mesh changed
In this example, the 2D to 3D analysis occurred at TIME = 1.
Two result data sets are generated, one for the 2D model, the other for the 3D model (indicated
by mesh changed).
1.4.5.2. Mapped Solution Results in Axisymmetric Cases

In axisymmetric cases (EEXTRUDE,AXIS), the element coordinate system for the new 3D elements
is the co-rotated 2D material system on the radial plane. The third direction is in the hoop direction
(similar to a cylindrical coordinate system). This behavior differs from that of the coordinate systems
of elements created directly from 3D geometry.
1.4.5.3. Mapped Solution Results in Plane Strain Cases

In plane strain cases (EEXTRUDE,PLANE), extra boundary conditions UZ = 0 are applied at nodes
where UX and UY = 0 are applied in the 2D model. The boundary conditions restrain the rigid-body
motions in the global Z direction.
Always verify that sufficient boundary conditions exist to constrain the rigid-body motion. If needed,
you can apply additional constraints after issuing the MAP2DTO3D,FINISH command but before
issuing the MAP2DTO3D,SOLVE command.
1.4.5.4. Rebalancing Considerations

Successful 2D to 3D solution rebalancing is typically achieved using the default maximum allowed
number of substeps.
If rebalancing is unsuccessful, you can increase the number of allowed substeps (via VALUE1 on
the MAP2DTO3D,SOLVE command). Before doing so, however, check the extruded 3D model to
ensure that all contact pairs are reconstructed completely, and that all boundary conditions and
loads have transferred correctly.
Rebalancing difficulties can occur if the extruded 3D model is not:
• a full circle in the hoop direction (axisymmetric case), or
• of sufficient length in the global Z direction (plane strain case).
To aid convergence, you can constrain the motion in the normal direction of the two ending planes.
If needed, you can constrain more planes parallel to the ending planes (the radial plane in
axisymmetric cases, and the plane parallel to the global XOY direction in plane strain cases).
1.4.5.4.1. Axisymmetric Rebalancing Cases with Reinforcing Elements

For axisymmetric cases, rebalancing may fail if reinforcing elements exist and:
• the reinforcing elements are oriented in a direction other than in the hoop and radial directions,
and
• the torsion degree of freedom is not enabled.
Failure occurs if the orientation of the reinforcing elements causes torsion but the torsion option
was not set in the 2D model. Not setting the torsion option is equivalent to introducing extra
constraints in the hoop direction; however, after torsion transfers to the 3D model, the equivalent
constraints are not constructed. To resolve the issue, allow torsion in 2D analysis, or constrain
the motion in the hoop direction for all the nodes of the 3D model.
1.4.5.4.2. Large Penetration and Rebalancing

During rebalancing, the porgram may issue a warning message similar to the following:
*WARNING*: Initial penetration 4.28926118 may be too large

for contact element 12685 (with target element 14190).
Check whether the pinball region is big enough to capture
initial interference.
If you encounter such a message during rebalancing, consider these remedies:
• Increase the number of elements (thereby increasing the corresponding number of contact
and target elements) in the hoop direction during the 2D to 3D extrusion process (EEX-
TRUDE,,NELEM).
• Ensure that target surfaces are at least equal to or larger than the contact surfaces.
• During the mapping process (after EEXTRUDE and before MAP2DTO3D,FINISH), try reducing
the pinball region (via the real constant PINB) for the problem contact pair.
2D to 3D Analysis

Contact pairs added manually after extrusion should be in a pre-contact state or just touching. If
contact occurs, the new contact pairs can affect the equilibrium of (and thereby change the solution
of ) the extruded 3D model or cause convergence difficulties.
1.4.5.6. Reviewing Results After Exiting Mechanical APDL

If you exit the Mechanical APDL program after the solution of a 2D to 3D analysis and want to review
the results of the analysis later, issue the /FILNAME,Jobname command the after starting the
program.
To compare the 2D to 3D analysis results to those of either the original 2D model or the new 3D
model, consider issuing the ERESX,NO command to prevent the program from introducing integ-
ration-point extrapolation results in the 2D and 3D model results.
Because the default PowerGraphics display mode (/GRAPHICS,POWER) displays the results on the
model's exterior facets only, you may prefer to compare all geometry and results (/GRAPHICS,FULL)
of the 2D to 3D analysis to the PowerGraphics-only results of the 2D model.
Note:
For /GRAPHICS,FULL, reinforcing element results are not included.
1.4.6. Step 6: Continue Your Analysis on the 3D Model

Using the rebalanced solution results for the new 3D model, you can continue your analysis via a
multiframe restart (or by starting a new 3D analysis using the 2D solution as the initial state (p. 43),
as described in Understanding the 2D to 3D Analysis Process (p. 3)).
If the MAP2DTO3D command used the results at the end of a load step, you can apply new loads
directly on the 3D model and proceed with the 3D analysis. If the command used the results at a
substep in the middle of a load step, end the current load step (ANTYPE,RESTART) before continuing
as a new load step with new loads..
If you rotated only the nodes with loads or displacements to a local Cartesian coordinate system
during extrusion (BCKEY = 1 on the EEXTRUDE command), the program resets displacement values
and initiates re-accumulation from zero. Newly applied displacements are therefore the new values
accumulated during the 3D analysis phase only, rather than from the beginning of the 2D analysis.
Regardless of the BCKEY value specified on the EEXTRUDE command, however, displacements shown
in the results file after mapping indicate the displacements at the 3D phase only (and not from the
initial stress-free state).
1.5. Example: 2D to 3D Analysis of a Simple Threaded Connection

Threaded connectors are commonly used components in the piping and offshore industry. The example
presented here is a simulation of a simple threaded connection.
The analysis occurs in two load steps:
Example: 2D to 3D Analysis of a Simple Threaded Connection
Load Step 1: Internal pressure and tensile force loads are applied to a 2D model.
Load Step 2: A bending load is applied to the extruded 3D model.
Because the geometry and loadings in the first load step are axisymmetric in nature, the analysis begins
with a 2D axisymmetric model to solve for internal pressure and tensile loadings. Using a 2D to 3D
analysis, the 2D deformed mesh (left) is extruded to a new 3D mesh (right):
The analysis continues on the 3D model, on which a bending load is applied.
1.5.1. 2D Axisymmetric Modeling

The 2D axisymmetric model of the simple threaded connection has two contact pairs:
• A flexible-to-flexible contact pair at the threads.
• A rigid-to-flexible redundant contact pair at the top face.
The rigid-to-flexible contact pair plays no role in the 2D axisymmetric analysis. It is required later,
however, for applying the bending load on the extruded 3D model.
Elastic-plastic material properties are used with bilinear isotropic hardening (TB,PLAS,,,,BISO). Internal
pressure is applied on the inner surfaces. Tensile force loading is applied on the top face. A static
analysis with large-deflection effects (NLGEOM,ON) is performed on the 2D axisymmetric model.
2D to 3D Analysis
1.5.2. 2D Axisymmetric Analysis Results

Following are the equivalent stress and total mechanical strain plots from the 2D axisymmetric ana-
lysis:
1.5.3. Generate the 3D Model from the 2D Model

Step Description Command Comments
Initiate the 2D to 3D Begins the analysis at the last (38th) substep
1 MAP2DTO3D,START,1,38
analysis. of the first load step.
Extrude the 3D mesh Revolves the 2D deformed geometry about
2 from the 2D deformed EEXTRUDE,AXIS,36 the global Y axis with 36 elements in the
mesh. hoop direction.
Transfers boundary conditions, pressure
loads, applied nodal forces, applied nodal
Map boundary displacements, and applied nodal
3 MAP2DTO3D,FINISH
conditions and loads. temperatures from the 2D mesh to the
corresponding entities in the extruded 3D
model
Transfers nodal and element solutions from
4 Map solution variables. MAP2DTO3D,SOLVE the 2D model to the 3D model and initiates
rebalancing.
2D to 3D Analysis
1.5.4. 2D to 3D Analysis Results

The following figures show the equivalent stress plots from the 2D axisymmetric model to the extruded
3D model:
2D to 3D Analysis
1.5.5. Performing a 3D Analysis on the Extruded Model

After performing a multiframe restart, the analysis resumes using the new 3D model, where a bending
load is applied:
Step Description Command(s) Comments

1 Restart the ANTYPE,,RESTART,1,39 Performs a multiframe restart at the last converged
analysis. substep (after MAP2DTO3D,SOLVE). In this case, it is
substep 39.
2 Apply the CNKMOD,9,12,5 This contact pair was created in the 2D model and
bending load. transferred to the extruded 3D model automatically
D, during the 2D to 3D analysis. The CNKMOD command
999,ROTZ,-0.00349 changes the behavior of the contact pair to bonded.
The D command applies the bending load on the
pilot node of the rigid-to-flexible contact pair (on the
top of the 3D model).
3 Solve and review SOLVE Solves the 3D analysis and enables you to review
results. results via standard output commands (PLNSOL and
*GET) in POST1.
For more information, see Input File for This Example (p. 18).
1.5.6. 3D Analysis Results

The following figure shows the stress plot from the 3D analysis with bending load:
1.5.7. Input File for This Example

Following is the input file used in this example 2D to 3D analysis of a simple threaded connection:
! Input file for Map2dto3d example number 1

/fil,Map2dto3d_Example1
/PREP7
!************************************************
!Create the Geometry of Threaded Connection
!************************************************
k,1,75
k,2,50
k,3,50,10
k,4,62,10
k,5,62,15
k,6,60,15.5
k,7,60,17.5
k,8,62,18
k,9,62,20
k,10,60,20.5
k,11,60,22.5
k,12,62,23
k,13,62,25
k,14,60,25.5
k,15,60,27.5
k,16,62,28
k,17,62,30
k,18,62,35
k,19,75,35
l,1,2
l,2,3
l,3,4
l,4,5
l,5,6
l,6,7
l,7,8
l,8,9
l,9,10
l,10,11
l,11,12
l,12,13
l,13,14
l,14,15
l,15,16
l,16,17
l,17,18
l,18,19
l,19,1
al,all
lsel,s,,,5,15
lgen,2,all,,,,,,,0
allsel,all
allsel,below,area
lsel,invert
lplot
LGEN, ,all, , ,-0.9,0.2, , , ,1
allsel,all
ldel,20
k,20,61.1,15.2
l,21,20
k,41,61.1,13.2
l,20,41
k,42,59.1,12.7
l,41,42
k,43,59.1,11
l,42,43
k,51,61.1,40
l,31,51
k,52,66,40
l,51,52
k,53,66,100
l,52,53
k,54,50,100
2D to 3D Analysis
l,53,54
k,55,50,35
l,54,55
k,56,50,11
l,55,56
l,56,43
allsel,all
allsel,below,area
lsel,invert
al,all
k,100,45,100
k,101,71,100
l,100,101
allsel,all
!************************************************
!Material Properties
!************************************************
!BISO Material
MP,EX,1,3e06
MP,PRXY,1,0.3
ET = 3e05
EP = 3e06*ET/(3e06-ET)
TB,PLAS,1,,,BISO
TBDATA,1,9e03,EP
mp,mu,2,0.1
!Meshing
et,1,182
keyopt,1,3,1
keyopt,1,6,1
esize,3
lsel,s,,,4,7
lsel,a,,,9,16
lsel,a,,,20,34
lesize,all,0.8
allsel,all
amesh,all
!************************************************
!Create contact pairs
!************************************************
et,2,169
et,3,172
keyopt,3,10,2
lsel,s,,,5,17
nsll,,1
esln
mat,2
type,3
real,3
esurf
lsel,s,,,20,32
nsll,,1
esln
mat,2
type,2
real,3
esurf
allsel,all
RMODIF,3,10,0.0245
!Create redundant contact pair for applying bending load in 3D model

et,4,169
et,5,172
keyopt,5,2,0
keyopt,5,10,2
lsel,s,,,37
nsll,,1
esln
type,5
real,5
mat,5
esurf
lsel,s,,,41
type,4
real,5
lmesh,41
allsel,all
!Create a pilot node for contact pair ID 5
REAL,5
TYPE,4
TSHAP,PILO
N,999, 0,100,0.0
E,999
allsel,all
!************************************************
!Create components for applying BCs and Loading
!************************************************
lsel,s,,,1
nsll,,1
cm,nd_fixed,node
d,all,all
allsel,all
lsel,s,,,38,39
lsel,a,,,2
nsll,,1
cm,nd_pres,node
allsel,all
lsel,s,,,37
nsll,,1
cm,nd_force,node
allsel,all
/PBC,ALL, ,1
/show,png
eplot
/show,close
FINISH
!************************************************
! 2D analysis
!************************************************
/solu
time,1
outres,all,all
eresx,no
rescontrol,define,all,1
nsub,50,10000,10
nlgeom,on
cmsel,s,nd_pres
sf,all,pres,4000
cmsel,s,nd_force
f,all,fy,6000
allsel,all
solve
finish
/post1
/out,
set,last
fsum
rsys,solu
/show,png
/graphics,full
plnsol,epto,eqv
*get,max_eptoeqv,plnsol,0,max
*get,min_eptoeqv,plnsol,0,min
plnsol,epto,x
2D to 3D Analysis
*get,max_eptox,plnsol,0,max
*get,min_eptox,plnsol,0,min
plnsol,s,eqv
*get,max_seqv,plnsol,0,max
*get,min_seqv,plnsol,0,min
plnsol,s,x
*get,max_sx,plnsol,0,max
*get,min_sx,plnsol,0,min
plnsol,cont,pres
*get,max_pres,plnsol,0,max
*get,min_pres,plnsol,0,min
plnsol,cont,pene
*get,max_pene,plnsol,0,max
*get,min_pene,plnsol,0,min
plnsol,cont,slid
*get,max_slid,plnsol,0,max
*get,min_slid,plnsol,0,min
/show,close
*status
finish
!************************************************
! Map2dto3d Analysis
!************************************************
/clear,nostart
/solu
MAP2DTO3D,START,1,38
allsel,all
shpp,off
EEXT,Axis,36
allsel,all
eresx,no
MAP2DTO3D,FINISH
MAP2DTO3D,SOLV
finish
/post1
/out,
!Settings for reverse video plot
/rgb,index,100,100,100, 0
/rgb,index, 80, 80, 80,13
/rgb,index, 60, 60, 60,14
/rgb,index, 0, 0, 0,15
jpgprf,,,1
/VIEW, 1, 0.646367088986E-01, 0.223695995480 , 0.972513340510
/ANG, 1, -0.946434514981
set,last
fsum
rsys,solu
/show,png
/graphics,full
plnsol,epto,eqv
plnsol,epto,x
plnsol,s,eqv
plnsol,s,x
plnsol,cont,pres
2D to 3D Analysis Restrictions
plnsol,cont,pene
plnsol,cont,slid
/show,close
/out,
*status
finish
!************************************************
! 3D analysis with Bending load in Restart Run
!************************************************
/clear,nostart
/solu
antype,,restart,1,39
cnkmod,9,12,5
allsel,all
d,999,rotz,-0.00349
nsub,10,10000,5
allsel,all
solve
finish
/post1
/out,
/VIEW, 1, 0.646367088986E-01, 0.223695995480 , 0.972513340510
/ANG, 1, -0.946434514981
set,last
fsum
rsys,0
/show,png
/graphics,full
plnsol,epto,eqv
plnsol,epto,x
plnsol,s,eqv
plnsol,s,x
plnsol,cont,pres
plnsol,cont,pene
plnsol,cont,slid
/show,close
/out,
*status
finish
1.6. 2D to 3D Analysis Restrictions

The following limitations apply to a 2D to 3D analysis:
2D to 3D Analysis
• You cannot use remeshing commands within the 2D to 3D analysis environment (that is, 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.
• 2D 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.
• Surface elements are not supported.
• ESOL for the POST26 postprocessor is not supported and the command is ignored.
Chapter 2: Semi-Implicit Method
The semi-Implicit method is a solution scheme in which the analysis starts out using an implicit solution
approach but transitions to a semi-implicit solution approach when the implicit solution fails to converge.
This is a hybrid method with some features from both the traditional implicit finite element method
and the traditional explicit finite element method.
• Similar to the explicit method, the semi-implicit approach relies on central difference time integration.
This guarantees a solution for every substep of the semi-implicit solution phase. (A guaranteed solution
is not possible with the implicit method since it requires Newton-Raphson iterations.)
• Similar to the implicit finite element method:
– The semi-implicit method has fully coupled nodal acceleration and, hence, involves solving a set
of coupled equations at every substep (unlike the explicit method).
– Lagrange multiplier-based constraints and mixed element formulations (mixed u-P based solid
elements) are supported.
– The semi-implicit method uses a bisection scheme.
The semi-implicit method is recommended for problems that, due to extreme nonlinearities, experience
a brief period during which they cannot converge in the implicit solution. For example, snap-through
problems, models with local buckling, analyses in which temporary rigid body modes are activated, and
models with sudden changes in material constitutive behavior can all benefit from the semi-implicit
method. For the brief period of extreme nonlinear behavior, the solution uses the semi-implicit solution
scheme. The analysis may or may not transition back to the implicit method, depending on a user-
specified criterion for time spent in the semi-implicit phase.
The following semi-implicit topics are available:

2.1. Semi-Implicit Basic Procedure
2.2. Semi-Implicit Solution Controls
2.3. Semi-Implicit Method Recommendations
2.4. Semi-Implicit Method Limitations
2.1. Semi-Implicit Basic Procedure

Use the SEMIIMPLICIT command to activate the semi-implicit method:
SEMIIMPLICIT, Option, Type, Value
Use the Option field to specify various controls for the semi-implicit solution (see the SEMIIMPLICIT
command for a list of valid Option values). Issue the command multiple times to specify the various
controls, or issue the command once with no arguments to activate the semi-implicit method using
Semi-Implicit Method
default settings (see the command description for default values). The command is valid only in the
solution processor (/SOLU) and must be issued before the first SOLVE command.
The following two Option values are most often used:
ETOI - Criterion for transitioning from the semi-implicit solution phase back to the implicit solution
phase.
MSCA - Selective mass scaling factor for the semi-implicit solution phase.
To illustrate use of this command and the basic semi-implicit procedure, the solution procedure is ex-
plained with respect to a representative example. The figure below shows a rigid ball impacting a net
modeled by beam elements.
Semi-Implicit Basic Procedure
Figure 2.1: Semi-Implicit Example Model
A purely implicit solution could have difficulty converging for this model due the highly nonlinear nature
of the analysis. It is therefore a good candidate for the semi-implicit method. Only two SEMIIMPLICIT
commands are needed beyond the typical input:
semiimplicit,msca,dtim,1/5000 ! Use a selective mass scaling factor such that the semi-implicit
! solution phase uses time increments of the order 1/5000
semiimplicit,etoi,time,0.1 ! Time to spend in the semi-implicit phase is 0.1
The different phases of the semi-implicit method are described below.
Initial Implicit Solution Phase

The solution starts off as an implicit static analysis. The SEMIIMPLICIT command enables the solver to
switch to the semi-implicit solution method when the implicit method fails to converge. The transition
is noted in the output as follows:
>>> TRANSITIONING TO SEMI-IMPLICIT METHOD
Semi-Implicit Solution Phase

During the semi-implicit solution phase, Newton-Raphson iterations are not required and each substep
has only one iteration. The resulting solution is checked for several possible errors, including but not
limited to sudden jumps in the displacement increment, an invalid mesh, an invalid contact solution,
and an invalid material state. The substep is bisected by reducing the time increment of the invalid
substep. During the semi-implicit solution phase, 10 bisections are allowed and the minimum time in-
crement is set to (total step time)/1x1015. Some of the element level error checks that trigger bisection
in an implicit solution phase are completely ignored.
Since the semi-implicit method has only one iteration per substep, the solution for a substep may not
be stable (that is, it may violate some of the element level error checks). However, this is only apparent
when element calculations are done in the next substep. When there is an element error and bisection
is performed, the program recalculates the previous completed substep with a smaller time increment
by resuming the previous substep, which is saved in the file Jobname.PSAV. The previous subtep
results, if written in the Jobname.RST file, are deleted as well, and new results are written if the substep
completes successfully. Similarly, the restart file for a substep is written after the end of the next substep
to make sure that the solution of the substep does not produce element errors in the next substep.
During the semi-implicit solution, the kinetic energy and potential energy are printed out instead of
solution residual norms that are printed during the implicit phase. For example, in the solution output
you will see something like this:
Kinetic Energy = 745.8 Potential Energy = 0.8909E+06
When solving a quasi-static problem, the ratio of the kinetic to potential energy is a good indicator of
how close the semi-implicit dynamic solution is to a quasi-static analysis. As a rule of thumb, kinetic
energy should be < 1% of potential energy. Reducing the mass scaling and/or reducing the factor of
safety can help to keep the kinetic energy low.
The monitor file (file.mntr) automatically lists the total kinetic and potential energies under variables
2 and 3 whenever a semi-implicit solution is activated. If you explicitly input the MONITOR command
to monitor variables, the command you input takes precedence and the energies are not printed.
2.2. Semi-Implicit Solution Controls

Following is a detailed discussion of all the control parameters available on the SEMIIMPLICIT,Op-
tion,Type, Value command.
Semi-Implicit Solution Controls
Selective Mass Scaling (Option = MSCA)

During the semi-implicit phase, the automatic time incrementation follows internal logic such that the
time increment is smaller than the stable time increment required for the semi-implicit solution. Com-
mands such as DELTIM and NSUBST that control the time increments in an implicit solution are ignored.
The stable time increments for a typical quasi-static solution are very small, and it would take an inor-
dinate amount of time to solve in the semi-implicit analysis. Therefore, the mass should be scaled to
increase the stable time increment (see Stability and Selective Mass Scaling in the Theory Reference).
The stable time increment increases proportional to the square root of the element mass.
Selective mass scaling is controlled by Option = MSCA on the SEMIIMPLICIT command. There are
two ways you can define the mass scaling:
Type = DTIM: specify an initial time increment. For this method, the program automatically scales
the mass of each element such that the initial stable time increment of the element is more than
the user-specified time increment. Internal logic determines the time increment to use; therefore,
the time increments used can be different than the one you specify. Once, the mass is scaled, the
program keeps the scaled mass constant throughout the semi-implicit phase of the solution.
Type = MASS: specify a value to directly scale the mass of each element.
The first substep of the semi-implicit solution phase uses a time increment which is 1/10 of the program-
calculated stable time increment.
If you do not want to include mass scaling, use Type = MASS and input a very small number in the
Value field (for example, SEMIIMPLICIT,MSCA,MASS,1e-20). Do not use 0 as that will make the program
scale the mass to the default value.
Factor of Safety for Time Incrementation (Option = SFAC)

The actual time increment to be used is determined by multiplying the stable time increment calculated
by a factor of safety. The default factor of safety is 0.9. For some cases where the semi-implicit solution
becomes unstable, it can be useful to reduce the factor of safety. For example, if you issue the following
command:
SEMIIMPLICIT,SFAC, ,0.1
the default factor of safety (0.9) is overwritten by 0.1.
Bisections Based on Maximum Displacement Increment (Option = AUTS,

Type = DSPL)
During the semi-implicit solution phase, if the maximum displacement increment changes more than
100 times that of the previous time increment, then the code automatically bisects and repeats the
substep again. This is done to achieve a more stable and smoother solution during the semi-implicit
phase. Any node with applied velocity or displacement boundary conditions is not included in this
check.
Use a value smaller than the default of 100 if the semi-implicit solution shows signs of instability; for
example, if parts held together by contact are flying away. You can control the allowable jump at which
to trigger bisection by using the command:
SEMIIMPLICIT,AUTS,DSPL,10
Bisections in the semi-implicit solution phase work slightly different than in the implicit algorithm. The
internal force does not change upon bisection as internal force is based on the displacement of the
previous substep. Therefore, bisection can sometimes fail in reducing the displacement increment in-
crease.
You can turn off bisection logic based on the displacement jump by inputting a value less than 1 in
the above SEMIIMPLICIT command.
Bisections Based on Kinetic Energy to Potential Energy Ratio (Option = AUTS,

Type = ENER)
In a static analysis, the default behavior for bisection in the semi-implicit solution phase differs from
other analysis types. During the semi-implicit solution phase, if the kinetic energy is more than 100
times the potential energy and the potential energy is more than the program-calculated minimum
reference, the semi-implicit solution bisects and tries to repeat the previous substep with a smaller time
increment in an attempt to reduce the kinetic energy. The program-calculated minimum reference is a
function of material properties and the model size.
If you want to trigger bisection at a different ratio than the default 100, or you want to trigger bisection
for a transient analysis, use the following command:
SEMIIMPLICIT,AUTS,ENER,10
This triggers bisection whenever the kinetic energy is more than the user-specified ratio times the po-
tential energy and the potential energy is more than the program-calculated reference value. In this
case, the reference value is much smaller than the reference value used when this command is not
specified so that bisections occur more often, even at low potential energy.
Bulk Viscosity (Option = BVIS)

During the semi-implicit solution, bulk viscosity is added to all elements except elements using incom-
pressible materials. The force due to bulk viscosity can be controlled using Option = BVIS on the
SEMIIMPLICIT command. Decreasing bulk viscosity improves accuracy, but the problem can become
more unstable and harder to solve, and the response will show more oscillations. Increasing bulk viscosity
generally improves solution stability.
Output Frequency (Option = EFRQ)

Since the number of substeps in the semi-implicit solution is significantly more than the implicit solution,
the results files (file.rst) and the restart files (file.rnn) are written less frequently than in the
implicit phase. The frequencies specified by the OUTRES command (for the results file) and the
RESCONTROL command (for the restart files) are not honored during the semi-implicit solution phase
unless a negative frequency value was input.
Semi-Implicit Solution Controls
By default, output to the results file and the restart files are written after every 100 substeps in the
semi-implicit phase. You can overwrite this default frequency by using Option = EFRQ on the
SEMIIMPLICIT command. For example, specifying:
SEMIIMPLICIT,EFRQ,OUTR,1
SEMIIMPLICIT,EFRQ,RESC,10
causes results to be written to file.rst at every substep of the semi-implicit solution phase, and
restart files to be written at every 10th substep of the load step.
The SEMIIMPLICIT,EFRQ command must be issued after OUTRES or RESCONTROL.
Transitioning Back to Implicit After the Semi-Implicit Solution (Option =

ETOI)
If you want the solution to attempt to come back to an implicit solution, specify this command:
SEMIIMPLICIT,ETOI,TIME,0.05
This command tells the solver to spend 0.05 time units in the semi-implicit solution phase and then
attempt to come back to the implicit solution; the following message is displayed:
>>> TRANSITIONING TO IMPLICIT METHOD
The first substep in the implicit solution phase after the transition uses the minimum time increment
given by the NSUBST and DELTIM commands.
When the transition happens from a semi-implicit to an implicit static solve, the residual for equilibrium
includes the inertia force generated in the semi-implicit phase. This inertial force needs to be balanced.
At first, the external load and the residual from the semi-implicit phase are applied together, and the
implicit solver tries to achieve convergence. If the solver fails to converge, it bisects; from then on only
the residual from the semi-implicit phase is applied, and no additional external load is applied. You will
see the following message to indicate that the substep is applying only the semi-implicit residual:
*** BEGIN BISECTION NUMBER 1 NEW REBALANCE FACTOR INCREMENT= 1.0000
Further bisections will change the rebalance factor increment, indicating how much of the residual from
the semi-implicit phase is being applied.
After the residual from the semi-implicit solution is completely rebalanced, the analysis proceeds with
regular time incrementation and loading in the implicit run.
Sometimes, the implicit solver cannot rebalance the residual from the semi-implicit phase and converge
fails. In such cases, the program then switches back to the semi-implicit solver and the counter is reset
back to 0. The next attempt to come back to the implicit solver is made after the time interval specified
on the SEMIIMPLICIT,ETOI,TIME command.
The example shown in Figure 2.1: Semi-Implicit Example Model (p. 27) transitions to the semi-implicit
solution phase multiple times during the analysis.
When transitioning from the semi-implicit solution phase to the implicit solution phase, the program
automatically turns on nonlinear stabilization (STABILIZE command). The stabilization force is applied
as if the command STABILIZE,REDUCE,ENERGY has been issued. An energy-dissipation ratio between
0.01 and 0.05 is used, and it is reduced linearly to zero to the end of the load step. You can control the
amount of stabilization by manually specifying the STABILIZE command, in which case it takes preced-
ence over the program internal logic. However, during the transition phase where only the residual
from the semi-implicit solution is applied and no additional external load is applied, stabilization is
turned off.
2.3. Semi-Implicit Method Recommendations

Keep in mind the following recommendations when using the semi-implicit method.
• Since the semi-implicit method uses semi-implicit transient dynamics for part of the solution, every
node in the model must have an associated mass. Therefore, each node must belong to at least one
element that has material density defined.
Important:
Because the SEMIIMPLICIT command can be issued in a restart after the base implicit
analysis has failed to converge, it is required that all nodes in the base implicit analysis
have an associated mass during the implicit solution. The restart framework does not
permit material density to be defined in the restart analysis.
• Since the stable time increment is dependent upon the element length, material density, and the
moduli, choosing the correct units and length scale for the problem is very important. For example,
in an implicit static solution scheme with linear elastic material behavior, to model a uniaxial tension
by modeling a block having a 1 cm length or a 100 cm length would take similar times and give
similar results. However, when the same problem is solved in a semi-implicit solution, the stable time
increment for the block of 1 cm length will be 100 times smaller (assuming identical meshes for the
1 cm and 100 cm cases).
• To achieve a faster solution, you can scale the mass. Two methods of scaling are available. Specify a
desired time increment, and the program automatically scales the mass to make the stable time in-
crement at the first substep of the semi-implicit solution to be more than the desired time increment.
Or scale the mass directly by giving a factor to achieve a faster solution. However, increasing mass
increases inertia, and with more inertia the solution will be farther away from the quasi-static solution.
Monitor the kinetic and potential energies that are printed from the solution to make sure the solution
is close to quasi-static. The energies are also printed in the monitor file (file.mntr). A good rule
of thumb is Kinetic energy < 1% of the potential energy for quasi-static problems.
• If the solution fails during the semi-implicit solution, consider using a smaller factor of safety (for
example, using the command SEMIIMPLICIT,SFAC,,0.1). Furthermore, a smaller mass scaling factor
will also help to achieve a solution in the semi-implicit phase. However, reducing either of them
would result in longer times to solve. It is also recommended that you use a smaller allowable increase
in maximum displacement increment (for example. SEMIIMPLICIT,AUTS,DSPL,10) so that the semi-
implicit solution bisects and provides a smoother solution.
• For problems that include contact elements and fail during the semi-implicit solution, lowering the
contact stiffness by a factor of 10 (real constant FKN = 0.1 for the contact elements) can be helpful.
Lowering the pinball value may also help if the semi-implicit solution fails due to spurious contact
detection.
Semi-Implicit Method Limitations
• For problems that include contact elements, a high mass scaling can result in large time increments
and large penetration in the substep. The contact force to resist this penetration can sometimes be
very high, causing instabilities. For a penalty enforcement of the contact constraint, this can cause
the parts to separate and fly away; and for a Lagrange enforcement of the contact constraint, this
may result in chattering and a non-smooth contact pressure distribution. Reducing the safety factor
and/or mass scaling will improve this.
• It is recommended that you specify a small value for the time to be spent in the semi-implicit phase.
The intent of the semi-implicit method is to help bypass small periods of extreme nonlinearities where
convergence in a pure implicit solution is difficult. However, if the problem has extreme nonlinearities
throughout the load history, then it is better to just continue in the semi-implicit solution as each
attempt to transition back to implicit is computationally expensive.
• It is expected that the results obtained using the semi-implicit method can be different than the
results obtained if the problem were to be solved entirely in the implicit solver. The magnitude of
the difference depends upon many factors such as, but not limited to, the mass scaling used and
thus the inertial loads in the body and the time spent in the semi-implicit solution phase.
• You should not save results at every substep of the analysis when using the semi-implicit method.
During the semi-implicit solution phase, there can be thousands of substeps. Therefore, saving results
at each substep can make the result files extremely large.
• If the implicit solution phase is a static analysis, the semi-implicit solution phase uses lumped mass
by default. Therefore, if the static analysis has any load (gravity for example) that uses density, and
therefore the mass, it is recommended that you explicitly define the mass lumping option you desire.
• When transitioning to the semi-implicit solution phase from implicit, if the solution shows large oscil-
lations, it is recommended that you define a mass proportional damping in the semi-implicit phase
that will help in damping out the oscillations.
• If gasket elements (INTER192 through INTER195) are included in the model, you must use the MP
command to define density for these elements. The density will be used to calculate the mass matrix
for the gasket elements during the semi-implicit solution phase. The mass matrix is not used for these
elements in the implicit solution phase.
2.4. Semi-Implicit Method Limitations

Keep in mind the following limitations when using the semi-implicit method.
• This method is only available for static (ANTYPE,STATIC) and full transient (ANTYPE,TRANS) analysis
types.
• This method is available only for structural degrees of freedom. It does not support any element with
non-structural degrees of freedom.
• This method does not support the element formulations listed below.
– Solid elements:
→ PLANE182 and PLANE183 with the generalized plane strain option (KEYOPT(3) = 5) or
the axisymmetric with torsion option (KEYOPT(3) = 6).
→ SOLID185 with the enhanced strain formulation (KEYOPT(2) = 2 or 3).
→ Solid shell element SOLSH190.
→ Generalized axisymmetric SOLID272 and SOLID273 elements.
→ SOLID285 4-node tetrahedral element.
– Shell elements:
→ SHELL181 with incompatible modes (KEYOPT(3) = 2).
– Beam elements:
→ BEAM188 and BEAM189 with the warping degree of freedom (KEYOPT(1) = 1).
– Pipe elements PIPE288 and PIPE289.
– Elbow element ELBOW290.
– Contact elements:
→ CONTA171 through CONTA177 with impact constraints (KEYOPT(7) = 4).
→ CONTA178 node-to-node element.
– MPC184 joint elements with friction, stops, and/or locks.
• The semi-implicit method does not support nonlinear mesh adaptivity (NLADAPTIVE) and manual
rezoning if the mesh changes occur during the semi-implicit solution phase. These capabilities are
supported if the mesh changes occur during the implicit solution phase.
• During the semi-implicit solution phase, you cannot access the element matrix files Jobname.EMAT
and Jobname.FULL, as the definitions of the matrices and what is stored in these files are different
during the semi-implicit solution phase compared to the implicit solution phase.
• Every node in the model must have a mass associated with it. Therefore, each node must belong to
at least one element that has material density defined. For example, you cannot have only joint ele-
ments (MPC184) in the model. Each joint element must be connected to a structural element.
• The semi-Implicit method ignores the constant term of constraint equations (both externally and in-
ternally generated) while enforcing constraints during the semi-implicit solution phase. This can lead
to some incompatibility in the enforcement of the constraint equations. For internally generated
constraint equations arising from contact element (CONTA172 through CONTA177) with KEYOPT(2)
= 2, it is recommended you set KEYOPT(9) = 1 so that there won't be any constant term in the con-
straint equation.
• The semi-implicit method requires that the material density remains constant throughout the solution.
Defining density as a function of solution variables via TB or MP commands is not supported.
• The semi-implicit method does not support restart from the first substep of the semi-implicit solution
phase. You can restart from any substep of the implicit phase or from the second substep and beyond
of the semi-implicit phase.
Semi-Implicit Method Limitations
• The semi-Implicit method does not support element birth and death during the semi-implicit solution
phase.
• The semi-Implicit method does not support the XFEM and SMART methods for crack growth simula-
tions.
• During the semi-implicit solution phase, no stabilization damping is applied. More specifically, stabil-
ization force from the following sources are not added: nonlinear stabilization (STABILIZE command),
contact stabilization damping (KEYOPT(15) on contact elements CONTA172, CONTA174, CONTA175,
and CONTA177), and viscous regularization (TB,CZM,,,,VREG).
Chapter 3: Automatic Transition Between Static and
Transient Solutions
The solution transition procedure is useful in overcoming convergence problems in some difficult implicit
static analyses. By this procedure, the analysis starts out as a static solution and automatically transitions
to a transient dynamic solution based on a user-defined criterion. This procedure is applicable to all
physics types.
An implicit static solution often has difficulty converging in the following circumstances:
• Loss of contact (stiffness matrix can become singular due to rigid body motion)
• Contact chattering
• When the physics dictates that constraints cannot be applied on some parts
• Local buckling
A transient dynamic simulation, especially a quasi-static simulation (TINTP,QUASI), works well in these
scenarios as the mass matrix keeps the global matrix invertible. Furthermore, the algorithmic damping
helps to stabilize the problem and suppresses the unwanted high-frequency response, therefore keeping
the solution close to the static solution.
Once the solution overcomes the convergence difficulty, the analysis may attempt to come back to a
static solution based on a user-specified criterion for time spent in the transient phase.
The following solution transition topics are available:

3.1. Solution Transition Procedure
3.2. Solution Transition Method Recommendations
3.3. Solution Transition Method Limitations
3.1. Solution Transition Procedure

Use the SOLOPTION command to activate the automatic transition from a static to a transient solution:
SOLOPTION, Option, Type, Value
The following Option values are available:
STOT - Use a criterion for transitioning from the static solution to the transient dynamic solution.
TTOS - Use a criterion for transitioning from the transient dynamic solution back to the static solution.
Issue the command two times to specify both controls, or issue the command once with no arguments
to activate the automatic solution transition using default settings (see SOLOPTION for default values).
Automatic Transition Between Static and Transient Solutions
The command is valid only in the solution processor (/SOLU) and must be issued before the first SOLVE
command.
To illustrate the basic solution transition procedure, the steps are explained with respect to the repres-
entative example shown below. The analysis involves snap-through of a slender beam under pressure.
Figure 3.1: Solution Transition Example Model - Collapse of a Slender Beam
A static solution will have difficulty converging for this model at the point of snap-through.
You might attempt to use nonlinear stabilization (STABILIZE command) to achieve convergence in the
static simulation, but the stabilization procedure requires you to experiment with the stabilization factor.
A simpler way to achieve convergence is to implement the automatic solution transition. Only two
SOLOPTION commands are needed beyond the typical input:
Example 3.1: SOLOPTION Commands Used for the Slender Beam Snap-Through
soloption ! Transition to a quasi solution when the static solution fails to converge (default s
soloption,ttos,time,0.1 ! Attempt a transition back to static solution after solving the transient for 0.1 sec
If SOLOPTION is issued with no arguments specified, as in the above example, the static solution
transitions to a quasi-static transient solution if the static solution fails to converge. This equates to the
default command settings: SOLOPTION,STOT,CONV,QUASI.
The different phases of the solution transition initiated by the above commands are described below.
Solution Transition Procedure
Initial Static Solution Phase

The solution starts off as a static analysis. The SOLOPTION command enables the solver to switch to a
transient solution when the static method fails to converge. In this example, the quasi-static transient
option (which uses backward Euler time integration, TINTP,QUAS) is specified. The transition is noted
in the output:
>>> TRANSITIONING TO QUASI-STATIC SIMULATION
Transient Solution Phase

During the transient solution phase, the solution follows the time integration scheme specified with
SOLOPTION (quasi-static in this case). Most of the commands valid for transient simulation (for example,
TRNOPT and TINTP) can be issued to control the time integration settings. During the transient phase
of the solution, the kinetic energy and potential energy are printed out along with the residual norms.
For example:
Kinetic Energy = 0.2271 Potential Energy = 0.8017E+08
When solving a quasi-static problem, the ratio of the kinetic to potential energy is a good indicator of
how close the transient solution is to the static solution. As a rule of thumb, kinetic energy should be
< 1% of potential energy. Reducing the density of the materials can help lower the kinetic energy.
The monitor file (Jobname.mntr) automatically lists the total kinetic and potential energies under
variables 2 and 3 whenever the solution transition scheme is activated. If you explicitly input the
MONITOR command to monitor variables, that command takes precedence and the energies are not
printed.
Transitioning Back to the Static Solution

Specify a second SOLOPTION command if you want the solution to attempt to come back to a static
solution after the transient phase. In this example, the second command is:
soloption,ttos,time,0.1
This tells the solver to spend 0.1 time units in the transient solution phase and then attempt to come
back to the static solution. The following message is displayed:
>>> TRANSITIONING TO STATIC SIMULATION
When the transition back to a static solution occurs, the residual for equilibrium includes the inertial
force generated in the transient phase. This inertial force must be balanced. At first, the external load
and the residual from the transient phase are applied together, and the solver tries to achieve conver-
gence. If the solver fails to converge, it bisects until the minimum time increment is reached. After that,
only the residual from the transient phase (inertial force) is applied, and no additional external load is
applied. The program issues this message to indicate only the transient residual is applied in the substep:
*** BEGIN BISECTION NUMBER 6 NEW REBALANCE FACTOR INCREMENT= 1.0000
Further bisections will change the rebalance factor increment and indicate how much of the residual
from the transient phase is applied.
Automatic Transition Between Static and Transient Solutions
After the residual from the transient solution is completely rebalanced, the analysis proceeds with reg-
ular time incrementation and loading in the static run.
Sometimes the static solver cannot rebalance the residual from the transient phase, and convergence
fails. In this case, the program then switches back to the transient solver and the counter is reset back
to 0. The next attempt to come back to the static solver is made after the time interval specified on the
SOLOPTION,TTOS,TIME command.
For the example shown in Figure 3.1: Solution Transition Example Model - Collapse of a Slender
Beam (p. 38), the problem fails to converge right at the point of collapse and then successfully transitions
back to a static solution at the end of the collapse event.
3.2. Solution Transition Method Recommendations

Use the solution transition method to achieve convergence in the following situations:
• Rigid body motion causing lack of convergence in a static solution. This can be due to a lack of
constraints or due to a loss of contact during an iteration. Both the mass matrix and algorithmic
damping of the quasi-static solution help achieve convergence for this case.
• Convergence difficulty due to contact chattering. The algorithmic damping of the transient
solution helps to achieve convergence.
• Collapse or buckling analysis. The algorithmic damping helps to achieve convergence.
Follow these recommendations when using the solution transition method:
• Since the procedure relies on the mass matrix and algorithmic damping to achieve convergence
when the static solution fails to converge, it is important to define density for all materials when using
this method.
Important:
Because SOLOPTION can be issued in a restart after the base static analysis has failed to
converge, you must define the densities during the static solution. The restart framework
does not permit material density to be defined in the restart analysis.
• During the transient solution phase, the default backward Euler time integration (SOLOPTION,STOT,
,QUASI) is recommended since the algorithmic damping in this method helps to keep the transient
solution close to the static solution.
• Monitor the kinetic energy to potential energy ratio during the transient solution to make sure it is
close to a static solution. You can reduce the densities and/or add damping (ALPHAD command) to
lower the kinetic energy. When adding damping, also monitor the damping energy. The kinetic and
damping energies are representative of the solution approximations made to achieve convergence
and should be a very small percentage (<1%) of the potential energy to achieve an accurate solution.
• If the static solution fails to converge due to rigid body motion or due to loss of contact, it might be
more efficient to use Type = RBM or CONT on the SOLOPTION command in order to trigger the
transition to a transient solution at the first occurrence of rigid body motion (RBM) or loss of contact
Solution Transition Method Limitations
of an entire pair (CONT). This will save on the number of iterations performed in the static solution
since it will transition before the point of convergence failure.
• For most problems, it can be advantageous to use the SOLOPTION command during the restart. Run
the static simulation as usual, but add material densities. Then issue SOLOPTION,STOT,FORC in the
restart to force a transition to the quasi-static solution. This approach can help to achieve convergence.
3.3. Solution Transition Method Limitations

Following are limitations for using the solution transition method:
• This method is only available for the static analysis type (ANTYPE,STATIC).
• The process of transitioning from the transient solution back to the static solution requires automatic
time stepping (AUTOTS,ON, which is the default). Automatic time stepping helps to achieve conver-
gence while balancing the residual from the transient analysis in the static analysis. If you turn auto-
matic time stepping off (AUTOTS,OFF), only the static-to-transient transition is supported.
• If the solution tries to transition from the transient solution back to the static solution and fails to
converge, then the solution continues in the transient analysis. However, the results will be slightly
different than if the solution continues in the transient solution without attempting to transition back
to the static solution. This is because the static-to-transient solution transition starts with zero velocity.
• During the solution transition phase from transient-to-static analysis, NLADAPTIVE based mesh
changes are not supported.
• The damping energy is zeroed out every time a transition is made from the transient phase back to
the static phase. Thus, if the analysis does multiple transient-to-static transitions, you must add up
the damping energy of each of the transient phases to get the total damping energy.
Chapter 4: 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.
Initial state is supported for the following analysis types (ANTYPE,Antype): Static (Antype = STATIC),
Transient (Antype = TRANS), Modal (Antype = MODAL), Harmonic (Antype = HARMIC), Buckling
(Antype = BUCKLE), and Soil (Antype = SOIL).
Initial-state data includes:
• Initial stress (p. 45)

• Initial strain (p. 46)
• Initial plastic strain (p. 47)
• Initial creep strain (p. 47)
• Initial void ratio and pore pressure (p. 48)
Initial-state support is also available for distributed-memory parallel processing analyses.
The following initial-state topics are available:

4.1. Specifying and Editing Initial-State Values
4.2. Initial-State Application
4.3. Initial-State (.IST) File
4.4. Using Coordinate Systems with Initial State
4.5. Initial-State Limitations
4.6. Example Problems Using Initial State
4.7. Writing Initial-State Values
Also see Applying an Initial State to Reinforcing Elements in the Structural Analysis Guide.
4.1. Specifying and Editing Initial-State Values

The initial-state capability is based on the INISTATE command. The command enables you to specify
and edit your initial-state data. You can also use it to read initial-state values from an external file (p. 50)
(INISTATE,READ) or to export existing values (p. 70) (INISTATE,WRITE) to such a file.
The following topics about initial-state data types are available:

4.1.1. Element-Based Initial State
Initial State
4.1.2. Node-Based Initial State
4.1.1. Element-Based Initial State

Element-based initial-state application is available 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
integration points.
• Beam elements
You can apply initial state to combinations of cell number, section integration and element integ-
ration points.
• All other elements
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).
4.1.2. Node-Based Initial State

Initial-state application can also be node-based, a capability available in current-technology elements.
• 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 integ-
ration 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
properties. For more information, see Understanding Field Variables in the Material Reference.
For more information, see Applying Node-Based Initial Strain (p. 48) and Example: Node-Based Initial
Strain (p. 64).
4.2. Initial-State Application

This section provides typical cases for applying an initial state, as follows:
Initial-State Application
4.2.1. Applying Initial Stress

4.2.2. Converting Initial Stress to Initial Strain
4.2.3. Applying Initial Strain
4.2.4. Applying Initial Plastic Strain
4.2.5. Applying Initial Creep Strain
4.2.6. Applying Initial State with State Variables
4.2.7. Applying Node-Based Initial Strain
4.2.8. Applying Initial Pore Pressure and Void Ratio
4.2.9. Applying Initial Degree of Saturation and Relative Permeability
4.2.10. Function-Based Initial State
4.2.1. Applying Initial Stress

Although initial stress is element-based, the structure of the INISTATE command is element-type-in-
dependent.
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.
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
Initial State
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. 53) and Example: Initial Stress (INISTATE Command) (p. 57).
4.2.2. Converting Initial Stress to Initial Strain

After you apply initial stress, Mechanical APDL can convert it to initial strain and apply it
(INISTATE,SET,STOE,1).
The initial-stress-to-strain option is available with elastic materials with these solid elements: SOLID182,
SOLID183, SOLID185, SOLID186, SOLID187, SOLSH190, SOLID272, and SOLID273.
Example 4.1: Initial Stress-to-Strain Conversion

! Constant initial stress on the whole model
inistate,set,dtyp,s
inistate,defi,,,,,100,0,0,0,0
! Convert initial stress to initial strain

inis,set,stoe,1
Also see Example: Convert Initial Stress to Initial Strain (INISTATE Command) (p. 54).
4.2.3. Applying Initial Strain

The initial stress application (p. 45) example can be extended for initial strain by simply changing
the data type to EPEL, as shown.
Initial elastic strain cannot be combined with initial stress. Either, but not both, can be specified in
the input.
! 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

!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. 57).
4.2.4. Applying Initial Plastic Strain

The initial stress application (p. 45) 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. 58).
4.2.5. Applying Initial Creep Strain

The initial stress application (p. 45) 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. 59).
Initial State
4.2.6. Applying Initial State with State Variables

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. 61).
4.2.7. Applying Node-Based Initial Strain

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. 64).
4.2.8. Applying Initial Pore Pressure and Void Ratio

Initial pore pressure and void ratio are available for coupled pore-pressure-thermal elements (CPTnnn).
Apply initial pore pressurel and void ratio on CPTnnn elements by changing the data type to PPRE
and VOID, respectively.
! Apply to all the selected elements
porepr=69
inistate,set,dtyp,ppre
inistate,defi,,,,,porepr

vratio=0.4
inistate,set,dtyp,void
inistate,defi,,,,,vratio
Also see Example: Initial Pore Pressure and Void Ratio (p. 65).
4.2.9. Applying Initial Degree of Saturation and Relative Permeability

Initial degree of saturation and relative permeability are available for coupled pore-pressure-thermal
elements (CPTnnn). Apply initial degree of saturation and relative permeability on CPTnnn elements
by changing the data type to DSAT and RPER, respectively.
Example 4.2: Applying Initial Degree of Saturation and Relative Permeability

init_sw=0.9
inistate,set,dtyp,dsat
inistate,defi,all,,,,init_sw
init_kr=0.87
inistate,set,dtyp,rper
inistate,defi,all,,,,init_kr
Also see Example: Initial Degree of Saturation and Relative Permeability (p. 67).
4.2.10. 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 (LINY),
or a linear function in Z coordinates. The method is available for both node-based and element integ-
ration-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 com-
mand 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
coordinates needed to evaluate the initial-state data are transformed to the user-defined coordinate
system before the evaluation process.
Example 4.3: Function-Based Initial State in a User-Defined Coordinate 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
Initial State
Also see Example: Function-Based Initial State (p. 68).
4.3. Initial-State (.IST) File

Although issuing multiple INISTATE,DEFINE commands is a valid way to assign explicit initial-state
values to various items, creating an external initial-state (.ist) file and reading it in (INISTATE,READ)
is a faster and more efficient method (especially for large amounts of initial-state data).
The following .ist file-format topics are available:

4.3.1. Data-Input Types Supported in the .IST File
4.3.2. Specifying Parameter Data in the .IST File
4.3.1. Data-Input Types Supported in the .IST File

The .ist file supports element-integration-point-based (p. 44) data input or node-based (p. 44) data
input (but not both at once).
The file format is comma-delimited ASCII, consisting of individual rows (lines) for each stress item.
Each row consists of 10 columns separated by commas. Your columns delineate the integration
point(s) for specific elements or nodes.
Element-integration-point-based data:
• The element ID number
• 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 stress/strain/initial-state components
Node-based data (specify /NODE,1 before the data in the .ist file):
• Node number
• Element ID number
• The layer number (for layered elements) or the cell number (for beam elements)
• The section-integration point (for beam and shell elements only)
• The stress/strain/initial-state components
The number of section-integration points for beams and shells depends on the associated user input.
An element ID number can be repeated on successive rows to specify different stresses at different
integration points.
For information about the number and location of available element integration points, see Integration
Point Locations in the Theory Reference. For a listing of the integration points for each specific element,
see Element Library in the Theory Reference.
Using Coordinate Systems with Initial State
4.3.2. Specifying Parameter Data in the .IST File

Parameters for element ID, element-integration point, layer number, cell number, or section-integration
point can be set to ALL in the .ist file.
You can provide additional data via attribute parameters (/ATTR,VALUE line). Supported parameters
are /CSYS, /DTYP, and /NODE:
• The default coordinate system is the global Cartesian system. Specify /CSYS,VALUE to set the
coordinate system to be used for the subsequent data provided in your .ist file.
• Apply initial strain by specifying /DTYP,EPEL before the initial-state/initial-strain data.
• To activate node-based initial state, specify /node,1 at the top of the initial-state input (.ist)
file.
Example 4.4: Setting parameters
This input applies an equal stress of SX = 100 to all integration points or layers of the element ID =
1:
1,all,all,all, 100, 0, 0, 0, 0, 0
This input applies an equal stress of SX = 100 to all integration points or layers to all of the selected
elements:
all,all,all,all, 100, 0, 0, 0, 0, 0
This input applies an initial strain of ex = 0.1 for all elements in the database.
/dtyp,epel all,all,all,all, 0.1, 0, 0, 0, 0, 0
To insert comments and other non-analysis information in the .ist file, precede them them with
an exclamation mark (!).
4.4. Using Coordinate Systems with Initial State

Options are available 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 -1 (material) or -2 (element), or 11 (any user-defined 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.
You can also specify which coordinate system to write to (INISTATE,WRITE): element, material, or
global (default).
Initial State
The material coordinate system refers to the solution coordinate system in which all results are evaluated.
At the start of solution, the material coordinate system and the element coordinate system for nonlayered
elements are coincident; for layered elements, the material coordinate system and the layer coordinate
system are coincident. For large-deformation problems, the material coordinate system may evolve
during solution and differ from the element coordinate system.
4.5. Initial-State Limitations

The following initial-state element limitations apply:
• It is available only for current-technology elements. Initial state supported for a given element is in-
dicated in the documentation for the element under “Special Features.”
• Node-based initial state (p. 44) is not supported for the following 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 (p. 43) is not available for beam sections of subtype ASEC (BEAM188 and BEAM189 with
SECDATA,BEAM,ASEC).
• Initial-state datatypes "void volume ratio" (VRAT) and "pore pressure" (PPRE) are available only for
coupled pore-pressure-thermal elements (CPTnnn).
The following initial-state material limitations apply:
• It is not supported for use with kinematic hardening material properties (TB,PLAS,,,,BKIN,
TB,PLAS,,,,KINH).
• It is not supported for use with the shape memory alloy material model (TB,SMA).
• Initial state with initial stress is not supported for gasket materials (TB,GASKET).
• Initial state with stress is supported for hyperelastic materials (TB,HYPER, TB,BB, TB,AHYPER, TB,CDM,
TB,EXPE). Initial state with initial elastic strain is not supported for hyperelastic materials nor gasket
materials (TB,GASKET).
• Initial state with plastic strain (which must include initial strain or stress, plastic strain, and accumulated
plastic strain) does not support gasket materials (TB,GASKET), porous media (TB,PM), rate-dependent
plasticity (TB,RATE), and viscoelasticity (TB,PRONY, TB,SHIFT).
• Initial state with field variables is not supported for fracture calculations initiated via the CINT com-
mand.
• 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.
Example Problems Using Initial State
• 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. 49) 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.
4.6. Example Problems Using Initial State

This section provides examples of typical initial-state problems, as follows:
4.6.1. Example: Initial Stress (IST File)
4.6.2. Example: Convert Initial Stress to Initial Strain (INISTATE Command)
4.6.3. Example: Initial Stress (INISTATE Command)
4.6.4. Example: Initial Strain
4.6.5. Example: Initial Plastic Strain
4.6.6. Example: Initial Creep Strain
4.6.7. Example: Initial Plastic Strain with State Variables
4.6.8. Example: Node-Based Initial Strain
4.6.9. Example: Initial Pore Pressure and Void Ratio
4.6.10. Example: Initial Degree of Saturation and Relative Permeability
4.6.11. Example: Function-Based Initial State
4.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 Mechanical APDL. 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
Initial State
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 Mechanical APDL
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
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.
4.6.2. Example: Convert Initial Stress to Initial Strain (INISTATE Command)

Initial stress generated from a test run is applied as initial stress. In a subsequent run, the initial stress-
to-strain option is enabled (INISTATE,SET,STOE,1). The results are compared to a run with equivalent
initial strains.
/com,*****************************************************************************************************
/com,Expected Results:Results of stress conversion model should match with eqv initial strain model
/com,*****************************************************************************************************
/prep7
! Define the material
TB,elas,1
TBDATA,1,1e9,.3
et,1,185
keyopt,1,2,2
keyopt,1,3,0
keyopt,1,6,1
BLOCK,0,1,0,1,0,1
lesize,all,,,1
vmesh,all,all
nsel,s,loc,x,0
nsel,r,loc,y,0
nsel,r,loc,z,0
d,all,all
nsel,s,loc,y,0
d,all,uy
nsel,s,loc,z,0
d,all,uz
nsel,s,loc,x,0
d,all,ux
nsel,s,loc,x,1
SF,all,press,100
allsel,all
nsel,s,loc,y,1
SF,all,press,100
allsel,all
nsel,s,loc,z,1
SF,all,press,100
allsel,all
cdwrite,all
/solu
inis,write,1,,,,0,S
solve
/post1
set,last,last
/out
/COM,**********************************************************************************
/COM, Simple Triaxial Load of Ux=-0.1,Uy=0.2,Uz=-0.3 Disp
/COM,**********************************************************************************
presol,s
presol,epel
prdi
/COM,**********************************************************************************
fini
/clear,nostart
Initial State
/PREP7
cdread,db,
nsel,s,loc,x,1
SF,all,press,200
allsel,all
nsel,s,loc,y,1
SF,all,press,200
allsel,all
nsel,s,loc,z,1
SF,all,press,200
allsel,all
!ddel,all,all
!d,all,all
/solu
inis,read
inis,set,stoe,1
/out
inis,list,all
solve
/post1
set,last,last
rsys,0
/out
/COM,**********************************************************************************
/COM, Applied a Initial Stress converted to initial strain
/com, This results should match with eqv initial strain model
/COM,**********************************************************************************
presol,s
presol,epel
prdi
/COM,**********************************************************************************
fini
/com,************************************************************************
/clear,nostart
/com,************************************************************************
/com,************************************************************************
/prep7
cdread,db
nsel,s,loc,x,1
SF,all,press,200
allsel,all
nsel,s,loc,y,1
SF,all,press,200
allsel,all
nsel,s,loc,z,1
SF,all,press,200
allsel,all
!ddel,all,all
!d,all,all
/solu
allsel,all
inis,set,dtyp,epel
inis,set,csys,0
inis,defi,all,all,all,all,-0.4e-7,-0.4e-7,-0.4e-7
solve
/post1
set,last,last
/out
/COM,**********************************************************************************
/COM, Applied a Initial Strain -Eqv Model
/COM,**********************************************************************************
presol,s
presol,epel
prdi
/COM,**********************************************************************************
fini
4.6.3. 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
4.6.4. 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
Initial State
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
4.6.5. Example: Initial Plastic Strain

This initial plastic strain example is a simple 3D 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)
! PLASTIC (MISO) material model

tb,plas,11,,3,miso
tbpt,,0.0,1e3
tbpt,,0.6,1e3
! PLASTIC (BISO) material model

tb,plas,12,,,biso
tbdata,1,100,100500
! 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
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
4.6.6. 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.
Initial State
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
!***************************************************************
! 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
4.6.7. Example: Initial Plastic Strain with State Variables

This initial-state example shows how you can use initial-state data (as state variables) from one ana-
lysis, 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 accu-
mulated 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 accu-
mulated 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.
Initial State
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
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
Initial State
esel,s,elem,,1
set,last
allsel,all
pretab,epplx_2r,epply_2r,epplz_2r,epplx_3r,epply_3r,epplz_3r
fini
4.6.8. 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 file 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,x,10
d,all,ux,0.1
nsel,s,loc,y,2
d,all,ux,0.01
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,epsx,node,,epel,x
*vget,epsy,node,,epel,y
*vget,epsz,node,,epel,z
*vget,epsxy,node,,epel,xy
*cfopen,tutor-bag07s-ist.dat ! Generate Ist File
*vwrite
('INIS,SET,NODE,1')
*vwrite,nl(1),epsx(1),epsy(1),epsz(1),epsxy(1)
('INIS,DEFI,',F4.0,' , , , , ',E,' , ',E,' , ',E,',',E,',0.0,0.0')
*cfclos
/solu
ddele,all,all
d,all,all
nall
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
nsel,a,loc,y,2.0
d,all,uy
nall
modopt,lanb,5
mxpand,5
solve
fini
/post1
file,,rstp
set,list
fini
4.6.9. 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-
thermal 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
Initial State
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
4.6.10. Example: Initial Degree of Saturation and Relative Permeability

This example shows how to apply and use initial degree of saturation and relative permeability on
coupled pore-pressure-thermal elements (CPTnnn).
For more information, see Porous Media in the Material Reference.

/prep7
et,1,213
keyopt,1,3,2
rectng,0,0.2,0,1
esize,0.2
amesh,1
MP,EX,1,22E6 ! YOUNG'S MODULUS 22MPa

MP,NUXY,1,0.1 ! POISSON'S RATIO
FPX=1.0e-6
ONE=1.0
TB,PM,1,,,PERM
TBDATA,1,FPX
TB,PM,1,,,BIOT ! BIOT COEFFICIENT
TBDATA,1,ONE
grav_val = 9.8
KS=38e20 !---BULK MODULUS OF SAND
GS=18000 !---SPECIFIC WEIGHT OF SAND
KF=2.0e9 !---BULK MODULUS OF WATER
GF=9800 !---SPECIFIC WEIGHT OF WATER
PORO=0.46
TB,PM,1,,,SP
TBDATA,1,KS,GS
TB,PM,1,,,FP
TBDATA,1,KF,9800,PORO
TB,PM,1,,,GRAV
TBDATA,1,grav_val
TB,PM,1,,,DSAT
TBPT, DEFI,-29392.04436, 6.55E-01
TBPT, DEFI,-19496.6884 , 6.97E-01
TBPT, DEFI,-9684.84608 , 7.68E-01
TBPT, DEFI,-4019.864744, 8.55E-01
TBPT, DEFI,-2600.901772, 8.93E-01
TBPT, DEFI,-1960, 9.16E-01
TBPT, DEFI,-1303.344238, 9.47E-01
TBPT, DEFI,-379.9278504, 9.76E-01
TBPT, DEFI,0, 1
TB,PM,1,,,RPER
TBPT,DEFI,-29399.14446, 1.49E-02
TBPT,DEFI,-19506.50996, 2.86E-02
TBPT,DEFI,-9792.20116, 0.105711
TBPT,DEFI,-4375.105336, 0.28040033
TBPT,DEFI,-2800.991802, 0.50408592
TBPT,DEFI,-2143.613388, 0.7166936
TBPT,DEFI,-1955.016308, 0.7875667
TBPT,DEFI,-1675.97297, 0.84350266
TBPT,DEFI,-1583.528982, 0.8546851
TBPT,DEFI,-1303.344238, 0.92554665
TBPT,DEFI,-841.695638, 0.9739965
TBPT,DEFI,0, 1
d,all,ux,0
nsel,s,loc,y,0
d,all,uy,0
Initial State
allsel
init_kr=0.92554665
init_sw=9.47E-01
inistate,set,dtyp,rper
inistate,defi,all,,,,init_kr
inistate,set,dtyp,dsat
inistate,defi,all,,,,init_sw
init_pres=-1303.344238
nsel,s,loc,y,0
d,all,pres,init_pres
allsel
nsel,s,loc,y,1
d,all,uy,0.01
allsel
finish
/solu
ANTYPE,SOIL
SSOPT,SFSW,0,-1,0,OFF,OFF ! NO FLUID WEIGHT
SSOPT,CONSOLIDATION
NROPT,UNSYM
NSUBST,50,5000,25
KBC,0 ! LOADS CHANGED IN STEPS
OUTRES,ALL,ALL
tim1 = 50
TIME,tim1
SOLVE
finish
/post1
set,first
*get, pp,node,node(0.2,0.4,0),pmsv,ppre
/out,
ppnode=pp
finish
/exit,nosave
4.6.11. 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
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
Initial State
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
4.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.
4.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
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 5: Rotating Structure Analysis
In a dynamic analysis involving a rotating structure, the program takes inertia effects due to the rota-
tional velocity into account. These effects are nonlinear and are automatically included in a nonlinear
transient analysis (NLGEOM,ON).
Depending on the model, these effects may be linearized either in a rotating reference frame or in a
stationary reference frame. The latter is commonly used in rotordynamics analysis and is the scope of
the Rotordynamic Analysis Guide. This section addresses differences between the two approaches as
well as rotating reference frame dynamics.
The linearization and reference frame setting is driven by the CORIOLIS command. When activated,
linear dynamics analysis (such as modal or harmonic analysis) of a rotating structure can be performed.
The following topics related to linear rotating structure analysis are available:
5.1. Understanding Rotating Structure Dynamics
5.2. Choosing the Appropriate Reference Frame Option
5.3. Using a Rotating Reference Frame
5.4. Rotating Reference Frame Analysis Examples
For additional information on the equations, see Rotating Structures in the Theory Reference.
5.1. Understanding Rotating Structure Dynamics

You can observe inertia effects, applied via the CORIOLIS command, in either a stationary reference
frame or a rotating reference frame (p. 73). 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.
[KSP] 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.
[B] is the rotating damping matrix. It changes the apparent stiffness of the structure in both a stationary
and a rotating reference frame. Note that it is not activated by default, but by using the RotDamp flag
on the CORIOLIS command. In a stationary reference frame, this effect is produced when damping is
present in a rotating part (see Adding Damping in the Rotordynamic Analysis Guide). In a rotating reference
frame, this effect only comes from stationary bearings (COMBI214).
Rotating Structure Analysis
[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.
[KSP], [B], and [G] are rotational-velocity-dependent matrices.
{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 centrifugal force.
Without the inertia effect applied via the CORIOLIS command, the program does not generate the [G]
and [B] matrices, and the usual effect of the angular rotation velocity specified by the OMEGA or
CMOMEGA command applies. 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.
For additional information, see Acceleration Effect and Rotating Structures in the Mechanical APDL
Theory Reference.
5.2. Choosing the Appropriate Reference Frame Option

Because the dynamic equations are expressed in different coordinate systems, the rotating (p. 73) and
stationary reference frame approaches have different benefits and limitations.
If the mass of your rotating structure is on the rotational velocity axis (line model), those two approaches
are equivalent as demonstrated in Example: Campbell Diagram Analysis of a Jeffcott Rotor (p. 76).
With increasing rotational velocity and mass*radius product, the stationary reference frame results become
less precise, but the simulation of a typical rotordynamics 3D solid shaft (where the product of mass
outside the centreline and radius is small) can still be performed in this reference frame with good ac-
curacy.
For large mass*radius product and/or large rotational velocity, the rotating reference frame approach
must be used, even if the 3D structure is axisymmetric. In this type of analysis, the prestress effect due
to the rotational velocity must be included. For an example of the procedure, see Example: Campbell
Diagram Analysis of a 3D Bladed Shaft-Disk Assembly (p. 89).
Use the following table to help you choose the best option for your application.
Reference Frame Considerations

Stationary Reference Frame Rotating (p. 73) Reference Frame
In a static analysis, the gyroscopic force vector is In a static analysis, the Coriolis force vector
given by: is given by:
where represents the nodal velocity vector

where represents the nodal velocity
(specified via the IC or ICROTATE command).
vector (specified via the IC or ICROTATE
command).
Using a Rotating Reference Frame
Reference Frame Considerations

Stationary Reference Frame Rotating (p. 73) Reference Frame
You can generate Campbell plots for computing rotor You can generate Campbell plots for computing
critical speeds. Frequency curve variations are usually rotor critical speeds. Frequency curve variations
smooth, and automatic sorting can be used. are usually strong, and automatic sorting is not
recommended.
Structure must be axisymmetric about the spin axis. Structure need not be axisymmetric about the
It is not applicable to rotating structures with periodic spin axis.
(cyclic) symmetry such as impellers.
There is no accuracy loss in this reference
With increasing rotational velocity and frame, but the prestress effect due to the
mass*radius product, the stationary reference rotational velocity must be included.
frame results become less precise, but the
simulation of a typical rotordynamics 3D solid
shaft can still be performed in this reference
frame with good accuracy.
The rotating structure can be part of a stationary The rotating structure must be the only part of
structure in an analysis model (such as a gas turbine an analysis model (such as a gas turbine engine
engine rotor-stator assembly). The stationary structure rotor), except for stationary supports modeled
and supports (such as bearings) need not be with the COMBI214 element.
axisymmetric.
The rotating damping effect can be taken into account The rotating damping effect can be taken into
in rotating parts. See the CORIOLIS command for the account in stationary COMBI214 elements only.
RotDamp option and a list of elements supporting If the element characteristics are isotropic, the
the rotating damping effect in a stationary reference element matrices are linear. Otherwise,
frame. corresponding periodic forces are generated in
a nonlinear transient analysis. See the CORIOLIS
command for the RotDamp option.
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.
Note:
Frequencies obtained from a modal analysis differ according to the reference frame option.
In most cases, frequencies are known in a stationary reference frame through analytical ex-
pressions or experiment. It is therefore recommended you use the stationary reference frame
for modal analyses when applicable.
5.3. Using a Rotating Reference Frame

The primary application for a rotating (rather than a stationary) frame of reference is in the field of
flexible body dynamics where, generally, the structure has no stationary parts and the entire non-
axisymmetric structure is rotating.
The program computes the displacement field and all other result quantities with respect to the coordin-
ate system rotating at the specified angular velocity (CORIOLIS,Option = ON,,,RefFrame = OFF).
Commands specific to modeling a rotating structure are listed in Commands Used in a Rotordynamic
Analysis in the Rotordynamic Analysis Guide.
The procedures for using a rotating reference frame, although similar to the procedures for a stationary
reference frame analysis described in the Rotordynamic Analysis Guide, have specificities detailed below.
One of them is the application of rotating forces (Defining Rotating Forces in the Rotordynamic Analysis
Guide). For example, in a rotating reference frame, a load synchronous with the rotational velocity is a
static load (see Example: Unbalance Response of a Jeffcott Rotor (p. 97)). Similarly, a load rotating at
twice the rotational velocity is synchronous when considered from a rotating reference frame perspective.
5.3.1. Elements Supported

The Coriolis matrix and forces are available for the structural elements listed in the notes section of
the CORIOLIS command.
The following options are not supported:
• Lumped mass (LUMPM) with translational mass only (KeyElt = 1) or frame invariant formu-
lation (KeyElt = 2)
• Layered shell elements
5.3.2. Spin-Softening Effect

In a dynamic analysis, the Coriolis matrix and the spin-softening matrix contribute to the gyroscopic
moment in the rotating reference frame; therefore, the program 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, a warning message about the negative pivot is issued.
• 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.
Using a Rotating Reference Frame
5.3.3. Analysis Types Supported

The following analysis types support rotating structure analysis using a rotating reference frame:
5.3.3.1. Static (ANTYPE,STATIC)
5.3.3.2. Modal (ANTYPE,MODAL)
5.3.3.3. Linear Transient (ANTYPE,TRANS)
5.3.3.4. Harmonic (ANTYPE,HARMIC)
5.3.3.1. Static (ANTYPE,STATIC)

Inertia effects are forces computed by multiplying the Coriolis damping matrix by the initial velocity
of the structure defined with the IC and ICROTATE commands.
5.3.3.2. Modal (ANTYPE,MODAL)

Because of the spin-softening effect, the damped eigensolver (MODOPT,DAMP) is recommended.
Depending on your model, the procedure to obtain eigensolutions and generate a Campbell diagram
is the following:
• If your model uses point mass and beam elements only, the frequencies and mode shapes are
directly obtained with the damped modal analysis. In post-processing, the Campbell diagram
(PRCAMP and PLCAMP commands) can be generated when multiple rotational velocity load
steps are calculated. See Example: Campbell Diagram Analysis of a Jeffcott Rotor (p. 76).
• If your model uses 3D solid or shell elements, as there is mass away from the rotational velocity
axis, prestress must be included and the frequencies and mode shapes are obtained with a linear
perturbation damped modal analysis. In postprocessing, the Campbell diagram (PRCAMP and
PLCAMP commands) can be generated if multiple linear perturbation modal analyses are per-
formed and CAMPBELL,RSTP is activated. See Example: Campbell Diagram Analysis of a 3D Bladed
Shaft-Disk Assembly (p. 89).
Note:
Because natural frequencies are subject to sudden changes around critical speeds in a
rotating reference frame, it is recommended that you use a small rotational velocity in-
crement and not activate the sorting option of the Campbell diagram commands (Option
on PRCAMP and PLCAMP). Also, it is often best to not draw the curves (THICK = -1 on
/GTHK), but show only the markers (specified by /GMARKER).
Frequencies obtained in a rotating reference frame are not the same as those obtained in a stationary
reference frame. Depending on your model and when applicable, a transformation can be used to
deduce one from the other. See Example: Campbell Diagram Analysis of a Jeffcott Rotor (p. 76).
5.3.3.3. Linear Transient (ANTYPE,TRANS)

Linear transient analysis is only applicable to mass and beam element models. Transient analysis
can be performed at a constant rotational velocity or with varying rotational velocity to simulate
a spin-up or spin-down. The procedure is similar to Example: Transient Response of a Startup in

the Rotordynamic Analysis Guide, except for the CORIOLIS command (use CORIOLIS,ON,,,OFF).
If bearings (COMBI214) are stationary, periodic coefficients are automatically included when the
full Newton-Raphson option is activated (NROPT,FULL) and the stiffness and/or damping properties
are not isotropic with respect to the rotational velocity axis.
5.3.3.4. Harmonic (ANTYPE,HARMIC)

The SYNCHRO command is used to specify whether the excitation frequency is synchronous or
asynchronous with the rotational velocity. Remember that, in a rotating reference frame, the ratio
between excitation frequency and rotational velocity (RATIO on the SYNCHRO command) needs
to be adjusted. It is equal to the value observed when in a stationary reference frame minus 1.
5.4. Rotating Reference Frame Analysis Examples

The following complete analysis examples, including command input, are presented here:
5.4.1. Example: Campbell Diagram Analysis of a Jeffcott Rotor
5.4.2. Example: Campbell Diagram Analysis of a Non-Axisymmetric Beam Model
5.4.3. Example: Campbell Diagram Analysis of a 3D Bladed Shaft-Disk Assembly
5.4.4. Example: Unbalance Response of a Jeffcott Rotor
For additional examples of a rotating structure analysis using a rotating reference frame, see the following
test cases in the Mechanical APDL Verification Manual:
• VM197: Rotating Elastic System.
• VM301: Critical Speed of Rotating Disk. Note that, because of the geometry and modes calculated,
CORIOLIS is not needed in this example.
• VM302: Rotating Circular Ring.
See also:
• Example: Piezoelectric Analysis with Coriolis Effect in the Coupled-Field Analysis Guide
5.4.1. Example: Campbell Diagram Analysis of a Jeffcott Rotor

The following example presents a Campbell diagram analysis of a Jeffcott rotor, first in a stationary
reference frame (SRF) and then in a rotating reference frame (RRF). It demonstrates the relationship
between RRF and SRF frequencies.
The model is a massless rigid rotating shaft supported at its ends by identical bearings (COMBI214).
A disk is mounted on the shaft and modelled with a point mass element (MASS21) located at 0.2 m
from its end. The shaft is modeled using constraint equations (CERIG command). The rotational velocity
varies between 0 rpm and 10,000 rpm along the Z axis.
Rotating Reference Frame Analysis Examples
5.4.1.1. Problem Specifications

Inertia properties of the mass:
Mass = 25 kg
Inertia (XX,YY) = 5 kg·m2
Inertia (ZZ) = 10 kg·m2
Shaft length: 1 m
Bearing stiffness: 4e+6 N/m
5.4.1.2. Input for the Analysis

/title, Campbell Diagram Analysis of Jeffcott Rotor
! ** parameters
mass = 25
iz = 10
ix = 5
iy = 5
k = 4e+6
pi = acos(-1)
ratio = pi/30
omend = ratio*10000
/prep7
n,1,0,0,0
n,2,0,0,1
n,3,0,0,0.2
et,1,mass21 ! fake mass for CERIG 6 DOFs

r,1
type,1
real,1
e,1
e,2
et,2,mass21
r,2,mass,mass,mass,ix,iy,iz
type,2
real,2
e,3
cerig,3,all,all
n,100,,,0
n,110,,,1
et,3,combi214 ! bearing
r,3,k,k
type,3
real,3
e,100,1
e,110,2
d,all,uz,0
d,all,rotz,0
d,100,all,0
d,110,all,0
finish
! *** Multistep modal analysis in SRF
nbp2 = 10
domg2 = omend/nbp2
*dim,omg2,array,nbp2+1
*do,iloop,1,nbp2
omg2(iloop+1) = omg2(iloop) + domg2
*enddo
omg2(1) = domg2*1e-2
/solu
antype,modal
modopt,damp,8
mxpand,8
coriolis,on,,,on
*do,iloop,1,nbp2+1
omega,,,omg2(iloop)
solve
*enddo
finish
! ** Campbell in SRF
/post1
/show,png,rev
/yrange,0,400
plcamp,,1,rpm
prcamp,,1,rpm
/show,close
*dim,FRQ_SRF,ARRAY,4
*do,iloop,1,4
*get,FRQ_SRF(iloop),CAMP,iloop,FREQ,nbp2+1
*enddo
finish
! *** Multistep modal analysis in RRF
nbp = 20
domg = omend/nbp
*dim,omg,array,nbp+1
*do,iloop,1,nbp
omg(iloop+1) = omg(iloop) + domg
*enddo
omg(1) = domg*1e-2
/solu
antype,modal
modopt,damp,8
mxpand,8
coriolis,on
*do,iloop,1,nbp+1
omega,,,omg(iloop)
solve
*enddo
finish
! ** Campbell diagram in RRF
/post1
/show,png,rev
/yrange,0,280
/gthk,curve,-1 ! no curve - only markers
/psymb,mark,4 ! marker size
*do,iloop,1,6
/gmarker,iloop,3 ! marker type
*enddo
plcamp,,,rpm
prcamp,,,rpm
/show,close
*dim,FRQ_RRF,ARRAY,4
*do,iloop,1,4
*get,FRQ_RRF(iloop),CAMP,iloop,FREQ,nbp+1
*enddo
finish
! ** Compare SRF and RRF frequencies at maximum spin

frend = omend/(2*pi)
*dim,FRQ_SRF_INRRF,ARRAY,4
FRQ_SRF_INRRF(1) = abs(FRQ_SRF(2) - frend)
FRQ_SRF_INRRF(2) = FRQ_SRF(1) + frend
FRQ_SRF_INRRF(3) = abs(FRQ_SRF(4) - frend)
FRQ_SRF_INRRF(4) = FRQ_SRF(3) + frend
*status,FRQ_SRF
*status,FRQ_RRF
*status,FRQ_SRF_INRRF
5.4.1.3. Output for the Analysis

The outputs for this analysis are shown in the figures below.
Figure 5.1: Campbell Diagram for the Jeffcott Rotor - Stationary Reference Frame (SRF)
Figure 5.2: Campbell Diagram for the Jeffcott Rotor - Rotating Reference Frame (RRF)
Figure 5.3: Relationship Between SRF and RRF Frequencies

PARAMETER STATUS- FRQ_SRF ( 21 PARAMETERS DEFINED)
(INCLUDING 2 INTERNAL PARAMETERS)
LOCATION VALUE
1 1 1 27.1023115
2 1 1 85.1999476
3 1 1 95.8462296
4 1 1 371.081927
PARAMETER STATUS- FRQ_RRF ( 21 PARAMETERS DEFINED)

LOCATION VALUE
1 1 1 81.4667190
2 1 1 193.768978
3 1 1 204.415260
4 1 1 262.512896
PARAMETER STATUS- FRQ_SRF_INRRF ( 21 PARAMETERS DEFINED)

LOCATION VALUE
1 1 1 81.4667190
2 1 1 193.768978
3 1 1 204.415260
4 1 1 262.512896
5.4.2. Example: Campbell Diagram Analysis of a Non-Axisymmetric Beam

Model
The following example from the reference [Friswell et al. (p. 82)] shows a Campbell diagram analysis
in the rotating reference frame of an asymmetric rotor carrying two disks, as shown in Figure 5.4: Asym-
metric Rotor (p. 82).
The model is an asymmetric shaft (BEAM188) defined by its cross-section and inertias supported at
its ends by identical bearings (COMBI214). The disks are modeled with two point-mass elements
(MASS21) located at 0.5 m and 1 m.
The undamped system is studied first, then damping is introduced in the bearings.
The rotational velocity varies between 0 rpm and 4500 rpm. The evolution of the frequencies and of
the stability values are plotted for both undamped and damped systems (PLCAMP). To obtain a more
precise shape of the curves around the instability regions, more points are requested by specifying
a smaller rotational velocity increment.
Only the shaft and disks are rotating, and the bearings are stationary. Bearing damping thus introduces
rotating damping terms in the rotating reference frame analysis (RotDamp = ON on the CORIOLIS
command).
Figure 5.4: Asymmetric Rotor
Reference
Friswell, M., Penny, J., Garvey, S., and Lees, A. Dynamics of Rotating Machines. Cambridge University
Press. 2010.

Geometric properties of the shaft:
Length = 1.5 m
Cross sectional area = 2e-3 m2
Moments of area (Iax, Iay) = (4.2043e-7 m4, 2.4112e-7 m4)
Geometric properties of the disk:
Diameter_1 = 0.28 m
Thickness_1 = 0.07 m
Diameter_2 = 0.07 m
Thickness_2 = 0.35 m
Material properties:
Young’s modulus (E) = 2.11e+11 N/m2

Density = 7810 kg/m3
Poisson's ratio (ν) = 0.3
Bearing properties:
Stiffness (K) = 1e+6 N/m

Damping (C) = 5e+3 N·s/m

/title, Campbell of Non-Axisymmetric Beam Model
! *** parameters
l = 1.5
a = 2e-3
iax = 4.2043e-7
iay = 2.4112e-7
jdummy = 1e-7
e = 211e+9
dens = 7810
nu = 0.3
lld = 0.5
lrd = 1
thkld = 0.07
dld = 0.28
thkrd = 0.07
drd = 0.35
k = 1e+6
c = 5e+3
pi = acos(-1)
ratio = pi/30
omend = 4500
esiz = 0.1
rld = dld/2
mld = pi*thkld*dens*rld**2
idld = mld*(3*rld**2 + thkld**2)/12
ipld = mld*rld**2/2
rrd = drd/2
mrd = pi*thkrd*dens*rrd**2
idrd = mrd*(3*rrd**2 + thkrd**2)/12
iprd = mrd*rrd**2/2
/prep7
! *** geometry
k,1
k,2,,,lld
k,3,,,lrd
k,4,,,l
l,1,2
l,2,3
l,3,4
! *** mesh
lesize,all,esiz
et,1,beam188
mp,ex,1,e
mp,dens,1,dens
mp,nuxy,1,nu
sectype,1,beam,asec
secdata,a,iax,,iay,,jdummy
type,1
mat,1
secnum,1
lmesh,1,3
et,2,mass21
r,2,mld,mld,mld,idld,idld,ipld
type,2
real,2
e,node(0,0,lld)
et,3,mass21
r,3,mrd,mrd,mrd,idrd,idrd,iprd
type,3
real,3
e,node(0,0,lrd)
et,4,combi214
r,4,k,k
type,4
real,4
n,100,0.1
n,104,0.1,,l
e,100,node(0,0,0)
e,104,node(0,0,l)
! *** boundary conditions
d,all,rotz
d,all,uz
d,100,all
d,104,all
! *** component definition
esel,,type,,1,3
cm,shaftcm,elem
allsel
finish
save,case1,db
! *************** Campbell diagram analysis of undamped model
nbp = 60
domg = omend/nbp
nbspins = 73
*dim,omg,array,nbspins+1
*do,iloop,1,nbspins
*if,omg(iloop)+domg,gt,675,and,omg(iloop)+domg,lt,1000,then,
omg(iloop+1) = omg(iloop) + domg/2
*elseif,omg(iloop)+domg,gt,2550,and,omg(iloop)+domg,lt,2925,then,
*elseif,omg(iloop)+domg,gt,4200,then,
*else
*endif
*enddo
omg(1) = domg*1e-2
/solu
antype,modal
modopt,damp,20
mxpand,20
coriolis,on
*do,iloop,1,nbspins+1
cmomega,shaftcm,,,omg(iloop)*ratio
solve
*enddo
finish
/post1
/show,png,rev
/yrange,0,150
/gthk,curve,-1
/psymb,mark,2
*do,iloop,1,10
/gmarker,iloop,3
*enddo
plcamp,,,rpm,,shaftcm,,yes,yes
prcamp,,,rpm,,shaftcm,,yes,yes
/yrange,-5,5
plcamp,,,rpm,,shaftcm,1,yes,yes
prcamp,,0,rpm,,shaftcm,1,yes,yes
/show,close
finish
/clear,nostart
! ***************** Campbell diagram analysis of damped model
/filname,case2
resume,case1,db
/prep7
rmodif,4,5,C,C ! add damping in bearing
finish
nbp2 = 40
nbp = 52
domg = omend/nbp2
*dim,omg,array,nbp+1
*do,iloop,1,nbp
*if,omg(iloop)+domg,gt,600,and,omg(iloop)+domg,lt,1100,then,
*else
*endif
*enddo
omg(1) = domg*1e-2
/solu
antype,modal
modopt,damp,15
mxpand,15
coriolis,on,,,,on ! activate rotating damping effect
*do,iloop,1,nbp+1
cmomega,shaftcm,,,omg(iloop)*ratio
solve
*enddo
finish
/post1
/show,png,rev
/yrange,0,150
/gthk,curve,-1
/psymb,mark,2
*do,iloop,1,10
/gmarker,iloop,3
*enddo
plcamp,,,rpm,,shaftcm,,yes,yes
prcamp,,,rpm,,shaftcm,,yes,yes
/yrange,-30,10
plcamp,,,rpm,,shaftcm,1,yes,yes
prcamp,,0,rpm,,shaftcm,1,yes,yes
/show,close
finish

Without damping, instability regions are identified based on the sign of the stability value. The
stability of the rotor is improved when damping is introduced. The results are shown in the graphs
below.
Figure 5.5: Campbell Diagram for the Undamped Model
Figure 5.6: Stability Values for the Undamped Model
Figure 5.7: Campbell Diagram for the Damped Model
Figure 5.8: Stability Values for the Damped Model
5.4.3. Example: Campbell Diagram Analysis of a 3D Bladed Shaft-Disk As-

sembly
The following example from the reference [Ruffini et al. (p. 91)] presents a Campbell analysis of the
3D bladed shaft-disk assembly shown in Figure 5.9: Bladed Shaft-Disk Assembly (THETA = 0) (p. 90).
The model consists of:
• 9 blades (SHELL181 shell elements)
• A disk (SOLID185 solid elements)
• A shaft (BEAM188 beam elements)
• Contact interfaces between shaft and disk and between disk and blades (TARGE170 target
elements and CONTA175 contact elements).
The shaft is fixed at its end. The rotational velocity varies between 0 rpm and 12,000 rpm along the
Z axis.
The orientation angle of the blade with respect to the rotational velocity axis (parameter THETA) is
first modeled as 0 degrees, then as 90 degrees.
Coriolis effects are activated in the rotating reference frame (CORIOLIS command), and the Campbell
procedure (CAMPBELL command) is used to support the Campbell diagram plot.
Figure 5.9: Bladed Shaft-Disk Assembly (THETA = 0)
Figure 5.10: Bladed Shaft-Disk Assembly (THETA = 90)
Reference
Ruffini V., Schwingshackl C.W., Green J.S. Prediction Capabilities of Coriolis and Gyroscopic Effects in
Current Finite Element Software. Proceedings of the 9th IFToMM International Conference on Rotor
Dynamics. Mechanisms and Machine Science, vol 21. Springer, Cham. 2015.

Geometric properties of the shaft:
Length = 0.25 m
Inner diameter = 0.014 m
Outer diameter = 0.02 m
Geometric properties of the disk:
Outer diameter = 0.2 m

Thickness = 0.04 m
Geometric properties of the blades:
Length = 0.3 m
Thickness = 0.003 m
Width = 0.04 m
Material properties:
Young’s modulus (E) = 2.07e+11 N/m2

Density = 7800 kg/m3
Poisson's ratio (ν) = 0.3

The input listing corresponds to the blade angle THETA = 0.
/title, Campbell of 3D Bladed-Disk-Shaft assembly
! *** PARAMETERS
NS = 9 ! number of blades
THETA = 0 ! orientation of the blades
! disk
Length_D = 0.04
ODiam_D = 0.1*2
! shaft
Length_S = 0.25
IDiam_S = 0.007*2
ODiam_S = 0.01*2
! blade
Length_B = 0.3
Width_B = 0.04
Thick_B = 0.003
! *** ELEMENT TYPES
/PREP7
et,1,185
mp,ex,1,2.07e11
mp,dens,1,7800
mp,nuxy,1,0.3
et,3,170
real,3
et,4,175
keyopt,4,2,2
keyopt,4,9,1
keyopt,4,12,5
et,5,188
mp,ex,5,2.07e11
mp,dens,5,7800
mp,nuxy,5,0.3
sectype,5,beam,ctube
secdata,IDiam_S/2,ODiam_S/2,12
et,6,181
mp,ex,6,2.07e11
mp,dens,6,7800
mp,nuxy,6,0.3
sectype,6,shell
secdata,Thick_B
et,7,170
real,7
et,8,177
keyopt,8,2,2
keyopt,8,9,1
keyopt,8,12,5
! *** DISK GEOMETRY AND MESH
cylind,ODiam_S/2,ODiam_D/2,Length_S-Length_D,Length_S,0,360/NS
ndvDR = 6 ! radial
ndvDC = 8 ! circumferential
ndvDZ = 8 ! along Z
LL = (ODiam_D/2) - (ODiam_S/2)
lsel,,length,,LL
lesize,all,,,ndvDR
lsel,,length,,Length_D
lesize,all,,,ndvDZ
lsel,,length,,Length_D
lsel,r,length,,LL
lsel,inve
lesize,all,,,ndvDC
allsel
type,1
mat,1
vmesh,1
! *** BLADE GEOMETRY AND MESH
csys,1
*get,maxnod,NODE,0,NUM,MAXD
n,maxnod+1,ODiam_D/2,360/NS/2,Length_S-(Length_D/2)
n,maxnod+2,(ODiam_D/2)+Length_B,360/NS/2,Length_S-(Length_D/2)
n,maxnod+3,ODiam_D/2,360/NS/2,Length_S
cs,20,0,maxnod+1,maxnod+2,maxnod+3
wpcsys,,20
wprota,,-THETA
rectng, 0,Length_B, Width_B/2,-Width_B/2
ndvBW = 6 ! width divisions
ndvBL = 50 ! length divisions
lsel,,length,,Length_B
lesize,all,,,ndvBL
lsla
lsel,r,length,,Width_B
lesize,all,,,ndvBW
csys,1
asel,,loc,x,(ODiam_D+Length_B)/2
type,6
mat,6
secnum,6
amesh,all
allsel
! *** CONTACT DISK-BLADE
! contact on blade root

csys,1
asel,,LOC,X,(ODiam_D+Length_B)/2
lsla
lsel,R,LOC,X,ODiam_D/2
nsll,,1
esln
real,3
type,4
esurf
allsel
! target on disk
csys,1
asel,,LOC,X,ODiam_D/2
nsla,,1
esln
type,3
esurf
allsel
! *** CONTACT SHAFT-DISK 1/2 (target elements on disk)
csys,1
asel,,LOC,X,ODiam_S/2
nsla,,1
esln
real,7
type,7
esurf
allsel
! *** GENERATE ALL SECTORS
csys,1
*get,_node_maxval,node,,num,maxd
egen,NS,_node_maxval,all, , , , , , , , , 360/NS
/out,scratch
esel,,type,,1
nsle
nummrg,node
allsel
/output
! *** SHAFT GEOMETRY AND MESH
*get,kpmax,KP,,NUM,MAXD
k,kpmax+1
k,kpmax+2,,,Length_S - Length_D
k,kpmax+3,,,Length_S
ndvS1 = 12
ndvS2 = 4
l,kpmax+1,kpmax+2,ndvS1
l,kpmax+2,kpmax+3,ndvS2
ksel,,kp,,kpmax+1,kpmax+3
lslk
type,5
mat,5
secnum,5
lmesh,all
! *** CONTACT SHAFT-DISK 2/2 (contact elements on shaft)

kpsel,,kp,,kpmax+3
lslk
nsll,,1
esln,,1
real,7
type,8
esurf
allsel
! *** BOUNDARY CONDITIONS

nsel,,loc,z,0
d,all,all
allsel
finish
! *** ROTATIONAL VELOCITY TABLE

nbstep = 25
spin = 12000
dspin = spin/(nbstep-1)
*dim,spins,,nbstep
*vfill,spins,ramp,0,dspin
RATIO = acos(-1)/30
! *** CAMPBELL ANALYSIS
*do,I,1,nbstep
/solu
antype,static
nlgeom,on
autots,on
nsub,2,20,1
omega,,,spins(I)*RATIO
coriolis,on
campbell,rstp
outres,all,none
outres,nsol,all
solve
fini
/solu
antype,static, restart,,,perturb
perturb, modal,,, INERKEEP
solve, elform
modopt,damp,40
mxpand,40
solve
fini
*enddo
! *** PLOT CAMPBELL DIAGRAM
/post1
file,,rstp
/show,JPEG
/yrange,0,250
/gthk,CURVE,-1
/psymb,MARK,4
*do,ILOOP,1,10
/gmarker,ILOOP,3
*enddo
plcamp,off,,RPM,,,,YES,YES
prcamp,off,,RPM,,,,YES,YES
finish

Campbell diagrams for the THETA = 0 and THETA = 90 cases are shown below.
Figure 5.11: Campbell Diagram THETA = 0 Degrees
Figure 5.12: Campbell Diagram THETA = 90 Degrees
5.4.4. Example: Unbalance Response of a Jeffcott Rotor

This example demonstrates the response of a Jeffcott rotor to mass unbalance excitation. It illustrates
the equivalence between the static response in the rotating reference frame and the synchronous
excitation (SYNCHRO command) in the stationary reference frame.
The model is the same as that shown in Example: Campbell Diagram Analysis of a Jeffcott Rotor (p. 76),
except damping is added in the bearings. This introduces rotating damping terms in the rotating
reference frame analysis.
In this example, a force due to a fictive mass unbalance is acting on the mass. The response is calcu-
lated over a frequency range of 0 to 300 Hz. POST26 commands are used to output amplitude versus
frequency/time graphs.
5.4.4.1. Problem Specification

Inertia properties of the mass:
Mass = 25 kg
Inertia (XX,YY) = 5 kg·m2
Inertia (ZZ) = 10 kg·m2
Shaft length: 1 m
Bearing stiffness: 4e+6 N/m
Bearing damping: 1e+3 N·s/m
Excitation force amplitude (mass unbalance multiplied by eccentricity): 1e-3 kg·m

/title, Unbalance Response of a Jeffcott Rotor
! ** parameters
mass = 25
iz = 10
ix = 5
iy = 5
k = 4e+6
c = 1e+3
pi = acos(-1)
nstep = 300
f0 = 1e-3
/prep7
n,1,0,0,0
n,2,0,0,1
n,3,0,0,0.2
et,1,mass21 ! fake mass for CERIG 6 dofs

r,1
type,1
real,1
e,1
e,2
et,2,mass21
r,2,mass,mass,mass,ix,iy,iz
type,2
real,2
e,3
cerig,3,all,all
n,100,,,0
n,110,,,1
et,3,combi214 ! bearing
r,3,k,k,,,c,c
type,3
real,3
e,100,1
e,110,2
d,all,uz,0
d,all,rotz,0
d,100,all,0
d,110,all,0
esel,,type,,2
cm,masscm,elem
allsel,all
finish
save
! *** SYNCHRO ANALYSIS IN SRF
/solu
antype,harmonic
hropt,full
harfr,0,300
nsubst,nstep
kbc,1
f,3,fx,f0
f,3,fy,,-f0
coriolis,on,,,on
synchro
omega,,,1.0
solve
finish
/post26
nsol,2,3,u,x,ux3
nsol,3,3,u,y,uy3
realvar,4,2,,,ux3r
realvar,5,3,,,uy3r
prod,6,4,4,,ux3_2
prod,7,5,5,,uy3_2
add,8,6,7,,ux3_2+uy3_2
sqrt,9,8,,,ampl3_srf
*get,max_srf_,VARI,9,EXTREM,VMAX
parsav
/show,png,rev
/gropt,logy,1
/xrange,0,300
plvar,9
finish
! *** STATIC ANALYSIS IN RRF
/clear, nostart
resume,,db
parres
dfrq = 1
/solu
antype,static
kbc,1
coriolis,on,,,,on
frq = dfrq
*do,iloop,1,nstep
/gopr
time,frq
omg = 2*pi*frq
cmomega,masscm,,,omg
ftot = f0*omg**2
f,3,fx,ftot
solve
frq = frq + dfrq
*enddo
finish
/post26
nsol,2,3,u,x,ux3
nsol,3,3,u,y,uy3
prod,6,2,2,,ux3_2
prod,7,3,3,,uy3_2
add,8,6,7,,ux3_2+uy3_2
sqrt,9,8,,,ampl3_rrf
*get,max_rrf_,VARI,9,EXTREM,VMAX
/show,png,rev
/gropt,logy,1
/xrange,0,300
plvar,9
finish
! *** COMPARE MAXIMUM AMPLITUDE

*status,PRM_

The unbalance force response is output for the stationary reference frame case, and the static re-
sponse is output for the rotating reference frame case.
Figure 5.13: Unbalance Force Response in SRF
Figure 5.14: Static Response in RRF
Chapter 6: Cyclic-Loading Analysis and Cycle-Jump
Method
A cyclic-loading analysis (p. 103) repeats a predefined loading cycle (or cycles) a specified number of
times. Cyclic-loading simulation has applications in industries where fatigue failure is a concern, such
as automotive, aerospace, nuclear power, chemical, and electronics. A load can be any external para-
meter or combination of parameters affecting the solution, such as force, displacement, and temperature.
Loading cycles are defined via tabular array parameters.
The cycle-jump method (p. 107) accelerates a cyclic-loading analysis by allowing the solver to jump over
loading cycles based on control-function criteria. The method can be applied to any cyclically loaded
problem where the solution may change rapidly within a particular cycle but evolves gradually on a
cycle-by-cycle (global) basis. The global slow evolution allows cycles to be jumped over in the interest
of efficiency and speed. When the global evolution is not slow, no cycle jumps occurs.
The following topics are available:

6.1. Cyclic-Loading Analysis
6.2. Cycle-Jump Analysis
Also see Accelerated Thermomechanical Fatigue Analysis of Thermal-Barrier Coatings in the Technology
Showcase: Example Problems.
6.1. Cyclic-Loading Analysis

This command initiates and sets solution parameters for a cyclic-loading analysis:
CLOAD, Option, Input1
To specify the various controls (Option), issue the command multiple times.
The following steps are involved in a cyclic-loading analysis:

6.1.1. Step 1: Define the Tabular Array
6.1.2. Step 2: Fill in the Cyclic-Loading Table Values
6.1.3. Step 3. Apply the Cyclic-Loading Table(s)
6.1.4. Step 4. Define Cyclic-Loading Parameters
6.1.5. Step 5. Define Time-Stepping Parameters
6.1.6. Step 6. Select Output Time Points
6.1.7. Step 7. Solve the Cyclic-Loading Analysis
Cyclic-Loading Analysis and Cycle-Jump Method
6.1.1. Step 1: Define the Tabular Array

Define the tabular array (*DIM). Set the tabular array size according to the number of time points
needed to define one cycle of loading. If you intend to use multiple tabular arrays for cyclic loading,
all arrays must be of the same size.
Issue CLOAD,DEFINE,BEGIN and CLOAD,DEFINE,END commands before and after load table definitions,
respectively, to mark tabular array or arrays as cyclic-loading tables.
Example 6.1: Marking Tabular Arrays as Cyclic-Loading Tables

CLOAD,DEFINE,BEGIN
*DIM,_cycload1,TABLE,4
*DIM,_cycload2,TABLE,4
CLOAD,DEFINE,END
Load tables not marked via CLOAD,DEFINE as cyclic-loading tables in this manner will not be cyclically
repeated.
6.1.2. Step 2: Fill in the Cyclic-Loading Table Values

Column 0 contains the time points of the cyclic-loading table, and column 1 contains the load values.
Example 6.2: Specifying Values in a Cyclic-Loading Table

! Time values
_cycload1(1,0) = 0.
_cycload1(2,0) = 0.25
_cycload1(3,0) = 0.8
_cycload1(4,0) = 1.2
! Load values
_cycload1(1,1) = 0.
_cycload1(2,1) = 0.1
_cycload1(3,1) = -0.15
_cycload1(4,1) = 0.
If there are multiple cyclic-loading tables, they must have the same time values.
6.1.3. Step 3. Apply the Cyclic-Loading Table(s)

Apply the cyclic-loading table(s) to the finite element problem.
Example 6.3: Applying Cyclic-Loading Tables

NSEL, S, LOC, Y, 10
D,All,UY,%_cycload1%
NSEL, S, LOC, X, 10
D,All,UX,%_cycload2%
6.1.4. Step 4. Define Cyclic-Loading Parameters

Define the cyclic-loading analysis parameters by specifying the length of each loading cycle
(CLOAD,CYCTIME) and total number of cycles (CLOAD,CYCNUM). The final time point of the defined
cyclic-loading tables must coincide with the value of the cycle length.
Cyclic-Loading Analysis
Example 6.4: Defining Cyclic-Loading Parameters

CLOAD,CYCNUM,100 ! total number of cycles
CLOAD,CYCTIME,1.2 !time length of each cycle
6.1.5. Step 5. Define Time-Stepping Parameters

By default, time-stepping (NSUBST or DELTIM) applies to a single cycle length (and not the total
analysis time).
If you increase the total number of cycles (CLOAD,CYCNUM), it is generally unnecessary to adjust
time-stepping. The program also ensures that the time points defined in the cyclic-loading table are
not missed.
Figure 6.1: Time Points and Ranges in a Cyclic-Loading Table
6.1.5.1. Enabling Time-Stepping for Each Time-Point Range

If the loading cycles have nonuniform time-point ranges, the default time-stepping scheme can
lead to an excessive number of substeps and longer run times.
In such cases, you can set time-stepping to apply to each time-point range ( in the figure)
in a cycle. If you enable this option (CLOAD,TSTEP), time-stepping resets at each time-point defined
in the cyclic-loading table.
Example 6.5: Defining Time-Stepping Parameters for a Time-Point Range

CLOAD,TSTEP ! enable time-point range time-stepping
NSUBST,1,20,1 ! time-stepping command
6.1.6. Step 6. Select Output Time Points

Writing all results for all substeps can lead to very large results (.rst) files.
To reduce the .rst file size, you can set output for specific time points only (CLOAD,OUTR), such
as A and B in Figure 6.1: Time Points and Ranges in a Cyclic-Loading Table (p. 105). Used with the key-
time array option (OUTRES,,%array%), defined output points are required for only one cycle.
If you limit output to specific time points, results are output for each cycle by default. You can adjust
the results frequency to output results at a specified cycle frequency (for example, every 10 cycles).
Any key-time array point defined must also be a defined time-point in the cyclic-loading table.
Example 6.6: Selecting Output Time Points

*dim,timvals,array,2
timvals(1)=0.25
timvals(2)=1.2
OUTRES,ALL,%timvals%
CLOAD,OUTR,10 ! output every 10 cycles
6.1.7. Step 7. Solve the Cyclic-Loading Analysis

Initiate the solution process (SOLVE). The program repeats the loading cycles for the specified number
of times. The final solution time is therefore CYCTIME x CYCNUM. Do not enter a time value (TIME)
for a cyclic-loading analysis solution.
Each cyclic-loading analysis solution occurs in a single load step with multiple substeps. All cycles are
part of the same load step.
Load-step output includes information about the cyclic-loading analysis:
A cyclic-loading solution can be combined with a standard analysis solution in any order and combin-
ation. A single analysis can include multiple solutions of either type. For a standard solution, input
the end time of the solution (TIME); otherwise, the program increments the prior load-step time value
by 1.
In the case of multiple cyclic-loading solutions in a single analysis, each one requires CLOAD,CYCNUM
to be issued before the associated SOLVE.
Example 6.7: Cyclic Loading and Standard Solutions in a Single Analysis

! Load step 1: Standard SOLVE
!define solution options
…
Cycle-Jump Analysis
TIME, 500
SOLVE
! Load step 2: Cyclic-Loading SOLVE

!define solution options
…
CLOAD,CYCNUM,10
CLOAD,CYCTIME,20 ! No TIME command entered
SOLVE

! define solution options
…
CLOAD,CYCNUM,5
CLOAD,CYCTIME,20 ! No TIME command entered
SOLVE
! Load step 4: Standard SOLVE

…
TIME, 900
SOLVE
All loads such as degree-of-freedom constraints, forces, surface loads, and body force loads can be
used for cyclic loading. The load must be entered as table. The start and end load values of the load
table should be the same to prevent unexpected large load increments when cyclic loading occurs.
In this figure, the applied force load is ramped up to the starting value of the cyclic loading, and the
cyclic loading has identical beginning and ending values:
Figure 6.2: Analysis with Two Standard Solutions Followed by a Cyclic-Loading Analysis
A cyclic-loading analysis can be performed independent of a cycle-jump analysis (p. 107).
6.2. Cycle-Jump Analysis

The cycle-jump analysis method accelerates a cyclic-loading analysis (p. 103) by jumping over cycles
based on a global evolution trend line.
The following topics about cycle-jump analysis are available:
6.2.1. Understanding the Cycle-Jump Method

6.2.2. Performing a Cycle-Jump Analysis
6.2.3. Cycle-Jump Recommendations
6.2.4. Cycle-Jump Limitations
6.2.5. Example: Cycle-Jump Analysis
6.2.1. Understanding the Cycle-Jump Method

The cycle-jump method is based on the observed response of a structure under cyclic loading, where
solution variables change rapidly within a given cycle but evolve gradually on a cycle-by-cycle basis.
Figure 6.3: Response of a Structure Under Cyclic Loading
The global long-term trend can be expressed mathematically as a global evolution function, enabling
solution variables to be extrapolated by jumping over intermediate cycles.
The solution variable monitored for global evolution to calculate the allowable jump is a control
variable. Variables involved in the finite element analysis (such as stress, plastic strain, and degrees
of freedom) can be control variables. Several control variables can be selected together.
The allowable jump is set as the minimum of the calculated jump values from all Gauss points (or
nodes) for a control variable. When more than one control variable is defined, the minimum value
across all control variables is used as the allowable jump.
A jump occurs if the allowable jump is greater than the cycle time. The jump value is always rounded
down to the nearest cycle-time multiple. If a jump occurs, all variables needed for a finite element
analysis (such as stress, strain, state variables, and degrees of freedom) are extrapolated. The extrapol-
ated state is imposed as the new state at time t0 after the jump.
Cycle-Jump Analysis
6.2.1.1. Jump Calculation

Consider the evolution of a given control variable over time, as shown in Figure 6.3: Response of a
Structure Under Cyclic Loading (p. 108). P1, P2, and P3 are points at the same relative point in time
for the previous three cycles, with P1 being the most recent point. The slopes s12 and s23 are cal-
culated as:
The allowable jump via either of the following methods:
• Slope-based (Cojocaru and Karlsson, 2006) (p. 109)
• Variable-based (Bogard et al., 2008) (p. 109)
6.2.1.1.1. Slope-Based Jump Calculation
The default slope-based method (CJUMP,CALC,1) calculates the allowable jump such
that the predicted slope does not change beyond a user-imposed jump criterion :
(6.1)
The slope-based calculation is susceptible to small or no jumps for small slope values.
6.2.1.1.2. Variable-Based Jump Calculation

Derived using a Taylor-series expansion of the variable evolution, the variable-based method
(CJUMP,CALC,2) calculates the allowable jump via a user-imposed jump criterion and
the cycle history of the control variables:
(6.2)
6.2.1.2. Extrapolation Following a Jump

The Heun integrator is used to extrapolate the solution variables for a cycle jump:
The extrapolation method is the same for slope-based (p. 109) and variable-based (p. 109) jump cal-
culation, where is calculated using Equation 6.1 (p. 109).
6.2.2. Performing a Cycle-Jump Analysis

A cycle-jump analysis requires an associated cyclic-loading analysis (p. 103) (CLOAD).
This command initiates and sets solution parameters for the cycle-jump analysis:
CJUMP, Option, Input1
To specify the various controls (Option), issue the command multiple times.
The following cycle-jump analysis topics are available:

6.2.2.1. Initiating the Cycle-Jump Analysis
6.2.2.2. Specifying the Intent of the Cycle Jump
6.2.2.3. Other Cycle-Jump Options
6.2.2.4. Understanding Cycle-Jump Solution Output
6.2.2.1. Initiating the Cycle-Jump Analysis

Define cyclic-loading options first, then initiate the cycle-jump analysis, specifying the jump criterion
(Option = CRIT).
Example 6.8: Initiating the Cycle-Jump Analysis

! define cyclic-loading options
…
CLOAD,CYCNUM,10
CLOAD,CYCTIME,20
! define cycle-jump options
CJUMP,CRIT,1
SOLVE
In the case of multiple cycle-jump solutions in a single analysis, each one requires CJUMP,CRIT to
be issued before the associated SOLVE.
6.2.2.2. Specifying the Intent of the Cycle Jump

In an analysis that includes standard solutions before a cyclic-loading analysis, specify the intent
of the cycle jump (Option = INTENT) before the first solution.
Cycle-Jump Analysis
Figure 6.4: Analysis with Standard Solutions Preceding the Cyclic-Loading Analysis
Example 6.9: Specifying the Intent of the Cycle Jump

!Load step 1: Standard SOLVE
…
CJUMP,INTENT
TIME, 2
SOLVE
…
…
CLOAD,CYCNUM,10
CLOAD,CYCTIME,30
CJUMP,CRIT,1
SOLVE
6.2.2.3. Other Cycle-Jump Options

While Option = CRIT (p. 110) is required to define the jump criterion, and Option = INTENT (p. 110)
must be specified when needed, all other CJUMP Option values are optional.
The following topics about optional cycle-jump settings are available:

6.2.2.3.1. Setting Minimum, Initial, and Maximum Cycles
6.2.2.3.2. Empirical Adjustment of Minimum Intermediate Cycles
6.2.2.3.3. Setting the Relative Time
6.2.2.3.4. Setting a Control Variable
6.2.2.3.5. Material-ID-Dependent Jump Control
6.2.2.3.6. Material-ID- and/or Control-Variable-Dependent Jump Criterion
6.2.2.3.7. Jump-Calculation Option
6.2.2.3.8. Statistical Jump Calculation
6.2.2.3.1. Setting Minimum, Initial, and Maximum Cycles

Set the minimum number of initial cycles at the beginning of a cyclic-loading analysis before a
jump is allowed via Option = INICYC.
To set the minimum number of intermediate cycles before a jump is allowed at any state of the
cyclic-loading analysis, use Option = MINCYC (including the initial cycles at the beginning of
the cyclic-loading analysis if INICYC is not set).
Defaults are INICYC = 3 and MINCYC = 3, as at least three cycles are needed to establish the
global trend.
To set the maximum intermediate number of cycles to jump, use Option = MAXJUMP.
Example 6.10: Setting Minimum, Initial, and Maximum Cycle-Jump Options

CJUMP,MINCYC,5
CJUMP,INICYC,10
CJUMP,MAXJUMP,20
6.2.2.3.2. Empirical Adjustment of Minimum Intermediate Cycles

You can adjust the minimum number of intermediate cycles N int based on the jump length,
thereby limiting jump occurrences in cases of highly nonlinear global trends. Initially, N int = N
min . The adjustment is calculated as:
are your minimum intermediate cycle-adjustment parameters defining the increase and
decrease, respectively, of intermediate cycles. To set your adjustment parameters, enter N min
(Input1), (Input2), and (Input3) via Option = MINCYC.
Example 6.11: Setting Minimum Intermediate Cycle-Jump Options

! Set minimum increase ( p) to 2 and minimum decrease ( m) to 1 for intermediate cycles
CJUMP,MINCYC,5,2,1
Defaults:
6.2.2.3.3. Setting the Relative Time

Cycle-jump calculations occur at the same relative point in time for each cycle.
As shown in Figure 6.4: Analysis with Standard Solutions Preceding the Cyclic-Loading Analys-
is (p. 111), points A1 and A2 are at the same relative point in time for the two cycles shown.
Similarly, points B1 and B2 are at the same relative point in time.
By default, the program sets the relative time value to correspond to an absolute maximum load
value for a defined load cycle. In the figure, the default would be set as B1 (or B2).
Cycle-Jump Analysis
Optionally, you can specify a relative time value via Option = RELTIME. The relative time must
coincide with a defined time point in the cyclic-loading table.
Example 6.12: Setting the Relative Time

CJUMP,RELTIME,25
6.2.2.3.4. Setting a Control Variable

The default control (Option = CONTROL) variable for cycle-jump calculation is stress (S).
Optionally, other control variables can be chosen via Option CONTROL. Multiple control variables
are allowed.
Generally, for control variables (such as stress, plastic strain, and degrees of freedom), jump cal-
culations are performed based on equivalent values.
Example 6.13: Setting Control Variables

! set stress control var
CJUMP,CONT,S
! set plastic strain control var
CJUMP,CONT,EPPL
For problems involving user-programmable features (such as UserMat), you can set state variables
as control variables. You can select specific state variables for jump control. The material ID asso-
ciated with the state variables must be specified.
For state-variable control, jump calculations are performed based on individual values.
Example 6.14: Setting State Variable Control

! select material associated with state variable
CJUMP,CONT,SVAR,MAT,2 !material 2
! enter up to 6 state variable entries per line
CJUMP,CONT,SVAR,SEL,2,3,5,6
! enter as many lines as needed
CJUMP,CONT,SVAR,SEL,9,1,100,12,8,19
Outputting State Variables at Select Time Points
To output state variables at select time points (p. 106), issue CLOAD,OUTR and OUTRES,ALL before
issuing OUTRES,SVAR.
Example 6.15: Outputting State Variables at Select Time Points

CLOAD,OUTR
OUTRES,ALL,%timvals%
OUTRES,SVAR,%timvals%
6.2.2.3.5. Material-ID-Dependent Jump Control

By default, all materials in a body control the jump.
You can select specific materials to control the jump (CJUMP,CNMT). Jump calculations are then
performed for the selected materials only. This option applies to both Gauss-point-based (stress,
plastic strain, etc.) and degree-of-freedom-based control. For materials not selected, jump calcu-
lations are omitted. When a jump occurs, however, extrapolation (p. 109) of values occurs for the
entire body.
You can specify up six material IDs on each CJUMP,CNMT command. Issue the command as many
times as needed.
Example 6.16: Setting Material-ID-Dependent Jump Control

CJUMP,CNMT,2,4,6,5 ! up to 6 mat IDs per line (can be less)
CJUMP,CNMT,1,11 ! enter as many lines as needed
6.2.2.3.6. Material-ID- and/or Control-Variable-Dependent Jump Criterion

You can set a jump criterion to be dependent on the material ID (CJUMP,ADCR,MAT) and/or the
control variable (CJUMP,ADCR,CONT).
Example 6.17: Setting a Material-ID- and Control-Variable-Dependent Jump Criterion

CJUMP,ADCR,MAT,2,0.5
CJUMP,ADCR,MAT,12,1.0
CJUMP,ADCR,CONT,DOF,0.6
CJUMP,ADCR,CONT,EPPL,0.2
If you define material-ID- and/or control-variable-dependent jump criteria, they override any
global jump criteria (defined via CJUMP,CRIT). Global jump criteria (if defined) still apply to any
jump-calculation point not affected by a CJUMP,ADCR command. If no global jump criteria are
defined, the jump calculation is omitted for any jump-calculation points not having associated
jump criteria. Global jump criteria are not required if you define material-ID- or control-variable-
dependent jump criteria.
When you define both material-ID- and control-variable-dependent jump criteria for a jump-cal-
culation point, the program uses the smaller value. For example, if your jump criterion is 0.8 for
material 2 and your jump criterion is 0.2 for control variable EPPL, a jump criterion of 0.2 will
apply to any jump-calculation point where the material ID is 2 and control is EPPL.
For a control-variable-dependent jump criterion, you must still set the appropriate control variable
(CJUMP,CONT).
In the case of multiple cycle-jump solutions in a single analysis, each requires a CJUMP,ADCR
command to be issued before the associated SOLVE command.
6.2.2.3.7. Jump-Calculation Option

By default, the program uses the slope-based (p. 109) jump-calculation method to calculate jump.
If needed, you can specify the variable-based (p. 109) jump-calculation method instead
(CJUMP,CALC,2).
6.2.2.3.8. Statistical Jump Calculation

By default, the program uses the minimum value across all jump-calculation points (Gauss point
and/or node) as the jump value.
Cycle-Jump Analysis
For some problems, the default behavior may be too conservative, as some jump-calculation
points lead to smaller-than-desired jumps. In such cases, you can use the statistical jump-calculation
method (CJUMP,PERC), which selects the jump value as a percentile of the cumulative frequency
of all jump values (Van Paepegem et al., 2001).
The percentile technique relies on the jump-value information from all jump-calculation points.
For multiple Gauss-point-based control variables active together (such as stress and plastic strain),
the smallest value is stored at a given Gauss point. When both Gauss-point and node-based
control are active together (such as stress, plastic strain, and degrees of freedom), the cumulative
frequency is determined based on information from both the Gauss points and nodes.
Example 6.18: Setting a Percentile of the Cumulative Frequency

CJUMP,PERC,2.5
6.2.2.4. Understanding Cycle-Jump Solution Output

The load-step options output indicates that a cycle-jump analysis is being performed:
When a jump occurs, the output indicates the jump value.
Example 6.19: Output Indicating a Jump
Basic cycle-number information is output.
Example 6.20: Cycle Output Information
When a jump is not possible, you can request diagnostic information (CJUMP,OUTP) such as the
smallest calculated jump and the location of the smallest jump values for the jump-calculation
points.
Example 6.21: Diagnostic Information Output
At the completion of the cycle-jump analysis, the output includes a summary.
Example 6.22: Cycle-Jump Analysis Summary
6.2.3. Cycle-Jump Recommendations

Consider the following recommendations when performing your own cycle-jump analysis:
• The jump criterion (p. 108) value (Option = CRIT) can be based on a sensitivity analysis where
the jump criterion value is varied and the cycle-jump behavior observed. As a reference, you can
use a solution where no cycle jumps occur. Ideally, the loading conditions in the sensitivity analysis
should replicate loading conditions for which the cycle-jump analysis is desired.
• Examine results carefully and look for large jump values (p. 115), as convergence may not always
guarantee that the solution is accurate with respect to a reference.
• Exercise care when using material models where solution variables are a function of time (such as
time-hardening creep). In such cases, the predicted slope will not match the actual slope, especially
for large jumps. If necessary, you can limit the maximum jump (p. 112) (Option = MAXJUMP).
• Stress (S) tends to work well as a control variable (p. 113) (Option = CONTROL). In general solution
variables with linear evolution may not work well as control variables (by themselves) as they will
trigger larger jumps not permitted by the more nonlinear response of another solution variable.
Cycle-Jump Analysis
• Compared to a cyclic-loading (p. 103)-only analysis, a cycle-jump analysis requires more memory
and generates larger .esav files to maintain a history of cycle information. Therefore, use the
cycle-jump feature only for problems where jumps are feasible.
6.2.4. Cycle-Jump Limitations

The following limitations apply to the cycle-jump analysis method:
• Available only for static analysis types (ANTYPE,STATIC).
• Supported only by the 18x group of element numbers.
• Enhanced strain is not supported.
• Can be used with the following material models only:
– Chaboche Nonlinear Kinematic Hardening (TB,CHABOCHE)
– Bilinear Isotropic Hardening Plasticity (TB,PLASTIC,,,,BISO)
– Bilinear Kinematic Hardening Plasticity (TB,PLASTIC,,,,BKIN)
– Multilinear Isotropic Hardening Plasticity (TB,PLASTIC,,,,MISO)
– Nonlinear Isotropic Hardening (TB,NLISO)
– Rate-Dependent Plasticity (TB,RATE)
• Contact element state variables are not extrapolated after a jump. Exercise caution and examine
results when using the cycle-jump method with contact elements.
6.2.5. Example: Cycle-Jump Analysis

Following is the model to be used in a cycle-jump analysis:
Figure 6.5: Plate with Hole
The results obtained from the cycle-jump analysis are compared with a reference jump-free cyclic-
loading solution.
The specimen has a rate-dependent Chaboche viscoplastic material. The Chaboche parameters are
temperature-dependent. Thermal expansion coefficients are also defined.
The specimen is subjected to cyclic pressure loading on the top face and displacement on the right
face. The entire specimen is subject to a temperature cycle as well. The loading cycles are as follows:
Cycle-Jump Analysis
All the example parameter values are given in the problem input.
The problem is solved in Mechanical APDL using the 3D SOLID185 element. A simply supported
boundary condition is imposed on the specimen.
The specimen is first loaded to imposed values via a standard solution. Therefore, the intent of cycle-
jump is declared (CJUMP,INTENT).
The cyclic-loading analysis (with cycle-jump) is performed for a total of 100 cycles.
The cycle-jump analysis results in 57 of 100 cycles jumped.
Following are plots of the equivalent stress and equivalent plastic strain as a function of time. A node
on the plate hole is selected for this result.
The following contour plots show the equivalent stress and equivalent plastic strain at the final time
value as a comparison against references. Observe that the final substep of the cycle-jump solution
is 860 compared to 2000 of the reference.
6.2.5.1. Input File Used in This Example

Following is the input file used in the example cycle-jump analysis:
/BATCH,LIST
/TITLE,platehole,Cycle-Jump: Plate with hole

/filn,platehole
! --- pre-processor
/prep7
Cycle-Jump Analysis
test_name = 'platehole'
! parameters
elem_ = 185
H_=100
W_=100
D_=100
temp_=100
nocyc_= 100
cyctime_ = 2000
!*******************************
! define material
MP,EX,1,200000
MP,NUXY,1,0.3
sig0=6.0
c1=248000.0
c2=300.0
c3=148000.0
c4=500.0
r0=10.0
Rinf=100.
b = 50
TB,CHAB,1
TBTEMP,0
TBDATA,1,sig0,c1,c2,c3,c4
TBTEMP,temp_
TBDATA,1,0.75*sig0,0.7*c1,c2,0.9*c3,c4
TB,RATE,1,,,EVH
TBDATA,1,sig0,r0,Rinf,b,0.3,100
cteval=1e-5
TB,CTE,1
TBDATA,1,cteval,cteval,cteval
! end material definition

!*******************************
!Element type
ET,1,185
! geometry
rectng,0,W_,0,H_
CYL4, W_/2, H_/2, H_/8
asba,1,2
extopt,esize,0.25
vext,3,,,,,D_/8
! mesh
esize,5
veorient,1,thin
local,11,0,0,0,0,0,0,0
esys,11
vsweep,1,3
csys,0
FINI
! --- solution
/SOLU
anty,stat
! displacement boundary conditions

NSEL,S,LOC,Y,0
D,All,UY,0
NSEL,S,LOC,X,0
D,All,UX,0
NSEL,S,LOC,Z,0
D,All,UZ,0
! declare cycle-jump intent before standard solution

CJUMP,INTENT
! loading
NSEL,S,LOC,X,W_
D,All,UX,-1
NSEL,S,LOC,Y,H_
SF,ALL,PRES,30
NSEL,ALL
DELT,100,10,100
TIME, 500
OUTRES,ALL,ALL
SOLVE !standard solution
!cyclic loading definition

CLOAD,DEFINE,BEGIN
! define cyclic load table
*DIM,_cycloadx,TABLE,5
*DIM,_cycloady,TABLE,5
*DIM,_cycloadtemp,TABLE,5
CLOAD,DEFINE,END
! define cyclic tabular load

! Time values
_cycloadx(1,0) = 0.
_cycloadx(2,0) = 500
_cycloadx(3,0) = 1000
_cycloadx(4,0) = 1500
_cycloadx(5,0) = cyctime_
! Load values
_cycloadx(1,1) = -1
_cycloadx(2,1) = -1
_cycloadx(3,1) = 1.5
_cycloadx(4,1) = 1.5
_cycloadx(5,1) = -1
! Time values
_cycloady(1,0) = 0.
_cycloady(2,0) = 500
_cycloady(3,0) = 1000
_cycloady(4,0) = 1500
_cycloady(5,0) = cyctime_
! Load values
_cycloady(1,1) = 30
_cycloady(2,1) = 30
_cycloady(3,1) = -20
_cycloady(4,1) = -20
_cycloady(5,1) = 30
! Time values
_cycloadtemp(1,0) = 0.
_cycloadtemp(2,0) = 500
_cycloadtemp(5,0) = cyctime_
! Temp values
Cycle-Jump Analysis
! apply cyclic load table

NSEL,S,LOC,X,W_
D,All,UX,%_cycloadx%
NSEL,S,LOC,Y,H_
SF,ALL,PRES,%_cycloady%
ALLSEL,ALL
BFE,ALL,TEMP,,%_cycloadtemp%
TREF,0
ALLSEL,ALL
!define cyclic loading analysis parameters

CLOAD,CYCNUM,nocyc_
CLOAD,CYCTIME,cyctime_
!define cycle-jump analysis parameters

CJUMP,CRIT,1
SOLVE !cycle-jump analysis solution
save
FINISH
! --- post-processor
/POST26
nsel,all
yhole = H_/2 - H_/8
nn=node(W_/2,yhole,0)
ANSOL,2,nn,s,eqv
ANSOL,3,nn,eppl,eqv
PRVAR,2,3
*GET,ndata,VARI,0, NSETS
*dim,stresseqv,array,ndata
*dim,plstraineqv,array,ndata
VGET,time,1
VGET,stresseqv,2
VGET,plstraineqv,3
! write results to file (for processing in plotting software)

*cfopen,results-platehole,out
*vwrite,time(1),stresseqv(1),plstraineqv(1)
(E16.6,E16.6,E16.6)
*cfclos
FINISH
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. 125). 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
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
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 depend-
ency 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. 127).
2. Create the submodel (p. 128).
3. Perform cut-boundary interpolation (p. 129).
Using Submodeling
4. Analyze the submodel (p. 131).
5. Verify that the distance between the cut boundaries and the stress concentration is ad-
equate (p. 133).
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. 141) allows you to build your coarse model
with shell elements and your submodel with 3D solid elements. This technique is discussed in Shell-
to-Solid Submodels (p. 141).
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
Submodeling
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
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
overwritten. 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 submodeling (p. 141) allows you to switch from shell elements in the coarse model to 3D
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. 128).
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 Interpolation (p. 129)). To specify node rotations, use one of these methods:
Using Submodeling
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.
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 interpol-
ating 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 temper-

ature-dependent material properties, or in a thermal-stress analysis, the temperature distribu-
tion 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,File-
name,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.
Submodeling
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
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
Postproc). 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 in-
terpolation 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 dif-
ferent 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 cumulative iteration number of the results set used).
Using Submodeling
8. All interpolation work is now done, so leave POST1 (FINISH) and restore the submodel
database (RESUME 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
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. 132)).
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.
Submodeling
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 re-
peated until all cut-boundary degree-of-freedom constraints are applied. Then, exit the solution pro-
cessor.
The overall data flow for submodeling (without temperature interpolation) is shown in Figure 7.6: Data
Flow Diagram for Submodeling (Without Temperature Interpolation) (p. 132).
Figure 7.5: Loads on the Submodel
Figure 7.6: Data Flow Diagram for Submodeling (Without Temperature Interpolation)
Using Submodeling
7.2.5. Verify the Distance Between the Cut Boundaries and the Stress Con-
centration
The final step is to verify that the cut boundaries of the submodel are far enough away from the
concentration. 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. 133) and Figure 7.8: Path Plots to Compare Results (p. 133).
Figure 7.7: Contour Plots to Compare Results
Figure 7.8: Path Plots to Compare Results
Submodeling
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
/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
...
Example Submodeling Analysis Input
/INPUT,submod,cbdo ! Cut-boundary degree-of-freedom 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
Submodeling
FINISH ! End of interpolation

RESUME ! Resume submodel database (submod.db)
ANTYPE,... ! Analysis type and options
...
/INPUT,submod,cbdo ! Cut-boundary degree-of-freedom 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 degree of freedom 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
material 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:
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 analysis, 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:
Submodeling
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:
Figure 7.11: Equivalent Plastic Strain Distributions in a Submodeling Analysis with Load-History
Dependency
Submodeling
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.
Shell-to-Solid Submodels
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
3D solid model, as shown in this example:
Figure 7.12: 3D 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
Figure 7.13: Node Rotations (p. 142)). 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
Submodeling
node. Interpolated temperatures (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. 142).
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 Figure 7.13: Node Rotations (p. 142). 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
Where to Find Examples
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.
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. 147).)
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
Element Birth and Death
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,
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 degrees of freedom. Inactive
degrees of freedom 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
singularities (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.
Using Birth and Death
• 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.
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
example, if you reduce an element's stiffness to almost zero, but retain its mass, it could result in a
singularity 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 config-
uration.
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 re-
sponses. You may want to constrain inactive degrees of freedom (D, CP, etc.) in some cases to reduce
the number of equations to be solved and to avoid ill-conditioning. Constraining inactive degrees
of freedom 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 degrees of freedom (that is, at nodes not connected
to any active elements). Similarly, you must specifically add nodal loads (if any) to reactivated degrees
of freedom.
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 degrees of freedom (optional)
NSEL,ALL ! Selects ALL nodes
ESEL,ALL ! Selects ALL elements
D,... ! Adds constraints as appropriate
F,... ! Adds nodal loads to active degrees of freedom 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 degrees of freedom
D,... ! Constrains inactive degrees of freedom
Using Birth and Death
...
F,... ! Adds nodal loads as appropriate to active degrees of freedom
DDELE,... ! Deletes constraints from reactivated degrees of freedom
SAVE
SOLVE
8.4.2.3. Using TABLE Type Array Parameters to Control Birth and Death
You can also use TABLE array parameters to control the activation of elements by defining a table
using *DIM and enclosing the table name in % symbols; for example, EALIVE,%tabname%. You
can also use TABLE parameters to control the deactivation of elements using EKILL,%tabname%.
Valid primary variable names are TIME, X, Y, Z and ELEM. Tabular loads can be defined in the
global Cartesian (default) coordinate system, or in a local coordinate system (LOCAL). Only Cartesian,
spherical, and cylindrical coordinate systems are valid. When defining the tables, the primary variables
must be in ascending order in the table indices (as in any table array). See the *DIM command for
more information on defining tables.
An EALIVE table is evaluated for a given element if that element is currently deactivated. If the
evaluation is non-zero, the element is activated and remains activated for the remainder of the
analysis (unless deactivated by EKILL).
An EKILL table is evaluated for a given element if that element is currently activated. If the evaluation
is non-zero, the element is deactivated and remains deactivated for the remainder of the analysis
(unless activated with EALIVE).
Note:
Tables interpolate between primary variables, so interpolations between a zero entry

and a non-zero entry will be non-zero, hence the element will be activated. For instance,
a table of heights (for example, *DIM,tabname,TABLE,n,,,Z) with Z-axis values of 0,10,20
and table values of 0,0,1 leads to all elements between Z = 10 and Z = 20 being activated.
The evaluation takes place at the element centroids for the X, Y, and Z primary variables.
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 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
in the Programmer's Reference.
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. 153),
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
User-Programmable Features and Nonstandard Uses
describing specific programming details. This section presents a general sequence of steps to follow.
The Guide to User-Programmable Features in the Programmer's Reference 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 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 ex-
ample, 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:
Nonstandard Uses of the Program
User-Programmable Features
User-defined elements 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 Programmer's Reference.
User-defined materials Define your own material model. See Customizing Material Behavior and
Subroutines for Customizing Material Behavior in the Programmer's Reference.
User-defined contact Contact elements (CONTA172, CONTA174, CONTA175, CONTA177, and
interfacial behaviors CONTA178) enable you to define your own interfacial behaviors between
surfaces. See Subroutines for Customizing Contact Interfacial Behavior in the
Programmer's Reference.
User real constants Elements COMBIN37, CONTA172, CONTA174, CONTA175, 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 Calculate plastic strains and form the tangent stress-strain matrix at an
integration point based on your own plasticity law.
User creep equation Specify your own creep equation.
User swelling law To account for swelling in an analysis (due to neutron bombardment, for
example), you can write the appropriate swelling law as a user routine.
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
subroutine own program, such as a user-written design optimization algorithm.
User access at the Evaluate results and perform any desired calculations during solution.
beginning and end of
each run solution,
load step, substep,
and equilibrium
iteration
USRSURF116 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
User-Programmable Features and Nonstandard Uses
is employing user-programmable features (p. 151).) 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 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.
Nonstandard Uses of the Program
• If you need to contact Ansys, Inc. Technical Support concerning an analysis involving nonstand-
ard 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 in the Programmer's
Reference.
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 Twin Builder.
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 (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 cor-
responding load vectors.
• If you need an initial condition for your reduced model, you must define the load in the modal ana-
lysis 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 Twin Builder are as follows:
• 10 modes are taken into account.
State-Space Matrices Export
• There are 2 inputs specified in the array parameter ‘inputTab’.
• The inputs labels are defined in the character array parameter ‘inputLab’.
• 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 Twin Builder is used to print out 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
State-Space Matrices Based on Modal Analysis
10.1.2. Example of Reduced Model Generation in Ansys and Usage in Twin

Builder
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 reduced model is generated in Ansys and imported into Twin Builder where global half-
sine acceleration is applied in a transient analysis.

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
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
State-Space Matrices Based on Modal Analysis
The state-space matrices file can be imported in Twin Builder using: Twin Builder Circuit > SubCir-
cuit > Add Mechanical Component
A transient analysis is performed in Twin Builder 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:
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 may be used to model the soil-pile interaction, with the soil data defined in addi-
tional text files. Piles should be modeled using PIPE288 and the surrounding soil environment using
COMBIN39 elements.
Examples of soil-pile interaction macros may be obtained through a Service Request on the Ansys cus-
tomer site.
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 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 Com-
mand (p. 166).
Coupling to External Aeroelastic Analysis of Wind Turbines
3. An aeroelastic solution is then carried out with the foundation effects included through util-
izing the generalized matrices and loading vector derived above. The forces and/or displace-
ments at the supporting structure top node at each solution time are written to a file.
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 spe-
cified 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
substructure 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 elev-
ation 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 Mechan-
ical 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 accel-
eration 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 simultan-
eously and keep exchanging 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
Sequential Coupled Wind Turbine Solution in Mechanical APDL
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.
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 **************************************************************************
Coupling to External Aeroelastic Analysis of Wind Turbines
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
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
Sequential Coupled Wind Turbine Solution in Mechanical APDL
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 interface node. These need to be converted from the aeroelastic output to Mechanical APDL
compatible 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 analysis.
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. 172) for it to be read during
the ocean loading procedure.
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
Applying Ocean Loading from a Hydrodynamic Analysis
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.
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 is composed of 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.
Hydrodynamic Data File Format
* text
where
* keyword to signify that this is a comment line

text description of the model
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)
ihead- wave direction number (position in the direction list)
ing
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. 176).
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
Example Analysis Using Results from a Hydrodynamic Diffraction Analysis
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:
Figure 13.1: Hydrodynamic Diffraction Analysis Pressure Results
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
Example Analysis Using Results from a Hydrodynamic Diffraction Analysis
! 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
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

ANSYS Mechanical APDL 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 Advanced Analysis Guide

Uploaded by

Copyright:

Available Formats

Advanced Analysis Guide

ANSYS, Inc. Release 2022 R2

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

U.S. Government Rights

Published in the U.S.A.

4.2.5. Applying Initial Creep Strain ................................................................................................... 47

5.4.4.2. Input for the Analysis ..................................................................................................... 98

8.2. Understanding Element Birth and Death ....................................................................................... 145

The following 2D to 3D analysis topics are available:

1.1. Benefits of 2D to 3D Analysis

1.2. 2D to 3D Analysis Requirements and Limitations

Support Category Requirements

• CONTA174 with any of the following valid KEYOPT settings:

Contact pair • Rigid-to-flexible[c]

Support Category Requirements

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

Loads and • Displacements, forces, pressures, and nodal temperatures

• Tabular pressures that are functions of time only[h]

• Fluid-penetration loads applied to contact elements (SFE)[h][i]

• SFCONTROL not supported

Files • .rdb, .rst, .ldhi, .ist, and .cdb.

1.3. Understanding the 2D to 3D Analysis Process

2. Initiate (p. 7) the 2D to 3D analysis process.

6. Continue as a 3D analysis (p. 12) via a multiframe restart.

• The initial-state values saved after Step 5 (INISTATE,WRITE).

• The .cdb file that includes the 3D mesh.

1.3.1. Understanding the 2D to 3D Analysis Process Flow

Figure 1.1: 2D to 3D Process Flow

1.3.2. Key Commands Used in a 2D to 3D Analysis

Command Description 2D to 3D Analysis Comments

Command Description 2D to 3D Analysis Comments

1.4. Performing a 2D to 3D Analysis

1.4.1. Step 1: Determine the Substep to Initiate

1.4.2. Step 2: Initiate the 2D to 3D Analysis

1. Clear the database (/CLEAR,NOSTART).

2. Reenter the solution processor (/SOLU).

Result: The program updates the geometry to the deformed configuration.

Proceed to Step 3: Extrude the 2D Mesh to a New 3D Mesh (p. 7).

1.4.3. Step 3: Extrude the 2D Mesh to a New 3D Mesh

Figure 1.2: Axisymmetric to 3D Solid Extrusion

Figure 1.3: 2D Plane Strain to 3D Solid Extrusion

1.4.3.1. Adding Contact Pairs

Rigid-to-flexible contact-pair limitations:

1.4.5.1. Example: Solution Variable Mapping and Rebalancing

PROBLEM DIMENSIONALITY. . . . . . . . . . . . .3D

*** LOAD STEP 1 SUBSTEP 11 COMPLETED. CUM ITER = 23

*** TIME = 1.00000 REBALANCE FACTOR = 1.00000

MAP2DTO3D,SOLV IS DONE SUCCESSFULLY IN 1 SUBSTEPS FOR 2D

In this example, the 2D to 3D analysis occurred at TIME = 1.

1.4.5.2. Mapped Solution Results in Axisymmetric Cases

1.4.5.3. Mapped Solution Results in Plane Strain Cases

1.4.5.4. Rebalancing Considerations

Rebalancing difficulties can occur if the extruded 3D model is not:

• a full circle in the hoop direction (axisymmetric case), or

• of sufficient length in the global Z direction (plane strain case).

1.4.5.4.1. Axisymmetric Rebalancing Cases with Reinforcing Elements

• the torsion degree of freedom is not enabled.

1.4.5.4.2. Large Penetration and Rebalancing

*WARNING*: Initial penetration 4.28926118 may be too large

If you encounter such a message during rebalancing, consider these remedies:

1.4.5.5. Adding Contact Pairs

1.4.5.6. Reviewing Results After Exiting Mechanical APDL

For /GRAPHICS,FULL, reinforcing element results are not included.

WARNING: Initial penetration 4.28926118 may be too large