Journaling is the capturing of Ansys Workbench actions (creating a project, opening a system, and so on) to a file. For Ansys CFX applications, CCL and command actions are embedded within Ansys Workbench actions. Scripting refers to the processes of editing and running a journal file in Ansys Workbench. With scripting, you could, for example, implement a prescribed workflow.
This section describes how to acquire, edit, and run script files that have commands that affect TurboSystem components. For more general information on journal files as well as scripting, refer to Workbench Scripting Guide.
Note:
Journal actions such as a CFD-Post Export or the loading of a static .res file record the path of the file. You may need to manually adjust this filepath before attempting to rerun the journal, particularly if you have created the journal using an unsaved project. More generally, when you create a project, you should save the project immediately to set filepaths that Ansys Workbench uses (rather than require Ansys Workbench to use filepaths that have temporary directories, as happens before the project is saved).
The handling of filepaths described in File Path Handling in Ansys Workbench in the Workbench Scripting Guide applies to file references that are made outside of CCL and command actions.
Workbench journal files for TurboGrid and TurboGrid session files from 12.0/12.1 may not work with 13.0 and later releases. If the recorded file does not explicitly set the topology type, the following CCL block must be added:
TOPOLOGY SET: ATM Topology Optimizer = off END
For Workbench journal files, this CCL block should be added immediately before the following line occurs:
> um mode=normal, object=/TOPOLOGY SET
The line above appears only in journal files that were recorded while the
Topology Setobject was processed (unsuspended).For session files, this CCL block should be added to the beginning of the session file.