![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Normalization and analysis of proteomic spectral count data | bjackson | Bioinformatics | 0 | 05-08-2015 10:37 AM |
RNA seq data filter low count before or after normalization | qliu | RNA Sequencing | 4 | 01-10-2015 02:21 AM |
NGS Data Normalization | Genohub | Literature Watch | 0 | 06-29-2014 08:16 AM |
Different normalization methods with count data | greener | Bioinformatics | 2 | 09-01-2013 06:27 AM |
ChIP-Seq: A normalization strategy for comparing tag count data. | Newsbot! | Literature Watch | 0 | 04-06-2012 06:00 AM |
![]() |
|
Thread Tools |
![]() |
#1 |
Member
Location: Germany Join Date: Sep 2013
Posts: 11
|
![]()
Dear community,
we have a MiSeq 16S-dataset featuring samples from enrichment studies, i.e. communities from a time series in which some OTUs become dominant over time, e.g. up to 90% of all reads. The biological question would to find a) which OTUs respond to different enrichment strategies and b) when they start to enrich. I guess, this qualifies as a expression analysis to detect differentially expressed OTUs. Thus, we need to normalize the data due to highly variable sequence depths (20,000 to 70, 000 reads) and to validate our post-hoc analysis. I tried percentile-based normalization like CSS but i have just learned the hard way, that they are not suited for this dataset (as they typically want to see relatively invariate data). CSS, e.g., just took away all observations from the enriched OTUs until the enrichment effect was not visible anymore. Rarefying is inadmissable as McMurdie & Holmes told us. Total-Sum-Scaling (i.e. scaling to all reads in a sample) is dangerous because it is sensitive to compositional effects (as our samples tend to become very uneven over time). Any ideas how to best treat the data would be greatly appreciated. I posted the same question to the QIIME and Biostars forums, but got few answers which sums up to "There is no real answer to your problem". I was pointed to ANCOM (and texmexseq), which are nice tools, but they either dont say anything about normalization or do it internally. |
![]() |
![]() |
![]() |
Thread Tools | |
|
|