4

I am currently running a source code in python which uses METIS. I wanted to run it using Jetbrains PyCharm, conda interpreter and these are installed on windows 10. Although I have installed METIS using conda, I could not enable shared libraries and I faced this error:

ModuleNotFoundError: No module named 'metis'

When I tried to run it without conda I faced the following error although I have added the metis.dll location to the environment variables.

RuntimeError: Could not load METIS dll

Could anyone please help me about it?

user3678355
  • 41
  • 1
  • 4

2 Answers2

2

This question is old, but I ran into the same problem and after going down the rabbit's hole for.. too long... I have an answer that worked for me.

First, you should get the python metis wrapper using pip: pip install metis.

Second, You must install conda-metis, which you can find here. Although pip calls the metis python wrapper metis, it just the metis wrapper and does not have metis itself.

Place the files in conda-metis-master in some file path.

The installation requires some fixes. Make sure you have a recent version of Visual Studios (I used 2017). For me, VS had a problem running the instructions in BUILD-WINDOWS.txt, which landed me on this thread:

Why does MSBuild look in C:\ for Microsoft.Cpp.Default.props instead of c:\Program Files (x86)\MSBuild? ( error MSB4019)

Specifically, the answer For Visual Studio 2017 and 2019 on Windows 10 was what I went with. Run:

set VCTargetPaths=C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets

in command prompt with full permissions to set the environment variable.

Also go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ in regedit and change in 4.0 the variable MSBuildOverrideTasksPath and in ToolsVersion\4.0\ the variable MSBuildToolPath to C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin.

For the python metis, we need a .dll, not .lib[1], so we must also look closer at the CMakeLists.txt (see the Linux version of this discussion here). We add on line 19: set(METIS_LIBRARY_TYPE SHARED).

You should follow the BUILD-WINDOWS.txt instructions, but run .\vsgen -G "Visual Studio 15 2017 Win64" inside your conda-metis file path in command prompt with full permissions instead of using Visual Studio 10.

Wait! We need another fix before following the instructions further on using VS to build the the library. Following what was said in:

rint() issue after creating VS Project using CMake

we have to edit the file path_to_your_metis_dir\GKlib\gk_arch.h by removing the line: #define rint(x) ((idx_t)((x)+0.5)). (Or the fix listed on this github exchange.)

Then go to path_to_your_metis_dir\build\windows\.

Open METIS.sln in Visual Studios, go to the top to Build and from the scroll-down go to Build Solution. Afterwards, the .dll file will be in path_to_your_metis_dir\build\windows\libmetis\Release\.

Last, we run in command prompt: set METIS_DLL=path_to_your_metis_dir\build\windows\libmetis\Release\metis.dll

After this, python metis no longer failed on the step from metis import * for me.

[1] If we could use .lib, then conda install -c conda-forge metis would work to get this file, but setting METIS_DLL to the .lib file leads to a windows error.

user73236
  • 161
  • 1
  • 9
  • Hi，thanks so much for your help! But for current version, there is a problem to generate dll file by adding line set(METIS_LIBRARY_TYPE SHARED). It would lead to error in Visual Studio to generate it. According to the report, it seems that the line directory is uncorrect. All the procedure works well if we do not add line set(METIS_LIBRARY_TYPE SHARED). But we could only generate .lib file in this way. Is there any possible solution for this problem? – Xiaojian Chen Mar 19 '21 at 12:25
  • @XiaojianChen, what was the error? What I did here is just a suggestion, based on what the linux version of that conversation looked like. Lines 14 to 18 do is check if the boolean Share was true or false and decide to build a static or dynamic library based on this. If there is a directory error, it seems unrelated to this choice, but you could try telling VS to pass a true value when doing its build instead of this fix. – user73236 Mar 21 '21 at 04:34
0

After getting the error described by @XiaojianChen , this is how I solved it (VS Studio 2022). Continuing after the above fixes, to generate a .dll file after opening up the VS solution file, go to the Solution Explorer, right click on the metis project file -> properties.

In General Properties, change the configuration type to Dynamic Library (.dll)

Screenshot of General Properties window

Under Advanced Properties, change the Target File Extension from .lib to .dll

Screenshot of Advanced Properties window

Since we only need the metis.dll file, right click the metis project file in the Solution Explorer and click build. The .dll can be found in ..\build\windows\libmetis\Release.

GabeTn
  • 1
  • 1