Replies: 3 comments 6 replies
-
Hi @DMaxJ Could you please run your script from terminal (or Anaconda Command Prompt in Windows)? Just run the following command in your "Anaconda Command Prompt":
This way, at least you should be able to have the entire output. |
Beta Was this translation helpful? Give feedback.
4 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
-
So far the work around is The problem seems to be with pardiso solver. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I am here again with another problem. Few days ago I was able to work with the installation of "dev" version of both OpenPNM and porespy. I was working with the older versions of both until 2020. Right now, I am getting some crazy behaviour when I run stokes flow algorithm. Spyder crashes, Before I can read the output on the screen, I get the following message
The system cannot find the path specified. OMP: Error #15: Initializing libiomp5md.dll, but found libiomp5md.dll already initialized. OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.
Any suggestions from your end? I am running on Windows10, Anaconda and porespy and openpnm installed in a virtual environment. Everything works fine until I apply boundary conditions. When
perm.run()
is keyed in it quickly shows some output, but the error message comes before I can read it.
Beta Was this translation helpful? Give feedback.
All reactions