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

Exisiting Triangulation #1

Open
rmchurch opened this issue Aug 18, 2015 · 2 comments
Open

Exisiting Triangulation #1

rmchurch opened this issue Aug 18, 2015 · 2 comments
Assignees

Comments

@rmchurch
Copy link

Nice work, this was quite the undertaking. I don't have a firm grasp on the code yet, but could it be sped up if there is an exisiting triangulation? (i.e. can I get rid of the Delaunay calls if I have by own triObj = Triangulation(x,y) and I normally call plt.tricontourf(triObj,data)). My hope was in cases such as animations of a stack of images of data on a triangulated mesh, this could perhaps significantly speed up the animation.

@asher-pembroke
Copy link
Owner

Thanks! Yes, I think it's feasible to use a pre-computed triangulation and call tricontourf instead (I didn't even know that function existed!). I'll look at the output from tricontourf: hopefully the paths will work the same. Thanks for the suggestion!

@asher-pembroke
Copy link
Owner

This enhancement seems a bit subtler than I thought. The problem is that the contour vertices are not in the graph of your triangulation, but they probably lie somewhere along on the triangulation edges. Maybe there's a way to identify which edges each contour vertex belongs to, then find the paths that join different contours. I will have to think about it more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants