ANSYS Customization Toolkit: an ACT demo for MAPDL users

Transcription

1 ANSYS Customization Toolkit: an ACT demo for MAPDL users Giovanni Federico Ansys UK ltd ANSYS, Inc. May 9, 2016

2 Agenda What is ACT? ACT demo for APDL users; ANSYS, Inc. May 9, 2016

3 What is ACT? ACT = Application Customization Toolkit An add-on module to the Workbench Environment based on Python and XML Add new capabilities Encapsulate process flows for interactive and batch execution Automate repetitive tasks Integrates external processes and codes ANSYS, Inc. May 9, 2016

4 Single Customization approach through ACT JScript Tcl/Tk Design Assessment SDK Scheme APDL External Connection Electronics Desktop AIM Fluent ACT ANSYS, Inc. May 9, 2016 R x 18 SpaceClaim

5 We do have an App Store! Accessible from ansys.com Current download rate (with limited marketing activity): 200 downloads per day 80,000 downloads per year 100 apps total - 14 paid-apps (6 thirdparty) ANSYS, Inc. May 9, 2016

6 Let s look at an example Motivation: reduce the amount of data written to the results file (*.rst), limiting to a set of bodies Solution: use the command OUTRES in a Command Snippet (MAPDL) to control the amount of data to save (scoped to a set of bodies: component body2) allsel cmsel,s,body2 nsle cm,bodynode,node allsel outres,erase outres,all,none, outres,nsol,all,bodynode outres,rsol,all, outres,esol,all,body ANSYS, Inc. May 9, 2016

7 Can we have this in an ACT extension? Let s have a look at the training material, for an example ANSYS, Inc. May 9, 2016

8 Can we have this in an ACT extension? ANSYS, Inc. May 9, 2016

9 ACT workflow and Basics Extension Definition File Behavior/ Instruction File An ACT extension consists of: XML file Configures the UI content Defines the extensions properties Configures behaviors for applicationspecific entries (loads, BCs, solver, tasks, etc.) Binds application callbacks to IronPython script functions IronPython script file Implements the extension s functionality Callback-driven Functions are invoked by application generated events Supports access to external libraries The script file is typically placed in a folder with the same name as the XML file ANSYS, Inc. May 9, 2016

10 Let s do it: prerequisites This workshop assumes that you understand XML and Python Start with WB project file blade-model-150 It has all the settings done (material, loads, analysis settings etc.) Review the command snippet Save the command snippet to a separate file (e.g. APDL_script_for_convection.inp) Only keep the part where the user inputs are used to apply the load Don t keep the user inputs as those will come from the load! APDL_script_for_convection.inp /prep7 thickness = film_coefficient = 200. temperature = 120 cmsel,s,component *GET,n_el,ELEM,0,num,max *GET,mat1, ELEM,n_el,ATTR,MAT et,100,152 keyop,100,8,2. et,1001,131 keyo,1001,3,2 sectype,1001,shell secdata,thickness,mat1 secoff,mid emodif,all,type,1001 emodif,all,secnum,1001 type,100 Commands: to be generated based on user inputs esurf fini alls /solu esel,s,type,,100 nsle sf,all,conv,film_coefficient,temperature allsel, all Static commands: to be reused ANSYS, Inc. May 9, 2016

11 Planning the extension XML Need a button in toolbar for the bladeload Details of the load: Scope to Geometry or Named Selection Only allow body selection Other inputs with appropriate units Python Create the load under analysis Insert the desired APDL commands to ds.dat during runtime 1. Collect the user inputs 2. Convert the user inputs to APDL commands 3. Reuse the APDL commands for applying the load using the user inputs ANSYS, Inc. May 9, 2016

12 1. Collect the user inputs Collect the user inputs ANSYS, Inc. May 9, 2016

13 2. Convert the user inputs to APDL commands Convert the user inputs to APDL commands Using an external module (myutils) to generate an ElementComponent from the selected bodies thickness = film_coefficient = 200. temperature = 120 /prep7 cmsel,s,component The desired APDL commands are written to the stream [ds.dat file] ANSYS, Inc. May 9, 2016

14 3. Reuse the static APDL commands Read the static APDL commands [from the input file] and write to the stream [ds.dat file] *GET,n_el,ELEM,0,num,max *GET,mat1, ELEM,n_el,ATTR,MAT et,100,152 keyop,100,8,2. et,1001,131 keyo,1001,3,2 sectype,1001,shell secdata,thickness,mat1 secoff,mid emodif,all,type,1001 emodif,all,secnum,1001 type,100 esurf fini alls /solu esel,s,type,,100 nsle sf,all,conv,film_coefficient,temperature allsel, all ANSYS, Inc. May 9, 2016

15 Let s try! Open the WB project example; System A will use snippets; System B will be used to build the ACT: Locate xml file and folder; Swap the *.inp file; Show edits in the *.inp file if needed (CM and /SOLU); Load the extension Try; Works? Yes? Bingo Problems? Debug? Use the binary install (WBEX) Open the scripted folder and look at main.py for code changes ANSYS, Inc. May 9, 2016

16 Script 1. Unzip and Open the WB project RST size_start.wbpz; 2. Open Mechanical 3. 2 Systems A has the snippet, B has not, Show named selections (bodyxx), Notice that snippets is as shown earlier; Solve them both, and show comparison of 2 contours (VonM or Displacements); Show RST size difference, Close Mechanical; 4. Now let s create an Extension using the WS material (folder ws basic material): Show the structure (bladeload.xml and main.py with image folder) Point to the inp file (APDL_script_for_convection.inp) and rename it to APDL_script_for_convection_old.inp) From the folder Inp File to Use, copy APDL_script_for_convection.inp to the folder bladeload in ws basic material; Open APDL_script_for_convection.inp and show that is similar to the snippet (component name is different); ON WB, click on ACT Start Page, Manage Extensions, Click on Manage Your Setting, and point the folder where the bladeload.xml is installed, This will bring up BladeLoad extension button, click on it to Load the extension; Switch to Project View, and open Mechanical; Add BladeLoad object in System A and scope this to the center block (add 1 values for the other details) Solve and notice same results, VM and Displacement; 5. OPTIONAL: remove and add the object, or scope to a different body: Solution will fail; Create the ds.dat and look for the OUTRES command snippet: notice discrepancy between names; 6. Let s look now at the binary extension (complete extension); On WB unload the BladeLoad extension; Load the binary (ReduceFileSize.wbex). In the folder ACT Binary and Script Final; Open Mechanical Add the RST scope to to 1 body and solve Change the scope to a different body or a set; Use Named Selection; Show edits in the scripted Bladeload.xml: captions, names and so on; Main.py: Snippet embedded plus removal of details of the object ANSYS, Inc. May 9, 2016

17 ANSYS, Inc. May 9, 2016 Q/A