Identifier	.odb		Description
	Field	History
TURBOMEGA	●	●	Specific turbulent energy dissipation rate.
TURBNU	●	●	Turbulent eddy viscosity.
TURBVISCOSITYRATIO		●	Eddy to molecular viscosity ratio.

Nodal variables You can request nodal variable output to the output database file (see “Node output” in “Output to the output database,” Section 4.1.3).

Identifier	.odbField History	Description
Geometric quantities
COORD	•	Coordinates of the node. These are the current coordinates if the mesh has moved.
COORn	•	Coordinate n (n = 1, 2, 3).
State and field variables
DENSITY	•	Fluid density at a node.
DIV	•	Divergence of the fluid velocity at a node.
PRESSURE	•	Fluid pressure at a node.
TEMP	•	Fluid temperature at a node.
U	•	Fluid displacement components at a node.
Un	•	$u_n$ fluid displacement component (n = 1, 2, 3).
V	•	Fluid velocity components at a node.
Vn	•	$\dot{u}_n$ fluid velocity component (n = 1, 2, 3).
QCRIT	•	Coherent structure visualizator, known as Qcriteria.
VGINV2	•	Second invariant of the rate-of-strain tensor (symmetric part of the velocity gradient tensor).
VORTICITY	•	Vorticity components at a node.
VORTICITYn	•	Vorticity $_n$ vorticity component (n = 1, 2, 3).
SHEARRATE	•	Shear rate at the nodes computed using the second invariant of the rate-of-strain tensor.
Turbulence variables
DIST	•	Wall-normal distance.
TURBEPS	•	Energy dissipation rate.

Identifier	.odb	Description
	Field History
TURBKE	•	Turbulent kinetic energy.
TURBOMEGA	•	Specific turbulent energy dissipation rate.
TURBNU	•	Turbulent eddy viscosity at a node.
TURBVISCOSITYRATIO		Eddy to molecular viscosity ratio.

# Surface variables You can request surface variable output to the output database file (see “Surface output in Abaqus/CFD” in “Output to the output database,” Section 4.1.3). The field output corresponds to the element faces attached to a surface.

Identifier	.odbField History	Description
Geometric quantities
SURFAREA	•	Area of a surface. For deforming meshes, it is the surface area in the current configuration.
State and field variables
AVGPRESS	•	Area-averaged surface pressure.
AVGTEMP	•	Area-averaged surface temperature.
AVGVEL	•	Area-averaged surface velocity vector.
FORCE	•	Total fluid force components on the surface.
HEATFLOW	•	Integrated normal heat flux on a given surface. Heat flow is considered positive if heat is added to the system and negative otherwise. This output request does not include the convective heat flow.
HFL	•	Heat flux vector on a surface. This output request does not include the convective heat flow.
HFLN	•	Normal heat flux on a surface. This output request does not include the convective heat flow.
MASSFLOW	•	Integrated mass flow rate across a given surface.
NTRACTION	•	Fluid normal traction on a surface.
PRESSFORCE	•	Fluid pressure force on a given surface.
STRACTION	•	Fluid surface (or shear) traction on a surface.

Identifier	.odb		Description
	Field	History
TRACTION	•		Fluid total traction on a surface. This is equal to the sum of the normal traction (NTRACTION) and the shear traction (STRACTION).
VISCFORCE		•	Fluid viscous force on a given surface.
VOLFLOW		•	Integrated volume flow rate across a given surface.
WALLSHEAR	•		Fluid shear stress magnitude on a surface. It is the magnitude of the shear traction (STRACTION) vector.
Turbulence variables
YPLUS	•		Wall-normal distance measured in viscous lengths or wall units. A default value of 0 is output for surfaces that are not attached to a wall boundary.
YSTAR	•		Wall-normal distance scaled using turbulent kinetic energy and viscosity. YSTAR output is available only when a turbulence model is specified. A default value of 0 is output for surfaces that are not attached to a wall boundary.

Whole and partial model variables The output variables listed below are available for part of the model as well as the whole model.

Identifier	.odbField History	Description
Geometric quantities
VOL	•	Current volume of the entire set or the entire model.

# Total energy output quantities If the following whole model variables are relevant for a particular analysis, you can request them as output to the output database file (see “Total energy output” in “Output to the output database,” Section 4.1.3). If you do not specify an output region, whole model variables are calculated. When you specify an output region, the relevant energy totals are calculated over the user-specified region. ALLKE Kinetic energy. # 4.3 The postprocessing calculator • “The postprocessing calculator,” Section 4.3.1 # 4.3.1 THE POSTPROCESSING CALCULATOR Products: Abaqus/Standard Abaqus/Explicit # References • “Output to the output database,” Section 4.1.3 • “Abaqus/Standard output variable identifiers,” Section 4.2.1 • “Abaqus/Explicit output variable identifiers,” Section 4.2.2 • “Abaqus/Standard, Abaqus/Explicit, and Abaqus/CFD execution,” Section 3.2.2 # Overview The postprocessing calculator can perform operations on output quantities written to the output database (job-name.odb) by Abaqus. It then expands the output database by writing these new output quantities to the output database. Once this expansion is done, it is not possible to convert the output database back to its original form. The postprocessing calculator is for use only with the Visualization module of Abaqus/CAE (Abaqus/Viewer). # Functionality of the calculator The postprocessing calculator performs the following calculations on data written to the output database: • Extrapolation of integration point quantities to the nodes or interpolation of integration point quantities to the centroid of an element, according to the user-specified position for element output; see “Selecting the position of element integration point and section point output” in “Output to the output database,” Section 4.1.3, for details. • Calculation of history output at tracer particles; see “Tracer particle output from Abaqus/Explicit” in “Output to the output database,” Section 4.1.3. # Running the calculator The postprocessing calculator is generally not required in Abaqus/Standard because by default Abaqus/Standard performs results postprocessing during the course of the analysis. You can override this default behavior by using the environment variable auto\_calculate in the Abaqus environment file. See “Using the Abaqus environment settings,” Section 3.3.1, for details. By default in Abaqus/Explicit or if requested in Abaqus/Standard (using auto\_calculate in the Abaqus environment file), the postprocessing calculator will run automatically upon the completion of an analysis. During the execution of the analysis, Abaqus will determine if there are keywords in the input file that require the use of the calculator and will initiate the calculator upon completion if it is required. You can override this default behavior by using the environment variable auto\_calculate in the Abaqus environment file. See “Using the Abaqus environment settings,” Section 3.3.1, for details. You can run the postprocessing calculator manually by using the convert=odb option on the abaqus execution procedure. To see the postprocessed results before an analysis is complete, you can run the postprocessing calculator manually while the analysis is still running, using the oldjob option in conjunction with the convert=odb option on the abaqus execution procedure. The postprocessing calculator will write a new output database using the value of the job parameter as the file name. Due to the fact that the analysis is writing to the output database at the same time the postprocessing calculator is attempting to read it, the output database may be in an inconsistent state that makes reading it impossible. If this problem occurs, the postprocessing calculator will stop attempting to read the output database and exit. A warning message explaining what has happened will be output to the screen. You can then attempt to run the postprocessing calculator again. If the inconsistent state has cleared, the postprocessing calculator will run normally. If the postprocessing calculator is run during an analysis without the oldjob option, Abaqus will ask you to confirm that the existing output database can be overwritten. You should make sure the analysis is complete before running the postprocessing calculator manually without the oldjob option. If the analysis is still running when the postprocessing calculator is run without using the oldjob option, the output database will be corrupted. For a detailed description of the procedure for running the postprocessing calculator manually, see “Abaqus/Standard, Abaqus/Explicit, and Abaqus/CFD execution,” Section 3.2.2. If an analysis aborts because available CPU time has expired and you restart the analysis, the postprocessing calculator will not automatically expand the output database from the original, aborted run. You must manually run the postprocessing calculator to expand the original output database using the procedure outlined above. # 5. File Output Format Accessing the results file 5.1