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

Cromwell workflow engine #2

Open
tavareshugo opened this issue Apr 24, 2023 · 0 comments
Open

Cromwell workflow engine #2

tavareshugo opened this issue Apr 24, 2023 · 0 comments

Comments

@tavareshugo
Copy link
Contributor

The Broad Institute workflow engine cromwell can be useful to running GATK workflows (written in WDL language).

Resources for this:

Some attempt to run this on CSD3. I have set the following config file:

backend {
  default = SLURM

  providers {
    SLURM {
      actor-factory = "cromwell.backend.impl.sfs.config.ConfigBackendLifecycleActorFactory"
      config {
        runtime-attributes = """
        Int runtime_minutes = 60
        Int cpus = 8
        Int requested_memory_mb_per_core = 3000
        String queue = "icelake,cclake,cclake-himem,icelake-himem"
        String account = "NAME-SL3-CPU"
        """

        submit = """
            sbatch -J ${job_name} -D ${cwd} -o ${out} -e ${err} -t ${runtime_minutes} -p ${queue} \
            ${"-c " + cpus} \
            --mem-per-cpu ${requested_memory_mb_per_core} \
            --wrap "/bin/bash ${script}"
        """
        kill = "scancel ${job_id}"
        check-alive = "squeue -j ${job_id}"
        job-id-regex = "Submitted batch job (\\d+).*"
      }
    }
  }
}

However, this would always submit the scripts with a fixed number of CPUs and time.
Not sure if this can be changed on a step-by-step basis, based on the workflow somehow (like with Nextflow).

The config file can be used with the pipeline by running it as:

 cromwell -Dconfig.file=csd3.conf run helloworld.wdl
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