You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ancestral] optional validation of aa vs nuc reconstructions
There's been a tension between the two ways we handle translations in
augur: the "old" way of inferring ancestral seqs then translating them
vs the "new" way of using nextclade to get translated tip-sequences and
reconstructing nucleotide & aa seqs independently across the tree.
The new way is arguable better, as nextclade has some alignment
heuristics around CDSs to produce better translations, but opens the
door to having mismatches between the inferred nuc seq and the
corresponding AA residue. These differences would be surfaced in Auspice
when looking at branch mutations.This commit adds an optional warning to
check for such mismatches.
A trial n=5.5k H3N2 HA dataset had the following differences:
- SigPep: 2 terminal nodes. Median residue mismatch count: 13 (range: 1 - 13)
- HA1: 2 terminal nodes and 4 internal nodes. Median residue mismatch
count: 3 (range: 1 - 5)
- HA2: 1 terminal node and 1 internal node were different. Median
residue mismatch count: 2 (range: 1 - 2)
0 commit comments