Use tabix when splitting imputation server vcfs #60
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
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 discussed in emails with Stephan. Using the new --deploy option for pre- and postprocessing imputation server files, I found the conversion from chromosomal vcfs to dosage chunks too slow in some cases.
I updated the scripts to use tabix for deployed imputation files with indices, which improved performance substantially (now my problematic chunks finish before the cluster kills them).
The logic I wrote stops with an error if using --deploy and there are no index files (I think both Sanger and Michigan provide them?), but for other uses of vcf2dos (i.e. in-house imputation), the script should proceed by reading the full file if there is no index.