English
English
English
  • SWARM Documentation
  • What's new?
    • Version 2024.2
    • Version 2024.1
    • Version 2023.3
      • Update 1
  • SWARM in a nutshell
    • SWARM Perception Platform Overview
  • Quick start guide
    • P101, P401 or OP101
      • P101 - Perception Box
      • P401 - Perception Box
      • OP101AC - Outdoor Perception Box
      • OP101DC - Outdoor Perception Box
    • Virtual Perception Box
      • System requirements
      • Install VPX Agent on NVIDIA Jetson (Jetpack 4.6)
      • Install VPX Agent on NVIDIA Jetson (Jetpack 5.1.2)
      • Install VPX Agent on X86/NVIDIA Server
  • Solution areas
    • Traffic Insights
      • Set-up Traffic Counting
      • Set-up Traffic Counting with speed estimates
      • Set-up Intersection Insights
    • Parking Insights
      • Set-up Barrierless Parking
      • Set-up Barrierless Parking with ANPR
        • Set-up guide and recommendations - ANPR
      • Set-up Single Space/Multi Space Parking
        • Standard examples
    • Advanced Traffic Insights
      • Set-up Adaptive Traffic Control
      • Set-up Journey Time & Traffic Flow
        • Set-up guide - Installation
        • Technical concept
      • Set-up Queue Length Detection
    • People Entry/Exit counting
  • SWARM Control Center
    • Devices
      • Camera & Device Monitoring
      • Camera Configuration
        • Scenario Configuration
          • Models
          • Calibration support
          • Camera settings
        • Rule Engine
          • Use Case Examples for Rule Engine
      • Device Health
    • Data Analytics
      • Creation and organization of dashboards
      • Dashboard overview & Widget creation
        • Traffic Scenario
        • Parking Scenario
        • Generic Scenario
    • Data Integration
      • Data Analytics API (REST API)
      • Raw event data with Custom MQTT server
      • SCC API
    • Administration
      • Monitoring Alerts
      • License Management
      • User Management
  • Test & Performance measurements
    • Benchmarks
      • How do we measure Performance?
    • White paper for use cases
      • Traffic Counting
      • Barrierless Parking and ANRP
  • Useful knowledge
    • 🚒Troubleshooting Guidelines
    • Network Requirements
    • Browser Compatibility SCC
    • Our Object Classes
    • Number Plate Area Code
  • Guidelines
    • How to access the debug output?
    • How to use Azure IotHub as Custom Broker
    • VPX
      • Upgrade IotEdge from 1.1 to 1.4
      • Upgrade Jetpack from 4.4.1 to 4.6.0
  • Getting Support
    • Get in touch
    • FAQs
Powered by GitBook
On this page
  • Adaptive Traffic Control
  • Device Health - The healthiness of your device at a glance
  • Model Improvements
  • Traffic & Parking (Standard and Accuracy+)
  • People Head
  • People Full body
  • Parking Fisheye
  • Device Metadata
  • Track Calibration History
  • Device Update
  • Other improvements

Was this helpful?

Export as PDF
  1. What's new?

Version 2023.3

Release Date: 15.11.2023

PreviousVersion 2024.1NextUpdate 1

Last updated 1 year ago

Was this helpful?

Adaptive Traffic Control

Adaptive traffic control enables you to interface with hardware devices like traffic controllers using dry contacts. Use cases and benefits:

  • 'Smart Prio' System: Prioritise certain traffic classes and ensure fluid traffic behavior in real-time (e.g. pedestrians, bicyclists, e-scooters, heavy traffic).

  • Simplify infrastructure maintenance: Replace multiple induction loops with a single Swarm Perception Box. The installation does not require excavation work, and reduces the maintenance effort/costs.

Device Health - The healthiness of your device at a glance

The following metrics are supported:

  • Device Uptime, Status, Restarts, Available Disk Space

  • Device Temperature (support for P101/OP101/Jetson Nano)

  • LTE Modem Traffic, Signal Strength and Reconnects (support for OP100/OP101)

  • Camera status and Camera processing speed (FPS)

  • Generated and Pending events

Model Improvements

Traffic & Parking (Standard and Accuracy+)

We improved the classification accuracy for both variants Standard and Accuracy+, especially for the classes: articulated truck, truck with trailer and car with trailer.

People Head

We fixed the class output, the event class output is now person (vs. previously head). Affected by this change are the devices P101/OP101/VPX. Not affected are the devices P100/OP100.

We improved the accuracy due to higher resolution processing.

People Full body

We improved the accuracy due to higher resolution processing.

Parking Fisheye

The model has been deprecated and will not be updated in the future. The model will continue to work as long as there are devices using it. Please consider switching to the Traffic & Parking model.

Device Metadata

Organize devices and generate events containing pre-defined device metadata. You can define up to five key and value pairs for a device. The keys and values can be freely defined by your choice, we support autocompletion for keys to avoid nasty typos.

Track Calibration History

Track calibration overlays the last 100 object tracks on a current camera frame. This enables you to position event triggers (e.g. counting lines) for optimal results. We extend the functionality with a history over the last 24 hours.

With track calibration history enabled you will be able to access the track calibration for every hour of the past 24 hours.

The track calibration images will be stored on the edge device and are only accessible through the Control Center. Make sure that viewing, storing, and processing of these images for up to 24 hours is compliant with your applicable data privacy regulations.

Device Update

You decide when your devices get an update. Please update soon in order to use the latest features (e.g. Adaptive Traffic Control, Track Calibration History) and to benefit from quality improvements (e.g. Model updates), bug fixes and security updates.

We will automatically update by 13.12.23.

Device Update size (2023.2 -> 2023.3):

  • P101/OP101 & NVIDIA Jetson devices: 460MB

  • P100/OP100: 470MB

Other improvements

  • Control Center - User Management - Invite users and manage permission of existing users

  • Control Center - MQTT client id can be defined for custom MQTT brokers

  • Data Analytics - Speed-up of Origin-Destination widgets

  • Data Analytics - Fix widget visualisation of the chord diagram (OD) and line charts

  • Under some conditions an ROI in combination with a rule did not trigger events

No breaking API/Event changes (only additions), this includes:

  • The Control Center API and Data Analytics API

  • The Event Format

To get started, check out the .

The device health metrics allow you to provide evidence for reliable and continuous data collection and to self-diagnose (e.g. stable network connectivity/power supply/camera connection/processing speed,... )

We replaced the model Parking (Single-/Multispace) with the model Traffic & Parking (Accuracy+). The model is tuned for accuracy while the processing speed (measured in FPS) is reduced. Ideally for use cases with less dynamic objects like and (Single- and Multispace).

Once defined, metadata allows you to filter the list of devices by metadata values and the generated events will include the pre-defined metadata for further processing by your application. For details have a look at the .

configuration steps
common problems
Adaptive Traffic Control
Parking Insights
event schema
Showcase Adaptive Traffic Control with the Rule Engine: Left Lane >=3 objects; Right Lane: >= 1 object
Model Description for Traffic & Parking (Accuracy+)
Device Metadata
Enable the feature for camera streams
A slider allows you to access the track calibrations of the last 24 hours