slurm parameter errors

[s-meaden]

Description of the bug

Thanks for DRAM v2. I understand it's still in beta development but have had some issues with the slurm parameters.
The docs state the slurm parameters in the config file (nextflow.config) must be strings (and I get an integer error if I don't use quotes, for example --cpu_provision_limit 32). However when I pass the following

Slurm resource requirements
    cpu_provision_limit = "32"
    mem_gb_provision_limit = "128"
    time_hr_provision_limit = "48"

I get the this error:

ERROR ~ No such variable: GB

Do you have any insight into why this error is being thrown? This could well be user error from me- not very familiar with Nextflow!

System information

DRAM version: WrightonLabCSU/dram -r dev
Nextflow version: version 25.10.2
Running on HPC with slurm and a Singularity/Apptainer engine.
OS: Rocky Linux 8.10 (Green Obsidian) - Kernel el8

Command used and terminal output

nextflow run WrightonLabCSU/DRAM -r dev \
--input_fasta test_proviruses/ \
--outdir test_output2 \
--rename \
--annotate \
--anno_dbs "dbcan,kofam,merops,viral,camper,canthyd,fegenie,sulfur,methyl,uniref,pfam,vogdb" \
-profile singularity \
--slurm

Terminal output:

 N E X T F L O W   ~  version 25.10.2

ERROR ~ No such variable: GB

 -- Check '.nextflow.log' file for details

Relevant files

No response

[madeline-scyphers]

Hey, thanks for reporting this bug. It used to need to be a string. Now it needs to be an integer, but it being marked as needing to be a string will fail the validation. I will fix it for the next release. For now, if they are left blank, then they default to huge_cpus_limit, huge_gb_mem_limit, and huge_hr_time_limit. So you can adjust those if needed before the next release hopefully by the end of the week.