Closed johnne closed 1 year ago
You may never use a config files with -c
defining params (as you did here), because those params can be overwritten. Use -params-file
instead, this equals using params on the command line, i.e. guarantees that the settings are used by the pipeline. Here is how to do that: https://nf-co.re/ampliseq/2.5.0/usage#setting-parameters-in-a-file
Having said that, this isnt the issue. The issue is:
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
which is not a bug but an incomplete download. Please re-download, auto is fine but manually might be more reliable.
Ok thanks, I don't run nextflow often enough to remember these things and always struggle to find documentation on how to define parameters without passing on the commandline.
I just ran into the same "issue". In my case, I specified an already extracted archive of the GTDB database which was present on our analysis cluster. It makes sense then that tar/gzip complains when attempting to extract it once again.
It doesn't seem to be what you're doing though since you're not specifying anything for the gtdb
database parameter?
To address @alneberg 's problem I'll also add functionality to support directory input of the database :) (then we can close this issue)
Will be supported in https://github.com/nf-core/mag/pull/436
I guess this shoiuld also apply to BUSCO database (i.e., make BUSCO_DB_PREPARATION optional)
I've added gtdb, not yet done for busco as more complicated.
I will close this and make a new issue for busco
Description of the bug
I'm running into an error when running nf-core/mag at prepping the GTDB-TK database. My config file contains the following:
Command used and terminal output
Relevant files
nextflow.log
System information