Гh$,%SrSSKrSSKrSSKrSSKrSSKJr SSKJrJ r SSK J r J r J r JrJr SSKrSSKJr SSKJrJrJrJrJrJr \R6"S 5r\ \\\4r\\ S '\ \\4r!\\ S '\"S S 55r"S\SS4Sjr#S$Sjr$S\4Sjr%S\4Sjr&S\4Sjr'S\ SS4Sjr(S\4Sjr)S\S\S\4Sjr*S\RVS\4Sjr,\ "SS\55r-S\R\S\-S\R\4S jr/S$S!jr0"S"S#5r1g)%z-XGBoost collective communication related API.N) dataclass)IntEnumunique)AnyDictOptional TypeAliasUnion)_T)_LIB _check_call build_infoc_str make_jcargspy_strz[xgboost.collective]_ArgVals_Argsc\rSrSr%SrSr\\\S'Sr \\\S'Sr \\ \S'Sr \\\S'Sr \\\S'S \S \4S jrS rg) ConfigaHUser configuration for the communicator context. This is used for easier integration with distributed frameworks. Users of the collective module can pass the parameters directly into tracker and the communicator. .. versionadded:: 3.0 Attributes ---------- retry : See `dmlc_retry` in :py:meth:`init`. timeout : See `dmlc_timeout` in :py:meth:`init`. This is only used for communicators, not the tracker. They are different parameters since the timeout for tracker limits only the time for starting and finalizing the communication group, whereas the timeout for communicators limits the time used for collective operations. tracker_host_ip : See :py:class:`~xgboost.tracker.RabitTracker`. tracker_port : See :py:class:`~xgboost.tracker.RabitTracker`. tracker_timeout : See :py:class:`~xgboost.tracker.RabitTracker`. Nretrytimeouttracker_host_ip tracker_porttracker_timeoutargsreturncvURbURUS'URbURUS'U$)z*Update the arguments for the communicator. dmlc_retry dmlc_timeout)rrselfrs eC:\Users\julio\OneDrive\Documentos\Trabajo\Ideas Frescas\venv\Lib\site-packages\xgboost/collective.pyget_comm_configConfig.get_comm_config8s7 :: !!%D  << ##'<rs`3  ! 88KK   1 2uS#X/)/X &y& && &R">">d">J/ #    'C'D'( C ,B,c,b,`bhh32BJJB2::B2 'P'Pr'