Specifies the name of a FORTRAN source or object file that contains any user subroutines to be used in the analysis. The name of the user routine may contain a path name and may be given with or without a file extension. This option is not applicable for ABAQUS/CFD.

If an extension is given, the program will take the appropriate action based on the file type. If the file name has no extension, the program will search for a FORTRAN source file. If the source file does not exist, an object file will be searched for instead. The execution procedure creates a shared library using the user subroutine file that is used by ABAQUS/Standard or ABAQUS/Explicit during execution.

If the same user subroutine will be required often, consider setting the usub_lib_dir environment file parameter and using the ABAQUS make execution procedure to create a shared library containing the user subroutine. This will avoid the need to recompile and/or relink the user subroutine each time it is needed. The user option is not required if the user subroutine called by the analysis is contained in the user library. User libraries contained in the directory given by the usub_lib_dir environment file parameter will not be used if the user option is specified.

This option cannot be used to specify an object file when the double option is used to run an ABAQUS/Explicit analysis because ABAQUS/Explicit double precision runs need both single precision and double precision objects. In this case, you must set the usub_lib_dir environment file parameter and place the single and double precision object files in the specified directory. Alternatively, you can supply the user subroutine source.

Specifies that the double precision executable is used for ABAQUS/Explicit. The possible values are: both, constraint, explicit, and off.

This capability is also supported through the ABAQUS environment file with the environment variable double_precision.

Specifies that ABAQUS/CAE is to be run without the graphical user interface (GUI). If no file name is specified, an ABAQUS/CAE license is checked out and the Python interpreter is initialized to allow interactive entry of Python or ABAQUS Scripting Interface commands.

If a file name is specified, ABAQUS/CAE runs the commands in the file and exits upon their completion. If no file extension is given, the default extension is .py. 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. 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.

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.

A copy of the file is stored in the working directory.

Defines the working file name. The working file name can be relative or absolute. If the file exists only once in the design directory, only the file name is defined. If the file exists in several subdirectories of the design directory, you should define the relative path.

You can use RegExes as working file names. To do so, select RegEx from the menu to the left of the field. When selected, the archival option is selected for all files that comply with the regular expression.

Wildcards are not regular expressions. The following is a list of the most important conversions for wildcards and some examples for RegExes.

Defines the importance of files using the following options.

You must specify the maximum runtime in the additional options when using the Wait and Wait, indicates failure settings. These settings wait at most until the expiration of this value, even if the (executed) process has already finished.

By default, conditions are checked every one second. The interval of the check can be changed in the configuration settings.

If only one of Wait or Wait, indicates failure is set, but the associated files are not created, the process node waits until the maximum runtime.

When selected, activates the launch of a single process for multiple designs. The process node creates a file with designs to be calculated and provides the following environment variables for the executing script:

If this option is enabled, the environment variables OSL_DESIGN_NO, OSL_DESIGN_NAME, and OSL_DESIGN_DIR are not available.

An example implementation for the script in process node:

REM This is a Windows batch script (*.bat)
copy ..\..\..\py\run_multi_cpfunc.py
python run_multi_cpfunc.py %OSL_DESIGNS_BASE% %OSL_DESIGNS_LIST%

An example code snippet to process the designs:

# This is the Python script "run_multi_cpfunc.py"
...
basedir=normpath(sys.argv[1]) # base directory
listfile=normpath(sys.argv[2]) # path of the file containing the listing of design folders
for folder in listfilereader(listfile):
    pd=myreader(join(basedir,folder,'inp_cpfunc.txt')) # pd stands for parameter dictionary
    results={'Y': 0.5*pd['X1']+pd['X2']+0.5*pd['X1']*pd['X2']+5*sin(pd['X3'])+0.2*pd['X4']+0.1*pd['X5']}
    mywriter(join(basedir,folder,'out_cpfunc.txt'),results)
...