3,072
edits
Metropolis Microservices/People Engagement Demo/Demo Description: Difference between revisions
Metropolis Microservices/People Engagement Demo/Demo Description (view source)
Revision as of 23:19, 31 March 2025
, 31 Marchno edit summary
Efernandez (talk | contribs) No edit summary |
Efernandez (talk | contribs) No edit summary |
||
| Line 19: | Line 19: | ||
* [https://developer.ridgerun.com/wiki/index.php/Metropolis_Microservices/RidgeRun_Services/Media Media Service]: This service receives RTSP streams, performs detection and head direction estimation for all detections across the input streams, and maintains consistent person IDs across all cameras using re-identification (ReID). The results are published to Redis. Additionally, the service generates an output RTSP stream that provides a Bird’s Eye View (BEV) combining all input streams. | * [https://developer.ridgerun.com/wiki/index.php/Metropolis_Microservices/RidgeRun_Services/Media Media Service]: This service receives RTSP streams, performs detection and head direction estimation for all detections across the input streams, and maintains consistent person IDs across all cameras using re-identification (ReID). The results are published to Redis. Additionally, the service generates an output RTSP stream that provides a Bird’s Eye View (BEV) combining all input streams. | ||
* [https://developer.ridgerun.com/wiki/index.php/Metropolis_Microservices/RidgeRun_Services/Engagement_Analytics Engagement Analytics]: The Engagement Analytics service reads detections and head orientation data and, based on a configured target, performs engagement estimation. It generates statistics such as total and average engagement time, engagement per ID, and visitor count. These statistics are then sent to InfluxDB. Additionally, the service calculates a heatmap of engaged individuals and publishes it to Redis. | * [https://developer.ridgerun.com/wiki/index.php/Metropolis_Microservices/RidgeRun_Services/Engagement_Analytics Engagement Analytics]: The Engagement Analytics service reads detections and head orientation data and, based on a configured target, performs engagement estimation. It generates statistics such as total and average engagement time, engagement per ID, and visitor count. These statistics are then sent to InfluxDB. Additionally, the service calculates a heatmap of engaged individuals and publishes it to Redis. | ||
* [https://developer.ridgerun.com/wiki/index.php/Metropolis_Microservices/RidgeRun_Services/Display Display Service]: The Display service presents a mosaic view with the main video showing the Bird’s Eye View (BEV) stream, alongside the individual camera streams. Additionally, it overlays the BEV with the engagement heatmap and tags for each person, indicating whether they are engaged or not, along with their engagement time. | * [https://developer.ridgerun.com/wiki/index.php/Metropolis_Microservices/RidgeRun_Services/Display Display Service]: The Display service presents a mosaic view with the main video showing the Bird’s Eye View (BEV) stream, alongside the individual camera streams. Additionally, it overlays the BEV with the engagement heatmap and tags for each person, indicating whether they are engaged or not, along with their engagement time. This information is shown in the board's display and it looks like this: | ||
[[File:display-example.png|600px|center|thumb| Ridgerun's Display Service example]] | |||
* '''Monitoring Service''': The Monitoring service consists of two applications: InfluxDB, which stores all the statistics generated by the Analytics service, and Grafana, which is used to create a dashboard for visualizing these statistics. | * '''Monitoring Service''': The Monitoring service consists of two applications: InfluxDB, which stores all the statistics generated by the Analytics service, and Grafana, which is used to create a dashboard for visualizing these statistics. | ||