matplotlib-users Mailing List for matplotlib

On 2015年06月30日 6:41 AM, Benjamin Root wrote:
> It looks like your X data is one element larger than it needs to be. I
> know pcolor() accepts grids that are (N+1,M+1), and I *think* pcolormesh
> does the same. It will also accept grids that are (N,M) as well, but
> will drop the last row and collumn.
Yes, pcolormesh and pcolor use the same argument parsing and checking. 
They actually *want* N+1, M+1; the *acceptance* of N, M is a matlab-ism 
that is convenient for quick looks, but is also a potential source of error.
The OP has an X dimension of M+2, which indicates an error earlier in 
the OP's code.
Eric

Well, the way those work is essentially overlay one axes object over
another along with some extra fanagiling to link up the shared axis and put
ticks on opposing sides. If your projection is already available as an
axes, then you are good to go that way. However, it sounds what you want is
to have some things follow one transform while others follow another? That
is certainly doable, it is just a question of bookkeeping.
I would check to see if the axis_artist1 toolkit supplies what you need (or
at least some of it).
Ben Root
On Tue, Jun 30, 2015 at 1:20 PM, T J <tj...@gm...> wrote:
> Ok, sounds like I'll have to copy what those do, as I'm not planning on
> working with Cartesian or even curvilinear coordinates.
>
> On Tue, Jun 30, 2015 at 11:36 AM, Benjamin Root <ben...@ou...> wrote:
>
>> twinx()/twiny() I think is your best bet. It isn't a fully generic
>> solution, but I think it addresses most needs.
>>
>> Ben Root
>>
>> On Mon, Jun 29, 2015 at 6:00 PM, T J <tj...@gm...> wrote:
>>
>>> When I read the transformations documentation:
>>>
>>>
>>> http://matplotlib.org/devel/add_new_projection.html#creating-a-new-projection
>>>
>>> it seems like each projection is tied to an Axes instance. How might I
>>> go about plotting two different projections on the same axes? Let's just
>>> assume that the actual axes each projection draws is exactly same and all
>>> that differs between to the two is how data is mapped to axis coordinates.
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Don't Limit Your Business. Reach for the Cloud.
>>> GigeNET's Cloud Solutions provide you with the tools and support that
>>> you need to offload your IT needs and focus on growing your business.
>>> Configured For All Businesses. Start Your Cloud Today.
>>> https://www.gigenetcloud.com/
>>> _______________________________________________
>>> Matplotlib-users mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>>
>>>
>>
>

Ok, sounds like I'll have to copy what those do, as I'm not planning on
working with Cartesian or even curvilinear coordinates.
On Tue, Jun 30, 2015 at 11:36 AM, Benjamin Root <ben...@ou...> wrote:
> twinx()/twiny() I think is your best bet. It isn't a fully generic
> solution, but I think it addresses most needs.
>
> Ben Root
>
> On Mon, Jun 29, 2015 at 6:00 PM, T J <tj...@gm...> wrote:
>
>> When I read the transformations documentation:
>>
>>
>> http://matplotlib.org/devel/add_new_projection.html#creating-a-new-projection
>>
>> it seems like each projection is tied to an Axes instance. How might I
>> go about plotting two different projections on the same axes? Let's just
>> assume that the actual axes each projection draws is exactly same and all
>> that differs between to the two is how data is mapped to axis coordinates.
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Don't Limit Your Business. Reach for the Cloud.
>> GigeNET's Cloud Solutions provide you with the tools and support that
>> you need to offload your IT needs and focus on growing your business.
>> Configured For All Businesses. Start Your Cloud Today.
>> https://www.gigenetcloud.com/
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>>
>

Yeah, this is a long-standing design issue:
https://github.com/matplotlib/matplotlib/issues/1483
There are some changes that are happening that would make it possible for
me to refactor mplot3d in a way that would make this feasible. I could bite
the bullet and just provide a partial workaround to this problem by
providing a get_3d_data() method to each Artist3D subclass. Should be a
fairly easy task for someone at SciPy 2015.
On Tue, Jun 30, 2015 at 11:51 AM, kola <ko...@sp...> wrote:
> Hi,
>
> I am able to use set_3d_properties to set z data for my 3D line. However,
> if
> I want to get the zdata, I cannot find a function like get_zdata or
> get_3d_properites.
>
> Is there anyway to get the zdata associated with the line?
>
> Thanks,
> Kola
>
>
>
> --
> View this message in context:
> http://matplotlib.1069221.n5.nabble.com/get-3d-properties-tp45851.html
> Sent from the matplotlib - users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

It looks like your X data is one element larger than it needs to be. I know
pcolor() accepts grids that are (N+1,M+1), and I *think* pcolormesh does
the same. It will also accept grids that are (N,M) as well, but will drop
the last row and collumn.
Given your statement that it sometimes works, I suspect you have a bug in
your code somewhere that is causing your Xs and Ys to not always be exactly
the length you'd expect them to be.
I hope that helps!
Ben Root
On Mon, Jun 29, 2015 at 2:06 PM, Ronquillo, Edgar Nahum <ero...@la...
> wrote:
> Hello,
>
> I am getting this error when I try calling pcolormesh this way:
>
>
>
> pcolormesh(x, y, data.T, cmap=cmap, vmin=0, vmax=100)
>
>
>
> I am doing the transpose of data so I don’t know what could be causing
> this. By the way, it does work with some images. Any suggestions?
>
>
>
> Thanks in advance
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

twinx()/twiny() I think is your best bet. It isn't a fully generic
solution, but I think it addresses most needs.
Ben Root
On Mon, Jun 29, 2015 at 6:00 PM, T J <tj...@gm...> wrote:
> When I read the transformations documentation:
>
>
> http://matplotlib.org/devel/add_new_projection.html#creating-a-new-projection
>
> it seems like each projection is tied to an Axes instance. How might I go
> about plotting two different projections on the same axes? Let's just
> assume that the actual axes each projection draws is exactly same and all
> that differs between to the two is how data is mapped to axis coordinates.
>
>
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

Hi,
I am able to use set_3d_properties to set z data for my 3D line. However, if
I want to get the zdata, I cannot find a function like get_zdata or
get_3d_properites.
Is there anyway to get the zdata associated with the line?
Thanks,
Kola
--
View this message in context: http://matplotlib.1069221.n5.nabble.com/get-3d-properties-tp45851.html
Sent from the matplotlib - users mailing list archive at Nabble.com.