|
| 1 | +/**: |
| 2 | + ros__parameters: |
| 3 | + update_rate: 10.0 |
| 4 | + latency_threshold_ms: 1000.0 |
| 5 | + window_size: 10 |
| 6 | + |
| 7 | + processing_steps: # processing steps used to calculate the latency. |
| 8 | + # The name of the steps are only used for setting the parameters and for debug outputs |
| 9 | + sequence: # sequence ordered from first to last step |
| 10 | + - multi_object_tracker |
| 11 | + - decorative_object_merger_node |
| 12 | + - map_based_prediction |
| 13 | + - planning |
| 14 | + - control |
| 15 | + # Each step needs to be associated with a topic, a topic type, a timestamp meaning, and a multiplier |
| 16 | + multi_object_tracker: |
| 17 | + topic: # input topic with the timestamp and the latency duration of the processing step |
| 18 | + /perception/object_recognition/tracking/multi_object_tracker/debug/meas_to_tracked_object_ms |
| 19 | + topic_type: # type of the input topic |
| 20 | + autoware_internal_debug_msgs/msg/Float64Stamped |
| 21 | + timestamp_meaning: "end" # whether the timestamp represent the "start" or "end" time of the step |
| 22 | + latency_multiplier: 1.0 # multiplier to convert the input latency duration into ms (e.g., 1e3 for s->ms, 1e-3 for us->ms) |
| 23 | + decorative_object_merger_node: |
| 24 | + topic: # input topic with the timestamp and the latency duration of the processing step |
| 25 | + /perception/object_recognition/tracking/decorative_object_merger_node/debug/processing_time_ms |
| 26 | + topic_type: # type of the input topic |
| 27 | + autoware_internal_debug_msgs/msg/Float64Stamped |
| 28 | + timestamp_meaning: "end" # whether the timestamp represent the "start" or "end" time of the step |
| 29 | + latency_multiplier: 1.0 # multiplier to convert the input latency duration into ms (e.g., 1e3 for s->ms, 1e-3 for us->ms) |
| 30 | + map_based_prediction: |
| 31 | + topic: # input topic with the timestamp and the latency duration of the processing step |
| 32 | + /perception/object_recognition/prediction/map_based_prediction/debug/processing_time_ms |
| 33 | + topic_type: # type of the input topic |
| 34 | + autoware_internal_debug_msgs/msg/Float64Stamped |
| 35 | + timestamp_meaning: "end" # whether the timestamp represent the "start" or "end" time of the step |
| 36 | + latency_multiplier: 1.0 # multiplier to convert the input latency duration into ms (e.g., 1e3 for s->ms, 1e-3 for us->ms) |
| 37 | + planning: |
| 38 | + topic: # input topic with the timestamp and the latency duration of the processing step |
| 39 | + /planning/planning_validator/validation_status |
| 40 | + topic_type: # type of the input topic |
| 41 | + autoware_planning_validator/msg/PlanningValidatorStatus |
| 42 | + timestamp_meaning: "end" # whether the timestamp represent the "start" or "end" time of the step |
| 43 | + latency_multiplier: 1.0e3 # multiplier to convert the input latency duration into ms (e.g., 1e3 for s->ms, 1e-3 for us->ms) |
| 44 | + control: |
| 45 | + topic: # input topic with the timestamp and the latency duration of the processing step |
| 46 | + /control/control_component_latency |
| 47 | + topic_type: # type of the input topic |
| 48 | + autoware_internal_debug_msgs/msg/Float64Stamped |
| 49 | + timestamp_meaning: "end" # whether the timestamp represent the "start" or "end" time of the step |
| 50 | + latency_multiplier: 1.0e3 # multiplier to convert the input latency duration into ms (e.g., 1e3 for s->ms, 1e-3 for us->ms) |
| 51 | + |
| 52 | + latency_offsets_ms: # [ms] extra offset to add to the total latency |
| 53 | + - 0.0 # sensing |
| 54 | + - 1.4 # perception |
| 55 | + - 50.0 # planning |
| 56 | + - 15.0 # control |
| 57 | + - 191.0 # vehicle interface |
0 commit comments