-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add ground_segmentation_evaluator #528
base: develop
Are you sure you want to change the base?
feat: add ground_segmentation_evaluator #528
Conversation
- judge if the cloud has entity_id field
@nanoshimarobot
|
ScenarioName: ground_segmentation-sample | ||
ScenarioDescription: ground_segmentation-sample | ||
SensorModel: aip_xx1 | ||
VehicleModel: jpntaxi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you test with pilot-auto?
VehicleModel: jpntaxi | |
VehicleModel: lexus |
634f47b
to
6973d00
Compare
SensorModel: aip_xx1 | ||
VehicleModel: jpntaxi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because aip_xx1
and jpntaxi
are TIER IV internal models, it is better to set them to sample_sensor_kit
and sample_vehicle
like other sample scenarios for perception tasks in driving_log_replayer.
driving_log_replayer/sample/perception/scenario.yaml
Lines 4 to 5 in a91986e
SensorModel: sample_sensor_kit | |
VehicleModel: sample_vehicle |
.vscode/c_cpp_properties.json
Outdated
// "/opt/ros/humble/include/**", | ||
"driving_log_replayer/include/**" | ||
// "${env:HOME}/ros_ws/awf/install/**", | ||
// "/usr/include/**", | ||
// "/usr/local/include/**" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Q] Are these comment out intended?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, those comments were unintentional. I have fixed them.
Quality Gate passedIssues Measures |
Types of PR
Description
Add ground segmentation evaluator scenario.
This evaluator has two types of ground truth data.
*.pcd.bin files located in t4_dataset/sample/data/LIDAR_CONCAT/ and the data has semantic label, provided by #107.
The rosbag data in the input_bag contains annotated pointcloud data, captured from sources such as AWSIM.
How to review this PR
Please download this driving_log_replayer_data for ground_segmentaion evaluation: TIERIV_INTERNAL_LINKThat data has only annotated pcd data, so please also check this annotated rosbag data: TIERIV_INTERNAL_LINKPlease download this driving_log_replayer_data for ground_segmentaion evaluation : TIERIV_INTERNAL_LINK
There are separate scenario.yaml and input_bag files for each mode, as shown in the image below:
Therefore, for testing, please modify each name to 'scenario.yaml' and 'input_bag/' before running the tests.
Others
When running ground_segmentation in 'annotated_rosbag' mode, it is necessary to modify the sensing module of autoware.universe as follows:
https://github.com/autowarefoundation/autoware.universe/blob/main/sensing/autoware_pointcloud_preprocessor/src/filter.cpp#L383-L390
When running ground_segmentation in 'annotated_pcd' mode, it is necessary to reduce the rosbag play rate because the evaluation process takes longer than the ground_segmentation process in this mode.
dlr simulation run -p ground_segmentation --launch_args play_rate:=0.1