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
(14) |
2
(11) |
|
3
(5) |
4
(17) |
5
(11) |
6
(37) |
7
(35) |
8
(9) |
9
(1) |
|
10
(9) |
11
(7) |
12
(22) |
13
(34) |
14
(24) |
15
(27) |
16
(13) |
|
17
(19) |
18
(43) |
19
(36) |
20
(12) |
21
(9) |
22
(21) |
23
(3) |
|
24
(5) |
25
(30) |
26
(14) |
27
(23) |
28
(19) |
29
(19) |
30
(10) |
|
31
(6) |
|
|
|
|
|
|
|
From: C M <cmp...@gm...> - 2009-05-11 05:26:48
|
On Mon, May 11, 2009 at 12:52 AM, Gökhan SEVER <gok...@gm...> wrote: > And the answer is: > > axis(xmin=..., xmax=...) > > Probably, that was a very easy question and no one wanted to answer :) > > Gökhan > > > On Sun, May 10, 2009 at 4:12 PM, Gökhan SEVER <gok...@gm...> wrote: >> >> Hello, >> >> I overlay bunch of boxplots with mean values shown as stars on each >> corresponding boxplot instance. (As could be seen in this image: >> http://img216.imageshack.us/img216/7528/boxplot.png. >> >> There is a minor thing that affects the appearance of the figure. That is >> 1st and the last boxplots don't fit in the figure borders. How can I fix >> this? Do you have any suggestions? >> >> Thank you. >> >> Gökhan What is the difference between doing that or using something like: axes.autoscale_view(tight=False, scalex=True, scaley=True) I am under the impression that if tight=False, the plot does not autoscale to precisely the xlims, but leaves some margin. Is that right? Che |
|
From: Gökhan S. <gok...@gm...> - 2009-05-11 04:53:05
|
And the answer is: axis(xmin=..., xmax=...) Probably, that was a very easy question and no one wanted to answer :) Gökhan On Sun, May 10, 2009 at 4:12 PM, Gökhan SEVER <gok...@gm...> wrote: > Hello, > > I overlay bunch of boxplots with mean values shown as stars on each > corresponding boxplot instance. (As could be seen in this image: > http://img216.imageshack.us/img216/7528/boxplot.png. > > There is a minor thing that affects the appearance of the figure. That is > 1st and the last boxplots don't fit in the figure borders. How can I fix > this? Do you have any suggestions? > > Thank you. > > Gökhan > |
|
From: Evan M. <eva...@gm...> - 2009-05-10 21:49:55
|
Thanks for that:
def ifmissing(x):
try: return float(x)
except: return np.nan
works just fine.
-Evan
On Sun, May 10, 2009 at 6:59 AM, Ryan May <rm...@gm...> wrote:
>
>
> On Sat, May 9, 2009 at 8:35 PM, Evan Mason <eva...@gm...> wrote:
>
>> Hi, I want to use mlab.load to load in some data:
>>
>>
>> 1) 2004/02/27 21:51:00 1 2553.51 2553.51
>> -99.0000N 3.217
>> 2) 2004/02/27 22:01:00 2 2553.47 2553.47
>> -99.0000N 3.217
>> 3) 2004/02/27 22:10:59 3 2553.45 2553.45
>> -99.0000N 3.218
>> 4) 2004/02/27 22:20:59 4 2553.46 2553.46
>> -99.0000N 3.223
>>
>>
>> unfortunately missing values are given as -99.000N, and these cause the
>> following error:
>>
>>
>> In [98]: mlab.load(site_file,skiprows=29,usecols=[4])
>>
>> ---------------------------------------------------------------------------
>> ValueError Traceback (most recent call
>> last)
>>
>> /Users/evan/python/tools/fig_NEA_seas_paper_RAPID.py in <module>()
>> ----> 1
>> 2
>> 3
>> 4
>> 5
>>
>> /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib/mlab.pyc
>> in load(fname, comments, delimiter, converters, skiprows, usecols, unpack,
>> dtype)
>> 1458 if usecols is not None:
>> 1459 vals = splitfunc(line)
>> -> 1460 row = [converterseq[j](vals[j]) for j in usecols]
>> 1461 else:
>> 1462 row = [converterseq[j](val)
>>
>> ValueError: invalid literal for float(): -99.00N
>>
>>
>> Is there any way around this, apart from editing all the data files to
>> remove every 'N'?
>
>
> Make use of the converters argument:
>
> mlab.load(..., converters={5:fix_func})
>
> Where fix_func is a function that will convert the -99.0000N values to what
> you're looking for.
>
> Ryan
>
> --
> Ryan May
> Graduate Research Assistant
> School of Meteorology
> University of Oklahoma
>
|
|
From: Sandro T. <mo...@de...> - 2009-05-10 21:33:39
|
Hi All,
I'm facing a weird problem while embedding in a gtk window made with
glade (dunno if this might be involved in the problem, but worth
noticing) + dynamical update of the plot.
What I'm doing is:
fig = Figure()
ax = fig.add_subplot(111)
line, = ax.plot([], [])
then using that reference to update the plot when user click on a button:
def update_graph(<params>):
line_ref.set_data(np.array([L1, L2]))
ax.set_yscale('log')
fig_ref.canvas.draw()
Sadly, the graph embedded remains unchanged, if not for the Y labels &
ticks that changes because of the log scale.
The data is there, becase if I explicitly set the x/ylim then the data
are shown, but i'd like mpl to autoscale.
I've used several tentatives to make it works:
- ax.set_autoscale_on(True)
- ax.autoscale_view()
but none of them worked.
Do you know if there's something I can do to make that graph autoscale
at "set_data" time? can I force it somehow? if I can't do it handy, is
there a workaround to obtain the same effect?
Thanks in advance,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
|
|
From: oh42 <ja...@ya...> - 2009-05-10 21:23:06
|
Pl see picture below. The grid always shows on top of the plot lines. Is it possible to put it below? Thanks! http://www.nabble.com/file/p23474184/gridlines.gif -- View this message in context: http://www.nabble.com/how-to-put-grid-under-the-plot-lines--tp23474184p23474184.html Sent from the matplotlib - users mailing list archive at Nabble.com. |
|
From: Gökhan S. <gok...@gm...> - 2009-05-10 21:12:34
|
Hello, I overlay bunch of boxplots with mean values shown as stars on each corresponding boxplot instance. (As could be seen in this image: http://img216.imageshack.us/img216/7528/boxplot.png. There is a minor thing that affects the appearance of the figure. That is 1st and the last boxplots don't fit in the figure borders. How can I fix this? Do you have any suggestions? Thank you. Gökhan |
|
From: Sebastian B. <web...@th...> - 2009-05-10 17:16:59
|
Hello everybody!
I am experiencing the following problem: when I draw text with usetex
enabled and the xcolor package, the result is not colored; however the
intermediate steps that I find in .../tex.cache still are!
The problem occurs with:
=====
from matplotlib import rc
from pylab import figure, text, show, savefig
rc('text', usetex=True)
rc('text.latex', preamble="\usepackage{xcolor}")
f = figure()
f.text(0.5,0.5,r"{\color[rgb]{0,1,0}a}b")
show()
#savefig("colortest.png")
=====
The resulting graph is not colored -- but in the directory
~/.matplotlib/tex.cache/ the text is green, both in the dvi and the png
file!
It therefore seems to me that this is not completely hopeless but I
cannot figure out how to proceed.
Can someone help?
Thanks & best regards,
Sebastian.
I am on
Linux macbook 2.6.27-11-generic #1 SMP Wed Apr 1 20:53:41 UTC 2009
x86_64 GNU/Linux
running
Python 2.5.2 (r252:60911, Oct 5 2008, 19:29:17)
and
matplotlib 0.98.3
downloaded from the Ubuntu repositories for 8.10.
I ran
> python colortest.py --verbose-helpful
/usr/lib/python2.5/site-packages/pytz/__init__.py:29: UserWarning:
Module dateutil was already imported from
/var/lib/python-support/python2.5/dateutil/__init__.py, but
/var/lib/python-support/python2.5 is being added to sys.path
from pkg_resources import resource_stream
$HOME=/...
CONFIGDIR=/.../.matplotlib
matplotlib data path /usr/share/matplotlib/mpl-data
loaded rc file /etc/matplotlibrc
matplotlib version 0.98.3
verbose.level helpful
interactive is False
units is False
platform is linux2
Using fontManager instance from /home/buschi/.matplotlib/fontManager.cache
backend TkAgg version 8.4
Found dvipng version 1.11
and
> python colortest.py --verbose-debug
/usr/lib/python2.5/site-packages/pytz/__init__.py:29: UserWarning:
Module dateutil was already imported from
/var/lib/python-support/python2.5/dateutil/__init__.py, but
/var/lib/python-support/python2.5 is being added to sys.path
from pkg_resources import resource_stream
$HOME=/...
CONFIGDIR=/.../.matplotlib
matplotlib data path /usr/share/matplotlib/mpl-data
loaded rc file /etc/matplotlibrc
matplotlib version 0.98.3
verbose.level debug
interactive is False
units is False
platform is linux2
loaded modules: ['numpy.lib.pkgutil', 'numpy.lib.tempfile',
'numpy.ma.types', 'xml.sax.urlparse', 'distutils', 'matplotlib.errno',
'matplotlib.matplotlib', '_bisect', 'numpy.core.defchararray',
'numpy.lib.bz2', 'matplotlib.tempfile', 'distutils.sysconfig',
'ctypes._endian', 'encodings.encodings', 'matplotlib.dateutil',
'matplotlib.colors', 'numpy.core.numerictypes', 'numpy.testing.sys',
'numpy.core.info', 'xml', 'numpy.fft.types', 'numpy.ma.operator',
'distutils.dep_util', 'numpy.ma.cPickle', 'struct', 'numpy.random.info',
'tempfile', 'mmap', 'xml.sax.urllib', 'numpy.linalg',
'matplotlib.threading', 'numpy.testing.operator', 'imp', 'compiler.sys',
'collections', 'compiler.pyassem', 'numpy.core.umath', '_struct',
'unittest', 'compiler.new', 'numpy.lib.numpy', 'numpy.testing.types',
'compiler.ast', 'numpy.ma.sys', 'zipimport', 'string',
'numpy.testing.os', 'matplotlib.locale', 'numpy.lib.arraysetops',
'numpy.testing.unittest', 'numpy.lib.inspect', 'encodings.utf_8',
'matplotlib.__future__', 'pytz.tzinfo', 'numpy.ctypeslib',
'numpy.testing.re', 'itertools', 'numpy.version', 'numpy.lib.re',
'distutils.re', 'ctypes.os', 'compiler.token', 'numpy.core.os',
'compiler', 'numpy.lib.type_check', 'httplib', 'bisect', 'signal',
'compiler.consts', 'numpy.lib._datasource', 'random', 'numpy.ma.extras',
'token', 'numpy.fft.fftpack_lite', 'shlex', 'ctypes.ctypes',
'xml.sax.xmlreader', 'matplotlib.pytz', 'numpy.__builtin__',
'numpy.testing.shlex', 'distutils.log', 'dis', 'numpy.lib.itertools',
'cStringIO', 'zlib', 'numpy.numpy', 'matplotlib.StringIO',
'numpy.random.mtrand', 'numpy.add_newdocs', 'numpy.lib.getlimits',
'compiler.dis', 'compiler.transformer', 'xml.sax.saxutils',
'compiler.struct', 'pkgutil', 'compiler.parser', 'numpy.lib.sys',
'encodings', 'compiler.symbol', 'numpy.lib.io', 'StringIO', 'dateutil',
'pydoc', 'pytz.cStringIO', 'numpy.imp', 'numpy.ctypes',
'matplotlib.warnings', 'rfc822', 'matplotlib.string', 'pytz.pytz',
'urllib', 'matplotlib.sys', 're', 'numpy.lib._compiled_base',
'threading', 'numpy.core.mmap', 'new', 'numpy.lib.struct', 'symbol',
'math', 'numpy.fft.helper', 'fcntl', 'numpy.ma.warnings',
'compiler.imp', 'UserDict', 'inspect', 'distutils.os', 'matplotlib',
'urllib2', 'pytz.os', 'fnmatch', 'numpy.lib.info', 'numpy.testing',
'numpy.testing.glob', 'numpy.lib.warnings', 'ctypes.struct', 'codecs',
'numpy.core._sort', 'numpy.os', 'pytz.bisect', 'compiler.visitor',
'md5', 'numpy.testing.difflib', 'matplotlib.sre_constants',
'matplotlib.os', 'thread', 'numpy.lib.ufunclike', 'numpy.core.memmap',
'traceback', 'pkg_resources', 'numpy.testing.warnings', 'weakref',
'numpy.core._internal', 'numpy.fft.fftpack', 'opcode',
'numpy.core.scalarmath', 'numpy.linalg.lapack_lite', 'ctypes',
'distutils.sys', 'os', 'marshal', 'sre_parse', 'numpy.lib.shutil',
'__future__', 'numpy.core.string', 'matplotlib.copy', 'xml.sax.types',
'numpy.random.numpy', '_sre', 'numpy.lib.gzip', 'numpy.core.sys',
'numpy.random', 'numpy.linalg.numpy', '__builtin__',
'numpy.lib.twodim_base', 'numpy.ma.core', 'matplotlib.re',
'numpy.core.cPickle', 'base64', 'operator', 'numpy.testing.parametric',
'numpy.core.arrayprint', 'distutils.string', 'ctypes._ctypes', '_heapq',
'ctypes.sys', 'matplotlib.datetime', 'posixpath', 'numpy.lib.financial',
'numpy.core.multiarray', 'errno', 'numpy.testing.numpy', '_socket',
'binascii', 'numpy.lib.compiler', 'sre_constants', 'compiler.cStringIO',
'locale', 'compiler.os', 'matplotlib.md5', 'types', 'pytz.sys',
'tokenize', 'xml.sax.handler', 'numpy.core.numpy', 'numpy',
'numpy.lib.urlparse', 'pytz.pkg_resources', 'matplotlib.types',
'numpy.core.defmatrix', 'xml.sax.os', 'cPickle', 'matplotlib.xml',
'_codecs', '_locale', 'matplotlib.traceback', 'numpy.__config__',
'numpy.fft.info', 'numpy.lib.types', 'pytz', 'matplotlib.pyparsing',
'compiler.copy_reg', 'numpy.ma.numpy', 'copy', 'numpy.core.re',
'socket', '_types', 'numpy.core.fromnumeric', 'hashlib',
'compiler.future', 'matplotlib.cbook', 'numpy.core.copy_reg',
'numpy.lib.scimath', 'numpy.fft', 'numpy.lib', '_ctypes',
'apport_python_hook', 'posix', 'encodings.aliases',
'matplotlib.fontconfig_pattern', 'exceptions', 'xml.sax._exceptions',
'datetime', 'sets', 'numpy.core.cStringIO', 'numpy.core.ctypes',
'mimetools', 'distutils.distutils', 'copy_reg', 'sre_compile',
'xml.sax', 'compiler.compiler', '_hashlib', '_random', 'parser', 'site',
'numpy.lib.polynomial', 'numpy._import_tools', 'numpy.glob',
'pytz.struct', 'numpy.lib.time', '__main__', 'compiler.misc',
'numpy.core.records', 'shutil', 'numpy.lib.cPickle', 'numpy.sys',
'matplotlib.weakref', 'numpy.lib.pydoc', 'numpy.core._dotblas',
'numpy.testing.traceback', 'strop', 'compiler.pycodegen',
'numpy.core.numeric', 'pytz.tzfile', 'numpy.linalg.info',
'encodings.codecs', 'gettext', 'pytz.datetime', 'heapq',
'numpy.lib.cStringIO', 'numpy.core', 'numpy.testing.info',
'matplotlib.rcsetup', 'matplotlib.time', 'pytz.sets',
'matplotlib.numpy', 'xml.sax.codecs', 'stat', '_ssl', 'numpy.lib.utils',
'numpy.lib.index_tricks', 'numpy.testing.utils', 'warnings',
'encodings.types', 'numpy.lib.math', 'glob', 'numpy.lib.shape_base',
'distutils.util', 'numpy.core.types', 'numpy.fft.numpy', 'repr', 'sys',
'numpy.core.warnings', 'numpy.lib.urllib2', 'compiler.types',
'numpy.core.__builtin__', 'xml.sax.sys', 'numpy.lib.format',
'numpy.lib.os', 'numpy.ma', 'os.path', 'bz2', 'pytz.gettext',
'sitecustomize', 'compiler.symbols', 'distutils.spawn',
'matplotlib.distutils', '_weakref', 'numpy.testing.numpytest',
'difflib', 'distutils.errors', 'urlparse', 'linecache',
'matplotlib.shutil', 'numpy.lib.function_base', 'numpy.testing.imp',
'time', 'gzip', 'numpy.lib.machar', 'compiler.marshal',
'numpy.linalg.linalg', 'compiler.syntax']
Using fontManager instance from /home/buschi/.matplotlib/fontManager.cache
backend TkAgg version 8.4
findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0
findfont returning /usr/share/fonts/truetype/ttf-bitstream-vera/Vera.ttf
Found dvipng version 1.11
|
|
From: Ryan M. <rm...@gm...> - 2009-05-10 14:02:50
|
On Sun, May 10, 2009 at 8:33 AM, Sahar <sa...@cm...> wrote: > Hello, > > Is it possible to autoscale the color map of an image (as in > matlab's 'imagesc')? > I'm using imshow and I can use vmin and vmax but than I have to set these > values manually. > If you don't give it a range, it should autoscale by itself. Double check to make sure there isn't a spurious value somewhere in your array. Otherwise, we'd need to see a complete, small example that demonstrates the problem you're seeing, as well as your version of matplotlib. Ryan -- Ryan May Graduate Research Assistant School of Meteorology University of Oklahoma Sent from Norman, Oklahoma, United States |
|
From: Ryan M. <rm...@gm...> - 2009-05-10 14:00:01
|
On Sat, May 9, 2009 at 8:35 PM, Evan Mason <eva...@gm...> wrote:
> Hi, I want to use mlab.load to load in some data:
>
>
> 1) 2004/02/27 21:51:00 1 2553.51 2553.51
> -99.0000N 3.217
> 2) 2004/02/27 22:01:00 2 2553.47 2553.47
> -99.0000N 3.217
> 3) 2004/02/27 22:10:59 3 2553.45 2553.45
> -99.0000N 3.218
> 4) 2004/02/27 22:20:59 4 2553.46 2553.46
> -99.0000N 3.223
>
>
> unfortunately missing values are given as -99.000N, and these cause the
> following error:
>
>
> In [98]: mlab.load(site_file,skiprows=29,usecols=[4])
> ---------------------------------------------------------------------------
> ValueError Traceback (most recent call last)
>
> /Users/evan/python/tools/fig_NEA_seas_paper_RAPID.py in <module>()
> ----> 1
> 2
> 3
> 4
> 5
>
> /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib/mlab.pyc
> in load(fname, comments, delimiter, converters, skiprows, usecols, unpack,
> dtype)
> 1458 if usecols is not None:
> 1459 vals = splitfunc(line)
> -> 1460 row = [converterseq[j](vals[j]) for j in usecols]
> 1461 else:
> 1462 row = [converterseq[j](val)
>
> ValueError: invalid literal for float(): -99.00N
>
>
> Is there any way around this, apart from editing all the data files to
> remove every 'N'?
Make use of the converters argument:
mlab.load(..., converters={5:fix_func})
Where fix_func is a function that will convert the -99.0000N values to what
you're looking for.
Ryan
--
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma
|
|
From: Sahar <sa...@cm...> - 2009-05-10 13:57:21
|
Hello, Is it possible to autoscale the color map of an image (as in matlab's 'imagesc')? I'm using imshow and I can use vmin and vmax but than I have to set these values manually. Thanks, Sahar ******************************************************************************************************* This e-mail message may contain confidential,and privileged information or data that constitute proprietary information of CMT Medical Ltd. Any review or distribution by others is strictly prohibited. If you are not the intended recipient you are hereby notified that any use of this information or data by any other person is absolutely prohibited. If you are not the intended recipient, please delete all copies. Thank You. http://www.cmt.co.il ******************************************************************************************************** ************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************************ |
|
From: Evan M. <eva...@gm...> - 2009-05-10 02:31:28
|
Hi, I want to use mlab.load to load in some data:
1) 2004/02/27 21:51:00 1 2553.51 2553.51
-99.0000N 3.217
2) 2004/02/27 22:01:00 2 2553.47 2553.47
-99.0000N 3.217
3) 2004/02/27 22:10:59 3 2553.45 2553.45
-99.0000N 3.218
4) 2004/02/27 22:20:59 4 2553.46 2553.46
-99.0000N 3.223
unfortunately missing values are given as -99.000N, and these cause the
following error:
In [98]: mlab.load(site_file,skiprows=29,usecols=[4])
---------------------------------------------------------------------------
ValueError Traceback (most recent call last)
/Users/evan/python/tools/fig_NEA_seas_paper_RAPID.py in <module>()
----> 1
2
3
4
5
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib/mlab.pyc
in load(fname, comments, delimiter, converters, skiprows, usecols, unpack,
dtype)
1458 if usecols is not None:
1459 vals = splitfunc(line)
-> 1460 row = [converterseq[j](vals[j]) for j in usecols]
1461 else:
1462 row = [converterseq[j](val)
ValueError: invalid literal for float(): -99.00N
Is there any way around this, apart from editing all the data files to
remove every 'N'?
Many thanks, Evan
|
|
From: Jae-Joon L. <lee...@gm...> - 2009-05-09 03:48:37
|
On Tue, May 5, 2009 at 5:20 PM, william ratcliff <wil...@gm...> wrote: > Hi! Quick question about pylab.annotate: > > Is it supposed to take keyword args such as fontsize? > Yes, it is. http://matplotlib.sourceforge.net/api/pyplot_api.html?highlight=fontsize#matplotlib.pyplot.annotate -JJ > Thanks, > William > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK > i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > |
|
From: jtamir <jt...@ar...> - 2009-05-08 22:56:31
|
Thanks for the response. drawlsmask gets the job done. Jon -- View this message in context: http://www.nabble.com/Basemap---fillcontinents-fills-entire-map-region-in-some-cases-tp23451317p23454957.html Sent from the matplotlib - users mailing list archive at Nabble.com. |
|
From: Jeff W. <js...@fa...> - 2009-05-08 22:01:44
|
jtamir wrote: > I am creating projections centered around various locations: > > > m = Basemap(width=best_width, height=best_height, lon_0=centerLon > lat_0=centerLat, resolution='c',area_thresh=10000.,projection='laea') > > For every location, i have the same code to fill the regions: > > m.fillcontinents(color='#997766',lake_color='#99ffff',zorder=1) > >> m.drawcoastlines(color='#000000', zorder=3) >> m.drawcountries(color="0.75", zorder=2) >> m.drawmapboundary(fill_color='#99ffff', zorder=0) >> >> > For most regions, this results in the expected plot ( > http://www.nabble.com/file/p23451317/good.png good.png ) > However, whenever the region includes South America/Antarctica, > fillcontinents will color the entire map ( > http://www.nabble.com/file/p23451317/bad.png bad.png ) > > Is this a known issue, and is there a way to circumvent it? > > Thanks, > Jon > > Jon: It's a know issue. From the KNOWN_BUGS file: * The fillcontinents method doesn't always do the right thing. Matplotlib always tries to fill the inside of a polygon. Under certain situations, what is the inside of a coastline polygon can be ambiguous, and the outside may be filled instead of the inside. To trigger this, run the garp.py example with lon=-71,lat=-33 (Santiago, Chile). Workaround - mask the land areas with the drawlsmask method instead of filling the coastline polygons. -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 Meteorologist FAX : (303)497-6449 NOAA/OAR/PSD R/PSD1 Email : Jef...@no... 325 Broadway Office : Skaggs Research Cntr 1D-113 Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg |
|
From: jtamir <jt...@ar...> - 2009-05-08 18:33:54
|
I am creating projections centered around various locations: m = Basemap(width=best_width, height=best_height, lon_0=centerLon lat_0=centerLat, resolution='c',area_thresh=10000.,projection='laea') For every location, i have the same code to fill the regions: m.fillcontinents(color='#997766',lake_color='#99ffff',zorder=1) > m.drawcoastlines(color='#000000', zorder=3) > m.drawcountries(color="0.75", zorder=2) > m.drawmapboundary(fill_color='#99ffff', zorder=0) > For most regions, this results in the expected plot ( http://www.nabble.com/file/p23451317/good.png good.png ) However, whenever the region includes South America/Antarctica, fillcontinents will color the entire map ( http://www.nabble.com/file/p23451317/bad.png bad.png ) Is this a known issue, and is there a way to circumvent it? Thanks, Jon -- View this message in context: http://www.nabble.com/Basemap---fillcontinents-fills-entire-map-region-in-some-cases-tp23451317p23451317.html Sent from the matplotlib - users mailing list archive at Nabble.com. |
|
From: Evan M. <eva...@gm...> - 2009-05-08 17:20:40
|
Hi, would it be possible to add a keyword to clabel to optionally switch off
the angle fix in contour.py lines 384+?
# Fix angle so text is never upside-down
if rotation > 90:
rotation = rotation - 180.0
if rotation < -90:
rotation = 180.0 + rotation
Something like "clabel(CS, upsidedown=True)" with the default as False would
do it.
I am using clabel to put directional arrows on a streamline contour plot,
and this rotation causes some of the arrows to point the wrong way. So it
seems it would be a useful feature. I'm willing to try to do it myself if
somebody could tell me which files I would need to edit in addition to
contour.py?
Many thanks,
Evan
|
|
From: Jouni K. S. <jk...@ik...> - 2009-05-08 16:43:17
|
Thomas Robitaille <tho...@gm...> writes: > In [2]: matplotlib.__revision__ > Out[2]: '$Revision: 6887 $' > > but this isn't actually the current revision number, I have upgraded > to 7096 (I'm suspecting that 6887 is the revision number for 0.98.5.2) The way Subversion works, 6887 is simply the latest revision in which matplotlib/__init__.py was changed. If you have a Subversion checkout, you can use the svnversion command to find out the revision of the checkout. This could in principle be incorporated into the release process to embed the latest revision somewhere in the source code. -- Jouni K. Seppänen http://www.iki.fi/jks |
|
From: Christopher B. <Chr...@no...> - 2009-05-08 16:39:24
|
Michael Droettboom wrote: > examples of embedding matplotlib inside of a wxPython GUI here: > > http://matplotlib.sourceforge.net/examples/user_interfaces/index.html I'd also check out wxMPL, it's a nice way to embedMPL in a GUI: http://agni.phys.iit.edu/~kmcivor/wxmpl/ -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no... |
|
From: Thomas R. <tho...@gm...> - 2009-05-08 16:18:22
|
Hello, I was wondering whether there is an easy way to find out the svn revision number of matplotlib in python. I tried: In [2]: matplotlib.__revision__ Out[2]: '$Revision: 6887 $' but this isn't actually the current revision number, I have upgraded to 7096 (I'm suspecting that 6887 is the revision number for 0.98.5.2) I know it's probably unlikely that it's possible to find out the exact revision, but just wanted to check just in case! Thanks, Thomas |
|
From: Michael D. <md...@st...> - 2009-05-08 12:31:01
|
There isn't a way to do this in matplotlib itself -- none of the text matplotlib draws is interactive and selectable etc. However, if you're embedded matplotlib in a wxPython GUI, you could stick a wxPython text widget underneath the plotting canvas and put whatever text you need there. The details of that are more of a wxPython issue than a matplotlib one -- but you can see a number of examples of embedding matplotlib inside of a wxPython GUI here: http://matplotlib.sourceforge.net/examples/user_interfaces/index.html Cheers, Mike Stefanie Lück wrote: > Hello! > > I'm new to matplotlib and want to draw a line chart. Everythings works > fine with the great matplotlib. Now my question: > I would like to draw under the diagramm a text, which can be > selected and copied. Is this possible? I guess the easiest way is to > do it over a GUI (I'm using wxPython). Please let me now if there's > another (easier) way! > > Kind regards > Stefanie > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > ------------------------------------------------------------------------ > > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA |
|
From: Stefanie L. <lu...@ip...> - 2009-05-08 09:01:58
|
Hello! I'm new to matplotlib and want to draw a line chart. Everythings works fine with the great matplotlib. Now my question: I would like to draw under the diagramm a text, which can be selected and copied. Is this possible? I guess the easiest way is to do it over a GUI (I'm using wxPython). Please let me now if there's another (easier) way! Kind regards Stefanie |
|
From: Erik T. <eri...@gm...> - 2009-05-07 23:40:36
|
Ah, I see... well, that's doable although not necessarily ideal. Thanks to you both! On Mon, May 4, 2009 at 10:24 AM, Ryan May <rm...@gm...> wrote: > On Mon, May 4, 2009 at 2:22 AM, Erik Tollerud <eri...@gm...> > wrote: >> >> I'm hoping to generate a line plot where the color of each pixel on >> the plot is given by linearly interpolating the colormap from each >> point specified in the line, instead of having the whole line be a >> solid color. I can "mock this up" by doing a scatter plot where the >> points are much closer together than the screen resolution, but that >> seems inelegant, and sometimes produces weird output. So is there a >> way to do effectively the same thing with a line plot or somehow >> specify this behavior in scatter? > > IIRC, the backends that matplotlib uses (Gtk, Agg, etc.) only support a > single color per line, so breaking up the line into different > segments/points is really your only option. Instead of scatter, you can > break up your line into separate sections and have them colormapped for you, > using a LineCollection. > > Ryan > > -- > Ryan May > Graduate Research Assistant > School of Meteorology > University of Oklahoma > Sent from Norman, Oklahoma, United States -- Erik Tollerud Graduate Student Center For Cosmology Department of Physics and Astronomy 2142 Frederick Reines Hall University of California, Irvine Office Phone: (949)824-2587 Cell: (651)307-9409 eto...@uc... |
|
From: Eric F. <ef...@ha...> - 2009-05-07 21:57:39
|
Ryan May wrote:
> On Thu, May 7, 2009 at 3:13 PM, Eric Firing <ef...@ha...
> <mailto:ef...@ha...>> wrote:
>
> Ryan May wrote:
>
> On Tue, Apr 28, 2009 at 9:54 PM, Thomas Robitaille
> <tho...@gm...
> <mailto:tho...@gm...>
> <mailto:tho...@gm...
> <mailto:tho...@gm...>>> wrote:
>
> Thanks! I could not find any documentation relating to this,
> so I was
> wondering whether it would be better to go with a well-documented
> function such as text or figtext? What would be best to use?
>
> Thomas
>
> On 28 Apr 2009, at 22:27, Yong-Duk Jin wrote:
>
> > You can use 'LABELPAD' to adjust label position.
> > e.g.
> >
> > import pylab
> > hAxes = pylab.axes()
> > pylab.xlabel('test')
> > hAxes.xaxis.LABELPAD = 0
> > pylab.show()
> >
>
>
> There's now a documented way to do this in SVN HEAD, by passing
> labelpad as an argument to the xlabel/ylabel functions.
>
>
> Ryan,
>
> Good idea, thanks.
>
> Quick thought, with no investigation on my part: wouldn't it be more
> natural and more useful if text placement pads like this were in
> font-size units, like the "em" and "ex", so that they would scale
> with the font size? I think that this would make the need to set
> them manually much less common.
>
>
> Good idea, I agree that might help. I was just going for somewhat of a
> quick hack, by just cleaning up access to a pre-existing constant.
> Right now it adds this pad value scaled by dpi/72.0 to an appropriate
> start in pixels. Any idea how the math could include a font size?
In any case where the text object exists at the time the calculation is
needed, and the method doing the calculation has access to that object,
it is just a matter of changing, for example,
self.label.set_position( (x, bottom -
self.labelpad*self.figure.dpi / 72.0))
to
pad = (self.labelpad_rel * self.label.get_size() *
self.figure.dpi / 72.0)
self.label.set_position( (x, bottom - pad))
I think that most of the pads used in mpl are associated with text
objects in such a way that this can be done. The question then becomes
one of how to implement it in a way that doesn't wreck existing code,
and doesn't create intolerable clutter. If this can be done, I think it
would make a *significant* improvement in mpl usability--at least for
anyone who needs to rescale plots for publication or for presentation
display, for example.
Another thing to watch out for in trying to make such a change: the pad
calculation would need to be done late enough to reflect the font size
at draw-time. I have not looked to see whether this is already the
case, or whether it would require substantial refactoring.
I was not suggesting that your labelpad patch should be changed right
away, but rather using it as an opportunity to raise the larger design
question, and see whether anyone is interested in pursuing it.
I have raised questions about pad units before, and in fact we now have
legend.borderpad (in legend font units) that replaces legend.pad (in
normalized axes units).
Eric
>
> Ryan
>
> --
> Ryan May
> Graduate Research Assistant
> School of Meteorology
> University of Oklahoma
> Sent from Norman, Oklahoma, United States
|
|
From: Ryan M. <rm...@gm...> - 2009-05-07 20:17:13
|
On Thu, May 7, 2009 at 3:13 PM, Eric Firing <ef...@ha...> wrote:
> Ryan May wrote:
>
>> On Tue, Apr 28, 2009 at 9:54 PM, Thomas Robitaille <
>> tho...@gm... <mailto:tho...@gm...>> wrote:
>>
>> Thanks! I could not find any documentation relating to this, so I was
>> wondering whether it would be better to go with a well-documented
>> function such as text or figtext? What would be best to use?
>>
>> Thomas
>>
>> On 28 Apr 2009, at 22:27, Yong-Duk Jin wrote:
>>
>> > You can use 'LABELPAD' to adjust label position.
>> > e.g.
>> >
>> > import pylab
>> > hAxes = pylab.axes()
>> > pylab.xlabel('test')
>> > hAxes.xaxis.LABELPAD = 0
>> > pylab.show()
>> >
>>
>>
>> There's now a documented way to do this in SVN HEAD, by passing labelpad
>> as an argument to the xlabel/ylabel functions.
>>
>
> Ryan,
>
> Good idea, thanks.
>
> Quick thought, with no investigation on my part: wouldn't it be more
> natural and more useful if text placement pads like this were in font-size
> units, like the "em" and "ex", so that they would scale with the font size?
> I think that this would make the need to set them manually much less
> common.
>
>
Good idea, I agree that might help. I was just going for somewhat of a quick
hack, by just cleaning up access to a pre-existing constant. Right now it
adds this pad value scaled by dpi/72.0 to an appropriate start in pixels.
Any idea how the math could include a font size?
Ryan
--
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma
Sent from Norman, Oklahoma, United States
|
|
From: Eric F. <ef...@ha...> - 2009-05-07 20:13:42
|
Ryan May wrote:
> On Tue, Apr 28, 2009 at 9:54 PM, Thomas Robitaille
> <tho...@gm... <mailto:tho...@gm...>> wrote:
>
> Thanks! I could not find any documentation relating to this, so I was
> wondering whether it would be better to go with a well-documented
> function such as text or figtext? What would be best to use?
>
> Thomas
>
> On 28 Apr 2009, at 22:27, Yong-Duk Jin wrote:
>
> > You can use 'LABELPAD' to adjust label position.
> > e.g.
> >
> > import pylab
> > hAxes = pylab.axes()
> > pylab.xlabel('test')
> > hAxes.xaxis.LABELPAD = 0
> > pylab.show()
> >
>
>
> There's now a documented way to do this in SVN HEAD, by passing labelpad
> as an argument to the xlabel/ylabel functions.
Ryan,
Good idea, thanks.
Quick thought, with no investigation on my part: wouldn't it be more
natural and more useful if text placement pads like this were in
font-size units, like the "em" and "ex", so that they would scale with
the font size? I think that this would make the need to set them
manually much less common.
Eric
>
> Ryan
>
> --
> Ryan May
> Graduate Research Assistant
> School of Meteorology
> University of Oklahoma
> Sent from Norman, Oklahoma, United States
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
|