Custom Query (2734 matches)
Results (31 - 33 of 2734)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #47 | done | Implement an engine for debugging purposes | epitzer | swagner |
| Description |
Developing complex algorithms is a quite difficult and error-prone task. Therefore a special engine for debugging algorithms would be very helpful. This engine should offer more insights into the operator graph and the scope tree during the execution of an algorithm. |
|||
| #48 | done | Refactor operator modularization concept | swagner | swagner |
| Description |
The operator modularization concept needs some revision. Handling with combined operators and operator extractors is quite cumbersome and should be simplified. Additionally, combined operators should also offer a possibility to define variable infos representing variables needed inside their wrapped operator graph (cf. programmable operator). |
|||
| #49 | done | Remove operator reset mechanism | swagner | swagner |
| Description |
The reset mechanism for operators is considered dangerous and should be removed. It may encourage users to implement operators with internal states (local variables) that are only valid for a single algorithm execution. This could be quite harmful as we saw in HeuristicLab 2.0. Instead, state variables should be stored in scopes. Local variables of operators should be valid throughout the whole life time of an operator which normally is longer than a single algorithm execution. |
|||
