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
I think you have a dengue like situation where a single phylogenetic analysis across all WNV lineages (or dengue serotypes) may be challenging to have very accurate molecular clock.
Rather than cuts between a global analysis and a north-america analysis, you might be better served by cutting by lineage instead. This would give URLs of wnv/all-lineages, wnv/lineage-1, wnv/lineage-2, etc... I wouldn't worry about trying to preserve that historical WNV/NA endpoint.
NCBI doesn't seem to have lineage well annotated, however if you source data from https://pathoplexus.org/west-nile/ you should get lineage for every sequence.
The text was updated successfully, but these errors were encountered:
We have a number of pathogens where the primary split is in terms of geography. For example: ncov/gisaid/global/ vs ncov/gisaid/north-america/. However, for WNV it looks like there are really very distinct lineages (that often have geographic correspondence). Here's a quick phylogeny from https://www.mdpi.com/1999-4915/15/1/35:
I think you have a dengue like situation where a single phylogenetic analysis across all WNV lineages (or dengue serotypes) may be challenging to have very accurate molecular clock.
Rather than cuts between a
global
analysis and anorth-america
analysis, you might be better served by cutting by lineage instead. This would give URLs ofwnv/all-lineages
,wnv/lineage-1
,wnv/lineage-2
, etc... I wouldn't worry about trying to preserve that historicalWNV/NA
endpoint.NCBI doesn't seem to have lineage well annotated, however if you source data from https://pathoplexus.org/west-nile/ you should get lineage for every sequence.
The text was updated successfully, but these errors were encountered: