Hi all,
What tools are people using for QC'ing the initial stages of NGS data analysis?
I'm thinking tools that run on
- unaligned .fastq
- aligned .bam
- single vs. paired end
- exome seq vs. RNAseq
- possibly whole-genome, chipseq
I'm currently using FastQC and picard - but have been thinking of ways to improve on this (which led to the feature list below). I would appreciate tool recommendations and/or suggestions for additional features you like or don't like in your QC tools.
Thanks,
-Ben
Ps. Desired features:
* FastQC-like
- user-friendly web interface
- very easy to download, install, run
* Picard-like
- handles both single and paired-end data, aligned and unaligned
- outputs data tables that are easy to read into R, etc.
* Extensibility
- A simple way to add custom graphs and stats would be nice. Although picard and FastQC are both open source and modular, they are written in Java which adds complexity and reduces the potential developer base relative to a language like python (or a toolkit that's not language-specific).
- An open development model (free/open-source) with more than one active contributor (but strong focus on retaining simplicity and not trying to solve all problems).
- That being said, ideally the tool would accumulate knowledge about typical problems/failures in common protocols, and where possible, give suggestions on causes rather than just report graphs/stats/warnings and expect users to know what to do. So where possible, aimed at NGS newbies.
* Holistic
- at the risk of added complexity, the tool could simultaneously take .fastq and one or more processed bam files from a single sample, and then show both unaliged and aligned stats in one interface, as well as how the stats change as a result of the different processing steps in the NGS pipeline.
What tools are people using for QC'ing the initial stages of NGS data analysis?
I'm thinking tools that run on
- unaligned .fastq
- aligned .bam
- single vs. paired end
- exome seq vs. RNAseq
- possibly whole-genome, chipseq
I'm currently using FastQC and picard - but have been thinking of ways to improve on this (which led to the feature list below). I would appreciate tool recommendations and/or suggestions for additional features you like or don't like in your QC tools.
Thanks,
-Ben
Ps. Desired features:
* FastQC-like
- user-friendly web interface
- very easy to download, install, run
* Picard-like
- handles both single and paired-end data, aligned and unaligned
- outputs data tables that are easy to read into R, etc.
* Extensibility
- A simple way to add custom graphs and stats would be nice. Although picard and FastQC are both open source and modular, they are written in Java which adds complexity and reduces the potential developer base relative to a language like python (or a toolkit that's not language-specific).
- An open development model (free/open-source) with more than one active contributor (but strong focus on retaining simplicity and not trying to solve all problems).
- That being said, ideally the tool would accumulate knowledge about typical problems/failures in common protocols, and where possible, give suggestions on causes rather than just report graphs/stats/warnings and expect users to know what to do. So where possible, aimed at NGS newbies.
* Holistic
- at the risk of added complexity, the tool could simultaneously take .fastq and one or more processed bam files from a single sample, and then show both unaliged and aligned stats in one interface, as well as how the stats change as a result of the different processing steps in the NGS pipeline.
Comment