Opened 6 years ago
Closed 6 years ago
#2986 closed defect (done)
RoundedNormalAllPositionsManipulator applies bounds incorrectly
Reported by: | jkarder | Owned by: | jkarder |
---|---|---|---|
Priority: | medium | Milestone: | HeuristicLab 3.3.16 |
Component: | Encodings.IntegerVectorEncoding | Version: | trunk |
Keywords: | Cc: |
Description
Since RoundFeasible was introduced, which takes care of transforming each dimension into a feasible value, part of the old transformation code was left over, which leads to wrong manipulations:
int value = (vector[i] + (int)Math.Round((N.NextDouble() * sigma[i % sigma.Length])) - min) / step; // transformation 1 max = FloorFeasible(min, max, step, max - 1); vector[i] = RoundFeasible(min, max, step, value); // transformation 2
Change History (6)
comment:1 Changed 6 years ago by jkarder
- Status changed from new to accepted
comment:2 Changed 6 years ago by jkarder
comment:3 Changed 6 years ago by jkarder
- Version set to trunk
comment:4 Changed 6 years ago by jkarder
- Owner changed from jkarder to abeham
- Status changed from accepted to reviewing
comment:5 Changed 6 years ago by abeham
- Owner changed from abeham to jkarder
- Status changed from reviewing to readytorelease
Reviewed r16619. Let's ignore a version increment, the integer vector encoding is currently hardly used.
comment:6 Changed 6 years ago by jkarder
- Resolution set to done
- Status changed from readytorelease to closed
Note: See
TracTickets for help on using
tickets.
r16619: fixed value transformation in RoundedNormalAllPositionsManipulator
Do we need a version increment?