![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
seq.txt, qseq.txt and fastq | NicoBxl | Bioinformatics | 5 | 01-03-2014 09:35 AM |
How to make sense of Tophat's output file 'junctions.bed' | gsinghal | RNA Sequencing | 4 | 09-03-2012 07:49 AM |
export.txt files/ quality filtering | oleg | Illumina/Solexa | 8 | 08-19-2010 06:20 AM |
qseq files versus sequence.txt files | drio | Illumina/Solexa | 3 | 11-09-2009 10:02 AM |
quality scores vs prb files | Leighton | Illumina/Solexa | 7 | 10-16-2008 02:58 AM |
![]() |
|
Thread Tools |
![]() |
#1 |
Member
Location: Riverside, CA Join Date: Oct 2008
Posts: 13
|
![]()
I'm running the Illumina pipeline 1.3.2, and I noticed that the quality scores in the qseq.txt file appear to be the same as the alignment-normalized scores produced by Eland/Gerald, which are totally erroneous for reads without a good reference genome.
It seems like Gerald is going back and injecting these quality scores into the Bustard output rather than just putting them in the Gerald output. Why would they do this? Is there any way to get the quality scores in the new (Phred) format without producing the legacy prb files and converting them?
__________________
@1 NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN + """""""""""""""""""""""""""""""""""" |
![]() |
![]() |
![]() |
#2 |
Member
Location: Cincinnati Join Date: Oct 2008
Posts: 15
|
![]()
As of 1.3.2, Bustard does the qs calibration according to an internal table. You can do custom calibration from the command line, so if you want uncalibrated scores in the new format you could create probably create a custom custom calibration table that leaves the values unchanged. I do not know the format of the calibration table off the top of my head, but it is somewhere in the distribution.
|
![]() |
![]() |
![]() |
#3 | |
Member
Location: Riverside, CA Join Date: Oct 2008
Posts: 13
|
![]()
So calibration no longer depends on the reference genome?
If so, this makes a lot of sense, as it doesn't make the (often false) assumption that all failed alignments are due to sequencing error. Quote:
__________________
@1 NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN + """""""""""""""""""""""""""""""""""" |
|
![]() |
![]() |
![]() |
Thread Tools | |
|
|