From 66f0401e3973b760c16af12727c0daf2f23b948e Mon Sep 17 00:00:00 2001 From: mglass Date: Mon, 21 Oct 2024 12:10:26 +0200 Subject: [PATCH] changed part6 to reflect the provided optimization-config file --- opendse-tutorial/src/main/tutorial/part6.xhtml | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/opendse-tutorial/src/main/tutorial/part6.xhtml b/opendse-tutorial/src/main/tutorial/part6.xhtml index d92c3fcc..55ddd211 100644 --- a/opendse-tutorial/src/main/tutorial/part6.xhtml +++ b/opendse-tutorial/src/main/tutorial/part6.xhtml @@ -15,12 +15,15 @@

For each specification, an optimization can be carried out. - The optimization can be started by running the main method of the Opt4J class:

+ The optimization can be started by running the main method of the Opt4J class or by simply evoking the run task via gradle:

+ 
opendse> ./gradlew run
Implementation -

The optimization has to be properly configured by selecting the modules as illustrated. - Additionally, it is necessary to select an input file which we set to this file. - We optimize a single objective which are the costs. +

The optimization has to be properly configured by selecting modules for your input specification, the preferred optimizer, as well as design objectives as illustrated exemplary in the figure. + For convenience, we provide a sample optimization-config.xml in

+

./opendse-tutorial/optimization-config.xml

+

that can be loaded via the Load button in the Opt4J configurator. + In this example, we optimize a single objective which are the costs. It is possible to implement any kind of evaluator, including non-linear objectives. Furthermore, it is possible to use external evaluators, i.e., programs that receive the respective implementation as XML and return their result as XML.