Closed roywei closed 6 years ago
@sandeep-krishnamurthy is this correct behavior? I didn't find this problem in other cnn examples
No, this warning should be shown only if custom loss is used. Will look into it.
@sandeep-krishnamurthy update: tried to change:
loss=keras.losses.categorical_crossentropy
to
loss='categorical_crossentropy'
warning is gone.
Closing as fixed in #158
Running a simple example under examples/mnist_cnn.py will produce the following warning:
Although it does not use any custom loss nor slice.