Metadata-Version: 2.1
Name: ways-py
Version: 0.1.1
Summary: WAYS package for Python developed at University of Warwick and The Alan Turing Institute.
Home-page: https://github.com/WarwickCIM/ways-py
License: MIT
Author: Ed Chalstrey
Author-email: echalstrey@turing.ac.uk
Requires-Python: ==3.9.9
Classifier: License :: OSI Approved :: GNU General Public License v3 (GPLv3)
Classifier: License :: OSI Approved :: MIT License
Classifier: Natural Language :: English
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.9
Requires-Dist: Shapely (>=1.8.0,<2.0.0)
Requires-Dist: altair (>=4.1.0,<5.0.0)
Requires-Dist: altair-saver (>=0.5.0,<0.6.0)
Requires-Dist: certifi (>=2021.10.8,<2022.0.0)
Requires-Dist: importlib-metadata (>=4.8.1,<5.0.0)
Requires-Dist: ipykernel (>=6.4.1,<7.0.0)
Requires-Dist: ipython (>=7.29.0,<8.0.0)
Requires-Dist: ipywidgets (>=7.6.5,<8.0.0)
Requires-Dist: jsonschema (==3.2.0)
Requires-Dist: jupyter (>=1.0.0,<2.0.0)
Requires-Dist: nbmake (>=0.8,<0.9)
Requires-Dist: pdocs (>=1.1.1,<2.0.0)
Requires-Dist: pytest (>=6.2.5,<7.0.0)
Requires-Dist: selenium (>=4.0.0,<5.0.0)
Requires-Dist: vega-datasets (>=0.9.0,<0.10.0)
Project-URL: Documentation, https://warwickcim.github.io/ways-py/
Description-Content-Type: text/markdown

<!-- badges: start -->
[![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/WarwickCIM/ways-py/develop)
[![Project Status: Concept – Minimal or no implementation has been done yet, or the repository is only intended to be a limited example, demo, or proof-of-concept.](https://www.repostatus.org/badges/latest/concept.svg)](https://www.repostatus.org/#concept)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
<!-- badges: end -->

# _WAYS: What Aren't You Seeing_

Python package for the [WAYS](https://www.turing.ac.uk/research/research-projects/ways-what-arent-you-seeing) project. See [API documentation](https://warwickcim.github.io/ways-py/).
<!-- badges: start -->
[![Publish](https://github.com/WarwickCIM/ways-py/actions/workflows/publish.yml/badge.svg?branch=release)](https://github.com/WarwickCIM/ways-py/actions/workflows/publish.yml)
[![Build](https://github.com/WarwickCIM/ways-py/actions/workflows/build.yml/badge.svg?branch=develop)](https://github.com/WarwickCIM/ways-py/actions/workflows/build.yml)
[![Docs](https://github.com/WarwickCIM/ways-py/actions/workflows/docs.yml/badge.svg?branch=develop)](https://github.com/WarwickCIM/ways-py/actions/workflows/docs.yml)
<!-- badges: end -->

“As you can see in figure 1…” may well be the most frequently made claim in science. But unlike claims concerning data, statistics, models and algorithms, those relating to visualisations are rarely evaluated or verified. So how can data scientists understand visualisations’ effectiveness and expressiveness? What is the visualisation equivalent of q-q plots, R^2 and K-folds tests?

Designing effective visualisations goes far beyond selecting a graph, scales and a ‘pretty’ style. Effective visualisations must negotiate sensitivities and interactions between visual elements (e.g. encodings, coordinate systems, guides, annotations), data (e.g. characteristics, transformations, partitions), and the discriminator function, which in this case is the perceptual and cognitive systems of humans. Despite their criticality, these methodological and design considerations are rarely surfaced, limiting the value extracted from visualisations. What does figure 1 actually visualise?

The ‘What Aren’t You Seeing’ (WAYS) project addresses 1) what we aren’t seeing in visualisations by 2) revealing the relevant knowledge, theory and practices that we are not seeing at the site of visualisation production. Our final goal is the WAYS package/library in which the properties, outcomes and affordances of visualisation designs are depicted through visualisations; a concept we term ‘Precursor Visualisations’. WAYS then addresses the challenge of generating a productive interplay between everyday visualisation work and the epistemology, practice, communication techniques and evaluation methods that should inform visualisation design at source (Robinson). To achieve this, we propose three work packages (WP1-3).

# Quick start

Install from [PyPI](https://pypi.org/project/ways-py/) using `pip install ways-py`.

## Development

To create the development environment, do the following:

1. Install python poetry by following the [install instructions](https://python-poetry.org/docs/)
2. From the top level dir: `poetry shell`
 - Note: your machine will need python 3.9 available - [install from here](https://www.python.org/downloads/release/python-397/) if you don't have it

# Emojis on commit messages

We use a number of `git` [aliases](/.gitconfig.aliases) to track different kinds of commit; to use these yourself, add an `[include]` section to your [`.gitconfig`](https://git-scm.com/docs/git-config).

