8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
While trying to run KrakenUniq, I noticed the job was taking forever. Turns out it was using 4 CPU by default.
Tried to overwrite this in a config file as follows:
process { withName: 'KRAKENUNIQ.*' { cpus = 32 memory = 64.GB } }
At run time, it turned out that only the memory requested was correctly updated, not the cpu (from .command.sh):
# Preload the KrakenUniq database into memory. krakenuniq \ \ --db KrakenUniq_MicrobialDB_2023-08-08 \ --preload \ --preload-size 64G \ --threads 4 # Run the KrakenUniq classification on each sample in the batch. while IFS=' ' read -r SEQ PREFIX; do krakenuniq \ --db KrakenUniq_MicrobialDB_2023-08-08 \ --threads 4 \ --report-file "${PREFIX}.krakenuniq.report.txt" \ \ \ \ \ "${SEQ}" done < .inputs.txt
Possibly related to issue #611 ?
No response
The text was updated successfully, but these errors were encountered:
Hi @AnotherSimon could you provide the command used, and any configs you were using?
Sorry, something went wrong.
I ask as the only time that cpus=4 is set for KrakenUniq is for the -profile test, (by default it runs with 12 CPUS, and is confirmed by the release tests results here: https://nf-co.re/taxprofiler/1.2.2/results/taxprofiler/results-80d2fcce1daeb95c69f16832ca253dbaeac8a11e/pipeline_info/?file=execution_report_2025-03-11_08-35-46.html)
cpus=4
-profile test
So it makes me wonder if the test command was accidently left in your command somewhere?
test
No branches or pull requests
Description of the bug
While trying to run KrakenUniq, I noticed the job was taking forever. Turns out it was using 4 CPU by default.
Tried to overwrite this in a config file as follows:
At run time, it turned out that only the memory requested was correctly updated, not the cpu (from .command.sh):
Possibly related to issue #611 ?
Command used and terminal output
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: