Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Found a possible bug #90

Closed
guilkey opened this issue Oct 10, 2023 · 1 comment
Closed

Found a possible bug #90

guilkey opened this issue Oct 10, 2023 · 1 comment

Comments

@guilkey
Copy link

guilkey commented Oct 10, 2023

Hi,

A few months ago I reported that I installed MPLBM-UT, but when I ran the single_phase_permeability example, it would hang. "top" reported that python was still doing work, but there was no progress. I finally returned to this and after putting bunches of print statements in the python code, figured out exactly where it was hanging. I am hoping that by sharing this, it might save someone else a bit of trouble. Specifically, in:

~/.local/lib/python3.9/site-packages/pypardiso/pardiso_wrapper.py

the following lines of code:

        globs = glob.glob(
            f'{sys.prefix}/[Ll]ib*/**/*mkl_rt*', recursive=True
        ) or glob.glob(
            f'{site.USER_BASE}/[Ll]ib*/**/*mkl_rt*', recursive=True
        )

were not able to find my mkl libraries. When I replaced these with:

          f'/usr/local/lib/*mkl_rt*', recursive=True

and:
f'/home/guilkey/.local/lib/mkl_rt', recursive=True

respectively, everything worked.

Note that I outputted sys.prefix and site.USER_BASE and these were reported as:

sys.prefix = /usr
site.USER_BASE = /home/guilkey/.local

so it seems the extra "**/" in each line isn't needed.

This is on a Debian system running Python 3.9.2

Also, in the same example, this appears twice in 1_phase_viz.py:

vel_mesh = vel_mesh.get_array('velocityNorm').reshape([nz, ny, nx+n_slices*2])

As shipped, this returns 100, 100, 102, but it should be 100, 100, 104. This was pretty easy to sort out, but there is, perhaps an incorrect assumption there.

Best regards,

James Guilkey
University of Utah

@je-santos
Copy link
Owner

Hi James,

Thanks for you interest in the codebase.
It seems that you were having trouble with the pypardiso package. I don't even know where is that used. I'm glad that you were able to sort the errors out.

Best,
Javier

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants