Skip to content
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

Best way to handle an asked candidate for which the loss calculation failed user-side #1498

Open
a-mazzetto opened this issue Feb 15, 2023 · 1 comment

Comments

@a-mazzetto
Copy link

Hello,
I have a question on how to best tell() the optimizer that a candidate's simulation has failed, without necessarily penalizing it with high loss. The scenario is such that between ask() and tell() there is a calculation that might fail for a number of reasons, some of which deserve a penalization with high loss, some others perhaps not (e.g. the calculation did not converge but might converge for a very similar candidate, not ideal but it is what it is). Would it make sense and is there any way to tell the optimizer to not expect a tell() for some specific candidate, or anyways make it aware that one candidate failed but that does not necessarily mean that similar candidates should be unfavored?
Any help on this would be really appreciated, thank you

@teytaud
Copy link
Contributor

teytaud commented Sep 20, 2023

Hello! There are algorithms that will not care too much if some candidates obtained by ask are never followed by tell. For example I think that DiscreteOnePlusOne will not care too much, and many related algorithms either. Do you have an example code ? If you have a code which fails due to this maybe we can just replace the optimizer by a more "robust" one.

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

No branches or pull requests

2 participants