fix: Fix wrong start for intersecting CNV events#70
Open
hwalinga wants to merge 1 commit intovplagnol:masterfrom
Open
fix: Fix wrong start for intersecting CNV events#70hwalinga wants to merge 1 commit intovplagnol:masterfrom
hwalinga wants to merge 1 commit intovplagnol:masterfrom
Conversation
Fixes vplagnol#19 (duplicate vplagnol#65) See also for deeper investigation: Multiplicom#4 (comment) Basically, when the Viterbi path switches from deletion to duplication or vice versa, the start variable is not updated. Thus eg the Viterbi path is 00000011111122220000, then the switch from 0 -> 1 is recording the start, and 1 -> 2 is saving that data, however not setting the start variable again when saving at 2 -> 0, thus "2" has the same start variable as "1".
Author
|
Hi Vincent @vplagnol Thanks a lot for the ExomeDepth package! And for still occasionally putting out a new release for this! I looked into a long-standing bug that we occasionally encountered and was able to fix it at the root of where the bug comes from. Adding a reproducible example here as well to show exactly when this happened. I hope a new release can have this fix, maybe now even release back on CRAN with 096bb38, but we are also very happy to get it from conda. Regards, |
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #19 (duplicate #65)
See also for deeper investigation: Multiplicom#4 (comment)
Basically, when the Viterbi path switches from deletion to duplication or vice versa, the start variable is not updated. Thus eg the Viterbi path is 00000011111122220000, then the switch from 0 -> 1 is recording the start, and 1 -> 2 is saving that data, however not setting the start variable again when saving at 2 -> 0, thus "2" has the same start variable as "1".
Now for a test, you can use this script, modified from the vignette:
NB. I noticed the vignette was not 100% working anymore out of the box because of a check that #68 introduced.
The current implementation will now output (second CNV has
start22 from preceding duplication):Now install my modified ExomeDepth from this branch:
My fix now correctly outputs (second CNV has now correct start of
25):