(phSSKJs Jr SSKJr SSKJr SSKJr "SS5rS\0r S r SS jr S r SS jr S r\ "SSS9 g)N)_basic_backend)_realtransforms_backend)_fftlog_backendc,\rSrSrSrSr\S5rSrg) _ScipyBackendaThe default backend for fft calculations Notes ----- We use the domain ``numpy.scipy`` rather than ``scipy`` because ``uarray`` treats the domain as a hierarchy. This means the user can install a single backend for ``numpy`` and have it implement ``numpy.scipy.fft`` as well. numpy.scipy.fftc[[URS5nUc[[URS5nUc[[URS5nUc[ $U"U0UD6$)N)getattrr__name__rrNotImplemented)methodargskwargsfns E/var/www/html/venv/lib/python3.13/site-packages/scipy/fft/_backend.py__ua_function___ScipyBackend.__ua_function__s`^V__d ; :0&//4HB :&//4@B :! !4"6""N) r __module__ __qualname____firstlineno____doc__ __ua_domain__ staticmethodr__static_attributes__rrrrrs &M # #rrscipyc[U[5(a [UnUR S:wa [ S5eU$![an[ SU35UeSnAff=f)z8Maps strings to known backends and validates the backendzUnknown backend Nr z,Backend does not implement "numpy.scipy.fft") isinstancestr_named_backendsKeyError ValueErrorr)backendes r_backend_from_argr($sl'3 B%g.G 11GHH N  B/y9: A Bs = AAAcD[U5n[R"XX#S9 g)aSets the global fft backend This utility method replaces the default backend for permanent use. It will be tried in the list of backends automatically, unless the ``only`` flag is set on a backend. This will be the first tried backend outside the :obj:`set_backend` context manager. 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 Whether to coerce input types when trying this backend. only : bool If ``True``, no more backends will be tried if this fails. Implied by ``coerce=True``. try_last : bool If ``True``, the global backend is tried after registered backends. Raises ------ ValueError: If the backend does not implement ``numpy.scipy.fft``. Notes ----- This will overwrite the previously set global backend, which, by default, is the SciPy implementation. Examples -------- We can set the global fft backend: >>> from scipy.fft import fft, set_global_backend >>> set_global_backend("scipy") # Sets global backend (default is "scipy"). >>> fft([1]) # Calls the global backend array([1.+0.j]) )coerceonlytry_lastN)r(uaset_global_backend)r&r*r+r,s rr.r.3sP (G'tOrcF[U5n[R"U5 g)a Register a backend for permanent use. Registered backends have the lowest priority and will be tried after the global backend. 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. Raises ------ ValueError: If the backend does not implement ``numpy.scipy.fft``. Examples -------- We can register a new fft backend: >>> from scipy.fft import fft, register_backend, set_global_backend >>> class NoopBackend: # Define an invalid Backend ... __ua_domain__ = "numpy.scipy.fft" ... def __ua_function__(self, func, args, kwargs): ... return NotImplemented >>> set_global_backend(NoopBackend()) # Set the invalid backend as global >>> register_backend("scipy") # Register a new backend # The registered backend is called because # the global backend returns `NotImplemented` >>> fft([1]) array([1.+0.j]) >>> set_global_backend("scipy") # Restore global backend to default N)r(r-register_backendr&s rr0r0_sH (G rcB[U5n[R"XUS9$)aContext manager to set the backend within a fixed scope. 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. 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]) )r*r+)r(r- set_backend)r&r*r+s rr3r3s8 (G >>'t <>> import scipy.fft as fft >>> fft.fft([1]) # Calls default SciPy backend array([1.+0.j]) >>> with fft.skip_backend('scipy'): # We explicitly skip the SciPy backend ... fft.fft([1]) # leaving no implementation available Traceback (most recent call last): ... BackendNotImplementedError: No selected backends had an implementation ... )r(r- skip_backendr1s rr5r5s2 (G ??7 ##rT)r,)FFF)FF)scipy._lib.uarray_libuarrayr-rrrrr#r(r.r0r3r5rrrr:sU%##2 ] )PX%!P=@$:7T*r