- Mapdl.rescontrol(action='', ldstep='', frequency='', maxfiles='', maxtotalfiles='', filetype='', **kwargs)#
Controls file writing for multiframe restarts.
APDL Command: RESCONTROL
Command action. Valid options are:
Issuing the command specifies how frequently the
.Xnnnrestart files are written for a load step (default).
Issuing the command prints the substep and load step information for all
.Xnnnfiles for the current jobname in the current directory. If this option is specified, all other arguments are ignored.
Issuing the command lists the current status in the tables of restart controls specified previously by RESCONTROL. If this option is specified, all other arguments are ignored.
Issuing the command cleans up some of the restart files after a Distributed ANSYS solution. The host process will not have the following files in the working directory at the end of the run:
`, `.LDHI. The slave processes will not have the following files in the working directory at the end of the run:
.RTH, etc.). Some of the restart files are never written, some are removed upon leaving
/SOLU(for example, upon FINISH), and some are removed upon exiting the program.
This option is useful for cleaning up files written by all of the Distributed ANSYS processes, particularly when you know that these restart files will not be needed later on. If this option is specified, all other arguments are ignored.
If this option is used in shared-memory parallel ANSYS, most of the restart files in the working directory are removed. It has the same effect as issuing
Issuing the command specifies the same actions as Action = DEFINE. However, this option is intended for linear static applications. For a linear static analysis, the restart capability is normally not needed. However, it is typically needed when a subsequent linear perturbation analysis is desired. By default, none of the restart files are written for a linear static analysis.
Delete the restart control specification corresponding to the
Ldsteplabel on a previous
Specifies how the
.Xnnnfiles are written for the specified load steps. This option also affects how often the load history information is written to the
.Xnnnfiles at the same substep Frequency for all load steps; write the load history information to the
.LDHIfile for all load steps.
.Xnnnfiles for the last load step only; write load history information to the
.LDHIfile for the last load step only. This option is the default for nonlinear static and full transient analyses. The remaining arguments are ignored.
Number that indicates how often the
.Xnnnfile is written.
Input a positive number to write the
.Xnnnfiles at the substep
Frequencyindicated only for load step N. Other load steps will be written at the default substep frequency or at a frequency defined by a previous
RESCONTROLspecification. Load history information is written to the
.LDHIfile only for load steps N.
Specifying a negative number (-N) to write the
.Xnnnfiles for every Nth load step at the specified substep Frequency. The load history information is written to the
.LDHIfile every Nth load step. This option is suitable for restart applications in which more than a few hundred load steps are required. Compared to the ALL and positive N options, it can save disk space since the
.LDHIfile is smaller and fewer
.Xnnnfiles are written.
If Ldstep = -N, all other Ldstep options specified by
RESCONTROLare ignored and the program follows the -N option (write load history information every Nth load step). If you want to change this pattern, issue
RESCONTROL,DELETE, -Nand then issue another
RESCONTROLcommand with the desired Ldstep option.
No multiframe restart files (
.RDB[restart database file],
.LDHI[load history file],
.Xnnn) are created. This option is the default for mode-superposition analyses. The remaining arguments are ignored.
For nonlinear static, linear static, and full transient analyses, this option allows a restart to be done at the last or abort point using the same procedure as in ANSYS 5.5 or earlier (using the
Frequency at which the
.Xnnnfiles are written at the substep level.
Do not write any
.Xnnnfiles for this load step.
.Xnnnfiles for the last substep of the load step only (default for nonlinear static and full transient analyses).
Nis positive, write the
.Xnnnfile every Nth substep of a load step. If
Nis negative, write
.Xnnnfiles within a load step.
In nonlinear static and full transient analyses, negative
Nis valid only when
AUTOTS,ON. In mode-superposition analyses, negative
Nis always valid.
Maximum number of
.Xnnnfiles to save for Ldstep.
.Xnnnfiles (default). The total maximum number of
.Xnnnfiles for one run is 999. If this number is reached before the analysis is complete, the program will reset the
.Xnnnfile numbering back to 1 and continue to write
.Xnnnfiles; the program keeps the newest 999 restart files and overwrites the oldest restart files.
Do not overwrite any existing
.Xnnnfiles. The total maximum number of
.Xnnnfiles for one run is 999. If this number is reached before the analysis is complete, the analysis continues but no longer writes any
Maximum number of
.xnnnfiles to keep for each load step. When
N.xnnnfiles have been written for a load step, the program overwrites the first
.xnnnfile of that load step for subsequent substeps.
Nmust be <= 999. If a total of 999 restart files is reached before the analysis is complete, the analysis continues but writes no additional
Total number of restart files to keep.
Default = 999for
.xnnnfiles and 99 for
.rdnnfiles. This option is valid only when
MAXFILES= -1 (default). Valid
maxtotalfilesvalues are 1 through 999 for
.xnnnfiles, and 1 through 99 for
When the total number of restart files written exceeds
maxtotalfiles, the program resets the
.rdnnfile numbering back to 1 and continues to write
.rdnnfiles. The newest files are retained and the oldest files are overwritten.
maxtotalfilesvalue specified applies to all subsequent load steps. To reset it to the default, reissue the command with
maxtotalfiles= 0 or some negative value.
maxtotalfilesis set to different values at different load steps, and if the value of
maxtotalfilesspecified in the prior load step is larger than that of the current load step, the program can only overwrite the current number of maximum restart files up to the number
maxtotalfilescurrently specified (which is smaller than the previous number).
The recommended way to control the maximum number of restart files is to specify
maxtotalfilesat the first load step and not vary it in subsequent load steps. Also,
maxtotalfilesis best used when Ldstep = -N or ALL.
The type of restart file to be controlled by this command. Valid only when Action = DEFINE:
.rdnnremeshing database files. Needed only for a nonlinear mesh adaptivity analysis.
RESCONTROLcommand is not issued during a structural analysis, the
.LDHIfiles are written as described in Restarting an Analysis.
For nonlinear static and full transient analysis:
The default behavior is multiframe restart:
.xnnnfile is written at the last substep of the last load step. An
.rnnnfile is also written at the iteration prior to the abort point of the run if a
jobname.abtfile was used (or the Stop button was pressed in the GUI), or if the job terminated because of a failure to reach convergence or some other solution error. No information at the aborted substep is saved to the
For nonlinear mesh adaptivity analysis:
The default behavior for
.rdnnfiles written is:
.rdnnfile is written at the last remesh of every load step by default. The
.rnnnfiles interact with each other. Generally,
.rdnnfile writing is superior to that of
.rnnnfile writing. For example, if no RESCONTROL,DEFINE command is issued, the default behavior is that both
.rnnnfiles are written at the last occurrence of every load step (equivalent to
RESCONTROLsets up the restart parameters for a multiframe restart, enabling you to restart an analysis from any load step and substep for which there is an
.xnnnfile. You can perform a multiframe restart for static and transient (full or mode-superposition method) analyses only. For more information about multiframe restarts and descriptions of the contents of the files used, see Restarting an Analysis in the Basic Analysis Guide.
Multiframe restart files are generically indicated here as
.xnnnfiles. They correspond to .rnnn files for nonlinear static and full transient analyses, and
.mnnnfiles for mode-superposition analyses. Remeshing database files are indicated as
.rdnnfiles. This type of restart file is needed only after remeshing during a nonlinear mesh adaptivity analysis. When
Action = DEFINE, the specified Filetype determines the type of file (
.rdnn) controlled by this command.
Number of Restart Files Allowed
The total number of restart files for any analysis cannot exceed 999 (for example,
jobname.r999). The total number of remeshing database files cannot exceed 99 (for example,
Considerations for Nonlinear Mesh Adaptivity Analysis
To control both
.rdnnfile writing (
Filetype = XNNNand
Filetype = RDNN, respectively), separate
RESCONTROLcommands are necessary.
Action = NORESTARTand
Ldstep = NONEare not valid and will cause the analysis to fail.
Ldstep = -Nis not valid for controlling
Limiting the Number of Files Saved
If you have many substeps for each load step and are writing
.xnnnfiles frequently, you may want to set
maxfilesto limit the number of
.xnnnfiles saved, as they can fill your disk quickly. You can specify
Frequencyfor individual load steps. These arguments take on the default value or the value defined by
RESCONTROL,,ALL,Frequency,maxfilesif they are not explicitly defined for a specific load step. When
.xnnnfiles are written over many load steps, you may want to further limit the number of
.xnnnfiles by setting
Maximum Number of Load Steps
You can specify a maximum of ten load steps; that is, you can issue the
RESCONTROL,,Ncommand a maximum of ten times. Specified load steps cannot be changed in a restart.
Specifying Ldstep = LAST or Ldstep = -N
The program accepts only one occurrence of
Ldstep = LAST. If you issue
RESCONTROL,,LAST,Frequency,maxfilesmultiple times, the last specification overwrites the previous one. The program accepts only one occurrence of
RESCONTROLwith a negative
Nis a negative number). If you issue
RESCONTROLmultiple times with a negative
Ldstepvalue, the last specification overwrites the previous one.