assert_approx_equal(actual, desired, significant=7, err_msg='', verbose=True)
:None:None:`assert_array_almost_equal_nulp` or :None:None:`assert_array_max_ulp` instead of this function for more consistent floating point comparisons.
Given two numbers, check that they are approximately equal. Approximately equal is defined as the number of significant digits that agree.
The object to check.
The expected object.
Desired precision, default is 7.
The error message to be printed in case of failure.
If True, the conflicting values are appended to the error message.
If actual and desired are not equal up to specified precision.
Raises an AssertionError if two items are not equal up to significant digits.
assert_allclose
Compare two array_like objects for equality with desired relative and/or absolute precision.
>>> np.testing.assert_approx_equal(0.12345677777777e-20, 0.1234567e-20)
... np.testing.assert_approx_equal(0.12345670e-20, 0.12345671e-20,
... significant=8)
... np.testing.assert_approx_equal(0.12345670e-20, 0.12345672e-20,
... significant=8) Traceback (most recent call last): ... AssertionError: Items are not equal to 8 significant digits: ACTUAL: 1.234567e-21 DESIRED: 1.2345672e-21
the evaluated condition that raises the exception is
This example is valid syntax, but we were not able to check execution>>> abs(0.12345670e-20/1e-21 - 0.12345672e-20/1e-21) >= 10**-(8-1) TrueSee :
Hover to see nodes names; edges to Self not shown, Caped at 50 nodes.
Using a canvas is more power efficient and can get hundred of nodes ; but does not allow hyperlinks; , arrows or text (beyond on hover)
SVG is more flexible but power hungry; and does not scale well to 50 + nodes.
All aboves nodes referred to, (or are referred from) current nodes; Edges from Self to other have been omitted (or all nodes would be connected to the central node "self" which is not useful). Nodes are colored by the library they belong to, and scaled with the number of references pointing them