matplotlib-users Mailing List for matplotlib

my .matplotlib folder is empty. also, my installation otherwise 
appears to work.
-gideon
On Jun 24, 2008, at 10:01 AM, John Hunter wrote:
> On Tue, Jun 24, 2008 at 8:27 AM, Gideon Simpson 
> <gr...@co...> wrote:
>> I built from source. I removed my existing installation of
>> matplotlib, but I am still getting the same error. I had not been
>> using setup.cfg, but edited the template so that the experimental
>> packages were turned off. I am still getting this error.
>
> Check to see if you have a matplotlibrc file in ~/.matplotlib. If so,
> replace it with the latest one from site-packages/matplotlib/mpl-data
> (or comment out the autolayout line in the one you already have in
> ~/.matplotlib).
>
> Let us know if this works.
>
> JDH

On Tue, Jun 24, 2008 at 8:27 AM, Gideon Simpson <gr...@co...> wrote:
> I built from source. I removed my existing installation of
> matplotlib, but I am still getting the same error. I had not been
> using setup.cfg, but edited the template so that the experimental
> packages were turned off. I am still getting this error.
Check to see if you have a matplotlibrc file in ~/.matplotlib. If so,
replace it with the latest one from site-packages/matplotlib/mpl-data
(or comment out the autolayout line in the one you already have in
~/.matplotlib).
Let us know if this works.
JDH

I built from source. I removed my existing installation of 
matplotlib, but I am still getting the same error. I had not been 
using setup.cfg, but edited the template so that the experimental 
packages were turned off. I am still getting this error.
-gideon
On Jun 24, 2008, at 7:31 AM, John Hunter wrote:
> On Mon, Jun 23, 2008 at 11:41 PM, Gideon Simpson 
> <gr...@co...> wrote:
>> I was trying to look up a module, and, after installing matplotlib
>> 0.98.1, I get:
>
>> File "/opt/lib/python2.5/site-packages/matplotlib/config/
>> tconfig.py", line 391, in __init__
>> raise TConfigInvalidKeyError(m)
>> matplotlib.config.tconfig.TConfigInvalidKeyError: In config defined 
>> in
>> file: '/opt/lib/python2.5/site-packages/matplotlib/mpl-data/
>> matplotlib.conf'
>> Error processing section: figure
>> These keys are invalid : ['autolayout']
>> Valid key names : ['edgecolor', 'facecolor', 'dpi', 'figsize']
>
> This looks like you have the experimental "traited config" turned on,
> and Michael may have not cleaned autolayout from the tconfig defaults
> when he removed it. Did you build from source or get your package
> from elsewhere. If building from source, edit setup.cfg next to
> setup.py and make sure that the traited config is off
>
> ## Experimental config package support, this should only be enabled 
> by
> ## matplotlib developers, for matplotlib development
> enthought.traits = False
> configobj = False
>
> If you got it from elsewhere, let the packager know this should be
> turned off. And Darren, can you make sure that tconfig is updated
> vis-a-vis the autolayout param removal.
>
> JDH

On Tue, Jun 24, 2008 at 6:14 AM, Darren Dale <dsd...@gm...> wrote:
> Please, include a brief standalone script that demonstrates the problem when
> reporting problems.
Sorry should have done that, I've attached an example script (and the
according data files) which exhibits the problem on 0.98.1, 0.98.0 has
no problems.
 File "./test.py", line 46, in <module>
 test_plot = test_axes.plot_date(test_dates, test, 'bo-')
 File "/opt/local/lib/python2.5/site-packages/matplotlib/axes.py",
line 3081, in plot_date
 self.xaxis_date(tz)
 File "/opt/local/lib/python2.5/site-packages/matplotlib/axes.py",
line 2015, in xaxis_date
 locator.refresh()
 File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
line 540, in refresh
 dmin, dmax = self.viewlim_to_dt()
 File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
line 436, in viewlim_to_dt
 return num2date(vmin, self.tz), num2date(vmax, self.tz)
 File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
line 233, in num2date
 if not cbook.iterable(x): return _from_ordinalf(x, tz)
 File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
line 156, in _from_ordinalf
 dt = datetime.datetime.fromordinal(ix)
ValueError: ordinal must be >= 1
What's strange is that if I comment out the plotting of the second
test data set then the plot is produced without error, even though the
reported error (when plotting both data sets) seems to have nothing to
do with the second data set.
Cheers
Adam

