Contributing

Overall guidance on contributing to a PyAnsys library appears in the Contributing topic in the PyAnsys Developer’s Guide. Ensure that you are thoroughly familiar with it and all Coding style before attempting to contribute to PyMAPDL.

The following contribution information is specific to PyMAPDL.

Cloning the PyMAPDL repository

Run this code to clone and install the latest version of PyMAPDL in development mode:

git clone https://github.com/pyansys/pymapdl
cd pymapdl
pip install pip -U
pip install -e .

Posting issues

Use the PyMAPDL Issues page to submit questions, report bugs, and request new features. When possible, use these issue templates:

• Bug report template

• Feature request template

If your issue does not fit into one of these categories, create your own issue.

To reach the project support team, email PyAnsys Core team.

Viewing PyMAPDL documentation

Documentation for the latest stable release of PyMAPDL is hosted at PyMAPDL Documentation.

In the upper right corner of the documentation’s title bar, there is an option for switching from viewing the documentation for the latest stable release to viewing the documentation for the development version or previously released versions.

Testing MAPDL

If you do not have MAPDL installed locally but still want to run the unit testing, you must set up the following environment variables.

In Windows, use:

SET PYMAPDL_START_INSTANCE=False
SET PYMAPDL_PORT=<MAPDL Port> (default 50052)
SET PYMAPDL_IP=<MAPDL IP> (default 127.0.0.1)

In Linux, use:

export PYMAPDL_START_INSTANCE=False
export PYMAPDL_PORT=<MAPDL Port> (default 50052)
export PYMAPDL_IP=<MAPDL IP> (default 127.0.0.1)

This tells ansys.mapdl.core to attempt to connect to the existing MAPDL service by default when the launch_mapdl function is used.

Additionally you can use the environment variables PYMAPDL_MAPDL_EXEC and PYMAPDL_MAPDL_VERSION to specify MAPDL executable path and the version to launch (if multiple versions of MAPDL are installed).

Code style

PyMAPDL follows PEP8 standard as outlined in the PyAnsys Development Guide and implements style checking using pre-commit.

To ensure your code meets minimum code styling standards, run:

pip install pre-commit
pre-commit run --all-files

You can also install this as a pre-commit hook by running:

pre-commit install

This way, it’s not possible for you to push code that fails the style checks. For example:

$ pre-commit install
$ git commit -am "added my cool feature"
black....................................................................Passed
isort....................................................................Passed
flake8...................................................................Passed
codespell................................................................Passed