Mapping of dimensions in QML and objectives in Opt4J may be broken
//FIXME: the mapping of dimensions in QML and objectives in Opt4J is broken: the quality attribute, such as dsexplore.performance is used here as a String, which means that two dimensions throughput and response time cannot be distinguished here.
It could not be confirmed that this is really a problem. In a quick check in one test case both values for throughput and response time were optimized independently.
It has to be confirmed if this is really a problem, because the original developer (Qais) is already finished. In agreement with Anne, it has to be checked first, whether both values are optimized for throughput and response time only according to one value for performance.
This issue is still relevant and should be fixed, reconfirmed with Anne