Workbench offers the ability to record the actions you perform in the user interface, also known as journaling. Journals are recorded as Python-based scripts. You can modify these scripts or create new ones by scripting. Together, these capabilities allow you to quickly and easily replay analyses you've already run using recorded journals, as well as to extend functionality, automate repetitive analyses, and run analyses in batch mode.

For detailed instructions on using journaling and scripting, as well as a complete list of all available data containers, namespaced commands, and data types, see the Workbench Scripting Guide.

Journaling

A journal is a record of all operations that have modified data during your session. Based on your preferences setting, a journal of your full session is automatically saved to the location you specify (see Setting Journaling Preferences). You can also choose to record part of a session to a journal file, capturing a specific set of actions. Playing back the journal recreates the recorded actions exactly. Journaling and scripting tools (including recording and playback) are available through the scripting menu and can be performed by anyone using Workbench. Use journaled sessions to restore work after a crash.

Journals are platform independent and portable, subject to file location consistency between accounts (see File Path Handling in Ansys Workbench for details on file path handling within journals and scripts). They can be used with any Ansys installation (release 12.1 or higher).

Scripting

A script is a set of instructions to be issued to Workbench. The script can be a modified journal, or it can be a completely new set of instructions that you write directly.

The creation of scripts requires a general understanding of programming constructs and paradigms. Workbench uses an object-based approach, similar to object-oriented programming.