PhNddlZddlmZddlmZmZddlmZddlm Z m Z ddl m Z m Z mZmZgdZed Gd d ZGd dej$ZGddej$Zy)N) dataclass)ListAny)Future)Metadata MetadataIndex)LoadPlanSavePlan SavePlanner LoadPlanner) WriteResult StorageWriter StorageReaderT)frozenc,eZdZUeed<eed<eed<y)rindex size_in_bytes storage_dataN)__name__ __module__ __qualname__r __annotations__introC:\Users\daisl\Desktop\realtime-object-detection\venv\Lib\site-packages\torch/distributed/checkpoint/storage.pyrrs rrc "eZdZdZej deddfdZej dedefdZ ej de ede efd Z ej ded e de e efd Zej d ed e e eddfdZy)ra Interface used by ``save_state_dict`` to write to storage. One StorageWriter instance acts as both the coordinator and the follower in a distributed checkpoint. As part of initialization, each instance is told its role. A subclass should expect the following sequence of calls. 1) (all ranks) set_up_storage_writer() 2) (all ranks) prepare_local_plan() 3) (coordinator) prepare_global_plan() 4) (all ranks) write_data() 5) (coordinator) finish() is_coordinatorreturnNcy)z Initialize this instance. Args: is_coordinator (bool): Whether this instance is responsible for coordinating the checkpoint. Nr)selfrs rset_up_storage_writerz#StorageWriter.set_up_storage_writer/ rplancy)a Perform storage-specific local planning. While this method can produce a completely different plan, the recommended way is to store storage specific data in SavePlan::storage_data. Args: plan (SavePlan): The local plan from the ``SavePlanner`` in use. Returns: A transformed ``SavePlan`` after storage local planning Nrr"r%s rprepare_local_planz StorageWriter.prepare_local_plan: rplanscy)a Perform centralized planning of storage. This method is only called on the coordinator instance. While this method can produce a completely different plan, the preferred way is to store storage specific data in SavePlan::storage_data. Args: plans: A list of ``SavePlan`` instances, one for each rank. Returns: A list of transformed ``SavePlan`` after storage global planning Nrr"r*s rprepare_global_planz!StorageWriter.prepare_global_planJ rplannercy)a Write all items from ``plan`` using ``planner`` to resolve the data. A subclass should call ``SavePlanner::resolve_data`` on each item from the plan to get access to the underlying object to write. Subclasses should lazily call `resolve_data` as it can allocate memory. In case of tensors, make following assumptions: - They might be on any device, including not matching the one on ``WriteItem::tensor_data`` - They might be views or not contiguous. Only the projection needs to be saved. Args: plan (SavePlan): The save plan to execute. planner (SavePlanner): Planner object to be used to resolve items to data. Returns: A future that completes to a list of WriteResult Nrr"r%r/s r write_datazStorageWriter.write_data\s. rmetadataresultscy)a Write the metadata and marks the current checkpoint as successful. The actual format/schema used for serializing `metadata` is an implementation detail. The only requirement is that it's recoverable in to the same object graph. Args: metadata (Metadata): metadata for the new checkpoint results: A list of WriteResults from all ranks. Returns: None Nr)r"r3r4s rfinishzStorageWriter.finishus$ r)rrr__doc__abcabstractmethodboolr#r r(rr-r rrr2rr6rrrrrs   D T     x  H      h DN  "   '2 [! "  0    +/[0A+B   rrc eZdZdZej defdZej dededdfdZ ej de de fd Z ej d e e de e fd Z ej de d ededfd Zy)ra  Interface used by ``load_state_dict`` to read from storage. One StorageReader instance acts as both the coordinator and the follower in a distributed checkpoint. As part of initialization, each instance is told its role. A subclass should expected the following sequence of calls by ``load_state_dict``: 1) (all ranks) read_metadata() 2) (all ranks) set_up_storage_reader() 3) (all ranks) prepare_local_plan() 4) (coordinator) prepare_global_plan() 5) (all ranks) read_data() r cy)z Read the checkpoint metadata. Returns: The metadata object associated with the checkpoint being loaded. Nr)r"s r read_metadatazStorageReader.read_metadatar$rr3rNcy)z Initialize this instance. Args: metadata (Metadata): The metadata schema to use. is_coordinator (bool): Whether this instance is responsible for coordinating the checkpoint. Nr)r"r3rs rset_up_storage_readerz#StorageReader.set_up_storage_readers rr%cy)a Perform storage-specific local planning. While this method can produce a completely different plan, the recommended way is to store storage specific data in LoadPlan::storage_data. Args: plan (LoadPlan): The local plan from the ``LoadPlan`` in use. Returns: A transformed ``LoadPlan`` after storage local planning Nrr's rr(z StorageReader.prepare_local_planr)rr*cy)a Perform centralized planning of storage loading. This method is only called on the coordinator instance. While this method can produce a completely different plan, the preferred way is to store storage specific data in LoadPlan::storage_data. Args: plans: A list of ``LoadPlan`` instances, one for each rank. Returns: A list of transformed ``LoadPlan`` after storage global planning Nrr,s rr-z!StorageReader.prepare_global_planr.rr/cy)a Read all items from ``plan`` using ``planner`` to resolve the data. A subclass should call ``LoadPlanner::load_bytes`` to deserialize a BytesIO object into the right place. A subclass should call ``LoadPlanner::resolve_tensor`` to get access to the tensors that in should load data into. It's the StorageLayer responsibility to properly schedule any cross device copies required. Args: plan (LoadPlan): The local plan to execute on planner (LoadPlanner): The planner object to use to resolve items. Returns: A future that completes once all reads are finished. Nrr1s r read_datazStorageReader.read_datas* r)rrrr7r8r9rr=r:r?r r(rr-r rrCrrrrrs   x     h    QU       x  H      h DN  "  h    rr)r8 dataclassesrtypingrr torch.futuresrr3rr r/r r r r __all__rABCrrrrrrIsj !   < $i CGGi X_ CGG_ r