Quantcast
Channel: TAO Toolkit - NVIDIA Developer Forums
Viewing all articles
Browse latest Browse all 549

Explanation on Detectnet_v2's `deadzone_radius` hyperparameter

$
0
0

We are training networks with Detectnet_v2 and are in the tuning process. We would like some clarification on the hyperparameter deadzone_radius. Per this documentation, deadzone_radius is

The area to be considered dormant (or area of no bbox) around the ellipse of an object. This is particularly useful in cases of overlapping objects so that foreground objects and background objects are not confused.

If I understand correctly, each detection is actually an ellipse with a box ideally circumscribing it. For example, say you want to detect a ball, the ellipse should be the same shape as the ball (since the object of interest is an ellipse itself). Then, the deadzone “around the ellipse of an object” (in our example) would be the area in red below:

If this is correct, then it would be best to set deadzone_radius: 1.0 since 100% of the area around the ellipse of the object is not part of the object (even though it is included in the bbox)? And, since not all objects are perfectly elliptical like a car for example:


The deadzone_radius would not be 1.0.

2 posts - 2 participants

Read full topic


Viewing all articles
Browse latest Browse all 549

Trending Articles