gast@schmalzl.tirol — A detection demo with invented parcels
Style
?
PS gast@schmalzl ~C:\Users\gast/en/blog/2026-09-24-synthetische-pakete-erkennungsdemo

A detection demo with invented parcels

By · Written: · Archive discovery date:

#KI #3D #Daten

24 September 2026 · Archive date

A video of passing parcels can illustrate a detection idea: objects are marked, counted or assigned to a simple class. If the scene was generated artificially, this origin must stay visible.

For a learning exercise, invented cubes in different colours are enough. They carry no real addresses, identifiers or company logos. The goal is an understandable observation, not a replica of a real operation.

What should be detected?

A possible task is: count all blue cubes that fully cross a marked line. That is more precise than "Detect the parcels". Now you can define when an object counts and whether a brief occlusion should affect the count.

The artificial scene contains three blue and two yellow cubes. One is briefly hidden behind another. The expected result is written down before the attempt. This creates a small, traceable comparison.

Extra boxes and labels in the video are only a visualisation. They have to match the actual analysis. A marking drawn in afterwards does not prove that a system recognised the object itself.

Show the limits of the exercise too

A synthetic scene can offer controlled conditions. Real surfaces, changing light and other movements can bring additional difficulties. A successful demonstration therefore does not allow a blanket statement about later use.

The value of the small exercise lies in its understandable setup: a known starting scene, a clear counting rule and a visible comparison. If errors are shown and explained, that is often more instructive than a smoothly edited video in which every object seems to be assigned correctly without effort.

Original finds

These links were the starting point for this post. The assessment in the text is my own; the linked posts are not my own tests.

About the date: This post was written on 11 October 2026. The archive date corresponds to the earliest related find in the collection, not to a publication at that time. Technical assessments and sources added later refer to the time of writing.