-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into feat/port/rosbag2_to_annotated_t4_tlr
- Loading branch information
Showing
4 changed files
with
391 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# Tools Overview | ||
|
||
This document offers a concise overview of the scripts employed in the conversion process for the tracking simulator. | ||
Prior to reading this document, we recommend referring to the [tools overview](./tools_overview.md) for a comprehensive description of the entire repository. | ||
|
||
## tracking debugger rosbag to annotated T4 format | ||
|
||
input: rosbag2 with ground_truth/objects | ||
output: T4 format data | ||
|
||
```bash | ||
python -m perception_dataset.convert --config config/rosbag2_to_t4/convert_tracking_debugger_to_tracking_eval.yaml | ||
``` | ||
|
||
## scenario simulator rosbag | ||
|
||
This guide emphasizes the utilization of the rosbag output generated by the planning scenario simulator. | ||
The T4 format of this output proves valuable for conducting regression tests on the tracking module. | ||
|
||
input: rosbag2 with ground_truth/objects and obstacle_segmentation/pointcloud | ||
output: T4 format data | ||
|
||
```bash | ||
python -m perception_dataset.convert --config config/rosbag2_to_t4/convert_scenario_sim_to_tracking_eval.yaml | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
16 changes: 16 additions & 0 deletions
16
tests/config/convert_tracking_debugger_to_tracking_eval.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
task: convert_rosbag2_to_t4_tracking | ||
description: | ||
scene: ["tracking_regression", "synthetic"] | ||
conversion: | ||
# path to rosbag dir output by simulator | ||
input_base: ./data/rosbag2_tracking_debugger | ||
output_base: ./data/pseudo_labeling_t4_format | ||
skip_timestamp: 1.0 | ||
num_load_frames: 0 | ||
object_topic_name: /perception/object_recognition/ground_truth/objects | ||
object_msg_type: TrackedObjects | ||
lidar_sensor: # tracking debugger data has no lidar | ||
topic: "" | ||
channel: "" | ||
camera_sensors: [] # synthetic data has no images | ||
topic_list: ./config/topic_list_tracking_eval.yaml |
Oops, something went wrong.