true_divide(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.
Returns a true division of the inputs, element-wise.
Unlike 'floor division', true division adjusts the output type to present the best answer, regardless of input types.
In Python, //
is the floor division operator and /
the true division operator. The true_divide(x1, x2)
function is equivalent to true division in Python.
Dividend array.
Divisor array. If x1.shape != x2.shape
, they must be broadcastable to a common shape (which becomes the shape of the output).
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.
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.
For other keyword-only arguments, see the ufunc docs <ufuncs.kwargs>
.
This is a scalar if both :None:None:`x1` and :None:None:`x2` are scalars.
This docstring was copied from numpy.true_divide.
>>> x = np.arange(5) # doctest: +SKIPThis example is valid syntax, but we were not able to check execution
... np.true_divide(x, 4) # doctest: +SKIP array([ 0. , 0.25, 0.5 , 0.75, 1. ])
>>> x/4 # doctest: +SKIP array([ 0. , 0.25, 0.5 , 0.75, 1. ])This example is valid syntax, but we were not able to check execution
>>> x//4 # doctest: +SKIP array([0, 0, 0, 0, 1])
The /
operator can be used as a shorthand for np.true_divide
on ndarrays.
>>> x = np.arange(5) # doctest: +SKIPSee :
... x / 4 # doctest: +SKIP array([0. , 0.25, 0.5 , 0.75, 1. ])
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