lanelet2_route_planning v2.0.0
Loading...
Searching...
No Matches
lanelet2_route_planning::TopicDiagnosticConfig Struct Reference

Configuration parameters for topic diagnostics. More...

#include <lanelet2_route_planning.hpp>

Public Attributes

double min_frequency = 0.0
 Minimum acceptable frequency.
 
double max_frequency = std::numeric_limits<double>::infinity()
 Maximum acceptable frequency.
 
double min_acceptable_timestamp_delta = 0.0
 Minimum acceptable difference between message timestamp and receipt time (in seconds)
 
double max_acceptable_timestamp_delta = std::numeric_limits<double>::infinity()
 Maximum acceptable difference between message timestamp and receipt time (in seconds)
 

Detailed Description

Configuration parameters for topic diagnostics.

Definition at line 39 of file lanelet2_route_planning.hpp.

Member Data Documentation

◆ max_acceptable_timestamp_delta

double lanelet2_route_planning::TopicDiagnosticConfig::max_acceptable_timestamp_delta = std::numeric_limits<double>::infinity()

Maximum acceptable difference between message timestamp and receipt time (in seconds)

Definition at line 58 of file lanelet2_route_planning.hpp.

◆ max_frequency

double lanelet2_route_planning::TopicDiagnosticConfig::max_frequency = std::numeric_limits<double>::infinity()

Maximum acceptable frequency.

Definition at line 48 of file lanelet2_route_planning.hpp.

◆ min_acceptable_timestamp_delta

double lanelet2_route_planning::TopicDiagnosticConfig::min_acceptable_timestamp_delta = 0.0

Minimum acceptable difference between message timestamp and receipt time (in seconds)

Definition at line 53 of file lanelet2_route_planning.hpp.

◆ min_frequency

double lanelet2_route_planning::TopicDiagnosticConfig::min_frequency = 0.0

Minimum acceptable frequency.

Definition at line 43 of file lanelet2_route_planning.hpp.


The documentation for this struct was generated from the following file: