[MATH-865] Wide bounds to CMAESOptimizer result in NaN parameters passed to fitness function

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0
• Fix Version/s: 3.1
• Assignee: Gilles Sadowski
• Reporter: Frank Hess
• Created: 19/Sep/12 21:10
• Updated: 04/Mar/13 18:53
• Resolved: 22/Sep/12 10:04

Description

If you give large values as lower/upper bounds (for example -Double.MAX_VALUE as a lower bound), the optimizer can call the fitness function with parameters set to NaN. My guess is this is due to FitnessFunction.encode/decode generating NaN when normalizing/denormalizing parameters. For example, if the difference between the lower and upper bound is greater than Double.MAX_VALUE, encode could divide infinity by infinity.