Stone-Soup icon indicating copy to clipboard operation
Stone-Soup copied to clipboard

Metric Managers (and Metrics) should be able to consider a history of sensor positions

Open sglvladi opened this issue 3 years ago • 1 comments

Currently, the SimpleManager has the ability to store and forward groundtruth_paths, tracks and detections to the managed Metrics, which is sufficient for the metrics that currently exists in Stone Soup.

However, there exist metrics (e.g. PCRB) that operate solely on the groundtruth_paths and the positions of the sensors at the respective timesteps, without requiring detections. As it stands, the sensor positions can only be inferred from the measurement_model property of detections, however since such metrics do not require detections by definition there is no proper way of supplying the sensor position history.

It would therefore be useful if we could add extra functionality to the SimpleManager to accept a history of sensor positions which can then be forwarded to managed metrics that require them.

sglvladi avatar Nov 23 '21 14:11 sglvladi

Passing the sensors as a set could be fine? From the sensor, you can use its movement_controller to determine historic states. So we just need to add one extra argument to the manager(s)' add_data method?

oharrald-Dstl avatar Jan 11 '22 13:01 oharrald-Dstl