2.15 Using Journaling and Scripting with FLUENT in Workbench

You can keep a history of your interactions within Workbench, that can also include your interactions within FLUENT, by recording your interactions with the program(s) in session journals (also referred to as journaling). This is done using the Scripting submenu in the Workbench File menu:

File $\rightarrow$ Scripting $\rightarrow$ Record Journal...

In addition, since the journal files are Python-based scripts, you can edit and/or play back previously recorded journal files, or create new journals manually (also known as scripting), that include your interactions within Workbench and, if applicable, any interactions within FLUENT:

File $\rightarrow$ Scripting $\rightarrow$ Run Script File...

For more information about recording and using session journals in Workbench, as well as reference documentation containing available commands and properties, see the separate ANSYS Workbench Scripting Guide.

When using the SendCommand method to directly call a FLUENT text user interface (TUI) command, the TUI command will not be recognized unless you use double quotes around it (e.g., setup.SendCommand("define model energy no")). If a string is included in the TUI command, then a backslash is required before the quotes around the string. For example:

     setup1.SendCommand(Command="(cx-gui-do cx-activate-item \"MenuBar*FileMenu*Close FLUENT\")")

FLUENT internal Scheme commands may not work properly when called directly using the SendCommand method. Therefore, you should use FLUENT text user interface (TUI) commands instead.