Code Monkey home page Code Monkey logo

Comments (3)

Jhsmit avatar Jhsmit commented on May 16, 2024 1

I made some custom KDE graphs for a publication recently:

image

These type of graphs are called 'raincloudplots': https://wellcomeopenresearch.org/articles/4-63 (which has a python implementation but is based on seaborn and therefore has the same problems)
The code for the KDE part of the graph is here: https://github.com/Jhsmit/PyHDX-paper/blob/master/biorxiv_v2/functions/rainbows.py

Feel free to use the code in proplot if you find it useful (although some parts are from joyplot). I'm using scipy's kde function which mostly works fine but especially for the 2D case it can be slow if you have a lot of datapoints.
I might want to try to find time to make a PR myself, I'm a big fan of proplot. I've started using it for my last publication and the subplot layout and sizing options in proplot really made my life a lot easier :) (paper / code)

I'll try to provide some feedback to proplot if that helps you.
PS. perhaps you could consider connecting your repository to zenodo such that the project can be cited.

from proplot.

bugsuse avatar bugsuse commented on May 16, 2024

It's a very nice feature! I can hardly wait!

from proplot.

lukelbd avatar lukelbd commented on May 16, 2024

Thanks for the code! This is a good base for adding KDE functionality -- I probably won't have time to work on this until later this year but happy to accept PRs if you feel inclined/want it sooner. Proplot's source code recently underwent some major improvements so it should be much easier to contribute.

We probably want to add the following:

  1. Add a shared helper function at the top of axes/plot.py that controls KDE estimation for various plotting functions. Users should be able to pass keyword arguments to the KDE algorithm from the plotting functions.
  2. Add a violinplot option to plot a left- or right-half violin (like in your example), maybe with the argument side='left' and side='right' (or side='top' or side='bottom' for horizontal violins), with side='both' being the default.
  3. Rewrite violinplot to use your method for KDE estimation rather than matplotlib's method. It would probably simply call fill_between or fill_betweenx and then you can add outlines to the violins like you would any other patch. It would still be able to add error bars/boxes using the shared PlotAxes._apply_bar method.
  4. Add a raincloudplot method (with the shorthand raincloud, consistent with other plotting commands) as a thin wrapper that calls boxplot, violinplot, and scatter. It would call boxplot and violinplot with reduced default widths arguments and default side='left' or side='top' for the violins.
  5. Make violinplot have no colormap gradations by default, but let users add them by passing cmap='name' to violinplot or raincloudplot (it should also accept vmin and vmax arguments, but set the default vmin and vmax to the minimum and maximum of all the distributions). To implement colormap gradations, violinplot will set the facecolor of the patch to 'none' (i.e., completely transparent) so that an imshow can be drawn underneath the patch border and "clipped" by the border coordinates, as you've done in your code.
  6. Add kdeplot and kdeplot2d commands (with shorthands kde and kde2d, consistent with other functions) that show KDE estimations using lines and contours (respectively). They should be thin wrappers around plot and contour/contourf, similar to how hist and hist2d are thin wrappers around bar and pcolor.
  7. Add the ability to pass kde=True to hist and hist2d and this will draw the kde and kde2d lines on top of the histograms, analogous to the current ability of passing linewidth=N to contourf and proplot adds an additional contour plot on top of the filled contours. KDE-algorithm or KDE-styling keywords could be passed to hist and hist2d with kde_kw={key: value, ...}, analogous to various other arguments ending in _kw.
  8. Update the user guide with lots of examples! By the time all of these features are added we'd probably need a separate "Statistical plotting" section separate from the current "1d plotting" and "2d plotting" sections.

And glad you find proplot useful :) it's already published on Zenodo but that probably wasn't clear -- there was just a Zenodo badge to the github home page. I've now added a link to the readthedocs homepage.

from proplot.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.