ReblockGVCFs now takes GVCFs that are not in the same location as their index #1081
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
|
Remember to squash merge! |
|
@jessicaway This is the change to ReblockGVCFs that will let GP run it themselves on data from TDR. Tests should pass (this change shouldn't change any outputs) so I think this is ready for review. |
ldgauthier
approved these changes
Sep 18, 2023
|
Joint genotyping test is failing for missing input. Our team is working on this. It can safely be ignored for now |
nikellepetrillo
approved these changes
Sep 19, 2023
3 tasks
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.
This change allows you to run ReblockGVCFs with input GVCFs in different locations than the index files (for example, if the data is in TDR).