Job customization parameters

Job customization parameters are available to customize Abaqus analysis jobs.

abq_cosimulation_lower_port

This variable specifies the lowest port number in the range of TCP/UDP port numbers available for co-simulation between two Abaqus analyses; it is valid only for Abaqus/CAE. The default value is 48000.

abq_cosimulation_upper_port

This variable specifies the highest port number in the range of TCP/UDP port numbers available for co-simulation between two Abaqus analyses; it is valid only for Abaqus/CAE. If this value is not specified, it is set to 1000 more than abq_cosimulation_lower_port.

auto_calculate

If this parameter is set to ANALYSIS, all output database postprocessing in Abaqus/Standard is performed as part of analysis execution. If this parameter is set to ON, output database postprocessing is performed by the postprocessing calculator at the end of an analysis if the execution procedure detects that output database postprocessing is necessary. If this parameter is set to OFF, no output database postprocessing occurs even if the execution procedure detects that it is necessary to postprocess the output database file. The default value is ANALYSIS. In Abaqus/Explicit auto_calculate=ANALYSIS is equivalent to auto_calculate=ON.

average_by_section

This parameter is used only for an Abaqus/Standard analysis. If this parameter is set equal to OFF, the averaging regions for output written to the data (.dat) file and results (.fil) file are based on the structure of the elements. If this parameter is set equal to ON, the averaging regions also take into account underlying values of element properties and material constants. In problems with many section and/or material definitions the default value of OFF will, in general, give much better performance than the nondefault value of ON. See Output to the Data and Results Files, for further details on the averaging scheme.

cae_error_limit

This variable defines the maximum number of error messages that will be sent from an analysis job to Abaqus/CAE; it is valid only for Abaqus/CAE. The default value is 50.

cae_no_parts_input_file

This variable defines the format of the input file generated by Abaqus/CAE; it is valid only for Abaqus/CAE. If this variable is set to ON, Abaqus/CAE will generate an input file without parts and assemblies. The default value is OFF. For more information, see Writing input files without parts and assemblies.

cae_warning_limit

This variable defines the maximum number of warning messages that will be sent from an analysis job to Abaqus/CAE; it is valid only for Abaqus/CAE. The default value is 200.

double_precision

The default precision version of Abaqus/Explicit to run if you do not specify the precision version on the abaqus command line. Possible values are EXPLICIT (only the Abaqus/Explicit analysis is run in double precision), BOTH (both the Abaqus/Explicit packager and analysis are run in double precision), CONSTRAINT (the constraint packager and constraint solver in Abaqus/Explicit are run in double precision, while the Abaqus/Explicit packager and analysis continue to run in single precision), or OFF (both the Abaqus/Explicit packager and analysis are run in single precision). The default is OFF.

max_history_requests

This parameter specifies the maximum number of history requests allowed in an Abaqus analysis. The default value is 10,000. History output in Abaqus is intended for relatively frequent output requests for small portions of a model and is displayed in X–Y plots in the Visualization module of Abaqus/CAE (Abaqus/Viewer). Requesting large amounts of history output will cause performance problems in both analysis and postprocessing of an Abaqus job. For vector- or tensor-valued output variables, each component is considered to be a single request. In the case of element variables, history output will be generated at each integration point. For example, requesting history output of the tensor variable S (stress) for a C3D10M element will generate 24 history output requests: (6 components) × (4 integration points). When requesting history output of vector- and tensor-valued variables, it is recommended that individual components be selected where applicable. In cases where large amounts of history output are required, it is recommended that the data be written to the output database (.odb) as field output from which history data can be extracted using the Visualization module of Abaqus/CAE.

odb_output_by_default

If this parameter is set to ON, output database output will be generated automatically. If this parameter is set to OFF, output database request keywords must be placed in an input file to obtain output database output and to allow the analysis to be restarted. The default value is ON.

onCaeGraphicsStartup

Optional function to be executed before Abaqus/CAE or Abaqus/Viewer begins. This function allows the user to change the graphics options. See Tuning graphics cards, for more information on this function. This function should not normally be changed.

onCaeStartup

Optional function to be executed before Abaqus/CAE begins. See Customizing Abaqus/CAE startup, for examples of this function.

onDesignStartup

Optional function to be executed before Abaqus/Design begins.

onJobCompletion

Optional function to be executed after the Abaqus job completes. A function specified in the Abaqus environment file in the current directory will be executed first, followed by the function in the user's home directory, and then the function in the Abaqus installation environment file. Multiple functions in the same environment file will result in only the last definition being used. See Job variables, for a list of variables available to this function.

onJobStartup

Optional function to be executed before the Abaqus job begins. See Job variables, for a list of variables available to this function.

printed_output

By default, the values of all PREPRINT parameters are NO and no results are printed to the data file. Set the printed_output parameter equal to ON to obtain the same preprint information in the data file as if

*PREPRINT, CONTACT=YES, ECHO=YES, HISTORY=YES, MODEL=YES

were included in the input file. Setting printed_output equal to ON can also cause a large volume of tabular results to be printed to the data file (unless printed output control options are used to limit the output). If the input file is in terms of parts and assemblies, setting printed_output equal to ON will cause the part-assembly map to print out in the data file regardless of the settings on the PREPRINT option; this allows the user to associate the printed output with the part-assembly defined in the input file. The default value for this variable is OFF.

run_mode

Default run mode (INTERACTIVE, BACKGROUND, or BATCH) if the user does not specify the run mode on the abaqus command line when running the analysis products. The default value is BACKGROUND. This variable should not be set to BATCH unless batch queues are defined.

split_dat

If this variable is set to ON, the data file will be split into two pieces. The output from the user input processing will be put in a file with a .pre extension. The analysis output file will still have a .dat file extension. The default value is OFF.

unconnected_regions

If this variable is set to ON, Abaqus/Standard will create element and node sets in the output database for unconnected regions in the model during a datacheck analysis. Element and node sets created with this option are named MESH COMPONENT N, where N is the component number.