matplotlib-devel Mailing List for matplotlib

On Sun, May 25, 2008 at 11:50 AM, Tony Yu <ts...@gm...> wrote:
> I must admit, I was a little worried when you suggested adding a big
> equation in the background, but I think you did a good job of making it look
> nice. Unfortunately, I get an error when I try to run the logo2 script:
I'm not wed to it, so just experiment.
> AttributeError: 'NoneType' object has no attribute 'get_ticklabels'
> module body in logo2.py at line 23
> for label in ax.get_xticklabels() + ax.get_yticklabels():
> If I comment-out that for-block, I run into another error:
> NotImplementedError: xlim not meaningful for polar axes
> module body in logo2.py at line 43
> ax.set_xlim(-2*sigma, 2*sigma)
> I'm guessing the first error is a trunk vs. v0_91_maint issue? Is the second
You need to be on the trunk and I think I was a commit behind -- try it now.
We will probably want to set the various ticklabel and title sizes to
something really small using rc
import matplotlib
matplotlib.rcParams['xtick.labelsize'] = 6
so that we can tweak all these in one place at the top of the script.
JDH

On May 25, 2008, at 12:13 PM, John Hunter wrote:
>
> I played around with this a bit this morning -- it may be too busy for
> your OS X sensibilities, but let me know if you think think this is an
> approach wotrh pursuing. I've added the mathtext background and a few
> axes and there are a few more axes to do. In svn as
> examples/api/logo2.py
I must admit, I was a little worried when you suggested adding a big 
equation in the background, but I think you did a good job of making 
it look nice. Unfortunately, I get an error when I try to run the 
logo2 script:
AttributeError: 'NoneType' object has no attribute 'get_ticklabels'
module body in logo2.py at line 23
for label in ax.get_xticklabels() + ax.get_yticklabels():
If I comment-out that for-block, I run into another error:
NotImplementedError: xlim not meaningful for polar axes
module body in logo2.py at line 43
ax.set_xlim(-2*sigma, 2*sigma)
I'm guessing the first error is a trunk vs. v0_91_maint issue? Is the 
second a naming error in the commit? Maybe axhist.set_xlim instead of 
ax.set_xlim?
Overall I really like the new logo, but I'd like play around with it a 
bit for kicks.
Thanks!
-Tony

On Sun, May 25, 2008 at 8:18 AM, John Hunter <jd...@gm...> wrote:
> Also, the banner should be generated as a matplotlib figure rather
> than put together in inkscape or something like that. How did you
> make this -- if is code, please post so we can play along. If not,
> see if you can write the logo example by laying out the axes just so.
I played around with this a bit this morning -- it may be too busy for
your OS X sensibilities, but let me know if you think think this is an
approach wotrh pursuing. I've added the mathtext background and a few
axes and there are a few more axes to do. In svn as
examples/api/logo2.py
JDH
import numpy as np
import matplotlib.pyplot as plt
import matplotlib.cm as cm
import matplotlib.mlab as mlab
axalpha = 0.05
figcolor = '#FFFFCC'
dpi = 80
fig = plt.figure(figsize=(8, 2),dpi=dpi)
fig.figurePatch.set_edgecolor(figcolor)
fig.figurePatch.set_facecolor(figcolor)
# the polar bar plot
ax = fig.add_axes([0.05, 0.05, 0.2, 01], polar=True)
ax.axesPatch.set_alpha(axalpha)
N = 20
theta = np.arange(0.0, 2*np.pi, 2*np.pi/N)
radii = 10*np.random.rand(N)
width = np.pi/4*np.random.rand(N)
bars = ax.bar(theta, radii, width=width, bottom=0.0)
for r,bar in zip(radii, bars):
 bar.set_facecolor( cm.jet(r/10.))
 bar.set_alpha(0.5)
for label in ax.get_xticklabels() + ax.get_yticklabels():
 label.set_visible(False)
# the histogram
axhist = fig.add_axes([0.275, 0.075, 0.2, 0.4])
axhist.axesPatch.set_alpha(axalpha)
mu, sigma = 100, 15
x = mu + sigma*np.random.randn(10000)
# the histogram of the data
n, bins, patches = axhist.hist(x, 50, normed=1, facecolor='green',
edgecolor='green', alpha=0.75)
y = mlab.normpdf( bins, mu, sigma)
l = axhist.plot(bins, y, 'r', lw=1)
axhist.set_title('Density of IQ',fontsize=6)
axhist.set_xlabel('IQ', fontsize=6)
axhist.set_ylabel('P(IQ)', fontsize=6)
ax.set_xlim(-2*sigma, 2*sigma)
for label in axhist.get_xticklabels() + axhist.get_yticklabels():
 label.set_visible(False)
axback = fig.add_axes([0., 0., 1., 1.])
#the math background
tex = r"$W^{3\beta}_{\delta_1 \rho_1 \sigma_2} = U^{3\beta}_{\delta_1
\rho_1} + \frac{1}{8 \pi 2} \int^{\alpha_2}_{\alpha_2} d
\alpha^\prime_2 \left[\frac{ U^{2\beta}_{\delta_1 \rho_1} -
\alpha^\prime_2U^{1\beta}_{\rho_1 \sigma_2} }{U^{0\beta}_{\rho_1
\sigma_2}}\right]$"
axback.text(0.5, 0.5, tex,
 transform=axback.transAxes, color="0.5", alpha=0.5, fontsize=40,
 ha='center', va='center')
axback.set_axis_off()
# the matplotlib title
axback.text(0.3, 0.95, 'matplotlib', color='black', fontsize=75,
 ha='left', va='top', alpha=1.0,
 transform=axback.transAxes)
fig.savefig('logo2.png', facecolor=figcolor, edgecolor=figcolor, dpi=dpi)
plt.show()

On Sat, May 24, 2008 at 11:21 PM, Tony Yu <ts...@gm...> wrote:
> I don't know if you were planning to accept submissions, but here's a logo
> with some of my favorite plots from examples.zip:
Submissions are extremely welcome, and I like the approach. I think
you might experiment with another font for the main text, and try to
incorporate some display of mathtext since this is a real selling
point. We also need one version that is no wider that 200 pages for
the sphinx navigation toolbar, so we will need to be judicious for
that one. But the one for the web page can be much larger, and I like
this as start. Is there anything we can do with the background to
make it a little more interesting? A very large equation that spans
most of the background but is so light in color (a gray with a low
alpha) that it very faint?
Also, the banner should be generated as a matplotlib figure rather
than put together in inkscape or something like that. How did you
make this -- if is code, please post so we can play along. If not,
see if you can write the logo example by laying out the axes just so.
JDH

On May 23, 2008, at 4:34 PM, John Hunter wrote:
> On Fri, May 23, 2008 at 3:31 PM, Darren Dale 
> <dar...@co...> wrote:
>
>> commit yout customizing.txt?
>
> done.
>
> I just discovered l
>
>
> # The name of an image file (within the static path) to place at 
> the top of
> # the sidebar.
> #html_logo = 'logo.png'
>
> so I have to get to work creating a new cool mpl figure for the logo.
> Our old banner is so 70s.
I don't know if you were planning to accept submissions, but here's a 
logo with some of my favorite plots from examples.zip:

On Sat, May 24, 2008 at 6:02 PM, Olle Engdegård <ol...@fy...> wrote:
> I very much miss the 'l' shortcut for toggling log/lin y-scale in the
> trunk! I use it a lot.
>
> I suggest restoring it with something like
>
> if self.get_yscale() is ("log" or "linear"):
> self.toggle_log_lineary()
> else: pass
>
> I think most of time most people use log or linear scales.
This seems reasonable, but when I tried to implement it it looked like
the nan mask for the simple_plot.py example was sticky, eg when I
toggled back to linear the negative values were still masked. I tried
a simpler example still (all positive y data) and got something very
strange: the plotted y values appear to change on a toggle from log
and back to linear:
In [18]: import matplotlib.pyplot as plt
In [19]: plt.close('all')
In [20]: ax = plt.subplot(111)
In [21]: ax.plot(np.random.rand(20))
Out[21]: [<matplotlib.lines.Line2D object at 0x123082f0>]
In [22]: ax.set_yscale('linear'); ax.figure.canvas.draw()
In [23]: ax.set_yscale('log'); ax.figure.canvas.draw()
In [24]: ax.set_yscale('linear'); ax.figure.canvas.draw() # the y
data are now plotted differently
I am not sure what is going on yet, but I'm sure Michael will chime in
since I think we are seeing some funkiness in the new transforms and
path infrastructure.
> The new hist() function looks really good, I especially welcome the "step"
> mode. A couple of comments:
>
> The latest svn incarnation doesn't allow for log scale in step-mode
> (unless you set it manually).
>
> Also, I think the step-mode should have fill=False as default, otherwise
> it does not look that much different from bar-mode. The nice thing about
> step histograms is that you can put several of them in the same plot while
> keeping it intelligible!
Manuel is the developer behind these nice new changes to hist --
hopefully he can help you here.
JDH

On Sat, May 24, 2008 at 6:29 PM, Tony Yu <ts...@gm...> wrote:
> I think this is what you're asking for, but I may have done the diff from
> the wrong directory.
I think the last one was a plain-ol-diff and this one is a svn diff so
it is better. I have applied it and committed it. FYI, I normally do
the svn diff at the same level that the setup.py resides in, but it is
easy enough to correct for,
> One last thing: is there some sort of tutorial for beginners who *may* want
> to contribute. Like a "Getting Started" page for developers. I have tons of
> questions, but I don't want to spam this list. For example: I checked out
> the maintenance version of MPL but the build and install set everything up
> in a new/separate directory. This means my subversion working copy is
> separate from the installed copy (what actually gets imported).
In the svn trunk, there are a few documents in docs/devel (you need a
fesh checkout to find it) that contain coding style guidelines, but
they are rather incomplete. We are in the process of a documentation
push, so we hope to add to these. Your questions are welcome, just
batch them into just one or a few emails rather than a ton of
individual ones. Perhaps one of your first projects can to write the
"getting_started.rst" for the developer's guide as you learn the
ropes. We can all pitch in with answers to your questions... In my
experience, one of the best time to write introductory documentation
is when you are learning something he first time, because the more
seasoned developers have trouble approaching the subject from the
perspective of a beginner.
JDH