Skip to content
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

Tune relative precision for unit test img_conv2 in test_NetworkCompare. #3591

Merged
merged 1 commit into from
Aug 21, 2017

Conversation

qingqing01
Copy link
Contributor

  1. It's no problem with relative precision 1e-3 when testing several times on my local machine.
  2. But the testing failed with 1e-2 in the TeamCity. And the output size is 4096, only one value's relative precision is over 1e-2.
[00:15:50]	I8018 16:15:50.212294 30060 test_NetworkCompare.cpp:172] ------------------------------ Check Network Output ------------------------------
[00:15:50]	I8018 16:15:50.212296 30060 test_NetworkCompare.cpp:176] OUTPUT VALUE: 0
[00:15:50]	I8018 16:15:50.212419 30060 test_NetworkCompare.cpp:164] Row: 8, network A output : -1.13249e-05 network B output : -1.14441e-05
[00:15:50]	/paddle/paddle/gserver/tests/test_NetworkCompare.cpp:168: Failure
[00:15:50]	Expected: 0
[00:15:50]	To be equal to: nNum
[00:15:50]	Which is: 1

https://paddleci.ngrok.io/viewLog.html?buildId=6071&buildTypeId=Paddle_GpuUnittest&tab=buildLog&_focus=4229

…e.cpp.

  1. It's no problem with relative precision 1e-3 when testing several times in my local machine.
  2. But the testing failed with 1e-2 in the TeamCity, and only one value's relative precision is over 1e-2. So tune it to 4e-2
@qingqing01 qingqing01 merged commit bcc6d14 into PaddlePaddle:develop Aug 21, 2017
@qingqing01 qingqing01 deleted the network_compare branch November 14, 2019 05:28
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.

None yet

2 participants