Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rename arviz-doc to arviz-docgrid and make arviz-doc a non-grid style #2157

Merged
merged 2 commits into from
Nov 11, 2022

Conversation

aloctavodia
Copy link
Contributor

@aloctavodia aloctavodia commented Nov 8, 2022


📚 Documentation preview 📚: https://arviz--2157.org.readthedocs.build/en/2157/

@aloctavodia aloctavodia marked this pull request as ready for review November 8, 2022 21:33
@codecov
Copy link

codecov bot commented Nov 8, 2022

Codecov Report

Merging #2157 (d809627) into main (2d88638) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2157   +/-   ##
=======================================
  Coverage   90.70%   90.70%           
=======================================
  Files         120      120           
  Lines       12647    12647           
=======================================
  Hits        11471    11471           
  Misses       1176     1176           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@OriolAbril
Copy link
Member

cc @sarinac

Copy link
Contributor

@sarinac sarinac left a comment

Choose a reason for hiding this comment

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

Thanks @aloctavodia for adding!

A few questions:

  1. I made comments on keeping the doc/docgrid styles exactly the same except for axes.grid=True. LMK if any concerns.
  2. Can you add the new arviz-docgrid to doc/examples/matplotlib/mpl_styles.py? That way users can discover it.
  3. This will remove grids for all charts generated throughout the entire documentation (homepage, example gallery, api documentation examples). Should we vary a few, change everything to arviz-docgrid, or leave things the way they are with the new arviz-doc (nothing will have grids)? My opinion is that there are some charts (e.g. violin) that look better with axes, but stuff like posterior plot (too cluttered in the examples right now) look better without.

Comment on lines 34 to 35
# axes.grid.axis: y # which axis the grid should apply to
axes.grid.which: major # grid lines at {major, minor, both} ticks
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we keep this? Without explicitly setting axes.grid.which to "major", the axis will show both major and minor. I like things more simple and less clutterry, which is what I was hoping this style goes for.

I think the only differentiator between arviz-doc and arviz-docgrid is the presence of the grid. Even with arviz-doc style applied, you can override the grid visibility by applying plt.grid(). If the user happens to do that, then I want it to match arviz-docgrid's style to a tee.

Comment on lines 38 to 42
grid.color: .8 # grid color
grid.linestyle: - # solid
grid.linewidth: 0.8 # in points
grid.alpha: 1.0 # transparency, between 0.0 and 1.0

Copy link
Contributor

Choose a reason for hiding this comment

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

Can we keep these too for the same reason above?

@aloctavodia
Copy link
Contributor Author

thanks for the comments @sarinac. I updated the styles

Copy link
Contributor

@sarinac sarinac left a comment

Choose a reason for hiding this comment

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

🎉 🎉 🎉

@aloctavodia aloctavodia merged commit 7e0691b into main Nov 11, 2022
@aloctavodia aloctavodia deleted the docgrid branch November 11, 2022 10:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants