René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Doc]: Contour functions: auto-generated levels","articleBody":"### Documentation Link\r\n\r\nhttps://matplotlib.org/devdocs/api/_as_gen/matplotlib.axes.Axes.contourf.html\r\nhttps://matplotlib.org/devdocs/api/_as_gen/matplotlib.axes.Axes.tricontourf.html\r\n\r\n### Problem\r\n\r\nThis applies to `tricontour/f` and `contour/f`.\r\n\r\nThe documentation of the contour functions' `levels` parameter states:\r\n\r\n```\r\n            If an int *n*, use `~matplotlib.ticker.MaxNLocator`, which tries\r\n            to automatically choose no more than *n+1* \"nice\" contour levels\r\n            between *vmin* and *vmax*.\r\n```\r\n\r\nThis is not true, the levels are always chosen betwen `Z.min()` and `Z.max()`. There is no way for the user to influence this when using the integer parameter variant. See implementation in `contour.py`: `ContourSet._autolev()`.\r\nEspecially deceptive because the text as written is very much what one would expect, but that functionality does not exist (and never has).\r\n\r\n### Suggested improvement\r\n\r\nChange \"between *vmin* and *vmax*\" to something like \"in the data range\" or more explicit \"between minimum and maximum values of *Z*\"","author":{"url":"https://github.com/martok","@type":"Person","name":"martok"},"datePublished":"2022-10-07T18:43:02.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/24121/matplotlib/issues/24121"}