![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
guidelines with 16s RNA data | bio_informatics | General | 8 | 05-01-2015 07:40 AM |
Removing duplicates from 16S RNA data | mhadidi2002 | Bioinformatics | 6 | 10-28-2014 06:59 AM |
lots of short read between 16s rDNA Region V1-V3 ? | stare024 | 454 Pyrosequencing | 4 | 11-25-2013 04:08 AM |
problems with fragments lenght | sarapegolo | Sample Prep / Library Generation | 0 | 10-11-2013 02:06 AM |
Optimal read lenght for RNASeq | cjohnson | RNA Sequencing | 6 | 12-09-2010 09:34 PM |
![]() |
|
Thread Tools |
![]() |
#1 |
Member
Location: Warsaw Join Date: Mar 2014
Posts: 17
|
![]()
Hi,
My amplicon after assembly shoud have approx. 460bp. Do I have to analyze only 460bp products or can I also analyze some shorter/longer amplicons. If yes, how to set a specific lenght range/limit. For example I have 200000 reads per sample, almost 52% of them are shorter than 460bp, but only 11% are shorter than 440bp. I think that those reads also have an importance and value, but how to set the range? Please help me. |
![]() |
![]() |
![]() |
#2 |
Senior Member
Location: California Join Date: Jul 2014
Posts: 198
|
![]()
What amplicon are you using? Some of them have substantial variation in length in the variable region.
See: https://www.biostars.org/p/78179/ |
![]() |
![]() |
![]() |
#3 |
Member
Location: Warsaw Join Date: Mar 2014
Posts: 17
|
![]()
primes that target 16S V3 and V4 region (used in illumina 16S metagenomic protocol)
|
![]() |
![]() |
![]() |
#4 |
Senior Member
Location: CT Join Date: Apr 2015
Posts: 243
|
![]()
I pretty strongly recommend using mothur which aligned the reads to a know database (more robust to discard seqs that don't align rather than picking an arbitrary length). But, know that the illumina 16s kit produces not great results because you have so little overlap to correct miscalled bases.
__________________
Microbial ecologist, running a sequencing core. I have lots of strong opinions on how to survey communities, pretty sure some are even correct. |
![]() |
![]() |
![]() |
Thread Tools | |
|
|