Skip to content
New issue

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

DRAM2 does not handle SLURM submissions using non-default accounts (includes work-around) #397

Open
LSHillary opened this issue Feb 6, 2025 · 0 comments

Comments

@LSHillary
Copy link

I've been testing DRAM 2 on my university's HPC cluster but SLURM was not submitting individual jobs through the desired account, and resorting to the default account, even if specifying the alternative account in the nextflow.config file. I fixed it by editing the singularity_slurm.config file to include --account=<INSERT ACCOUNT NAME> after each instance of clusterOptions = (params.slurm_node ? "--nodelist=${params.slurm_node} " : "") + "--job-name=DRAM-..."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant