Package-level declarations
Telemetry, the entry point, which wraps a shared TelemetryRegistry. Log by name with Telemetry.log("Drive/Pose", pose), or hold a typed handle for the fast path: DoubleTopic, IntTopic, LongTopic, FloatTopic and BooleanTopic for numbers and booleans, and Topic<T> for strings, arrays, structs, and lists of structs. TelemetryTable groups related topics under a path, and TelemetryLoggable lets an object publish its own fields. For a type you don't own, register a TelemetryTypeHandler in TelemetryRegistry.handlers; Measure has one by default, which logs the base-unit value with its unit.
The registry stamps each value, sends it to every registered backend (or only those registered for a path prefix), and reports problems through a warning handler instead of throwing. A path keeps one type while a backend is registered, repeated numbers and strings are skipped unless a handle's keepDuplicates is set, and a handle made before any backend exists starts working when one is registered.
A handle can carry properties, the first being a unit that dashboards such as AdvantageScope show and convert: table.doubleTopic("wheelVelocity").withUnit("m/s"). They go out when the path is first published, as the properties of the NetworkTables announcement and as the metadata of the log entry, laid out the way WPILib logs NetworkTables topics. Values are strings, booleans, or finite numbers.
TelemetryBackend and TelemetryEntry are what a destination implements.
Types
A handle on a boolean topic.
A handle on a double topic.
A handle on a float topic.
A handle on an integer topic, for values that fit in an Int. For larger ones use LongTopic.
A handle on an integer topic.
A struct, or an array of them, described by schema.
The entry point for telemetry: a shared TelemetryRegistry and its root table.
A destination for logged values: a log file, a live server, a test double.
Where the values of one path end up.
An object that knows how to publish itself into a TelemetryTable.
The names of topic properties that dashboards understand.
The set of TelemetryBackends that logged values are routed to, plus the clock that stamps them.
A namespace of logged values: a path like /Drive, whose topics are /Drive/leftVelocity and so on, and whose children are tables like /Drive/Odometry.
A handle on one telemetry path, which values are set on.
What a telemetry path holds: one of the ValueTypes, or a StructType.
Knows how to publish values of a type that can't publish themselves, such as one from a library.
The TelemetryTypeHandlers of a TelemetryRegistry, by the type they handle.
Receives the warnings telemetry reports instead of throwing.
A handle on a topic of reference values: strings, arrays, structs, and lists of structs.
Functions
Sets properties on this topic, in addition to the ones it has, and returns the handle.