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 run functional prediction profile using Tax4Fun on my dataset, and getting an error: ErrorPlease check the taxonomy labels
I have used qiime2 to generate ASVs and Silva db release 132 for taxonomy assignment.
For the input into MicrobiomeAnalystR I am using text file containing features and taxonomy, what you refer in your instructions as "Taxonomic profile with valid taxonomy identifier labeled names" and metadata file. The uploading of data (Taxonomy lables: SILVA), inspection, filtration and normalisation works fine. Same as taxa visualisation, alpha, beta diversity, etc.
However, it seems that there is some problem with prediction part (QIIME against SILVA databse), or as the error message specifies, taxonomy labels.
Taxonomic profile file is structured exactly the same way as in you example. I am not sure what is happening here.
Any help appreciated,
Deni
The text was updated successfully, but these errors were encountered:
Hi there,
I am trying to run functional prediction profile using Tax4Fun on my dataset, and getting an error:
ErrorPlease check the taxonomy labels
I have used qiime2 to generate ASVs and Silva db release 132 for taxonomy assignment.
For the input into
MicrobiomeAnalystR
I am using text file containing features and taxonomy, what you refer in your instructions as "Taxonomic profile with valid taxonomy identifier labeled names" and metadata file. The uploading of data (Taxonomy lables: SILVA), inspection, filtration and normalisation works fine. Same as taxa visualisation, alpha, beta diversity, etc.However, it seems that there is some problem with prediction part (QIIME against SILVA databse), or as the error message specifies, taxonomy labels.
Taxonomic profile file is structured exactly the same way as in you example. I am not sure what is happening here.
Any help appreciated,
Deni
The text was updated successfully, but these errors were encountered: