Skip to content
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

Add chromothripsis #32

Open
wants to merge 15 commits into
base: master
Choose a base branch
from
Open

Add chromothripsis #32

wants to merge 15 commits into from

Conversation

evanbiederstedt
Copy link
Collaborator

@evanbiederstedt evanbiederstedt commented Oct 18, 2017

Well, it looks like this passes. I'm still skeptical, but...

If so, then this branch should create chromothripsis. One reserves entire chromosomes to be rearranged with SVs (except no insertions).

One then creates no more SVs in these chromosomes---users will know there could be issues with the coordinate system.

In this case, I would be interested in creating an log file only for "chromothriptic rearrangements" for each chromosome, possibly using our existing infrastructure and import logging. Talk to Nick about this. I suspect it's straightforward to do---log the events in the order they take place, and allow users to "work backwards" if they are so inclined.

reference: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3065307/
Based on Stephens et al 2011, it looks like chromothripsis happening on 20-200Kb. I believe this is the current length scale, but users could crank this up/down via the probability parameter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant