René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Path snapping does not respect quantization scale appropriate for Retina displays","articleBody":"Here's a toy version of something I'm working on:\n\n\u003cpre\u003eimport numpy as np, pylab as pl\nN = M = 10\nn = 1000\na = (np.random.standard_normal((n,N,M)) + 1j * np.random.standard_normal((n,N,M))) * .5**.5\nb = np.linalg.svd(a)\npl.clf()\nfor i in xrange(b[1].shape[1]):\n    _=pl.hist(b[1][:,i], bins=100, histtype='step', normed=True)\n\u003c/pre\u003e\n\n\nIf you run this with the macosx backend on a Retina display and carefully resize the window, you will find that the path snapping algorithm is snapping to the nearest two-pixel boundary, rather than the intended behavior of snapping to the nearest one-pixel boundary.\n\nI speculate that this is also an issue with marker placement and hatching.\n\nTwo solutions are apparent.\n\nOne is for the macosx backend to do a little dance of rescaling the transform matrices before and after passing paths through the path iterator.  This seems like a pain and not very portable.  I believe that the other backends will be growing high-DPI flavors soon!  [edit: just took a look and it seems like only the macosx backend uses the PathCleanupIterator.  Is that correct?]\n\nThe other solution is for the path iterator to take the image magnification factor as an argument, and thread this through the code to the actual path snapper.\n\nIncidentally, we might consider renaming the image magnification factor since it matters for vectors too.\n","author":{"url":"https://github.com/piannucci","@type":"Person","name":"piannucci"},"datePublished":"2013-12-28T00:04:06.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/2697/matplotlib/issues/2697"}