Make pycaffe errors behave in a reasonable way

[longjon]

Currently recoverable errors in pycaffe (such as using the wrong input dimensions) cause interpreter crashes instead of Python exceptions.

[Yangqing]

That would be a very nice feature to have. I am not sure what is the
easiest way to do this, because right now the errors are produced by glog's
LOG(FATAL) command, which I am not sure could be caught as an exception.

One possible way to handle this is to run the pycaffe module at a separate
subprocess, which also brings the additional benefit of asynchronous calls
(run caffe prediction, immediately returns, join later). A potential
problem is that we will then need to pipe data between processes, which may
create some additional overhead.

Yangqing

On Wed, Jan 15, 2014 at 3:25 PM, longjon notifications@github.com wrote:

Currently recoverable errors in pycaffe (such as using the wrong input
dimensions) cause interpreter crashes instead of Python exceptions.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/35
.

[shelhamer]

Fixed in #311 and 76c2554 and others! Not everything is caught for python yet, but the usual errors aren't crashes anymore.