SourceForge logo
SourceForge logo
Menu

matplotlib-users — Discussion related to using matplotlib

You can subscribe to this list here.

2003 Jan
Feb
Mar
Apr
May
(3)
Jun
Jul
Aug
(12)
Sep
(12)
Oct
(56)
Nov
(65)
Dec
(37)
2004 Jan
(59)
Feb
(78)
Mar
(153)
Apr
(205)
May
(184)
Jun
(123)
Jul
(171)
Aug
(156)
Sep
(190)
Oct
(120)
Nov
(154)
Dec
(223)
2005 Jan
(184)
Feb
(267)
Mar
(214)
Apr
(286)
May
(320)
Jun
(299)
Jul
(348)
Aug
(283)
Sep
(355)
Oct
(293)
Nov
(232)
Dec
(203)
2006 Jan
(352)
Feb
(358)
Mar
(403)
Apr
(313)
May
(165)
Jun
(281)
Jul
(316)
Aug
(228)
Sep
(279)
Oct
(243)
Nov
(315)
Dec
(345)
2007 Jan
(260)
Feb
(323)
Mar
(340)
Apr
(319)
May
(290)
Jun
(296)
Jul
(221)
Aug
(292)
Sep
(242)
Oct
(248)
Nov
(242)
Dec
(332)
2008 Jan
(312)
Feb
(359)
Mar
(454)
Apr
(287)
May
(340)
Jun
(450)
Jul
(403)
Aug
(324)
Sep
(349)
Oct
(385)
Nov
(363)
Dec
(437)
2009 Jan
(500)
Feb
(301)
Mar
(409)
Apr
(486)
May
(545)
Jun
(391)
Jul
(518)
Aug
(497)
Sep
(492)
Oct
(429)
Nov
(357)
Dec
(310)
2010 Jan
(371)
Feb
(657)
Mar
(519)
Apr
(432)
May
(312)
Jun
(416)
Jul
(477)
Aug
(386)
Sep
(419)
Oct
(435)
Nov
(320)
Dec
(202)
2011 Jan
(321)
Feb
(413)
Mar
(299)
Apr
(215)
May
(284)
Jun
(203)
Jul
(207)
Aug
(314)
Sep
(321)
Oct
(259)
Nov
(347)
Dec
(209)
2012 Jan
(322)
Feb
(414)
Mar
(377)
Apr
(179)
May
(173)
Jun
(234)
Jul
(295)
Aug
(239)
Sep
(276)
Oct
(355)
Nov
(144)
Dec
(108)
2013 Jan
(170)
Feb
(89)
Mar
(204)
Apr
(133)
May
(142)
Jun
(89)
Jul
(160)
Aug
(180)
Sep
(69)
Oct
(136)
Nov
(83)
Dec
(32)
2014 Jan
(71)
Feb
(90)
Mar
(161)
Apr
(117)
May
(78)
Jun
(94)
Jul
(60)
Aug
(83)
Sep
(102)
Oct
(132)
Nov
(154)
Dec
(96)
2015 Jan
(45)
Feb
(138)
Mar
(176)
Apr
(132)
May
(119)
Jun
(124)
Jul
(77)
Aug
(31)
Sep
(34)
Oct
(22)
Nov
(23)
Dec
(9)
2016 Jan
(26)
Feb
(17)
Mar
(10)
Apr
(8)
May
(4)
Jun
(8)
Jul
(6)
Aug
(5)
Sep
(9)
Oct
(4)
Nov
Dec
2017 Jan
(5)
Feb
(7)
Mar
(1)
Apr
(5)
May
Jun
(3)
Jul
(6)
Aug
(1)
Sep
Oct
(2)
Nov
(1)
Dec
2018 Jan
Feb
Mar
Apr
(1)
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
2020 Jan
Feb
Mar
Apr
May
(1)
Jun
Jul
Aug
Sep
Oct
Nov
Dec
2025 Jan
(1)
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
S M T W T F S
1
2
(6)
3
(5)
4
(5)
5
6
7
8
(2)
9
10
(1)
11
(4)
12
(1)
13
14
(2)
15
(1)
16
(3)
17
(5)
18
19
(7)
20
(1)
21
(1)
22
23
(2)
24
(4)
25
(5)
26
(3)
27
28
(3)
29
(3)
30
(5)





Showing 5 results of 5

From: Benjamin R. <ben...@ou...> - 2013年09月17日 16:34:53
On Tue, Sep 17, 2013 at 11:55 AM, Chad Kidder <cck...@gm...> wrote:
> I'm following the MPL Qt4 example given at
> http://matplotlib.org/examples/user_interfaces/embedding_in_qt4.html and
> it looks like I am timing out somewhere in the setup. The error I am
> getting is:
>
> RuntimeError: super-class __init__() of type MyDynamicMplCanvas was never
> called
>
> It's timing out on a function that goes and talks to a piece of test
> equipment to get some data to plot. That function takes on the order of a
> second to complete and is located in compute_initial_figure(self): for the
> previously mentioned class. I will need to make these calls whenever I go
> into the update routine and they may take a few seconds to update.
>
> First, where is the "timeout" that I am violating? Second, how do I fix
> this? Thanks for your help.
>
>
> --Chad Kidder
>
>
Hi Chad,
I think the timeout is right over here:
class MyDynamicMplCanvas(MyMplCanvas):
 """A canvas that updates itself every second with a new plot."""
 def __init__(self, *args, **kwargs):
 MyMplCanvas.__init__(self, *args, **kwargs)
 timer = QtCore.QTimer(self)
 QtCore.QObject.connect(timer, QtCore.SIGNAL("timeout()"),
self.update_figure)
 timer.start(1000)
My suspicion would be to either bump up that timer to take more than a
second, or come up with a different signal function to more intelligently
handle refreshes.
Cheers!
Ben Root
From: Chad K. <cck...@gm...> - 2013年09月17日 15:56:03
I'm following the MPL Qt4 example given at
http://matplotlib.org/examples/user_interfaces/embedding_in_qt4.html and it
looks like I am timing out somewhere in the setup. The error I am getting
is:
RuntimeError: super-class __init__() of type MyDynamicMplCanvas was never
called
It's timing out on a function that goes and talks to a piece of test
equipment to get some data to plot. That function takes on the order of a
second to complete and is located in compute_initial_figure(self): for the
previously mentioned class. I will need to make these calls whenever I go
into the update routine and they may take a few seconds to update.
First, where is the "timeout" that I am violating? Second, how do I fix
this? Thanks for your help.
 --Chad Kidder
From: Nils W. <ni...@go...> - 2013年09月17日 14:19:30
Hi Ben,
It works for me. Thank you very much !
Best wishes
 Nils
