Why are the min/max read counts from the data inspection page different from the original file?

Maximum and minimum read counts may not correspond to the original ASV/OTU/KO table because the original data file goes through some pre-processing steps during the data Sanity Check.

First, features whose total count across all samples is 1 are removed (since this is likely to be sequencing error or artifacts). Additionally, features that have a variance of 0 are dropped. Then the min/max number of OTUs >=2 are calculated from this filtered table. Note, the minimum sample count is the highest non-zero value.