• Capture the existing simulation process • Make repetitive operations automatic • Integrate CAE with other in-house analysis processes • Make the technology available to a wider group (non CAE experts)
Workbench Scripting • For task automation at project level – Creating project, performing parameters simulations, optimization etc. • Works “hand-in-hand” with scripting in DIAs – Can embed JScript, CCL, Scheme, APDL
Scripting in Data Integrated Applications Data Integrated Native Support Support Scripting Applications Scripting Journaling with with Language SendCommand SendCommand Mechanical APDL Yes APDL You can insert the ‘SendCommand’ Mechanical JScript Yes call into your ANSYS Workbench scripts to drive these data-integrated DesignModeler JScript Yes applications.
Meshing JScript Yes
FE Molder JScript Yes
AQWA JScript Yes
CFX CCL Yes Yes
CFD Post CCL Yes Yes Recording WB journal will record the FLUENT Scheme Yes Yes actions applied during the set up in PolyFlow N/A theses data integrated apps.
Automation Scenario: Mechanical User Scenario-A :Interested in automating some steps within Mechanical • Examples: – Automate “Analysis Settings” from an Excel file – Generate contacts based on Named Selections – Apply transient Force/Moment loads from Excel – …
Different Customization Methods Workbench: • External Connection Add-in – Making external applications (not integrated with WB) to participate in workflow through parameters – Python scripting can be integrated to add functionality to WB (buttons, menu etc.)
• C# Add-in using Software Development Kit (SDK)
– Integrate external applications in workflow through custom systems – WB GUI customization (addition of buttons, menu etc.) – Listening to various events in Workbench and performing actions – SDK offers much more access compared to External Connection
• Scenario-H: Integrate an in-house/third-party code with WB (not just parameters are exchanged) • Examples: – Use the Mechanical simulation results to perform a life analysis using in-house code – ..
Function Function ality ality • Running WB from other software • Task automation in DM, Meshing, • MATLAB, Excel etc. Mechanical etc. • Read/Write external data in WB • Create a workflow in DM, Meshing, • Integration of in-house/third-party code Mechanical etc. through parameters • Interface to take interactive inputs • Hosting custom toolbar/menu, vertical and task automation applications • High-level integration of in-house/third- Add high-level functionality/GUI in •
Examples (1) Example: • Using External Connection, HFSS parameters and properties are available within Workbench – System acts as proxy for Ansoft HFSS application Typical Usage: • Integration of in-house/third-party code based on parametric input/output
Examples (4) Example: • nCode is integrated in Workbench Project Schematic using C# add-in Typical Usage: • Integrate in- house/third-party codes deep in WB workflow
customize Workbench • Python scripting • Application-level scripting • External Connection add-in • Workbench SDK Different data-integrated applications also allow different types of customization Power and complexity range from basic scripting to full programming Choose method that best fits your needs
• Python scripting – End-to-end “native” simulation applications are under active development – Enables end-to-end automation using only Python scripting
• Application-level scripting – Data-integrated applications will co-exist with native apps for many releases, investments made here will be useful for a long time • External Connection add-in – Being extended to include data transfer in future releases
• Workbench SDK – As native simulation tools emerge, the SDK will enable development of full-featured custom applications
