X Tutup
Skip to content

Change default interpolation to nearest#4622

Closed
jenshnielsen wants to merge 13 commits intomatplotlib:masterfrom
jenshnielsen:default_interpolation
Closed

Change default interpolation to nearest#4622
jenshnielsen wants to merge 13 commits intomatplotlib:masterfrom
jenshnielsen:default_interpolation

Conversation

@jenshnielsen
Copy link
Copy Markdown
Member

As discussed in the Scipy BOF I propose changing the default interpolation of imshow to nearest.

I haven't yet refreshed any of the tests. So this will likely fail.

@jenshnielsen
Copy link
Copy Markdown
Member Author

Need to refresh the following tests

matplotlib.tests.test_axes.test_specgram_angle_freqs.test
matplotlib.tests.test_axes.test_specgram_magnitude_noise.test
matplotlib.tests.test_axes.test_specgram_magnitude_noise.test
matplotlib.tests.test_axes.test_specgram_noise.test
matplotlib.tests.test_axes.test_specgram_noise.test
matplotlib.tests.test_axes.test_specgram_noise_angle.test
matplotlib.tests.test_backend_svg.test_noscale.test
matplotlib.tests.test_backend_svg.test_noscale.test
matplotlib.tests.test_image.test_image_clip.test
matplotlib.tests.test_image.test_image_clip.test
matplotlib.tests.test_image.test_image_clip.test
matplotlib.tests.test_image.test_image_cliprect.test
matplotlib.tests.test_image.test_image_cliprect.test
matplotlib.tests.test_image.test_image_cliprect.test
matplotlib.tests.test_image.test_image_composite_background.test
matplotlib.tests.test_image.test_image_composite_background.test
matplotlib.tests.test_image.test_image_composite_background.test
matplotlib.tests.test_image.test_rasterize_dpi.test
matplotlib.tests.test_image.test_rasterize_dpi.test
matplotlib.tests.test_patheffects.test_patheffect1.test
matplotlib.tests.test_patheffects.test_patheffect1.test
matplotlib.tests.test_patheffects.test_patheffect1.test
matplotlib.tests.test_patheffects.test_patheffect2.test
matplotlib.tests.test_patheffects.test_patheffect2.test matplotlib.tests.test_patheffects.test_patheffect2.test mpl_toolkits.tests.test_axes_grid.test_imagegrid_cbar_mode_edge.test

@efiring
Copy link
Copy Markdown
Member

efiring commented Jul 11, 2015

Changing to "nearest" makes sense to me; I have never seen the present default as useful.

@tacaswell
Copy link
Copy Markdown
Member

👍

@tacaswell tacaswell modified the milestones: next major release, Color overhaul Jul 11, 2015
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the comma be removed between "nearest" and "and 'bilinear'"?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mdboom
Copy link
Copy Markdown
Member

mdboom commented Jul 13, 2015

I agree with this change. However, the one downside is that it will increase file sizes for the vector backends (since the data will now be upsampled to the output resolution). We should probably include that as a note in the "What's new" about this change.

@WeatherGod
Copy link
Copy Markdown
Member

Doesn't that depend on whether the default is 'none' versus 'nearest'?

On Mon, Jul 13, 2015 at 12:47 PM, Michael Droettboom <
notifications@github.com> wrote:

I agree with this change. However, the one downside is that it will
increase file sizes for the vector backends (since the data will now be
upsampled to the output resolution). We should probably include that as a
note in the "What's new" about this change.


Reply to this email directly or view it on GitHub
#4622 (comment)
.

@mdboom
Copy link
Copy Markdown
Member

mdboom commented Jul 13, 2015

@WeatherGod: You're right. Ignore my comment.

@astrofrog
Copy link
Copy Markdown
Contributor

👍 for changing to nearest by default

@jradavenport
Copy link
Copy Markdown

👍 for nearest. I'm seeing more and more figures making it in to published literature using 'none', which are unreadable. Changing this default would promote best-practices for scientific figures.

@tacaswell tacaswell modified the milestones: Color overhaul, next major release (2.0) Oct 26, 2015
tacaswell and others added 5 commits November 4, 2015 22:50
CLN: Remove various Python 2.6 related workarounds
FIX: Apply asanyarray to arguments for pcolor and family
…ndent

Merge pull request matplotlib#5407 from tacaswell/doc_boxplot
tacaswell and others added 7 commits November 5, 2015 11:29
MNT: Remove uses of font.get_charmap

Conflicts:
    lib/matplotlib/tests/test_font_manager.py

Conflicts with merging the tests, resloved to add only relavent code.
Merge pull request matplotlib#5410 from mdboom/get-charmap-removal
Use a specific version of Freetype for testing
@jenshnielsen
Copy link
Copy Markdown
Member Author

replaced by #5416 against the correct branch and with the typo fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants

X Tutup