> For the complete documentation index, see [llms.txt](https://carec.gitbook.io/carec-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://carec.gitbook.io/carec-docs/documentation/autonomous-mobility/evaluation-metrics.md). # Evaluation Metrics Metrics are defined before testing and reported with system version, environment, sample size, and uncertainty. ## Safety and control * Collision and near-miss count * Minimum clearance and stopping distance * E-stop and takeover latency * Unsafe-command rejection * Safe-state transition success ## Perception and localization * Per-class precision, recall, and hazardous false negatives * False alerts per operating hour * Capture-to-decision latency * Localization position/heading error * Loss detection and relocalization time ## Navigation and human factors * Goal success, route violations, doorway clearance * Intervention, recovery, and no-progress rate * Task success by input method * Alert recognition and caregiver delivery * Acceleration, jerk, and comfort indicators * Uptime, restart rate, battery runtime, and thermal limits Aggregate success must not hide safety-critical failures; report them by scenario and cause. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://carec.gitbook.io/carec-docs/documentation/autonomous-mobility/evaluation-metrics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.