matplotlib-users Mailing List for matplotlib

On Mon, 24 Apr 2006, Christopher Barker apparently wrote: 
> I think it might use dvips or something to do that. rather than 
> reading and rendering the DVI itself. 

That is not my understanding,
which however is limited.

Cheers,
Alan Isaac

PS I have tried to reopen the discussion with the PyX 
developers.  I'll post any useful outcomes.

John Hunter wrote:
>>>>>> "Alan" == Alan G Isaac <ai...@am...> writes:
>     Alan> Is this the PyX approach?  I ask that in hopes there may
>     Alan> synergies that save some developer time.
> 
> pyx is GPL -- we've contacted them about relicensing their code but
> got nowhere.

I didn't think it was the PyX approach anyway, but I just took another 
look. Does anyone know for sure? In PyX's case, it is going from TeX to 
PS, so I think it might use dvips or something to do that. rather than 
reading and rendering the DVI itself.

Speaking of which, perhaps pdfTeX is an option. I think pdfTeX generates 
pdf directly, which we could either just use, or maybe parse. I don't 
know if that would be harder or easier than DVI though.

-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...

>>>>> "Alan" == Alan G Isaac <ai...@am...> writes:
    Alan> Is this the PyX approach?  I ask that in hopes there may
    Alan> synergies that save some developer time.

pyx is GPL -- we've contacted them about relicensing their code but
got nowhere.

JDH

Christopher Barker wrote:

> PyShell is good option, if you can get ipython to work with it.


oops, I meant PyCrust. Sorry.

-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...

> Darren Dale wrote: 
>> The basic approach is to extract the font layout information from the 
>> dvi files. LaTeX could be the only dependency. 


On Mon, 24 Apr 2006, Christopher Barker apparently wrote: 
> Wonderful idea! I've been hoping someone would write this for ages. This 
> could lead to using TeX as a layout engine for creating Reports, etc. in 
> all kinds of other apps as well. 


Is this the PyX approach?
I ask that in hopes there may
synergies that save some developer time.

Cheers,
Alan Isaac

Darren Dale wrote:
> The basic approach is to extract the font layout information from the
> dvi files. LaTeX could be the only dependency.

Wonderful idea! I've been hoping someone would write this for ages. This 
could lead to using TeX as a layout engine for creating Reports, etc. in 
all kinds of other apps as well.

I'm looking forward to seeing how it works out.

-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...

Matt Newville wrote:

> I think it would be easy to write a wxPython App (even with
> PythonCard) that provided
> a command-line which was passed off to IPython (say, on an Enter
> event).

PyShell is good option, if you can get ipython to work with it.

-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...

Eric,

I don't know much about setup and installation, but based on your 
message and a quick look at the relevant part of setupext.py, my guess 
is that there is something odd about your tk/tcl installation.  The code 
is trying to use methods provided by Tkinter to automatically locate the 
header files.  This code must work for nearly everyone, or else there 
would be many problem reports like yours.

You might be able to track down the problem by executing the header 
discovery code in find_tcltk line-by-line from the interpreter, or by 
adding lots of print statements.

Did you by any chance manually install your tk/tcl header files, as 
opposed to installing them as part of a *-devel rpm?  I am assuming you 
are running Linux.

Eric

Eric Emsellem wrote:
> Hi,
> 
> please let me know if this remark is irrelevant:
>  this is the third email mentioning that I still have to add one line in 
> setupext.py in order for matplotlib to be installed without crashing 
> (see below).
> For some reason this 'bug' (if it is one?) is present since many 
> versions and has not been solved for me although I have tried to send 
> emails regularly regarding this item. Please let me know if this is 
> normal or if it is just something not set up right for me.
> 
> ALSO: I posted a request for help on mplot3d twice, but got no feedback. 
> Any help is welcome!
> 
> thanks in advance,
> Eric
> 
> P.S.: here is what I have to do everytime I wish to install a new 
> version of matplotlib:
> 
> # add one line in setupext.py:
> 
>         o.tcl_inc="/usr/include/"
> 
> # before
>         if not os.path.exists(o.tcl_inc):
>             print 'cannot find tcl/tk headers. giving up.'
>             sys.exit()
>     return o
> 
> 
> -------------------------------------------------------
> 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

