QIIME classic OTU table (tabbed text)
Home Software Services About Contact     
 
Follow on twitter

Robert C. Edgar on twitter

11-Aug-2018 New paper describes octave plots for visualizing alpha diversity.

12-Jun-2018 New paper shows that one in five taxonomy annotations in SILVA and Greengenes are wrong.

18-Apr-2018 New paper shows that taxonomy prediction accuracy is <50% for V4 sequences.

05-Oct-2017 PeerJ paper shows low accuracy of closed- and open-ref. QIIME OTUs.

22-Sep-2017 New paper shows 97% threshold is wrong, OTUs should be 99% full-length 16S, 100% for V4.

24-Nov-2016
UPARSE tutorial video posted on YouTube. Make OTUs from MiSeq reads.

 

USEARCH v11

QIIME classic OTU table (tabbed text)

See also
 
Making an OTU table (otutab command)

QIIME classic format is a tab-separated text used to store an OTU table. Newer versions of QIIME are moving to BIOM format for OTU tables, though in QIIME v1.9 some (many or most?) scripts still support classic files.

The first line has column headings, the remaining lines are OTUs.

The first column heading is "#OTU ID" (the quotes are not included, and there is exactly one space between OTU and ID). The other headings are sample names.

Optionally, the last column is used for a taxonomy annotation. I'm not sure which QIIME scripts use / need  this column, or what the formatting requirements for the taxonomy names and ranks. If you need taxonomy in a classic table and run into problems, please let me know and I'll update this documentation and add features to USEARCH as needed.

A value in the matrix is an integer count, i.e. the number of reads for that OTU in that sample. As far as I know, fractional values such as frequencies are not supported by QIIME. It is up to the user to keep track of which type of count is used, e.g. raw, normalized, subsampled or rarified.

WARNING -- QIIME doesn't like underscores in OTU names
Some of my examples use OTU idenfiers like OTU_123, as in the table below. Underscores in OTU identifiers can cause problems with QIIME, apparently because the Newick tree file standard uses underscore to mean a blank space (because the problem only seems to occur when a tree file is used). Some USEARCH commands only allow letters, digits and underscores in OTU identifiers, so you can't use another punctuation symbol (e.g., a period). The safest choice is to avoid underscores and use something like Otu123.

Example QIIME classic OTU table

Image