Skip to content
This repository has been archived by the owner on Feb 23, 2023. It is now read-only.

Not feasible points - constraints not respected #156

Open
LEleonora opened this issue Jan 26, 2018 · 1 comment
Open

Not feasible points - constraints not respected #156

LEleonora opened this issue Jan 26, 2018 · 1 comment

Comments

@LEleonora
Copy link
Contributor

Hi,

currently a batch solution can contain infeasible points in case of batch generation and local penalization (LP). The constrains are checked when the acquisition function is evaluated, but then the acquisition function value is penalized for the local penalization strategy. I would suggest to consider the case of not feasible points as a separate case so that these points will not be consider as possible minima in the next steps. For example, if the constraints are not respected, the penalized acquisition function value is set to infinite. Would this be a proper solution?

Thank you.

@oliversheridanmethven
Copy link

I think I have encountered a similar solution, although I had constructed (naively?) functions which throw assertions then infeasible points are evaluated.

cf Suggested point is infeasible #94

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants