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
(5) |
2
(23) |
3
(17) |
4
(14) |
5
(12) |
6
(2) |
7
(3) |
8
(7) |
9
(13) |
10
(19) |
11
(24) |
12
(28) |
13
(9) |
14
(5) |
15
(7) |
16
(17) |
17
(17) |
18
(15) |
19
(6) |
20
|
21
(7) |
22
(20) |
23
(6) |
24
(4) |
25
(5) |
26
(11) |
27
(1) |
28
(2) |
29
(14) |
30
(7) |
|
|
|
|
From: Filipe P. A. F. <oc...@gm...> - 2010-11-15 23:02:25
|
Since you are using OpenSuse, (and If you are brave enough) you can add my REPO and use the latest version of matplolib: http://download.opensuse.org/repositories/home:/ocefpaf/openSUSE_11.3/ I compile the svn version every week there. Filipe. On Mon, Nov 15, 2010 at 13:45, Michael Droettboom <md...@st...> wrote: > Since their package is crashing, I would report this bug against OpenSUSE's python-matplotlib package. > > If that doesn't get you any response, it would be helpful to get a better idea of where it is failing. Can you provide a gdb backtrace? > > Mike > > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > |
From: Chloe L. <ch...@be...> - 2010-11-15 20:10:48
|
I think the pretty-fying done in the Colorbar class will make this harder; at least, twiny on an existing colorbar doesn't work (overwrites original ticks); having two colorbars works fine but wastes space; and adding a spine had surprising side-effects (changed the color range!). I would guess that you want a custom Colorbar class, with a different offset for a second set of ticks. note that in colorbar.py, there's some code specific to CountourSets. &C On Nov 15, 2010, at 15 Nov, 8:22 AM, Daniel Welling wrote: > Greetings. > > I am making some contour plots and in my field for this particular > value, there are two widely used units. As such, it is very useful > to have both units listed on the colorbar. To clarify: the > colorbar's normal ticks would be facing to the right and labeled > with Unit Type 1, which was the units that the data were in when > they were plotted. Unit Type 2 is simply a factor of X different > than unit type two. It would be nice if I could add a second set of > ticks to the color bar using a different locator and have them face > left. Is this possible? Is there another way to display two values > for each tick such that the colorbar shows both units? > > Thanks. > -dw > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev_______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users Chloe Lewis Ecosystem Sciences, Policy and Management, UC Berkeley 137 Mulford Hall Berkeley, CA 94720-3114 http://nature.berkeley.edu/~chlewis |
From: <dav...@ub...> - 2010-11-15 19:40:50
|
Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mails are not encrypted and cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. UBS Limited is a company limited by shares incorporated in the United Kingdom registered in England and Wales with number 2035362. Registered office: 1 Finsbury Avenue, London EC2M 2PP. UBS Limited is authorised and regulated by the Financial Services Authority. UBS AG is a public company incorporated with limited liability in Switzerland domiciled in the Canton of Basel-City and the Canton of Zurich respectively registered at the Commercial Registry offices in those Cantons with Identification No: CH-270.3.004.646-4 and having respective head offices at Aeschenvorstadt 1, 4051 Basel and Bahnhofstrasse 45, 8001 Zurich, Switzerland. Registered in the United Kingdom as a foreign company with No: FC021146 and having a UK Establishment registered at Companies House, Cardiff, with No: BR 004507. The principal office of UK Establishment: 1 Finsbury Avenue, London EC2M 2PP. In the United Kingdom, UBS AG is authorised and regulated by the Financial Services Authority. UBS reserves the right to retain all messages. Messages are protected and accessed only in legally justified cases. |
From: Michael D. <md...@st...> - 2010-11-15 18:45:32
|
Since their package is crashing, I would report this bug against OpenSUSE's python-matplotlib package. If that doesn't get you any response, it would be helpful to get a better idea of where it is failing. Can you provide a gdb backtrace? Mike |
From: Kurt M. <kur...@su...> - 2010-11-15 18:28:48
|
Hi, Since upgrading to SUSE 11.3 matplotlib simply craches (segfault on dlopen("/usr/lib/python2.6/site-packages/matplotlib/_path.so", 2); > python -V Python 2.6.5 > uname -a Linux mcp20 2.6.34.7-0.5-default #1 SMP 2010-10-25 08:40:12 +0200 i686 i686 i386 GNU/Linux I did a 1-Click Installation from http://software.opensuse.org. http://software.opensuse.org/search/download?base=openSUSE%3A11.3&file=devel%3A%2Flanguages%3A%2Fpython%2FopenSUSE_11.3%2Fi586%2Fpython-matplotlib-1.0.0-2.9.i586.rpm&query=python-matplotlib So I have python-matplotlib-1.0.0-2.9.i586.rpm When I do: python -v -c "import matplotlib.figure" ... import matplotlib.docstring # precompiled from /usr/lib/python2.6/site-packages/matplotlib/docstring.pyc # /usr/lib/python2.6/site-packages/matplotlib/transforms.pyc matches /usr/lib/python2.6/site-packages/matplotlib/transforms.py import matplotlib.transforms # precompiled from /usr/lib/python2.6/site-packages/matplotlib/transforms.pyc dlopen("/usr/lib/python2.6/site-packages/matplotlib/_path.so", 2); Speicherzugriffsfehler (means "Segfault") The same is when I do: python -v -c "from pylab import *" mport matplotlib.docstring # precompiled from /usr/lib/python2.6/site-packages/matplotlib/docstring.pyc # /usr/lib/python2.6/site-packages/matplotlib/transforms.pyc matches /usr/lib/python2.6/site-packages/matplotlib/transforms.py import matplotlib.transforms # precompiled from /usr/lib/python2.6/site-packages/matplotlib/transforms.pyc dlopen("/usr/lib/python2.6/site-packages/matplotlib/_path.so", 2); Speicherzugriffsfehler I googled around. Some Chaco users seems to have similar problems. But for now I have no idea what to do next. Please, somebody be so kind and give me some hint. Have a nice day. -- Kurt Müller, mu...@pr... |
From: Daniel W. <dan...@gm...> - 2010-11-15 16:23:07
|
Greetings. I am making some contour plots and in my field for this particular value, there are two widely used units. As such, it is very useful to have both units listed on the colorbar. To clarify: the colorbar's normal ticks would be facing to the right and labeled with Unit Type 1, which was the units that the data were in when they were plotted. Unit Type 2 is simply a factor of X different than unit type two. It would be nice if I could add a second set of ticks to the color bar using a different locator and have them face left. Is this possible? Is there another way to display two values for each tick such that the colorbar shows both units? Thanks. -dw |
From: Guy G. <guy...@re...> - 2010-11-15 10:14:50
|
On Friday 12 Nov 2010 15:20:43 Ryan May wrote: > On Fri, Nov 12, 2010 at 8:40 AM, Benjamin Root <ben...@ou...> wrote: > > On Fri, Nov 12, 2010 at 5:11 AM, Guy Griffiths > > <guy...@re...> > > > > wrote: > >> Hi, > >> > >> I've been using matplotlib for a while for plotting scientific data, and > >> recently upgraded from version 0.99.1.1 to 1.0.0. Primarily I use > >> pcolor to > >> produce plots of concentration in 2D space. I use reasonably fine > >> meshes, and > >> in v0.99.1.1 the output looked great. > >> > >> In v1.0.0, all of my plots (using the same code) have faint gridlines > >> visible. > >> Since the mesh I am using is quite fine, this makes the plots look > >> terrible > >> (i.e. more gridlines than actual data). This seems to be controlled by > >> the > >> "edgecolors" keyword, but even when set to 'none' they are still there. > >> Is > >> there any way to remove them completely without reverting back to > >> 0.99.1.1 (which I'd prefer not to do, since some of the API changes are > >> really useful > >> for creating very polished graphs suitable for publication)? > >> > >> imshow seems to have closer results to what I want (i.e. no gridlines), > >> but > >> with imshow, the axes denote the pixel position, and there is no option > >> to display on polar axes (which is essential). > >> > >> Any help would be much appreciated. > >> > >> Regards, > >> > >> Guy Griffiths > > > > Guy, I have noticed something similar a few months ago with pcolor, but I > > am not certain if it is the same problem as yours. First, which backend > > are you using? Second, are you seeing the grid lines in both the figure > > window and the saved output? Also, what format are you saving your > > output to? Lastly, which pcolor function are you using (pcolor(), > > pcolormesh(), pcolorfast())? > > > > If you could include a screenshot or the saved file, I could see if it is > > similar to my problem. > > Yeah, I had noticed a problem with pcolor too. You can see the problem > I've been seeing here: > > http://matplotlib.sourceforge.net/examples/pylab_examples/pcolor_demo.html > > Calling pcolor with antialiased=False removes the lines, but that's > just a workaround, not a solution. I'm not really sure where to start > to track this down, so if anyone has a suggestion, I'm all ears. > > Ryan Hi, Thanks for the help. The problem I'm seeing is as Ryan describes (same effect as in the screenshot, but let me know if you still want me to provide an example), and appears in both the figure window and saved output (at least png and pdf). The backend I am using is Qt/Agg. I was using pcolor(), but it appears that pcolormesh() doesn't (always) have this problem. Setting antialiased=False removes some of the problems. In summary: pcolor(), antialiased=True - lines on screen, png, pdf pcolor(), antialiased=False - lines on pdf, fine on png/screen pcolormesh() - lines on pdf, fine on png/screen Regards, Guy |