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

stopping criteria and failed evaluation question #17

Closed
rho80 opened this issue Mar 15, 2017 · 5 comments
Closed

stopping criteria and failed evaluation question #17

rho80 opened this issue Mar 15, 2017 · 5 comments

Comments

@rho80
Copy link

rho80 commented Mar 15, 2017

Hi there,
to be sure, currently the only one stopping criteria supported in pySOT is maximum number of evaluations, am I right?
The second question is about failed evaluation. What should my own "objfunction" method return to consider it as failed evaluation by pySOT? Should "ValueError" exception arise? And what about optimization process behavior in this case, does it stop or continue? (I've read the issues #8 and #9)

@dme65
Copy link
Owner

dme65 commented Mar 15, 2017

Hi!

  1. That is correct. Are you interested in using another stopping criterion? I would be happy the add some and doing this shouldn't require much work on my part.
  2. This example should be helpful: https://github.com/dme65/pySOT/blob/master/pySOT/test/test_subprocess.py
    pySOT will try to go back and evaluate this input again if something went wrong the first time.

@rho80
Copy link
Author

rho80 commented Mar 17, 2017

Thanks for information and for the example.
Regarding to stopping criterion: especially during testing stage (which means before the final start of (possibly) very time consuming optimization process) I'd welcome "real time" criterion - something like run till Monday morning ;). And sometimes it'd be useful to have criterion related to fitness value (absolute value or no improvement after specified number of evaluations for example).

@SanPen
Copy link

SanPen commented Mar 28, 2017

Hi,
+1 to a stopping criteria.

Outstanding work by the way.

@dme65
Copy link
Owner

dme65 commented Mar 30, 2017

@dbindel: Is there support for this in POAP?

@SanPen: I'm glad you like pySOT!

@dme65
Copy link
Owner

dme65 commented Apr 27, 2017

A real-time stopping criterion will be added to the next version.

@dme65 dme65 closed this as completed Apr 27, 2017
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

3 participants