How should the order of microbiome data preprocessing be prioritized?
1
0
Entering edit mode
11 days ago
ssko ▴ 20

Hello,

I have the microbiome count otu-table and I want to do an inferential/regression analysis. I want to present the results of my analysis at genus level. The literature says that the order of pre-processing can change depending on the purpose, but I want to be sure to get a consistent result. Is there any order of data pre-processing for this type of analysis: for example, is it recommended to do taxonomic aggregation at genus level first, then filter the genera by prevalence, then normalization/transformation, or is it recommended to do filtering first and then aggregation at genus level?

Thank you!

aggregation microbiome preprocess normalization filter • 359 views
ADD COMMENT
1
Entering edit mode
11 days ago
hakimbazol ▴ 40

Based on my experience, it depends on your dataset. Since you are talking about OTU, I assume your data based on amplicon sequencing, which usually only accurate up to genus level. Perhaps you can start your analysis from the common one, such as phyla, and then it goes to more specific level. If you have phenotype data, it also helps you quite much I think.

Hope it helps!

ADD COMMENT
0
Entering edit mode

So, is it acceptable to transform filtered relative abundance data with clr tranformation, or is it recommended to use all unfiltered data for clr transformation?

ADD REPLY
1
Entering edit mode

I think you should use all unfiltered data for clr transformation, and then use the transformation result to explore further about genotype-phenotype relationship for example. I found the publication that may become your reference.

https://microbiomejournal.biomedcentral.com/articles/10.1186/s40168-023-01747-z

Hope it helps!

ADD REPLY
0
Entering edit mode

I can't thank you enough for your great answers! hakimbazol

ADD REPLY

Login before adding your answer.

Traffic: 1990 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6