inaccurate marker positioning in plot()

mpl 1.5.3/2.0b4/master, no matplotlibrc

_xs = np.linspace(0, 30, 201); plt.plot(_xs, scipy.stats.lognorm.pdf(_xs / 14, .472) / 14, ".")

Note the slight inaccuracy in positioning of the markers at the positioning of the markers at the positions marked with the red circles, resulting in a "step-like" behavior (you may need to open the image in a larger viewer to notice it).

The data itself does not present this behavior, as can be checked just by zooming in these regions.

I wonder whether it is just a limitation on the ability of antialiasing to deliver a visual impression of sub-pixel accuracy. The steppiness is at the one-pixel level, but it doesn't look like simple pixel-snapping.

@mdboom

Turning snapping off does not help that much. I wonder if this is related to the way we 'stamp' the markers?

attn @mdboom

import numpy
import scipy.stats
import matplotlib.pyplot as plt
plt.ion()
fig, ax = plt.subplots()
_xs = np.linspace(0, 30, 201); 
ln, = ax.plot(_xs, scipy.stats.lognorm.pdf(_xs / 14, .472) / 14, ".")

Yes, it's definitely related to how we stamp the markers. We don't do individual subpixel positioning for the markers. We could do that but it would be significantly slower (so should be a user-configurable option).

I'm also suffering from this issue. See the attached script and image for an example of what happens to a grid of evenly spaced markers. This level of quality is simply not acceptable for professional use - it looks like something out of the 1980s, but this 2017, and subpixel positioning is no longer optional.

grid.py.txt

Could you repost that example. The link appears to be broken.

I would be curious if this is something that could be resolved with the Cairo rework?

import math
import numpy
import matplotlib
matplotlib.use('Agg')
import matplotlib.pyplot as plt
plt.style.use('dark_background')
fig = plt.figure()
ax = fig.add_subplot(111)
xv = []
yv = []
for y in range(10):
    for x in range(10):
        xv.append(x * 0.147)
        yv.append(y * 0.147)
ax.set_xlim(0, 10)
ax.set_ylim(0, 10)
plt.scatter(xv, yv)
fig.savefig('grid.png')

@WeatherGod

@WeatherGod It is indeed solved by mpl_cairo (in fact this was one of the original motivations for writing it). See second example at https://gitter.im/matplotlib/matplotlib?at=5963202789aea4761d81a829. (You even commenter right under it :-))
As a side note mpl_cairo also stamps the markers much faster (there's a timing script in the examples).

I hadn't noticed the marker positioning examples. I was more interested in the text kerning at the time. That's great to know that the Cairo-based backends can be a suitable work-around when they are available (I am open to making them the default over AGG, but that might have to wait until v3.0, and wider adoption of the newer C++ standards across compilers).

…

On Thu, Aug 3, 2017 at 11:17 AM, Antony Lee ***@***.***> wrote: @WeatherGod <https://github.com/weathergod> It is indeed solved by mpl_cairo (in fact this was one of the original motivations for writing it). See second example at https://gitter.im/matplotlib/matplotlib?at= 5963202789aea4761d81a829. (You even commenter right under it :-)) As a side note mpl_cairo also stamps the markers much faster (there's a timing script in the examples). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7233 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AARy-G6TeHkczcdOOvjZokIwOXP9bqzLks5sUeSbgaJpZM4KRdrP> .

not sure if related or said before, but either:

the pixel marker position is 1 pixel too high when other markers are fine
other markers positions are 1 pixel too low, while the pixel marker position if fine
(depending on if the axis is positioned correctly as well)

example:

plt.xlim(0, 3)
plt.ylim(0, 3)
plt.plot(.05, 1, ',b')
plt.plot(.1, 1, '.b')
plt.plot(.2, 1, 'ob', ms=10, mew=1)
plt.plot(.3, 1, ',b')
plt.plot(.3, 1, 'or', fillstyle='none', ms=10, mew=1)
plt.plot(.4, 1, '.b', ms=9)
plt.plot(.4, 1, 'or', fillstyle='none', ms=10, mew=1)    
plt.savefig('tst.png', dpi=100)

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!

Snap markers to subpixels instead of whole ones

Navigation Menu

Repository navigation

inaccurate marker positioning in `plot()` #7233

17 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

inaccurate marker positioning in plot() #7233

Description

Activity

efiring commented on Oct 7, 2016

tacaswell commented on Oct 8, 2016

tacaswell commented on Oct 29, 2016

mdboom commented on Dec 5, 2016

gson1703 commented on Aug 3, 2017

WeatherGod commented on Aug 3, 2017

WeatherGod commented on Aug 3, 2017

gson1703 commented on Aug 3, 2017

anntzer commented on Aug 3, 2017

WeatherGod commented on Aug 3, 2017

17 remaining items

Jona-L commented on Apr 22, 2020

github-actions commented on Oct 9, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

inaccurate marker positioning in `plot()` #7233