-
Notifications
You must be signed in to change notification settings - Fork 597
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
[BIOIN-1570] Fixed edge case in variant annotation #8810
Merged
ilyasoifer
merged 4 commits into
broadinstitute:master
from
Ultimagen:ilyasoifer/BIOIN-1570-fix-bug-flow-annotations
Jun 3, 2024
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -69,7 +69,28 @@ public Object[][] getTestData() { | |
// ins hmer indel | ||
"TATCT C ATTGACCAA", "CA", | ||
"ins", "1", "2", "A", "ATCTC", "TTGAC", "0.3", "NA", "h-indel" | ||
}, | ||
//The following tests test the edge case of variant so close to the edge of the chromosome | ||
//that some of the annotations can't be calculated | ||
{ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you add to these comments a little more context for the nature of this error and what those are testing? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Added comments |
||
// Close to 5' edge of the chromosome, expect not to crash on finding the left motif | ||
"ATCT C ATTGACCAA", "CA", | ||
"ins", "1", "2", "A", null, "TTGAC", "0.3", "NA", "h-indel" | ||
}, | ||
{ | ||
// close to 3' edge of the chromosome, should not find left motif or GC content | ||
"TATCT C ATT", "CA", | ||
"ins", "1", "2", "A", "ATCTC", null, null, "NA", "h-indel" | ||
}, | ||
{ | ||
// very close to 3' edge of the chromosome, should not find left motif, GC content or if it is | ||
// an hmer indel | ||
"TATCT C ", "CA", | ||
"ins", "1", null, null, "ATCTC", null, null, "NA", "non-h-indel" | ||
} | ||
|
||
|
||
|
||
}; | ||
|
||
return testData; | ||
|
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm looking inside of establishReadGroupFlowOrder() and it looks like it tries to disable annotation if it can't establish what the flow order is for the local context (which is explicitly the case for the user that brought up this issue)... Can you disentangle what is supposed to happen for this annotation class in the event that no-flow order can be established? The annotation requires a flow order in order to determine what kind of indel it is no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is a method called isActualFlowOrderRequired in this abstract class that returns false, the annotations that the user enabled all inherit from that abstract class and do not require flow order. The only annotation that does require it is
CycleSkipStatus
.