Replaying an Abaqus/CAE session

Almost every operation that you perform in Abaqus/CAE is recorded automatically in the replay file (abaqus.rpy) in the form of Abaqus Scripting Interface commands. Executing the replay file is equivalent to replaying the original sequence of operations including any redundant procedures and any mistakes and subsequent corrections that you made. The replay file also includes canvas operations, such as creating a new viewport.

Abaqus/CAE retains the five most recent versions of the replay file. The most recent version of the replay file is called abaqus.rpy; it is created when you start a session. The four older versions have a number appended to the end of the file name; the file name with the lowest number indicates the oldest replay file, and the file name with the highest number indicates the second most recent replay file.

You can execute the commands in a replay file when you start Abaqus/CAE or during a session; however, the result may be different if the replay file generates an error.

From the Abaqus execution procedure

To run a replay file from the Abaqus execution procedure, type abaqus cae (or abaqus viewer) replay=replay_file_name.rpy. If executing the replay file generates an error, Abaqus/CAE ignores the error and continues to the next command in the replay file. As a result, Abaqus/CAE always attempts to execute every command in the replay file. You cannot use the replay option to execute a script with control flow statements. For more information, see Abaqus/CAE execution.

During an Abaqus/CAE session

To run a replay file during a session, select FileRun Script from the main menu bar. If the replay file generates an error, Abaqus/CAE stops executing the replay file and displays an error message in the command area. It is recommended that you run a replay file from the Abaqus execution procedure.

You can also execute a replay file using the Abaqus Python development environment (Abaqus PDE). The Abaqus Scripting Interface commands in the replay file must be run in the kernel workspace in the Abaqus PDE. For more information on the Abaqus PDE, see The Abaqus Python Development Environment.