akaszynski
commented
3 years ago Great questions!
Hi, first time posting an issue, idk if it's the right place to post, but I got no response on the discord server (so sorry if this isn't the place to ask this type of question).
Sorry about not posting on discord. I'm not sure if we'll continue using that or move over into using an Ansys forum, or just having questions and discussions on GitHub. I'll wait until the dust settles from this transition until we make a decision.
I'm getting started with Ansys, as it seems it's what my department wants to use for a project where I will be doing most of the mechanical models. I was looking at pyansys because I will need to run a lot of models, with tons of variable parameters, and I thought using python would be the way to go. While looking into how to interface with Ansys from python I found 2 things: Pyansys and Ansys ACT.
To answer your question, it all depends on your pipeline and software approach. Ansys Act is a workbench dependent approach where extensions are built from within the ACT App Builder and then run from within Ansys Mechanical. If you intend to vary parameters, you'll then need to use Ansys optiSLang to vary those parameters and batch your solutions.
I just wanted to ask what are the main features or advantages that Pyansys has that Ansys ACT doesn't. Seeing as ACT is officially supported, I'm guessing Pyansys has to have some advantages over the default implementation, something that it can do that ACT can't. I'm just trying to decide which interface to learn, as I will probably be using it for a long time, and once I start implementing functions I'll be somewhat locked into my choice.
In a few days, Ansys will be officially releasing support for the PyAnsys project, so both Ansys ACT and PyAnsys will be supported. The main advantages that PyAnsys has over Ansys ACT are:
- Tight integration with python tools and open source modules alongside Ansys software.
- Scripts are written in python. ACT uses .net and you can call ironpython, and potentially other tools available within Ansys Mechanical.
- Being outside of Ansys Mechanical means that you can call our application workflow without opening up the GUI for user interaction. Should you desire a GUI, you can create your own via
PyQt, or just output plots viamatplotliborvtk.
The PyAnsys project is quite new, and we're adding features and additional functionalities to it based on customer requests, or if something's missing or you need to customize it, you can clone the project, add your own code, and submit a PR. Or simply import ansys.mapdl.core and then create a custom script within your Python environment.
In short, the best approach will depend on your workflow needs and how you'd like to develop software. Should you have any additional questions or need support regarding PyAnsys, please let me know.
CesarRodriguezPereira
ghost
jgd10
Hi, first time posting an issue, idk if it's the right place to post, but I got no response on the discord server (so sorry if this isn't the place to ask this type of question).
I'm getting started with Ansys, as it seems it's what my department wants to use for a project where I will be doing most of the mechanical models. I was looking at pyansys because I will need to run a lot of models, with tons of variable parameters, and I thought using python would be the way to go. While looking into how to interface with Ansys from python I found 2 things: Pyansys and Ansys ACT.
I just wanted to ask what are the main features or advantages that Pyansys has that Ansys ACT doesn't. Seeing as ACT is officially supported, I'm guessing Pyansys has to have some advantages over the default implementation, something that it can do that ACT can't. I'm just trying to decide which interface to learn, as I will probably be using it for a long time, and once I start implementing functions I'll be somewhat locked into my choice.