Fix callVariant to treat all peptides on accept subgraph as variant peptides #377
Conversation
This file contains 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
…variant being the global variant, so all peptides of the accepter subgraph will be t reated as potential variant peptides
lydiayliu
reviewed
Jan 31, 2022
lydiayliu
approved these changes
Jan 31, 2022
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.
As described in #376 that non in-frame fusion will cause the entire accept transcript being novel. And even if both donor and accepter breakpoints are in-frame, upstream frameshifting indel will also changes this. So I decided to do it in this way to treat the entire fusion subgraph as potential variant peptides. If the fusion is in-frame and there isn't any frameshifting mutation upstream, those non novel peptides from the accepter transcript will be removed when comparing to the canonical peptide pool.
Closes #376