How to call Python scripts towards the EDT Ansys from MATLAB?

[Hozad69]

Is there any instruction anywhere on how to configure so that I can call Python scripts towards the EDT (2025 R1 and forward) from MATLAB? I get a lot of “library not found” errors and so on when using pyenv in MATLAB but I’m not sure how to do the configuration. I have a virtual environment defined thorough the Ansys Python Manager and then there is the native environment so I’m a little bit confused how to get all this to work together with MATLAB.

[mohammadrezwankhan]

The main point is to make MATLAB use the exact Python executable belonging to the environment in which PyAEDT is installed. Do not mix the AEDT-native interpreter, an Ansys Python Manager environment, and a different Python found through PATH.

First verify the chosen environment outside MATLAB. On Windows:

C:\path\to\pyaedt_venv\Scripts\python.exe -c "import sys, importlib.metadata as m; import ansys.aedt.core; print(sys.executable); print(m.version('pyaedt'))"

If that import fails, install PyAEDT into that same interpreter:

C:\path\to\pyaedt_venv\Scripts\python.exe -m pip install --upgrade pyaedt

Then start a fresh MATLAB session and bind pyenv to the full executable path before making any py.* call:

pythonExe = "C:\path\to\pyaedt_venv\Scripts\python.exe";

pe = pyenv;
if pe.Status == "Loaded"
    if pe.ExecutionMode == "OutOfProcess"
        terminate(pe);
    else
        error("Restart MATLAB before changing an in-process Python interpreter.");
    end
end

pe = pyenv(Version=pythonExe, ExecutionMode="OutOfProcess");
disp(pe)
disp(string(py.sys.executable))

% Import PyAEDT and connect to an existing AEDT 2025 R1 session.
aedt = py.importlib.import_module("ansys.aedt.core");
desktop = aedt.Desktop(pyargs( ...
    "version", "2025.1", ...
    "non_graphical", false, ...
    "new_desktop", false, ...
    "close_on_exit", false));

Use new_desktop=true if MATLAB should launch a separate AEDT instance instead of attaching to an existing one. If several 2025 R1 processes are running, Desktop also accepts aedt_process_id together with new_desktop=false.

ExecutionMode="OutOfProcess" is a good first choice here because PyAEDT and MATLAB can load native libraries with conflicting dependencies. Once the workflow is stable, you can test in-process execution if call overhead matters.

If py.sys.executable is not the executable you selected, stop there: MATLAB is still bound to the wrong environment. Also check getenv("PYTHONHOME"); a stale PYTHONHOME can override or conflict with pyenv.

For AEDT 2025 R1, a Python 3.10 environment is the conservative choice. PyAEDT's installation documentation notes that AEDT 2023 R2 and later use Python 3.10 wheelhouses, while MATLAB's supported Python version still depends on the MATLAB release.

References:

• MATLAB pyenv: https://www.mathworks.com/help/matlab/ref/pyenv.html
• PyAEDT installation: https://aedt.docs.pyansys.com/version/stable/Getting_started/Installation.html
• PyAEDT Desktop: https://aedt.docs.pyansys.com/version/stable/API/_autosummary/ansys.aedt.core.desktop.Desktop.html