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

non-rigid icp computing the wrong edge triangles? #55

Open
HaoyangWang opened this issue Apr 17, 2018 · 2 comments
Open

non-rigid icp computing the wrong edge triangles? #55

HaoyangWang opened this issue Apr 17, 2018 · 2 comments

Comments

@HaoyangWang
Copy link

edge_tris = source.boundary_tri_index()

Although the edge constraint is disabled in the code, the edge triangles should be computed on the target mesh instead of the source.

@Mad-Thanos
Copy link

I guess the following line is also incorrect:

w_i_e = np.in1d(tri_indices, edge_tris, invert=True)

the tri_indices contains triangle indices into the facet array of the target mesh, but the edge_tris is an array of boolean values. The np.in1d() does not work that way, right?

So actually at runtime, the w_i_e array is always all True.

@Mad-Thanos
Copy link

May I ask, why was the edge constraint disabled?

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