| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
You have a lot of test failures: https://travis-ci.org/matplotlib/matplotlib/jobs/112810572 |
Sorry, something went wrong.
| minz = 1e9 | ||
| for (xs, ys, zs) in xyslist: | ||
| minz = min(minz, min(zs)) | ||
| minz = np.min(xys[:, :, 2]) |
There was a problem hiding this comment.
We are not guaranteed a non-empty array, hence the initialization of minz with 1e9.
Sorry, something went wrong.
|
+1 to this. I still haven't found a good method for plotting 3-D brains w/ points on top of it in python. Making a trisurf is super slow when I have lots of triangles. |
Sorry, something went wrong.
|
Hi, |
Sorry, something went wrong.
|
'power cycled' to restart the CI against current master. |
Sorry, something went wrong.
|
Looks like there is a problem in one of the examples Warning, treated as error:
/home/travis/build/matplotlib/matplotlib/doc/examples/mplot3d/pathpatch3d_demo.rst:8: WARNING: Exception occurred in plotting pathpatch3d_demo
from /home/travis/build/matplotlib/matplotlib/doc/mpl_examples/mplot3d/pathpatch3d_demo.py:
Traceback (most recent call last):
File "/home/travis/build/matplotlib/matplotlib/lib/matplotlib/sphinxext/plot_directive.py", line 654, in render_figures
figman.canvas.figure.savefig(img.filename(format), dpi=dpi)
File "/home/travis/build/matplotlib/matplotlib/lib/matplotlib/figure.py", line 1666, in savefig
self.canvas.print_figure(*args, **kwargs)
File "/home/travis/build/matplotlib/matplotlib/lib/matplotlib/backend_bases.py", line 2227, in print_figure
**kwargs)
File "/home/travis/build/matplotlib/matplotlib/lib/matplotlib/backends/backend_agg.py", line 517, in print_png
FigureCanvasAgg.draw(self)
File "/home/travis/build/matplotlib/matplotlib/lib/matplotlib/backends/backend_agg.py", line 464, in draw
self.figure.draw(self.renderer)
File "/home/travis/build/matplotlib/matplotlib/lib/matplotlib/artist.py", line 68, in draw_wrapper
return draw(artist, renderer, *args, **kwargs)
File "/home/travis/build/matplotlib/matplotlib/lib/matplotlib/figure.py", line 1262, in draw
renderer, self, dsu, self.suppressComposite)
File "/home/travis/build/matplotlib/matplotlib/lib/matplotlib/image.py", line 139, in _draw_list_compositing_images
a.draw(renderer)
File "/home/travis/build/matplotlib/matplotlib/lib/mpl_toolkits/mplot3d/axes3d.py", line 279, in draw
for patch in self.patches]
File "/home/travis/build/matplotlib/matplotlib/lib/mpl_toolkits/mplot3d/axes3d.py", line 279, in <listcomp>
for patch in self.patches]
File "/home/travis/build/matplotlib/matplotlib/lib/mpl_toolkits/mplot3d/art3d.py", line 320, in do_3d_projection
s = np.vstack(self._segments3d, np.ones(self._segments3d.shape[1]))
AttributeError: 'PathPatch3D' object has no attribute '_segments3d'
|
Sorry, something went wrong.
|
I guess my point is more "let's not add more public API". |
Sorry, something went wrong.
|
Hi @AlexandreAbraham |
Sorry, something went wrong.
|
Hi, I ended up here from this paper: https://riojournal.com/articles.php?id=12342 I'd be very interested in using the method in the paper, but I'm finding the speed that it can be accomplished with the current implementation of 3d meshses is a dealbreaker. Is there hope for this PR moving forward? |
Sorry, something went wrong.
|
+1 to this PR moving forward |
Sorry, something went wrong.
|
ok, I'll make it a priority this week during SciPy.
…On Wed, Jul 12, 2017 at 10:11 AM, Chris Holdgraf ***@***.***> wrote:
+1 to this PR moving forward
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6085 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARy-Lv2kePQIHFLTlgb98P4Wy33BQm1ks5sNNQCgaJpZM4HmSzk>
.
|
Sorry, something went wrong.
|
I think that this is the PR that @GaelVaroquaux mentioned to me earlier this week. |
Sorry, something went wrong.
|
lmk if you want someone to usertest this at the sprint. I can bring some brain surfaces :-) |
Sorry, something went wrong.
|
There are several unaddressed comments from @Kojoley . I am currently working on rebasing this as well. I'll force-push a rebase soon (if github allows me). |
Sorry, something went wrong.
|
doesn't look like github will let me, so, I'll do it the old way and submit a PR against your branch. |
Sorry, something went wrong.
|
hmmph, that won't work, either. @AlexandreAbraham , do you see any option to allow maintainers to push changes to your PR on this page? |
Sorry, something went wrong.
| self._segments3d_data = np.vstack(segments) | ||
| # Add a fourth dimension for quaternions | ||
| self._segments3d_data = np.hstack([self._segments3d_data, | ||
| np.ones((n_segments, 1))]) |
There was a problem hiding this comment.
This would be marginally better as
self._segments3d_data = np.empty((n_segments, 4)) self._segments3d_data[:,:3] = segments self._segments3d_data[:,3] = 1
Also, are you sure you mean "quaternion" and not "homogenous coordinate"?
Sorry, something went wrong.
| cum_s = 0 | ||
| for s in self._seg_sizes: | ||
| segments_2d.append(xys[cum_s:cum_s + s, :2]) | ||
| cum_s += s |
There was a problem hiding this comment.
I think this loop is np.split in some form
Sorry, something went wrong.
| tis = vecw[1] < 1 | ||
| vecw /= vecw[3] | ||
| # Integrating tis in the numpy array for optimization purposes | ||
| vecw[3, :] = tis |
There was a problem hiding this comment.
Get rid of this colon - it makes the function fail on 1d inputs
Sorry, something went wrong.
There was a problem hiding this comment.
Storing coordinates in the first axis of the array is kind of unusual (see how np.linalg and scipy.misc.imread behave).
Perhaps these should all be xyz[..., 0] instead of xyz[0]?
Sorry, something went wrong.
|
This seems to have attracted lots of interest, but eventually never made it over the hump. @WeatherGod is there still some hope for this, or has its momment passed? |
Sorry, something went wrong.
|
Perhaps parts of this needs to be separated out into smaller PRs. There is
some good stuff here, but there were also some questionable stuff, too,
that never got addressed.
…On Wed, May 2, 2018 at 1:10 PM, Jody Klymak ***@***.***> wrote:
This seems to have attracted lots of interest, but eventually never made
it over the hump. @WeatherGod <https://github.com/WeatherGod> is there
still some hope for this, or has its momment passed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6085 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARy-ENj7x-jsaEbU7onzowiCV_Giuu8ks5tueiYgaJpZM4HmSzk>
.
|
Sorry, something went wrong.
|
Closing as inactive. The goodies are here for anyone who wants them! |
Sorry, something went wrong.
If it's closed, what's the mechanism then for contributors to know that this PR is stalled, needs help and can be continued ?
Should be allowed by Github by default now.
Maybe someone might be interested in looking into it during the scipy sprint next week? |
Sorry, something went wrong.
|
If I understand correctly this PR rebased (as of July 2017) can be found in @WeatherGod 's https://github.com/WeatherGod/matplotlib/tree/pr/6085 branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
While printing 3D objects, I noticed that the display was pretty slow. The reason is that matplotlib relies a lot on list of objects instead of using big numpy arrays to fasten 3D projections.
This PR aims at solving part of this problem. I replaced some airthmetic on list of vectors by artihmetic on big matrices. This impacts mainly 3D display.
I work on neuroimaging data. I noticed an approximate 25% speedup optimization on 3D display (depending on the complexity of the figure). Refreshment in interactive plotting is also faster. Example script:
Possible other optimizations:
@agramfort and @juhuntenburg, do you notice significant running time reduction with this PR?