Tweet
Originally posted by F_KVH
View Post
-
No, you'd only need something like xcode if you wanted to edit the source code. It wouldn't be needed just to run it. -
Dealing with Random Hexamer Bias?
Our group recently used the HiSeq 2000 platorm to generate transcriptome data (single-end, 50 bp reads). I have noticed that Illumina transcriptome sequencing yields typically yield these errors ("Per base sequence content" and "Per base GC content") during FastQC analysis. You suggest that these can safely be ignored when mapping to a genome? I wasn't sure if there was a "best practices" approach to dealing with these biases. Is there a mapping algorithm that is preferred among those who are dealing with Illumina transcriptome sequencing data?Originally posted by lletourn View Post
(I am sorry if this question has been answered thoroughly elsewhere in the forum... I have only just joined, and despite trying to navigate the posts with the "Search" tool, I have not yet come across an answer).Comment
-
It would probably be better to ignore them than try to correct them, though if you posted the fastqc graphs it would be easier to say.Originally posted by boilermaker View Post
I prefer BBMap when mapping Illumina RNA-seq data. It's more robust to errors than other RNA-seq aligners, and doesn't require an annotation file. Oh, and I wrote it, but that's not why.Is there a mapping algorithm that is preferred among those who are dealing with Illumina transcriptome sequencing data?Comment
-
Thank you Brian. I will certainly give BBMap a try (and thank you very much for scripting it!)Originally posted by Brian Bushnell View Post
I have attached a "typical" fastqc graphs (per base gc content, per base sequence content) from one of my datasets (most have profiles like this example).Comment
-
Doesn't look ideal, but I can't think of a good way to improve it, assuming you've already trimmed adapters (which can alter the base composition).Comment
-
The base composition bias you are seeing is very typical for RNA-Seq, and has indeed been mentioned on numerous posts here. The most relevant publication about this can be found here: http://nar.oxfordjournals.org/content/38/12/e131.full.
In essence, the bias is normally introduced by the random priming step in the RNA-Seq library preparation which is not quite as random as you would hope it was. Trimming the first positions of every read wouldn't make any difference since the sequence would still align to the very same position.Comment
-
If I had a penny for every time this question has been asked (and answered)Originally posted by fkrueger View Post
You (or Simon) really should make a sticky post with a few example plots about this (and k-mers). Will save many, a bunch of time and worry. Another suggestion would be to put a note on the FastQC page itself, so it would be visible to anyone downloading the software.Last edited by GenoMax; 04-30-2014, 04:10 PM.Comment
-
I don't think we, as normal users, can create sticky posts can we?Originally posted by GenoMax View PostIf I had a penny for every time this question has been asked (and answered)
You (or Simon) really should make a sticky post with a few example plots about this (and k-mers). Will save many, a bunch of time and worry. Another suggestion would be to put a note on the FastQC page itself, so it would be visible to anyone downloading the software.
I've added some information about this topic to the FastQC help so at least there will be a bit more guidance in the next release. I'll also have to make a new video for that so I'll make sure to mention it there. This is something we talk about at some length in the RNA-Seq analysis courses I run since it is a true technical bias but just one we tend to ignore (mostly because of not having any other option).
It's maybe also worth noting that a similar bias now seems to be appearing in transposase fragmented libraries, so it's not just RNA-Seq libraries which see this.Comment
-
I was thinking that you can create a post and then PM ECO (or one of the other moderators) to see if they can make it sticky.Originally posted by simonandrews View Post
Would it be useful to make this information available in the "Documentation" section of the main FastQC page where you have the Good/bad data set examples? Something along the lines of "this type of nucleotide distribution is normal if you have RNAseq data". Creating a video is a good idea but having the information available on a page that people can glance through (while their FastQC download is ongoing?) can make a better impact.Originally posted by simonandrews View PostComment
-
That's exactly what I did. When the package updates to the next version it will be there.Originally posted by GenoMax View PostComment
-
Hi All,
has by chance anybody figured out a pipeline that would automatically produce/convert the FASTQC report as a single file -perhaps as a single PDF file?
In my eyes it would be great if one could run FASTQC from the command line and not have to deal with an HTML folder and multiple files.
Thanks in advance.Comment
-
The next release of the program (which will be out by the end of next week if it kills me!) creates a single HTML file with embedded graphics so you will then be able to distribute just that file instead of having to keep the existing folder structure.Originally posted by luc View PostComment
-
Hi Simon,
thanks a lot. That sounds very practical.Comment
-
After a very long gestation I've finally released a new version of FastQC (v0.11.1). This is now available from the project web site.
This is a major release of the software which introduces a load of new features. Some of the big changes are:
- Added configurable warn/fail thresholds for all modules
- Allow modules to be selectively turned off
- Added a per-tile quality plot for Illumina libraries
- Added an adapter content plot
- Improved the duplication plot
- Improved the Kmer module
- Used embedded graphics in the HTML output so you can distribute a single file
- Added the ability to read data from stdin
- Changed how base grouping works to better accommodate long reads
- Dropped support for Solexa64 format (NB not Phred 64 which is still supported) to avoid mis-detection errors
We've done a fair bit of testing on the new version but I'm aware that there's a lot of new code in there so please report any problems either directly into our bug tracking system or via email to [email protected]Comment
-
Shouldn't that be2-6-13: Version 0.11.1 released
Thank you for adding the example reports on the FastQC page!2-6-14: Version 0.11.1 releasedComment
-
Data variability is still an issue in sequencing technologies despite the advances in reproducibility and accuracy of these platforms. But the problem does not originate in the sequencing itself, but in the previous steps, before the sample reaches the sequencer.
The first step is collection, followed by preservation and sample preparation for analysis. Most scientists overlook those steps, but not being careful might just be skewing the experiment’s results.
...Yesterday, 10:05 AM -
With the launch of new single-cell sequencing platforms in 2026, the field stands at an exciting inflection point. This article surveys the most impactful advances in the field and discusses how they’re reshaping research in cancer, immunology, and beyond.
Introduction
Single-cell sequencing technologies have undergone remarkable advances over the past decade, transitioning from low-throughput experimental approaches to highly scalable platforms capable of...05-22-2026, 06:42 AM -
Studying ecosystems means dealing with complex, multi-species communities that are hard to observe at scale. This complexity, however, hides many important questions to be answered, from how biogeochemical cycles work and how climate change can affect species distribution to how conservation strategies can work best.
Genomics, particularly since the expansion of NGS, has transformed ecosystem ecology. By sequencing environmental DNA, we can now assess biodiversity without direct...05-06-2026, 09:04 AM
Comment