7. Usage

Mikado is composed of four different programs (configure, prepare, serialise, pick) which have to be executed serially to go from an ensemble of different assemblies to the final dataset. In addition to these core programs, Mikado provides a utility to compare annotations, similarly to CuffCompare and ParsEval (compare), and various other minor utilities to perform operations such as extracting regions from a GFF, convert between different gene annotation formats, etc.

7.1. Mikado pipeline stages

The Mikado pipeline is composed of four different stages, that have to be executed serially:

  1. Mikado configure, for creating the configuration file that will be used throughout the run.
  2. Mikado prepare, for collapsing the input assemblies into a single file. After this step, it is possible to perform additional analyses on the data such as TransDecoder (highly recommended), Portcullis, or BLAST.
  3. Mikado serialise, to gather all external data into a single database.
  4. Mikado pick, to perform the actual selection of the best transcripts in each locus.

7.2. Compare

Mikado also comprises a dedicated utility, Mikado compare, to assess the similarity between two annotations.

7.3. Daijin

Mikado provides a pipeline manager, Daijin, to align and assemble transcripts with multiple methods and subsequently choose the best assemblies among the options. The pipeline is implemented using Snakemake [Snake].

7.4. Miscellaneous utilities

Finally, Mikado provides some dedicated utilities to perform common tasks.

  • Some of the utilities are integral to the Mikado suite and can be accessed as subcommands of Mikado. These utilities comprise programs to calculate annotation statistics, retrieve or exclude specific loci from a file, etc.
  • Other utilities are provided as stand-alone scripts; while some of them directly depend on the Mikado library, this is not necessarily the case for them all.