Re: [matplotlib-devel] Matplotlib patch on EPD trac?
Ryan May has been doing all the heavy lifting with respect to PSD and specgram, so I am going to turf this to him :-) It may be that the bug filer's problems are resolved in the recent changes in 98.5.2, but Ryan should confirm On Fri, Jan 9, 2009 at 2:45 PM, Dave Peterson wrote: > Hi John, > > Sorry for sending this directly, but I'm still waiting for my matplotlib > devel mailing subscription to go through > > We've just had an EPD user submit a patch for matplotlib to 'fix' a problem > they were seeing with the PSD function. Is this a known issue or something > that you'd be interested in including in future versions of matplotlib? Or > is it something that you disagree is 'right'? > > https://svn.enthought.com/epd/ticket/581 > > I'd like to know to do the right thing with the matplotlib we include in > EPD. :-) > > > -- Dave > > -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Matplotlib patch on EPD trac?
John Hunter wrote: > Ryan May has been doing all the heavy lifting with respect to PSD and > specgram, so I am going to turf this to him :-) It may be that the > bug filer's problems are resolved in the recent changes in 98.5.2, but > Ryan should confirm > > On Fri, Jan 9, 2009 at 2:45 PM, Dave Peterson wrote: >> Hi John, >> >> Sorry for sending this directly, but I'm still waiting for my matplotlib >> devel mailing subscription to go through >> >> We've just had an EPD user submit a patch for matplotlib to 'fix' a problem >> they were seeing with the PSD function. Is this a known issue or something >> that you'd be interested in including in future versions of matplotlib? Or >> is it something that you disagree is 'right'? >> >> https://svn.enthought.com/epd/ticket/581 >> >> I'd like to know to do the right thing with the matplotlib we include in >> EPD. :-) Specgram specifically handles the case of moving frequencies to -Fs/2 to Fs/2, instead of 0 to Fs. It was this way before I did any of my changes and I just left it as it was. Psd returns frequencies 0 to Fs for Matlab compatibility (I think anyways, John?). Personally, I'd also prefer to have -Fs/2 to Fs/2 returned as well, so I don't have to do it in my own code. However, I'm also loath to add yet another flag to toggle Matlab compatibility. As far as the patch goes, it looks fine. It won't work as is with the refactoring I've already done in SVN, but it wouldn't be hard to implement the changes, if we decide to go that way. Maybe it's time to refactor here to get routine(s) that operate how we want (IMO more sanely than Matlab), and we provide wrappers that give Matlab-like behavior. Maybe we can also get these sane routines upstream into Scipy. At that point, however, I'm not sure what to do about the plotting functions, since there's a variety of behavior. Thoughts? Ryan -- Ryan May Graduate Research Assistant School of Meteorology University of Oklahoma -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] matplotlib+setuptools
Hi,
I'm sending a little module I use to force a particular version of
matplotlib and backend in my library.
This is imported in my package __init__.py to make sure the
environment is sane. It can also be imported in the beginning of the
app to set up a sane environment, which may be necessary if the app
uses matplotlib outside my library.
I don't think there is anything we can do within matplotlib to
address the version requirements.
The backend check could be a little easier if we modify matplotlib.use
() to be silent if the backend is already in use, or raise an error
if it isn't. ImportError seems appropriate, since use() is kind of
like an import. Calling switch_backend() is another option.
- Paul
# This program is public domain
"""
Configure plotter for plottools.
This must be imported first in __init__.py for plottools.
If your application uses matplotlib outside plottools, then
please do the following at the start of your application:
# Select matplotlib version and backend
import danse.common.plottools.config
Note that plottools requires particular versions of matplotlib
and a particular backend. As of this writing it is the WXAgg
backend for matplotlib>=0.98.
The plottools package uses pkg_resources if available to select
the correct version of matplotlib. If you need multiple matplotlib
versions in your path, be sure to use "easy_install -m" for all
of them. If a version is installed without "-m" that does not
meet the requirements, then pkg_resources.require() will fail,
even if you have installed a suitable version with "-m". In this
case you will need to fix up your site-packages directory,
probably by removing site-packages/matplotlib and the associated
egg file for that version, and reinstalling with "-m". You may
also need to edit site-packages/easy-install.pth.
"""
import sys
__all__ = []
plot_version="0.98"
plot_backend="WXAgg"
# Sort out matplotlib version
try:
import pkg_resources
pkg_resources.require("matplotlib>="+plot_version)
except ImportError:
import matplotlib
from distutils.version import StrictVersion as Version
if Version(matplotlib.__version__) < Version(plot_version):
raise ImportError("Matplotlib version must be %s or newer"%(plot_version,))
# Sort out matplotlib backend
import matplotlib
if 'matplotlib.backends' not in sys.modules:
# if no backend yet, be sure to use the correct one
matplotlib.use(plot_backend)
elif matplotlib.get_backend() != plot_backend:
# if a backend has already been selected, make sure it is the correct one.
raise ImportError("Matplotlib not using backend "+plot_backend)
--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] maximum recursion error with imshow
I noticed today, through a fault in my own code, that imshow produces a maximum recursion error if passed an extents list of strings instead of numbers. Its kind of a rediculous scenario, but I thought I should bring it up just in case. Darren -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
