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 think we use both "feature" and "taxa" when we are talking about rows. "Feature" is more generic, but we could use more "taxa" as most of the readers are working with them as @nuorenarra pointed out.
The text was updated successfully, but these errors were encountered:
Consistency is good. I would say that consistency is even more important.
It could be taxa but on the other hand, we may also deal with functional predictions (e.g. from HUMAnN) or other omics (e.g. metabolomics) using the same methods, and this is now done on a regular basis. Therefore referring to "taxa" can be confusing as well. It might depend on the context.
Perhaps "taxonomic features"? And if there are other types of examples, then functional or metabolomic features.
It might be good, anyway, to explain the relation between these in the introductory chapter where the data structure is introduced.
I think we use both "feature" and "taxa" when we are talking about rows. "Feature" is more generic, but we could use more "taxa" as most of the readers are working with them as @nuorenarra pointed out.
The text was updated successfully, but these errors were encountered: