#509 closed enhancement (rejected)
Change SimOpt Constraint Handling
| Reported by: | abeham | Owned by: | abeham |
|---|---|---|---|
| Priority: | medium | Milestone: | HeuristicLab 3.3.0 |
| Component: | ZZZ OBSOLETE: SimOpt | Version: | 3.2 |
| Keywords: | Cc: |
Description
Currently parameters for simulation optimization are encapsulated in a ConstrainedItemList. Constraints are defined on the list which are applied to the parameters. This works quite well in some ways, but carries a number of significant drawbacks.
Possibly the worst thing is that SimOpt operates in a very closed environment. The recent changes to crossover however give the benefit of applying representation specific crossovers to the parameters. In some way this is already realized in SimOpt through an own crossover preparator, but could be streamlined with the core.
Constraints on scopes are of course a no-go and would only complicate things, so some kind of constraint checker is needed which is able to solve the situation of constraint violation (in the object parameters).
Change History (3)
comment:1 Changed 15 years ago by abeham
- Resolution set to wontfix
- Status changed from new to closed
comment:2 Changed 14 years ago by swagner
- Milestone changed from Iteration 4 to Current
Milestone Iteration 4 deleted
comment:11 Changed 14 years ago by swagner
- Milestone changed from Current to HeuristicLab 3.3.0
Milestone Current deleted
constraints were removed entirely. It was decided that attaching the constraints to the data is not a good choice when all data manipulators also need to be aware of them anyway.