You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to build a MICOM model using abundance data generated from Paprica, with preprocessing applied to match MICOM’s expected format. However, I am encountering the following warning when running MICOM: Less than 50% of the abundance could be matched to the model database. Model community.py:229 sample_1105 may not be representative of the sample.
Additionally, when checking the manifest file, I noticed that none of my taxa were found in the MICOM model database, leading to a found_abundance_fraction of 0.0 for all samples.
Dataset Information
The taxonomy and abundance values were generated using Paprica.
Preprocessing was done to format it for MICOM.
Here is an example of my dataset before processing:
The manifest file shows that no taxa were matched in MICOM:
Would appreciate any guidance on resolving this issue. Thanks!
The text was updated successfully, but these errors were encountered:
So your taxa don't look right. The genus seems to be wrong for all of them. funiformis is Megamonas and Firmicutes is a phylum not a genus. copri would the Prevotella genus. MICOM always matches on as many ranks as possible, so in that case none of the genera match.
I am trying to build a MICOM model using abundance data generated from Paprica, with preprocessing applied to match MICOM’s expected format. However, I am encountering the following warning when running MICOM:
Less than 50% of the abundance could be matched to the model database. Model community.py:229 sample_1105 may not be representative of the sample.
Additionally, when checking the manifest file, I noticed that none of my taxa were found in the MICOM model database, leading to a found_abundance_fraction of 0.0 for all samples.
Dataset Information
The manifest file shows that no taxa were matched in MICOM:
Would appreciate any guidance on resolving this issue. Thanks!
The text was updated successfully, but these errors were encountered: