Merge pull request #39826 from yongtang:compatibility-numpy.testing.assert_close

PiperOrigin-RevId: 313208135
Change-Id: I8c1efc4f9c37134c94501ab5a3fcad412008858b
This commit is contained in:
TensorFlower Gardener 2020-05-26 09:43:41 -07:00
commit db0a3952c0
1 changed files with 6 additions and 6 deletions

View File

@ -765,9 +765,9 @@ def assert_near_v2(x, y, rtol=None, atol=None, message=None, summarize=None,
statically known. statically known.
@compatibility(numpy) @compatibility(numpy)
Similar to `numpy.assert_allclose`, except tolerance depends on data type. Similar to `numpy.testing.assert_allclose`, except tolerance depends on data
This is due to the fact that `TensorFlow` is often used with `32bit`, `64bit`, type. This is due to the fact that `TensorFlow` is often used with `32bit`,
and even `16bit` data. `64bit`, and even `16bit` data.
@end_compatibility @end_compatibility
""" """
return assert_near(x=x, y=y, rtol=rtol, atol=atol, summarize=summarize, return assert_near(x=x, y=y, rtol=rtol, atol=atol, summarize=summarize,
@ -818,9 +818,9 @@ def assert_near(
Op that raises `InvalidArgumentError` if `x` and `y` are not close enough. Op that raises `InvalidArgumentError` if `x` and `y` are not close enough.
@compatibility(numpy) @compatibility(numpy)
Similar to `numpy.assert_allclose`, except tolerance depends on data type. Similar to `numpy.testing.assert_allclose`, except tolerance depends on data
This is due to the fact that `TensorFlow` is often used with `32bit`, `64bit`, type. This is due to the fact that `TensorFlow` is often used with `32bit`,
and even `16bit` data. `64bit`, and even `16bit` data.
@end_compatibility @end_compatibility
""" """
message = message or '' message = message or ''