eggNOG mapper
Overview
EGGNog-Mapper is a tool for fast functional annotation of novel sequences. It uses precomputed orthologous groups and phylogenies from the eggNOG database (http://eggnog5.embl.de) to transfer functional information from fine-grained orthologs only.
Version 2.0.5 is installed on the CSF.
Restrictions on use
If you use the software please cite the two references given at: https://github.com/eggnogdb/eggnog-mapper/wiki/eggNOG-mapper-v2.0.2-v2.0.6#Citation
Please note that the eggnog databases have been downloaded and installed centrally. You do not need your own copy. The modulefile (see below) will set up the path to these databases.
Set up procedure
We now recommend loading modulefiles within your jobscript so that you have a full record of how the job was run. See the example jobscript below for how to do this. Alternatively, you may load modulefiles on the login node and let the job inherit these settings.
Load one of the following modulefiles:
module load apps/python/eggnog-mapper/2.0.5
You may run the following command on the login node to get help with the command-line flags:
emapper.py --help
Running the application
Please do not run eggnog-mapper on the login node. Jobs should be submitted to the compute nodes via batch.
Note that a serial (one-core) job may not give you enough memory to run eggnog-mappy (it gives you 4-5GB). The software is multi-core capable so we recommend using a parallel job (see below) which will speed up the software and give you more memory to work with (4-5GB per core).
Serial batch job submission
Note that a serial (one-core) job may not give you enough memory to run eggnog-mappy (it gives you 4-5GB). The software is multi-core capable so we recommend using a parallel job (see below) which will speed up the software and give you more memory to work with (4-5GB per core).
Create a batch submission script (which will load the modulefile in the jobscript), for example:
#!/bin/bash --login #$ -cwd # Job will run from the current directory # NO -V line - we load modulefiles in the jobscript # Load the version you require module load apps/python/eggnog-mapper/2.0.5 emapper.py --cpu $NSLOTS --scratch_dir ~/scratch -i FASTA_FILE -o resultsname # # Add --output_dir dirname to write results to a directory other than the current directory
Submit the jobscript using:
qsub scriptname
where scriptname is the name of your jobscript.
Parallel batch job submission
Create a batch submission script (which will load the modulefile in the jobscript), for example:
#!/bin/bash --login #$ -cwd # Job will run from the current directory #$ -pe smp.pe 8 # Number of cores (can be 2--32) ### You may wish to add a high-memory flag but this may limit the number of cores ### #$ -l mem512 # Load the version you require module load apps/python/eggnog-mapper/2.0.5 emapper.py --cpu $NSLOTS --scratch_dir ~/scratch -i FASTA_FILE -o resultsname # # Add --output_dir dirname to write results to a directory other than the current directory
Submit the jobscript using:
qsub scriptname
where scriptname is the name of your jobscript.
Further info
Updates
None.