Kriging optimization strategy
Types of changes
What types of changes does your code introduce? Check all the boxes that apply:
-
Bug fix (non-breaking change which fixes an issue), -
New feature (non-breaking change which adds functionality), -
Breaking change (fix or feature that would cause existing functionality to change), -
Documentation.
All following must be checked:
-
I have checked there is no similar merge request on the track, -
I have read the CONTRIBUTING document. -
My code follows the code style of this project. -
I have updated the documentation accordingly. -
I have added tests to cover my changes. -
All new and existing tests passed.
Description
Be able to specify if global optimization or gradient based optimization should be use. Most of the time, gradient optimization is enough and faster to compute.
This proposal add the keyword global_optimizer
in both kriging class and settings.
Edited by Pamphile Roy