Documentation/Modules/ClassesModules - Versionsgeschichte

Dirk am 18. März 2013 um 21:08 Uhr

2013-03-18T21:08:37Z

Dirk: /* Need for Classes */

2013-03-18T21:08:21Z

‎Need for Classes

Dirk: Created page with "== Need for Classes == `Modules` are connected. The information passed between these `Modules` may be a class of type * `Solution`s in the cas..."

2013-03-18T21:07:47Z

Created page with "== Need for Classes == <code>Modules</code> are connected. The information passed between these <code>Modules</code> may be a class of type * <code>Solution</code>s in the cas..."

Neue Seite

== Need for Classes ==

<code>Modules</code> are connected. The information passed between these <code>Modules</code> may be a class of type

* <code>Solution</code>s in the case of an optimization or
* <code>Data</code> in the case of learning

Often, <code>Modules</code> look similar, and someone writing a new <code>Module</code> doesn't want to implement all interface methods by hand.

For these cases, we wrote the abstract classes

* <code>Optimizer</code>s in the case of an optimization algorithm
* <code>Problem</code>s in the case of an optimization problem
* <code>Learner</code>s in the case of a learning algorithm

These classes already implement most of the necessary methods. A writer of an '''optimizer''' just has to implement the algorithm itself and no other details such as checking or connecting.

Similarly, a writer of a '''problem''' just has to implement the <code>evaluate(...)</code> method of the <code>Problem</code> class.

In a '''learner''', the method to override is <code>run()</code> . It executes the learning algorithm.

← Nächstältere Version		Version vom 18. März 2013, 21:08 Uhr
Zeile 9:		Zeile 9:

	For these cases, we wrote the abstract classes		For these cases, we wrote the abstract classes
−

	* <code>Optimizer</code>s in the case of an optimization algorithm		* <code>Optimizer</code>s in the case of an optimization algorithm

@@ Zeile 3: / Zeile 3: @@
 <code>Modules</code> are connected. The information passed between these <code>Modules</code> may be a class of type
- * <code>Solution</code>s in the case of an optimization or
+* <code>Solution</code>s in the case of an optimization or
- * <code>Data</code> in the case of learning
+* <code>Data</code> in the case of learning
 Often, <code>Modules</code> look similar, and someone writing a new <code>Module</code> doesn't want to implement all interface methods by hand.
@@ Zeile 11: / Zeile 11: @@
- * <code>Optimizer</code>s in the case of an optimization algorithm
+* <code>Optimizer</code>s in the case of an optimization algorithm
- * <code>Problem</code>s in the case of an optimization problem
+* <code>Problem</code>s in the case of an optimization problem
- * <code>Learner</code>s in the case of a learning algorithm
+* <code>Learner</code>s in the case of a learning algorithm
 These classes already implement most of the necessary methods. A writer of an '''optimizer''' just has to implement the algorithm itself and no other details such as checking or connecting.

Documentation/Modules/ClassesModules - Versionsgeschichte

Dirk am 18. März 2013 um 21:08 Uhr

Dirk: /* Need for Classes */

Dirk: Created page with "== Need for Classes == Modules are connected. The information passed between these Modules may be a class of type * Solutions in the cas..."

Dirk: Created page with "== Need for Classes == `Modules` are connected. The information passed between these `Modules` may be a class of type * `Solution`s in the cas..."