how to avoid to rerun?

I am new to cromwell.

Now I am test to run the following code on my local machine like this:

java -jar -Dconfig.file=cromwell/application.conf cromwell/cromwell-36.jar run cromwell/wdl/wf.wdl --inputs cromwell/wdl/wf.json

I succeed running wf.wdl and get the output, but each time when I rerun this code, this code will run again.

Does anyone know how to set in application.conf to avoid this.
I set up call-caching.enabled=true in my application.conf, but it seems it does not work.

Thank you,
Aimin

My cromwell/application.conf looks like the following:

include required(classpath("application"))

Note: If you spot a mistake in this configuration sample, please let us know by making an issue at:

https://github.com/broadinstitute/cromwell/issues

call-caching {
enabled = true
}

{

"write_to_cache": true,

"read_from_cache": true

}

backend {
default = "Local"
providers {
Local {
actor-factory = "cromwell.backend.impl.sfs.config.ConfigBackendLifecycleActorFactory"
config {
run-in-background = true
runtime-attributes = "String? docker Int? max_runtime = 2"
submit = "/bin/bash ${script}"
submit-docker = "docker run --rm -v ${cwd}:${docker_cwd} -i ${docker} /bin/bash < ${script}"

    # Root directory where Cromwell writes job results. This directory must be
    # visible and writeable by the Cromwell process as well as the jobs that Cromwell
    # launches.
    root: "cromwell-executions"

    filesystems {
      local {
        localization: [
          "soft-link", "hard-link", "copy"
        ]

        caching {
          duplication-strategy: [
            "soft-link"
          ]


          # Possible values: file, path
          # "file" will compute an md5 hash of the file content.
          # "path" will compute an md5 hash of the file path. This strategy will only be effective if the duplication-strategy (above) is set to "soft-link",
          # in order to allow for the original file path to be hashed.
          hashing-strategy: "path"

          # When true, will check if a sibling file with the same name and the .md5 extension exists, and if it does, use the content of this file as a hash.
          # If false or the md5 does not exist, will proceed with the above-defined hashing strategy.
          check-sibling-md5: true
        }
      }
    }
  }
}

}
}

database {

db.url = "jdbc:mysql://mysql-db/cromwell_db?useSSL=false&rewriteBatchedStatements=true"

db.user = "cromwell"

db.password = "cromwell"

db.driver = "com.mysql.jdbc.Driver"

profile = "slick.jdbc.MySQLProfile$"

db.connectionTimeout = 15000

}

Tagged:

Answers

Sign In or Register to comment.