You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When installing interproscan via conda it is currently necessary to separately download the databases and add them to the interproscan folder (see post-link.sh).
While this is generally working many users will probably not noticing that this is required.
In addition there are cases where this procedure is not even applicable.
Especially when including the conda-package in a snakemake workflow.
As snakemake is maintaining conda-environments on its own it is not possible to include the database files in the environment.
This could be easily solved in two ways by allowing to:
define a custom interproscan.properties-file via a command line parameter
set the only the path of the data directory by a parameter
The text was updated successfully, but these errors were encountered:
👍 that would be quite useful
Currently in the Galaxy tool we use this ugly trick = create a .interproscan-5/interproscan.properties file in a job specific HOME dir.
When installing interproscan via conda it is currently necessary to separately download the databases and add them to the interproscan folder (see post-link.sh).
While this is generally working many users will probably not noticing that this is required.
In addition there are cases where this procedure is not even applicable.
Especially when including the conda-package in a snakemake workflow.
As snakemake is maintaining conda-environments on its own it is not possible to include the database files in the environment.
This could be easily solved in two ways by allowing to:
interproscan.properties
-file via a command line parameterThe text was updated successfully, but these errors were encountered: