# Mpox lineage in metadata is different from what shows in the tree

**URL:** <https://nextstrain.discourse.group/t/mpox-lineage-in-metadata-is-different-from-what-shows-in-the-tree/1714>\
**Category:** General\
**Created:** [August 19, 2024, 3:11am UTC](https://nextstrain.discourse.group/t/mpox-lineage-in-metadata-is-different-from-what-shows-in-the-tree/1714 "2024-08-19T03:11:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dlu](https://avatars.discourse-cdn.com/v4/letter/d/e36b37/32.png) [@dlu](https://nextstrain.discourse.group/u/dlu)\
**Post date:** [August 19, 2024, 3:11am UTC](https://nextstrain.discourse.group/t/mpox-lineage-in-metadata-is-different-from-what-shows-in-the-tree/1714/1 "2024-08-19T03:11:17Z")

</div>

We’re using [a fork from the mpox repo](https://github.com/nextstrain/mpox/tree/644d07ebe3fa5ded64d27d0964064fb722797c5d) 2 years ago and I just wanted to check in case there is an obvious answer for this.

We have some samples that have lineage `B.1.20` in the metadata (downloaded from [data.nextstrain.org/files/workflows/mpox/metadata.tsv.gz](http://data.nextstrain.org/files/workflows/mpox/metadata.tsv.gz))

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/nextstrain/original/1X/ceddd2aa76b4bc8f925c1e4d03105db81a6170ac.png)

But are showing up as `B.1` on the tree

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/nextstrain/original/1X/a877dd618f9ded2cbcb56d0bf6d327dbd5ae744a.jpeg)

I dug around and vaguely remember something about the `color_ordering.tsv` needs to have all lineages we want to show on the tree. Is that right?

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/nextstrain/original/1X/0128042e69a3f4a96d29f1f9f83152f381022770.png)

In any case, what is the best approach to make sure all lineages show up in the tree? Any pointers would be appreciated!

---

<div class="post-metadata">

**Author:** ![rneher](https://yyz1.discourse-cdn.com/flex031/user_avatar/nextstrain.discourse.group/rneher/32/20_2.png) [@rneher](https://nextstrain.discourse.group/u/rneher)\
**Post date:** [August 20, 2024, 10:17am UTC](https://nextstrain.discourse.group/t/mpox-lineage-in-metadata-is-different-from-what-shows-in-the-tree/1714/2 "2024-08-20T10:17:12Z")

</div>

The lineages on the tree are assigned using the `clades.tsv` file in your fork from 2 years ago:

> <https://github.com/nextstrain/mpox/blob/644d07ebe3fa5ded64d27d0964064fb722797c5d/config/clades.tsv>

The clades in the metadata use a recent nextclade dataset which includes additional lineages that were defined in the mean time.

you have two options:

- update the clades.tsv to a more version
- color the tree by metadata without using the phylogenetic clade determination step in the workflow.

does that make sense?

---

<div class="post-metadata">

**Author:** ![dlu](https://avatars.discourse-cdn.com/v4/letter/d/e36b37/32.png) [@dlu](https://nextstrain.discourse.group/u/dlu)\
**Post date:** [August 20, 2024, 4:58pm UTC](https://nextstrain.discourse.group/t/mpox-lineage-in-metadata-is-different-from-what-shows-in-the-tree/1714/3 "2024-08-20T16:58:12Z")

</div>

All makes sense. I’ll look into it. Thanks very much!