René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Issue(?): head size of FancyArrowPatch changes between interactive figure and picture export","articleBody":"### Issue (?)\n\nWhen plotting a arrow (with `FancyArrowPatch` from `matplotlib.patches`), and exporting it to a picture, the size of its head is not consistent with what is displayed in the interactive figure. (The linewidth seems to remain OK between interactive and exported file, whatever format is used.) \n\nAs far as I understand, it seems to be DPI-related:\n- If the DPI value is the same between the interactive figure and the export made with `savefig`, then everything is fine.\n- However, if I want to export with DPI 3 times bigger than in the interactive figure (for example 300 DPI instead of 100 DPI), one workaround I found is to use a mutation_scale 3 times bigger than before when plotting the interactive figure. Unfortunately, it is neither really convenient nor satisfying as it affects what is displayed in the interactive figure (the arrow head is 3 times bigger...) \n\nI don't know if it is a bug or the expected behavior, but I find it disturbing to have an export that is (that) different from the interactive display.\n### Environment infos\n- Linux, Python 2.7 (from Anaconda2), Matplotlib v1.5.0\n- Interactive backend is Qt4Agg\n### Example script\n\nHere is a script that generates a figure with 2 arrows (FancyArrowPatch), and exports it to different formats:\n\n```\nimport matplotlib.pyplot as plt\nfrom matplotlib.patches import FancyArrowPatch\nplt.ion() # My interactive backend is Qt4Agg, with default @ 80 DPI\n\n\"\"\" Prepare and plot 2 FancyArrowPatch instances, the 2nd one with a \n    mutation_scale parameter 3 times bigger than the 1st one. \n\"\"\"\ncommon_opts = dict(arrowstyle=u'-\u003e', lw=3)\narrow_patch_0 = FancyArrowPatch(posA=(0.2, 0.8), posB=(0.8, 0.65),\n                                mutation_scale=50, **common_opts)\narrow_patch_1 = FancyArrowPatch(posA=(0.2, 0.2), posB=(0.8, 0.45),\n                                mutation_scale=150, **common_opts)\n\nfig, ax = plt.subplots(figsize=(8, 6), dpi=100)\nax.text(0.2, 0.85, \"mutation_scale = 50\", ha='left', va='bottom')\nax.text(0.2, 0.15, \"mutation_scale = 150\", ha='left', va='top')\nfor arrow_patch in [arrow_patch_0, arrow_patch_1]:\n    ax.add_patch(arrow_patch)\n\n\"\"\" Export to different formats, with different DPI values if rasterized.\n\"\"\"\ncommon_prefix = 'FancyArrowPatch_testfile'\nfig.savefig(common_prefix + '.eps')\nfig.savefig(common_prefix + '.pdf')\nfig.savefig(common_prefix + '_300dpi.png', dpi=300)\nfig.savefig(common_prefix + '_100dpi.png', dpi=100)\nfig.savefig(common_prefix + '_300dpi.jpg', dpi=300)\nfig.savefig(common_prefix + '_100dpi.jpg', dpi=100)``\n```\n\nAnd below is a picture that compares the 6 different output files (2 x 3 bottom panels) with a screenshot of the interactive figure (top center panel).\n![fancyarrowpatch_export_issue](https://cloud.githubusercontent.com/assets/17270724/13196822/0c681712-d7da-11e5-9958-9c6e12878f21.png)\n### Observations about the example\n\nOne can see that with the raster formats (PNG and JPG):\n- @ 100 DPI (blue labels), the exports are the same as in the screenshot of the interactive display with 100 DPI. \n- @ 300 DPI (red labels), the exports differ from the interactive display. Besides, the arrow head with mutation_scale = 150 seems to be as big as the arrow head with mutation_scale = 50 @ 100 DPI.\n\nConcerning the (at least partially) vector formats that I tested (PDF and EPS, with purple labels), one can observe that the arrow heads do not have exactly the same size as in the interactive display either (they are slightly bigger).\n","author":{"url":"https://github.com/afvincent","@type":"Person","name":"afvincent"},"datePublished":"2016-02-20T13:49:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":10},"url":"https://github.com/6035/matplotlib/issues/6035"}