Export Coupling Interface Diagnostics

Controls for exporting interface and data transfer diagnostics are available in the data model as beta functionality.

Note:  This functionality was previously available as the ExportInterfaceDataPerStep, ExportInterfaceDataPerIteration, and EnableCsvExport expert settings.

When beta features are activated, the following settings defined under the OutputControl.AsciiOutput singleton allow you to set parameters for exporting diagnostics data to ASCII-formatted output files :

Option

This setting controls the frequency with which diagnostics output are generated.

Possible options:

  • None (default value)

    Disabled. No diagnostics output is generated.

  • EveryIteration

    Enabled. Files are written at the end of each iteration and named according to the following convention:

    <interfaceName>_iteration<#>_side<#>_<regionName>

  • EveryStep

    Enabled. Files are written at the end of the final iteration of each step and named according to the following convention:

    <interfaceName>_step<#>_side<#>_<regionName>

When diagnostics are enabled, System Coupling generates two files for each data transfer on each coupling interface, with one file for each participant, and writes them to System Coupling's working directory.

Note:  One interface is created for a given side One / side Two pair of regions, and that all valid data transfers for the pair occur within the interface.

Each file includes the mesh for all nodes (mapped and unmapped) and the results for data transfer variables for the corresponding step or iteration.

Format

When ASCII-formatted diagnostics are enabled, this setting controls the format of generated output.

Possible values:

  • Axdt (default value)

    Diagnostics files are written to .axdt files.

  • Csv

    Diagnostics files are written as a cloud of points to .csv files.