>>>>> "Eric" == Eric Emsellem <ems...@ob...> writes:

    Eric> Hi, please let me know if this remark is irrelevant: this is
    Eric> the third email mentioning that I still have to add one line
    Eric> in setupext.py in order for matplotlib to be installed
    Eric> without crashing (see below).  For some reason this 'bug'
    Eric> (if it is one?) is present since many versions and has not
    Eric> been solved for me although I have tried to send emails
    Eric> regularly regarding this item. Please let me know if this is
    Eric> normal or if it is just something not set up right for me.

    Eric> ALSO: I posted a request for help on mplot3d twice, but got
    Eric> no feedback. Any help is welcome!


mplot3 is not in any official matplotlib version -- it resides in svn 
and is awaiting integration.  I took a stab at this after your last
email but ran into difficulties.  Thus you should consider mplot3d
unsupported until we make a release that includes it.

    Eric> thanks in advance, Eric

    Eric> P.S.: here is what I have to do everytime I wish to install
    Eric> a new version of matplotlib:

    Eric> # add one line in setupext.py:

    Eric>          o.tcl_inc="/usr/include/"


The problem is that this fixes the bug for your system, but is not a
general solution.  Other platforms will put their tcl/tk libs in a
different place.  So we need a generic solution which will work across
platforms, which is why I haven't committed this.  Granted
/usr/include is a standard location, and this would be a good fallback
to try if the current method fails (it fails for you and works for
most -- perhaps some tcl config app is missing on your system?).

JDH

Hi,

please let me know if this remark is irrelevant:
  this is the third email mentioning that I still have to add one line 
in setupext.py in order for matplotlib to be installed without crashing 
(see below).
For some reason this 'bug' (if it is one?) is present since many 
versions and has not been solved for me although I have tried to send 
emails regularly regarding this item. Please let me know if this is 
normal or if it is just something not set up right for me.

ALSO: I posted a request for help on mplot3d twice, but got no feedback. 
Any help is welcome!

thanks in advance,
Eric

P.S.: here is what I have to do everytime I wish to install a new 
version of matplotlib:

# add one line in setupext.py:

         o.tcl_inc="/usr/include/"

# before
         if not os.path.exists(o.tcl_inc):
             print 'cannot find tcl/tk headers. giving up.'
             sys.exit()
     return o

>>>>> "Matt" == Matt Newville <new...@ca...> writes:

    Matt> Hi Marc, I'm not very familiar with IPython (probably to my
    Matt> detriment), but I believe this may be an inherent problem
    Matt> with wx v. command-line program, and have little to do with
    Matt> MPlot, matplotlib, or IPython.  That is, I think that
    Matt> wxWidgets/wxPython's MainLoop() is never really going to
    Matt> interact well with a command-line application.  I'd be happy

ipython has a wx mode (-pylab with a wx* backend or -wthread for
general wx apps) which is designed to allow you to control wx apps
from the ipython shell.  It does this by starting the wx application
mainloop and then hijacking the wx mainloop so that application
attempts to start the mainloop will be ignored.

IPython/Shell.py
def hijack_wx():
    """Modifies wxPython's MainLoop with a dummy so user code does not
    block IPython.  The hijacked mainloop function is returned.
    """    
    ...snip...

it then runs a wx timer to check for input from the shell user.

The bulk of this was written by Fernando and myself, and neither of
us pretend to be wx experts, so it is quite possible that something is
not working right and can be improved.  It might be as simple as a
need to update the hijack function for a new version of wx.  Or it
might be something deep, subtle and nasty.  Or it might simply be user
error.  Without example code that replicates the problem, it's
difficult to say.

I suggest that Marc try and run some of the embedding_in_wx*
applications in the matplotlib examples dir from the ipython shell and
see if these work.  And then gradually add some of the functionality
you are using in your real app (eg dynamic updates).

Marc, my guess is that you are mixing programming idioms (OO and
pylab).  For an application like yours, you should not be using pylab
at all, and I see that you are with the pylab.ion call.  You should
follow the examples of embedding_in_wx* and then call
fig.canvas.draw() when you want your figure to draw.  Note that
interactive mode will not affect OO calls, eg even if you do

  ax.plot(something)

you will still need to do

  fig.canvas.draw()

since the interactive mode only applies to *pylab* plot commands, eg, 

  pylab.plot(something)

