Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Altair Tutorial

Eitan Lees
November 10, 2018

Altair Tutorial

Here are the slides presented at an Altair tutorial and workshop I gave in the Department of Scientific Computing at FSU.

Eitan Lees

November 10, 2018
Tweet

More Decks by Eitan Lees

Other Decks in Technology

Transcript

  1. Acknowledgments - Altair is developed by Jake Vanderplas and Brian

    Granger in close collaboration with the UW Interactive Data Lab - Much of this tutorial is from Jake Vanderplas’ PyCon 2018 tutorial - Special thanks to the Altair Community on GitHub.
  2. Building Blocks of Visualization 1. Data 2. Transformations 3. Marks

    4. Encoding - mapping from fields to mark properties 5. Scale - functions that map data to visual scales 6. Guides - visualizations of scales (axes, legends, etc.)
  3. Strengths: - Designed like MatLab: switching was easy - Many

    rendering backends - Can reproduce just about any plot (with a bit of effort) - Well-tested, standard tool for over a decade Weaknesses: - API is imperative & often overly verbose - Poor support for web/interactive graphics - Often slow for large & complicated data
  4. Tidy data: i.e. rows are samples, columns are features “

    I want to scatter petal length vs. sepal length, and color by species” Example: Statistical Data
  5. Toward a well-motivated Declarative Visualization Imperative - Specify How something

    should be done. - Specification & Execution intertwined. - “Put a red circle here and a blue circle here” Declarative - Specify What should be done. - Separates Specification from Execution - “Map <x> to a position, and <y> to a color” Declarative visualizations lets you think about the data and relationships, rather than incidental details
  6. Toward a well-motivated Declarative Visualization Imperative - Specify How something

    should be done. - Specification & Execution intertwined. - “Put a red circle here and a blue circle here” Declarative - Specify What should be done. - Separates Specification from Execution - “Map <x> to a position, and <y> to a color” Declarative visualizations lets you think about the data and relationships, rather than incidental details
  7. ...

  8. Key: Visualization concepts should map directly to visualization implementation Check

    out Jeff Heer’s class on data visualization https://courses.cs.washington.edu/courses/cse442/17au/