Re: [Matplotlib-users] matplot3d: add_collection3d: Turn off baseline?

[Benjamin R. <ben...@ou...>]

On Thu, Oct 31, 2013 at 9:43 AM, Guido Avvisati <gui...@gm...>wrote:

> Benjamin Root <ben.root@...> writes:
>
> >
> >
> > On Tue, Nov 20, 2012 at 8:12 PM, Stephen Gibson <Stephen.Gibson-
> FCV...@pu...> wrote:
> >
> > Ok. Adding an NaN as the last data point did not help.
> > However, I notice that the return path is two segments that go through
> (0,0).
> > i.e. the baseline (or return) path may actually start/finish at (0,0)
> > The attached image shows my data offset in y-direction by +1. The end
> points
> > have been set to y=0.5.  The baseline (or return path) is the line
> segment
> that
> > starts at the first data point, passes through (x=0,y=0), and ends at the
> last
> > data point.
> > Steve.
> >
> >
> > Actually, this might be related to a bug that was pointed out to me a
> while back that I just could not figure out.  Having this example might
> help
> in narrowing down the cause.  Essentially, the (0,0) vertex was being added
> even when it shouldn't have been.  The key difference in this example is
> that zdir='y' is used, which causes the (0,0) vertex to refer to the x,z
> coordinate.  Interesting...I will have to investigate further.Ben Root
> >
> >
> >
> >
> >
> --------------------------------------------------------------------------
> ----
> > Monitor your physical, virtual and cloud infrastructure from a single
> > web console. Get in-depth insight into apps, servers, databases, vmware,
> > SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> > Pricing starts from $795 for 25 servers or applications!
> > http://p.sf.net/sfu/zoho_dev2dev_nov
> >
> > _______________________________________________
> > Matplotlib-users mailing list
> > Matplotlib-users@...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >
>
>
> Hi,
>
> I have exactly the same problem described here. Is there any solution to
> turn off the baseline in the polycollection?
>
> Cheers,
> Guido
>
>
>
There was a pull request that was put together about 6 months ago that I
think fixed the problem, IIRC, but it broke the API and the submitter
eventually retracted the PR because it didn't seem like the right solution.
The problem is extremely nuanced and there is no clear solution,
unfortunately. The general idea is that the path codes are not being stored
with the vertices because the underlying object holding that data is a Path
(so the 3D vertices are stored separately, and as such, the list of
vertices diverges from the list of path codes). Perhaps, if there was a way
to make Path objects be able to hold 3D vertices, we might be able to solve
this issue once and for all?

Ben Root