ooSoft

ACT Extension Installation

ACT Workshop
Calgary November 7th
Hands On Workshop #1
Loic.Degueldre@o-o-Soft.com
 ooSoft

SCRIPTED EXTENSION INSTALLATION

2
 ooSoft
Objectives

Install the example scripted extension

Stage-1: Install the extension in %appdata% path
Stage-2: Install the extension in any user specified folder

Load and tryout the extension

3
 ooSoft
Stage-1

1. Copy the XML file (example.xml) and the Folder (example) to the extension folder in
%appdata% path (e.g. %appdata%\ansys\v182\ACT\extensions)

2. Start Workbench and open the Extensions Manager

3. Load the example extension

4
 ooSoft
Stage-1

4. Add a new Static Structural system

5. Import a geometry file

6. Open Mechanical (double click on Model cell)

7. Click the button in the example extension

5
 ooSoft
Stage-2

1. Define the Additional Extension Folder under Workbench menu (Tools

Options)
2. Move the XML file (example.xml) and the Folder (example) to this path
If same scripted extension is available in two different paths, only one is loaded
based on path priority
3. Start a New Project in Workbench and open the Extension Manager
This refreshes the list of available extensions
4. Load the example extension
5. Add a new Static Structural system
6. Import a geometry file
7. Open Mechanical (double click on Model cell)
8. Click the button in the example extension
6
 ooSoft

BINARY EXTENSION INSTALLATION

7
 ooSoft
Objectives

Make a binary example extension and use it

Stage-1: Build and install the binary extension
Stage-2: Hide the Python source code when building the binary
extension

8
 ooSoft
Open the Binary Extension Builder

Build binary extensions

Launch the Extension Builder to

migrate an extension from the
scripted to binary format Manager

9
 ooSoft
Stage-1

1. Select the example extension and build a

binary extension for the same

2. Install the binary example extension

Verify the files installed in the %appdata% Go through the Developers Guide
path (e.g.
%appdata%\ansys\v170\ACT\extensions) and understand the different
Security Options
3. Open the Extension Manager to verify
To avoid any file overwriting issues
while installing binary extensions, it
is recommended to use a different
folder for the scripted extensions.
4. Load and try out the binary example
extension Remark: The Python source file
script.py is still readable in the
example repository of the
10
extension
 ooSoft
Stage-2

1. Edit the example.xml file and add the

attribute compiled=true for the
<script> node
2. Start a New Project in Workbench to
update the changes done to the
extension
3. Build a binary extension for the
example extension

Notice the Skip line. This means

the file will not be visible once the 11
binary extension is installed
 ooSoft
Stage-2

1. Uninstall the previously installed

binary example extension
2. Install the new binary example
extension
Verify the files installed in the
%appdata% path
3. Load and try out the binary example
extension
After installing the binary extension, one can move the WBEX file and the associated
folder to a different path [when one central installation for many users is desired]
! In that case, make sure that the Additional Extension Folder option refers to the
desired path
12