-
Notifications
You must be signed in to change notification settings - Fork 132
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
petro.resistivityArchie interpolation returns 'corrupt mesh' error #107
Comments
If you don't updated GIMLI .. I assume your input has been changed .. such spooky behavior seems a little unlikely. The error message says one of the meshes have free nodes (nodes that are not related to the mesh elements). |
You're quite right, something must have changed. I just can't see what exactly... There doesn't seem to be any duplicate sensors in the ertScheme. All of the files are below; Alexs_Main_Workbook - Copy.py.txt Edit; What is the best way to check if free nodes exist?! I can't understand why free nodes should exist on the parameter mesh, as it was generated with the sensor list. It's quite obviously something to do with the interpolation, but I still can't work out why there would be free nodes |
Maybe there are duplicated points in your point cloud? You can count through you mesh nodes e.g.
btw. It would be easier for us to check stuff, if you provide either all meshes or data directly. e.g. to check the command |
In your As this seems to happen regularly .. I think we will drop a Warning about in mt.createPolygon(). If you want to close the polygon set |
Good point - sorry about that. My scripts probably quite poorly written too. It's all a bit intertwined at the moment. I removed those equal points in the hull - I think it may have solved some instability issues I was having when making meshes, (:yay:), but hasn't immediately solved the other issues yet. |
why you don't use |
Sorry. I'd used mesh.saveAscii thinking it would be easier... lol. |
m1 have no cells and hence can't be used for interpolation. |
Thank you. Meshing on that double node was causing my iPython to crash 40% of the time too. Seems stable so far!
|
I'm certain this was working yesterday, and now this morning - it does not!!!!
Why would it say my mesh is now corrupt?!
I've tried re-creating the mesh without additional arguments and still get the error...
meshERT is created from a set of sensors located on the topography.
e.g.
Resulting in the error below;
Winpython-64bit-3.6.2.0Qt5, Spyder 3.2.4, pyGimli-1.0.3-cp36-cp36m-win_amd64.whl
The text was updated successfully, but these errors were encountered: