#142 closed enhancement (done)
The number of stored BadChildren can be reduced
Reported by: | gkronber | Owned by: | swagner |
---|---|---|---|
Priority: | lowest | Milestone: | HeuristicLab 3.3.0 |
Component: | ZZZ OBSOLETE: Selection.OffspringSelection | Version: | 3.1 |
Keywords: | Cc: |
Description
I think it is not necessary to keep all bad children generated in the BadChildren list. Because in the end only the first few lucky losers are prompted to the next generation anyway, the rest is discarded. It would be more RAM friendly to keep only the necessary amount of bad children. See attached patch
Change History (9)
comment:1 Changed 16 years ago by swagner
- Status changed from new to assigned
comment:2 Changed 16 years ago by swagner
comment:3 Changed 16 years ago by gkronber
bug-fixes in r297
- fixed an 'off by one' error in the calculation of the number of bad children needed
- fixed calculation of current success-ratio (used number of good children since last iteration instead of the total number of good children)
comment:4 Changed 16 years ago by swagner
comment:5 Changed 16 years ago by swagner
- Resolution set to fixed
- Status changed from assigned to closed
comment:6 Changed 16 years ago by gkronber
comment:7 Changed 15 years ago by swagner
- Milestone changed from 3.1 to Iteration 0
Milestone 3.1 deleted
comment:8 Changed 13 years ago by swagner
- Milestone changed from Iteration 0 to Current
Milestone Iteration 0 deleted
comment:11 Changed 13 years ago by swagner
- Milestone changed from Current to HeuristicLab 3.3.0
Milestone Current deleted
Note: See
TracTickets for help on using
tickets.
Applied patch in r296