Thank you for your response Yury! I was hoping to get a bit more (than just catching ValueError or some other exception) info on why certain algorithms (e.g., all the global ones) fail to execute at all or fail after apparently spending quite some time on a problem (based on the time it takes and the activity of the objective function).
I did try to figure that out from the vectors but with no success. A friend of mine is telling me with verbose mode on in C he could get a lot of useful diagnostic information when such problems appeared but switching to C would be a bit of an overkill if there is a simple way to turn verbose mode on in Python (might still need to do that if there isn't). Thanks, Artem. Yury V. Zaytsev <yury@...> writes: What would you actually expect from the verbose mode? You can log the vectors that NLopt passes to your objective function from the callbacks. _______________________________________________ NLopt-discuss mailing list NLopt-discuss@ab-initio.mit.edu http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/nlopt-discuss
