Open
Conversation
Wrong file name in WGS intervals prevents scatters wider than ~210
Collaborator
|
Can one of the admins verify this patch? |
1 similar comment
Collaborator
|
Can one of the admins verify this patch? |
|
Remember to squash merge! |
Member
|
add to whitelist |
|
Remember to squash merge! |
🔍Changelog Validation Results: |
🔍Version Validation Results: |
Contributor
|
@ldgauthier @rickymagner Do you still want this PR merged in? Is this the interval list that should be used in our WARP tests? |
Author
|
Yes please! I believe it's the same territory, but split wider, so tests shouldn't change, but it would like to use this for tests as well. |
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.
Wrong file name in WGS joint genotyping intervals prevents scatters wider than ~210
Checklist
If you can answer "yes" to the following items, please add a checkmark next to the appropriate checklist item(s) and notify our WARP documentation team by tagging either @ekiernan or @kayleemathews in a comment on this PR.
@ekiernan