You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mxnet.apache.org by GitBox <gi...@apache.org> on 2018/06/25 02:58:57 UTC

[GitHub] lanking520 commented on issue #11377: [MXNET-564] Fix the Flaky test on arange

lanking520 commented on issue #11377: [MXNET-564] Fix the Flaky test on arange
URL: https://github.com/apache/incubator-mxnet/pull/11377#issuecomment-399817052
 
 
   Source to the changes on the number:
   - We use `toString` on the number that passed to the backend, there should be minimum losses.
   - The number return type are NDArray, the toArray method brings this: `DType.Float32 => units.map(wrapBytes(_).getFloat)`, this should have minimum impact to the result
   - Scala addition method already changed to while loop, but it doesn't help
   - Not only the last number in the Scala Array influence the accuracy, there are more.
   
   Guys, do you think this problem is more like a JVM and C difference question?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services