KB-2026003: How to Manage Restart Files and Restart a Radioss Simulation

How to Manage Restart Files and Restart a Radioss Simulation

1. Overview

Radioss provides restart and checkpoint capabilities that allow engineers to save simulation states, stop ongoing analyses, and resume simulations from previously saved time steps.

This guide explains how to:

  • Configure automatic restart file generation.

  • Stop a Radioss simulation gracefully while generating restart files.

  • Restart an analysis from a previously saved time step.

  • Modify selected simulation parameters when performing a restart.

2. Automatic Restart File Generation

By default, at the end of every Radioss run, a restart file is automatically generated with the following naming convention:

runname_0001_0001.rst

Configuring Multiple Restart Files

If multiple restart files are required during the analysis, add the following option to the Radioss Engine file:

/RFILE/n

Where:

  • n defines the number of restart file sets to be stored.

  • Radioss writes restart files cyclically.

  • Once the specified number of restart file sets is reached, the oldest files are overwritten by newer ones.

Identifying the Latest Restart File

To identify the latest restart file generated during the simulation, review the Engine output (.out) file.

3. How to Stop a Radioss Simulation Gracefully

When a simulation needs to be stopped before completion, it is important to ensure that the required restart or checkpoint files are generated correctly.

Recommended method: Control File (C-File)

The recommended approach is to use the Radioss Control File (C-File) option.

Using the C-File allows the simulation to stop gracefully while ensuring that the required restart/checkpoint files are written correctly.

For detailed information, refer to the official documentation:

Radioss Control File (C-File)

4. How to Restart a Radioss Simulation

A Radioss simulation can be restarted from a previously stopped time step using either of the following methods:

  1. Restart using an additional Engine file.

  2. Restart using a checkpoint file (CHECK_FILE).


4.1 Restart Using a Second Engine File

This method is useful when you want to continue an analysis using a new Engine file.

Procedure:

  1. Create a new Engine file.

  2. Modify the /RUN card to increment the run number.

  3. Ensure that the run name remains consistent with the original simulation.

Example:

Original run:

/RUN/TensileTest/1

Restart run:

/RUN/TensileTest/2

Where:

  • TensileTest is the simulation run name.

  • 2 indicates the restart run number.

The restart analysis will continue from the latest available restart file.

4.2 Restart Using a Checkpoint File (CHECK_FILE)

If no modifications to the Engine file are required, the simulation can be restarted using a checkpoint file named:

CHECK_FILE

The file should contain the following entry:

/RERUN/RunName/RunNumber

For example:

/RERUN/TensileTest/2

The CHECK_FILE can be created in two ways:

Method 1: Automatic Creation

The checkpoint file can be generated automatically by stopping the simulation through Altair Compute Console (ACC) using the STOP and CHKPT options.

Method 2: Manual Creation

To create the CHECK_FILE manually:

  1. Copy the original Engine file.

  2. Rename the copied file as CHECK_FILE.

  3. Replace the /RUN line with /RERUN.

  4. Delete all other lines from the file.

4.3 Submitting a Checkpoint Restart

When restarting through Altair Compute Console or a Radioss script:

  • Use the same processor settings as the original simulation.

  • Include the -checkpoint option.

Example:

radioss -np 4 -checkpoint tensileTest_0000.rad

If running Radioss directly using executables, provide the CHECK_FILE as input to the Engine executable.

5. What Parameters Can Be Modified During a Restart?

Radioss restart functionality allows selected simulation parameters to be modified without necessarily restarting the entire analysis from the beginning.

The following features can be altered using the restart option:

Parameter / Feature Description
Gravity and pre-tension Initialize gravity or pre-tension before a simulation
Output frequency Change the write frequency of animation files (/ANIM/DT, /H3D/DT), time history (/TFILE), and restart files (/RFILE)
Time step control Modify time step control options using /DT/Keyword
System damping Modify damping using /DAMP, /DYREL, or /KEREL
Boundary conditions Add or remove boundary conditions using /BCS/Keyword
Initial conditions Define initial conditions using /INIV/Keyword
Element deletion Remove elements using /DEL/Eltyp
Rigid body control Turn rigid bodies on or off using /RBODY/Keyword2

6. Quick Reference

Requirement Recommended approach
Generate multiple restart files Add /RFILE/n to the Engine file
Identify the latest restart file Review the Engine .out file
Stop a simulation gracefully Use the Control File (C-File)
Restart with a modified Engine file Create a second Engine file and increment the /RUN number
Restart without modifying the Engine file Use CHECK_FILE
Generate a checkpoint automatically Use ACC with STOP and CHKPT options
Generate a checkpoint manually Create CHECK_FILE using the /RERUN entry

7. References

Tags
KB2026002: How to model condensation
KB-2026004: How to Apply Temperature Loads in OptiStruct – Understanding Temperature Subcase Options