-
Notifications
You must be signed in to change notification settings - Fork 30
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
Graph of recombination events algorithm #142
Comments
Hi Valery, the y-axis is the number of recombination events observed which cover that particular position in the genome. Note that an event may involve many strains but only be counted once (the red blocks indicate events which are inferred on ancestral nodes and therefore involve more than one tip). |
sorry, one more clarifying question. by the number of recombination events Do you mean exactly the number of strains that were detected in the regions of recombination on that position? But it couldn't be so, because I have near 300 isolates and there were positions where all isolates were involved but the max value on the graph is near 100. Maybe is there some window within it's counting? or relative value?
|
No, the number of recombination events. If a recombination event is inferred to happen at an ancestral node then one event will involve multiple strains. The Gubbins paper details how these are inferred, phandango just visualises them.
No. It is the number of recombination events. |
Ok, thank you, I'll try, it's special terminology from gubbins. So if we return to the output gff file and the output of Phandango graph. Does it count exactly number of rows where the value from the last column "node=" is the ancestral node? |
Hello,
I have the data from gubbins gff file with coordinated (Start and Stop, and snp_count), I've downloaded this data and had the graph with peaks at the bottom. Could you please explain what is y-value? and how this value was calculated? I've tried to do the same distribution and had different result)
Best regards,
Valery
The text was updated successfully, but these errors were encountered: