matplotlib-devel Mailing List for matplotlib (Page 107)

Brought to you by: cjgohlke, dsdale, efiring, heeres, and 8 others

matplotlib-devel — matplotlib developers

You can subscribe to this list here.

2003	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (1)	Nov (33)	Dec (20)
2004	Jan (7)	Feb (44)	Mar (51)	Apr (43)	May (43)	Jun (36)	Jul (61)	Aug (44)	Sep (25)	Oct (82)	Nov (97)	Dec (47)
2005	Jan (77)	Feb (143)	Mar (42)	Apr (31)	May (93)	Jun (93)	Jul (35)	Aug (78)	Sep (56)	Oct (44)	Nov (72)	Dec (75)
2006	Jan (116)	Feb (99)	Mar (181)	Apr (171)	May (112)	Jun (86)	Jul (91)	Aug (111)	Sep (77)	Oct (72)	Nov (57)	Dec (51)
2007	Jan (64)	Feb (116)	Mar (70)	Apr (74)	May (53)	Jun (40)	Jul (519)	Aug (151)	Sep (132)	Oct (74)	Nov (282)	Dec (190)
2008	Jan (141)	Feb (67)	Mar (69)	Apr (96)	May (227)	Jun (404)	Jul (399)	Aug (96)	Sep (120)	Oct (205)	Nov (126)	Dec (261)
2009	Jan (136)	Feb (136)	Mar (119)	Apr (124)	May (155)	Jun (98)	Jul (136)	Aug (292)	Sep (174)	Oct (126)	Nov (126)	Dec (79)
2010	Jan (109)	Feb (83)	Mar (139)	Apr (91)	May (79)	Jun (164)	Jul (184)	Aug (146)	Sep (163)	Oct (128)	Nov (70)	Dec (73)
2011	Jan (235)	Feb (165)	Mar (147)	Apr (86)	May (74)	Jun (118)	Jul (65)	Aug (75)	Sep (162)	Oct (94)	Nov (48)	Dec (44)
2012	Jan (49)	Feb (40)	Mar (88)	Apr (35)	May (52)	Jun (69)	Jul (90)	Aug (123)	Sep (112)	Oct (120)	Nov (105)	Dec (116)
2013	Jan (76)	Feb (26)	Mar (78)	Apr (43)	May (61)	Jun (53)	Jul (147)	Aug (85)	Sep (83)	Oct (122)	Nov (18)	Dec (27)
2014	Jan (58)	Feb (25)	Mar (49)	Apr (17)	May (29)	Jun (39)	Jul (53)	Aug (52)	Sep (35)	Oct (47)	Nov (110)	Dec (27)
2015	Jan (50)	Feb (93)	Mar (96)	Apr (30)	May (55)	Jun (83)	Jul (44)	Aug (8)	Sep (5)	Oct	Nov (1)	Dec (1)
2016	Jan	Feb	Mar (1)	Apr	May	Jun (2)	Jul	Aug (3)	Sep (1)	Oct (3)	Nov	Dec
2017	Jan	Feb (5)	Mar	Apr	May	Jun	Jul (3)	Aug	Sep (7)	Oct	Nov	Dec
2018	Jan	Feb	Mar	Apr	May	Jun	Jul (2)	Aug	Sep	Oct	Nov	Dec

Flat | Threaded

<< < 1 .. 105 106 107 108 109 .. 554 > >> (Page 107 of 554)

Re: [matplotlib-devel] 1.1.1rc does not fix tight_layout for figtext?

From: Jae-Joon L. <lee...@gm...> - 2012-03-28 12:59:46

I'm afraid that, unfortunately, it won't be fixed soon (if ever, as
far as I can tell).
What "tight_layout" does is to adjust the *subplot parameters* of the
figure so that the "subplots" fit in. Artists created with figtext
command is not affected by the subplot parameters, i.e. there is not
much thing we can do for these artists within the current
implementation. It would be better if some warning is printed in such
case (there are lots of cases that tight_layout will fail), but this
is not currently done.

Depending on your need, you may leave out some area for figtext when
you call "tight_layout". This is only supported for gridspec though.

import matplotlib.pyplot as plt
import matplotlib.gridspec as gridspec

fig = plt.figure()

gs1 = gridspec.GridSpec(2, 2)
ax_list = [fig.add_subplot(ss) for ss in gs1]

fig.text (02, 0, "test", horizontalalignment='left',
          verticalalignment='bottom', size=5)
fig.text (0.5, 1, "01", horizontalalignment='left',
          verticalalignment='top', size='x-small')

gs1.tight_layout(fig, rect=[0, 0.03, 1, 0.97]) # adjust rect parameter
to make some room for figtext.

Regards,

-JJ

On Wed, Mar 28, 2012 at 9:17 PM, Neal Becker <ndb...@gm...> wrote:
> I just tried 1.1.1rc to see if it fixed the tight_layout for figtext.
>
> I have a semilogy plot, and add  some lines of text on the bottom (and top):
>
>        plt.figtext (0, 0, res['carriers'].values, horizontalalignment='left',
> verticalalignment='bottom', size=5)
>        plt.figtext (0.5, 1, self.pageno, horizontalalignment='left',
> verticalalignment='top', size='x-small')
>        ##plt.tight_layout(pad=1.0)
>        plt.tight_layout()
>
> The text on the bottom is overprinting the x axis - the same as happened  with
> the previous release.
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

[matplotlib-devel] 1.1.1rc RuntimeError: underlying C/C++ object has been deleted

From: Neal B. <ndb...@gm...> - 2012-03-28 12:34:39

I'm getting these messages, which did not occur with 1.1:

Traceback (most recent call last):
  File "/home/nbecker/.local/lib/python2.7/site-
packages/matplotlib/backends/backend_qt4.py", line 151, in <lambda>
    lambda: self.close_event())
  File "/home/nbecker/.local/lib/python2.7/site-
packages/matplotlib/backend_bases.py", line 1564, in close_event
    self.callbacks.process(s, event)
RuntimeError: underlying C/C++ object has been deleted

[matplotlib-devel] 1.1.1rc does not fix tight_layout for figtext?

From: Neal B. <ndb...@gm...> - 2012-03-28 12:17:35

I just tried 1.1.1rc to see if it fixed the tight_layout for figtext.  

I have a semilogy plot, and add  some lines of text on the bottom (and top):

        plt.figtext (0, 0, res['carriers'].values, horizontalalignment='left', 
verticalalignment='bottom', size=5)
        plt.figtext (0.5, 1, self.pageno, horizontalalignment='left', 
verticalalignment='top', size='x-small')
        ##plt.tight_layout(pad=1.0)
        plt.tight_layout()

The text on the bottom is overprinting the x axis - the same as happened  with 
the previous release.

Re: [matplotlib-devel] Using `hexbin` with `edgecolors = 'none'`

From: Tony Yu <ts...@gm...> - 2012-03-27 14:00:14

On Mon, Mar 26, 2012 at 7:42 PM, Tony Yu <ts...@gm...> wrote:

> I'm drawing hexbins with alpha < 1 and get dark lines at the bin edges. It
> turns out that setting `edgecolors = 'none'` sets the edge color to be the
> same as the face color, as mentioned in the docstring:
>
>            If ``'none'``, draws the edges in the same color as the fill
> color.
>            This is the default, as it avoids unsightly unpainted pixels
>            between the hexagons.
>
> This behavior is a bit weird, since setting colors to 'none' usually makes
> the element invisible. Wouldn't it be more consistent to let 'none' be
> passed to the PolyCollection (which draws the hexbins), such that edges
> aren't drawn. Then, to maintain the current behavior, change the default to
> 'face'. (Of course, this wouldn't really maintain current behavior for code
> that explicitly passes `edgecolors='none'`.)
>
> Also, if I let 'none' get passed to the PolyCollection, I don't see the
> "unsightly unpainted pixels between the hexagons". Is this just a
> system-dependent artifact, or is it an outdated docstring?
>
> Thanks,
> -Tony
>

Just to clarify, here's an example of how I think hexbin should behave:
https://github.com/tonysyu/matplotlib/commit/39e28540d30a55c18975533fe3625c47506c5908

-Tony