#2466 closed defect (done)
SASEGASA terminates too early
| Reported by: | pfleck | Owned by: | abeham |
|---|---|---|---|
| Priority: | medium | Milestone: | HeuristicLab 3.3.13 |
| Component: | Algorithms.OffspringSelectionGeneticAlgorithm | Version: | 3.3.12 |
| Keywords: | Cc: |
Description
SASEGASA ignores the FinalMaximumSelectionPressure when only a single village remains, still using the MaximumSelectionPressure and terminates too early.
Change History (8)
comment:1 Changed 9 years ago by pfleck
- Status changed from new to accepted
comment:2 Changed 9 years ago by pfleck
- Owner changed from pfleck to abeham
- Status changed from accepted to reviewing
comment:3 Changed 9 years ago by gkronber
I guess a plugin version increment is necessary?
comment:4 Changed 9 years ago by abeham
yes
comment:5 Changed 8 years ago by abeham
- Status changed from reviewing to readytorelease
Surprise (or not), we will this time not increase the version number. The reasons are:
- The offspring selection genetic algorithm (OSGA) and its island version are defined in the same plugin and would also be affected by the version change. OSGA instances are used quite often in practice.
- The results of SASEGASA would not deteriorate due the change, but the runtime would increase. Results could be better though.
- Code that uses SASEGASA and stops it after a fixed amount of time would not experience worse behavior. Code that waits upon its completion however would experience different behavior. The old behavior can be restored if FinalMaximumSelectionPressure is set to the same value as MaximumSelectionPressure (which is the default).
comment:6 Changed 8 years ago by gkronber
;)
comment:7 Changed 8 years ago by abeham
- Resolution set to done
- Status changed from readytorelease to closed
comment:8 Changed 8 years ago by mkommend
Note: See
TracTickets for help on using
tickets.
r12886 Use the CurrentMaximumSelectionPressure instead of the MaximumSelectionPressure to determine termination.