A WORKFLOW-type anvi’o artifact. This artifact is typically generated, used, and/or exported by anvi’o (and not provided by the user)..
🔙 To the main page of anvi’o programs and artifacts.
Required or used by
There are no anvi’o tools that use or require this artifact directly, which means it is most likely an end-product for the user.
The workflow can run the following programs in order.
- Illumina-utils, for merging paired-end reads and quality control
- anvi-script-reformat-fasta, for making FASTA deflines anvio-compliant
- anvi-trnaseq, for predicting tRNA sequences, structures, and modification sites in each sample
- anvi-merge-trnaseq, for predicting tRNA seed sequences and their modification sites from the set of samples
- anvi-run-trna-taxonomy, for assigning taxonomy to tRNA seeds
- anvi-tabulate-trnaseq, for generating tables of seed and modification information that are easily manipulated
The tRNA-seq workflow requires two files to run: a json-formatted config file and samples-txt. Generate the default config file, here called
config.json, with the following command.
anvi-run-workflow -w trnaseq --get-default-config config.json
Different “rules,” or steps, of the workflow can be turned on and off as needed in the config file. The workflow can be restarted at intermediate rules without rerunning prior rules that have already completed.
samples-txt will contain a list of FASTQ or FASTA files and associated information on each library. FASTQ files contain unmerged paired-end tRNA-seq reads. Reads are merged in the workflow by Illumina-utils. FASTA files contain merged reads, and the initial read-merging steps in the workflow are skipped.
Here is an example tRNA-seq samples file with FASTQ inputs.
The treatment column is optional. The treatment indicates a chemical application, such as demethylase, and can be used to have a bearing on seed sequence determination in anvi-merge-trnaseq. In the absence of a treatment column, all samples are assigned the same treatment, which can be specified in the
anvi_trnaseq section of the workflow config file and defaults to
Read 1 and 2 prefix columns are also optional. These represent sequences that Illumina-utils should identify and trim from the start of the read. In the example, the read 1 prefix is a unique molecular identifier (UMI) of 6 random nucleotides, and the read 2 prefix is a sample barcode. Illumina-utils will discard the paired-end read if the prefix is not found. In the example, the read 1 UMI will always be found, but the read 2 barcode must match exactly.
Here is an equivalent tRNA-seq samples file with FASTA inputs.
Note that barcodes and other sequence prefixes should already be trimmed from FASTA sequences.
Edit this file to update this information.