3
$\begingroup$

NB- see this question for a more formal request.

For many many years (honestly, since 1987) I've had my own MMa computational geometry code for dealing with 3D meshes. I principally (there's a joke there somewhere) use it to calculate coordinate frames / curvatures at the discrete vertex positions, etc.

The introduction of MeshRegion[] in 10.x seems to make my some of my code redundant (thankfully!) but I'm not 100% sure how to proceed.

I can imagine a few things, like computing and saving useful information about the vertices (coordinate frame, curvatures, etc) as Property[] for each vertex, but computing that stuff (seems like) I'd just do it the old 'discrete' way. I'd also suppose that something along the lines of using NDSolve over the {x,y,z} in the MeshRegion[] would also be useful here.

Has anyone already done/started to do such a thing?

$\endgroup$

closed as too broad by user21, Kuba, m_goldberg, dr.blochwave, MarcoB Oct 7 '15 at 12:32

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    $\begingroup$ More detail would be useful. Perhaps, you could provide the code for some of your functions that you feel may now be redundant. $\endgroup$ – bbgodfrey Mar 24 '15 at 18:15