On Tue, Sep 17, 2013 at 3:25 PM, Benjamin Root <ben...@ou...> wrote:
>
>
>
> On Tue, Sep 17, 2013 at 4:25 AM, Nils Wagner <ni...@go...>wrote:
>
>> Hi all,
>>
>> How can I modify the grid linewidth and grid line color of an Axes3D
>> object ?
>> is it possible to use white instead of gray for the background color ?
>>
>> The following snippet doesn't show the desired effect.
>>
>> from mpl_toolkits.mplot3d import Axes3D
>> import matplotlib.pyplot as plt
>> fig = plt.figure(figsize=(10,8))
>> ax = fig.gca(projection='3d')
>> ax.grid(color='r',linestyle='-',linewdith=2)
>>
>>
> A (somewhat) undocumented feature (and is not guaranteed to work in the
> future!) is the axis's _axinfo dictionary.
>
> # This is a temporary member variable.
> # Do not depend on this existing in future releases!
> self._axinfo = self._AXINFO[adir].copy()
> self._axinfo.update({'label' : {'space_factor': 1.6,
> 'va': 'center',
> 'ha': 'center'},
> 'tick' : {'inward_factor': 0.2,
> 'outward_factor': 0.1},
> 'ticklabel': {'space_factor': 0.7},
> 'axisline': {'linewidth': 0.75,
> 'color': (0, 0, 0, 1)},
> 'grid' : {'color': (0.9, 0.9, 0.9, 1),
> 'linewidth': 1.0},
> })
>
> where _AXINFO is a class-level attribute defined as:
> # Some properties for the axes
> _AXINFO = {
> 'x': {'i': 0, 'tickdir': 1, 'juggled': (1, 0, 2),
> 'color': (0.95, 0.95, 0.95, 0.5)},
> 'y': {'i': 1, 'tickdir': 0, 'juggled': (0, 1, 2),
> 'color': (0.90, 0.90, 0.90, 0.5)},
> 'z': {'i': 2, 'tickdir': 0, 'juggled': (0, 2, 1),
> 'color': (0.925, 0.925, 0.925, 0.5)},
> }
>
> This information used to be hard-coded throughout the axis3d.py module. I
> consolidated it all into this dictionary for each Axis3D instance. So, you
> should be able to create your Axes3D object, and then do something like the
> following:
>
> ax = fig.gca(projection='3d')
> ax.xaxis._axinfo['grid'].update({'color': 'r', 'linewidth': 2})
> ax.xaxis._axinfo['color'] = 'white'
>
> (Note: untested code!) I don't think the linestyle can be specified,
> though. At some point, I probably should get the Axes3D.grid() function
> defined to mess around with this _axinfo modify the _axinfo dictionary.
>
> I hope that helps!
> Ben Root
>
From: Benjamin R. <ben...@ou...> - 2013年09月17日 13:25:59
On Tue, Sep 17, 2013 at 4:25 AM, Nils Wagner <ni...@go...> wrote:
> Hi all,
>
> How can I modify the grid linewidth and grid line color of an Axes3D
> object ?
> is it possible to use white instead of gray for the background color ?
>
> The following snippet doesn't show the desired effect.
>
> from mpl_toolkits.mplot3d import Axes3D
> import matplotlib.pyplot as plt
> fig = plt.figure(figsize=(10,8))
> ax = fig.gca(projection='3d')
> ax.grid(color='r',linestyle='-',linewdith=2)
>
>
A (somewhat) undocumented feature (and is not guaranteed to work in the
future!) is the axis's _axinfo dictionary.
 # This is a temporary member variable.
 # Do not depend on this existing in future releases!
 self._axinfo = self._AXINFO[adir].copy()
 self._axinfo.update({'label' : {'space_factor': 1.6,
 'va': 'center',
 'ha': 'center'},
 'tick' : {'inward_factor': 0.2,
 'outward_factor': 0.1},
 'ticklabel': {'space_factor': 0.7},
 'axisline': {'linewidth': 0.75,
 'color': (0, 0, 0, 1)},
 'grid' : {'color': (0.9, 0.9, 0.9, 1),
 'linewidth': 1.0},
 })
where _AXINFO is a class-level attribute defined as:
 # Some properties for the axes
 _AXINFO = {
 'x': {'i': 0, 'tickdir': 1, 'juggled': (1, 0, 2),
 'color': (0.95, 0.95, 0.95, 0.5)},
 'y': {'i': 1, 'tickdir': 0, 'juggled': (0, 1, 2),
 'color': (0.90, 0.90, 0.90, 0.5)},
 'z': {'i': 2, 'tickdir': 0, 'juggled': (0, 2, 1),
 'color': (0.925, 0.925, 0.925, 0.5)},
 }
This information used to be hard-coded throughout the axis3d.py module. I
consolidated it all into this dictionary for each Axis3D instance. So, you
should be able to create your Axes3D object, and then do something like the
following:
ax = fig.gca(projection='3d')
ax.xaxis._axinfo['grid'].update({'color': 'r', 'linewidth': 2})
ax.xaxis._axinfo['color'] = 'white'
(Note: untested code!) I don't think the linestyle can be specified,
though. At some point, I probably should get the Axes3D.grid() function
defined to mess around with this _axinfo modify the _axinfo dictionary.
I hope that helps!
Ben Root
From: Nils W. <ni...@go...> - 2013年09月17日 08:25:16
Hi all,
How can I modify the grid linewidth and grid line color of an Axes3D object
?
is it possible to use white instead of gray for the background color ?
The following snippet doesn't show the desired effect.
from mpl_toolkits.mplot3d import Axes3D
import matplotlib.pyplot as plt
fig = plt.figure(figsize=(10,8))
ax = fig.gca(projection='3d')
ax.grid(color='r',linestyle='-',linewdith=2)
Nils

Showing 5 results of 5

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X





Briefly describe the problem (required):
Upload screenshot of ad (required):
Select a file, or drag & drop file here.
Screenshot instructions:

Click URL instructions:
Right-click on the ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Ad destination/click URL:

AltStyle によって変換されたページ (->オリジナル) /