System Coupling can generate diagnostics and debugging output to help you troubleshoot issues with coupled analyses. For more information, see:
System Coupling can generate debug log files to record transactions between itself and its participant solvers. Log file content is controlled by the command-line options listed in Debug Logging Command-Line Options in the System Coupling Settings and Commands Reference documentation.
To request that debug log files are generated, perform the following steps:
Start System Coupling from the command line (in either the CLI or the GUI), using the -l or --logLevel option to specify a logging level of
1or higher.Optionally, you can use the following additional arguments to specify details for the log output:
Use the --logDir option to specify an output directory for the log files.
Note: By default, the log files are written to System Coupling's working directory.
If the logging level is set to a value of
2or higher, use the --logMaxArrayElements to specify the maximum number of data array elements that can be included in the file. (Default value is5.)
When System Coupling is started, debug logging is activated.
When debug logging is activated, during the solution, System Coupling will write data to
the following files, with "date" and
"time" indicating when the run
began:
- SyC_Log_Controller_<
date>_<time>.txt Contains log information from the controller process.
- SyC_Log_CNode<
N>_<date>_<time>.txt Contains log information from compute node "
N"Tip: The log file for compute node 0 usually contains the most relevant information.
Example 48: When starting the CLI on Windows, request that Level 1 debug log files are written to the default directory
Log files containing RPC calls will be written to System Coupling's working directory.
> "%AWP_ROOT242%\SystemCoupling\bin\systemcoupling" --logLevel=1
Example 49: When starting the GUI on Windows, request that Level 2 log files are written to the specified directory
Log files containing RPC calls and diagnostics will be written to the SyC/DebugOutput directory within System Coupling's working directory.
> "%AWP_ROOT242%\SystemCoupling\bin\systemcoupling" -G --logLevel=2 --logDir=SyC/DebugOutput
Example 50: When starting the CLI on Linux, request that Level 3 log files are written to the default directory
Log files containing RPC calls/diagnostics and a maximum of three heavyweight data array elements will be written to System Coupling's working directory.
$ "$AWP_ROOT242/SystemCoupling/bin/systemcoupling" --l3 --logMaxArrayElements=3
System Coupling can generate files containing diagnostic information for mapping weights, interpolation, interfaces, and data transfers. These capabilities are available as beta functionality. For more information, see the following sections in the System Coupling Beta Features documentation: