home.social

#samtools — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #samtools, aggregated by home.social.

  1. RE: genomic.social/@yokofakun/1157

    github.com/samtools/htsjdk/dis

    > HTSJDK has not been the most actively maintained project for a long time, and with many departures from Broad in the last couple of years, it's not clear to me who still has an active interest in helping maintain the project.

    #java #htsjdk #samtools

  2. RE: genomic.social/@yokofakun/1157

    github.com/samtools/htsjdk/dis

    > HTSJDK has not been the most actively maintained project for a long time, and with many departures from Broad in the last couple of years, it's not clear to me who still has an active interest in helping maintain the project.

    #java #htsjdk #samtools

  3. RE: genomic.social/@yokofakun/1157

    github.com/samtools/htsjdk/dis

    > HTSJDK has not been the most actively maintained project for a long time, and with many departures from Broad in the last couple of years, it's not clear to me who still has an active interest in helping maintain the project.

    #java #htsjdk #samtools

  4. RE: genomic.social/@yokofakun/1157

    github.com/samtools/htsjdk/dis

    > HTSJDK has not been the most actively maintained project for a long time, and with many departures from Broad in the last couple of years, it's not clear to me who still has an active interest in helping maintain the project.

    #java #htsjdk #samtools

  5. RE: genomic.social/@yokofakun/1157

    github.com/samtools/htsjdk/dis

    > HTSJDK has not been the most actively maintained project for a long time, and with many departures from Broad in the last couple of years, it's not clear to me who still has an active interest in helping maintain the project.

    #java #htsjdk #samtools

  6. github.com/Dedaniya08/samtools This repository is a GPU-accelerated fork of samtools/samtools, originally developed by Genome Research Ltd. and contributors.

    #samtools #bioinformatics #gpu

  7. github.com/Dedaniya08/samtools This repository is a GPU-accelerated fork of samtools/samtools, originally developed by Genome Research Ltd. and contributors.

    #samtools #bioinformatics #gpu

  8. github.com/Dedaniya08/samtools This repository is a GPU-accelerated fork of samtools/samtools, originally developed by Genome Research Ltd. and contributors.

    #samtools #bioinformatics #gpu

  9. github.com/Dedaniya08/samtools This repository is a GPU-accelerated fork of samtools/samtools, originally developed by Genome Research Ltd. and contributors.

    #samtools #bioinformatics #gpu

  10. github.com/Dedaniya08/samtools This repository is a GPU-accelerated fork of samtools/samtools, originally developed by Genome Research Ltd. and contributors.

    #samtools #bioinformatics #gpu

  11. @kaasbaas #wikipedia (English language) is only ~22GB of #bzip2 compressed #xml (uncompressed size is ~86GB).
    is it possible to access it without decompression? I guess #random #access to .xml.bz2 should be a solved problem, right?
    we're routinely using gzip with random access in #bioinformatics ie via #samtools or #tabix

    EDIT:
    Wikipedia xml.bz2 does support random access for multistream version. does @kiwix or any other wiki reader support it? I couldn't find info on their website...

  12. @kaasbaas #wikipedia (English language) is only ~22GB of #bzip2 compressed #xml (uncompressed size is ~86GB).
    is it possible to access it without decompression? I guess #random #access to .xml.bz2 should be a solved problem, right?
    we're routinely using gzip with random access in #bioinformatics ie via #samtools or #tabix

    EDIT:
    Wikipedia xml.bz2 does support random access for multistream version. does @kiwix or any other wiki reader support it? I couldn't find info on their website...

  13. @kaasbaas #wikipedia (English language) is only ~22GB of #bzip2 compressed #xml (uncompressed size is ~86GB).
    is it possible to access it without decompression? I guess #random #access to .xml.bz2 should be a solved problem, right?
    we're routinely using gzip with random access in #bioinformatics ie via #samtools or #tabix

    EDIT:
    Wikipedia xml.bz2 does support random access for multistream version. does @kiwix or any other wiki reader support it? I couldn't find info on their website...

  14. @kaasbaas #wikipedia (English language) is only ~22GB of #bzip2 compressed #xml (uncompressed size is ~86GB).
    is it possible to access it without decompression? I guess #random #access to .xml.bz2 should be a solved problem, right?
    we're routinely using gzip with random access in #bioinformatics ie via #samtools or #tabix

    EDIT:
    Wikipedia xml.bz2 does support random access for multistream version. does @kiwix or any other wiki reader support it? I couldn't find info on their website...

  15. @kaasbaas #wikipedia (English language) is only ~22GB of #bzip2 compressed #xml (uncompressed size is ~86GB).
    is it possible to access it without decompression? I guess #random #access to .xml.bz2 should be a solved problem, right?
    we're routinely using gzip with random access in #bioinformatics ie via #samtools or #tabix

    EDIT:
    Wikipedia xml.bz2 does support random access for multistream version. does @kiwix or any other wiki reader support it? I couldn't find info on their website...

  16. Just out: @multiqc v1.25.2 🎉

    This patch release fixes a whole host of bugs, the most important one being for #bcl2fastq 🐛

    There are also a host of small additions sneaking in for #ngsbits, #picard, #Nanostat, #Samtools and more - so well worth the update!

    github.com/MultiQC/MultiQC/rel

  17. Just out: @multiqc v1.25.2 🎉

    This patch release fixes a whole host of bugs, the most important one being for #bcl2fastq 🐛

    There are also a host of small additions sneaking in for #ngsbits, #picard, #Nanostat, #Samtools and more - so well worth the update!

    github.com/MultiQC/MultiQC/rel

  18. Just out: @multiqc v1.25.2 🎉

    This patch release fixes a whole host of bugs, the most important one being for #bcl2fastq 🐛

    There are also a host of small additions sneaking in for #ngsbits, #picard, #Nanostat, #Samtools and more - so well worth the update!

    github.com/MultiQC/MultiQC/rel

  19. Just out: @multiqc v1.25.2 🎉

    This patch release fixes a whole host of bugs, the most important one being for #bcl2fastq 🐛

    There are also a host of small additions sneaking in for #ngsbits, #picard, #Nanostat, #Samtools and more - so well worth the update!

    github.com/MultiQC/MultiQC/rel

  20. Just out: @multiqc v1.25.2 🎉

    This patch release fixes a whole host of bugs, the most important one being for #bcl2fastq 🐛

    There are also a host of small additions sneaking in for #ngsbits, #picard, #Nanostat, #Samtools and more - so well worth the update!

    github.com/MultiQC/MultiQC/rel

  21. gcc -g -Wall -O2 -fvisibility=hidden -I. -c -o simd.o simd.c

    simd.c:126:5: warning: implicit declaration of function ‘_mm_lddqu_si128’ [-Wimplicit-function-declaration]
    __m128i nuc_lookup_vec = _mm_lddqu_si128((__m128i *)seq_nt16_str);
    ^
    simd.c:126:30: error: incompatible types when initializing type ‘__m128i’ using type ‘int’
    __m128i nuc_lookup_vec = _mm_lddqu_si128((__m128i *)seq_nt16_str);

    🤔 #samtools 1.21

  22. gcc -g -Wall -O2 -fvisibility=hidden -I. -c -o simd.o simd.c

    simd.c:126:5: warning: implicit declaration of function ‘_mm_lddqu_si128’ [-Wimplicit-function-declaration]
    __m128i nuc_lookup_vec = _mm_lddqu_si128((__m128i *)seq_nt16_str);
    ^
    simd.c:126:30: error: incompatible types when initializing type ‘__m128i’ using type ‘int’
    __m128i nuc_lookup_vec = _mm_lddqu_si128((__m128i *)seq_nt16_str);

    🤔 #samtools 1.21

  23. gcc -g -Wall -O2 -fvisibility=hidden -I. -c -o simd.o simd.c

    simd.c:126:5: warning: implicit declaration of function ‘_mm_lddqu_si128’ [-Wimplicit-function-declaration]
    __m128i nuc_lookup_vec = _mm_lddqu_si128((__m128i *)seq_nt16_str);
    ^
    simd.c:126:30: error: incompatible types when initializing type ‘__m128i’ using type ‘int’
    __m128i nuc_lookup_vec = _mm_lddqu_si128((__m128i *)seq_nt16_str);

    🤔 #samtools 1.21

  24. gcc -g -Wall -O2 -fvisibility=hidden -I. -c -o simd.o simd.c

    simd.c:126:5: warning: implicit declaration of function ‘_mm_lddqu_si128’ [-Wimplicit-function-declaration]
    __m128i nuc_lookup_vec = _mm_lddqu_si128((__m128i *)seq_nt16_str);
    ^
    simd.c:126:30: error: incompatible types when initializing type ‘__m128i’ using type ‘int’
    __m128i nuc_lookup_vec = _mm_lddqu_si128((__m128i *)seq_nt16_str);

    🤔 #samtools 1.21

  25. gcc -g -Wall -O2 -fvisibility=hidden -I. -c -o simd.o simd.c

    simd.c:126:5: warning: implicit declaration of function ‘_mm_lddqu_si128’ [-Wimplicit-function-declaration]
    __m128i nuc_lookup_vec = _mm_lddqu_si128((__m128i *)seq_nt16_str);
    ^
    simd.c:126:30: error: incompatible types when initializing type ‘__m128i’ using type ‘int’
    __m128i nuc_lookup_vec = _mm_lddqu_si128((__m128i *)seq_nt16_str);

    🤔 #samtools 1.21

  26. I was reminded of this helpful tool the other day to identify SAM/BAM/CRAM flag values.
    Great when you are hacking away with #samtools view commands and need to know the flag number to filter based on read properties, such as read unmapped and mate unmapped.
    #genomics #bioinformatics
    broadinstitute.github.io/picar

  27. I just wrote a new PR for `samtools coverage` to plot the depth instead of the '% of covered bases' . Useful to validate #CNV in the terminal. #samtools #bioinformatics #sv #variant #bam

    github.com/samtools/samtools/p

  28. plot depth of #coverage in the #terminal using #samtools #depth and gnuplot:

    ```
    $ samtools depth -a -r "chr1:234-456" in.bam | cut -f 2,3 | gnuplot -e 'set terminal dumb size 120,28; plot "-" smooth csplines with lines notitle'
    ```

    #linux #bioinformatics