On Tue, Jun 24, 2008 at 6:43 AM, Johan Mazel <joh...@gm...> wrote:
> I used to have such errors when I was trying to display empty vectors.
> But since you're saying that the script work on previous version of
> Matplotlib...
I recently made some changes to try and support a use-case where the
user has no data and sets ax.set_xdate and later plots some date data.
Eg, the following used to fail on the call to xaxis_date because the
default data/viewlim are 0..1
 import datetime
 import matplotlib.pyplot as plt
 dt = datetime.date
 x = dt(2002,1,1), dt(2003,1,1), dt(2004,1,1)
 fig = plt.figure()
 ax = fig.add_subplot(111)
 ax.xaxis_date()
 ax.plot(x, [1,2,3])
 fig.autofmt_xdate()
 plt.show()
so it is possible these edits are causing the change Adam is
describing (even though they were designed to fix it), but as Darren
notes we will need a standalone script since our examples are working
fine and it is hard to debug in the void.
JDH

On Tue, Jun 24, 2008 at 7:05 AM, Michael Droettboom <md...@st...> wrote:
> I removed the autolayout key from all the various config files in SVN,
> but of course, forgot that any users with already-installed copies of
> matplotlibrc will get this error. Should I put the key back in as a
> deprecated no-op?
Yes, that is probably a good idea. Issue a warning pointing them to
the latest rc (http://matplotlib.sf.net/matplotlibrc).
JDH

I removed the autolayout key from all the various config files in SVN, 
but of course, forgot that any users with already-installed copies of 
matplotlibrc will get this error. Should I put the key back in as a 
deprecated no-op?
Cheers,
Mike
John Hunter wrote:
> On Mon, Jun 23, 2008 at 11:41 PM, Gideon Simpson <gr...@co...> wrote:
> 
>> I was trying to look up a module, and, after installing matplotlib
>> 0.98.1, I get:
>> 
>
> 
>> File "/opt/lib/python2.5/site-packages/matplotlib/config/
>> tconfig.py", line 391, in __init__
>> raise TConfigInvalidKeyError(m)
>> matplotlib.config.tconfig.TConfigInvalidKeyError: In config defined in
>> file: '/opt/lib/python2.5/site-packages/matplotlib/mpl-data/
>> matplotlib.conf'
>> Error processing section: figure
>> These keys are invalid : ['autolayout']
>> Valid key names : ['edgecolor', 'facecolor', 'dpi', 'figsize']
>> 
>
> This looks like you have the experimental "traited config" turned on,
> and Michael may have not cleaned autolayout from the tconfig defaults
> when he removed it. Did you build from source or get your package
> from elsewhere. If building from source, edit setup.cfg next to
> setup.py and make sure that the traited config is off
>
> ## Experimental config package support, this should only be enabled by
> ## matplotlib developers, for matplotlib development
> enthought.traits = False
> configobj = False
>
> If you got it from elsewhere, let the packager know this should be
> turned off. And Darren, can you make sure that tconfig is updated
> vis-a-vis the autolayout param removal.
>
> JDH
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> 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

I used to have such errors when I was trying to display empty vectors.
But since you're saying that the script work on previous version of
Matplotlib...
Sorry if it hasn't helped.
Johan
2008年6月24日 Darren Dale <dsd...@gm...>:
> On Monday 23 June 2008 23:37:09 Adam Mercer wrote:
> > Hi
> >
> > Just upgraded to matplotlib-0.98.1, and a code that worked with 0.98.0
> > is now failing with the following error:
>
> Please, include a brief standalone script that demonstrates the problem
> when
> reporting problems.
>
> > Traceback (most recent call last):
> > File "./plot_workout.py", line 126, in <module>
> > time_plot = time_axes.plot_date(times_dates, times, 'bo-')
> > File "/opt/local/lib/python2.5/site-packages/matplotlib/axes.py",
> > line 3081, in plot_date
> > self.xaxis_date(tz)
> > File "/opt/local/lib/python2.5/site-packages/matplotlib/axes.py",
> > line 2015, in xaxis_date
> > locator.refresh()
> > File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
> > line 540, in refresh
> > dmin, dmax = self.viewlim_to_dt()
> > File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
> > line 436, in viewlim_to_dt
> > return num2date(vmin, self.tz), num2date(vmax, self.tz)
> > File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
> > line 233, in num2date
> > if not cbook.iterable(x): return _from_ordinalf(x, tz)
> > File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
> > line 156, in _from_ordinalf
> > dt = datetime.datetime.fromordinal(ix)
> > ValueError: ordinal must be >= 1
> >
> > Any ideas?
> >
> > Cheers
> >
> > Adam
> >
> > -------------------------------------------------------------------------
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> > http://sourceforge.net/services/buy/index.php
> > _______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

On Mon, Jun 23, 2008 at 11:41 PM, Gideon Simpson <gr...@co...> wrote:
> I was trying to look up a module, and, after installing matplotlib
> 0.98.1, I get:
> File "/opt/lib/python2.5/site-packages/matplotlib/config/
> tconfig.py", line 391, in __init__
> raise TConfigInvalidKeyError(m)
> matplotlib.config.tconfig.TConfigInvalidKeyError: In config defined in
> file: '/opt/lib/python2.5/site-packages/matplotlib/mpl-data/
> matplotlib.conf'
> Error processing section: figure
> These keys are invalid : ['autolayout']
> Valid key names : ['edgecolor', 'facecolor', 'dpi', 'figsize']
This looks like you have the experimental "traited config" turned on,
and Michael may have not cleaned autolayout from the tconfig defaults
when he removed it. Did you build from source or get your package
from elsewhere. If building from source, edit setup.cfg next to
setup.py and make sure that the traited config is off
 ## Experimental config package support, this should only be enabled by
 ## matplotlib developers, for matplotlib development
 enthought.traits = False
 configobj = False
If you got it from elsewhere, let the packager know this should be
turned off. And Darren, can you make sure that tconfig is updated
vis-a-vis the autolayout param removal.
JDH

On Monday 23 June 2008 23:37:09 Adam Mercer wrote:
> Hi
>
> Just upgraded to matplotlib-0.98.1, and a code that worked with 0.98.0
> is now failing with the following error:
Please, include a brief standalone script that demonstrates the problem when 
reporting problems.
> Traceback (most recent call last):
> File "./plot_workout.py", line 126, in <module>
> time_plot = time_axes.plot_date(times_dates, times, 'bo-')
> File "/opt/local/lib/python2.5/site-packages/matplotlib/axes.py",
> line 3081, in plot_date
> self.xaxis_date(tz)
> File "/opt/local/lib/python2.5/site-packages/matplotlib/axes.py",
> line 2015, in xaxis_date
> locator.refresh()
> File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
> line 540, in refresh
> dmin, dmax = self.viewlim_to_dt()
> File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
> line 436, in viewlim_to_dt
> return num2date(vmin, self.tz), num2date(vmax, self.tz)
> File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
> line 233, in num2date
> if not cbook.iterable(x): return _from_ordinalf(x, tz)
> File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
> line 156, in _from_ordinalf
> dt = datetime.datetime.fromordinal(ix)
> ValueError: ordinal must be >= 1
>
> Any ideas?
>
> Cheers
>
> Adam
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Delbert Franz wrote:
> I have been working to display an image of a USGS 7.5 minute quad sheet. 
> These are provided at various locations about the Web. Since the 
> range of colors on these maps is limited, the *.tif files appear to 
> use an indexed color map wherein each pixel has a value 0 to 255 and 
> the color is found from a table with 256 entries having triplets of
> the RGB in the range of 0-255. I have not been able to sort out
> how to get the gdal package to give me the color map from within python, so I dumped it
> from the image file using gdalinfo and then cut and pasted to get
> the following script:
> 
> ---------------------------------------------------------------------------------
> import numpy as np
> import matplotlib.pyplot as plt
> import matplotlib.cm as cm
> from matplotlib.colors import ListedColormap
from matplotlib.colors import NoNorm
> 
> import osgeo.gdal as gdal
> from osgeo.gdalconst import *
> 
> gd = gdal.Open('o37122d1.tif')
> 
> #Setup to compute the colormap from the RGB triplets from the geotif file
> div = np.zeros( (256,3), np.float32)
> 
> div = 255.0
> ctab = np.array([
> [ 255,255,255],
> [ 0,0,0],
> [ 255,255,255],
> [ 91,159,230],
> [ 230,45,30],
> [ 162,96,71],
> [ 210,255,177],
> [ 197,101,197],
> [ 255,240,0],
> [ 202,225,245],
> 
> ...snip.... (deleted many lines:)
> [ 250,202,250],
> [ 230,230,230],
> [ 222,167,146],
> [ 255,255,255],
> [ 255,255,255] ], dtype=np.uint8)
> 
> #Compute colors in range 0.0 to 1.0. 
> fctab= ctab/div
> 
> usgscm = ListedColormap(fctab, name='usgs',N=None)
> 
> 
> doq = gd.ReadAsArray()
> # doq proves to be a uint8 array: 8802 rows and 7066 columns
> 
> # Cut out a subset from the main array--to large to display and
> # slow as 'molasses in January' to process:)
> suba = doq[0:1101 ,0:1801 ]
> 
> fig = plt.figure()
> ax = fig.add_subplot(111)
> ax.imshow(suba, cmap=usgscm, origin='upper')
Instead, try:
ax.imshow(suba, cmap=usgscm, norm=NoNorm(), origin='upper')
> 
> plt.show()
> ---------------------------------------------------------------------------------
> This script does give me an image--but in badly wrong colors:( The script does 
> properly display gray-scaled Digital Ortho-quadrangles using cm.gray as the color
> map in imshow. Consequently something is not quite correct with respect to the 
> definition or the use of the color map. It appears that each map, and there 
> are about 56,000 of them available on one site, could have its own color map.
> Thus my application must be able to compute a color map unique to each of the 
> topographic maps. 
> 
> Questions:
> 
> 1. What am I missing to get imshow to pick out the correct colors from the 
> color map?
The default norm will scale your inputs; specifying the norm as a NoNorm 
instance will pass the integers through directly, so they will be used 
as indices into the colormap.
> 
> 2. Should I be using the name, usgs, given in the ListedColormap instance someplace?
> Not clear to me what role that name plays. 
> 
None, really. I can imagine ways in which it could be useful, but 
unless you know you need it, consider it optional.
> 3. Is there a way to use ctab directly in the ListedColormap instance? Class Colormap
> has a bytes argument, False by default, but I am not yet sure if it has any bearing
> on my problem. 
No, sorry, but the bytes argument is only in the __call__ method, where 
it is used to improve efficiency within mpl. There is no facility for 
using ints in the lookup table, and no recognition of 0-255 ints within 
mpl colorspecs, hence no way to feed your ctab in directly. Even if 
there were, though, I don't think it would make much difference in 
plotting time.
Eric
> 
> I am using Matplotlib 0.98 with the latest numpy, and gdal. I am not using 
> Basemap, after some study, because it contains far more "horsepower" than my 
> simple topographic-map viewer application requires. Also, this is my first 
> foray into "image processing". I am finding the learning curve a bit steep,
> as usual, with multiple names for the same thing popping up in descriptions
> from various sources--business as usual in the computer business:) 
> 
> Thanks from a happy matplotlib user in California!
> 
> Delbert
> 
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

I was trying to look up a module, and, after installing matplotlib 
0.98.1, I get:
help> modules
Please wait a moment while I gather a list of all available modules...
Traceback (most recent call last):
 File "<stdin>", line 1, in <module>
 File "/sw/lib/python2.5/site.py", line 346, in __call__
 return pydoc.help(*args, **kwds)
 File "/sw/lib/python2.5/pydoc.py", line 1636, in __call__
 self.interact()
 File "/sw/lib/python2.5/pydoc.py", line 1654, in interact
 self.help(request)
 File "/sw/lib/python2.5/pydoc.py", line 1670, in help
 elif request == 'modules': self.listmodules()
 File "/sw/lib/python2.5/pydoc.py", line 1791, in listmodules
 ModuleScanner().run(callback)
 File "/sw/lib/python2.5/pydoc.py", line 1842, in run
 for importer, modname, ispkg in pkgutil.walk_packages():
 File "/sw/lib/python2.5/pkgutil.py", line 125, in walk_packages
 for item in walk_packages(path, name+'.', onerror):
 File "/sw/lib/python2.5/pkgutil.py", line 110, in walk_packages
 __import__(name)
 File "/opt/lib/python2.5/site-packages/matplotlib/config/ 
__init__.py", line 10, in <module>
 from mplconfig import rcParams, mplConfig, save_config, rcdefaults
 File "/opt/lib/python2.5/site-packages/matplotlib/config/ 
mplconfig.py", line 486, in <module>
 filePriority=True)
 File "/opt/lib/python2.5/site-packages/matplotlib/config/ 
tconfig.py", line 567, in __init__
 self.tconf = configClass(self.fconfCombined,monitor=monitor)
 File "/opt/lib/python2.5/site-packages/matplotlib/config/ 
tconfig.py", line 431, in __init__
 section = v(sec_config,self,monitor=monitor)
 File "/opt/lib/python2.5/site-packages/matplotlib/config/ 
tconfig.py", line 391, in __init__
 raise TConfigInvalidKeyError(m)
matplotlib.config.tconfig.TConfigInvalidKeyError: In config defined in 
file: '/opt/lib/python2.5/site-packages/matplotlib/mpl-data/ 
matplotlib.conf'
Error processing section: figure
These keys are invalid : ['autolayout']
Valid key names : ['edgecolor', 'facecolor', 'dpi', 'figsize']

Hi
Just upgraded to matplotlib-0.98.1, and a code that worked with 0.98.0
is now failing with the following error:
Traceback (most recent call last):
 File "./plot_workout.py", line 126, in <module>
 time_plot = time_axes.plot_date(times_dates, times, 'bo-')
 File "/opt/local/lib/python2.5/site-packages/matplotlib/axes.py",
line 3081, in plot_date
 self.xaxis_date(tz)
 File "/opt/local/lib/python2.5/site-packages/matplotlib/axes.py",
line 2015, in xaxis_date
 locator.refresh()
 File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
line 540, in refresh
 dmin, dmax = self.viewlim_to_dt()
 File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
line 436, in viewlim_to_dt
 return num2date(vmin, self.tz), num2date(vmax, self.tz)
 File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
line 233, in num2date
 if not cbook.iterable(x): return _from_ordinalf(x, tz)
 File "/opt/local/lib/python2.5/site-packages/matplotlib/dates.py",
line 156, in _from_ordinalf
 dt = datetime.datetime.fromordinal(ix)
ValueError: ordinal must be >= 1
Any ideas?
Cheers
Adam

 Wasn't this answered by the two_scales.py example?
On Monday 23 June 2008 20:53:56 Adam Mercer wrote:
> Hi
>
> Anyone know how to fix this problem?
>
> Cheers
>
> Adam
>
> On Thu, Jun 19, 2008 at 8:31 PM, Adam Mercer <ram...@gm...> wrote:
> > Hi
> >
> > I have a plot that has two different y-axis scales and I want
> > appropriate tick marks for the different y-axes. ie I want the tick
> > marks on the left axis to correspond to the scale on the left axis
> > etc... As far as I can tell the way to accomplish this, after
> > consulting the documentation, is to use the tick_left() and
> > tick_right() methods, I therefore have the following code:
> >
> > axes1.yaxis.tick_left()
> > axes1.yaxis.set_major_locator(pylab.MultipleLocator(0.1))
> > axes1.yaxis.set_minor_locator(pylab.MultipleLocator(0.05))
> > axes2.yaxis.tick_right()
> > axes2.yaxis.set_major_locator(pylab.MultipleLocator(5))
> > axes2.yaxis.set_minor_locator(pylab.MultipleLocator(1))
> >
> > but the minor ticks are on both the left and right y-axes. How can I
> > make the minor ticks for axes1 only appear on the the left and the
> > minor ticks for axes2 appear on the right?
> >
> > Cheers
> >
> > Adam
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Hi
Anyone know how to fix this problem?
Cheers
Adam
On Thu, Jun 19, 2008 at 8:31 PM, Adam Mercer <ram...@gm...> wrote:
> Hi
>
> I have a plot that has two different y-axis scales and I want
> appropriate tick marks for the different y-axes. ie I want the tick
> marks on the left axis to correspond to the scale on the left axis
> etc... As far as I can tell the way to accomplish this, after
> consulting the documentation, is to use the tick_left() and
> tick_right() methods, I therefore have the following code:
>
> axes1.yaxis.tick_left()
> axes1.yaxis.set_major_locator(pylab.MultipleLocator(0.1))
> axes1.yaxis.set_minor_locator(pylab.MultipleLocator(0.05))
> axes2.yaxis.tick_right()
> axes2.yaxis.set_major_locator(pylab.MultipleLocator(5))
> axes2.yaxis.set_minor_locator(pylab.MultipleLocator(1))
>
> but the minor ticks are on both the left and right y-axes. How can I
> make the minor ticks for axes1 only appear on the the left and the
> minor ticks for axes2 appear on the right?
>
> Cheers
>
> Adam
>