Recode your application so that pylab is imported nowhere, and call
canvas.draw() when you need the canvas to update.  You can post pylab
snippets here if you need help translating them to OO matplotlib.

JDH

I had no troubles installing matplotlib on my 32-bit laptop, but cannot
get it to install on my amd64 debian desktop. I've pulled in the latest
svn version (to go with the latest numpy and scipy), then run:

$ python setup.py install

and after a few ms of successful compile get the following error:

building 'matplotlib._agg' extension
gcc options: '-pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall
-Wstrict-prototypes -fPIC'
creating build/temp.linux-x86_64-2.3/agg23
creating build/temp.linux-x86_64-2.3/agg23/src
compile options: '-Iagg23/include -Isrc -Iswig -I/usr/include/python2.3 -c'
gcc: agg23/src/agg_path_storage.cpp
gcc: installation problem, cannot exec 'cc1plus': No such file or directory
gcc: installation problem, cannot exec 'cc1plus': No such file or directory
error: Command "gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall
-Wstrict-prototypes -fPIC -Iagg23/include -Isrc -Iswig
-I/usr/include/python2.3 -c agg23/src/agg_path_storage.cpp -o
build/temp.linux-x86_64-2.3/agg23/src/agg_path_storage.o" failed with
exit status 1

I have verified that the required files are present:

$ locate cc1plus
/usr/lib/gcc/x86_64-linux-gnu/3.4.6/cc1plus
/usr/lib/gcc-lib/x86_64-linux-gnu/3.3.6/cc1plus

which is basically the same as my 32-bit machine but with the
correspondingly different directory name, so it must be a linkage
problem. I'd like to try adding -m64 in the gcc flags, but have no idea
where to add that in when building via python.

1) How do I fix this?

2) Would my fix work? I can't find the gcc flags anywhere in the
matplotlib directory so I'm guessing this is passed on to main python
installation to construct (but don't know where) - is this correct?

Many thanks,

Angus.
-- 
Angus McMorland
email a.m...@au...
mobile +64-21-155-4906

PhD Student, Neurophysiology / Multiphoton & Confocal Imaging
Physiology, University of Auckland
phone +64-9-3737-599 x89707

Armourer, Auckland University Fencing
Secretary, Fencing North Inc.

Hi Marc,

I'm not very familiar with IPython (probably to my detriment), but I
believe this may
be an inherent problem with wx v. command-line program, and have
little to do with
MPlot, matplotlib, or IPython.   That is, I think that
wxWidgets/wxPython's MainLoop()
is never really going to interact well with a command-line
application.  I'd be happy
to be proven wrong -- I've hit this problem myself and been unable to
reliably solve it.
Anyway, can you send a simple example that demonstrates non-responsiveness?

I think it would be easy to write a wxPython App (even with
PythonCard) that provided
a command-line which was passed off to IPython (say, on an Enter
event).  I'd be much
more confident that  you could get the wx widgets to respond, and
still have a working
command-line.  I don't know whether this is  compatible with the "IPython w=
ay".

Cheers,

--Matt Newville

I just ran our sample against the latest SVN and it's still failing.  

I've hand coded a quick fixed aspect ratio setter so we can get by with the current version.  Mike will send out a sample script that shows the problem some time later this week (we're in the middle of a big release right now so it might be later rather than earlier).

Ted

----- Original Message -----
From: John Hunter <jdh...@ni...>
Date: Friday, April 21, 2006 8:20 pm
Subject: Re: [Matplotlib-users] autoscale and "equal aspect" mode

> >>>>> "Michael" == Michael P Mossey <mo...@jp...> writes:
> 
>    Michael> I'm using this aspect mode: axes.set_aspect( 'equal',
>    Michael> adjustable='datalim' )
> 
>    Michael> With several xy line plots on the axes, autoscaling
>    Michael> doesn't seem to occur properly. It cuts off part of the
>    Michael> data. Is this a known issue? I don't have a simple script
>    Michael> to replicate it---I'll have to pull that out of a larger
>    Michael> program---but just wanted to check if it is known. I
>    Michael> don't see anything in the bug tracker.
> 
> matplotlib version number?  a lot of work as been done quite recently
> on aspect handling.  You should test against the latest svn and then
> post a complete example describing what is wrong if you are
> unsatisfied.
> 
> 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 
> Geronimohttp://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
>