evomo.algorithms.telso#
Attributes#
Classes#
Initialize the TELSO population and optimization state. |
Module Contents#
- class evomo.algorithms.telso.TELSO(pop_size: int, n_objs: int, lb: torch.Tensor, ub: torch.Tensor, max_fe: int = 10000, **kwargs)#
Bases:
evox.core.AlgorithmInitialize the TELSO population and optimization state.
- Parameters:
pop_size (int) – Required. Requested number of candidate solutions. Use a positive integer; algorithm-specific minimums and reference-vector sampling are described below.
n_objs (int) – Required. Number of objectives, matching the second dimension of the problem’s objective tensor. Objectives are minimized; this library targets two or more objectives.
lb (torch.Tensor) – Required. Lower decision bounds of shape
(D,), whereDis the number of decision variables. Use floating-point bounds with the same shape, dtype and device asub, andlb <= ubelementwise.ub (torch.Tensor) – Required. Upper decision bounds of shape
(D,). The decision dimension is inferred from the bounds, rather than passed separately. Matchlbin shape, dtype and device.max_fe (int) – Default:
10000. Positive evaluation horizon for the mask-learning ratio and reference-vector angle penalty, using the internalfe / max_feprogress value. It does not enforce termination.kwargs (dict) – Default:
{}. Extra keyword arguments are accepted for constructor compatibility but are not read by this implementation. In particular, passingdevice=...here does not move tensors; place both bounds on the intended device before construction.
Note
Use this algorithm through a workflow that connects the problem’s evaluation method. Call
workflow.init_step()beforeworkflow.step()or compiling the step. The current evaluation path expects an objective tensor of shape(B, n_objs). It does not consume a(fitness, constraint_violation)tuple.Tensor allocation uses
lb.device. There is no explicit device parameter; prepare both bounds on the intended device.- init_step() None#
Evaluate the initial population and initialize algorithm state.
Invoke through
workflow.init_step()before the first optimization step.- Returns:
None; results are stored in algorithm state.
- step() None#
Advance optimization and update population and fitness state in place.
Invoke through
workflow.step()after initialization. The caller controls termination.- Returns:
None; results are stored in algorithm state.
- evomo.algorithms.telso.algo#