matplotlib-users Mailing List for matplotlib

On Thu, Jul 15, 2010 at 9:13 PM, Jeff Berry <jj...@em...>wrote:

> Hi,
>
> I'm using the new mixed axes feature in matplotlib 1.0.0 to combine 3D and
> 2D plots in a single figure. The problem is that the 3D axes have a lot of
> extra white space around them that prevents the plot to line up flush with
> the 2D plot. Here is an example image of this:
>
> using matplotlib: http://www.u.arizona.edu/~jjberry/matplotlib.png<http://www.u.arizona.edu/%7Ejjberry/matplotlib.png>
>
> vs. matlab of the same thing: http://www.u.arizona.edu/~jjberry/matlab.png<http://www.u.arizona.edu/%7Ejjberry/matlab.png>
>
> Is there any way of changing the space on the 3D axis to look more like the
> matlab figure?
>
> Thanks,
> Jeff Berry
>
>
>
Jeff, thanks for pointing this out.  An inadvertant side-effect of using
add_subplot() for 3d axes seems to be that the creation process greatly
restricts the available space for the 3d figure to be plotted.  Whereas
doing the old Axes3D() approach (albeit for non-subplots) would allow the 3D
figure to use all the available space.

I am currently examining this issue right now and might be tied to another
bug that has been reported recently.

Ben Root


>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

2010/7/18 Simon Friedberger <sim...@a-...>:
> On 22:49 Sat 17.07.10, Friedrich Romstedt wrote:
>> Maybe try to use axes.set_xticks() first, see
>> http://matplotlib.sourceforge.net/api/axes_api.html#matplotlib.axes.Axes.set_xticks
>> .
> I know about that but couldn't find any useful way. Could you be more
> specific?

Try to add:

ax.set_xticks(range(0, 10))
ax.set_yticks(range(0, 10))

before the imshow call.

For some reason it must happen before the imshow call and not after,
else the yscaling will change (I don't understand this).

>> Your code on pocoo is messed up with whitespace.  Is that intentional?
> Messed up? It looks all good to me.

Sorry, but there is plenty of whitespace at the end of each line when
I copy-paste the code, even in raw format.

hth you,
Friedrich

On 22:49 Sat 17.07.10, Friedrich Romstedt wrote:
> Maybe try to use axes.set_xticks() first, see
> http://matplotlib.sourceforge.net/api/axes_api.html#matplotlib.axes.Axes.set_xticks
> .
I know about that but couldn't find any useful way. Could you be more
specific?

> Your code on pocoo is messed up with whitespace.  Is that intentional?
Messed up? It looks all good to me.

Regards
Simon