Philipp Schlegel

Yeah, `skeletor.fix_mesh()` is not a magic bullet unfortunately. I'm a fan of tools doing one thing, and doing that well. `skeletor` already does a bit more than just skeletonising but...

Yeah, let me know what you find. If you are happy sharing one of your meshes, I could have a crack and see how far I get with them. Curious...

Are you referring to the mesh contraction or the edge collapse?

In general, the algorithm presented in the paper leaves a lot of details out which in turn left me to go with my best guess and "whatever works". Hence the...

Hi. Re the `float128` error: What version of Numpy are you running? Re the skeletonization results: It's impossible to tell without inspecting your mesh. It would also be helpful if...

OK, not sure where the np.float128 issue is coming from (possibly platform dependent?) but I'll drop that bit from the code in the next version. Re your mesh: I think...

I guess it depends on your implementation but in general you would need to combine two maps: 1. Vertex to voxel 2. Voxel to pixel in the thinned image The...

Hi. It looks to me like your mesh is not fully connected - i.e. it consists of multiple disconnected shapes that only appear to be a closed surface. `sk.pre.fix_mesh` then...

A single connected component is actually what you want. Could you perhaps share the `Matrixvertices` as a properly formatted list (i.e. with commas) so that I can copy paste them...

Ah OK. So here is the rub: Your set of faces + vertices is disconnected. If you set `process=False` and trimesh does not merge duplicate vertices, you get this: ```Python...