You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Re-heading the VCF by adding contigs information from NCBI GRCh38 FASTA sequence file does not help and same error persists. Looks like the file itself is not a strict VCF v4.1, even though it declares itself as such. But it was indexed at some point somehow, since the FTP site also contains accompanying freq.vcf.gz.tbi file. However, it is not possible to recreate the index file using the current version 1.21 of tabix.
The text was updated successfully, but these errors were encountered:
It looks like the data is malformed. The second sequence in the VCF is NC_000008.11 and one of the records there has a missing column - there should be 21, like in the rest of the VCF, but one row has just 20
Oh, so "sequence" in the error message means contig, that helps. The VCF file in question is really a mess, sorry for bugging you about something that was not your code's problem in the first place. Thank you!
Hi,
I am getting this cryptic error message when trying to create an index for NCBI ALFA VCF:
$ tabix -p vcf freq.vcf.gz
[E::hts_idx_push] Invalid record on sequence #2: end 1 < begin 2040518
tbx_index_build3 failed: freq.vcf.gz
The VCF was downloaded from NCBI FTP site: https://ftp.ncbi.nih.gov/snp/population_frequency/latest_release/
$ tabix |& head -3
Version: 1.21
Usage: tabix [OPTIONS] [FILE] [REGION [...]]
Re-heading the VCF by adding contigs information from NCBI GRCh38 FASTA sequence file does not help and same error persists. Looks like the file itself is not a strict VCF v4.1, even though it declares itself as such. But it was indexed at some point somehow, since the FTP site also contains accompanying freq.vcf.gz.tbi file. However, it is not possible to recreate the index file using the current version 1.21 of tabix.
The text was updated successfully, but these errors were encountered: