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
We need to develop tools to visualise GIGs, and the algorithms used to simulate them. As I starting point, I wanted to visualise how the random_matching_positions algorithm worked:
We can see how fragmented the MRCA nodes are, and how the MRCA node's interval matches the nodes U and V. It might be useful for debugging once SVs are added.
Not sure how useful it is in this form, though, since it's difficult to integrate plotting into the simulation code. @hyanwong, maybe it would be helpful to make the mrcas_structure a class? We could add a simplified version of this code as a plot method perhaps, and also add methods to extract useful data conveniently. Probably only worthwhile at a later stage, since the data structure might change.
The text was updated successfully, but these errors were encountered:
Thanks a lot for this @duncanMR: it's really helpful to have someone else looking at all this. I'm sure there are things I've missed or done wrong.
I was indeed wondering about making the mrcas structure a class, which could help elsewhere too. It needs to be pretty lightweight, but that's fine. We could even make it a namedtuple, which is about as lightweight as you can get (and still allows methods to be attached to the class).
We need to develop tools to visualise GIGs, and the algorithms used to simulate them. As I starting point, I wanted to visualise how the
random_matching_positions
algorithm worked:Here is an example, from this simulation:
I extracted the last MRCA structure used in the algorithm and plotted it:
We can see how fragmented the MRCA nodes are, and how the MRCA node's interval matches the nodes U and V. It might be useful for debugging once SVs are added.
Not sure how useful it is in this form, though, since it's difficult to integrate plotting into the simulation code. @hyanwong, maybe it would be helpful to make the mrcas_structure a class? We could add a simplified version of this code as a
plot
method perhaps, and also add methods to extract useful data conveniently. Probably only worthwhile at a later stage, since the data structure might change.The text was updated successfully, but these errors were encountered: