-
Notifications
You must be signed in to change notification settings - Fork 58
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
signed_distance and barycentric_coordinates_tri crash kernel #33
Comments
can you provide with the example and data? |
So I try to find the triangle to closest point on the mesh (attached) for the following points:
Then for the barycentric coordinates of my point
|
I tried and this works for me
|
ok so it seems like it had to do with the format of the data I input. |
Yes, we are working on that. The problem is that most igl function are designed for |
You are right that we should not crash with badly shaped inputs! Keep in mind that these python bindings are still in beta (we're still version 0.4!) so issues like this may arise. We really appreciate you reporting any problems we run into, and we'll do our best to resolve them :) |
I just pushed a new version on conda 4.1.1. Now it should print an error in case of wrong sizes. The new version is building and should take 1h for unix and 2h for windows |
Nice! I'm very appreciative of your work. |
I have now a problem with signed_distance() which crashes my jupyter kernel for some points. I don't get any error message I only get "The kernel appears to have died. It will restart automatically".
And for barycentric_coordinates_tri() it always crashes the kernel, even for the points for which I could identify the closest point and triangle they belong to with signed_distance().
Do you have any idea about what could be the problem ?
Thanks for your help
The text was updated successfully, but these errors were encountered: