-
Notifications
You must be signed in to change notification settings - Fork 157
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
Grid3D broken by numpy 1.10 #475
Comments
guyer
added a commit
that referenced
this issue
Nov 25, 2015
This never should have worked, but numpy 1.10 actually checks. Also provide some documentation for what `_faceToCellDistanceRatio` is and why it's scalar. Addresses #475
This was referenced Nov 25, 2015
pkgw
added a commit
to pkgw/fipy
that referenced
this issue
Dec 9, 2015
…() calls As far as I can tell, there were several codepaths in the UniformGrid3D class that seemed not to have been tested since they didn't work at all; in particular, the _cellToCellIDs map was broken. This commit fixes that (I hope) and a couple of more invalid `axis=n` keywords to `numerix.concatenate()`. Unfortunately I have not put together test cases for these problems, so I'm not completely sure that the "fixed" _cellToCellIDs is always correct. See issue usnistgov#470, issue usnistgov#475, and issue usnistgov#477.
guyer
pushed a commit
that referenced
this issue
Dec 27, 2015
…() calls As far as I can tell, there were several codepaths in the UniformGrid3D class that seemed not to have been tested since they didn't work at all; in particular, the _cellToCellIDs map was broken. This commit fixes that (I hope) and a couple of more invalid `axis=n` keywords to `numerix.concatenate()`. Unfortunately I have not put together test cases for these problems, so I'm not completely sure that the "fixed" _cellToCellIDs is always correct. See issue #470, issue #475, and issue #477.
This seems to still be an issue on clean pip installations, tentatively fixed by removing axis=1 parameter on line 279, uniformGrid3D.py |
For anybody reading in 2018, the issue is actually solved in the development branch (not by me, just to be clear) but not in the version you get when installing via pip. You will have to clone from git, checkout development and build with python setup.py install |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of numpy 1.10, any uses of
Grid3D
fail, e.g.The issue is that
numerix.ravel
returns a 1Darray
and soaxis=1
is nonsensical in_faceToCellDistanceRatio
. It looks like this was always wrong (going back to at least 2011), but numpy tolerated it until now.Probably safe to just remove the
axis=1
argument, but need to test.The text was updated successfully, but these errors were encountered: