Mapping of dimensions in QML and objectives in Opt4J may be broken

Description

de.uka.ipd.sdq.dsexplore.qml.pcm.reader.PCMDeclarationsReader.translateEvalAspectToObjective()

See
//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.

Environment

None

Activity

Show:
Yves Kirschner
October 22, 2020, 7:46 PM

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.

Yves Kirschner
January 24, 2020, 1:03 PM

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.

Martina Rapp
January 17, 2020, 1:07 PM

This issue is still relevant and should be fixed, reconfirmed with Anne

Cannot Reproduce

Assignee

Yves Kirschner

Reporter

Anne Koziolek

Labels

None

Requirement Category

None

External issue URL

None

Epic Link

Priority

Minor