What happens
The Runs step prints a product whose factors do not give its own answer.
The parameter settings require 2 runs (1 input resources × 1 parameters).
1 × 1 is 1, not 2. The count 2 is correct — the dataslice held two resources, and two Tapis
jobs were submitted. The 1 input resources label is wrong; it should read 2.
Seen twice at TACC, on two different threads and two different datasets:
- thread
x4gbmq00msmbp9ib — 2 runs (1 input resources × 1 parameters)
- thread
jx8ibyilmsmg1pvt — 2 runs (1 input resources × 1 parameters), dataset
nunap-interview-data, which then submitted 2 executions
A single-resource dataslice prints 1 runs (1 input resources × 1 parameters), which is
consistent. So the count is right and only the printed factor is wrong.
Why it matters
The user reads this line before pressing Send Runs. It is the only warning of how many jobs
are about to go to the cluster. It currently understates the input count.
Found while resolving #92.
What happens
The Runs step prints a product whose factors do not give its own answer.
1 × 1 is 1, not 2. The count
2is correct — the dataslice held two resources, and two Tapisjobs were submitted. The
1 input resourceslabel is wrong; it should read 2.Seen twice at TACC, on two different threads and two different datasets:
x4gbmq00msmbp9ib—2 runs (1 input resources × 1 parameters)jx8ibyilmsmg1pvt—2 runs (1 input resources × 1 parameters), datasetnunap-interview-data, which then submitted 2 executionsA single-resource dataslice prints
1 runs (1 input resources × 1 parameters), which isconsistent. So the count is right and only the printed factor is wrong.
Why it matters
The user reads this line before pressing Send Runs. It is the only warning of how many jobs
are about to go to the cluster. It currently understates the input count.
Found while resolving #92.