Understanding Report Errors

Error output is available for a subset of commonly used reports—reports that require a field function and a list of parts to be specified by the user.

The following is a list of possible error outputs for those reports and a brief description for each. These errors could appear in the output for a specific part from the list of selected parts or for the overall report.

Error Text Meaning
no data No data found for the report computation. A common cause is that the number of cells/vertices that contribute to the report computation is zero.
invalid part The selected part is not feasible for computing this report. This error is not common.
unable to compute Report value(s) could not be computed. A common cause is a failure to fill a field function that is required for the report computation, on a part or a list of parts selected in the report.
incomplete computation This error is output for the overall report value as a result of a combination of per-part value errors. A common example is when the report value could not be computed for a subset of parts from the list of specified parts, but the report computation was successful on the other parts in the list.
nonexistent report This error occurs when an incorrect report name is used in the field function expression getReportValue, which may be used in an Expression Report.
nonexistent report part This error occurs when an incorrect part name is used in the field function expression getReportValue, which may be used in an Expression Report.
missing auxiliary data

This error output is limited to Minimum and Maximum Reports, and Statistics Reports with the Minimum or Maximum statistic selected. The error occurs when the following types of data are unavailable:

  • Collocated data corresponding to a field function that was selected in the list of collocated field functions
  • Co-temporal data corresponding to a monitor that was selected in the list of co-temporal monitors
nonexistent collocated field A field function specified in the field function expression getCollocatedValue does not exist in the list of collocated field functions that was selected under the Min/Max report properties.
using vertex data instead of cell data The report value was computed using the data at the vertices due to unavailability of data at the cells, even if you did not explicitly activate the Smooth Values option under the report properties.
insufficient data This error output occurs most often in Monitor-based reports (Statistics and Integral) and indicates that the existing data was not sufficient to perform the requested computation.
undefined ratio This error indicates a zero denominator during the computation of reports that have a numerator divided by a denominator, such as Average reports, Deviation reports, and Uniformity reports.
invalid idealization

Possible causes for this error are:

  • A periodic interface may not have a definable number of periodic repeats, or have only one total repeat.
  • A symmetry boundary may be non-planar or have no available boundary faces to use to define the symmetry plane.

If the invalid idealization error message appears next to an idealization in this display, it indicates a problem with using that idealization, most likely because of a problem with the interface (for periodic interface idealizations) or one or more symmetry boundaries of the region (for symmetry idealizations).

If a report tries to access a non-existent or ill-defined field function during a simulation run, Simcenter STAR-CCM+ displays a server error message that interrupts the simulation. Examples of reports that can cause interruptions are:

  • Report and field function not compatible with each other—for example, a vector field function is used by a report that requires a scalar field function.
  • Report using nonexistent user-defined field function—for example one that was deleted since the report was created.
  • User-defined field function using incorrectly defined expressions.

To prevent such interruptions, check your simulation for objects that use the wrong field functions, and delete or modify those objects.

Concise versions of the error messages appear in the Output window. The following example shows the output from a Surface Standard Deviation report that was run with an inappropriate input part. 

Surface Standard Deviation of Temperature on Volume Mesh

Part                   Value (K)         Errors
--------------------   -------------     -------------------------------
Threshold               3.343456e+02     no data, invalid part
                       -------------     -------------------------------
               Total:   0.000000e+00     no data, incomplete computation

For detailed information, right-click the report and select Error Log. Details appear in the Output window. The following example is the error log for the Surface Standard Deviation report shown previously: 

Surface Standard Deviation 1: no data
  Threshold: no data, invalid part
    OutputPiece of Threshold from Region 1: no data

You can also display error points visually. See instructions for displaying computation errors in a monitor plot.