[Matplotlib-users] Why the V parameter in matplotlib.axes.Axes.contour must be increasing?
ben.v.root at gmail.com
Wed Aug 16 09:49:46 EDT 2017
Probably because nobody noticed that discrepancy before. I'd imagine it
would be fairly simple to apply a sort to the list of values within the
function itself. The underlying contouring implementation assumes a
monotonically increasing set of contour levels, and I would imagine that
MATLAB's version does too -- just that they sort the contour levels for you.
At the moment, I don't see any reason why we couldn't do that, too.
On Wed, Aug 16, 2017 at 8:33 AM, Xi Shen <davidshen84 at gmail.com> wrote:
> https://matplotlib.org/api/_as_gen/matplotlib.axes.Axes.contour.html says
> the contour function accept a vector parameter V which must be in
> increasing value. But the contour function in MATLAB does not have this
> I understand the underlining implementation of these two functions could
> be very different. I want to understand what is the purpose of this
> restriction, and if it possible to create a contour image the same as
> MATLAB does by using contour with V = [0 0]?
> Matplotlib-users mailing list
> Matplotlib-users at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Matplotlib-users