-
Notifications
You must be signed in to change notification settings - Fork 156
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
Future functionality for IntrinsicTriangulation IO #166
Comments
I think I almost managed to do the above without any change to the existing code. The only issue is the BaseGeometryInterface has a reference to the intrinsic mesh in IntrinsicTriangulation that fails to be corrected (and I have no way to change without modifying the class(es)). Everything else I was about to restore I believe.
|
Any thoughts on this? Saving and loading Intrinsic Triangulations would be incredibly useful. My application inserts up to a million intrinsic vertices and takes a long time to reconstruct from the initial Extrinsic mesh |
Hey,
My application requires saving the mesh connectivity, mesh geometry, and mesh data for intrinsic triangulation on top of extrinsic input meshes. I tried using RichSurfaceMeshData and creating the intrinsic geometry elements and properties (ply file format); however, there is no way (at least I can see) of restoring the intrinsic triangulation alongside the extrinsic data without saving the history of how the triangulation was formed. My intent was to save a ply with both the input extrinsic structure and the input triangulation(s). Is there any future work for improving the IO of the GC structures?
Jeffrey Layton
The text was updated successfully, but these errors were encountered: