-
Notifications
You must be signed in to change notification settings - Fork 5
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
Feature addition request #37
Comments
Adding another tool that relates to this thread, http://www.bcgsc.ca/platform/bioinfo/software/biobloomtools I think this is a tool that can sample fastq file and blast to see different species contamination |
I've been experimenting with For all these tools you need some kind of reference database(s) to screen against, which can involve different amounts of mucking around to setup properly depending on the tool (eg Bowtie indices vs pre-computed Bloom filter databases vs pre-computed 'sketch' indices). mash screenPros: single (relatively) small reference database (RefSeq genomes) is provided, simplifying setting up a pretty comprehensive screening db. Pretty fast. Cons: no MultiQC plugin (yet) fastq_screenPros: MultiQC support. Database download is now simple (but huge and slow) since they've added the Cons: Precomputed reference database might not be as comprehensive as the biobloomPros: MultiQC support. Cons: As far as I can tell, no precomputed reference databases are provided. |
Another option to consider (designed more for human data with potential microbial contamination): PathSeqhttp://software.broadinstitute.org/pathseq/ Doesn't appear to be in bioconda, so probably a non-starter :/ |
Thinking of adding a sample contamination check into the pipeline to get an assessment on sample purity.
Will become an increasing issue for those playing in microbiome/host genomics. But also for xenograft experiments (human/mouse) as examples.
One tool I have used is fastq screen
https://www.bioinformatics.babraham.ac.uk/projects/fastq_screen/
as a suggestion, I am sure there are other equivalent tools.
The text was updated successfully, but these errors were encountered: