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

Proposal for a B.1 sublineage, circulating in Germany during 2023 [32 seqs] #35

Closed
corneliusroemer opened this issue Jan 16, 2024 · 3 comments · Fixed by #37
Closed

Comments

@corneliusroemer
Copy link
Contributor

Most of (sequenced) global B.1* circulation in 2023 falls into C.1, B.1.20 and the proposed lineage in #34

The second biggest lineage in 2023 that is still B.1 behind #34 is a lineage sequenced 13 time in Germany in late 2023.

In 2022, the lineage was also found once in Belgium, and the ancestor was also found in Australia and the US.

image

https://next.nextstrain.org/mpox/lineage-B.1?branchLabel=aa&gt=nuc.101418T

Defining mutations (broad):

  • C34784T (unique, i.e. has not occurred elsewhere within B.1 yet)
  • C101418T(unique, i.e. has not occurred elsewhere within B.1 yet)
@corneliusroemer
Copy link
Contributor Author

There are now 32 German sequences from this lineage, but they may well be from 2022 rather than 2023 due to a date error, see: sequence-review/mpox#2

@corneliusroemer corneliusroemer changed the title Proposal for a B.1 sublineage, circulating in Germany during 2023 [15 seqs] Proposal for a B.1 sublineage, circulating in Germany during 2023 [32 seqs] Jan 22, 2024
@corneliusroemer
Copy link
Contributor Author

Submitter has confirmed that the dates are correct, so this lineage might be worth designating. Since I opened the issue, around 17 more sequences have been uploaded, all from Germany.

@mengfeip
Copy link

Is there an update about the above proposed B.1 sublineage circulating in Germany 2023?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants