Open multimeric opened 6 years ago
Hmm, strange, I can't reproduce this, see session below:
(pysam-devel) andreas@cgath2[0]: /ifs/devel/andreas/pysam/tests/tt >
ls
test.vcf.gz
(pysam-devel) andreas@cgath2[0]: /ifs/devel/andreas/pysam/tests/tt >
python -c 'from pysam import tabix_index; tabix_index("test.vcf.gz", preset="vcf")'
(pysam-devel) andreas@cgath2[0]: /ifs/devel/andreas/pysam/tests/tt >
ls
test.vcf.gz test.vcf.gz.tbi
(pysam-devel) andreas@cgath2[0]: /ifs/devel/andreas/pysam/tests/tt >
python -c 'from pysam import tabix_index; tabix_index("test.vcf.gz", preset="vcf", csi=True)'
(pysam-devel) andreas@cgath2[0]: /ifs/devel/andreas/pysam/tests/tt >
ls
test.vcf.gz test.vcf.gz.csi test.vcf.gz.tbi
(pysam-devel) andreas@cgath2[0]: /ifs/devel/andreas/pysam/tests/tt >
Could you double-check?
I think I realised the issue was that it was actually a bcf
file, but with a filename ending in .vcf
. So I guess it actually did the correct behaviour
Basically,
pysam.tabix_index
always tries to make a CSI index for VCF files, no matter what you do. This is different behaviour fromtabix
, and also probably a bug.