You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you uninstall your MAPDL version, and then install a new version, PyMAPDL does not update the value in CONFIG_FILE.
If the executable path in that file is not valid, we should probably delete it, raise a better exception, or reuse the default methods to re-detect MAPDL. Since the user does not set the value in that file in most of the cases (although he can using save_ansys_path), I guess the best is to reset it and loop for another installation.
The text was updated successfully, but these errors were encountered:
The CONFIG_FILE management is now delegated to ansys-tools-path hence we need to make sure we are resetting that config file (ours does not exist anymore).
If you uninstall your MAPDL version, and then install a new version, PyMAPDL does not update the value in
CONFIG_FILE
.If the executable path in that file is not valid, we should probably delete it, raise a better exception, or reuse the default methods to re-detect MAPDL. Since the user does not set the value in that file in most of the cases (although he can using
save_ansys_path
), I guess the best is to reset it and loop for another installation.The text was updated successfully, but these errors were encountered: