-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ScaleCoordinates gives an unexpected outcomes #279
Comments
What is the expected outcome? |
What I interseted is the best solutions. If I understand correctly, the best solution from the outputs is the |
I suspect the incumbent is what you are interested in ("the best solution"): if you evaluate The respective solution to the original function can be obtained as scaled_objective.transform([0.8333333278186403, 0.2307692269918536, 0.08256880736110907]) giving the output array([-3.30881575e-08, -4.91059035e-08, 2.36088783e-08]) |
Hi,
Below is a toy example that confuses me. If no ScaleCoordinates is implemented, the result is right, but if it is implemented, the result has a bit difference from the expected.
Regards
While use non-ScaleCoordinates, executing
result = cma.fmin(objective_function, x0, sigma, options={"bounds":[min_values,max_values]})
, the outcomes as follows:While use ScaleCoordinates, executing
result = cma.fmin(scaled_objective, x0, sigma, options={'popsize':popsize})
, the outcomes as follows:The text was updated successfully, but these errors were encountered: