{"id":25910,"date":"2013-10-02T00:14:00","date_gmt":"2013-10-02T00:14:00","guid":{"rendered":"https:\/\/www.padtinc.com\/2013\/10\/02\/making-apdl-parameters-available-in-the-ansys-parameter-manager-or-designxplorer-prep-solve-and-post\/"},"modified":"2022-03-29T19:03:57","modified_gmt":"2022-03-29T19:03:57","slug":"making-apdl-parameters-available-in-the-ansys-parameter-manager-or-designxplorer-prep-solve-and-post","status":"publish","type":"post","link":"https:\/\/www.padtinc.com\/2013\/10\/02\/making-apdl-parameters-available-in-the-ansys-parameter-manager-or-designxplorer-prep-solve-and-post\/","title":{"rendered":"Making APDL Parameters Available in the ANSYS Parameter Manager or DesignXplorer: Prep, Solve, and Post"},"content":{"rendered":"\n

This is one of those questions that comes up every once in a while that is not so obvious at first glance, but that is simple once you understand how ANSYS Mechanical interacts with ANSYS Mechanical APDL.  After a couple of email exchanges around a tech support question, we thought it would be good to share with everyone.<\/p>\n\n\n\n

Before we get started, if you need a refresher on Command Objects in ANSYS Mechanical, the way in which you send APDL commands to the ANSYS Mechanical APDL solver, here is a seminar from a couple of years ago that covers the whole deal:<\/p>\n\n\n\n

<\/object>PADT_Webinar_Code_Snippets_2011_05_26<\/a>Download<\/a><\/div>\n\n\n\n

The basic problem is this: you have an APDL script you execute as a command object that does some sort of model interrogation or stores the result of some calculation, and you want to use that parameter in the parameter manager or in DesignXplorer.  If you look at the details view for a command object you will notice that it only supports input parameters: ARG1-ARG9.<\/p>\n\n\n\n

\"image\" <\/picture><\/a><\/figure>\n\n\n\n

If you look at the example (silly) macro you will see that it:<\/p>\n\n\n\n

  1. Grabs component (named selection) END1<\/li>
  2. Figures out how many nodes are attached to END1 (NMND)<\/li>
  3. Takes ARG1 as the total load applied load<\/li>
  4. Calculates the per node load by dividing the total load by the number of loads.<\/li>
  5. Applies that per node load<\/li>
  6. Reselects all the nodes<\/li><\/ol>\n\n\n\n

    If I want to know how many nodes I put the load on and what the per node load is I\u2019m kind of stuck here.  Any command object you add to the tree above the Solution branch only allows input parameters.<\/p>\n\n\n\n

    But a command snippet applied in the Solution branch is different, it allows you to pull parameters back and share them through the parameter manager.<\/p>\n\n\n\n

    When you first insert a command object you only get input parameters (ARG1-ARG9) as usual, and an empty section called \u201cResults\u201d<\/p>\n\n\n\n

    \"image\" <\/picture><\/a><\/figure>\n\n\n\n

    The way you get result parameters, or what I think should be called \u201cOutput Parameters\u201d is you create a parameter in the command object\u2019s APDL script that starts with \u201cmy_\u201d  When you click outside the text input window the program parses you script and if it finds any \u201cmy_\u201d parameters in the text, it sticks them in the Results section:<\/p>\n\n\n\n

    \"image\" <\/picture><\/a><\/figure>\n\n\n\n

    Note, the default is \u201cmy_\u201d but you can change it n the \u201cOutput Search Prefix\u201d line in the Definition block.<\/p>\n\n\n\n

    Initially they will show up pinkish because the model has not been run and they are not defined. Click on the box to make them parameters that get passed outside of the program and then run:<\/p>\n\n\n\n

    \"image\" <\/picture><\/a><\/figure>\n\n\n\n

    If you pop back out to the project view you will see that we now have a Parameter Set bar with both input and output parameters:<\/p>\n\n\n\n

    \"image\" <\/picture><\/a><\/figure>\n\n\n\n

    And if you open the parameter manager up you can see the input and output parameters:<\/p>\n\n\n\n

    \"image\" <\/picture><\/a><\/figure>\n\n\n\n

    This works because all ANSYS mechanical is doing is making one big batch input file for ANSYS MAPDL.  That file contains any command objects you insert into the tree and extracts any parameters that you tagged in a post processing command object for return to ANSYS Mechanical.<\/p>\n","protected":false},"excerpt":{"rendered":"

    This is one of those questions that comes up every once in a while that is not so obvious at […]<\/p>\n","protected":false},"author":33,"featured_media":25911,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2323],"tags":[511,492,493,803],"post-podcast":[],"_links":{"self":[{"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/posts\/25910"}],"collection":[{"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/users\/33"}],"replies":[{"embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/comments?post=25910"}],"version-history":[{"count":0,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/posts\/25910\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/media\/25911"}],"wp:attachment":[{"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/media?parent=25910"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/categories?post=25910"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/tags?post=25910"},{"taxonomy":"post-podcast","embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/post-podcast?post=25910"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}