stopping criteria and failed evaluation question about pysot

[dme65]

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]

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]

Hi,
+1 to a stopping criteria.

Outstanding work by the way.

[dme65]

@dbindel: Is there support for this in POAP?

@SanPen: I'm glad you like pySOT!

[dme65]

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