Frequently Asked Questions
This section covers frequently asked question on how to run or configure the JUBE environment.
1. When I call JUBE with the parameters -update and -result I don't get the expected results printed. Why?
Each individual analysis pattern has to have at least one entry for the $walltime variable. If the variable is not set after output analysis, no report on this run will be generated. The reason for an unset walltime variable can be i) the job did not run yet, ii) the job ended prematurely and did not output the appropriate line in the output, or iii) the regular expression defined for the walltime variable does not match correctly.
First address for troubleshooting is to check the output of stdout and stderr in the logs/ directory.
2. I would like to run an application with a different numbers of cores than what is pre-configured in the official benchmark files. In addition to changing the task tag in the top-level benchmark file, what other modifications I need to make?
Detailed information on the input data for an individual benchmark is given in its README. In general the JUBE environment is capable of generating input data tailored to the task description, if the application supports this. This means no other modifications need to be done, while the tasks stay in the supported range.
DEISA Benchmark Suite
1. Where can I get CPMD, IFS, NAMD, and Fenfloss sources and how can I import them into the JUBE environment?
The benchmarking harness for those applications is supplied with the benchmark suite. The README file of the corresponding application will give detailed information on how and where to obtain the source code. The harness itself is configured in a way that you only have to place the sources into the src/ directory of the application's benchmarking harness.
2. The application benchmarks are configured up to 4096 processes. What do I have to do, to use more than that?
4096 processes is the maximum number of processes the DEISA Benchmark Suite has been tested with. Using more processes will not work on applications where static input data for a given number of processes is needed. Check the prepare.xml to see how the input data is prepared for each run, to set it up manually.