Add support for a user config file #65
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If HUMAnN is installed in a directory a user does not have write access
to, this patch allowes the config file to be elsewhere, with the path
set in the environment variable: HUMAnN_CONFIG
for example:
export HUMAnN_CONFIG="/projects/databases/humann.cfg"
Copy the humann.cfg from the install tree to the above path, then
(with this environemtn variable set,) alternate locations for the
databases can be configured. For example:
humann_config --update database_folders nucleotide /projects/databases/chocophlan
humann_config --update database_folders protein /projects/databases/uniref
humann_config --update database_folders utility_mapping /projects/databases/utility_mapping
Tested with HUMAnN versions 3.6 and 3.9
Tony
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
If HUMAnN is installed in a directory a user does not have write access to,
this patch allowes the config file to be elsewhere, with the path set in the
environment variable: HUMAnN_CONFIG
for example:
export HUMAnN_CONFIG="/projects/databases/humann.cfg"Copy the humann.cfg from the install tree to the above path,
then (with this environemtn variable set,) alternate locations for
the databases can be configured.
For example:
Tested with HUMAnN versions 3.6 and 3.9
Tony