Package org.moeaframework.problem.CEC2009

Class UF9

java.lang.Object

org.moeaframework.problem.AbstractProblem

org.moeaframework.problem.CEC2009.UF9

All Implemented Interfaces:

AutoCloseable, Problem

public class UF9
extends AbstractProblem

The unconstrained UF9 test problem from the CEC 2009 special session and competition.

Field Summary

Fields inherited from class org.moeaframework.problem.AbstractProblem

numberOfConstraints, numberOfObjectives, numberOfVariables

Constructor Summary

Constructors

Constructor	Description
UF9()	Constructs a UF9 test problem with 30 decision variables.
UF9(int numberOfVariables)	Constructs a UF9 test problem with the specified number of decision variables.

Method Summary

Modifier and Type	Method	Description
void	evaluate(Solution solution)	Evaluates the solution, updating the solution's objectives in place.
Solution	newSolution()	Returns a new solution for this problem.

Methods inherited from class org.moeaframework.problem.AbstractProblem

close, getName, getNumberOfConstraints, getNumberOfObjectives, getNumberOfVariables

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface org.moeaframework.core.Problem

isType

Constructor Details

UF9

public UF9()

Constructs a UF9 test problem with 30 decision variables.

UF9

public UF9(int numberOfVariables)

Constructs a UF9 test problem with the specified number of decision variables.

Parameters:

numberOfVariables - the number of decision variables

Method Details

evaluate

public void evaluate(Solution solution)

Description copied from interface: Problem

Evaluates the solution, updating the solution's objectives in place. Algorithms must explicitly call this method when appropriate to evaluate new solutions or reevaluate modified solutions.

Parameters:

solution - the solution to be evaluated

newSolution

public Solution newSolution()

Description copied from interface: Problem

Returns a new solution for this problem. Implementations must initialize the variables so that the valid range of values is defined, but typically leave the actual value at a default or undefined state.

Returns:

a new solution for this problem