Mechanical APDL Basic Analysis Guide - Ansys
Mechanical APDL Basic Analysis Guide - Ansys Mechanical APDL Basic Analysis Guide - Ansys
Chapter 5: Solution If the files Jobname.LDHI and Jobname.RDB exist, the ANTYPE,,REST command will cause ANSYS to do the following: • Resume the database Jobname.RDB • Rebuild the loading and boundary conditions from the Jobname.LDHI file • Rebuild the ANSYS solution commands and status from the .Rnnn file, or from the .Mnnn file in the case of a mode-superposition transient analysis. At this point, you can enter other commands to overwrite input restored by the ANTYPE command. Note The loading and boundary conditions restored from the Jobname.LDHI are for the FE mesh. The solid model loading and boundary conditions are not stored on the Jobname.LDHI. After the job is restarted, the files are affected in the following ways: • The .RDB file is unchanged. • All information for load steps and substeps past the restart point is deleted from the .LDHI file. Information for each new load step is then appended to the file. • All of the .Rnnn or .Mnnn files that have load steps and substeps earlier than the restart point will be kept unchanged. Those files containing load steps and substeps beyond the restart point will be deleted before the restart solution begins in order to prevent file conflicts. • For nonlinear static and full transient analyses, the results file .RST is updated according to the restart. All results from load steps and substeps later than the restart point are deleted from the file to prevent conflicts, and new information from the solution is appended to the end of the results file. • For a mode-superposition transient analysis, the reduced displacements file .RDSP is updated according to the restart. All results from load steps and substeps later than the restart point are deleted from the file to prevent conflicts, and new information from the solution is appended to the end of the reduced displacements file. When a job is started from the beginning again (first substep, first load step), all of the restart files (.RDB, .LDHI, and .Rnnnor .Mnnn) in the current directory for the current jobname will be deleted before the new solution begins. You can issue a ANTYPE,,REST,LDSTEP,SUBSTEP,RSTCREATE command to create a results file for a particular load step and substep of an analysis. Use the ANTYPE command with the OUTRES command to write the results. A RSTCREATE session will not update or delete any of the restart files, allowing you to use RSTCREATE for any number of saved points in a session. The RSTCREATE option is not supported in mode-superposition analysis. The sample input listing below shows how to create a results file for a particular substep in an analysis. ! Restart run: /solu antype,,rest,1,3,rstcreate !Create a results file from load !step 1, substep 3 outres,all,all !Store everything into the results file outpr,all,all !Optional for printed output solve !Execute the results file creation finish /post1 set,,1,3 !Get results from load step 1, !substep 3 122 Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
prnsol finish 5.9.2. VT Accelerator Re-run Once you have performed an analysis using the VT Accelerator option [STAOPT,VT or TRNOPT,VT], you may rerun the analysis; the number of iterations required to obtain the solution for all load steps and substeps will be greatly reduced. You can make the following types of changes to the model before rerunning: • Modified or added/removed loads (constraints may not be changed, although their value may be modified) • Materials and material properties • Section and real constants • Geometry, although the mesh connectivity must remain the same (i.e. the mesh may be morphed) VT Accelerator allows you to effectively perform parametric studies of nonlinear and transient analyses in a cost-effective manner (as well as to quickly re-run the model, which is typically necessary to get a nonlinear model operational). 5.9.2.1. VT Accelerator Re-run Requirements When rerunning a VT Accelerator analysis, the following files must be available from the initial run: • Jobname.DB – the database file. It may be modified as listed in the previous section. • Jobname.ESAV – Element saved data • Jobname.RSX – Variational Technology results file 5.9.2.2. VT Accelerator Re-run Procedure The procedure for rerunning a VT Accelerator analysis is as follows: 1. Enter the ANSYS program and specify the same jobname that was used in the initial run with /FILNAME (Utility Menu> File> Change Jobname). 2. Resume the database file using RESUME (Utility Menu> File> Resume Jobname.db) and make any modifications to the data. 3. Enter the SOLUTION processor using /SOLU (Main Menu> Solution), and indicate that this is a restart analysis by issuing ANTYPE,,VTREST (Main Menu> Solution> Restart). 4. Because you are re–running the analysis, you must reset the load steps and loads. If resuming a database saved after the first load step of the initial run, you will need to delete the loads and redefine the loads from the first load step. 5. Initiate the restart solution by issuing the SOLVE command. See Obtaining the Solution (p. 112) for details. 6. Repeat steps 4, 5, and 6 for the additional load steps, if any. 5.10. Exercising Partial Solution Steps When you initiate a solution, the ANSYS program goes through a predefined series of steps to calculate the solution; it formulates element matrices, triangularizes matrices, and so on. Another SOLUTION command, PSOLVE, (Main Menu> Solution> Partial Solu) allows you to exercise each such step individually, completing just a portion of the solution sequence each time. For example, you can stop at the element matrix formu- Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates. 5.10. Exercising Partial Solution Steps 123
- 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 and 128: Figure 5.2 PGR File Options From th
- Page 129 and 130: GUI: Main Menu> Solution> Current L
- 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: 5.9.1.1.1. Multiframe Restart Limit
- 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
- Page 179 and 180: Write Results - You can use the dat
- Page 181 and 182: NOTE: When you append data to your
- Page 183 and 184: EMF - Windows Enhanced Metafile For
- Page 185 and 186: Figure 7.20 The PGR File Options Di
- Page 187 and 188: 7.4.8. Comparing Nodal Solutions Fr
Chapter 5: Solution<br />
If the files Jobname.LDHI and Jobname.RDB exist, the ANTYPE,,REST command will cause ANSYS to do<br />
the following:<br />
• Resume the database Jobname.RDB<br />
• Rebuild the loading and boundary conditions from the Jobname.LDHI file<br />
• Rebuild the ANSYS solution commands and status from the .Rnnn file, or from the .Mnnn file in the<br />
case of a mode-superposition transient analysis.<br />
At this point, you can enter other commands to overwrite input restored by the ANTYPE command.<br />
Note<br />
The loading and boundary conditions restored from the Jobname.LDHI are for the FE mesh.<br />
The solid model loading and boundary conditions are not stored on the Jobname.LDHI.<br />
After the job is restarted, the files are affected in the following ways:<br />
• The .RDB file is unchanged.<br />
• All information for load steps and substeps past the restart point is deleted from the .LDHI file. Information<br />
for each new load step is then appended to the file.<br />
• All of the .Rnnn or .Mnnn files that have load steps and substeps earlier than the restart point will be<br />
kept unchanged. Those files containing load steps and substeps beyond the restart point will be deleted<br />
before the restart solution begins in order to prevent file conflicts.<br />
• For nonlinear static and full transient analyses, the results file .RST is updated according to the restart.<br />
All results from load steps and substeps later than the restart point are deleted from the file to prevent<br />
conflicts, and new information from the solution is appended to the end of the results file.<br />
• For a mode-superposition transient analysis, the reduced displacements file .RDSP is updated according<br />
to the restart. All results from load steps and substeps later than the restart point are deleted from the<br />
file to prevent conflicts, and new information from the solution is appended to the end of the reduced<br />
displacements file.<br />
When a job is started from the beginning again (first substep, first load step), all of the restart files (.RDB,<br />
.LDHI, and .Rnnnor .Mnnn) in the current directory for the current jobname will be deleted before the<br />
new solution begins.<br />
You can issue a ANTYPE,,REST,LDSTEP,SUBSTEP,RSTCREATE command to create a results file for a particular<br />
load step and substep of an analysis. Use the ANTYPE command with the OUTRES command to write the<br />
results. A RSTCREATE session will not update or delete any of the restart files, allowing you to use RSTCREATE<br />
for any number of saved points in a session. The RSTCREATE option is not supported in mode-superposition<br />
analysis.<br />
The sample input listing below shows how to create a results file for a particular substep in an analysis.<br />
! Restart run:<br />
/solu<br />
antype,,rest,1,3,rstcreate !Create a results file from load<br />
!step 1, substep 3<br />
outres,all,all !Store everything into the results file<br />
outpr,all,all !Optional for printed output<br />
solve !Execute the results file creation<br />
finish<br />
/post1<br />
set,,1,3 !Get results from load step 1,<br />
!substep 3<br />
122<br />
Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information<br />
of ANSYS, Inc. and its subsidiaries and affiliates.