You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FADU is a great tool, especially for measuring transcription of operons. Unfortunately, I've run into a couple issues with FADU's compatibility with other common tools, such as bwa mem, bowtie2, and samtools.
First, from what I can tell, FADU only uses the optional "NH" sam attribute to detect multi-mapped reads. Neither bowtie2 nor bwa mem annotate alignments with NH. FADU does not return an error/ warning message when run on alignments lacking the NH attribute. Rather, it appears to just treat all reads as individually mapped. It might be helpful to include a warning, or even a script for annotating .bam files with the NH attribute.
Second, FADU will frequently fail on .bam files that have been processed with samtools view. I'm not sure why this is, but it occurs for roughly half of my samples. The error always occurs after the info message:
[ Info: Now finding overlaps between alignment and annotation records...
I've tried messing around with the samtools view parameters but still consistently get the error. It always occurs for some samples, and never for others. FADU runs without error on the original, pre samtools view alignment file, or .bam files created with pysam using the original alignment file as template.
The text was updated successfully, but these errors were encountered:
Thank you for the advice for the first issue... I will consider which is the best course of action between adding a warning or implementing alternative detection methods. For the second issue, can you list which version of FADU you are currently using? The latest version is v1.8.3.
Hi,
FADU is a great tool, especially for measuring transcription of operons. Unfortunately, I've run into a couple issues with FADU's compatibility with other common tools, such as bwa mem, bowtie2, and samtools.
First, from what I can tell, FADU only uses the optional "NH" sam attribute to detect multi-mapped reads. Neither bowtie2 nor bwa mem annotate alignments with NH. FADU does not return an error/ warning message when run on alignments lacking the NH attribute. Rather, it appears to just treat all reads as individually mapped. It might be helpful to include a warning, or even a script for annotating .bam files with the NH attribute.
Second, FADU will frequently fail on .bam files that have been processed with
samtools view
. I'm not sure why this is, but it occurs for roughly half of my samples. The error always occurs after the info message:[ Info: Now finding overlaps between alignment and annotation records...
And the stack trace always ends with:
I've tried messing around with the
samtools view
parameters but still consistently get the error. It always occurs for some samples, and never for others. FADU runs without error on the original, presamtools view
alignment file, or .bam files created with pysam using the original alignment file as template.The text was updated successfully, but these errors were encountered: