15.11.2012 Views

Mechanical APDL Basic Analysis Guide - Ansys

Mechanical APDL Basic Analysis Guide - Ansys

Mechanical APDL Basic Analysis Guide - Ansys

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

5.9.1.1.1. Multiframe Restart Limitations<br />

Multiframe restart in nonlinear static and full transient analyses has the following limitations:<br />

• It does not support the KUSE command. A new stiffness matrix and the related .LN22 file will be regenerated.<br />

• The .Rnnn file does not save the EKILL and EALIVE commands. If EKILL or EALIVE commands are required<br />

in the restarted session, you must reissue these commands.<br />

• The .RDB file saves only the database information available at the first substep of the first load step.<br />

If you input other information after the first load step and need that information for the restart, you<br />

must input this information in the restart session. This situation often occurs when parameters are used<br />

(<strong>APDL</strong>). You must use PARSAV to save the parameters during the initial run and use PARRES to restore<br />

them in the restart. The situation also occurs when you want to change element REAL constants values.<br />

Reissue the R command during the restart session in this case.<br />

• You cannot restart a job at the equation solver level (for example, the PCG iteration level). The job can<br />

only be restarted at a substep level (either transient or Newton-Raphson loop).<br />

• You cannot restart an analysis with a load step number larger than 9999.<br />

• Multiframe restart does not support the ENDSTEP option of ANTYPE when the arc-length method is<br />

employed.<br />

• All loading and boundary conditions are stored in the Jobname.LDHI file; therefore, upon restart, removing<br />

or deleting solid modeling loading and boundary conditions will not result in the removal of<br />

these conditions from the finite element model. You must remove these conditions directly from nodes<br />

and elements.<br />

• You cannot restart an analysis if the job was terminated by a Jobname.ABT file in the GUI.<br />

• You cannot save the database information (SAVE) before solving (SOLVE).<br />

• You cannot nest *DO loops into each other in restart.<br />

5.9.1.2. Multiframe Restart Procedure<br />

Use the following procedure to restart an analysis:<br />

1. Enter the ANSYS program and specify the same jobname that was used in the initial run. To do so, issue<br />

the /FILNAME command (Utility Menu> File> Change Jobname). Enter the SOLUTION processor using<br />

/SOLU (Main Menu> Solution).<br />

2. Determine the load step and substep at which to restart by issuing RESCONTROL, FILE_SUMMARY.<br />

This command will print the substep and load step information for all .Rnnn files in the current directory.<br />

3. Resume the database file and indicate that this is a restart analysis by issuing ANTYPE,,REST,LDSTEP,SUB-<br />

STEP,Action (Main Menu> Solution> Restart).<br />

4. Specify revised or additional loads as needed. Be sure to take whatever corrective action is necessary<br />

if you are restarting from a convergence failure.<br />

5. Initiate the restart solution by issuing the SOLVE command. (See Obtaining the Solution (p. 112) for<br />

details.) You must issue the SOLVE command when taking any restart action, including ENDSTEP or<br />

RSTCREATE.<br />

6. Postprocess as desired, then exit the ANSYS program.<br />

Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information<br />

of ANSYS, Inc. and its subsidiaries and affiliates.<br />

5.9.1. Multiframe Restart<br />

121

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!