use individual tables when writing out vcf files
See original GitHub issueCurrently write_vcf
has a ploidy
argument, and will assume that adjacent samples belong to the same individual. This should be deprecated after we provide a make_individuals
method, and write_vcf
should have an argument that toggles whether to write individuals or genomes (maybe: output
either monoploid
by default or phased
or `unphased).
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Chapter 22 Basic Handling of VCF files
Even though it is named query its main purpose is simply extracting fields of information from a VCF file and spitting them out...
Read more >Working with VCF Files - NCBI - NIH
VCF files can be opened from local and remote locations and viewed in a few different views including Graphical Sequence view, VCF table...
Read more >VariantsToTable – GATK - Broad Institute
This tool extracts specified fields for each variant in a VCF file to a tab-delimited table, which may be easier to work with...
Read more >VCF Processing Guide - ANNOVAR Documentation
This article describes some thoughts about VCF pre-processing to ensure a more accurate/reliable functional annotation of VCF files.
Read more >Introduction to vcfR
The vcfR package is designed to work with data from VCF files. The use of a sequence file (FASTA format) and an annotation...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Right. Well, we should output diploid genotypes based on individuals in a way that works well with scikit-allel.
Closed in #286.