o z“©i@ ã@sxddlmZmZddlmZddlmZmZmZm Z m Z ddl m Z e dƒZ eGdd„dƒƒZGdd „d eee ƒZd S) é)ÚABCÚabstractmethod)Ú dataclass)ÚAnyÚDictÚGenericÚOptionalÚTypeVar)ÚMisconfigurationExceptionÚTc@s"eZdZdeeeffdd„ZdS)Ú OutputResultÚreturncCst‚©N)ÚNotImplementedError©Úself©rú`/home/ubuntu/.local/lib/python3.10/site-packages/pytorch_lightning/loops/optimization/closure.pyÚasdictszOutputResult.asdictN)Ú__name__Ú __module__Ú __qualname__rÚstrrrrrrrr sr cs`eZdZdZd‡fdd„ Zdefdd„Zeded edefd d „ƒZ ded edefd d „Z ‡Z S)ÚAbstractClosurea$Abstract base class for optimizer closures in Lightning. Formally, a closure is binding variables from an external scope to a function that does a computation on these variables without taking them explicitly as input. This has the benefit that a closure can be passed to an object which later can call it like a function but without requiring to pass in any arguments. This class provides a simple abstraction making the instance of this class callable like a function while capturing the closure result and caching it. r Ncstƒ ¡d|_dSr)ÚsuperÚ__init__Ú_resultr©Ú __class__rrr)s  zAbstractClosure.__init__cCs$|jdur tdƒ‚|jd}|_|S)zÕThe cached result from the last time the closure was called. Once accessed, the internal reference gets reset and the consumer will have to hold on to the reference as long as necessary. NzÒThe closure hasn't been executed. HINT: did you call `optimizer_closure()` in your `optimizer_step` hook? It could also happen because the `optimizer.step(optimizer_closure)` call did not execute it internally.)rr )rÚresultrrrÚconsume_result-s ÿzAbstractClosure.consume_resultÚargsÚkwargscOsdS)zAImplements the behavior of the closure once it is getting called.Nr©rr!r"rrrÚclosure=szAbstractClosure.closurecOs|j|i|¤Ž|_|Sr)r$rr#rrrÚ__call__BszAbstractClosure.__call__)r N) rrrÚ__doc__rr r rrr$r%Ú __classcell__rrrrrs rN)ÚabcrrÚ dataclassesrÚtypingrrrrr Ú&pytorch_lightning.utilities.exceptionsr r r rrrrrÚs