![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
MiSeq gDNA reads still fail "Kmer content" and "per base seq content" after trimming" | ysnapus | Illumina/Solexa | 4 | 11-12-2014 08:25 AM |
AVA-difference betweeen "computation" reads and "global align" reads | CCBIO | 454 Pyrosequencing | 0 | 01-17-2014 04:13 AM |
DEXSeq error in estimateDispersions: match.arg(start.method, c("log(y)", "mean")) | fpadilla | Bioinformatics | 14 | 07-03-2013 03:11 PM |
The position file formats ".clocs" and "_pos.txt"? Ist there any difference? | elgor | Illumina/Solexa | 0 | 06-27-2011 08:55 AM |
SEQanswers second "publication": "How to map billions of short reads onto genomes" | ECO | Literature Watch | 0 | 06-30-2009 12:49 AM |
![]() |
|
Thread Tools |
![]() |
#1 |
Senior Member
Location: Hong Kong Join Date: Mar 2010
Posts: 498
|
![]()
http://www.ncbi.nlm.nih.gov/sra/SRX573008[accn]
I downloaded this SRA data. I noticed that the R1 reads are 150bp but the R2 reads are 350bp. How could that be? Aren't they supposed to be the same length??? ![]() |
![]() |
![]() |
![]() |
#2 |
Jafar Jabbari
Location: Melbourne Join Date: Jan 2013
Posts: 1,238
|
![]()
Unequal length on MiSeq is permitted.
|
![]() |
![]() |
![]() |
#3 |
Senior Member
Location: Hong Kong Join Date: Mar 2010
Posts: 498
|
![]() |
![]() |
![]() |
![]() |
#4 |
Super Moderator
Location: Walnut Creek, CA Join Date: Jan 2014
Posts: 2,707
|
![]()
All else equal... longer reads are more useful. 350bp reads can span repeats that 250bp reads can't, for example.
However, all else is NOT equal, and I seriously doubt the quality at the end of those 350bp reads is very good. |
![]() |
![]() |
![]() |
#5 |
Senior Member
Location: Hong Kong Join Date: Mar 2010
Posts: 498
|
![]()
Thanks a lot for your reply. Are there any limitations to adjusting the lengths? Can you do 1/499 or even 0/500???
|
![]() |
![]() |
![]() |
#6 |
Senior Member
Location: Bethesda MD Join Date: Oct 2009
Posts: 509
|
![]()
Well, you need 4-5 cycles in the first read to call clusters, and at least 25 cycles for base-calling. Plus, as Brian noted, the quality drops precipitously with the longer reads. But I think that the instrument could be programmed for 25/475.
|
![]() |
![]() |
![]() |
#7 | |
Senior Member
Location: Hong Kong Join Date: Mar 2010
Posts: 498
|
![]() Quote:
![]() |
|
![]() |
![]() |
![]() |
#8 |
Senior Member
Location: East Coast USA Join Date: Feb 2008
Posts: 7,087
|
![]()
Or you could do a 600 cycle SE run.
|
![]() |
![]() |
![]() |
#9 |
Senior Member
Location: Hong Kong Join Date: Mar 2010
Posts: 498
|
![]() |
![]() |
![]() |
![]() |
#10 |
Jafar Jabbari
Location: Melbourne Join Date: Jan 2013
Posts: 1,238
|
![]()
It can be done with v2 too and possibly on HiSeq. In MiSeq after cycle 200 the quality drops and is in lowest value at 300 cycle. Increasing cycle beyond that results in low quality so it may not be useful depending on intended use of data.
|
![]() |
![]() |
![]() |
#11 | |
Member
Location: UK Join Date: Jan 2012
Posts: 36
|
![]() Quote:
So we often do 100/400 reads to ensure we get index data for all clusters, then hopefully get as much of a reverse read as possible for the small percentage of larger fragments in the library - if the run aborts on read 2, we can at least recover the data, but if it aborts on read 1, the data is useless as it can't be demultiplexed. |
|
![]() |
![]() |
![]() |
Thread Tools | |
|
|