matplotlib-users Mailing List for matplotlib

Hi all,
I am creating a GUI using wxPython and Matplotlib. In it, I am trying to
delete an axis in a figure and then adding another axis to the same figure.
In essence, I am attempting to dynamically update the figure. I am using
pylab.figure.
I am using the figure.delaxes function to delete the desired axes. That
works fine. I am then changing the geometry of the rest of the axes to
update the display. Afterwards, I am trying to append a new axes to the end
after updating the other axes (once again using change_geometry).
Pseudocode:
- delete the selected axis using figure.delaxes(axis)
- update the rest of the axes using change_geometry
- when it is time to add a new axis
 -update the current axes using change_geometry
 -add a subplot to the end
This approach works fine if the axes that was deleted was the axis on the
end (the last one). If the deleted axis was in the middle or beginning then
the figure.add_subplot(...) does not add an axis to the figure. Instead, it
returns the previous axis. So if there were two axes left when one axis in
the middle was deleted, ie. [axis1, axis2], figure.add_subplot would return
axis2 and so the axes list would still be [axis1, axis2]
This occurs both in the GUI and when run interactively via PyCrust.
Any thoughts on to why this would happen?
python 2.7
matplotlib version: 1.1.0
OS X 10.6.8

Gotcha ya working perfectly now thank you for the help!
Benjamin Root-2 wrote:
> 
> On Thursday, August 2, 2012, surfcast23 wrote:
> 
>>
>> Wouldn't
>>
>> X= np.ones((1, 45))
>> Y= np.zeros((32, 1))
>>
>> change the existing values of the elements to ones and zeros?
>>
>>
> I was just demonstrating what np.broadcast_arrays() does. Take your x and
> y arrays and put them through this function and put the outputs into
> plot_wireframe(). Ignore the ones() and zeros().
> 
> Ben Root
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 
-- 
View this message in context: http://old.nabble.com/Size-of-array-elements-when-using-Axes3D.plot_wireframe%28X%2C-Y%2C-Z%2C-*args%2C-**kwargs%29-tp34243823p34249265.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Friday, August 3, 2012, surfcast23 wrote:
>
> I tested it out and it does change all the values to ones and zeros. Is
> there
> a way to broadcast and keep the original values that were in the arrays?
> Thanks for the help
>
>
>
Don't use ones() and zeros(). It was just a way to swtup a demonstration
since I dont have your data. Use your data instead of my ones() and
zeros().
Also, it would be more useful to post your latest version of your code that
is causing problems so that we can double-check it, rather than guessing
what the problem is.
Cheers!
Ben Root

I tested it out and it does change all the values to ones and zeros. Is there
a way to broadcast and keep the original values that were in the arrays?
Thanks for the help
Benjamin Root-2 wrote:
> 
> On Thursday, August 2, 2012, surfcast23 wrote:
> 
>>
>> Okay thank you! The Matlab code I am basing this on takes arrays of
>> different
>> shapes with different sized elements ie
>> x = 1 512
>> y = 101 1
>> and I guess automatically makes the the same shape. Can you point me in
>> the
>> direction of documentation that will explain how I can do this in Python?
>>
>>
> Ok, I just double-checked the source for plot_wireframe(). It does not
> perform any broadcasting (which I consider to be a bug).
> 
> Until it is fixed, you will have to do the broadcasting yourself:
> 
> X= np.ones((1, 45))
> Y= np.zeros((32, 1))
> x, y = np.broadcast_arrays(X, Y)
> 
> Which produces x and y with the same shapes, and their values duplicated
> in
> the direction the array was "expanded".
> 
> Pass those into plot_wireframe().
> 
> Ben Root
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 
-- 
View this message in context: http://old.nabble.com/Size-of-array-elements-when-using-Axes3D.plot_wireframe%28X%2C-Y%2C-Z%2C-*args%2C-**kwargs%29-tp34243823p34249203.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Thursday, August 2, 2012, surfcast23 wrote:
>
> Wouldn't
>
> X= np.ones((1, 45))
> Y= np.zeros((32, 1))
>
> change the existing values of the elements to ones and zeros?
>
>
I was just demonstrating what np.broadcast_arrays() does. Take your x and
y arrays and put them through this function and put the outputs into
plot_wireframe(). Ignore the ones() and zeros().
Ben Root

sorry misssed this line "Which produces x and y with the same shapes, and
their values duplicated in
the direction the array was "expanded"."
surfcast23 wrote:
> 
> Wouldn't
> 
> X= np.ones((1, 45))
> Y= np.zeros((32, 1))
> 
> change the existing values of the elements to ones and zeros? 
> 
> 
> Benjamin Root-2 wrote:
>> 
>> On Thursday, August 2, 2012, surfcast23 wrote:
>> 
>>>
>>> Okay thank you! The Matlab code I am basing this on takes arrays of
>>> different
>>> shapes with different sized elements ie
>>> x = 1 512
>>> y = 101 1
>>> and I guess automatically makes the the same shape. Can you point me in
>>> the
>>> direction of documentation that will explain how I can do this in
>>> Python?
>>>
>>>
>> Ok, I just double-checked the source for plot_wireframe(). It does not
>> perform any broadcasting (which I consider to be a bug).
>> 
>> Until it is fixed, you will have to do the broadcasting yourself:
>> 
>> X= np.ones((1, 45))
>> Y= np.zeros((32, 1))
>> x, y = np.broadcast_arrays(X, Y)
>> 
>> Which produces x and y with the same shapes, and their values duplicated
>> in
>> the direction the array was "expanded".
>> 
>> Pass those into plot_wireframe().
>> 
>> Ben Root
>> 
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and 
>> threat landscape has changed and how IT managers can respond. Discussions 
>> will include endpoint security, mobile security and the latest in malware 
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>> 
>> 
> 
> 
-- 
View this message in context: http://old.nabble.com/Size-of-array-elements-when-using-Axes3D.plot_wireframe%28X%2C-Y%2C-Z%2C-*args%2C-**kwargs%29-tp34243823p34249160.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Wouldn't
X= np.ones((1, 45))
Y= np.zeros((32, 1))
change the existing values of the elements to ones and zeros? 
Benjamin Root-2 wrote:
> 
> On Thursday, August 2, 2012, surfcast23 wrote:
> 
>>
>> Okay thank you! The Matlab code I am basing this on takes arrays of
>> different
>> shapes with different sized elements ie
>> x = 1 512
>> y = 101 1
>> and I guess automatically makes the the same shape. Can you point me in
>> the
>> direction of documentation that will explain how I can do this in Python?
>>
>>
> Ok, I just double-checked the source for plot_wireframe(). It does not
> perform any broadcasting (which I consider to be a bug).
> 
> Until it is fixed, you will have to do the broadcasting yourself:
> 
> X= np.ones((1, 45))
> Y= np.zeros((32, 1))
> x, y = np.broadcast_arrays(X, Y)
> 
> Which produces x and y with the same shapes, and their values duplicated
> in
> the direction the array was "expanded".
> 
> Pass those into plot_wireframe().
> 
> Ben Root
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 
-- 
View this message in context: http://old.nabble.com/Size-of-array-elements-when-using-Axes3D.plot_wireframe%28X%2C-Y%2C-Z%2C-*args%2C-**kwargs%29-tp34243823p34249151.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Thursday, August 2, 2012, surfcast23 wrote:
>
> Okay thank you! The Matlab code I am basing this on takes arrays of
> different
> shapes with different sized elements ie
> x = 1 512
> y = 101 1
> and I guess automatically makes the the same shape. Can you point me in the
> direction of documentation that will explain how I can do this in Python?
>
>
Ok, I just double-checked the source for plot_wireframe(). It does not
perform any broadcasting (which I consider to be a bug).
Until it is fixed, you will have to do the broadcasting yourself:
X= np.ones((1, 45))
Y= np.zeros((32, 1))
x, y = np.broadcast_arrays(X, Y)
Which produces x and y with the same shapes, and their values duplicated in
the direction the array was "expanded".
Pass those into plot_wireframe().
Ben Root

Okay thank you! The Matlab code I am basing this on takes arrays of different
shapes with different sized elements ie 
x = 1 512
y = 101 1
and I guess automatically makes the the same shape. Can you point me in the
direction of documentation that will explain how I can do this in Python?
 
Benjamin Root-2 wrote:
> 
> On Thursday, August 2, 2012, surfcast23 wrote:
> 
>>
>>
>>
>> surfcast23 wrote:
>> >
>> > In the documentation it says that Axes3D.plot_wireframe(X, Y, Z, *args,
>> > **kwargs) takes 2D arrays as the first two arguments. Do the arrays
>> have
>> > to have the same size dimensions?
>> >
>> >
>>
>> Any one know?
> 
> 
> Working from memory, the first two have to at least be "broadcastable"
> into
> the shape of Z. But absolutely, if x, y, and z are 2d, they have to be
> the
> same shape. It makes no sense otherwise.
> 
> Cheers!
> Ben Root
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 
-- 
View this message in context: http://old.nabble.com/Size-of-array-elements-when-using-Axes3D.plot_wireframe%28X%2C-Y%2C-Z%2C-*args%2C-**kwargs%29-tp34243823p34248914.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Aug 2, 2012, at 5:25 PM, John Hunter wrote:
>
> I also extend my heartfelt thanks to Perry Greenfield and STScI. They
> have been supporting matplotlib since 2004 with ideas, code and
> developer resources. They employ Michael currently, and are part of
> the reason why he is able to take on the leadership of this large
> project.
>
John, it has been our great fortune have joined the matplotlib effort. 
It saved us an enormous effort. It has been an incredible pleasure 
working with you. I'm not sure you realize how very much Mike and I 
hope you can rejoin the matplotlib effort. It will always be there for 
you.
Perry