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

falco doesn't consider BAM flag bits #59

Open
wm75 opened this issue Jun 29, 2024 · 4 comments
Open

falco doesn't consider BAM flag bits #59

wm75 opened this issue Jun 29, 2024 · 4 comments

Comments

@wm75
Copy link

wm75 commented Jun 29, 2024

It seems that falco doesn't handle reverse-complemented read sequences in mapped BAM files correctly.
Specifically, when flag bit 0x04 of a read is not set (i.e. when the read is mapped), falco should consider the status of the 0x10 bit and reverse-complement the sequence if that bit is set.

Example output of falco (multiqc visualized) on just the reverse-strand reads from a mapped bam:

image

and those same reads analyzed with fastqc:

image

@bgruening
Copy link

@andrewdavidsmith this is blocking us from deploying falco as a real alternative for fastqc. Can you please have a look?

Thanks!

@andrewdavidsmith
Copy link
Collaborator

Yes, thanks. I can take a look within the next couple days.

@andrewdavidsmith
Copy link
Collaborator

@bgruening I have a fix in branch bam-strand-fix that shows these problems corrected for per-position quality scores and per-position nucleotide distributions. If you can check by pulling and building that specific branch it would be great. I should be able to merge this into the master branch soon.

@wm75
Copy link
Author

wm75 commented Jul 16, 2024

I tested the version on that branch and it behaves just like fastqc now.
Looking forward to seeing this in a release and thank you!

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

No branches or pull requests

3 participants