Skip to content

Conversation

mattdawkins
Copy link
Contributor

Add extra safety check to the forward function of the net class, such that a more descriptive error is written out (as opposed to a segfault) when attempting to input too many blobs for the network, or using a mis-configured net.

@longjon
Copy link
Contributor

longjon commented Sep 3, 2015

Yes, thank you. (Note, however, that input blobs are planned for eventual deprecation.)

Perhaps the check should even be CHECK_EQ? Otherwise won't input blobs retain stale data? It would also be nice to have a message (just use the check as a stream, CHECK_???(...) << "Wrong number of input blobs supplied" or some such thing).

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

Successfully merging this pull request may close these issues.

2 participants