Mercurial > repos > galaxyp > eggnog_mapper
comparison README @ 13:844fa988236b draft
planemo upload for repository https://github.com/galaxyproteomics/tools-galaxyp/tree/master/tools/eggnog_mapper/eggnog_mapper commit 468bd31b8858adbba2854f118e4cbe31f4cd68cb
author | galaxyp |
---|---|
date | Mon, 04 Sep 2023 12:47:09 +0000 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
12:9d1fbff733cf | 13:844fa988236b |
---|---|
1 This folder contains three tools: | |
2 | |
3 1. eggnogg_mapper: which runs the search and annotation phase in a single tool | |
4 2. eggnogg_mapper_search: which implements the search phase | |
5 3. eggnogg_mapper_annotate: which implements the annotation phase | |
6 | |
7 While the search phase of eggnog_mapper is very CPU intense and is efficient | |
8 also for a larger number of threads, the annotation phase is very IO intensive | |
9 and can be very inefficient (depending on the configuration, e.g. if the | |
10 reference data is located on a slow partition). | |
11 | |
12 While for most applications eggnogg_mapper will be sufficient to separate the | |
13 two phases can be more efficient: | |
14 | |
15 - sending eggnogg_mapper_search to a destination using many threads | |
16 - and eggnogg_mapper_annotate to a destination using a small number of threads | |
17 | |
18 Admins can choose to set the environment variable ``EGGNOG_DBMEM=--dbmem`` | |
19 which will copy the complete EggNOG annotation DB into memory which is usually | |
20 much faster than using multiple cores (but needs approx. 37GB of RAM). |