HoloViews Cheat Sheet

[philippjfr]

The idea of a HoloViews cheat sheet has cropped up on a number of occasions but we haven't raised it as an official issues. I think it's a great idea, which could be leveraged in two forms 1) the actual condensed cheat sheet 2) a more plotting centric user guide. To start with I'd like brainstorm sections and specific items such a cheat sheet might include, that might look something like this:

Operating on the data

• sorting
• selecting
• aggregate

Plotting

• Labeling axes (Dimension labels)
• Setting axis ranges (.redim.range, and soon range padding)
• Mapping visual attributes (Cycle, cmap, *_index, and soon ops)
• ...

[ea42gh]

Re Plotting, for now in no particular order (mostly copied from headers in github.com/ea42gh/HoloviewsPlayground/CurvesAndPaths.ipynb)

• datasources (e.g., dataframe, numpy array, xarray, sqlite, dask...)
  • Data arguments for Element constructors
• Figure Size And Layout
  • ways to organize figures: cols(), grid..., HoloMaps/DynamicMaps, Tabs
• Combining elements into figures
• Colors and Color Cycles, muted_alpha
• Labels, Legends and Titles (including adding an HTML div)
• Axes
  • Ticks (number of ticks, lists, Tick label formating)
  • controling axes
    • hv.Dimensions to control axis labels, to control axis independence
    • for multiple plots axiswise
    • for multiple displays framewise
  • Twin Axes
• ColorMapping Elements
  • images with contours and colorbar
• operations (e.g., datashader)
• Hover, custom hover, hover+datashader
• Dynamic Plots
  • holomaps, dynamicmaps
  • scrubber
  • widgets
  • streams
  • buffers, pipes, ...
• Extending plot types
  • functions that return plots that work for both bokeh and matplotlib (use group labels to allow caller to modify options)
  • operations
  • adding a new Element class

I'll come back and add as I get time... Any ideas on how to organize this so it's useful? Is there an easy way to share some notebooks?

[ea42gh]

How to package a plotting function

I currently ended up with something like #2527 which leads to the following

• add groups to components that might be styled differently by the caller
• document the layout.traverse to get hold of a plot component when an unknown label ends up in the path to a plotting element
• reset title_format to suppress the group showing up in the plot titles
• set options for each of the desired backends

[ea42gh]

• A howto addressing plotting speed issues
  • Curve/Path
  • datashader etc

[vv111y]

This issue came up as the first search result. So ... any cheetsheats?

[jbednar]

Not that I've seen, but I'd sure be happy to see one! I'd rather see one first for hvPlot, then for HoloViews...

[ahuang11]

Here's a draft:

The source is from here (albeit messy and full of copy/paste): https://github.com/ahuang11/holoviews-cheat-sheet

I think there could be more advanced ones. This one is pretty beginner level.

[jlstevens]

@ahuang11 This is great!

This should be linked to from our docs, or maybe allow a direct download/view of it (with attribution of course!). @droumis Any thoughts of where something like this would fit in our planned documentation structure?

[droumis]

this is an great, @ahuang11!

I think it could go in (or be linked to from) the Getting Started section, as IMO its main purpose is to get people started working asap. Its secondary purpose is as a superficial Reference. An awesome next step might be to add links to associated docs pages as a sort of drill down.

[ahuang11]

I just realized this didn't go anywhere, but should this be linked somewhere?

[ahuang11]

Decided to share my cheat sheet here https://www.reddit.com/r/Python/comments/18mzyof/holoviews_cheat_sheet_for_bokeh_backend/

Will try to get a PR to link it in HoloViews getting started page soon.