Text-based monitor output is contained in the System Coupling Log (SCL) file that is created in the run directory. Sections of the SCL file that are most relevant to the debugging process are identified below. If problems are encountered, you should carefully review all of these sections.
Setup Validation: This section facilitates review and verification of the input settings made for the system coupling service. These inputs are validated by the coupling service, and both warnings and errors generated during validation are reported here. Any automatic corrections applied to the inputs are listed with validation warnings.
Mapping Summary: This section summarizes the extent to which the source and target regions associated with each data transfer are correctly mapped onto one-another. Under normal conditions, diagnostics should report a nearly perfect mapping. Less than perfect mappings should be critically considered for their validity.
Coupled Solution Convergence History: This section summarizes the convergence of both the coupling participants and the data transfers that target each of the participants. It is strongly recommended that sufficient coupling iterations be executed, per step, to ensure that the field equations solved by all coupling participants and the data transfers defined for the coupled analysis converge fully. Note, however, that the coupling service will advance to the next coupling step, regardless of convergence, once the maximum number of coupling iterations per step has been executed. You are advised to identify and understand all reasons for poor convergence of coupling participants or data transfers.
Error Messages: Fatal errors are reported, as they occur, in the log output. These errors may have originated either within the coupling service itself or within any of the coupling participants. When such an error occurs, output from the service and all participants should be critically reviewed.
Shutdown Reporting: Under normal conditions, the end of the log output generated by the coupling service reports whether or not the coupled analysis completed successfully. When the analysis does not complete successfully, additional information is provided as to what may have caused the problem.
For more information on the content of the SCL file see System Coupling Service Log File (scLog.scl_, scLog_##.scl). Note, as well, that supplemental debug output can also be written to the SCL file to facilitate debugging. This output is generated by adding debug output specifications to the system coupling setup.
Similar output files often exist (either by default or by user request) for the coupling participants. For example, the ANSYS Fluent solver can generate a text based transcript file and the ANSYS Mechanical APDL solver can generate a text based output file. Please refer to Supported System Coupling Participants for more information regarding the text based monitor output that they can generate.