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
(17) |
2
(3) |
3
(2) |
4
(11) |
5
(8) |
6
(22) |
7
(16) |
8
(9) |
9
(14) |
10
(1) |
11
(8) |
12
(5) |
13
(7) |
14
(10) |
15
(28) |
16
(8) |
17
(20) |
18
(6) |
19
(5) |
20
(15) |
21
(8) |
22
(7) |
23
(14) |
24
(10) |
25
(6) |
26
(8) |
27
(9) |
28
(11) |
29
(13) |
30
(20) |
|
On Wed, Sep 14, 2011 at 4:34 PM, CAB <ca...@ya...> wrote: > > > But now, let's say I want to italicize only the 'f' and 'x'. I can't find > any easy way to do that while retaining the Arial font. > > And no, I don't want to use TeX. Target users' computers might not have > it. > That's fine, that's why matplotlib imitates TeX with mathtext... > > I've tried using mathtext, but that uses one of mathtext's fonts, not mine > (computer modern, etc., or sansserif, etc.) > I am sure there must be some way to change the font, but Arial might not be supported for this... haven't tried though. > > I've tried setting mathregular, but that won't allow me to vary > italic/nonitalic text. > > Could you include some examples of what you tried? > I'm left with not labeling the axes at all, but simply putting four > different text objects next to each other and hoping that it doesn't look > too jury-rigged. > > Yeah, based on your requirements (italicize individual characters) your choices are to either use the latex-like syntax that matplotlib allows for, or to individually set the characters in their own text boxes. But, really, I think if you rethink your requirements, then you will realize that mathtext is the better way to go. It looks much more aesthetically pleasing that way. > Either that, or Photoshop the puppy. > > Let's see if we can avoid that... Cheers, Ben Root
Hey, All, I've combed the documentation ad nauseum, but I can't find a solution for this one, besides a very brute-force one. Let's say I've set my default sans-serif font as 'Arial'. Fine. Now, let's say, in a standard plot, I set the x label of this plot using something like: matplotlib.pyplot.xlabel('f(x) (widgets/quatloo)') Fine again. But now, let's say I want to italicize only the 'f' and 'x'. I can't find any easy way to do that while retaining the Arial font. And no, I don't want to use TeX. Target users' computers might not have it. I've tried using mathtext, but that uses one of mathtext's fonts, not mine (computer modern, etc., or sansserif, etc.) I've tried setting mathregular, but that won't allow me to vary italic/nonitalic text. I'm left with not labeling the axes at all, but simply putting four different text objects next to each other and hoping that it doesn't look too jury-rigged. Either that, or Photoshop the puppy. Any suggestions? Chad
Having issues with installing the matplotlib package under Linux SUSE SLES 11 SP1 (s390): The original distribution gcc throws an error: "src/ft2font.h:14:22: error: ft2build.h: No such file or directory" when adding the file ft2build.h the linkage process stops at this error: G++ cannot find -lfreetype When trying to manually install the latest Freetype2 package, I get an error when using the package build commands, both at the "make" and "jam" Errors: ------- error at make command: zbra:/opt/python/freetype2/freetype-2.4.6 # make config.mk:25: builds/unix/unix-def.mk: No such file or directory config.mk:26: builds/unix/unix-cc.mk: No such file or directory make: *** No rule to make target `builds/unix/unix-cc.mk'. Stop. error at jam command zbra:/opt/python/freetype2/freetype-2.4.6 # jam install don't know how to make install ...found 1 target(s)... ...can't find 1 target(s)... Thanks in advance for any hints, Claude -- View this message in context: http://old.nabble.com/Problems-installing-Matplotlib-under-SUSE-SLES-11-SP1-tp32467417p32467417.html Sent from the matplotlib - users mailing list archive at Nabble.com.
On Wed, Sep 14, 2011 at 3:08 PM, Youngung Jeong <you...@gm...>wrote: > Hi, > > I have x-y grid data with z values and want to have a pixel view and > contour view at the same time on the same position. Both cases should have > polar coordinate system but since contour function does not plot on the > polar coordinate system, it is plotted on a rectilinear projection with > converting the polar grid into x-y grid. Please let me know if this isn't > true. > > For pixel view, pcolormesh was used. The subplot was added with specifying > the projection='polar', as something like below: > > >>> axp=fig.add_subplot(1,1,1,projection='polar') > >>> axr=fig.add_subplot(2,2,1) > > Then, I will have two independent axes shown in the figure canvas. > Since I want to place the two axes on the same position, if allowed, I > would like to do: > > >>> axp=fig.add_subplot(1,1,1,projection='polar') > >>> axr=fig.add_subplot(1,1,1) > > But it only gives one axis added to 'fig.axes'. > Is there any work-around? Or am I missing some other feature of matplotlib? > > Youngung > > There are some ways to do this, but I haven't tried them myself. http://matplotlib.sourceforge.net/mpl_toolkits/axes_grid/users/axislines.html Ben Root
Hi, I have x-y grid data with z values and want to have a pixel view and contour view at the same time on the same position. Both cases should have polar coordinate system but since contour function does not plot on the polar coordinate system, it is plotted on a rectilinear projection with converting the polar grid into x-y grid. Please let me know if this isn't true. For pixel view, pcolormesh was used. The subplot was added with specifying the projection='polar', as something like below: >>> axp=fig.add_subplot(1,1,1,projection='polar') >>> axr=fig.add_subplot(2,2,1) Then, I will have two independent axes shown in the figure canvas. Since I want to place the two axes on the same position, if allowed, I would like to do: >>> axp=fig.add_subplot(1,1,1,projection='polar') >>> axr=fig.add_subplot(1,1,1) But it only gives one axis added to 'fig.axes'. Is there any work-around? Or am I missing some other feature of matplotlib? Youngung
Hi, I am trying to create a hatched region, with a "diagonal lines" hatch pattern. When using the PS backend, the hatch lines come out very narrow. Is there a way to increase the thickness of the hatch lines? I am using mpl version 1.0.1. I think this question has been asked before (e.g., in 2008), but I couldn't find an answer. Thanks! -Jeff P.S. I apologize if this message arrives twice.
On 09/14/2011 09:17 AM, Raymond Hawkins wrote: > I'm getting odd behavior when I try to use fmin and pylab in the same program. The issue is illustrated in the code snippet below. As written, fmin won't work: the "print xopt" simply returns the contents of x0 as assigned in the line before fmin. If the "from pylab import *" line is commented out, however, then fmin runs as expected. > This is a good illustration of why "from package_x import *" is so strongly discouraged; it is throwing away one of the most important features of python--the default separation of packages into their own name spaces. The only exception with respect to pylab is that for quick and dirty interactive use, particularly within ipython, it is sometimes worthwhile to sacrifice some name space separation for typing speed. But in a script that imports from more than one external package, it is best to always use explicit imports in some form. The preferred idiom is to avoid importing pylab at all in scripts; instead, do this: import numpy as np import matplotlib.pyplot as plt Eric > I'm running python 2.7.2 on a MacBook Pro with a recent install& upgrade of scipy and matplotlib via macports. Any suggestions would be appreciated. > > ------------------------------------- > > #!/opt/local/bin/python > > from scipy import * > from scipy.optimize import fmin > import matplotlib > matplotlib.use('MacOSX') > from pylab import * > > def rosen(x): # The Rosenbrock function > return sum(100.0*(x[1:]-x[:-1]**2.0)**2.0 + (1-x[:-1])**2.0) > > x0 = [1.3, 0.7, 0.8, 1.9, 1.2] > > xopt = fmin(rosen, x0) > > print xopt > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > Learn about the latest advances in developing for the > BlackBerry® mobile platform with sessions, labs& more. > See new tools and technologies. Register for BlackBerry® DevCon today! > http://p.sf.net/sfu/rim-devcon-copy1 > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
On Wed, Sep 14, 2011 at 2:17 PM, Raymond Hawkins <rha...@ea...>wrote: > I'm getting odd behavior when I try to use fmin and pylab in the same > program. The issue is illustrated in the code snippet below. As written, > fmin won't work: the "print xopt" simply returns the contents of x0 as > assigned in the line before fmin. If the "from pylab import *" line is > commented out, however, then fmin runs as expected. > > I'm running python 2.7.2 on a MacBook Pro with a recent install & upgrade > of scipy and matplotlib via macports. Any suggestions would be appreciated. > > ------------------------------------- > > #!/opt/local/bin/python > > from scipy import * > from scipy.optimize import fmin > import matplotlib > matplotlib.use('MacOSX') > from pylab import * > > def rosen(x): # The Rosenbrock function > return sum(100.0*(x[1:]-x[:-1]**2.0)**2.0 + (1-x[:-1])**2.0) > > x0 = [1.3, 0.7, 0.8, 1.9, 1.2] > > xopt = fmin(rosen, x0) > > print xopt > Because pylab brings the numpy namespace into the current namespace, numpy's fmin is imported and replaces the previously def'ed fmin from scipy.optimize. Numpy's fmin function is completely different from scipy's fmin. Try putting the "from scipy.optimize import fmin" after the pylab import line. Or, do something like "from scipy.optimize import fmin as fminimize" to avoid name collision. I hope that helps. Ben Root
Hi, I am trying to create a hatched region, with a "diagonal lines" hatch pattern. When using the PS backend, the hatch lines come out very narrow. Is there a way to increase the thickness of the hatch lines? I am using mpl version 1.0.1. I think this question has been asked before (e.g., in 2008), but I couldn't find an answer. Thanks! -Jeff
I'm getting odd behavior when I try to use fmin and pylab in the same program. The issue is illustrated in the code snippet below. As written, fmin won't work: the "print xopt" simply returns the contents of x0 as assigned in the line before fmin. If the "from pylab import *" line is commented out, however, then fmin runs as expected. I'm running python 2.7.2 on a MacBook Pro with a recent install & upgrade of scipy and matplotlib via macports. Any suggestions would be appreciated. ------------------------------------- #!/opt/local/bin/python from scipy import * from scipy.optimize import fmin import matplotlib matplotlib.use('MacOSX') from pylab import * def rosen(x): # The Rosenbrock function return sum(100.0*(x[1:]-x[:-1]**2.0)**2.0 + (1-x[:-1])**2.0) x0 = [1.3, 0.7, 0.8, 1.9, 1.2] xopt = fmin(rosen, x0) print xopt