-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Difference between CPU and GPU generated models? #1346
Comments
@mortengryning I am not sure why you closed the issue. Is it resovled? Is your model using Batch Normalization, Convolution engine? What is the difference in results between GPU and CPU? Thanks, |
I also want to know the difference between CPU and GPU generated models. I've used the pre-trained ResNet model on the CPU-only machine and got terrible results but it worked as expected on a GPU machine. I've used the ResNet-34 model from: https://github.com/Microsoft/CNTK/tree/v1.7.2/Examples/Image/Miscellaneous/ImageNet/ResNet Thanks! |
I closed it because the error was my own fault :-). The models works fine both on CPU and GPU. So no issue for me atleast. |
@mortengryning Hello, when I run the above coding in CPU by cents 2.1 ,there is an error said"TensorOp (binary): The only permitted binary reduction operation is opSum." Would you please tell me how to solve it? Thanks! |
Hi,
I'm trying to evaluate a custom RCNN model using the new managed C# library.
When I use an old model that I have trained in version 3 on the CPU, my code runs and I get the expected results.
However, when I run my code on a model trained by the GPU, the code runs but I get strange results back. This applies on both version 3, version 8 and version 9 of CNTK.
When I evaluate the network on the GPU using the python scripts B3_EvaluateOutput... I get the same results as a model trained on the CPU. I have also checked that the ROI are the same.
Are there some differences between the models that would explain why I can only evaluate the model trained on the CPU?
My code is the following:
`
DeviceDescriptor device = DeviceDescriptor.GetCPUDevice();
The text was updated successfully, but these errors were encountered: