- database
-
This option specifies the name of the model database file or output database
file to open. You can open either type of file in
Abaqus/CAE;
you can open only output database files in
Abaqus/Viewer.
To specify a model database file, include either the .cae
file extension or no file extension in your file name. To specify an output
database file when running
Abaqus/CAE,
include the .odb file extension in your file name. If you
are running
Abaqus/Viewer,
you can omit the .odb file extension.
- 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.
You cannot use the replay option to execute a script with
control flow statements. For more information, see
Replaying an Abaqus/CAE session.
- recover
-
This option specifies the name of the file from which a model database is to
be rebuilt; it is not available if you are running
Abaqus/Viewer.
The commands in journal-file
(model_database_name.jnl) will
execute immediately upon startup of
Abaqus/CAE.
For more information, see
Recreating a saved model database,
and
Recreating an unsaved model database.
- 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.
Abaqus/CAE
does not echo the commands to the replay file when they are executed.
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.
- script
-
Same as startup.
- 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. If you
use the noGUI option,
Abaqus/CAE
ignores any other command line options that you provide.
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. If
you are using the noGUI option, you can use an argument to
pass in a variable that would otherwise be provided by a command line option.
For example, you can pass in the name of a file that would otherwise be
specified by the script option.
A sample usage of the noGUI option is
available in
Abaqus/CAE Execution.
- 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 startup command to
suppress all configuration commands except for those in the
startup file.
- noSavedOptions
-
This option specifies that
Abaqus/CAE
should not apply the display options settings (for example, the render style
and the display of datum planes) stored in the
abaqus_2024.gpr
file. For more information, see
Working with abaqus_2024.gpr files,
and
Saving your display options settings.
- noSavedGuiPrefs
-
This option specifies that
Abaqus/CAE
should not apply the GUI options settings (for
example, the size and location of the
Abaqus/CAE
main window or its dialog boxes) stored in the
abaqus_2024.gpr
file.
- noStartupDialog
-
This option specifies that the Start Session dialog box
for
Abaqus/CAE
or
Abaqus/Viewer
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
or
Abaqus/Viewer.
For more information, see
Introduction.
- guiTester
-
This option starts a separate user interface containing the
Abaqus
Python development environment along with
Abaqus/CAE
or
Abaqus/Viewer.
The
Abaqus
Python development environment allows you to create, edit, step through, and
debug Python scripts. For more information, see
The Abaqus Python Development Environment.
You can specify a script as the argument for this option, which prompts
Abaqus/CAE
or
Abaqus/Viewer
to run a GUI script.
Abaqus/CAE
or
Abaqus/Viewer
closes when the end of the script is reached.
- guiRecord
-
This option enables you to record your actions in the
Abaqus/CAE
or
Abaqus/Viewer
user interface in a file named abaqus.guiLog. Creating a
record of your actions in the GUI can help you capture and replay common
activities in
Abaqus/CAE
or
Abaqus/Viewer
for demonstration or training purposes. You can replicate all of the actions
from a .guiLog file in
Abaqus/CAE
or
Abaqus/Viewer
by running the file in the
Abaqus
Python Development Environment (PDE); for more
information, see
Running a script.
If desired, you can set guiRecord at
startup by using the environment variable
ABQ_CAE_GUIRECORD. The
guiRecord option cannot be used with the
guiTester option.
- guiNoRecord
-
This option enables you to disable user interface recording when the
environment variable ABQ_CAE_GUIRECORD is set.