nextafter(x1, x2, /, out=None, *, where=True, casting='same_kind', order='K', dtype=None, subok=True[, signature, extobj])

Some inconsistencies with the Dask version may exist.

Return the next floating-point value after x1 towards x2, element-wise.

Parameters

x1 : array_like

Values to find the next representable value of.

x2 : array_like

The direction where to look for the next representable value of :None:None:`x1`. If x1.shape != x2.shape , they must be broadcastable to a common shape (which becomes the shape of the output).

out : ndarray, None, or tuple of ndarray and None, optional

A location into which the result is stored. If provided, it must have a shape that the inputs broadcast to. If not provided or None, a freshly-allocated array is returned. A tuple (possible only as a keyword argument) must have length equal to the number of outputs.

where : array_like, optional

This condition is broadcast over the input. At locations where the condition is True, the :None:None:`out` array will be set to the ufunc result. Elsewhere, the :None:None:`out` array will retain its original value. Note that if an uninitialized :None:None:`out` array is created via the default out=None , locations within it where the condition is False will remain uninitialized.

**kwargs :

For other keyword-only arguments, see the ufunc docs <ufuncs.kwargs> .

Returns

out : ndarray or scalar

The next representable values of :None:None:`x1` in the direction of :None:None:`x2`. This is a scalar if both :None:None:`x1` and :None:None:`x2` are scalars.

This docstring was copied from numpy.nextafter.

Examples

This example is valid syntax, but we were not able to check execution

>>> eps = np.finfo(np.float64).eps  # doctest: +SKIP
... np.nextafter(1, 2) == eps + 1  # doctest: +SKIP
True

This example is valid syntax, but we were not able to check execution

>>> np.nextafter([1, 2], [2, 1]) == [eps + 1, 2 - eps]  # doctest: +SKIP
array([ True,  True])

See :

Local connectivity graph

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

---

File: /dask/array/ufunc.py#None
type: <class 'dask.array.ufunc.ufunc'>
Commit: