System Performance


System Requirements

The critical requirements for this project are listed below under Mandatory Requirements. These are the ‘needs’ of the project. Additionally, the team identified several value-added requirements during brainstorming. These ‘wants’ are listed below under Desired Requirements.

Mandatory Requirements

  • M.F.1 Plan Paths
  • M.F.2 Predict Cost Map with AI Prediction Model
  • M.F.3 Update Cost Map with Real Time External Sensor Data
  • M.F.4 Decide Route
  • M.F.5 Handle Emergency
  • M.F.6 Log Data
  • M.F.7 Interact with User
  • M.F.8 Visualize Maps and Routes

Desired Requirements

  • M.P.1.1: Generate time-dependent hourly cost maps for the full operating space in ≤ 60 seconds at the start of the day.
  • M.P.1.2: Create 1 scalar cost value that can representing importance for each grid cells with the size of 1 meter^2 .
  • M.P.2.1: Allow at most 1 human operator to drop, move, and delete waypoints directly on the map via the UI.
  • M.P.2.2: Present ≥ 3 candidate route on the UI as a distinct gray polyline overlay on the map.
  • M.P.2.3: Allow the human operator to select 1 candidate route as the final patrol route and visualize it in blue.
  • M.P.3.1: Generate at least 3 candidate routes (max score, shortest path, max coverage) in ≤ 5 seconds.
  • M.P.3.2: Record log locally every 30 secs.
  • M.P.3.3: Send the selected route to the robot ≤ 1 second**.**
  • M.P.4.1: Receive real-time data from ICM module with miss rate < 1%.
  • M.P.4.2: Update data at least once per minute.
  • M.P.4.3: Compute cost changes that imply the change in risk ≤ 3 seconds**.**
  • M.P.5.1: Generate new route(s) with the new cost map ≤ 1 second.
  • M.P.5.2: Visualize new routes in gray on the UI ≤ 1 second.
  • M.P.5.3: Update the active route after change (if selected) ≤ 1 second**.**
  • M.P.6.1**:** Detect emergency from thermal data and video feeds ≤ 10 seconds.
  • M.P.6.2: Update cost map value within 0.1 second.
  • M.P.6.3: When an emergency is detected,  generate and allow user to select candidate routes that pass through the emergency site from the current K7 position.
  • M.P.6.4: Achieve true positive rate > 95%, false negative < 5%.
  • M.P.7.1: Handle emergency in 2 seconds, if emergency, start live streaming and ; else, mark false alarm**.**
  • M.P.7.2: Highlight emergency route on UI under 1 second**.**
  • M.P.7.3: Maintain at least 10 FPS live stream video.
  • M.P.7.4: Generate a new route to K7’s original mission after the alarm within 1 minutes**.**
  • M.P.8.1: Log records (cost maps, routes, selections, emergency events) with timestamps within 500 ms of the triggering event**.**
  • M.P.8.2: Store operational logs (robot positions and route changes) for at least 30 days.
M.F.1Plan Paths
M.P.1.1Generate three candidate patrol rou, max-coverage route) within 5 seconds after each cost-map update, which occurs every 1 minute.