Optimization Benchmarking

Release 0.8.7: Alpha-2

17 Jul 2016

Today, version 0.8.7, the “Alpha-2” release of our optimizationBenchmarking.org software suite, was published. Compared to the previous release, several issues have been improved and fixed:

  • A new module, Behavior Modeling, was added. This module tries to represent the runtime behavior of an algorithm by fitting a function to it. This module is in a very early state of development.
  • The grouping of algorithms and instances by their behavior has become more reliable, as we now use several function fitting procedures and pick the best results.
  • The intrinsic parallelism of the processing of our system has been improved. We moved from ForkJoinPool to an own execution engine more suitable for our use cases.
  • Several minor bugs have been fixed.

Like version 0.8.6, our new software release comes in three flavors:

  1. evaluator/GUI
  2. dockerized evaluator/GUI
  3. evaluator/CLI

The GUI is a stand-alone server providing a web-based interface for managing your experimental data, creating meta data, and running the evaluator.

The dockerized version of the GUI comes as a, well, Docker image. This image has all the software requirements pre-installed, including the Java 8 OpenJDK, TeX Live, R, the needed R packages, and ghostscript. Using the evaluator as Docker image requires more disk space, but apart from Docker itself, you don’t need to install anything. This seems to be quite a convenient scenario to me, given that you would otherwise need to install R and several of its packages, TeX Live, and such and such, to fully enjoy all features of our system.

The CLI, i.e., the command line interface, is a only the pure evaluator component to be executed manually. This may make sense when running it as component of another, non-Java process. If you would want to use the software inside your Java program, you can just the libraries directly. If you want to know how to do that, <a href=”mailto:tweise@ustc.edu.cn>contact me</a>.

Anyway, both the GUI and the CLI come as stand-alone jars and you can run them directly via java -jar evaluatorGui.jar (in case of the GUI) and java -jar evaluator.jar in case of the evaluator. In the dockerized GUI version, this is already automatically done for you.

[home] • [status] • [atom feed] • [rss feed]

Contact: Dr.  Thomas Weise, http://www.it-weise.de, tweise@ustc.edu.cn