Fix Slicer matplotlib-warning.#217
Fix Slicer matplotlib-warning.#217jcapriot merged 2 commits intosimpeg:masterfrom prisae:slicer-fix-matplotlib-warning
Conversation
|
What I am not sure about is... I think I included |
Codecov Report
@@ Coverage Diff @@
## master #217 +/- ##
==========================================
+ Coverage 81.39% 81.41% +0.01%
==========================================
Files 24 24
Lines 5197 5202 +5
==========================================
+ Hits 4230 4235 +5
Misses 967 967
Continue to review full report at Codecov.
|
|
That needs more testing, because vmin/vmax are log if the norm is log... so the current version will fail. I think we need to talk about this, and maybe get rid of clim to simplify things. |
|
Good to go and ready for review. Works also with norms. I made another small change. We should not patch matplotlib, and propagate deprecation warnings. We should simply not cause matplotlib errors. So now, these two possibilities run without warnings: and and these two cases will raise a matplotlib deprecation warning, because they should be adjusted (to the above versions): and Here a minimum working example to test: |
jcapriot
left a comment
There was a problem hiding this comment.
This looks good for the slicer
Closes #215