biostar-central VS htslib

Biostars is a great community, basically a bioinformatics-focused version of stackoverflow.

Go here: https://www.biostars.org/

Biostars (https://www.biostars.org/) Q and A forum for questions about bioinformatic tasks like alignment, differential expression analysis, etc., organized in a vaguely stack overflow like way.

Other place to get suggestions and padding for your Git repo would be to look at questions on boards like BioStars or StackExchange Implement, test, push, and comment with your solution. Make sure you all follow proper coding conventions too. Folks not only want the right answer they want to understand how it's done

also consider posting bioinformatics questions over at https://www.biostars.org/ instead of reddit

In the bioinformatics sphere there is this MIT-licensed Stack Exchange clone: https://github.com/ialbert/biostar-central

There is another nice multi-core gzip based library called BGZF[1]. It is commonly used in bioinformatics. BGZF has the added advantage that it is block compressed with built in indexing method to permit seeking in compressed files.

[1] https://github.com/samtools/htslib

In contrast, processing can start immediately and only transfer what is necessary if tooling can read bytes of data directly from Amazon S3. Tools based on htslib can do this, so you can run something like:

Another idea is add in reading cloud data natively e.g. htslib which samtools relies on can read s3 directly. https://github.com/samtools/htslib

Greetings! I'm a bioinformatics software dev in San Francisco and I'm looking for others interested in working on a high-performance genetic data analysis project. The project is in C, using https://github.com/samtools/htslib.

I'm working on a bioinformatics-related binding called ruby-htslib. htslib makes heavy use of bit fields throughout the library, so supporting bit fields is inevitable.