Repository navigation
expand log demo to a tutorial #8863
Description
The behavior of log scales when dealing with non-positive values is a common gotcha issue.
This seems to only be documented at
https://matplotlib.org/api/scale_api.html#matplotlib.scale.LogScale and http://matplotlib.org/devdocs/gallery/pylab_examples/log_demo.html
The log-demo should be expanded to a tutorial with prose explaining
- npos clip vs mask behavior (fill_between incorrect with log y-axis and value 0 #8623 Addresses #8045 (set_yscale("log") inconsistent with semilogy()) #8056 and links there in)
- loglog vs semilog vs ax.set_scale vs plt.xscale/plt.yscale
- changing the base
- how ticking works with log scale (issues around http://matplotlib.org/users/dflt_style_changes.html?highlight=default%20changes#tick-label-formatting and issue around it (Minor ticks on log-scale colorbar are not cleared #8358 Default locator for log-scale messes up minor ticks sometimes #7200 ticklabels on log axes sometimes adds overwritten labels on top of existing ones #8622 Issue #6967 - symlog + minor ticks = exception #8353 Incorrect display of minor ticks in Log Scale plot with large font size #8419 weird bug when using custom formatter; tick labels overlapping #8401 Log-scale ignores Formatter #8517 Colorbar with imshow(logNorm) shows unexpected minor ticks #8307)
- maybe fold in the symlog demo (https://matplotlib.org/examples/pylab_examples/symlog_demo.html)
Activity
afvincent commented on Oct 24, 2017
@tacaswell I added #8307 to your list of issues related to a surprising behavior with ticking and log scale.
github-actions commented on Apr 14, 2023
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!
tacaswell commented on Apr 14, 2023
Still a good thing to be better documented.
timhoffm commented on Apr 14, 2023
So, keep?
github-actions commented on May 13, 2024
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!