CV Aggregation Data Structure

[AskewParity]

🚀 Feature

We want to store all the outputs from our cv piplines into a comprehensive data structure.

When CV aggregator returns the results, it will return a list of detected objects. We will save them into a permanent list (along with global IDs <-- protos change).

Motivation

We want to do statistics on the CV results.

Details:

• Modify mission_state to contain a map of IdentifiedTarget protos objects.
  • Add pruneRuns(list of runs given its ID): Takes in a list of runs of prune, and modifies/removes them from the list.
  • On protos, there needs to be a wrapper object that includes IdentifiedTarget and a 64b encoding of an image.
• Modify gcs_routes.cpp in the /target/all route such that the map is updated when the Runs are queried. Since this may run more than once, it might need to be concatenated onto any existing route.