6.4. Diagnostic Output

Aria is instrumented with a diagnostic output capability that can be very useful when you’re debugging problems. You can tell Aria to write additional information to the log file by enabling different “print masks”. A list of common diagnostic options is summarized in the list below. For the complete list you can refer to the Aria runtime help which is printed if you add -h or --help to your launch command (e.g. aria --help).

• --tftklog expression - This option prints out the full expression tree to the log file. It can be useful for diagnosing missing expression errors.

• --arialog nonlinear - Output detailed nonlinear solve information in the log file and the exodus output file at each nonlinear iteration.

• --tftklog finite_check - Do additional checks for NaN or Inf values from expressions and output additional diagnostics.

• --tftklog sens_check - Perform a numerical differentiation of all expressions to check that their provided sensitivities are correct.

• --arialog bc - Display additional boundary condition information in the log file.

Another way to enable a print mask is more versatile and is done through your aria input file. At the highest level of the input file - somewhere in the BEGIN SIERRA block - you can add a DIAGNOSTIC CONTROL block. This enables you to specify intervals in time or time step number over which print masks should be enabled. As a simple example, let’s say you want to enable the sensitivity checker (--tftklog sens_check) around time step number 47. Here’s an example input file snippet that allows you to do that:

Begin Diagnostic Control tftklog
  From Step 46 to 48 enable sens_check
End

With this, the sensitivity checker will only be active for those three time steps (it’s also valid to say From Step 47 to 47 ...). The Diagnostic Control section includes a detailed command reference for that input.