Axes3d

Hello list,

I know it is not recommended to use matplotlib for 3d plotting, but for a
while simple plots worked fine for me. This is not the case with actual svn
version and therefore my question is: Would it break at lost or cost much
effort to make the 3d-plot-examples of the Cookbook work?

if I try:
[1] import matplotlib.axes3d as p3
I get the error attached below.

Thanks for any advise in advance.

best regards Matthias

···

---------------------------------------------------------------------------
<type 'exceptions.ImportError'> Traceback (most recent call last)

/home/michler/CompPhys_2008/Uebungsaufgaben/050_Antidot/3D_matplotlib/<ipython

in <module>()

/scratch/michler/SOFT/lib/python2.5/site-packages/matplotlib/axes3d.py in
<module>()
     14 from axes import Axes
     15 import cbook
---> 16 from transforms import unit_bbox
     17
     18 import numpy as np

<type 'exceptions.ImportError'>: cannot import name unit_bbox

/scratch/michler/SOFT/lib/python2.5/site-packages/matplotlib/axes3d.py(16)<module>()

     15 import cbook
---> 16 from transforms import unit_bbox
     17

I'm not very familiar with how axes3d works, but just by looking at the number of transform calls and objects, it appears that it will take significant effort to update it. It was never one of the goals of the transformation refactoring to have that working. Personally, I'm +1 on removing axes3d.py to avoid confusion.

However, a motivated user could follow the information in API_CHANGES to update axes3d.py. I'd be happy to help if you got stuck, but I don't really have the motivation/mandate to do the whole thing myself.

Cheers,
Mike

Matthias Michler wrote:

···

Hello list,

I know it is not recommended to use matplotlib for 3d plotting, but for a while simple plots worked fine for me. This is not the case with actual svn version and therefore my question is: Would it break at lost or cost much effort to make the 3d-plot-examples of the Cookbook work?

if I try:
[1] import matplotlib.axes3d as p3
I get the error attached below.

Thanks for any advise in advance.

best regards Matthias

---------------------------------------------------------------------------
<type 'exceptions.ImportError'> Traceback (most recent call last)

/home/michler/CompPhys_2008/Uebungsaufgaben/050_Antidot/3D_matplotlib/<ipython > in <module>()

/scratch/michler/SOFT/lib/python2.5/site-packages/matplotlib/axes3d.py in <module>()
     14 from axes import Axes
     15 import cbook
---> 16 from transforms import unit_bbox
     17 18 import numpy as np

<type 'exceptions.ImportError'>: cannot import name unit_bbox
  

/scratch/michler/SOFT/lib/python2.5/site-packages/matplotlib/axes3d.py(16)<module>()
    

     15 import cbook
---> 16 from transforms import unit_bbox
     17

-------------------------------------------------------------------------
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
Matplotlib-users@lists.sourceforge.net
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

Michael Droettboom wrote:

I'm not very familiar with how axes3d works, but just by looking at the number of transform calls and objects, it appears that it will take significant effort to update it. It was never one of the goals of the transformation refactoring to have that working. Personally, I'm +1 on removing axes3d.py to avoid confusion.

I agree. This is overdue.

Eric

Mike, just a question about the new transforms backend -- can the input
dimensionality be greater than 2? (I realize functions to do so probably
don't currently exist, but the question is about the transforms
machinery itself.)

-Andrew

Michael Droettboom wrote:

···

I'm not very familiar with how axes3d works, but just by looking at the
number of transform calls and objects, it appears that it will take
significant effort to update it. It was never one of the goals of the
transformation refactoring to have that working. Personally, I'm +1 on
removing axes3d.py to avoid confusion.

However, a motivated user could follow the information in API_CHANGES to
update axes3d.py. I'd be happy to help if you got stuck, but I don't
really have the motivation/mandate to do the whole thing myself.

Cheers,
Mike

Matthias Michler wrote:
  

Hello list,

I know it is not recommended to use matplotlib for 3d plotting, but for a
while simple plots worked fine for me. This is not the case with actual svn
version and therefore my question is: Would it break at lost or cost much
effort to make the 3d-plot-examples of the Cookbook work?

if I try:
[1] import matplotlib.axes3d as p3
I get the error attached below.

Thanks for any advise in advance.

best regards Matthias

---------------------------------------------------------------------------
<type 'exceptions.ImportError'> Traceback (most recent call last)

/home/michler/CompPhys_2008/Uebungsaufgaben/050_Antidot/3D_matplotlib/<ipython
> in <module>()

/scratch/michler/SOFT/lib/python2.5/site-packages/matplotlib/axes3d.py in
<module>()
     14 from axes import Axes
     15 import cbook
---> 16 from transforms import unit_bbox
     17
     18 import numpy as np

<type 'exceptions.ImportError'>: cannot import name unit_bbox
  

/scratch/michler/SOFT/lib/python2.5/site-packages/matplotlib/axes3d.py(16)<module>()
    

     15 import cbook
---> 16 from transforms import unit_bbox
     17

-------------------------------------------------------------------------
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
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
  

In theory, yes, but it's a completely untested theory. Each transform class has an input_dims and output_dims member that defines the input and output dimensions. So theoretically, you could create a perspective or orthogonal projection that maps from 3D to 2D.

Cheers,
Mike

Andrew Straw wrote:

···

Mike, just a question about the new transforms backend -- can the input
dimensionality be greater than 2? (I realize functions to do so probably
don't currently exist, but the question is about the transforms
machinery itself.)

-Andrew

Michael Droettboom wrote:
  

I'm not very familiar with how axes3d works, but just by looking at the number of transform calls and objects, it appears that it will take significant effort to update it. It was never one of the goals of the transformation refactoring to have that working. Personally, I'm +1 on removing axes3d.py to avoid confusion.

However, a motivated user could follow the information in API_CHANGES to update axes3d.py. I'd be happy to help if you got stuck, but I don't really have the motivation/mandate to do the whole thing myself.

Cheers,
Mike

Matthias Michler wrote:
  

Hello list,

I know it is not recommended to use matplotlib for 3d plotting, but for a while simple plots worked fine for me. This is not the case with actual svn version and therefore my question is: Would it break at lost or cost much effort to make the 3d-plot-examples of the Cookbook work?

if I try:
[1] import matplotlib.axes3d as p3
I get the error attached below.

Thanks for any advise in advance.

best regards Matthias

---------------------------------------------------------------------------
<type 'exceptions.ImportError'> Traceback (most recent call last)

/home/michler/CompPhys_2008/Uebungsaufgaben/050_Antidot/3D_matplotlib/<ipython > in <module>()

/scratch/michler/SOFT/lib/python2.5/site-packages/matplotlib/axes3d.py in <module>()
     14 from axes import Axes
     15 import cbook
---> 16 from transforms import unit_bbox
     17 18 import numpy as np

<type 'exceptions.ImportError'>: cannot import name unit_bbox
  

/scratch/michler/SOFT/lib/python2.5/site-packages/matplotlib/axes3d.py(16)<module>()
    

     15 import cbook
---> 16 from transforms import unit_bbox
     17

-------------------------------------------------------------------------
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
Matplotlib-users@lists.sourceforge.net
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

Done

home:~/mpl/lib/matplotlib> cat axes3d.py
raise NotImplmentedError('axes3d is not supported in matplotlib-0.98.
You may want to try the 0.91.x maintenance branch')

···

On Fri, Jun 20, 2008 at 12:12 PM, Eric Firing <efiring@...202...> wrote:

transformation refactoring to have that working. Personally, I'm +1 on
removing axes3d.py to avoid confusion.