feat(planning_data_analyzer): add open-loop drivable area compliance metric#381
Conversation
|
Thank you for contributing to the Autoware project! 🚧 If your pull request is in progress, switch it to draft mode. Please ensure:
|
|
Updated in ee58930. I also revalidated the analyzer through the open-loop pipeline on local bags that include route + /map/vector_map and explicit vehicle_model input. |
I validated the analyzer changes through the current open-loop pipeline and local bags, but I have not yet done a full DLR package-level compatibility sweep. Since this PR changes analyzer launch/output behavior, DLR integration is a valid concern. If needed, I will do a follow-up DLR compatibility check after the EPDMS implementation series. |
The evaluator inside TIER IV uses the DLR, so better to check ASAP. I think it won'T be a problem for now, since we allow the vehicle model to be empty. |
|
@go-sakayori |
|
@beomseok-kimm |
77e634e
into
autowarefoundation:main
Description
This PR is the second implementation step in a series toward full
EPDMSsupport inautoware_planning_data_analyzer, following theNAVSIMmetric definition and reference implementation.This PR specifically adds
DAC (Drivable Area Compliance)as the next standalone subscore.How was this PR tested?
Successfully created output rosbag and JSON results that contain the
DACmetric when route, vector map, and vehicle info are available.input and output link:
Notes for reviewers
The current
DACimplementation is a package-level approximation based on preferred lanelets and ego footprint corner checks.Effects on system behavior
None.