feature: VCF File Input Support #9
Draft
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
…n memory, and will use significant amounts of memory, about the size of the uncompressed ped.
…lly using it just for testing and debugging.
…be big in memory.
…t a time, making memory usage manageable.
|
Do these new changes reduce the amount of memory required for loading VCFs? Is there anything I can do to help? |
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.
Add basic VCF input support. This solution transposes the whole VCF in memory, and will use significant amounts of memory, about the size of the uncompressed ped.
WIP right now. This is not polished or ready to merge. I need to test more, and make sure that this is a sane design.