DOI: 10.5281/zenodo.5751456
title: NanoClass-compatible BOLD CO1 databases

description: BOLD CO1 databases reformatted to use in NanoClass (https://github.com/ejongepier/NanoClass; version 0.3.0-beta or higher) and QIIME2. Three separate databases are included for use in combination with primers mtD, LCO-HCO and CI. Databases include reference sequences and reference taxonomies for the use in NanoClass, as well as pre-trained classifiers for use in QIIME2. See usage instructions below. For questions, please contact e.jongepier@uva.nl. ==========================================<br> WARNING<br> ========================================== Please note this version of a custom BOLD CO1 db comes with absolutely no warranties. When using this db in NanoClass, mind that it has only been tested with methods: ["megablast","minimap","spingo"]<br> NanoClass cannot be run in combination with these BOLD CO1 databases using methods ["mothur","centrifuge","kraken"].<br> Compatibility with ["blast","dcmegablast","qiime","rdp"] is untested.<br> Just remove the tools you want to skip from the NanoClass/config.yaml (see also the NanoClass documentation here: https://ejongepier.github.io/NanoClass/) Never use this data base in combination with the NanoClass snakemake -F parameter or this BOLD CO1 database will be overwriten by the default 16S SILVA database. ==========================================<br> DESCRIPTION<br> ========================================== BOLD CO1 database (last) downloaded on 20210420 and reformatted for use in QIIME2 and NanoClass.<br> To clean-up BOLD CO1 db these steps were taken (step 7 to 11 were repeated for each of the 3 primers):<br> - remove identical duplicates [3597874]<br> - drop seqs with non-IUPAC characters [3597839]<br> - remove leading and trailing ambiguous bases [3597839]<br> - remove low quality reads<br> - remove reads with homopolymer runs<br> - filter by length<br> - extract fragments between primer sequences [mtD:112450; CI:121391; LCO-HCO:65307]<br> - dereplicate / cluster [mtD:55075; CI:46470; LCO-HCO:24835]<br> - remove uninformative taxonomic labels [mtD:55073; CI:46466; LCO-HCO:24832]<br> - reformat db for use in NanoClass<br> - train classifier based on fragments ==========================================<br> HOW TO USE THESE DBS<br> ========================================== Use in NanoClass: Unzip the database and copy the reference taxonomy and (unzipped) reference sequences to the NanoClass/db/common directory, like so: $ cp mtD/bold-v20210421-taxonomy-mtD.tsv /path/to/NanoClass/db/common/ref-taxonomy.txt<br> $ gzip -d -c mtD/bold-v20210421-frags-mtD.fa.gz &gt; /path/to/NanoClass/db/common/ref-seqs.fna Something similar can be done for the other two primers (CI or LCO-HCO). Only these three primers are supported at this point. Next, create an (empty) ref-seqs.aln file just to prevent NanoClass from automatically downloading the default 16S SILVA database, which would overwrite the BOLD db you just copied into NanoClass/db/common. $ touch /path/to/NanoClass/db/common/ref-seqs.aln Finally, you need to make a change to the NanoClass/Snakefile (i.e change first line into the second). optrules.extend(["plots/precision.pdf"] if len(config["methods"]) &gt; 2 else [])<br> optrules.extend(["plots/precision.pdf"] if len(config["methods"]) &gt; 200 else []) This will disable the computation of precision plots by NanoClass as this is not supported in combination with the custom BOLD CO1 databases. Also mind that you need to change the nanofilt minlen and maxlen in the NanoClass/config.yaml to capture the appropriate fragment length for your primer. For the mtD primer I used minlen 600 and maxlen 900 for testing. <br> Use in QIIME2: You can use the trained classifier directly in QIIME2, like so: $ qiime feature-classifier classify-sklearn \<br> --i-classifier mtD/bold-v20210421-classifier-mtD.qza \<br> --i-reads &lt;your-reprseqs&gt;.qza \<br> --o-classification &lt;your-classification&gt;.qza \<br> --verbose Something similar can be done for the other two primers (CI or LCO-HCO). Only these three primers are supported at this point.<br> The classifiers have only been tested with with the sklearn algorithm.<br>