#5448: [with patch, needs work] rework save/show in plot, use Matplotlib's axes
code, upgrade matplotlib
-------------------------+--------------------------------------------------
Reporter: mhansen | Owner: mhansen
Type: enhancement | Status: assigned
Priority: major | Milestone: sage-4.1.2
Component: graphics | Keywords:
Reviewer: | Author:
Merged: |
-------------------------+--------------------------------------------------
Comment(by kcrisman):
Okay, first off patch needs work if only because it does not apply to
4.1.1! Fix is to correct all spellings of "apect" in the patch to
"aspect" and to replace one instance of "png's" at the end to "PNG's".
Also, eventually presumably axes.py should go to dev/null, right? I also
get a bunch of deprecation warnings, but presumably that is known.
As to the stuff itself:
1. When using pointsize, matplotlib axes (or the way in which they are
used) has some whitespace cutting off points, for example when pointsize
is large (20 worked for me, but unfortunately I can't cut and paste and
example here).
2. I'm not sure I like the non-intersecting axes on regular plots. That
is weird, especially in graphs like the plot of x squared type things.
plot(x**2,0,1) looks great; plot(x**2,-1,1) looks... interesting.
3. For some reasons, showing some plots yields the #5956 ValueError of
"ValueError: width and height must each be below 32768" which apparently
comes from matplotlib/backends/backend_agg.py, the RendererAgg (whatever
that is). I should point out these are plots which worked before.
Apparently it has something to do with adding axes_labels, because without
them, this problem does not appear. Did something get a LOT bigger on the
axis labels?
4. The two zeros where axes intersect is distracting. I'm not sure what
else to say about that, other than that it's true. This is especially
true when the graph gets close to the origin. Of course, the reason for
labeling it has been discussed elsewhere - it just may have to get
"smart". Maybe when the origin IS the intersection point of the axes (as
one might expect), this could be tacitly omitted?
5. For some reason William's example in some talk where he does a little
eye candy with image manipulation (e.g., "compressed using x eigenvalues")
doesn't work right; only the second matrix_plot works properly, the other
one does not. So something with the new axes and frame isn't working
right.
6. Ironically, switching slope fields to normal (not frame) axes is worse,
because it's hard to see the numbers with any reasonably density of the
points for the slopes.
7. This is just a question: is it possible to get custom labeling for axis
numbering now in matrix plots? E.g., (!) if I am taking just the 4th-6th
powers of some numbers and plotting them in a grid, can I label those
columns as 4-6? I don't know if mpl has this; the axes_grid thing on the
website looked conceivably related, maybe even good for matrix_plot or
multiple graphics.
But great work notwithstanding! Looking forward to whatever comes out of
this ticket, and the mpl upgrade seems nice.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5448#comment:10>
Sage <http://sagemath.org/>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
