Skip to content
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.

figuring out tabix version #32

Open
prasundutta87 opened this issue Aug 13, 2020 · 4 comments
Open

figuring out tabix version #32

prasundutta87 opened this issue Aug 13, 2020 · 4 comments

Comments

@prasundutta87
Copy link

Hi,

Is there a way where I can figure out the version of tabix used for indexing a vcf.gz file?

Regards,
Prasun

@valeriuo
Copy link

No, tabix doesn't burn its version into the output index. How would that information help you?
Also, bear in mind that the latest released and maintained version of tabix is part of HTSlib.

@prasundutta87
Copy link
Author

prasundutta87 commented Aug 13, 2020

Thanks @valeriuo. I want to provide the version of tabix for a manuscript.

@valeriuo
Copy link

If you just want the version of tabix you are currently using, you can obtain that with the command:
tabix --version

@prasundutta87
Copy link
Author

prasundutta87 commented Aug 13, 2020

Actually, an analysis was done approx 1.5 years ago and tabix was the only tool whose version was not recorded. Our cluster system has different versions of tabix (sole installations) and various versions of samtools and bcftools. Tabix was run after running a Picard tool and now it is not known if it was the sole installation one or a part of HTSlib (samtools/bcftools) and hence, this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants