Summary
In riptide_mapping/riptide_mapping2/mapping.py, the transform_detection_to_object_parent method normalizes orientation for downward-facing objects by checking result.hypothesis.class_id against self.downwards_objects. However, in binary-classifier mode the detection class (e.g., blood) can differ from the assigned mapping target (e.g., bin_target1), causing downward normalization to be incorrectly skipped for downward targets.
This can inject unstable orientation updates into downward-facing mapping targets when the binary classifier is active.
Expected Fix
Replace the check on the raw detection class with a check on the resolved mapping target (child):
# Before
if result.hypothesis.class_id in self.downwards_objects.keys():
# After
if child in self.downwards_objects:
Context
Requester
Requested by @zehdari
Summary
In
riptide_mapping/riptide_mapping2/mapping.py, thetransform_detection_to_object_parentmethod normalizes orientation for downward-facing objects by checkingresult.hypothesis.class_idagainstself.downwards_objects. However, in binary-classifier mode the detection class (e.g.,blood) can differ from the assigned mapping target (e.g.,bin_target1), causing downward normalization to be incorrectly skipped for downward targets.This can inject unstable orientation updates into downward-facing mapping targets when the binary classifier is active.
Expected Fix
Replace the check on the raw detection class with a check on the resolved mapping target (
child):Context
Requester
Requested by @zehdari