Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User Guide #114

Open
danielecook opened this issue Jul 22, 2014 · 6 comments
Open

User Guide #114

danielecook opened this issue Jul 22, 2014 · 6 comments

Comments

@danielecook
Copy link

Is there a user guide / documentation for htslib?

@jmarshall
Copy link
Member

There is at present nothing beyond the (rather incomplete) API documentation inline in the header files.

(And what can be gleaned by considering the samtools and bcftools code as "sample code".)

@danielecook
Copy link
Author

Thanks. I'll see what I can pick up.

pd3 added a commit to pd3/htslib that referenced this issue Sep 25, 2015
@imgag
Copy link

imgag commented Mar 21, 2018

I started using htslib to read/manipulate BAM files a few days ago and I second that there should be more documentation.

I can see that this is boring work and that documentation often diverges from the code, which is why in-code documentation has its advantages. However, the in-code documentation is often incomplete or completely missing (at least for the BAM part). Thus, I advocate for some example programs that read/write data to illustrate the most common use-cases. The example programs would be buildable/testable, so it's easy to keep them up-to-date.

For BAM files I would have hoped for these examples:

  • read and print the file header and alignments
  • manipulate the file header and alignments (including bases, qualities, CIGAR, ...)

@rulixxx
Copy link

rulixxx commented Dec 8, 2020

Started using htslib myself some months ago and still find it difficult to find usage of some parts of it. It makes development more time consuming and error prone.

@valeriuo
Copy link
Contributor

valeriuo commented Dec 8, 2020

@rulixxx We are quite aware of this aspect and we are planning to invest more resources in the documentation and the user guide. In the meantime, can you describe your use case and see how we can assist you?
You can use [email protected], if you don't want to post it here.

@rulixxx
Copy link

rulixxx commented Dec 8, 2020 via email

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

No branches or pull requests

4 participants