set_backend(backend, coerce=False, only=False)

Upon entering the with statement, the given backend will be added to the list of available backends with the highest priority. Upon exit, the backend is reset to the state before entering the scope.

Parameters

backend : {object, 'scipy'}

The backend to use. Can either be a str containing the name of a known backend {'scipy'} or an object that implements the uarray protocol.

coerce : bool, optional

Whether to allow expensive conversions for the x parameter. e.g., copying a NumPy array to the GPU for a CuPy backend. Implies only .

only : bool, optional

If only is True and this backend returns NotImplemented , then a BackendNotImplemented error will be raised immediately. Ignoring any lower priority backends.

Context manager to set the backend within a fixed scope.

Examples

>>> import scipy.fft as fft
... with fft.set_backend('scipy', only=True):
...     fft.fft([1])  # Always calls the scipy implementation
array([1.+0.j])

See :

Back References

The following pages refer to to this document either explicitly or contain code examples using this.

scipy.fft._backend.set_backend

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

---

GitHub : /scipy/fft/_backend.py#127
type: <class 'function'>
Commit: