Optimize Poly3DCollection.get_vector for ndarray arguments #16680
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds some extra code-paths, which take advantage of the fact that the input polygons have the same number of vertices and are already in a NumPy array.
|
Superseded by #16688 |
|
(You can force-push to the same branch to reuse the PR.) |
|
I know, but I've decided to take a completely different approach, so I figured it might be better to create a new one. It needed a whole new description, etc. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
This adds some extra code-paths, which take advantage of the fact that
the input polygons have the same number of vertices and are already
in a NumPy array.
Saves 0.3s for a 400x400 surface plot on my old MBP. This continues the series of patches from #16659.
PR Checklist