+ nDjp^RIHt^RIHtHtHt^RIHt^RIH t H t ^RI H t ^RI Ht!RR]4tR #) ) annotations)ComponentColumnComponentColumnListDescribedComponentBatch) AsComponents) AnyBatchValueComponentValueLike)DynamicArchetype)catch_and_log_exceptionsc]tRt^ tRtRRRlltRR/RRlltRR/RR lltR R lt] RR R ll4t ] RRl4t Rt R#) AnyValuesub Helper to log arbitrary values as a bundle of components. Example ------- ```python rr.log( "any_values", rr.AnyValues( confidence=[1.2, 3.4, 5.6], description="Bla bla bla…", # URIs will become clickable links homepage="https://www.rerun.io", repository="https://github.com/rerun-io/rerun", ), ) ``` Tc$V^8dQhRRRRRR/#)drop_untyped_nonesboolkwargsComponentValueLike | NonereturnNone)formats"S/data/cameron/venvs/s3viz/lib/python3.14/site-packages/rerun_sdk/rerun/any_value.py __annotate__AnyValues.__annotate__s#.:.:4.:B[.:`d.:c \P!V3/VBVnVPPVPP 4R#)a Construct a new AnyValues bundle. Each kwarg will be logged as a separate component batch using the provided data. - The key will be used as the name of the component - The value must be able to be converted to an array of arrow types. In general, if you can pass it to [pyarrow.array][] you can log it as a extension component. Note: rerun requires that a given component only take on a single type. The first type logged will be the type that is used for all future logs of that component. The API will make a best effort to do type conversion if supported by numpy and arrow. Any components that can't be converted will result in a warning (or an exception in strict mode). `None` values provide a particular challenge as they have no type information until after the component has been logged with a particular type. By default, these values are dropped. This should generally be fine as logging `None` to clear the value before it has been logged is meaningless unless you are logging out-of-order data. In such cases, consider introducing your own typed component via [rerun.ComponentBatchLike][]. You can change this behavior by setting `drop_untyped_nones` to `False`, but be aware that this will result in potential warnings (or exceptions in strict mode). If you are want to inspect how your component will be converted to the underlying arrow code, the following snippet is what is happening internally: ``` np_value = np.atleast_1d(np.array(value, copy=False)) pa_value = pa.array(value) ``` Parameters ---------- drop_untyped_nones: If True, any components that are either None or empty will be dropped unless they have been previously logged with a type. kwargs: The components to be logged. N)r _default_without_archetype_builder _with_name __class____name__)selfrrs&&,r__init__AnyValues.__init__s:Z)CCDVaZ`a    !8!89rrc(V^8dQhRRRRRRRR/#) r descriptorstrvaluerrrrr r)rs"rrrNs,&?X\ rc @VPPWVR7V#)z3Adds an `AnyValueBatch` to this `AnyValues` bundle.r)rwith_component_from_data)r"r&r(rs&&&$rr+"AnyValues.with_component_from_dataNs! ..zUg.h rc ,V^8dQhRRRRRRRRRR /#) rfieldr'component_typer(rrrrr r)rs"rrrUs4*-6Ohl rc @VPPWW4R7V#)zPAdds an `AnyValueBatch` to this `AnyValues` bundle with name and component type.r*)rwith_component_override)r"r.r/r(rs&&&&$rr1!AnyValues.with_component_overrideUs  --eU-r rcV^8dQhRR/#rrzlist[DescribedComponentBatch]r)rs"rrr\s44&C4rc 6VPP4#Nras_component_batchesr"s&rr8AnyValues.as_component_batches\s}}1133rc$V^8dQhRRRRRR/#)rrrrrrrr)rs"rrr`s#8,8,8,@Y8,^q8,rc .p\R4;_uu_4VP4F4wrE\P!WEVR7pVfK#VP V4K6 RRR4\ V4# +'giL;i)a Construct a new column-oriented AnyValues bundle. This makes it possible to use `rr.send_columns` to send columnar data directly into Rerun. The returned columns will be partitioned into unit-length sub-batches by default. Use `ComponentColumnList.partition` to repartition the data as needed. Each kwarg will be logged as a separate component column using the provided data. - The key will be used as the name of the component - The value must be able to be converted to an array of arrow types. In general, if you can pass it to [pyarrow.array][] you can log it as a extension component. Note: rerun requires that a given component only take on a single type. The first type logged will be the type that is used for all future logs of that component. The API will make a best effort to do type conversion if supported by numpy and arrow. Any components that can't be converted will result in a warning (or an exception in strict mode). `None` values provide a particular challenge as they have no type information until after the component has been logged with a particular type. By default, these values are dropped. This should generally be fine as logging `None` to clear the value before it has been logged is meaningless unless you are logging out-of-order data. In such cases, consider introducing your own typed component via [rerun.ComponentBatchLike][]. You can change this behavior by setting `drop_untyped_nones` to `False`, but be aware that this will result in potential warnings (or exceptions in strict mode). If you are want to inspect how your component will be converted to the underlying arrow code, the following snippet is what is happening internally: ``` np_value = np.atleast_1d(np.array(value, copy=False)) pa_value = pa.array(value) ``` Parameters ---------- drop_untyped_nones: If True, any components that are either None or empty will be dropped unless they have been previously logged with a type. kwargs: The components to be logged. zAnyValues.columnsr*N)r itemsrcolumnappendr)clsrrcolumnsnamer(cols&&, rrAAnyValues.columns_sgf*, %&9 : :%||~ #**4K]^?NN3' .; #7++ ; :s/A2 A22 B cV^8dQhRR/#r4r)rs"rrrs44#@4rc 6VPP4#r6r7r9s&rcomponent_batchesAnyValues.component_batchess}}1133r)rN)T)r! __module__ __qualname____firstlineno____doc__r#r+r1r8 classmethodrApropertyrG__static_attributes__rrrr r sU&.:`_cos48,8,t44rr N) __future__r _baseclassesrrr_lograny_batch_valuerr dynamic_archetyper error_utilsr r rrrrVs("WW>/1R4 R4r