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
It's not clear to me how SNPgenie polarizes the mutations (to compute dN/dS and piN/piS).
Does it assume the ancestral states are the ones supplied in the reference fasta? If so, how would SNPgenie deal with having ancestral states in the reference fasta that do not mach the REF column in the VCF?
Thank you!
The text was updated successfully, but these errors were encountered:
Greetings, Murillo! Thanks a lot for the question. Actually, being designed originally for πN/πS, SNPGenie is entirely phylogeny-agnostic. This mean it is not calculating dN/dS (or πN/πS) along branches or lineages, but rather simply the mean value between all choose(n,2) pairs of extant (provided) sequences. This may have less power than methods that trace changes over a phylogeny. On the other hand, the approach is robust to errors in phylogenetic and ancestral sequence reconstruction, and to artifacts due to linkage or recombination. Note that this distinction is probably only necessary for dN/dS, because πN/πS usually employs this non-phylogenetic by definition (i.e., it's a population measure).
Hi,
It's not clear to me how SNPgenie polarizes the mutations (to compute dN/dS and piN/piS).
Does it assume the ancestral states are the ones supplied in the reference fasta? If so, how would SNPgenie deal with having ancestral states in the reference fasta that do not mach the REF column in the VCF?
Thank you!
The text was updated successfully, but these errors were encountered: