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

Document color schemes #901

Open
huddlej opened this issue Mar 29, 2022 · 1 comment
Open

Document color schemes #901

huddlej opened this issue Mar 29, 2022 · 1 comment
Labels
enhancement New feature or request source: office hours Issue mentioned during office hours

Comments

@huddlej
Copy link
Contributor

huddlej commented Mar 29, 2022

Context

At the beginning of the pandemic, Trevor created a collection of color schemes that could scale to hundreds of categorical values. These color schemes were originally used to generate colors for geographic regions, but they have become handy for more general use throughout ncov analyses (and elsewhere).

Description

We should document where the color schemes file resides and how to use it for primary use cases (like assigning colors to a for custom metadata column associated with a manuscript, etc.).

Possible solution

For example, we could at least link out to the color schemes file, list the hex values up to 10 colors, and then show Python code for how to use these colors in a matplotlib figure or the like.

@huddlej huddlej added the enhancement New feature or request label Mar 29, 2022
@victorlin victorlin added the source: office hours Issue mentioned during office hours label Mar 30, 2022
@jameshadfield
Copy link
Member

One limitation of the current ncov workflow (and nextstrain more generally) is that all custom colours have to be specified in one file to be passed to augur export. For example, if you want to use our provided (ordered) colours for country, pango lineage etc, but add in some custom colours then there's no easy way to do this (if you're happy with our colours and simply want to change the ordering or add new values, you can modify ./defaults/color_ordering.tsv but this isn't very nice). This relates to the "data curation" framework we've been talking about, where I'd want to make it easy to define colours independently for different metadata (but without having to keep track of lots of TSVs!).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request source: office hours Issue mentioned during office hours
Projects
No open projects
Status: Backlog
Development

No branches or pull requests

3 participants