Skip to main content

Ansys Workflow

Everyone has their own workflow in doing their analysis with different goals and preferences. Here's mine and a reasoning of why I do so. I would be eager to hear thoughts from other people on this subject.
  1. Geometry Cleanup in SpaceClaim
    • The first step here is self explanatory. The litmus test is a crude mesh.
    • Simplification of the model while maintaining objectives is next.
  2. Named Selection in SpaceClaim
    • For a middle to large size model, every object I need in Mechanical gets a Named Selection. This is critical in organizing contacts and mesh properties. Modeling decisions gets clarity at this stage. 
    • Rotating, hiding different parts and visualization is simply just easier in SpaceClaim compared to Mechanical. 
    • If any geometry changes needs to be made, much of the model could be reused (e.g. contacts, boundary conditions). 
  3. First Pass Analysis
    • The first analysis is usually very crude. The goal is to have a minimum viable product on hand that can be shared with the customer. We can then talk through the assumptions and risk/benefits of future analysis, sensitivity studies, parameter exploration etc. 
    • Going further without talking to the customer is risky as it may waste precious time chasing unwanted goals.
  4. Accumulate Additional Layers of Analysis Complexity
    • The first pass analysis has a lot of assumptions. By peeling away the assumptions, there are trade offs like solution time, untested scripts etc which can be isolated for faster iterative troubleshooting. 
    • Exporting the model to ANSYS Classic is sometimes done at this point for custom scripts testing. Standalone simple models with expected outcomes may be also created at this stage to verify implementation.
    • Any significant results are shared with the customer. It could be just a simple screenshot and a phone conversation but it heads off any surprises later. This also aids the customer in making design decisions in parallel to the analysis. 
  5. Report Writing
    • Not very sexy. This benefits from proper file naming and documentation of assumptions during analysis. 
    • As a legacy document, a well written report will help peers and successors recreate and build on the work. 


Popular posts from this blog

ANSYS User Defined Results

There is an abundant of options in ANSYS classic when one wishes to post process results. ANSYS workbench default pull down menu post processing options are more limited but they can still be accessed via the User Defined Results. One way not commonly used but can come in handy is as follows: Zeroth: Under Analysis Settings, there is "Output Controls" where you can toggle to "Yes" what you would like to save before the solution starts. This is like OUTRES in APDL. Output Controls First: After solving the model, click on Solution in the tree to highlight it. Solution Second: Click on Worksheet in the toolbar. Worksheet Third: In the worksheet, you will see list of results that are saved. Right click on it to create the User Defined Results. Create User Defined Results So here we have it. You could of look up the different expressions in the help document but I find this method of accessing the results convenient.  Example: Aspec

Export Stiffness Matrix from Ansys

It is sometimes useful to extract the mass and stiffness matrix from Ansys.     *SMAT, MatK, D, IMPORT, FULL, file.full, STIFF       *PRINT, matk, matk, txt Exporting mass matrix would be similar:       *SMAT, MatM, D, import, full, file.full, MASS The above script uses APDL Math to get the job done. (Please see previous post for another example). The ordering of the matrix is unfortunately not concurrently exported. To verify the sequencing is as expected, we will work to replicate a truss example in the  Finite Element Trusses course notes by Bob Greenlee. Figure 1: Truss Problem Setup Model Creation Script to create model: /prep7 !! Creates Model to reflect course notes ! Properties et ,1,1  mp , ex, 1, 29.5e6 r , 1, 1 ! Geometry n ,1 $  n ,2, 40 $  n ,3, 40, 30 $  n ,4, 0, 30 e ,1,2 $  e ,2,3 $  e ,1,3 $  e ,3,4 ! Boundary Conditions d ,1,ux,0 $  d ,1,uy,0 d ,2,uy,0 d ,4,ux,0 $  d ,4,uy,0 f ,2,fx,20e3 f ,3,fy,-25e3 ! solves /solu eqslv , sparse

ANSYS APDL Syntax Highlighting editor

Notepad++ with APDL User Defined Language The editor of my choice is Notepad++  with the available User Defined Language Files for APDL . You can install it without administrative privileges via the zip file. The best part of it is, it's FREE! After installing Notepad++, go to "Language>Define Your Language..." then "Import" the XML file downloaded from the above link. Remember to restart Notepad++ so that the language changes will take into effect. Opening up any *.inp or *.ans files should automatically switch highlighting to APDL. I made some minor edits. Here's my XML file: LINK . I also heard Sublime Text and  Ultraedit  has more advance features but they aren't (totally) free.