BVhIdZddlmZddlmZej r ej Zn ejZdZ dZ dZ iZ iZ dZGdd eZy ) zClass to represent a device.)tf2) device_specc.tj|y)zvCheck that a device spec is valid. Args: spec: a string. Raises: An exception if the spec is invalid. N) DeviceSpec from_string)specs R/home/dcms/DCMS/lib/python3.12/site-packages/tensorflow/python/framework/device.py check_validr s c6t|tjS)z;Abstract away the fact that DeviceSpecV2 is the base class.) isinstancer DeviceSpecV2)objs r is_device_specr(s C11 22r c|yt|r|jStj|}|jS)zCReturns a canonical name for the given `DeviceSpec` or device name.)r to_stringrr)devices r canonical_namer-s@ ^ F      # #F +F    r ct|tr|Stj|}|r|St|}|t|<|S)aReturns a device function that merges devices specifications. This can be used to merge partial specifications of devices. The innermost setting for a device field takes precedence. For example: with tf.device(merge_device("/device:GPU:0")) # Nodes created here have device "/device:GPU:0" with tf.device(merge_device("/job:worker")): # Nodes created here have device "/job:worker/device:GPU:0" with tf.device(merge_device("/device:CPU:0")): # Nodes created here have device "/job:worker/device:CPU:0" with tf.device(merge_device("/job:ps")): # Nodes created here have device "/job:ps/device:CPU:0" Args: spec: A `DeviceSpec` or a device spec string (partially) describing the device that should be used for all nodes created in the scope of the returned device function's with block. Returns: A MergeDevice object with the above-described behavior. Raises: ValueError: if the spec was not valid. )r MergeDevice_cached_mergersget)rmergers r merge_devicer=sD6k" K   t $& M t & /$ -r cJeZdZdZdgZdZdZdZfdZe dZ xZ S)raWraps a device specification (DeviceSpec or str) with merge functionality. When called, this class will merge a node_def with its own spec. It also exposes a `shortcut_string_merge` method which can significantly improve performance of device placement. _specct|tjr||_yt|tjr/|j j |j|_ytj ||_y)N) r rrr DeviceSpecV1 __class__rrr)selfrs r __init__zMergeDevice.__init__nsX$ 001dj D+22 3>>--dnn.>?dj))$/djr c~tj|jxsd}|jj |S)Nr)rrrrmake_merged_spec)r!node_defcurrent_devices r __call__zMergeDevice.__call__ws2  ++HOO,ArBN :: & &~ 66r c|jxsd}|j|f}tj|}|(|j |j }|t|<|S)aHMerge a node def without materializing a full DeviceSpec object. Often a device merge is invoked in order to generate a string which can be passed into the c api. In such a case, we can cache the node_def.device -> merge_result_string map, and in most cases avoid: - Materializing a copy of self._spec (In the case of DeviceSpecV1) - Materializing a DeviceSpec for node_def.device - A DeviceSpec.merge_from invocation In practice the cache hit rate for this function is very high, because the number of invocations when iterating through the device stack is much larger than the number of devices. Args: node_def: An Operation (or Operation-like) to merge device constraints with self._spec Returns: A string containing the merged device specification. r)rr_string_merge_cacherr'r)r!r%r merge_keyresults r shortcut_string_mergez!MergeDevice.shortcut_string_merges^.__ "FV$I $ $Y /F ~}}X&002f'-)$ Mr cxdjtt||jj S)Nz {} (spec: {}))formatsuperr__repr__rr)r!r s r r0zMergeDevice.__repr__s4  ! ! k4)+TZZ-A-A-C EEr cJt|jj S)aTIndicate whether the wrapped spec is empty. In the degenerate case where self._spec is an empty specification, a caller may wish to skip a merge step entirely. (However this class does not have enough information to make that determination.) Returns: A boolean indicating whether a device merge will be trivial. )boolrr)r!s r is_null_mergezMergeDevice.is_null_mergesDJJ((*+ ++r ) __name__ __module__ __qualname____doc__ __slots__r"r'r,r0propertyr3 __classcell__)r s@r rrds;i)07!FE  ,  ,r rN)r7tensorflow.pythonrtensorflow.python.frameworkrenabledrrrr rrrr)robjectrr r r@sa #!33;;=''*''* 3 $NN,&N,r