3.2.3 Execution procedure for ABAQUS/CAE

Product: ABAQUS/CAE  

Reference

Overview

ABAQUS/CAE, an interactive environment for creating, submitting, monitoring, and evaluating results from ABAQUS simulations, is executed by running the ABAQUS execution procedure and specifying the cae parameter.

Command summary

abaqus cae
[database=database-file]
 
[replay=replay-file]
[recover=journal-file]
[startup=startup-file]
[script=script-file]
[noGUI=noGUI-file]
[custom=script-file]

Command line options

database

This option specifies the name of the model database file or output database file to open. To specify a model database file, include either the .cae file extension or no file extension in the file name. To specify an output database file, include the .odb file extension in the file name.

replay

This option specifies the name of the file from which ABAQUS/CAE commands are to be replayed. The commands in replay-file will execute immediately upon startup of ABAQUS/CAE. If no file extension is given, the default extension is .rpy.

recover

This option specifies the name of the file from which a model database is to be rebuilt. The commands in journal-file will execute immediately upon startup of ABAQUS/CAE. If no file extension is given, the default extension is .jnl.

startup

This option specifies the name of the file containing Python configuration commands to be run at application startup. Commands in this file are run after any configuration commands that have been set in the environment file.

script

This option specifies the name of the file containing Python configuration commands to be run at application startup. Commands in this file are run after any configuration commands that have been set in the environment file.

Arguments can be passed into the file by entering -- on the command line, followed by the arguments separated by one or more spaces. These arguments will be ignored by the ABAQUS/CAE execution procedure, but they will be accessible within the script.

noGUI

This option specifies the name of a file containing Python scripts to be run without the graphical user interface (GUI). This option is useful for automating pre- or post-analysis processing tasks without the added expense of running a display. Since no interface is provided, the scripts cannot include any user interaction. ABAQUS/CAE runs the commands in the file and exits upon their completion. If no file extension is given, the default extension is .py.

Arguments can be passed into the file by entering -- on the command line, followed by the arguments separated by one or more spaces. These arguments will be ignored by the ABAQUS/CAE execution procedure, but they will be accessible within the Python script.

noenvstartup

This option specifies that all configuration commands in the environment files should not be run at application startup. This option can be used in conjunction with the script command to suppress all configuration commands except those in the script file.

noSavedOptions

This option specifies that ABAQUS/CAE should not apply the display options settings stored in abaqus_v6.6.gpr (for example, the render style and the display of datum planes). For more information, see Saving your display options settings, Section 50.12 of the ABAQUS/CAE User's Manual.

noStartupDialog

This option specifies that the Start Session dialog box for ABAQUS/CAE should not be displayed.

custom

This option specifies the name of the file containing ABAQUS GUI Toolkit commands. This option executes an application that is a customized version of ABAQUS/CAE. For more information, see Chapter 1, Introduction,” of the ABAQUS GUI Toolkit User's Manual.

Examples

The following command will execute ABAQUS/CAE and load the model database file called “beam”:

abaqus cae database=beam
The following command will run the Python script in a file named “try.py” at application startup and pass “argument1” to the script:
abaqus cae script=try.py -- argument1
If “try.py” is defined as
import sys
print sys.argv[-1]
the above command will print argument1.