Nicholas Sharp

Hi! Thanks for opening this. I'm interested in merging this, the fast method seems quite nice. I am a liiiiitle wary because the existing colPivQR approach was very extensively numerically...

Hi! I have no idea, I haven't heard anything about it since Math first created it. Perhaps worth reaching out http://mathwhittakerdesign.co.uk/ComputationalDesign.html ? If Math has moved on from the project,...

(long delayed response in case others hit this problem) I think you might be able to get this result via `find_geodesic_path_poly()` , by passing a list `[start_point, a, b, start_point]`,...

(pardon the slow response!) This makes sense. In the underlying C++ code, this is tracked via a `SurfacePoint` class --- we could expose that class in these python bindings to...

(long-delayed response in case it's useful for others) I'd suggest simply calling these algorithms in a for-loop over all vertices. The underlying algorithms do not have offer any special accelerations...

Hi! Pardon the slow response here, I missed this issue. Unfortunately the short answer is that almost nothing in geometry-central is guaranteed to be thread safe. There are a few...

I believe accessing/reading/writing elements in a `MeshData` container should be thread-safe. At that point it's just a decorator over access into the underlying `Eigen` array. The only problems should arise...

Hi David, very happy to hear it, it would be great to get this in! I don't have a ton of time these days, but happy to help how I...

Hi @DavidJourdan thanks again for this! I went ahead and merged this since the code looks pretty polished :) Hopefully it can be useful to others. However, I tried running...

Oh yeesh, not using the 2 RoSy field was a bad mistake! Thanks for pointing that out, I can confirm that it's producing much more sane outputs with that fix...