From a27fa567f2e3f83f07403ae7c39cf7ee4f9e7217 Mon Sep 17 00:00:00 2001 From: Pariksheet Nanda Date: Wed, 8 May 2019 11:29:35 -0400 Subject: [PATCH] DOC: Clarify how example 3 uses the input parameters --- README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 03e76a1..e8bbae8 100644 --- a/README.md +++ b/README.md @@ -128,10 +128,11 @@ input parameters. This example is nearly the same as the previous example, but instead of using the the task ID as the input, it uses a long list of record IDs. The record ID is read by the program to find the corresponding -input parameters, and saves the result. +input parameters, the program calculates the result from the +parameters and saves the result in a directory. -Results are saved into a directory and, once all records are -completed, the results are aggregated into a single results file. +Once all records are completed, the results from the directory are +aggregated into a single results file. GNU Parallel automatically feeds record IDs to task workers as the task workers complete records and become available. @@ -139,7 +140,7 @@ task workers complete records and become available. ```sh # From the command-line cd ~/parallel-slurm/examples -rm -f joblog submit.out +rm -rf joblog submit.out results/ results.csv for i in {1..5}; do sbatch 03-submit-param-sweep.slurm; done touch submit.out && tail -f submit.out # Hit Ctrl+C to exit