Ignored exceptions

[altaetran]

Hey,

I noticed that when I use optimize_hyperparameters (with multiple random starts) in succession, I obtain the message:

"Exception RuntimeError: RuntimeError('cannot join current thread',) in <Finalize object, dead> ignored"

and cannot seem to suppress it using warnings.simplefilter("ignore"). Do you think this is something that can be hidden? Thanks!

Best,

Han

[markchil]

Han:

I am not sure what the cause of that exception is — that message of course appears to be related to the use of multiprocessing to do the random starts in parallel, but I am not sure what would cause that to happen without first emitting a more meaningful error/warning.

Try calling GaussianProcess.optimize_hyperparameters() with the extra keyword verbose=True. This will print the number of random starts that completed successfully, along with other useful information. Compare this to the requested number of starts (which will be what you set the random_starts keyword, or the default is the number of cores on your system). This will tell you if random starts are in fact failing and getting dropped, or if the warning is in fact benign.

As for suppressing the warnings, I recall reading at one point that there are issues with warnings filters and multiprocessing. This SO thread has some details from a slightly different context:
http://stackoverflow.com/questions/12654267/python-3-catching-warnings-during-multiprocessing

-Mark

On Aug 30, 2014, at 12:03 AM, Han Altae-Tran notifications@github.com wrote:

Hey,

I noticed that when I use optimize_hyperparameters (with multiple random starts) in succession, I obtain the message:

"Exception RuntimeError: RuntimeError('cannot join current thread',) in ignored"

and cannot seem to suppress it using warnings.simplefilter("ignore"). Do you think this is something that can be hidden? Thanks!

Best,

Han

—
Reply to this email directly or view it on GitHub.