Follow up on #21309.
The problem is contour on discontinuous functions. Mpl makes the (sane) assumption that, if a quad's corners have the values 0.0 and 0.78, the level contour of 0.51 (for example) has to pass somewhere through the quad, and draws it. This is incorrect where the function is actually discontinuous, but of course mpl has no way of knowing that.
See this stackoverflow post or here.
Proposed solutionA simple solution for this would be to allow for a user-supplied float parameter, max_jump or discontinuity_threshold or something like that, defaulting to np.inf. If within a quad the function values differ by more than this threshold, a discontinuity is assumed and the level contour is assumed not to pass through the quad.
No response
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4