Learning Forum

[Andrew Skocz]

Hello,

I often use Hypermesh combined with the Abaqus solver. The process consists of creating an input deck and solving it using a comand line without the need to start Abaqus.

I was wondering if a similar approach is possible using Ansys. I am using Ansys Workbench 2022. I know I can export an input file but not sure how to solve it.

Thanks

[mrife]

Hi Andrew

Please see the Mechanical APDL help, Operations Guide chapter 4.  This details the different ways to start MAPDL.  Your workflow will be to launch it as a batch process.  There are OS specific details, and even shell type (on Linux) specific details so giving you an exact answer is a little difficult without knowing all of those details.

Mike

p.s. WB Mechanical can work with different solvers; and Ababqus has explicit and implicit capability.  Most of the (structural) analysis systems in WB are using MAPDL as the solver, but not all.  So which specific analysis system are you asking about? 

[Andrew Skocz]

Hi Mike, thanks very much for a quick reply. 

In WB, I am using standard mechanical with some contacts and joints. It is all static.

 

Do you know if the written input file is version agnostic? I am using WB 2022 but also have a WB 2015 with some HPC licenses that I'd like to use but not sure if 2015 would solve the input file exported from 2022.

[mrife]

Andrew

No, the input file should be considered version specific.  That's not to say that it (file from v22) will not solve (on solver v15); it depends on if you are using a feature/function that has changed or not.  Or even using a feature/function in v22 that did not even exist at v15.  The Help has Release Notes for each version that goes into details of the changes.   

[Andrew Skocz]

Mike, thanks for that.

I've just checked the help and could not find how to specify the number of cores to use in the batch solve. Could you help with that?

[mrife]

See chapter 4.1 of that help guide...

[Andrew Skocz]

Hi Mike, all good and working. I managed to get the 2022 file to be solved with 2015 version. It was much slower though, 31sec (2022) vs 95sec (2015). Interesting...

 

Thanks very much for your help.