-
-
Notifications
You must be signed in to change notification settings - Fork 6
Bottom Spine and Log Tick Locations #25
Comments
Interesting. For trying things out, you can adapt your style with, e.g., ax.spines['right'].set_visible(True)
ax.spines['top'].set_visible(True) I would like to see a comparison of the current state and what your suggest in the README example and your example. That'll give us a better idea of what's reasonable. |
Well the problem is that the README example looks fine (I'd add the bottom spine in the left plot but it looks nice enough as we have multiple gridlines that give the chart a structure; in the right plot the lowest grid lines even coincides with the axis so that it looks perfect to me). What is difficult and where I don't have an idea yet is the ticking issue for log scales (that's why I opened an issue and not a PR 😊) To play around you can for instance use this gist and set |
Well, I believe you that it doesn't look good. The question is how to adapt the default style. I wouldn't want to add more lines to the plots that already look good. Perhaps the solution is to manually add yticks? |
Alternatively, you can set before ax.spines['left'].set_visible(True)
ax.spines['bottom'].set_visible(True) There are methods for all the other mods as well. |
First of all - congrats on your great module
perfplot
that uses this style. Although I myself am a great fan of removing chartjunk I guess that less in sometimes more even in trying to do less that is indeed more in many cases.What I mean is that removing the bottom spine (and left spine if no gridlines are used) and using only sparse tick labels doesn't increase readability, on contrary it can make things much worse:
I admit this is a specifically constructed minimal example but the reason behind it is that I ended up with such a perfplot where we have just one grid line in the middle of the chart (kind of visually dividing the chart into two halves) and a single x tick label floating in the middle of free space.
.
So my proposal is
The text was updated successfully, but these errors were encountered: