JointTolerance

control_msgs/JointTolerance: limits on one joint's |reference - measured|.

Full docstring

A value above 0 is a limit; 0 or -1 means not checked. WHY: ROS reads 0 as "use the
controller default" and -1 as "no limit"; here a `Tolerances` *is* that default set, and
merging a per-goal tolerance onto it is the caller's job, so both mean "this is not checked".

Import

from robot_msgs.compare import JointTolerance

ROS 2no ROS equivalent

Fields

Name	Type	Default
`name`	`str`	`required`
`position`	`float`	`0.0`
`velocity`	`float`	`0.0`
`acceleration`	`float`	`0.0`

Example

One instance from the package's own test catalog; the output is its real repr().

JointTolerance(name='j1', position=0.01, velocity=0.1, acceleration=0.0)

to_dict() as JSON

{
  "_type": "compare/JointTolerance",
  "name": "j1",
  "position": 0.01,
  "velocity": 0.1,
  "acceleration": 0.0
}

Long arrays are cut after 16 values and say so with “…”.

Functions

Constructors

Classmethods and staticmethods: ways to build one.

`from_dict`

from Msg

from_dict(data: Mapping[str, Any]) -> M

No docstring.

Methods

Return new values; messages are never mutated.

`replace`

from Msg

replace(**changes: Any) -> M

A copy with some fields changed. Validation runs again.

`to_dict`

from Msg

to_dict() -> dict[str, Any]

JSON-safe dict with a "_type" key; arrays keep their dtype and shape.

Used by

Types whose fields refer to it.

Tolerances