Builder integration

[ackurth]

Kaveh and I finished the Builder integration.

The machine parameters at compile time (i.e. number of cores to compile on) are hardcoded in the helper.yaml.
We chose this, since otherwise the users would need to configure one additional config file leading to an unnecessary increase of complexity.
If you, however, would prefer to store them externally, this is also possible.

[jasperalbers]

I get the following error when trying to execute the current version:

name="sub_bench_job" not found inside "helpers/helpers.yaml"

I myself produced a similar issue when trying to define multiple substitutesets as is currently done in helpers.yaml. I believe one is only allowed to define one (?).

[ackurth]

Kaveh and I looked into this. We suspect it to be a bug in JUBE. Kaveh will check this tomorrow with the JUBE devlopers. If it turns out to be true, we already have a solution - at the expense of adding one additional helper file - at hand.
If possible, we, however, would try to avoid introducing this new file.

[ackurth]

@jasperalbers, we resolved the problem.
In order to minimize the user interaction upon running jube run /path/to/benchmark.yaml we introduced a --get --silent mode in Builder.
The code for this modification can be found here. Since this changes is not too large, I think it can be merged into the Builder master rather timely.

[jasperalbers]

I am getting the following error:

Cannot evaluate "$vps_per_node*$num_nodes" for parameter "num_vps": invalid syntax (<string>, line 1)

If I comment out the build step the bench step works, so it is a problem in the newly introduced build step.
Have you run this on JURECA-DC before?

[Kaveh01]

I am getting the following error:

Cannot evaluate "$vps_per_node*$num_nodes" for parameter "num_vps": invalid syntax (<string>, line 1)

If I comment out the build step the bench step works, so it is a problem in the newly introduced build step. Have you run this on JURECA-DC before?

For which benchmark?

[jasperalbers]

hpc-benchmark 31

[Kaveh01]

hpc-benchmark 31

Please give it a try.

[jasperalbers]

Very elegant integration of the build step. All my test run successfully now, thanks a lot @ackurth @Kaveh01 @terhorstd! 🎉