Logging Management

Message logging is involved in several contexts inside optiSLang.

  • Application logging

    The protocol file optiSLang.DATE_TIME.PID.log collects the messages that are optiSLang application specific. Its exact location is platform-dependent.

    • Windows: %APPDATA%\Ansys\optiSLang\Logs

    • Linux: $HOME/.config/Ansys/optiSLang/Logs

  • Project logging

    Project specific messages are shown in the project message log. Additionally, these message are collected in the protocol file Protocol.txt which is embedded in the project.

  • Algorithm logging

    Algorithm specific log messages can be collected. See Parametric System for more information.

Component-specific support for output of logging information include:

  • Message pane of node dialogs

  • Progress state of nodes and systems

  • Command Line Interface with console output

  • Process and Scripts

    • Environment variables

    • Executed scripts process_err.txt and process_out.txt are written to the current design directory

    • Standard output/error streams are written to the OStdOut and OStdErr slots

  • Python node redirects the standard output/error streams and trace back in the message window.

  • MATLAB node redirects the output to a file by using the diary function.

  • Ansys Workbench

    • Setting the environment variable DYNARDO_VERBOSE_LEVEL=1 results in writing of console output in

      • Windows: %TEMP%\optiSLangWBExtensionLogs

      • Linux: /tmp/optiSLangWBExtensionLogs

      and writing an output file to the current design directory when running in batch mode.

    • The folder with logging files written from Workbench can be found in Workbench > Tools > Options > Folder for Temporary Files.

  • Postprocessing

    • Error messages at start up when Python scripts report errors

    • Outputs in Python console when scripted interactively

    • Error logging files are written in

      • Windows: %TEMP%\optiSLang_monitoring

      • Linux: /tmp/optiSLang_monitoring