PyMAPDL provides a Pythonic interface to Ansys Mechanical APDL (MAPDL), enabling engineers and researchers to programmatically control, automate, and integrate MAPDL simulations within Python workflows. It offers direct access to simulation data and remote connectivity, streamlining complex engineering analysis and accelerating product development cycles.

How It Works

The library facilitates direct communication with MAPDL processes, supporting interactive sessions, remote connections via gRPC, and programmatic access to MAPDL arrays, meshes, and geometry as Python objects. It also exposes low-level APDL solver capabilities through a SciPy-like interface, allowing for advanced scripting and data manipulation directly from Python.

Quick Start & Requirements

• Installation: Install ansys-mapdl-core (specific command not detailed in README).
• Prerequisites: Requires a legally licensed local copy of Ansys. Compatible with Windows, Linux, and macOS.
• Environment: Works in Jupyter Notebooks, standard Python console, or batch mode.
• Documentation: PyMAPDL Documentation
• Cheat Sheet: Available for syntax reference.

Highlighted Details

• Enables remote MAPDL connections via gRPC.
• Provides direct Python object access to MAPDL arrays, meshes, and geometry.
• Features a SciPy-like interface for low-level APDL math.
• Integrates specialized AI agents for development, testing, and documentation assistance.
• Supports cross-platform execution on Windows, Linux, and macOS.

Maintenance & Community

• Community support and feedback via PyMAPDL Discussions and Ansys Developer portal Discussions.
• Bug reports and feature requests are managed through PyMAPDL Issues.
• Project formerly known as pyansys, now actively developed by Ansys.
• Contribution guidelines are available.

Licensing & Compatibility

• License: MIT License.
• Compatibility: Requires a licensed Ansys installation. Makes no commercial claim over Ansys software itself.

Limitations & Caveats

• Interactive APDL control necessitates a legally licensed Ansys installation.
• Specific library questions should be directed to GitHub Issues/Discussions, not the core team email.