-
Notifications
You must be signed in to change notification settings - Fork 10
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
Prepend Points are not being inlcuded in ranking of "global search" #40
Comments
I looked at the code and it looks OK, can you please give me an MWE? |
This code seems to generate the error:
It prints:
As you can see, the "local phase", does not start from [0.0,0.1], it starts from some other point. |
But note the line Param:[0.0, 0.1]
val:0.010000000000000002 in your output. The point is visited, right after the starting points are generated. |
Yes, I figured that out. However, I expected to apply the local optimizer to the prepended_point rather than starting from a linear combination of the prepended_point and the best starting point. |
Hi,
I am using the
prepend_points
option to add a candidate for optimality of a previous run.However, after evaluating the 2500 Sobol points and the prepend_point, the "local phase" is not starting from the correct point, i.e
it is evaluating the prepend point here:
Parameters:[2.0023715563522275, 0.47616619564356855, 4.0064103584405935, 9.991268276769539, 2.0070308283954614, 0.7000687884505741]
Criterion Function:2.4557462126908754e-5
but when the local phase starts, it is starting from other visited minimum.
Parameters:[1.7097586400102227, 0.17207853362685677, 8.172369551469059, 7.004253780801954, 4.9741088445582955, 0.8102656679075574]
Criterion Function:16.682058405554365
The text was updated successfully, but these errors were encountered: