Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TugboatEng on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!
How to go back to WB from Ansys
- Thread starter cuteice
- Start date
Hi,
Recommendation: don't go back to WB just to solve the model: it's absolutely useless, since WB's "solve" calls the exact same solver as "Classical", with the difference that Classical enables a bit more control (of course, if you know how to play with APDL "Commands" snippets in WB, you can do everything with it).
In addition, it can also be "dangerous" since, as I've been explained by the Customer Support, some operations combine the data stored in the "database" part and other data stored in the "results" part. The "results" part now is identical in WB and Classical (I'm speaking about v.11.0), but the "database" is NOT and in the future never will be (It wouldn't be possible, due to the totally different architecture). So, some functions which are "supported" in WB because they are APDL commands, seem to work but restitute incorrect results: the most clear example is with the "CYCLIC" command.
To make a long story short: with v.11.0, use this sequence:
- prepare in WB
- edit in Classical (this is what you already did)
- solve in Classical
- close Classical, open WB, create a Solution Environment and "Read ANSYS Results File", pointing to the directory in which your ".rst" file has been stored. NOTE: it MUST be called "file.rst". From this point, any post-processing typical to WB is allowed (as I already said, the .rst MUST have been generated with a model which is "inter-compatible" between the two systems).
Regards
Recommendation: don't go back to WB just to solve the model: it's absolutely useless, since WB's "solve" calls the exact same solver as "Classical", with the difference that Classical enables a bit more control (of course, if you know how to play with APDL "Commands" snippets in WB, you can do everything with it).
In addition, it can also be "dangerous" since, as I've been explained by the Customer Support, some operations combine the data stored in the "database" part and other data stored in the "results" part. The "results" part now is identical in WB and Classical (I'm speaking about v.11.0), but the "database" is NOT and in the future never will be (It wouldn't be possible, due to the totally different architecture). So, some functions which are "supported" in WB because they are APDL commands, seem to work but restitute incorrect results: the most clear example is with the "CYCLIC" command.
To make a long story short: with v.11.0, use this sequence:
- prepare in WB
- edit in Classical (this is what you already did)
- solve in Classical
- close Classical, open WB, create a Solution Environment and "Read ANSYS Results File", pointing to the directory in which your ".rst" file has been stored. NOTE: it MUST be called "file.rst". From this point, any post-processing typical to WB is allowed (as I already said, the .rst MUST have been generated with a model which is "inter-compatible" between the two systems).
Regards
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
