matplotlib-users Mailing List for matplotlib

>>>>> "Christopher" == Christopher Barker <Chr...@no...> writes:
 Christopher> well, duh. sorry for being such and idiot, but I'm
 Christopher> surprised that you can set numerix after importing
 Christopher> pylab.
You can't -- you need to change the numerix setting first (or use the
command line arg or the rc file)
import matplotlib
matplotlib.rcParams['numerix'] = 'numpy'
import pylab

Gary Ruben wrote:
> Yep, just do
> 
> from pylab import *
> rcParams['numerix'] = 'numpy'
well, duh. sorry for being such and idiot, but I'm surprised that you 
can set numerix after importing pylab.
> If I was developing something now, I would only bother supporting numpy.
That's my thought too, but I think I'll probably build Numeric an NumPy 
in anyway, as it's not hard to do.
Eric Firing wrote:
> For testing you may also take advantage of command-line arguments:
> 
> python examples/image_demo.py --Numeric
Excellent! that will make things much easier.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

>>>>> "Richard" == Richard Albright <ral...@in...> writes:
 Richard> thanks for the subsy tip!, it did exactly what i couldn't
 Richard> do using NullLocator() and NullFormatter(), regardless if
 Richard> i put it before or after the semilogy command.
That's probably because you were setting the major locator and you
should have been setting the minor locator.
Eg,
 from pylab import subplot, semilogy, NullLocator, show
 x = 1,2,3
 y = 1,10,100
 ax = subplot(111)
 ax.semilogy(x, y)
 ax.yaxis.set_minor_locator(NullLocator())
 show()

thanks for the subsy tip!, it did exactly what i couldn't do using
NullLocator() and NullFormatter(), regardless if i put it before or
after the semilogy command.
On Fri, 2006年07月14日 at 11:52 -0500, John Hunter wrote:
> >>>>> "PGM" == PGM <pgm...@gm...> writes:
> 
> >> There is an easier way, however.
> 
> PGM> That's what I like in matplotlib: no matter how hard you try,
> PGM> there's always a simpler solution you're not yet aware of...
> 
> hmm... if you try hard, you should be led to the easy way! while
> subsx and subsy are documented in semilogx and semilogy, I added some
> detail to make this more obvious.
> 
> Cheers,
> JDH
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
-- 
Rick Albright
Senior Quantitvative Analyst
Indie Research, LLC
254 Witherspoon Street
Princeton, NJ 08542
(609)497-1030
ral...@in...

>>>>> "PGM" == PGM <pgm...@gm...> writes:
 >> There is an easier way, however.
 PGM> That's what I like in matplotlib: no matter how hard you try,
 PGM> there's always a simpler solution you're not yet aware of...
hmm... if you try hard, you should be led to the easy way! while
subsx and subsy are documented in semilogx and semilogy, I added some
detail to make this more obvious.
Cheers,
JDH

> There is an easier way, however. 
That's what I like in matplotlib: no matter how hard you try, there's always a 
simpler solution you're not yet aware of...

>>>>> "PGM" == PGM <pgm...@gm...> writes:
 PGM> On Friday 14 July 2006 11:25, Richard Albright wrote:
 >> from pylab import * x=(1,2,3,4,5) y=(13, 22,19,26,32)
 >> set_major_locator(NullLocator())
 >> set_major_formatter(NullFormatter()) semilogy(x,y) show()
 PGM> Have you tried that ?
 PGM> gca().yaxis.set_minor_locator(NullLocator()) Or maybe I don't
 PGM> understand what you're trying to do...
I'm also a little unclear as to what Richard wants to do, but if you
want to turn off the minor ticks, your approach is correct. You just
need to make sure you set the minor locator *after* the call to
semilogy.
There is an easier way, however. The kwargs subsy is a sequence of
locations where you want the minor ticks (eg 1,2,5) for base-10.
You can set this list to be empty to turn off all the minor ticks
 In [3]: semilogy(x,y,subsy=[])
JDH

On Friday 14 July 2006 11:25, Richard Albright wrote:
> from pylab import *
> x=(1,2,3,4,5)
> y=(13, 22,19,26,32)
> set_major_locator(NullLocator())
> set_major_formatter(NullFormatter())
> semilogy(x,y)
> show()
Have you tried that ?
gca().yaxis.set_minor_locator(NullLocator()) 
Or maybe I don't understand what you're trying to do...

How can I turn off the decade ticks in the following simple example?
from pylab import *
x=(1,2,3,4,5)
y=(13, 22,19,26,32)
set_major_locator(NullLocator())
set_major_formatter(NullFormatter())
semilogy(x,y)
show()
I am building stock graphs with the library, but have not been able to
figure out how to turn off the decade tick marks. If its possible, any
advice on how to do this would be greatly appreciated. 
-- 
Rick Albright
Senior Quantitvative Analyst
Indie Research, LLC
254 Witherspoon Street
Princeton, NJ 08542
(609)497-1030
ral...@in...

On Thu, Jul 13, 2006 at 08:21:14PM -0400, Darren Dale wrote:
> On Thursday 13 July 2006 8:08 pm, Brian Wilfley wrote:
> > I'm afraid I mixed and matched inappropriately withe the enthought 2.=
4
> > beta 3 and matplotlibe 0.87.4 py2.4 pairing.
> >
> > Any thoughts?
>=20
> >
> > RuntimeError: module compiled against version 90709 of C-API but this
> > version of numpy is 90907
>=20
> I think the numpy version provided with enthought is pulled from the sv=
n=20
> repository. If this is true, it will make life difficult for packages l=
ike=20
> matplotlib for windows that are compiled against the latest numpy relea=
se, in=20
> this case 0.9.8. Somebody please correct me if I'm wrong.
>From http://code.enthought.com/enthon it looks like matplotlib is
distributed along with the package, so there should be no need to use
a separate install of matplotlib.
Regards
St=E9fan

Till Wagner <sac...@ya...> writes:
> leg.draw_frame(False) might be an option, but I use
> self.axes.grid(True) and when the legend has no
> borders, the grid is shown through the text and makes
> ist nearly unredable.
I use something like this ("setp(legendframe, linewidth=3D0.0)" is the
crucial command):
# http://matplotlib.sourceforge.net/matplotlib.pylab.html#-legend
legend(loc=3D'upper left', shadow=3DFalse)
legend =3D gca().get_legend()
legendtext =3D legend.get_texts()
legendlines =3D legend.get_lines()
legendframe =3D legend.get_frame()
setp(legendtext, fontsize=3D'small')
setp(legendlines, linewidth=3D1.5)
#legend.draw_frame(False) # don't draw the legend frame
setp(legendframe, linewidth=3D0.0)
legendframe.set_facecolor(0.98) # set the frame face color to light =
gray
HTH,
 Colin

You are right, concerning your comment below.
That will work just fine,
Mark
On 7/13/06, Eric Firing <ef...@ha...> wrote:
>
>
>
> But why is this better than the following?
>
> plot(Z[0,:], Z[1:,:])
>
> The latter would accomplish the same, be completely consistent with
> option 4, be completely explicit and unambiguous, require no more typing
> than using a kwarg, require no extra logic in the plot code, and require
> no extra documentation for the plot command.
>
> Eric
> >
> > As you said, there will be many more opinions,
> >
> > Mark
> >
> >
> >
> > To summarize, the options seem to be:
> >
> > 1) Leave plot argument parsing alone.
> > 2) Accept an Nx2 array in place of a pair of arguments containing x
> > and y.
> >
> > 3) Implement the Matlab model.
> > 4) Implement the Matlab model, but taking rows instead of columns in
> an
> > X or Y array that is 2-D.
> >
> > I am open to arguments, but my preference is the Matlab model. I
> don't
> > think that the difference in native array storage order matters
> much.
> > It is more important to have the API at the plot method and function
> > level match the way people think.
> >
> > Eric
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> >
> -------------------------------------------------------------------------
> > Using Tomcat but need to do more? Need to support web services,
> security?
> > Get stuff done quickly with pre-integrated technology to make your job
> easier
> > Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

