Mercurial > repos > galaxyp > data_manager_eggnog_mapper_abspath
diff tool-data/eggnog_mapper_db_versioned.loc.sample @ 3:b711f5b6bd44 draft
"planemo upload for repository https://github.com/galaxyproteomics/tools-galaxyp/tree/master/tools/eggnog_mapper/data_manager_eggnog_mapper_abspath commit fd234f7532b34a1b6ced0d3ac53a8f42348e23f7"
author | galaxyp |
---|---|
date | Fri, 19 Feb 2021 18:54:00 +0000 |
parents | |
children | fcb8bdd124f4 |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tool-data/eggnog_mapper_db_versioned.loc.sample Fri Feb 19 18:54:00 2021 +0000 @@ -0,0 +1,22 @@ +#This is a sample file distributed with Galaxy that enables tools +#to use a directory of eggnog_mapper data files. +# +# eggnog-mapper requires the following files to be installed in the data directory: +# https://github.com/jhcepas/eggnog-mapper/blob/master/data/og2level.tsv.gz +# http://eggnog5.embl.de/download/emapperdb-5.0.0/eggnog.db.gz +# A complete diamond database is available from: +# http://eggnog5.embl.de/download/emapperdb-5.0.0/eggnog_proteins.dmnd.gz +# +# The python script download_eggnog_data.py, +# included with eggnog_mapper, can be used to download the files to the correct directory +# +# The near-equivalence of columns "value" and "db" is needed for the tests to work, +# and for the setting of --data_dir to the parent directory of eggnog.db +# The complicated eggNOG database structure makes passing custom HMM databases somewhat tricky. +# See test-data/cached_locally/eggnog_mapper.loc for how this was done with the included test databases +# In all other cases, when the appropriate HMM database (for example, "thaNOG") was downloaded from eggnogdb.embl.de, +# value and db should be the same (in the example, both should be "thaNOG") +# +# +#db_version name path +#5.0 eggnog_5.0 /path/to/directory/that/contains/eggnog.db