REL-2.7.1

• Added: GitLab-CI tests for make commands.
• Added: jube continue test for tagging example.
• Fixed: Only in the case of jube run, check that there is a tag attribute description for tags that are not used in the input file.
• Fixed: Glossar and jube help.

REL-2.7.0

• Added: New <tags> tag, which includes the <tag> tag to write a description for each tag specified in the input file.
• Added: New command jube tag to print out the tag description of a given input file or benchmark directory.
• Added: A new operator ^ (exclusive disjunction (xor)) for the tag attribute and <check_tags>.
• Added: New primekey attribute for the key-tag of the database to define whether this key is a primary key of the database or not. Can be set to true or false (default: false).
• Added: New environment variable JUBE_VERBOSE to set the verbosity level.
• Added: Warning when the current verbosity level from the command line or environment variable is out of range.
• Added: New environment variable JUBE_BENCHMARK_OUTPATH to set the benchmark outpath.
• Added: New command line option --outpath of jube run to specify the benchmark outpath.
• Changed: The jube info command now also shows information about all sets, steps, analyser and result from the configuration.xml.
• Changed: The outpath attribute of the <benchmark> tag no longer needs to be specified in the input file if either the command line option --outpath is set or the new environment variable JUBE_BENCHMARK_OUTPATH is used. The command line option overrides the environment variable, which in turn overrides the attribute in the input file.
• Changed: The modified convert type warning is only logged to the analyse.log file and no longer printed to the console output.
• Changed: If the title attribute of a <database> <key> is set, then this title is used as the name of the database column instead of the parameter or pattern name.
• Changed: The <check_tags> tag is now a subelement of the new <tags> tag.
• Changed: Changed the name of the source directory from jube2 to jube and adapted the code to the name change. The links to the documentation on the websites have also been adjusted accordingly.
• Deprecated: The primekeys attribute of the <database> is no longer supported. Use the new primekey attribute of the <database> <key> instead.
• Deprecated: <check_tags> will no longer be supported on a global level. Instead, it should be specified in the <tags> tag.
• Removed: Comma character (,) is no longer supported in <check_tags> and the tag attribute. Instead use |, ^ + and !.
• Fixed: Allow YAML scripts to include a list of nested parametersets with !include.
• Fixed: Allow YAML scripts to use the tag attribute in the <path> of the <include-path>-tag.

REL-2.6.2

• Added: CONTRIBUTING.md file
• Added: New parameter named jobname in parameterset systemParameter of file platform/slurm/platform.xml to modify the value of the --job-name argument in submit.job. During substitution in executesub, quotes are added around the value of jobname.
• Added: Test to verify that a step with a do operation that contains a done_file has been successfully executed.
• Added: CODE_OF_CONDUCT.md file
• Added: JUBE logo in svg and eps format
• Fixed: Resolved deprecation warnings
• Fixed: Parameters of a dependent step with an update_mode step are updated when a jube continue is executed.
• Fixed: Allow YAML and XML scripts to include paths per include in include-path.
• Fixed: Use correct continue log file for parallel step execution.
• Deprecated: Comma character (,) will not be supported anymore in tag attributes. Instead use |, + and !.
• Changed: The unit of a parameter or pattern will also be displayed in the results output when a title is specified.
• Changed: Redesign of the README.md file
• Changed: Colors on website

REL-2.6.1

• Added: CITATION.cff file
• Added: New argument -w for command line option jube info to print information about the given workpackage.
• Fixed: Overwrite the sub with the same source, so that the substitution with init_with will work again.
• Changed: The substitute_tests has been adapted so that the tests fail when the bug fixed in this release occurs.

REL-2.6.0

• Added: New option <check_tags>, which allows you to specify tags that must be set for the script to run.
• Added: New optional mode attribute to the sub-tag, allowing regex substitution as an alternative to text-based substitution. The latter remains the default.
• Added: The jube result command line call has been extended by the options --select and --exclude to show and hide selected result columns.
• Added: New command line option jube output to print out the path and the contents of the files stdout and stderr.
• Added: A new unit attribute to parameter, which has the same function as the unit attribute of pattern.
• Added: New jube variable $jube_wp_status which contains the status of the current workpackage at the time the variable is evaluated.
• Added: New YAML schema file.
• Added: Missing database-tag to dtd, rnc and xsd schema files. (Issue #1 on GitHub)
• Added: A validity check by use of the pip package ruamel.yaml is introduced. This package is used if it is installed. Otherwise, there will be no validity check for yaml files.
• Fixed: The include-path for YAML scripts and added an usage example to the advanced tutorial. (Issue #2 on GitHub)
• Fixed: export of an empty parameter. (Issue #3 on GitHub)
• Fixed: Backward compatibility for floating number value definitions of parameters of type int was restored such that only warning messages are printed in this case.
• Fixed: Typos and bugs in the glossary and the help message.
• Changed: The files_and_sub, parallel_workpackages, result_creation, result_database and tagging example has been updated.
• Changed: The jube complete help output was debugged.
• Changed: The tests for the examples have been completely rewritten to avoid using run.log files.
• Changed: Improved CI: separated tests and automatic tasks for releases.

REL-2.5.1

• The default behaviour of replacing two parameters with different options without throwing an error was restored.
• The testing suite was extended.
• The schema files were corrected such that they contain the duplicate option.

REL-2.5.0

• Several independent workpackages within a step can be executed by multiple processes in parallel by stating procs=#number_of_parallel_processes# within the step tag. An example and a documentation entry was added.
• A result database can be produced by use of the database tag. An example and a documentation entry was added.
• python2-support was removed.
• A couple of unittests were added which now include the testing of most of the examples.
• Sample run.log of most examples were added to tests/examples_output.
• Some yaml example scripts were corrected.
• The MANIFEST file was removed.
• A typo in the error message was fixed.
• Fix result command documentation.
• A wrong result entry in the glossary was fixed.
• A bug for the usage of a newline separator within yaml scripts is resolved.
• A feature to create a do_log file for every workpackage of a step is integrated. The do_log file contains the whole environment while execution, the execution shell, the change of current work directories, comments if a directive was executed in a shared fashion and the do directives of the steps.
• The execution cancels now, when a parameter is of type int or float and the parameter value has not the form of a int or float correspondingly.
• The FAQ documentation was extended with yaml examples.
• The option duplicate for parametersets and parameters was introduced.

REL-2.5.0rc1

• Several independent workpackages within a step can be executed by multiple processes in parallel by stating procs=#number_of_parallel_processes# within the step tag. An example and a documentation entry was added.
• A result database can be produced by use of the database tag. An example and a documentation entry was added.
• python2-support was removed.
• A couple of unittests were added which now include the testing of most of the examples.
• Sample run.log of most examples were added to tests/examples_output.
• Some yaml example scripts were corrected.
• The MANIFEST file was removed.
• A typo in the error message was fixed.
• Fix result command documentation.
• A wrong result entry in the glossary was fixed.
• A bug for the usage of a newline separator within yaml scripts is resolved.
• A feature to create a do_log file for every workpackage of a step is integrated. The do_log file contains the whole environment while execution, the execution shell, the change of current work directories, comments if a directive was executed in a shared fashion and the do directives of the steps.
• The execution cancels now, when a parameter is of type int or float and the parameter value has not the form of a int or float correspondingly.
• The FAQ documentation was extended with yaml examples.

2.4.3

• Fixes a bug related to <include> and init-with combinations.
• JUBE_EXEC_SHELL is now also taken into account during parameter evaluation.
• jube status now also returns ERROR state.
• Fixes a bug of using $$ in shell commands.
• Updates SLURM gres default value in platform files.
• Fixes a bug of having a list of benchmarks in YAML format.

2.4.2

• JUBE will raise an error if an changed work_dir contains unknown variables.
• A bug was solved which enabled dotall="true" by default for all pattern, which can make those costly to evaluate.
• Fixes a bug in result data processing.
• Fixes a bug in YAML input format if benchmark key is not used.
• A empty value in YAML input format will now be treated liek an empty String not as a None value.
• Avoid crash due to overflow error for huge pattern values.
• Fixes a bug, which blocked include blocks to include other include blocks.
• setup.py now moves all additional non-code data to .../share/jube, which allows better utilization of pip based installation