Our AI model has been mostly trained with adults. The detection of babies might be less accurate.
I’ll suggest you to disable the “body fitting” option, it might help a bit for baby detection.
I just tried to comment out the body fitting, I don’t see the effect though…
The baby skeleton keeps flicking, but the cam is just looking at the same scene without anything moving. (Baby doll) object_confidence is around 9% sometimes 70%
the object_id increment fast, is there any parameter to recognize the same object in the same location?
Note1: obj_runtime_param.detection_confidence_threshold is 0.01#40 (very low already, is there a threshold for object and another threshold for skeleton?)
Note2: I have kind of confuse with other threshold like runtime threshold, does it affect the cloud not object?
In my application, the baby does not move very often, is there any setting that once the skeleton is detected, it shows up in the 2D window for longer time? And without changing the object_id?
Plan B, is there any tutorial link of how to train a baby skeleton? And how to import the model into your code?
Do you need to detection the skeleton of the baby or only it’s position (bounding box) ?
Because, with the SDK you can use the Custom Detector feature (Using the Object Detection API with a Custom Detector | Stereolabs) which allow you to ingest 2D detection data from an external object detector into the SDK that will compute the 3D data (such as position, 3D bounding box…). That allow you to use another AI model, that can potentially detect baby more accurately.
If the bounding box is enough for your project, you can either try our object detection model (called MULTI_CLASS_BOX_ACCURATE) or use an external detector such as YOLO.
We will do more tests internally for the baby skeleton detection and try to improve the quality of the detection in the future release.
Could you record one or multiple SVOs showing this issue and share them with us.
Send us a mail at support@stereolabs.com with the SVOs files.
It will help us a lot.