We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
We have installed gtdbtk on our servers but the users do not necessarily know were are the gtdbtk reference data and the mash index.
For the gtdbtk reference data, we can set and export the environment variable GTDBTK_DATA_PATH. Yet, it doesn't fix the issue for the mash index.
What about adding another environment variable for the mash index?
The text was updated successfully, but these errors were encountered:
Hi Florian,
FYI, we are currently in the process of removing Mash for the GTDB pipeline and migrate to only skani in the future.
This change is currently being tested, and if the results are conclusive, Mash will no longer be included in the next releases of GTDB-Tk.
Cheers, Pierre
Sorry, something went wrong.
Hi Pierre,
I guess the issue would be the same with skani if gtdbtk uses a database of pre-sketched genomes?
Hi Florian, This is correct :) We'll work on making this feature available in the next release of GTDB-Tk.
No branches or pull requests
Hi,
We have installed gtdbtk on our servers but the users do not necessarily know were are the gtdbtk reference data and the mash index.
For the gtdbtk reference data, we can set and export the environment variable GTDBTK_DATA_PATH. Yet, it doesn't fix the issue for the mash index.
What about adding another environment variable for the mash index?
The text was updated successfully, but these errors were encountered: