matplotlib-users Mailing List for matplotlib

Dear Sam,

Could you please try the following patch? I think it will fix the issue, 
but I'm not sure -- I don't have this problem on my linux system. If it 
works, I'll commit it to svn.

(Robert Kern suggested modifying the setup.py to include a compiler 
command-line directive. IMO this is better because it will be in the 
source file and is thus more visible to anyone who wants to re-use the 
code. Additionally, it will modify the file, triggering a re-build.)

Samuel M. Smith wrote:

>Well, I gave up. I regressed and installed numpy 0.9.6 from the  
>package installer and looks like matplotlib works now.
>It sure blows my confidence when two months go by and there are  
>enough changes that I can't install from source anymore.
>I would like to try again but it would be nice to know what you did  
>to get it to work since what I did last time no longer works.
>
>Sam
>
>_______________________________________________
>Pythonmac-SIG maillist  -  Pyt...@py...
>http://mail.python.org/mailman/listinfo/pythonmac-sig
>  
>

>>>>> "Stefan" == Stefan van der Walt <st...@su...> writes:

    Stefan> But, after fixing all these problems, I still can't get it
    Stefan> to plot.  It might be worth including surface.py in the
    Stefan> examples directory, as a test, to guarantee that the 3D
    Stefan> code gets updated with the rest.

    Stefan> It could be that I am missing something completely obvious
    Stefan> -- I'd appreciate any help in getting it running!

This code is known to be broken (and never worked).  John Porter's
code originally worked as an add-on module to matplotlib.  Since then
TextWithDash has been refactored which broke mplot3d.  I've been
planning to refactor the code to make it work internally, eg like the
rest of pylab, but haven't gotten it done yet.

JDH

Hi all,

I am trying to get the examples from
http://www.scipy.org/Cookbook/Matplotlib/mplot3D
to work.

I found that the 3D code is already included in matplotlib (SVN
version), but that it does not work:

- axes3d.py makes use of pylab, but it is not imported.

- text_update_coords in axis3d.py refers to self._mytext.foo, but
  TextWithDash has been updated to use the form Text.foo(self,...)
  instead.

- The TextWithDash class's doesn't have a_twd_window_extent
  property. Instead of assigning it in update_coords, it should be
  assigned in __init__.

- When working with matrices, the following occurs:

  def bar(self,M=3DNone):
	M =3D somematrix or M

  which is not allowed.  It should be

        if nx.any(somematrix): M =3D somematrix

But, after fixing all these problems, I still can't get it to plot.
It might be worth including surface.py in the examples directory, as a
test, to guarantee that the 3D code gets updated with the rest.

It could be that I am missing something completely obvious -- I'd
appreciate any help in getting it running!

Cheers
St=E9fan

is there a way to modify the toolbars in matplotlib and add more functions,
like a button for averaging the data displayed then display it; draw
threshold levels and have a spin up button to change the level while drawin=
g
it?

Hi,

Thanks for all the replies, It helped me finding the the cause of the 
problem rather quickly. I did a special trick with the title, that is 
not accepted by the PS backend:

pylab.title("\begin{center} First line \\ Next line \end{center}")

I poked a bit in the code, and it seems that the version 0.87.2 does not 
offer real good alternative for this trick. When making the following 
modification in text.py, one can obtain the intended double title:

         if self.is_math_text():
             tmp = self._text.split("\n\n")
             lines = []
             for line1 in tmp:
                 if len(line1.strip()) > 0:
                     for line2 in line1.split(r"\\"):
                         lines.append(line2.strip())

Using this patch, I just have to use this code for a centered double title:

pylab.title("First line \\ Next line")

This works well and gives the same result independent of the backend 
that is being used. Is the proposed patch a good idea?

regards,

Toon

Jouni K Seppanen wrote:
> Toon Verstraelen <Too...@UG...> writes:
> 
>> I tried to use the PS backend of matplotlib 0.87.2 to create EPS
>> figures, but I got the error at the bottom of this email. 
> [...]
>> ! LaTeX Error: Something's wrong--perhaps a missing \item.
> 
> There is probably something in the text strings you are plotting that
> LaTeX doesn't like. You need to post an example of the script that
> produces the error so we can debug it.
> 

[snipping cross-posts]

Samuel M. Smith wrote:
> So I could either regress numpy or build Matplotlib from source.  Since
> I like being able to get
> the latest bug fixes for Matplotlib and the last time I build it from 
> svn it went without a hitch, I
> decided to try to build Matplotlib from source. Unfortunately it  didn't
> work this time. I get the error shown below.
> I have a powerbook g4 with 10.4.6 and Universal Python 
> 2.4.3-2006-04-07.dmg. What am I missing?

> gcc: src/_ns_cntr.c
> In file included from /usr/include/math.h:26,
>                  from /Library/Frameworks/Python.framework/Versions/
> 2.4/include/python2.4/pyport.h:90,
>                  from /Library/Frameworks/Python.framework/Versions/
> 2.4/include/python2.4/Python.h:55,
>                  from src/_ns_cntr.c:17:
> /usr/include/architecture/ppc/math.h:477: warning: conflicting types 
> for built-in function 'scalb'
> In file included from src/_ns_cntr.c:28:
> /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-
> packages/numpy/core/include/numpy/arrayobject.h:139: error: 
> redefinition of typedef 'ushort'
> /usr/include/sys/types.h:85: error: previous declaration of 'ushort' 
> was here

It looks like matplotlib should be building all of the _ns_*.c modules with
-DPY_ARRAY_TYPES_PREFIX=something_or_other .

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless enigma
 that is made terrible by our own mad attempt to interpret it as though it had
 an underlying truth."
  -- Umberto Eco

Well, I gave up. I regressed and installed numpy 0.9.6 from the  
package installer and looks like matplotlib works now.
It sure blows my confidence when two months go by and there are  
enough changes that I can't install from source anymore.
I would like to try again but it would be nice to know what you did  
to get it to work since what I did last time no longer works.

Sam