Commit 1cd6255
authored
DOC: Clarify contour levels parameter as boundaries to fix ambiguity
The previous documentation stated that `MaxNLocator` chooses "no more than n+1" levels, which was mathematically incorrect for the default case (n=7 produces 9 levels).
Additionally, the distinction between `contour` (lines) and `contourf` (filled regions) created confusion, as `contourf` produces one fewer region than the number of lines (unless `extend` is used).
This update redefines `levels` strictly as "contour boundaries." This terminology:
1. Is accurate for both functions (lines are at boundaries, regions are between them).
2. Remains correct regardless of the `extend` parameter.
3. Explicitly documents the default behavior for n=7.1 parent 787c773 commit 1cd6255
1 file changed
Lines changed: 7 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1487 | 1487 | | |
1488 | 1488 | | |
1489 | 1489 | | |
1490 | | - | |
1491 | | - | |
| 1490 | + | |
| 1491 | + | |
| 1492 | + | |
| 1493 | + | |
1492 | 1494 | | |
1493 | 1495 | | |
1494 | 1496 | | |
1495 | 1497 | | |
1496 | | - | |
1497 | | - | |
1498 | | - | |
| 1498 | + | |
| 1499 | + | |
| 1500 | + | |
1499 | 1501 | | |
1500 | 1502 | | |
1501 | 1503 | | |
| |||
0 commit comments