[ ] Check if the program run in the command{} block has an argument for CPUs or threads.
[ ] If argument is for CPUs then the CPU input variable should be passed to the command{}~{cpus} variable and to a runtime{} as a variable ~{cpu}. Currently, most of the tasks have an integer as in the runtime argument for cpus rather than a variable being passed. In other words, the runtime{} cpu argument should match what is requested in the input{} and passed to command{}~{cpus} variable.
[ ] If the program has an argument for threads than a line should be added within the command{} block to create a new variable ~{threads} that is 2X the requested ~{cpu} in the input{} and pass this new ~{threads} variable to the program rather than ~{cpu} . As with the point above add ~{cpu} to the runtime{} cpu argument to make sure what is requested in the input{} is passed to the runtime{} cpu argument.
For each task that has CPUs as an input:
command{}block has an argument forCPUsorthreads.command{}~{cpus}variable and to aruntime{}as a variable~{cpu}. Currently, most of the tasks have an integer as in the runtime argument for cpus rather than a variable being passed. In other words, theruntime{}cpu argument should match what is requested in theinput{}and passed tocommand{}~{cpus}variable.command{}block to create a new variable~{threads}that is 2X the requested~{cpu}in theinput{}and pass this new~{threads}variable to the program rather than~{cpu}. As with the point above add~{cpu}to theruntime{}cpu argument to make sure what is requested in theinput{}is passed to theruntime{}cpu argument.Comment when a task has been checked and edited.