Mechanical APDL Basic Analysis Guide - Ansys
Mechanical APDL Basic Analysis Guide - Ansys Mechanical APDL Basic Analysis Guide - Ansys
Chapter 5: Solution • Thermal Strain • Creep Strain • Thermal Gradient • Thermal Flux • Electric Field • Electric Flux Density • Magnetic Field Intensity • Magnetic Flux Density • Magnetic Forces • Pressure Gradients • Body Temperatures • Densities for Topological Optimization Data to save on file - From this location, you can designate whether to store averaged data or averaged plus unaveraged nodal data. You can also specify whether to use the surface data or the surface data in conjunction with the interior data. Averaged data is used with the PLNSOL and PRNSOL commands. Unaveraged data is used with the PLESOL and PRESOL commands. The averaging scheme used for the “Surface and Interior data” selection will yield stress contours that are similar to those obtained in the Full Model Graphics mode or in PowerGraphics with the AVRES,,FULL command option. The data obtained with the “Surface data only selection will be the same as the data obtained using PowerGraphics with the default AVRES command option (using only the exterior element faces). Interior data can be obtained only when nodal data averaging is enabled. This function cannot be changed if you plan to append your PGR file. Interior model data - This selection actually saves the interior results data for subsequent displays using slicing, capping, vector display, or isosurface display techniques (see the /TYPE, /CTYPE, and PLVECT commands). The data that is saved when this item is selected can be displayed on the model or ported to data tables and listings. This function cannot be changed if you plan to append your PGR file. Stresses can only be displayed in the coordinate system that was active when the PGR file was written. If you wish to use the results viewer to view stresses in other coordinate system displays, you must reload your results file (*.RST, *.RFL, *.RTH, *.RMG, etc.) in POST1, in that coordinate system. 5.5.3. PGR Commands The ANSYS PGR file uses the following commands to create and access the PGR data: Solution Commands PGWRITE, POUTRES, and AVRES. Postprocessing Commands POUTRES, PGSAVE, PGRAPH, PGRSET, PLESOL, PLNSOL, PLTRAC, and PLVECT. 5.6. Obtaining the Solution To initiate the solution, use one of the following: 112 Command(s): SOLVE Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
GUI: Main Menu> Solution> Current LS or Run FLOTRAN Because the solution phase generally requires more computer resources that the other phases of an analysis, it is better suited to batch (background) mode than interactive mode. The solver writes output to the output file (Jobname.OUT) and the results file. If you run the solution interactively, the output "file" is actually your screen (window). By using one of the following before issuing SOLVE, you can divert the output to a file instead of the screen: Command(s): /OUTPUT GUI: Utility Menu> File> Switch Output to> File or Output Window Data written to the output file consist of the following: • Load summary information • Mass and moments of inertia of the model • Solution summary information • A final closing banner that gives total CPU time and elapsed time. • Data requested by the OUTPR output control command or its GUI counterpart In interactive mode, much of the output is suppressed. The results file (.RST, .RTH, .RMG, or .RFL) contains all results data in binary form, which you can then review in the postprocessors. Another useful file produced during solution is Jobname.STAT, which gives the status of the solution. You can use this file to monitor an analysis while it is running. It is particularly useful in iterative analyses such as nonlinear and transient analyses. The SOLVE command calculates the solution for the load step data currently in the database. 5.7. Solving Multiple Load Steps There are three ways to define and solve multiple load steps: • Multiple SOLVE method • Load step file method • Array parameter method. 5.7.1. Using the Multiple SOLVE Method This method is the most straightforward. It involves issuing the SOLVE command after each load step is defined. The main disadvantage, for interactive use, is that you have to wait for the solution to be completed before defining the next load step. A typical command stream for the multiple SOLVE method is shown below: /SOLU ... ! Load step 1: D,... SF,... 0 SOLVE ! Solution for load step 1 ! Load step 2 F,... SF,... ... Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates. 5.7.1. Using the Multiple SOLVE Method 113
- Page 77 and 78: Command GUI Menu Paths Main Menu> S
- Page 79 and 80: ! Load Step 1: D, ... ! Loads SF, .
- Page 81 and 82: Modeling> Create> Elements> Auto Nu
- Page 83 and 84: Figure 2.22 Pretension Section Samp
- Page 85 and 86: cylind,0.35,1, 0.75,1, 0,180 wpstyl
- Page 87 and 88: 11. Select Utility Menu> PlotCtrls>
- Page 89 and 90: 24. Select Utility Menu> Plot> Comp
- Page 91 and 92: Chapter 3: Using the Function Tool
- Page 93 and 94: Hint: A common error is a divide-by
- Page 95 and 96: 3.3. Using the Function Loader When
- Page 97 and 98: 2. Define the convection boundary c
- Page 99 and 100: 7. Optional: Enter comments for thi
- Page 101 and 102: 3.6.1. Graphing a Function From the
- Page 103 and 104: Chapter 4: Initial State The term i
- Page 105 and 106: inis,defi,,,1,,100,200,150 inis,def
- Page 107 and 108: applies an equal stress of SX = 100
- Page 109 and 110: 4.7.2. Example: Initial Stress Prob
- Page 111 and 112: inis,defi,all,all,all,all,0.1,,, in
- Page 113 and 114: Chapter 5: Solution In the solution
- Page 115 and 116: Solver Typical Applications * In to
- Page 117 and 118: used. Running the distributed spars
- Page 119 and 120: With all iterative solvers, be part
- Page 121 and 122: 5.3.3. Disk Space (I/O) and Postpro
- Page 123 and 124: If your analysis is either static o
- Page 125 and 126: Note Whether you make changes to on
- Page 127: Figure 5.2 PGR File Options From th
- Page 131 and 132: Figure 5.3 Examples of Time-Varying
- Page 133 and 134: Requirements for Performing an Anal
- Page 135 and 136: *dim,temtbl,table,4,1,,time ! Defin
- Page 137 and 138: 5.9.1.1.1. Multiframe Restart Limit
- Page 139 and 140: prnsol finish 5.9.2. VT Accelerator
- Page 141 and 142: 5.12. Stopping Solution After Matri
- Page 143 and 144: Chapter 6: An Overview of Postproce
- Page 145 and 146: each element. Derived data are also
- Page 147 and 148: Chapter 7: The General Postprocesso
- Page 149 and 150: Although not required for postproce
- Page 151 and 152: The ETABLE command documentation li
- Page 153 and 154: • Path plots • Reaction force d
- Page 155 and 156: The PLETAB command contours data st
- Page 157 and 158: PLDISP,1 ! Deformed shape superimpo
- Page 159 and 160: 7.2.1.6. Particle Flow and Charged
- Page 161 and 162: • Particle flow traces occasional
- Page 163 and 164: The surfaces you create fall into t
- Page 165 and 166: You can opt to archive all defined
- Page 167 and 168: 19 41.811 51.777 .00000E+00 -66.760
- Page 169 and 170: Sample PRETAB and SSUM Output *****
- Page 171 and 172: 7.2.5. Mapping Results onto a Path
- Page 173 and 174: Command(s): PDEF GUI: Main Menu> Ge
- Page 175 and 176: To retrieve path information from a
- Page 177 and 178: 7.2.6. Estimating Solution Error On
Chapter 5: Solution<br />
• Thermal Strain<br />
• Creep Strain<br />
• Thermal Gradient<br />
• Thermal Flux<br />
• Electric Field<br />
• Electric Flux Density<br />
• Magnetic Field Intensity<br />
• Magnetic Flux Density<br />
• Magnetic Forces<br />
• Pressure Gradients<br />
• Body Temperatures<br />
• Densities for Topological Optimization<br />
Data to save on file - From this location, you can designate whether to store averaged data or averaged<br />
plus unaveraged nodal data. You can also specify whether to use the surface data or the surface data in<br />
conjunction with the interior data. Averaged data is used with the PLNSOL and PRNSOL commands. Unaveraged<br />
data is used with the PLESOL and PRESOL commands.<br />
The averaging scheme used for the “Surface and Interior data” selection will yield stress contours that are<br />
similar to those obtained in the Full Model Graphics mode or in PowerGraphics with the AVRES,,FULL<br />
command option. The data obtained with the “Surface data only selection will be the same as the data obtained<br />
using PowerGraphics with the default AVRES command option (using only the exterior element<br />
faces). Interior data can be obtained only when nodal data averaging is enabled. This function cannot be<br />
changed if you plan to append your PGR file.<br />
Interior model data - This selection actually saves the interior results data for subsequent displays using<br />
slicing, capping, vector display, or isosurface display techniques (see the /TYPE, /CTYPE, and PLVECT commands).<br />
The data that is saved when this item is selected can be displayed on the model or ported to data<br />
tables and listings. This function cannot be changed if you plan to append your PGR file.<br />
Stresses can only be displayed in the coordinate system that was active when the PGR file was written. If<br />
you wish to use the results viewer to view stresses in other coordinate system displays, you must reload<br />
your results file (*.RST, *.RFL, *.RTH, *.RMG, etc.) in POST1, in that coordinate system.<br />
5.5.3. PGR Commands<br />
The ANSYS PGR file uses the following commands to create and access the PGR data:<br />
Solution Commands<br />
PGWRITE, POUTRES, and AVRES.<br />
Postprocessing Commands<br />
POUTRES, PGSAVE, PGRAPH, PGRSET, PLESOL, PLNSOL, PLTRAC, and PLVECT.<br />
5.6. Obtaining the Solution<br />
To initiate the solution, use one of the following:<br />
112<br />
Command(s): SOLVE<br />
Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information<br />
of ANSYS, Inc. and its subsidiaries and affiliates.