![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
what is the meaning of BED score? | whfwind | Bioinformatics | 3 | 07-24-2017 11:45 PM |
What is the meaning density in CummeRbund plots? | Carlos Borroto | Bioinformatics | 16 | 12-29-2016 10:05 PM |
the meaning of sequence 'M','Y','K' in samtools? | dkrtndhkd | Bioinformatics | 2 | 02-06-2012 12:56 AM |
Meaning of '0' quality score in MAQ | paulig | Bioinformatics | 0 | 11-29-2010 07:33 AM |
the meaning of Match Position for reads? | beliefbio | Illumina/Solexa | 2 | 11-27-2009 06:43 PM |
![]() |
|
Thread Tools |
![]() |
#1 |
Junior Member
Location: houston Join Date: Jan 2009
Posts: 1
|
![]()
In the XXXX_.QV.qual file, there is a quality value for each position.
I wonder how they calculate this value and what is the meaning of this value. For traditional sequecing, I think quality value is the P value of the corret read over the noise, then -10logP. However, for SOLID, every read is from 2 base pair, how do they get the quality value? Anybody can provide some advice or reference? Thanks a lot! |
![]() |
![]() |
![]() |
#2 |
Member
Location: India Join Date: Oct 2008
Posts: 36
|
![]()
I think it gives quality value for color call...this is abased many parameters majorly intensity.
|
![]() |
![]() |
![]() |
#3 |
Member
Location: Sydney, Australia Join Date: Jan 2009
Posts: 17
|
![]()
This is all I have been able to find:
"The QV value is calculated using a phred like score q = -10 x log10(p) where q is the quality value and (p) is the predicted probability that the color call is incorrect" which is from this document: ftp://ftp.ncbi.nih.gov/pub/TraceDB/S...ions_Guide.pdf |
![]() |
![]() |
![]() |
#4 |
Member
Location: New York City Join Date: Aug 2009
Posts: 14
|
![]()
If you convert from colorspace to [ATGC], how do you convert the QV value? Take the average?
|
![]() |
![]() |
![]() |
#5 | |
Senior Member
Location: Purdue University, West Lafayette, Indiana Join Date: Aug 2008
Posts: 2,317
|
![]() Quote:
I recommend against conversion of raw reads from color space because an error in one position would propagate through the rest of the read. That is, if your read had a single error at base 2, then by converting the read to base space, you would ensure that every base after base 2 was incorrect. Later errors could shift you back into the correct sequence frame, however. So, even were you wanting to risk switching into base space, there would be no way to convert the quality values. Or at least, no trivial way. On the other hand, converting base space sequence into color space involves no such risk. Converting quality values would still not be straight forward, but you could estimate them by choosing the lower quality value of the two bases. Really, if you are trying to use color space-naive code, your only decent choice is to use "double encoding". This involves doing a tr/0123/acgt/ conversion. The resulting fake sequence now is usable in color space-naive code. With the caveat that reverse-complementing is illegitimate on double encoded sequence. (Because in color space one reverses to reverse-complement...) -- Phillip |
|
![]() |
![]() |
![]() |
Tags |
solid |
Thread Tools | |
|
|