Closed AlistairNWard closed 8 years ago
I'm taking a look at this now.
My first thought is that the original S3 location doesn't have the vcf.gz.tbi in the same directory or it is not set to public access.
I can reproduce the problem with the local file. I'm debugging the problem now.
Tried running a public 10X vcf file and it failed citing that vcf.iobio couldn't get the reference sequence lengths and set them all to zero. Looking at the vcf file, there doesn't seem to be any obvious reason why this would fail. It seems that this error is only occuring when pulling the vcf from the 10X S3 bucket or as a local file. I uploaded the vcf to app_testing (https://s3.amazonaws.com/iobio/app_testing/vcf_files/NA12878_10X.vcf.gz) and this seems to work, except for the ordering of the chromosomes.
URL to our S3 bucket:
From local file: