Open
Conversation
…ax cpu usage on a hpc via slurm
…nal snp calling, and global cpu resource management on slurm
Collaborator
|
This is great!! Very excited to have the separated MQC outs and I think it's good to reduce the number of jobs for slurm. Such a bummer we can't easily set maximum cpus for slurm in nextflow, but I think what you have is a good call. |
erflynn
approved these changes
Mar 13, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
key modifications to the pipeline:
executor.cpusparameter inconfig/base.configto be able to control maximum allowable number of CPU usage when running underlocalprofile i.e. running the pipeline on a local machine or on a developmental (dev) nodeexecutor.queueSizeparameter inconfig/base.configto be able to control maximum allowable number of jobs to run when running the pipeline on a cluster via slurmmax_cpus_per_jobparameter inconfig/parametersto be able to control maximum allowable number of CPU usage per job when running the pipeline on a cluster via slurmcall_snpsparameter inconfig/parameters.configto be able to control whether or not SNP calling process steps need to be carried out. This was requested by the Genomics core and makes sense since these steps have considerably high computational requirements