Currently any chimera information is logged only in the "all reads" FASTA file, would ideally extend the sample tally TSV with another column. Perhaps also for tagging reads which pass the spike-in test. Then could be used in the main reports.
Note this requires invoking VSEARCH twice, once for denoising, and again for chimera detection. Although time overhead seems minimal, should this be optional?
Currently any chimera information is logged only in the "all reads" FASTA file, would ideally extend the sample tally TSV with another column. Perhaps also for tagging reads which pass the spike-in test. Then could be used in the main reports.
Note this requires invoking VSEARCH twice, once for denoising, and again for chimera detection. Although time overhead seems minimal, should this be optional?