Hi everyone! This question was answered in other scenarios but I am still confused.
I am simply filtering out archea and eukaryotes from my 16srRNA data and whwnever I try to make the veiwable bar plots I get this error followed by a list of my samples. “Feature IDs found in the table are missing from the taxonomy:”
I assume it is because the table and the taxonomy did not filter out the same things but I am unfamiliar with QIIME2 and have no idea how to check if this is the case or how to gfix it. I have included my code below. All taxonomy assignments prior to filtering worked without a hitch but for some reason filtering is breaking everything.
Thank you so much for such a swift reply! I am a little confused why this works, wouldnt we want to use the filtered taxonomy for the bar plote? why use the original taxonomy file? Also when I check the bar plot, I still see d__Eukaryota;p__Diatomea represented, is there a way to filter again or did I miss something?
Thank you so much for all your help, I was finally able to make the bar plots! I simply wanted to filter out euks and archaea and in a tutorial that was made in my lab it had us make new filtered table, taxonomy and rep-seqs files then use that for all downstream analysis. I copied the code below. To my understanding, the way you did it uses the filtered table and the original taxonomy instead of the filtered taxonomy, why is that? I am a little confused why that works.
Hi @mainly.microbe,
Good question. It basically comes down to trying to simplify data management for users.
We tend to think of the information in these other artifacts (FeatureData[Taxonomy], FeatureData[Sequence], Phylogeny) as annotations of the features in a feature table - similar to how we think of sample metadata. Since feature tables tend to get filtered in various ways (on both the sample and feature axes), allowing the ids represented in these other artifacts to be a superset of the ones represented in the feature table prevents the need for lots of filtered versions of the other artifacts. For example, you might have two or three different feature tables that you're working with, but if they all use the same FeatureData[Taxonomy] artifact, that's easier to keep track of and the extra annotations in the FeatureData[Taxonomy] just get ignored. Same goes with sample metadata: there can be extra sample ids in there with respect to a feature table, but all sample ids represented in feature table must be present in the metadata.