Proposal: Renaming DetectionMetrics → PerceptionMetrics

[dpascualhe]

As part of the ongoing DetectionMetrics revamp, the tool now supports both image/LiDAR detection and segmentation. Given this broader scope, we believe that a more suitable name moving forward would be PerceptionMetrics, a term that naturally umbrellas detection, segmentation, and future perception-related tasks.

A quick search on Google and GitHub shows no significant existing projects named PerceptionMetrics, which makes it a strong and unique candidate.

Since there are several references to DetectionMetrics in past GSoC projects and a published article, it’s important to ensure that all existing links to old repo and old docs remain functional and correctly redirect after renaming.

✅ Action Items / Checks Before Proceeding

GitHub & Repository

• Confirm GitHub’s automatic redirect after renaming.
• Check if it is possible to keep old GitHub pages URL redirecting to the new one.
• Create new perceptionmetrics branch.
• Update README (include disclaimer informing about the renaming process and pointing to DetectionMetrics v1).
• Update all code references to detectionmetrics, including toml config file.
• Update GitHub pages.
• Rename repo and merge changes from perceptionmetrics branch to main.
• Check that old repo and GitHub pages links redirect as expected.

After finishing the process, we could consider creating a new repo with the old DetectionMetrics name and include a README with a disclaimer to address the situation and pointing to old source code, docs, etc. In that way, instead of simply redirecting users we would inform them in a more explicit way.

[dpascualhe]

@SakhinetiPraveena any thoughts?