-
Notifications
You must be signed in to change notification settings - Fork 309
model.evaluate and model.predict conflict #252
Comments
hello, I have run into the same issue, have you got the solution? |
No, but I've not looked at it. It also fails if you try and switch the order (i.e. predict and then evaluate) |
Same problem on my M1 Mac:
If I run either one of model.evaluate() or model.predict(), then it is fine.
Looks like there is code error when using both functions in sequence. |
Experiencing the same problem as well (MacBook Pro 13-inch, 2020, Quad-Core Intel Core i5). |
#266 (comment) |
It seems the culprit here is the specified activation function of the output layer. Once this parameter is removed, the code works fine. |
A strange issue when running an example from Laurence Moroney's "AI and Machine Learning for Coders...". When running the following code on an M1 MacBook Air
I have the following output:
whereas on a 2017 Intel MBP, I have:
Also, if I remove either the
model.predict
or themodel.evaluate
the code produces correct output and no errors.I'm using regular python virtual envs on the MBP but Miniforge on the MacBook Air
Tensorflow package differences are as follows:
The text was updated successfully, but these errors were encountered: