Inspect the output
Finding your way around
By default, Maker will write the output of its different analyses into a folder named:
<name_of_genome_fasta>.maker.output
In our case:
genome.maker.output
Within the main output directory, Maker keeps a copy of the config files, a database (here: 4.db), directories for the blast databases created from your evidence data and a file called genome_master_datastore_index.log.
Out of these files, only the genome_master_datastore_index is really interesting to us. It includes a log of all the contigs included in the genome fasta file - together with their processing status (ideally: FINISHED) and the location of the output files. Since Maker can technically run in parallel on a large number of contigs, it creates separate folders for each of these input data. For larger genomes, this can generate a very deep and confusing folder tree. The genome_master_datastore_index.log helps you make sense of it:
This meens the sequence chr4 was started - and finished, with all data (annotation, protein predictions etc) written to the subfolder genome_datastore/27/AC/chr4/.
If you look into that folder, you will find the finished Maker annotation for this contig.
* only if an abinitio tool has been activated
The main annotation file is ‘chr4.gff’ - including both the finished gene models and all the raw compute data. The other files include fasta files for the different sequence features that have been annotated - based on ab-initio predictions through augustus as well as on the finished gene models. The folder ‘theVoid’ include all the raw computations that Maker has performed to synthesize the evidence into gene models.