The scLog.scl file provides key runtime information related to a coupled analysis between various participants, including:
The command line used to start the system coupling service
System coupling header and build information
A summary of system coupling setup information, including:
Analysis information
Coupling participant information (number of participants, and summary information pertaining to each participant)
Data transfer information (number of data transfers, and summary information pertaining to each data transfer)
Execution control information (co-simulation sequence, debug output)
Setup validation (summary of system coupling input file validation)
System coupling co-simulation summary (summary of system coupling participants)
Solution information, including:
Mapping summary (including percentages of mapped source and target nodes and the percentages of mapped source and target areas, depending upon the mapping algorithm that was used)
Convergence information at each coupling step and iteration
The information here includes the coupling step index, the current analysis time for transient couplings, the coupling iteration index, the participant name and data transfer name, the participant convergence status (for example, “Not Yet Converged...”, “Converged”, and so on), and the data transfer convergence (for example, the RMS/Maximum normalized change).
Shutdown information, including:
Run completion status
During the execution of a run, the service log file, named scLog.scl_, is generated, evolving with the analysis,
and is finally renamed at the end of the run. The final log file is
named with the convention: scLog_##.scl, where
the suffix _## denotes the run index. For
example, scLog_13.scl corresponds to the 13th
run (that is, the 12th restart) executed for the analysis.
For more detailed information about the log file contents, see Understanding the System Coupling Log File.