{"id":25608,"date":"2012-03-30T15:30:00","date_gmt":"2012-03-30T15:30:00","guid":{"rendered":"https:\/\/www.padtinc.com\/2012\/03\/30\/changing-results-values-in-ansys-mechanical-apdl-dnsol-and-vput\/"},"modified":"2022-08-18T14:35:13","modified_gmt":"2022-08-18T21:35:13","slug":"changing-results-values-in-ansys-mechanical-apdl-dnsol-and-vput","status":"publish","type":"post","link":"https:\/\/www.padtinc.com\/2012\/03\/30\/changing-results-values-in-ansys-mechanical-apdl-dnsol-and-vput\/","title":{"rendered":"Changing Results Values in ANSYS Mechanical APDL\u2013DNSOL and *VPUT"},"content":{"rendered":"

So it is Friday afternoon and that big, involved, deep-dive into some arcane ANSYS capability is still not written.\u00a0 So, time for plan B and the list of not so involved but still somewhat arcane capabilities that we like to expose in The Focus.\u00a0 At the top of that list right now is how to change the results in an ANSYS Mechanical APDL (MAPDL) solve.<\/p>\n

One might ask why would you want to do this?\u00a0 Well the most common usage is that you want to use APDL to calculate some result value and then display it in a plot.\u00a0 Similarly, you may want to do some sort of calculation or post processing on MAPDL results but using and external piece of code, but still show the results in ANSYS.\u00a0 Another common usage is to use MAPDL as a post processor for some external solver.<\/p>\n

And, it turns out, it is pretty easy.\u00a0 And, as you probably have learned by now if you use MAPDL a lot, there is more than one way to do it.<\/p>\n

The \u201cDatabase\u201d<\/h1>\n

Before we get into how to do this, we need to talk about the \u201cdatabase\u201d in MAPDL. If you read through the documentation on the commands we will use, it will talk about the database.\u00a0 This is not the jobname.db file.\u00a0 That is the db file.\u00a0 The database refers to the representation of your model, including results and the currently active loads, in memory when you are running MAPDL.<\/p>\n

When you do a RESUME command, MAPDL reads the DB file and stores the model, including geometry, mesh, loads, and run parameters, in memory.\u00a0 When you do a SET command, it then adds the results and related information into memory.<\/p>\n

So when we use the commands we will talk about next, you are changing what is in the database, not what is in the DB file on your disk.\u00a0 And you are storing it temporarily.\u00a0 Many different commands cause the database to go back to its original values.\u00a0 So you need to be very careful in how you use these tools, and don\u2019t assume that once you have used them, the changes are permanent.<\/p>\n

DNSOL<\/h1>\n

The simplest way to do it is with the DNSOL command: DNSOL<\/strong>, NODE<\/i>, Item<\/i>, Comp<\/i>, V1<\/i>, V2<\/i>, V3<\/i>, V4<\/i>, V5<\/i>, V6<\/i><\/p>\n

So, if you do a dnsol,32,u,x,3.145\u00a0 the value in memory for deflection in the X direction will be changed to 3.145.\u00a0 dnsol,32,s,x,1.1,2.2,3.3 will change the stress on node 32 in the X direction to 1.1, in the Y direction to 2.2, and in the Z direction to 3.3.<\/p>\n

The second argument can also be a component, so you can assign a uniform result value to many nodes at the same time.<\/p>\n

Here is an example, very simple, of a block where we set the deflection on the top nodes to 1 in.<\/p>\n

\n
\n
   1:<\/span> finish<\/pre>\n
<\/p>\n
   2:<\/span> \/clear<\/pre>\n
<\/p>\n
   3:<\/span> \/prep7<\/pre>\n
<\/p>\n
   4:<\/span> blc4,-2,-2,4,4,20<\/pre>\n
<\/p>\n
   5:<\/span> et,1,185<\/pre>\n
<\/p>\n
   6:<\/span> mptemp,1,70<\/pre>\n
<\/p>\n
   7:<\/span> mpdata,ex,1,1,20e6<\/pre>\n
<\/p>\n
   8:<\/span> mpdata,nuxy,1,1,.23<\/pre>\n
<\/p>\n
   9:<\/span> mpdata,dens,1,1,.001<\/pre>\n
<\/p>\n
  10:<\/span><\/pre>\n
<\/p>\n
  11:<\/span> vmesh,all<\/pre>\n
<\/p>\n
  12:<\/span> \/view,1,1,1,1<\/pre>\n
<\/p>\n
  13:<\/span> \/vup,1,z<\/pre>\n
<\/p>\n
  14:<\/span> \/RGB,INDEX,100,100,100, 0<\/pre>\n
<\/p>\n
  15:<\/span> \/RGB,INDEX, 80, 80, 80,13<\/pre>\n
<\/p>\n
  16:<\/span> \/RGB,INDEX, 60, 60, 60,14<\/pre>\n
<\/p>\n
  17:<\/span> \/RGB,INDEX, 0, 0, 0,15<\/pre>\n
<\/p>\n
  18:<\/span> \/show,png<\/pre>\n
<\/p>\n
  19:<\/span> eplot<\/pre>\n
<\/p>\n
  20:<\/span><\/pre>\n
<\/p>\n
  21:<\/span> nsel,s,loc,z,0<\/pre>\n
<\/p>\n
  22:<\/span> cm,nbt,node<\/pre>\n
<\/p>\n
  23:<\/span> d,all,all<\/pre>\n
<\/p>\n
  24:<\/span> nsel,s,loc,z,20<\/pre>\n
<\/p>\n
  25:<\/span> cm,ntp,node<\/pre>\n
<\/p>\n
  26:<\/span> f,all,fx,10<\/pre>\n
<\/p>\n
  27:<\/span> f,all,fy,12<\/pre>\n
<\/p>\n
  28:<\/span> allsel<\/pre>\n
<\/p>\n
  29:<\/span> save<\/pre>\n
<\/p>\n
  30:<\/span><\/pre>\n
<\/p>\n
  31:<\/span> \/solu<\/pre>\n
<\/p>\n
  32:<\/span> solve<\/pre>\n
<\/p>\n
  33:<\/span> finish<\/pre>\n
<\/p>\n
  34:<\/span> \/post1<\/pre>\n
<\/p>\n
  35:<\/span> plnsol,u,sum<\/pre>\n
<\/p>\n
  36:<\/span><\/pre>\n
<\/p>\n
  37:<\/span> dnsol,ntp,u,y,1<\/pre>\n
<\/p>\n
  38:<\/span> plnsol,u,sum<\/pre>\n
<\/p>\n
  39:<\/span><\/pre>\n
<\/p>\n
  40:<\/span> \/show,close<\/pre>\n
<\/p>\n<\/div>\n<\/div>\n
\"aa1003\"<\/a>The Fancy Mesh<\/p>\n
\"aa1004\"<\/a>The Normal Solution<\/p>\n
\"aa1005\"<\/a>Solution with 1\u201d deflection DNSOL\u2019d onto the top nodes<\/p>\n
Pretty simple.<\/p>\n
NOTE:<\/strong> One key thing to remember is you can not use this with Powergraphics. You must have \/graph,full turned on.<\/p>\n
*VPUT<\/p>\n
The DNSOL is great for a few nodes here and there, or a constant value. But it makes for a big nasty *do loop if you want to do a lot of nodes. So ANSYS, Inc. give us the *VPUT command:<\/p>\n
*VPUT<\/strong>, ParR<\/i>, Entity<\/i>, ENTNUM<\/i>, Item1<\/i>, IT1NUM<\/i>, Item2<\/i>, IT2NUM<\/i>, KLOOP<\/i><\/p>\n
As you can see, this command has a lot of options, so read the Help before you use it. Most of the time you have an array that stores the value you want stuck on your model in an array (ParR).\u00a0 Then you specify what MAPDL result you want to overwrite and it takes care of it for you.<\/p>\n
*vput,nws1(1),node,1,s,1 will place new values for maximum principal stress on all the nodes covered in the array , starting at 1.<\/p>\n
Here is an example of the code, after the same solve as above, to do a *vput instead of a DNSOL:<\/p>\n
\n
\n
   1:<\/span> finish<\/pre>\n
<\/p>\n
   2:<\/span> \/post1<\/pre>\n
<\/p>\n
   3:<\/span> plnsol,u,sum<\/pre>\n
<\/p>\n
   4:<\/span><\/pre>\n
<\/p>\n
   5:<\/span> *get,nmnd,node,,num,max<\/pre>\n
<\/p>\n
   6:<\/span> *dim,nwux,,nmnd<\/pre>\n
<\/p>\n
   7:<\/span> *do,i,1,nmnd<\/pre>\n
<\/p>\n
   8:<\/span>     nwux(i) =  i<\/pre>\n
<\/p>\n
   9:<\/span> *enddo<\/pre>\n
<\/p>\n
  10:<\/span><\/pre>\n
<\/p>\n
  11:<\/span> *vput,nwux(1),node,1,u,x<\/pre>\n
<\/p>\n
  12:<\/span> plnsol,u,sum<\/pre>\n
<\/p>\n<\/div>\n<\/div>\n
\"aa1017\"<\/a><\/p>\n
The code places a displacement in the X direction equal to its node number.\u00a0 So node 80 has a UX of 80.<\/p>\n
A key thing to note with *vput is that it is much more transient. Pretty much any other command that involves anything other than plotting or listing blows away the values you assigned with *VPUT.\u00a0 So we recommend that you do a *vput before every plot or listing you do.<\/p>\n
Thoughts, Questions, and Conclusion<\/h1>\n
Of course you should never use this to fudge results.<\/p>\n
You can get very fancy with this. When I use it I often turn off all the plot controls and then create my own legend. That way I can put hours of life on as temperature or SX and then make my own legend that says LIFE or something of the sort.<\/p>\n
Another thing to note is that if you DNSOL or *VPUT a displacement, then ANSYS will distort your plot by that much.\u00a0 That is OK if you are changing deflection, but not so good if you are plotting life or some esoteric stress value.<\/p>\n
A common question when you play with these commands is if you can store the modified results in the RST file.\u00a0 You can for degree of freedom results, but not for stresses.\u00a0 You use LCDEF and RAPPND.<\/p>\n
And what about ANSYS Mechanical?\u00a0 Well it works totally different, and better. You can do all of this using Design Assessment, which was covered in a webinar and a Focus article you can find here<\/a>.<\/p>\n
The key to using these two commands is pretty much the same as any APDL command: Start on a small test model, write a macro to do it, and keep things simple. And, read the manual.\u00a0 Everything you need to know is in there.<\/p>\n","protected":false},"excerpt":{"rendered":"
So it is Friday afternoon and that big, involved, deep-dive into some arcane ANSYS capability is still not written.\u00a0 So, […]<\/p>\n","protected":false},"author":33,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2323],"tags":[],"post-podcast":[],"_links":{"self":[{"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/posts\/25608"}],"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=25608"}],"version-history":[{"count":0,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/posts\/25608\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/media?parent=25608"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/categories?post=25608"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/tags?post=25608"},{"taxonomy":"post-podcast","embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/post-podcast?post=25608"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}