Skip to content

Commit

Permalink
🚧 adjust section names and move "Focus on selected" lower
Browse files Browse the repository at this point in the history
  • Loading branch information
victorlin committed Dec 13, 2024
1 parent e412d55 commit 5939717
Showing 1 changed file with 27 additions and 27 deletions.
54 changes: 27 additions & 27 deletions static-site/content/blog/2024-12-10-auspice-2024.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,34 +17,14 @@ git tag --list --format='%(creatordate:short)' | grep '^2024' | wc -l

## Table of contents

- [Focus on Selected](#focus-on-selected)
- [View in Other Platforms](#view-in-other-platforms)
- [View in other platforms](#view-in-other-platforms)
- [Performance improvements](#performance-improvements)
- [Conveying confidence of tips through saturation](#conveying-confidence-of-tips-through-saturation)
- [Filtering on all metadata](#filtering-on-all-metadata)
- [Convey tip confidence through saturation](#convey-tip-confidence-through-saturation)
- [Focus on selected](#focus-on-selected)
- [Filter on all metadata](#filter-on-all-metadata)
- [Full changelog](#full-changelog)

## Focus on Selected

When viewing large phylogenetic trees with a sparse filter, it can be difficult
to really see and understand the selected tips as they occupy a minority of the
vertical space available. Enabling **Focus on Selected** allows the selected
tips to take up more vertical space compared to other tips. For example,
[filtering the SARS-CoV-2 global 6m view to one of the earliest clades, 20I
(Alpha)](https://nextstrain.org/ncov/gisaid/global/6m@2024-12-10?d=tree&f_clade_membership=20I%20%28Alpha%29&p=full):

[![Focus on Selected example](/blog/img/focus-on-selected-example.png)]()

You can toggle this focus on/off in the sidebar:

[![Focus on Selected toggle](/blog/img/focus-on-selected-toggle.png)]()

We [plan](https://github.com/nextstrain/auspice/issues/1368) to continue
exploring better ways to understand sets of sequences in the context of the
larger tree, initially by better use of the horizontal axis which should help
for early clades in the tree such as 20I (Alpha).

## View in Other Platforms
## View in other platforms

Historically, we have always been strong advocates for interoperability between
platforms. For many years, Nextstrain.org has supported
Expand Down Expand Up @@ -93,7 +73,7 @@ trees with over 4,000 tips](https://github.com/nextstrain/auspice/pull/1880).
These changes should result in a more responsive feel, especially on large
datasets.

## Conveying confidence of tips through saturation
## Convey tip confidence through saturation

We've long used desaturation to convey (lack of) confidence in inferred metadata
for branches, and we now do the same for tips. Tips with high confidence will
Expand All @@ -104,7 +84,27 @@ dataset where many tips lack geographic metadata:

[![Confidence through saturation](/blog/img/confidence-through-saturation.png)]()

## Filtering on all metadata
## Focus on selected

When viewing large phylogenetic trees with a sparse filter, it can be difficult
to really see and understand the selected tips as they occupy a minority of the
vertical space available. Enabling **Focus on Selected** allows the selected
tips to take up more vertical space compared to other tips. For example,
[filtering the SARS-CoV-2 global 6m view to one of the earliest clades, 20I
(Alpha)](https://nextstrain.org/ncov/gisaid/global/6m@2024-12-10?d=tree&f_clade_membership=20I%20%28Alpha%29&p=full):

[![Focus on Selected example](/blog/img/focus-on-selected-example.png)]()

You can toggle this focus on/off in the sidebar:

[![Focus on Selected toggle](/blog/img/focus-on-selected-toggle.png)]()

We [plan](https://github.com/nextstrain/auspice/issues/1368) to continue
exploring better ways to understand sets of sequences in the context of the
larger tree, initially by better use of the horizontal axis which should help
for early clades in the tree such as 20I (Alpha).

## Filter on all metadata

All categorical metadata available for the tree – i.e. all data within
`node.node_attrs` – are now available as options for **Filter Data**. Combined
Expand Down

0 comments on commit 5939717

Please sign in to comment.