In case there is some interest, I changed _mathtext_data.py to support 
nonslanted uppercase greek characters rather (\Omega & stuff, see .diff).
BTW, in _mathtext_data.py there is a line
font = FT2Font('/usr/local/share/matplotlib/cmr10.ttf')
I think this is a obsolete location, right? (at least I don't have it)
cheers,
steve
-- 
Random number generation is the art of producing pure gibberish as 
quickly as possible.

Christopher Barker wrote:
> Hi all,
> 
> I'm working on a MPL build for OS-X, and I'd like to be able to write 
> scripts that will test as much as I can. In particular, I want to have 
> this build work with Numeric, numarray and numpy.
> 
> To script that test, I need to be able to set numerix in a script, 
> rather than in matplotlibrc. Can that be done?
For testing you may also take advantage of command-line arguments:
python examples/image_demo.py --Numeric
for example, runs using Numeric as the numerix setting.
The relevant code in numerix/__init__.py is:
for a in sys.argv:
 if a in ["--Numeric", "--numeric", "--NUMERIC",
 "--Numarray", "--numarray", "--NUMARRAY",
 "--NumPy", "--numpy", "--NUMPY", "--Numpy",
 ]:
 which = a[2:], "command line"
 break
 del a
If such a command-line option is found, it overrides everything else.
Eric

On Thursday 13 July 2006 8:08 pm, Brian Wilfley wrote:
> Hello,
>
> I've just come across matplotlib and I'm very impressed. It looks very
> useful.
>
> I just installed on a WinXP machine:
> enthon-python2.4-1.0.0.beta3.exe
> matplotlib-0.87.4.win32-py2.4.exe.
>
> The install went fine. I also put the default matplotlibrc file into
> my %HOME%\.matplotlib.
>
> I ran ipython from the "Start" menu. Note that this runs ipython
> without the -pylab argument.
>
> I started to try the first example and had a problem with "from pylab
> import * ". Also this failure occured using the "ordinary" python
> shell. The output from ipython is below.
>
> I'm afraid I mixed and matched inappropriately withe the enthought 2.4
> beta 3 and matplotlibe 0.87.4 py2.4 pairing.
>
> Any thoughts?
>
> RuntimeError: module compiled against version 90709 of C-API but this
> version of numpy is 90907
I think the numpy version provided with enthought is pulled from the svn 
repository. If this is true, it will make life difficult for packages like 
matplotlib for windows that are compiled against the latest numpy release, in 
this case 0.9.8. Somebody please correct me if I'm wrong.

Hello,
I've just come across matplotlib and I'm very impressed. It looks very useful.
I just installed on a WinXP machine:
enthon-python2.4-1.0.0.beta3.exe
matplotlib-0.87.4.win32-py2.4.exe.
The install went fine. I also put the default matplotlibrc file into
my %HOME%\.matplotlib.
I ran ipython from the "Start" menu. Note that this runs ipython
without the -pylab argument.
I started to try the first example and had a problem with "from pylab
import * ". Also this failure occured using the "ordinary" python
shell. The output from ipython is below.
I'm afraid I mixed and matched inappropriately withe the enthought 2.4
beta 3 and matplotlibe 0.87.4 py2.4 pairing.
Any thoughts?
Thanks for your help.
Brian
--------------------ipython shell output----------------------------------
**********************************************************************
Python 2.4.3 - Enthought Edition 1.0.0.beta3 (#69, Jul 6 2006, 11:38:02) [MSC v
.1310 32 bit (Intel)]
Type "copyright", "credits" or "license" for more information.
IPython 0.7.2 -- An enhanced Interactive Python.
? -> Introduction to IPython's features.
%magic -> Information about IPython's 'magic' % functions.
help -> Python's own help system.
object? -> Details about 'object'. ?object also works, ?? prints more.
In [1]: from pylab import *
C:\Python24\lib\site-packages\matplotlib\font_manager.py:453: UserWarning: Could
 not open font file C:\WINDOWS\Fonts\ORLANDO.TTF
 warnings.warn("Could not open font file %s"%fpath)
---------------------------------------------------------------------------
exceptions.RuntimeError Traceback (most recent call
 last)
C:\Python24\<ipython console>
C:\Python24\Lib\site-packages\pylab.py
----> 1 from matplotlib.pylab import *
C:\Python24\Lib\site-packages\matplotlib\pylab.py
 198 import mlab #so I can override hist, psd, etc...
 199
--> 200 from axes import Axes, PolarAxes
 201 import backends
 202 from cbook import flatten, is_string_like, exception_to_str, popd, \
C:\Python24\Lib\site-packages\matplotlib\axes.py
 21 import cm
 22 from cm import ScalarMappable
---> 23 from contour import ContourSet
 24 import _image
 25 from ticker import AutoLocator, LogLocator, NullLocator
C:\Python24\Lib\site-packages\matplotlib\contour.py
 16
 17 from mlab import linspace, meshgrid
---> 18 import _contour
 19 from cm import ScalarMappable
 20 from cbook import iterable, is_string_like, flatten, enumerate, \
C:\Python24\Lib\site-packages\matplotlib\_contour.py
 15 else: # Must be numpy
 16 try:
---> 17 from matplotlib._ns_cntr import *
 18 except ImportError:
 19 numerix._import_fail_message("_contour", "_ns")
RuntimeError: module compiled against version 90709 of C-API but this version of
 numpy is 90907
In [2]:
----------------------------------------------------------