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

Threading control #601

Open
choishingwan opened this issue Jan 26, 2024 · 0 comments
Open

Threading control #601

choishingwan opened this issue Jan 26, 2024 · 0 comments
Labels

Comments

@choishingwan
Copy link

Currently, we can supply a variable to control for the number of CPU required. Is it possible such that when we update the number of CPU required, the task do not rerun? For example, if we have the following

task plink_freq{
    input{
         File bed
         File bim
         File fam
         Int threads = 1
   }
    command <<<
        plink --bed ~{bed} --bim ~{bim} --fam ~{fam} --freq --threads ~{threads}
    >>>
   runtime{
     cpu: "~{threads}"
   }
}

When we update the thread number, the task will rerun because it sees one variable (threads) to be different from previous input. Can we use something like ~{runtime.cpu}? I am guessing this is similar to what is proposed in #418 ?

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

No branches or pull requests

2 participants