matplotlib-users Mailing List for matplotlib

On Sat, Jul 14, 2012 at 04:09:48PM -0400, Benjamin Root wrote:
> On Saturday, July 14, 2012, John Hunter wrote:
> 
> >
> >
> > On Sat, Jul 14, 2012 at 11:48 AM, John Hunter <jd...@gm...<javascript:_e({}, 'cvml', 'jd...@gm...');>
> > > wrote:
> >
> >> I do not understand why in the following example, if I set
> >> patch_alpha=1.0, I do not see the shadow effect. I would expect to see it
> >> for the the rightmost four bars, where the original bars do not entirely
> >> occlude the shadow, so even if alpha is 1.0, there are parts of the shadow
> >> that are not behind the original bars and should still be visible.
> >>
> >>
> >>
> >
> > I now see that this line explains the behavior
> >
> >
> > https://github.com/matplotlib/matplotlib/blob/master/lib/matplotlib/patheffects.py#L183
> >
> > gc0.set_alpha(1.-self._patch_alpha)
> >
> > so maybe I should amend my question: is this desirable that the shadow
> > alpha is 1-patch_alpha, since an alpha of 1 on the patch does not imply
> > that there is no visible shadow?
> >
> >
> 
> I would argue that the shadow's alpha should equal the patch's alpha. The
> more opaque the patch, the less light that should get through. Could there
I am inclined to agree here. Should it instead be:
gc0.set_alpha(self._patch_alpha)?
> have been an alpha blending reason for this?
> 
> Ben Root
-- 
Damon McDougall
http://damon-is-a-geek.com
B2.39
Mathematics Institute
University of Warwick
Coventry
West Midlands
CV4 7AL
United Kingdom

So, I have
[code]
from mpl_toolkits.mplot3d import axes3d
fig = plt.figure(figsize=(10,7))
ax = fig.gca(projection='3d')
ax.scatter(xs, ys, zs, c='r')
plt.show()
[/code]
but when the figure first comes up, it is not to my liking; when I
interactively (with the mouse) move it around to my liking, the lower right
corner of the window displays: "azimuth=20 deg, elevation=35 deg...
...how can I achieve my desired azimuth, elevation from the beginning? is it
possible to set it up? I search the on-line docs and found nothing.
thanks,
gsal
-- 
View this message in context: http://old.nabble.com/axes3d%2C-initial-azimuth-and-elevation-tp34161970p34161970.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Saturday, July 14, 2012, John Hunter wrote:
>
>
> On Sat, Jul 14, 2012 at 11:48 AM, John Hunter <jd...@gm...<javascript:_e({}, 'cvml', 'jd...@gm...');>
> > wrote:
>
>> I do not understand why in the following example, if I set
>> patch_alpha=1.0, I do not see the shadow effect. I would expect to see it
>> for the the rightmost four bars, where the original bars do not entirely
>> occlude the shadow, so even if alpha is 1.0, there are parts of the shadow
>> that are not behind the original bars and should still be visible.
>>
>>
>>
>
> I now see that this line explains the behavior
>
>
> https://github.com/matplotlib/matplotlib/blob/master/lib/matplotlib/patheffects.py#L183
>
> gc0.set_alpha(1.-self._patch_alpha)
>
> so maybe I should amend my question: is this desirable that the shadow
> alpha is 1-patch_alpha, since an alpha of 1 on the patch does not imply
> that there is no visible shadow?
>
>
I would argue that the shadow's alpha should equal the patch's alpha. The
more opaque the patch, the less light that should get through. Could there
have been an alpha blending reason for this?
Ben Root

On Sat, Jul 14, 2012 at 11:48 AM, John Hunter <jd...@gm...> wrote:
> I do not understand why in the following example, if I set
> patch_alpha=1.0, I do not see the shadow effect. I would expect to see it
> for the the rightmost four bars, where the original bars do not entirely
> occlude the shadow, so even if alpha is 1.0, there are parts of the shadow
> that are not behind the original bars and should still be visible.
>
>
>
I now see that this line explains the behavior
https://github.com/matplotlib/matplotlib/blob/master/lib/matplotlib/patheffects.py#L183
 gc0.set_alpha(1.-self._patch_alpha)
so maybe I should amend my question: is this desirable that the shadow
alpha is 1-patch_alpha, since an alpha of 1 on the patch does not imply
that there is no visible shadow?

I do not understand why in the following example, if I set patch_alpha=1.0,
I do not see the shadow effect. I would expect to see it for the the
rightmost four bars, where the original bars do not entirely occlude the
shadow, so even if alpha is 1.0, there are parts of the shadow that are not
behind the original bars and should still be visible.
import matplotlib.pyplot as plt
import matplotlib.patheffects as PathEffects
import numpy as np
np.random.seed(2358)
fig = plt.figure()
# sime bar shadows
x = np.random.randn(1000)
n, bins, patches = plt.hist(x, bins=7)
shadow = PathEffects.withSimplePatchShadow(offset_xy=(10,-10),
patch_alpha=0.8, shadow_rgbFace=(0.25,0.25,0.25))
for p in patches:
 p.set_path_effects([shadow])
plt.show()

On 7/14/12 8:27 AM, Stefan Mertl wrote:
> What's the reason for the reduction to 0/0? I'm going to create some
> interactive maps. For this it would be easier to have the original
> projected coordinates as the coordinates of the map axes.
> Would it be possible to add a flag to decide if the coordinates should
> be reduced or not?
>
> Regards,
> Stefan.
Stefan: I had to standardize the plotting methods around a specific 
convention, and that seemed as good a one as any. I would suggest you 
override __call__ method to do the transformation for you (as 
illustrated in the utmtest.py example).
-Jeff
>
> On Fri, 2012年07月13日 at 21:26 -0600, Jeff Whitaker wrote:
>> On 7/13/12 8:18 AM, Stefan Mertl wrote:
>>> The UTM support is great. Thanks for that.
>>> Is there a possibility to display the projected coordinates without the
>>> reduction of the x/y coordinates to 0/0 in the left bottom corner?
>>>
>>> Regards
>>> Stefan.
>> Stefan: No - that's the only coordinate system Basemap supports.
>>
>> -Jeff
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Matplotlib-users mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>

What's the reason for the reduction to 0/0? I'm going to create some
interactive maps. For this it would be easier to have the original
projected coordinates as the coordinates of the map axes. 
Would it be possible to add a flag to decide if the coordinates should
be reduced or not? 
Regards,
 Stefan.
On Fri, 2012年07月13日 at 21:26 -0600, Jeff Whitaker wrote:
> On 7/13/12 8:18 AM, Stefan Mertl wrote:
> > The UTM support is great. Thanks for that.
> > Is there a possibility to display the projected coordinates without the
> > reduction of the x/y coordinates to 0/0 in the left bottom corner?
> >
> > Regards
> > Stefan.
> 
> Stefan: No - that's the only coordinate system Basemap supports.
> 
> -Jeff
> >
> >
> > ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 

Hi Josh,
I am not quite sure what information you need, but I have an application with several wx notebooks, each with pages carrying related but different 2D and 3D plots. I hope this overview covers what you want. In the code below I set up the axes and toolbar in each panel ready to accept plots as required. I use wxFormbuilder to create MyFrame1 and then this code to add graphs and other functionality. The 'tickle' function is called when a notebook is selected for display.
import wx
from matplotlib.backends.backend_wxagg import FigureCanvasWxAgg as FigureCanvas
from matplotlib.backends.backend_wxagg import NavigationToolbar2WxAgg
from matplotlib.figure import Figure
from mpl_toolkits.mplot3d import Axes3D
class ProjectFrame(bare_gui.MyFrame1):
 def __init__( self, parent):
 bare_gui.MyFrame1.__init__( self, parent)
...
 self.Create2DGraph(self.CT_graph_1, "Current / %")#CT notebook
 self.Create2DGraph(self.VT_graph_1, "Voltage/ %")#VT notebook
...
 self.Show(True)
 def Create2DGraph(self, panel, xlabel):
 panel.figure = Figure(None)
 panel.canvas = FigureCanvas(panel, -1, panel.figure)
 panel.axes1 = panel.figure.add_subplot(2,1,1)
 panel.axes2 = panel.figure.add_subplot(2,1,2)
 panel.axes1.set_xlabel(xlabel)
 panel.axes1.set_ylabel('Error / %')
 panel.axes2.set_xlabel(xlabel)
 panel.axes2.set_ylabel('Phase / crad')
 panel.sizer = wx.BoxSizer(wx.VERTICAL)
 panel.sizer.Add(panel.canvas, 1, wx.LEFT | wx.TOP | wx.GROW)
 panel.SetSizer(panel.sizer)
 panel.Fit()
 self.add_2Dtoolbar(panel)
 def add_2Dtoolbar(self, panel):
 panel.toolbar = NavigationToolbar2WxAgg(panel.canvas)
 panel.toolbar.Realize()
 tw, th = panel.toolbar.GetSizeTuple()
 fw, fh = panel.canvas.GetSizeTuple()
 panel.toolbar.SetSize(wx.Size(fw, th))
 panel.sizer.Add(panel.toolbar, 0, wx.LEFT | wx.EXPAND)
 # update the axes menu on the toolbar
 panel.toolbar.update()
 def Create3DGraph(self, panel):
 panel.figure = Figure(None)
 panel.canvas = FigureCanvas(panel, -1, panel.figure)
 panel.ax = Axes3D(panel.figure)
 #these labels should be selected later for specific components
 panel.ax.set_xlabel('Current / %')
 panel.ax.set_ylabel('Phase / degree')
 panel.ax.set_zlabel('Error / %')
 panel.sizer = wx.BoxSizer(wx.VERTICAL)
 panel.sizer.Add(panel.canvas, 1, wx.LEFT | wx.TOP | wx.GROW)
 panel.SetSizer(panel.sizer)
 panel.Fit()
 self.add_2Dtoolbar(panel)
________________________________
From: Joshua Koehler [jjk...@gm...]
Sent: Friday, 13 July 2012 10:45 p.m.
To: mat...@li...
Subject: Re: [Matplotlib-users] wxpython matplotlib figure resize
Hi Keith,
How are you storing the plot in the frame/panel?
Josh
On Jul 12, 2012, at 11:59 PM, Keith Jones wrote:
Hi Josh,
Yes I too am using the wx backend.
Regards,
Keith
________________________________
From: Tony Yu [mailto:ts...@gm...]
Sent: Friday, 13 July 2012 3:16 p.m.
To: Keith Jones
Cc: Joshua Koehler; mat...@li...<mailto:mat...@li...>
Subject: Re: [Matplotlib-users] wxpython matplotlib figure resize
On Thu, Jul 12, 2012 at 9:27 PM, Keith Jones <K....@ir...<mailto:K....@ir...>> wrote:
Hi,
I am interested in a better solution to this problem, but I have used this simple method to force the right size.
 def tickle(self):
 #gets frame to redraw and resize, not elegant.
 if self.IsMaximized(): #then needs a kick
 self.Restore()
 self.Maximize()
 else:
 x,y = self.GetSize()
 self.SetSize((x-1, y-1))
 self.SetSize((x, y))
Regards,
Keith
________________________________
From: Joshua Koehler [mailto:jjk...@gm...<mailto:jjk...@gm...>]
Sent: Saturday, 7 July 2012 1:51 a.m.
To: mat...@li...<mailto:mat...@li...>
Subject: [Matplotlib-users] wxpython matplotlib figure resize
Hi all,
I am currently trying to use matplotlib with wxPython and all is going well except for one annoying issue that I can't figure out.
I initialize a wxcanvas object with a figure and then throughout the life of the program I want the canvas' figure to change and display the corresponding plot. I can get the change of figure, but when the program goes to plot, the figure isn't the right size. It changes to the right size only when I manually resize the figure (see attached images). Is there some command that I am missing? This is the update sequence I am using:
self.figure = figure
 self.canvas.figure.clear()
 self.canvas.figure = self.figure
 self.canvas.draw()
 self.color_background()
 #self.GetParent().Layout()
 #self.SetSizer(self.main_sizer)
 #self.Fit()
 self.SendSizeEvent()
As you can tell from the comments (there are more in my code), I have tried a variety of ways to update the figure off the bat.
Thanks!
Josh
This may be similar to a Qt-backend bug, which didn't take the toolbar into account when resizing the figure:
https://github.com/matplotlib/matplotlib/pull/756
It doesn't quite fit, though, because Josh's original example shows a figure that's the correct size (but the axes doesn't fill the figure). The toolbar issue tended to squish the axes in the vertical direction (at least in the GUI window), whereas Josh's example is squished in the horizontal direction.
Keith: Are you also using the Wx-backend? I don't have Wx installed so I can't provide much help. I've been planning to take a look at a similar issue in the Tk backend, but haven't had time.
Best,
-Tony
________________________________
This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.

On 7/13/12 8:18 AM, Stefan Mertl wrote:
> The UTM support is great. Thanks for that.
> Is there a possibility to display the projected coordinates without the
> reduction of the x/y coordinates to 0/0 in the left bottom corner?
>
> Regards
> Stefan.
Stefan: No - that's the only coordinate system Basemap supports.
-Jeff
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

On Fri, Jul 13, 2012 at 7:01 PM, Damon McDougall
<dam...@gm...>wrote:
> On Wed, Jul 11, 2012 at 08:33:21PM -0400, Tony Yu wrote:
> > On Wed, Jul 11, 2012 at 2:28 PM, Benjamin Root <ben...@ou...> wrote:
> >
> > >
> > >
> > > On Wed, Jul 11, 2012 at 11:23 AM, John Hunter <jd...@gm...>
> wrote:
> > >
> > >>
> > >>
> > >> On Wed, Jul 11, 2012 at 10:09 AM, Damon McDougall <
> > >> dam...@gm...> wrote:
> > >>>
> > >>> Well, as Ben said, that error fill plot is neato! It doesn't look too
> > >>> complicated, either. I'd be more than happy to port it over later
> today
> > >>> when I get bored of typing up my thesis. It'll probably only take me
> > >>> about 30 minutes.
> > >>>
> > >>> If nobody is opposed to this idea, I'll go ahead and submit a PR this
> > >>> evening (British Summer (hah!) Time).
> > >>>
> > >>
> > >>
> > >> While it is a nice graph, I am not sure that the use case is common
> > >> enough to justify a new plotting method. One can get the same result
> with:
> > >>
> > >>
> > >> In [68]: x = np.linspace(0, 2 * np.pi)
> > >>
> > >> In [69]: y_sin = np.sin(x)
> > >>
> > >> In [70]: err = np.concatenate([y_sin + 0.2, y_sin[::-1] - 0.2])
> > >>
> > >> In [71]: plot(x, y_sin)
> > >> Out[71]: [<matplotlib.lines.Line2D object at 0x96959ec>]
> > >>
> > >> In [72]: fill_between(np.concatenate([x, x[::-1]]), err,
> > >> facecolor='red', alpha=0.5)
> > >> Out[72]: <matplotlib.collections.PolyCollection object at 0x962758c>
> > >>
> > >> Admittedly the [::-1] thing is a bit counter-intuitive, but rather
> than
> > >> adding a new plotting method, perhaps we would be better off with a
> helper
> > >> method to create the xs and ys for fill_between
> > >>
> > >> xs, ys = mlab.pad_line(x, y, 0.2)
> > >> fill_between(xs, ys)
> > >>
> > >> JDH
> > >>
> > >
> > >
> > > I could definitely agree with a pad_line() function. We might want to
> > > revisit the issue of how much visibility the mlab module should get in
> the
> > > documentation (it currently doesn't get much at all). My whole take on
> > > mlab was that it was a left-over from the days of working around
> issues in
> > > NumPy and SciPy and that it was being slowly phased out. As for other
> > > possible locations, cbook feels like it is more for the devs than for
> the
> > > users, and adding it to pyplot would render the whole purpose of
> creating
> > > this function as opposed to errorfill moot.
> > >
> > > As an additional point about such a pad_line function, it should
> probably
> > > be nice to mirror the errorbar() functionality to allow not only a
> constant
> > > error, but also a N, Nx1, or 2xN array of +/- error. (note that
> errorbar()
> > > for the 2xN array case does -row1 and +row2).
> > >
> >
> > Damon: it sounds like you're volunteering to submit a PR to add this
> > function ;)
> >
> > Here's the relevant bit (which should already handle the cases Ben
> mentions
> > above):
> >
> >
> >
> https://github.com/tonysyu/mpltools/blob/master/mpltools/special/errorfill.py#L54
> >
>
> Great. I've basically done this. I have one suggestion, though. In the
> case where len(zerr) == 2, you are setting
>
> zmin, zmax = zerr
>
> I think it makes more sense to set
>
> zmin, zmax = z - zerr[0], z + zerr[1]
>
> What do you think?
>
Your suggestion would be consistent with how errorbar() works, I think.
Ben Root

http://comidaspopulares.com/yqwpcmdkr/344707.html