Struct robotics_signals::navigation::Odometry

#[repr(C)]
pub struct Odometry {
    pub header: Header,
    pub child_frame_id: String,
    pub pose: PoseWithCovariance,
    pub twist: TwistWithCovariance,
}

This represents an estimate of a position and velocity in free space. The pose in this message should be specified in the coordinate frame given by header.frame_id The twist in this message should be specified in the coordinate frame given by the child_frame_id

Fields

header: Header

child_frame_id: String

Frame id the pose points to. The twist is in this coordinate frame.

pose: PoseWithCovariance

Estimated pose that is typically relative to a fixed world frame.

twist: TwistWithCovariance

Estimated linear and angular velocity relative to child_frame_id.

Implementations

impl Odometry

pub fn create_topic_with_name(
    participant: &DdsParticipant,
    name: &str,
    maybe_qos: Option<DdsQos>,
    maybe_listener: Option<DdsListener>
) -> Result<DdsTopic<Self>, DDSError>

Create a topic using of this Type specifying the topic name

Arguments

• participant - The participant handle onto which this topic should be created
• name - The name of the topic
• maybe_qos - A QoS structure for this topic. The Qos is optional
• maybe_listener - A listener to use on this topic. The listener is optional

pub fn create_topic(
    participant: &DdsParticipant,
    maybe_topic_prefix: Option<&str>,
    maybe_qos: Option<DdsQos>,
    maybe_listener: Option<DdsListener>
) -> Result<DdsTopic<Self>, DDSError>

Create a topic of this Type using the default topic name. The default topic name is provided by the Self::topic_name function.

Arguments

• participant - The participant handle onto which this topic should be created
• maybe_topic_prefix - An additional prefix to be added to the topic name. This can be None
• maybe_qos - A QoS structure for this topic. The Qos is optional
• maybe_listener - A listener to use on this topic. The listener is optional

pub fn create_sample_buffer(len: usize) -> SampleBuffer<Odometry>

Create a sample buffer for storing an array of samples You can pass the sample buffer into a read to read multiple samples. Multiple samples are useful when you have one or more keys in your topic structure. Each value of the key will result in the storage of another sample.

Trait Implementations

impl<'de> Deserialize<'de> for Odometry

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
    __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for Odometry

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>where
    __S: Serializer,

Serialize this value into the given Serde serializer.

impl TopicType for Odometry

fn key_cdr(&self) -> Vec<u8>

return the cdr encoding for the key. The encoded string includes the four byte encapsulation string.

fn is_fixed_size() -> bool

fn has_key() -> bool

fn force_md5_keyhash() -> bool

fn hash(&self) -> u32

fn typename() -> CString

The type name for this topic

fn topic_name(maybe_prefix: Option<&str>) -> String

The default topic_name to use when creating a topic of this type. The default implementation uses ‘/’ instead of ‘::’ to form a unix like path. A prefix can optionally be added